Shepherd writeup

As required by RFC 4858, this is the current template for the Document Shepherd Write-Up. 

Changes are expected over time. This version is dated 24 February 2012.

(1) What type of RFC is being requested (BCP, Proposed Standard, Internet Standard, Informational, Experimental, or Historic)? Why is this the proper type of RFC? Is this type of RFC indicated in the title page header? 

A Proposed Standard RFC is being requested. The document specifies normatively how SDP offer/answer exchange is used to achieve out-of-band (non-DCEP) negotiation for WebRTC data channel setup. The title page indicates "Standards Track".

(2) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Write-Up. Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: 

Technical Summary:

 Relevant content can frequently be found in the abstract and/or introduction of the document. If not, this may be an indication that there are deficiencies in the abstract or introduction.

The Real-Time Communication in WEB-browsers (RTCWeb) working group has defined the concept of bi-directional data channels running on top of the Stream Control Transmission Protocol (SCTP), where each data channel might be used to transport other protocols, called subprotocols.  Data channel setup can be done using either the in-band Data Channel Establishment Protocol (DCEP) or using some out-of-band non-DCEP protocol.  This document specifies how the SDP (Session Description Protocol) offer/answer exchange can be used to achieve such an out-of-band non-DCEP negotiation.

Working Group Summary:

 Was there anything in WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough?


Document Quality:

 Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted? 

The document was reviewed and discussed multiple times by a fair amount of MMUSIC members (listed in Acknowledgements section). Nokia (former Alcatel-Lucent) implemented an earlier version of the draft, but no other implementations are known to the shepherd, although CLUE WG also makes use of WebRTC datachannel as the "CLUE channel" in their specifications and should therefore have seen some implementation.


 Who is the Document Shepherd? Who is the Responsible Area Director?

The Document Shepherd is Bo Burman.
The Responsible AD is Ben Campbell.

(3) Briefly describe the review of this document that was performed by the Document Shepherd. If this version of the document is not ready for publication, please explain why the document is being forwarded to the IESG.

The document shepherd read the submitted version of the document fully and found only a few minor nits that were announced on the mailing list and should be addressed in an upcoming revision.

(4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? 

There are no concerns. The document got good review from a fair number of MMUSIC members and all of those comments were addressed.

(5) Do portions of the document need review from a particular or from broader perspective, e.g., security, operational complexity, AAA, DNS, DHCP, XML, or internationalization? If so, describe the review that took place.

Not applicable.

(6) Describe any specific concerns or issues that the Document Shepherd has with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the WG has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here.

No concerns.

(7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why?

The authors have confirmed that they do not know of any IPR disclosures that would be required.

(8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures.

No IPR disclosures have been filed.

(9) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? 

A handful of interested people (except the authors) have commented on the draft in MMUSIC, and all those comments are addressed in the current draft.

(10) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise the areas of conflict in separate email messages to the Responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.)


(11) Identify any ID nits the Document Shepherd has found in this document. (See and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough.

No issues are found by ID nits tool.

(12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, media type, and URI type reviews.

Not applicable.

(13) Have all references within this document been identified as either normative or informative? 


(14) Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the plan for their completion? 

This document has no normative references that are not ready for advancement:
* ietf-rtcweb-data-channel; in RFC Ed queue MISSREF.
* ietf-mmusic-sctp-sdp; in RFC Ed queue MISSREF.
* ietf-mmusic-sdp-mux-attributes; in RFC Ed queue MISSREF.

(15) Are there downward normative references (see RFC 3967)? If so, list these downward references to support the Area Director in the Last Call procedure. 


(16) Will publication of this document change the status of any existing RFCs? Are those RFCs listed on the title page header, listed in the abstract, and discussed in the introduction? If the RFCs are not listed in the Abstract and Introduction, explain why, and point to the part of the document where the relationship of this document to the other RFCs is discussed. If this information is not in the document, explain why the WG considers it unnecessary.


(17) Describe the Document Shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all protocol extensions that the document makes are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that newly created IANA registries include a detailed specification of the initial contents for the registry, that allocations procedures for future registrations are defined, and a reasonable name for the new registry has been suggested (see RFC 5226).

The document shepherd reviewed the IANA section and its relation to and consistency with the document body, and found no issues. The IANA SDP attribute new usage level in section 8.3 is correct. No initial registrations for this new usage level are provided in this document.

(18) List any new IANA registries that require Expert Review for future allocations. Provide any public guidance that the IESG would find useful in selecting the IANA Experts for these new registries. 

New "DCSA" usage level added to the set of IANA "att-field" registries. Given that all other "att-field" registries require expert review, it is reasonable to assume the same "Specification Required" status for this one. Suggest the same expert as for the existing registries in that set: Flemming Andreasen.

(19) Describe reviews and automated checks performed by the Document Shepherd to validate sections of the document written in a formal language, such as XML code, BNF rules, MIB definitions, etc. 

Passes Bill's ABNF Parser (