Shepherd writeup
rfc7680-05

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

Internet Standard.   See section 7, “RFC 2680 bis”, of the draft for a detailed discussion. The document being replaced, RFC 2680, is a proposed standard.


(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 memo (RFC 2680 bis) defines a metric for one-way delay of
packets across Internet paths.  It builds on notions introduced and
discussed in the IPPM Framework document, RFC 2330.  This memo makes RFC 2680 obsolete.

Working Group Summary

There was nothing unusual or controversial.

Document Quality

  Are there existing implementations of the protocol? 

"Surveyor Implementation Report RFC 2679-2680": https://www.ietf.org/proceedings/60/slides/ippm-6.pdf

https://tools.ietf.org/html/draft-ietf-ippm-implement-02


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?

See slides and documents referenced in “Document Quality”.

Personnel

The document shepherd is Bill Cerveny.  The responsible area director is Spencer Dawkins.

(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 was reviewed by the document shepherd for which changes were suggested and implemented in the draft. 

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

(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

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

No

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

It has support across the working group in general and participants familiar with the topic support the document.

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

Note downward refs documented by idnits  in question #15.

From idnits:
  
  -- The draft header indicates that this document obsoletes RFC2680, but the
     abstract doesn't seem to directly say this.  It does mention RFC2680
     though, so this could be OK.

The text from the abstract is, “This memo makes RFC 2680 obsolete.”

  == The document seems to lack the recommended RFC 2119 boilerplate, even if
     it appears to use RFC 2119 keywords -- however, there's a paragraph with
     a matching beginning. Boilerplate error?

     (The document does seem to have the reference to RFC 2119 which the
     ID-Checklist requires).

This appears to be a parsing error on the part of idnits.

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

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?

No

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

From idnits:

  ** Downref: Normative reference to an Informational RFC: RFC 2330

  ** Downref: Normative reference to an Informational RFC: RFC 7312

As discussed with Al Morton, editor:

“In the past, Wes Eddy put in a standing exception for 2330, the original framework.
We should ask for a similar exception for RFC 7312, which updates 2330, and has the
same status.

“In any case, Downrefs like these have to be on the exception list,
or specifically noted in the IETF Last Call Notice.”


(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 replaces and obsoletes RFC 2680. RFC 2680 was a proposed standard; the new document will be an Internet standard.

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

As stated in the draft, “This memo makes no requests of IANA.”  There are no IANA considerations.

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

None

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

Not applicable.

Back