Resource Reservation Protocol (RSVP) Extensions for Path Key Support
draft-ietf-ccamp-path-key-ero-04

IANA Last Call comments:

Action 1:

Upon approval of this document, IANA will make the following
assignments in "Class Names, Class Numbers, and Class Types" at
http://www.iana.org/assignments/rsvp-parameters

Class
Number Class Name Reference
------ ----------------------- ---------
20 EXPLICIT_ROUTE [RFC3209]
Class Types or C-Types:
1 Type 1 Explicit Route [RFC3209]
Sub-object type
64 Path Key with 32-bit PCE ID [RFC-ccamp-path-key-ero-03]
65 Path Key with 128-bit PCE ID [RFC-ccamp-path-key-ero-03]

[Note: These values should match those defined in
http://www.iana.org/assignments/pcep/pcep.xhtml#path-key-subobject]


Action 2:

Upon approval of this document, IANA will make the following
assignments in "Class Names, Class Numbers, and Class Types" at
http://www.iana.org/assignments/rsvp-parameters

Class
Number Class Name Reference
------ ----------------------- ---------
21 ROUTE_RECORD [RFC3209]
(also known as RECORD_ROUTE)
Class Types or C-Types:
1 Type 1 Route Record [RFC3209]
Sub-object type
64 Path Key with 32-bit PCE ID [RFC-ccamp-path-key-ero-03]
65 Path Key with 128-bit PCE ID [RFC-ccamp-path-key-ero-03]

[Note: These values should be the same as in Action 1]


Action 3:

Upon approval of this document, IANA will make the following
assignments in the "Error Codes and Globally-Defined Error Value
Sub-Codes" registry at
http://www.iana.org/assignments/rsvp-parameters

Error Code Meaning
24 Routing Problem [RFC3209]
This Error Code has the following globally-defined Error
Value sub-codes:

[tbd(31)] = Unknown PCE-ID for PKS expansion
[RFC-ccamp-path-key-ero-03]
[tbd(32)] = Unreachable PCE for PKS expansion
[RFC-ccamp-path-key-ero-03]
[tbd(33)] = Unknown Path Key for PKS expansion
[RFC-ccamp-path-key-ero-03]
[tbd(34)] = ERO too large for MTU
[RFC-ccamp-path-key-ero-03]

We understand the above to be the only IANA Actions for this document.

Intended status : Standards Track

> (1.a) Who is the Document Shepherd for this document? Has the
> Document Shepherd personally reviewed this version of the
> document and, in particular, does he or she believe this
> version is ready for forwarding to the IESG for publication?

Deborah Brungard is the document shepherd.
She has personally reviewed the I-D and believes it is ready for
forwarding to the IESG for publication.

> (1.b) Has the document had adequate review both from key WG members
> and from key non-WG members? Does the Document Shepherd have
> any concerns about the depth or breadth of the reviews that
> have been performed?

This document has been reviewed by the CCAMP and PCE working groups.

> (1.c) Does the Document Shepherd have concerns that the document
> needs more review from a particular or broader perspective,
> e.g., security, operational complexity, someone familiar with
> AAA, internationalization or XML?

No concerns.

> (1.d) Does the Document Shepherd have any specific concerns or
> issues 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. Has an IPR disclosure related to this document
> been filed? If so, please include a reference to the
> disclosure and summarize the WG discussion and conclusion on
> this issue.

The document is sound.
No IPR disclosures filed.

> (1.e) 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 were no problems with consensus for this document.

> (1.f) 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
> entered into the ID Tracker.)

No threats. No discontent.

> (1.g) Has the Document Shepherd personally verified that the
> document satisfies all ID nits? (See
> http://www.ietf.org/ID-Checklist.html and
> http://tools.ietf.org/tools/idnits/). Boilerplate checks are
> not enough; this check needs to be thorough. Has the document
> met all formal review criteria it needs to, such as the MIB
> Doctor, media type and URI type reviews?

All checks made.

> (1.h) Has the document split its references into normative and
> informative? 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
> strategy for their completion? Are there normative references
> that are downward references, as described in [RFC3967]? If
> so, list these downward references to support the Area
> Director in the Last Call procedure for them [RFC3967].

References split.
No downrefs.

> (1.i) Has the Document Shepherd verified that the document IANA
> consideration section exists and is consistent with the body
> of the document? If the document specifies protocol
> extensions, are reservations requested in appropriate IANA
> registries? Are the IANA registries clearly identified? If
> the document creates a new registry, does it define the
> proposed initial contents of the registry and an allocation
> procedure for future registrations? Does it suggest a
> reasonable name for the new registry? See [RFC2434]. If the
> document describes an Expert Review process has Shepherd
> conferred with the Responsible Area Director so that the IESG
> can appoint the needed Expert during the IESG Evaluation?

IANA section is OK.
The IANA section requests consistent codepoint allocation with
draft-ietf-pce-path-key-05.txt.

> (1.j) Has the Document Shepherd verified that sections of the
> document that are written in a formal language, such as XML
> code, BNF rules, MIB definitions, etc., validate correctly in
> an automated checker?

No formal language present.

> (1.k) 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 paths taken by Multiprotocol Label Switching (MPLS) and
Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched
Paths (LSPs) may be computed by Path Computation Elements (PCEs).
Where the TE LSP crosses multiple domains, such as Autonomous Systems
(ASes), the path may be computed by multiple PCEs that cooperate,
with each responsible for computing a segment of the path.

To preserve confidentiality of topology within each AS, the PCEs
support a mechanism to hide the contents of a segment of a path (such
as the segment of the path that traverses an AS), called the
Confidential Path Segment (CPS), by encoding the contents as a Path
Key Subobject (PKS) and embedding this subobject within the result of
its path computation.

This document describes how to carry Path Key Subobjects in the
Resource Reservation Protocol (RSVP) Explicit Route Objects (EROs)
and Record Route Object (RROs) so as to facilitate confidentiality in
the signaling of inter-domain TE LSPs.

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

The draft was reviewed in last call across the CCAMP and PCE working
groups.

A last-minute question was raised on the number of bits assigned to
the path key ID (should 16 be extended to 32). This was resolved in
discussions on the PCE mailing list, and it was decided to leave it at
16 consistent with draft-ietf-pce-path-key-05.txt.

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

There are several interoperable implementations of
draft-ietf-pce-path-key-05.txt. These implementations are of no value
without the extensions defined in this draft (since a computed path is
of no value if you can't signal it).

There is one known experimental implementation of the extensions
defined in this draft.