Shepherd writeup
draft-ietf-mmusic-rfc4566bis-37

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

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?

Proposed Standard – the title page indicates the intended status of “Standards Track”, which is appropriate since the document obsoletes RFC 4566, which is also 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.

This memo defines the Session Description Protocol (SDP).  SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation.  This document obsoletes RFC 4566.


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?

This updated version of RFC 4566 has been in in the works since late 2007, and as such it has undergone a number of revisions and improvements consistent with overall work on SDP related extensions in that timeframe. Consensus on the document is solid and there are no particular controversies related to it. 



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 SDP protocol is widely implemented by a number of different vendors. A number of people in the MMUSIC group have contributed and commented over the years, however there is no single reviewer that merits special mention. 


Personnel

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

Flemming Andreasen is the Document Shepherd
Ben Campbell is the Responsible Area Director

(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.

I have reviewed -24, and -29 through -32 in detail. As a result of these reviews, various updates have been made and the document is ready for publication at this point. 


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

No concerns. 

(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 such 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.

Each author has confirmed

(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 disclosure

(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?   

There is solid consensus in the WG overall. 

(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.) 

Not applicable

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

The document has been checked for nits. The ID-Nits tool has a couple of false positives:
- RFCXXXX will be updated by the RFC Editor to refer to the assigned RFC number for this document
- The multicast IPv4 address (in the ABNF) is not an example address.
- There is no code in the document
- RFC2978 is indeed used as a reference in the document (in Section 6.10).
- E164 refers to ITU-T Recommendation E.164, which is an open external standard
- The reference to RFC 2327 is intentional


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

The document updates the existing registration of the “application/sdp” media type, and as such is subject to the procedures of RFC 6838, Section 5.5. Per RFC 6838, Section 3.1, this procedure is expected to be performed by the IESG as part of the publication process. 


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

Yes

(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?

The document normatively references draft-ietf-mmusic-ice-sip-sdp, which is currently not ready for advancements. The document is waiting for a potential update to align with recent changes to draft-ietf-rtcweb-jsep. Once this potential alignment issue has been resolved, the document is ready for publication. 

The document also normatively references draft-ietf-data-channel-sdpneg, which has been submitted for publication and is currently undergoing AD review.  


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

Not applicable. 

(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.

Yes. The document will obsolete RFC 4566, which is listed on the title page, and mentioned in both the abstract and introduction. 

(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 IANA considerations section has been reviewed and found to comply with the above. 

(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.

Not applicable. 

(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.

I have reviewed the current version (-32) detail. ID-nits have been run on the document, and the ABNF has been verified with Bill Fenner’s ABNF parsing service. 
Back