Shepherd writeup

Document shepherd write-up for draft-ietf-ccamp-flexigrid-lambda-label-04.txt

> (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 requested for publication as a Proposed Standard document.

This is appropriate because the document defines the encoding of GMPLS labels for flexible grid lambda switching capable devices. 
This track is noted in the document header.

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

GMPLS supports the description of optical switching by identifying entries in fixed lists of switchable wavelengths (called grids) through the encoding of lambda labels.  Work within the ITU-T Study Group 15 has defined a finer granularity grid, and the facility to flexibly select different widths of spectrum from the grid.  This document defines a new GMPLS lambda label format to support this flexi-grid.

This document updates RFC 3471 and RFC 6205 by introducing a new label format.

> Working Group Summary:

This document has been reviewed by the CCAMP working group and received
some comments at IETF meetings and on the mailing list.

There was some discussion about whether to include the management of multi-carrier signals (not yet standardized by the ITU-T). The WG came to consensus that these must be managed as per GMPLS inverse multiplexing capabilities already supported for TDM. The decision lead to the introduction of chapter 4.3 “composite labels”.

There were no problems with consensus for this document.

> Document Quality:

The work has had contributions from a large group of people, the draft is pretty simple, clear and based on RFC6205. Additionally, the work has had external review form the IDEALIST EU project that is making multiple inter-operating implementions of a GMPLS control plane for flexi-grid.

> Personnel:

Daniele Ceccarelli is the Document Shepherd
Deborah Brungard 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.

The document shepherd has reviewed the current revision of the
document and believes it 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 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.

The definition of a new label encoding does not introduce any new security considerations to RFC3471 and RFC3473. Other topics are not touched by the document.

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

The WG chairs chased all authors and contributors for statements that
they had complied with IETF IPR policy. All responded. The replies have been tracked in the datatracker and can be found in the history of 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 disclosures have been made.

> (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 has been substantial and broad review. There is good consensus 
on 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 threats or discontent.

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

idnits is clean apart from false positives.

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

No such reviews needed.

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

All references correctly identified.

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

None such.

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

idnits warns about normative references to ITU Recommendations as
potential downrefs, but everything is OK.

> (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 document updates RFC3471 and RFC6205. This is correctly noted in the header. 

> (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 section is consistent with the rest of the document. Two registries are requested to be updated. 

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

The draft does not request the definition of new registries. 

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

No such sections.