Shepherd writeup for draft-ietf-clue-rtp-mapping-14:
[This is based on the template version 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?
This document is marked as Standards Track in the title page header,
and that is appropriate - it is defining required functionality for CLUE.
(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
This document describes how the Real Time transport Protocol (RTP) is
used in the context of the CLUE protocol (ControLling mUltiple
streams for tElepresence). It also describes the mechanisms and
recommended practice for mapping RTP media streams defined in Session
Description Protocol (SDP) to CLUE Media Captures and defines a new
RTP header extension (CaptureId).
Working Group Summary
Very late in the game we received substantial comments on this document
from an RTP expert that had not been active in the work group. This
led to some substantial revisions, primarily for alignment with other
RTP-related documents. The primary effect was to remove a lot of text
that was thought to be be confusing. Some tightening of language was
also added to improve privacy.
Document Quality
Are there existing implementations of the protocol?
A prototype implementation has been built and demonstrated.
Have a significant number of vendors indicated their plan to
implement the specification?
Not yet.
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?
Colin Perkins and Magnus Westerlund made major comments that resulted
in better alignment of this document with other work.
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?
N/A
Personnel
Who is the Document Shepherd?
Paul Kyzivat
Who is the Responsible Area Director?
Alissa Cooper
(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 shepherd has been an active reviewer of this document throughout
its development, and reviewed it again in its entirety while preparing
this writeup.
In the view of this shepherd the document is ready for
publication?
YES.
(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?
No concerns. The document has been thoroughly reviewed.
(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.
N/A
(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.
None
(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.
Yes, each author has stated they have no IPR claims on the document.
(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 has been filed against this document.
(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 strong WG consensus for this document by all those who have
actively participated in the group.
(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarize 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.)
No.
(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.
There are no nits.
(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.
N/A
(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?
There are normative references to several other CLUE drafts.
The intent is that these will all progress together.
There is also a normative reference to
draft-ietf-mmusic-sdp-bundle-negotiation-36. That draft is
itself near to completion. Waiting on it is acceptable.
(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.
There are no downrefs.
(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.
This document doesn't change the status of any other document.
(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 is in good order.
(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.
N/A - no new registries are defined.
(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.
None.