Shepherd writeup
rfc7898-05

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

Experimental.

> Why is this the proper type of RFC?  

The document defines RSVP related formats that are at this juncture being used only for 
"experimental" purposes. The experimentation is expected to continue until there
is sufficient experience gained to determine if this is a function worth standardization.

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

The Resource ReserVation Protocol - Traffic Engineering (RSVP-TE) 
specification and the Generalized Multiprotocol Label Switching 
(GMPLS) extensions to RSVP-TE allow abstract nodes and resources 
to be explicitly included in a path setup.  Further Exclude Routes 
extensions to RSVP-TE allow abstract nodes and resources to be 
explicitly excluded in a path setup.

This document specifies new subobjects to include or exclude domain 
during path setup where domain is a collection of network elements 
within a common sphere of address management or path computational 
responsibility (such as an Interior Gateway Protocol (IGP) area or an 
Autonomous System (AS)).

This is a companion document to Path Computation Element Protocol 
(PCEP) extensions for the domain sequence [PCE-DOMAIN] 
(http://datatracker.ietf.org/doc/draft-ietf-pce-pcep-domain-sequence/).

> 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 document moved from the CCAMP WG to TEAS WG as part of the 
routing WG changes. The progress of the draft through the WG 
(first CCAMP, then TEAS) has been smooth.

> 
> 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 (G)MPLS RSVP protocol has been implemented. The 
extensions defined in this document are compatible with earlier 
implementations.  There have been no public statements on 
implementation. Three of the four authors are from the same 
vendor organization while the fourth is from a research institute – 
implementation for experimental purposes is expected.  

> Personnel
> 
>   Who is the Document Shepherd? 

Vishnu Pavan Beeram

> Who is the Responsible Area Director?

Deborah Brungard

> 
> (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 WG (first CCAMP, then TEAS). The Shepherd believes this 
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?

No.

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

The document shepherd has no concerns regarding "experimentation" with
the proposed extensions. It is to be noted that some in the WG (first in CCAMP 
and then in TEAS) have questioned the utility of some/all of the functionality 
discussed in this draft. This is one of the reasons why "experimental" status is 
appropriate for this document.

> 
> (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, see thread
http://www.ietf.org/mail-archive/web/teas/current/msg00425.html

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

Yes, an IPR disclosure has been filed that references this document
(https://datatracker.ietf.org/ipr/2186/). There was no WG discussion 
regarding the IPR. The disclosure was filed in a timely manner.

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

Given the “experimental” nature of this document, the overall support
for this document has been tepid. However, the consensus is solid among 
the few who are interested. "strong concurrence of a few individuals, 
with others not caring about this work one way or the other" is a reasonable 
characterization.

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

> 
> (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 ID 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 no normative references to documents that are not ready for 
advancement or are otherwise in an unclear state. However, it is to be 
noted that there is a normative reference to the companion document - 
(http://datatracker.ietf.org/doc/draft-ietf-pce-pcep-domain-sequence/) 
- [PCE-DOMAIN]. At the time of publishing this “Shepherd Write-Up”, 
[PCE-DOMAIN] had completed PCE WG Last Call.

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

As stated above, there is a normative reference to the companion document - 
[PCE-DOMAIN] (http://datatracker.ietf.org/doc/draft-ietf-pce-pcep-domain-sequence/). 
At the time of publishing this “Shepherd Write-up”, [PCE-DOMAIN] was at the same 
maturity level as this document.

> (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. All protocol 
extensions that the document makes are associated with the appropriate 
reservations in IANA registries.

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

N/A
Back