Shepherd writeup
rfc7197-03

PROTO Writeup for draft-ietf-mmusic-delayed-duplication-02

(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 notes the document as 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

   A straightforward approach to provide protection against packet
   losses due to network outages with a longest duration of T time units
   is to simply duplicate the original packets and send each copy
   separated in time by at least T time units.  This approach is
   commonly referred to as Time-shifted Redundancy, Temporal Redundancy
   or simply Delayed Duplication.  This document defines an attribute to
   indicate the presence of temporally redundant media streams and the
   duplication delay in the Session Description Protocol.


Working Group Summary

  There is WG consensus behind this draft. All issues raised during
  and before WGLC have been addressed.


Document Quality

  The document has received reviews from working group participants
  both at MMUSIC and AVTEXT and the document shepherd.  There is
  currently at least one vendor implementing this mechanism and
  various other vendors have expressed interest for this technique.


Personnel

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

  Ari Keranen is the Document Shepherd, and the Responsible Area
  Director is Gonzalo Camarillo.


(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 has reviewed the past two versions of the
 document and believes the document is ready for publication.


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

 No.


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

 No need for any such review.


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

 Yes, the shepherd has received confirmation from all authors.


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

 There are no filed IPR disclosures for 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 seems to be good consensus on the current document by the WG,
  which seems to understand and agree with it.


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

 No.


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

 Idnits complains about possibly incorrect name for
 draft-ietf-mmusic-duplication-grouping and therefore possible
 downref. The reference is however correct and there is no
 downref. Idnits also complains about RFCXXXX references that will be
 fixed by RFC editor. 


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

  The document provides extensions to SDP only and as such the
  necessary review has already been done by the MMUSIC WG.


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

 Yes, all references are classified 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?

  There is no such dependency. The only normative reference in draft
  state is advanced at the same time.


(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 downward normative references.


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

  The publication of this document will not change the status of any
  existing RFC.


(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 no issues found. 


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

  There are no new IANA registries defined by this document.


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

  The ABNF in section 3 was checked with the Bap tool and appears to
  be correct.
Back