Shepherd writeup
rfc7689-12

Write up for draft-ietf-ccamp-wson-signaling

> As required by RFC 4858, this is the current template for the Document 
> Shepherd Write-Up.
> 
> 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)?

Standards Track

> Why is this the proper type of RFC?  

The document defines RSVP related formats and behaviors. 

> Is this type of RFC indicated in the title page header?

Yes.
 
> (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 provides extensions to Generalized Multi-Protocol Label
   Switching (GMPLS) signaling for control of wavelength switched
   optical networks (WSON).  Such extensions are applicable in WSONs
   under a number of conditions including: (a) when optional
   processing, such as regeneration, must be configured to occur at
   specific nodes along a path, (b) where equipment must be configured
   to accept an optical signal with specific attributes, or (c) where
   equipment must be configured to output an optical signal with
   specific attributes. In addition this memo provides mechanisms to
   support distributed wavelength assignment with choice in distributed
   wavelength assignment algorithms. These extensions build on previous
   work for the control of lambda and G.709 based networks. This
   document updates [RFC6205] as make it applicable to WSON-LSC capable
   equipment.
 
> 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 topic been discussed in the WG for a very long time, perhaps 6
years.  Support for the work has been tepid, but there are multiple
sets of contributors who would like to see the work result in proposed
standards. 
 
> 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 base GMPLS protocol has been implemented.  The extensions defined in
this document are compatible with earlier implementations.  Multiple
implementors have stated their intent to implement, or have stated that
they have already implemented, the mechanisms defined in this document.

> Personnel
> 
>   Who is the Document Shepherd? 

Lou Berger

> Who is the Responsible Area Director?

Adrian Farrel 

> (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 document as it has progressed
through the CCAMP WG, including as part of an extended WG last calls.
The Shepherd believes this document is ready for publication. This
document is part of a set of documents on WSON and final publication --
and at the AD's discretion, IETF LC -- should occur as a set.
The documents set includes:
    draft-ietf-ccamp-rwa-info
    draft-ietf-ccamp-general-constraint-encode
    draft-ietf-ccamp-rwa-wson-encode
    draft-ietf-ccamp-gmpls-general-constraints-ospf-te
    draft-ietf-ccamp-wson-signal-compatibility-ospf
    draft-ietf-ccamp-wson-signaling

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

As part of the 2nd WG LC, both the OSPF WGs chairs were consulted, and
one provided comments.
 
> (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, via messages to/on the CCAMP WG list.
 
> (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 disclosed 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?   

Good among interested parties. No objections from others.

> (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 to my knowledge.
 
> (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.

The document passes tools idnits with 1 warning.
 
> (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?


Note that this document uses mechanisms defined in
draft-ietf-ccamp-lsp-attribute-ro which the WG expects to progress/LC
shortly. Given the size of the WSON document set, we expect this
document will be ready for publication at the roughly 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. 

None. 

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

No.
 
> (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 was fully reviewed by the document shepherd.  Three new
allocations are requested in this document. 

Two registries are created, both with Standards Action and Specification
Required policies as defined in [RFC5226].

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

This document contains RBNF as defined in RFC5511.  There are no automated
tools for the validation of such, but RBNF was reviewed and discussed as
part of last call.
Back