diff --git a/index.bs b/index.bs
new file mode 100644
index 0000000..cda44e6
--- /dev/null
+++ b/index.bs
@@ -0,0 +1,396 @@
+
+Title: WebRTC RTP Transport
+Shortname: webrtc-rtptransport
+Level: None
+Status: ED
+Group: webrtc
+TR: https://www.w3.org/TR/webrtc-rtptransport/
+Repository: w3c/webrtc-rtptransport
+URL: https://github.com/w3c/webrtc-rtptransport
+Editor: Peter Thatcher, w3cid 68236, Microsoft Corporation https://www.microsoft.com, pthatcher@microsoft.com
+Editor: Bernard Aboba, w3cid 65611, Microsoft Corporation https://www.microsoft.com, bernarda@microsoft.com
+
+Abstract: The WebRTC-RtpTransport API allows web applications to send and receive packets
+Abstract: using the RTP/RTCP protocol defined in [[RFC3550]].
+Complain About:accidental-2119 yes
+Markup Shorthands: css no, markdown yes, dfn yes
+!Participate: Git Repository.
+!Participate: File an issue.
+!Version History: https://github.com/w3c/webrtc-rtptransport/commits
+
The WebRTC-RtpTransport API allows web applications to send and receive packets
+
+using the RTP/RTCP protocol defined in [RFC3550].
+
+
Status of this document
+
+
This is a public copy of the editors’ draft.
+ It is provided for discussion only and may change at any moment.
+ Its publication here does not imply endorsement of its contents by W3C.
+ Don’t cite this document other than as work in progress.
+
If you wish to make comments regarding this document, please send them to public-webrtc@w3.org (subscribe, archives).
+ When sending e-mail,
+ please put the text “webrtc-rtptransport” in the subject,
+ preferably like this:
+ “[webrtc-rtptransport] …summary of comment…”.
+ All comments are welcome.
This document was produced by a group operating under
+ the W3C Patent Policy.
+ W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group;
+ that page also includes instructions for disclosing a patent.
+ An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
Conformance requirements are expressed
+ with a combination of descriptive assertions
+ and RFC 2119 terminology.
+ The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
+ in the normative parts of this document
+ are to be interpreted as described in RFC 2119.
+ However, for readability,
+ these words do not appear in all uppercase letters in this specification.
+
All of the text of this specification is normative
+ except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
+
Examples in this specification are introduced with the words “for example”
+ or are set apart from the normative text
+ with class="example",
+ like this:
+
+
+
This is an example of an informative example.
+
+
Informative notes begin with the word “Note”
+ and are set apart from the normative text
+ with class="note",
+ like this:
+
Note, this is an informative note.
+
+
Conformant Algorithms
+
Requirements phrased in the imperative as part of algorithms
+ (such as "strip any leading space characters"
+ or "return false and abort these steps")
+ are to be interpreted with the meaning of the key word
+ ("must", "should", "may", etc)
+ used in introducing the algorithm.
+
Conformance requirements phrased as algorithms or specific steps
+ can be implemented in any manner,
+ so long as the end result is equivalent.
+ In particular, the algorithms defined in this specification
+ are intended to be easy to understand
+ and are not intended to be performant.
+ Implementers are encouraged to optimize.