GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) Configuration
RFC 7260

Note: This ballot was opened for revision 12 and is now closed.

(Adrian Farrel) (was Discuss, Yes) Yes

Comment (2014-02-26)
No email
send info
IANA issues have been discussed and resolved to my satisfaction

(Jari Arkko) No Objection

(Richard Barnes) No Objection

(Stewart Bryant) No Objection

Comment (2014-01-22 for -12)
No email
send info
This is a well written document and I just have a few nits that you might consider.

There were a number of terms that as far as I could see were unexpanded on first use and are not "well known". I picked up DWDM, RSVP-TE, LSP, WSON, TDM, SDH/SONET. Please can I suggest an quick abbreviation scrub.

With the text "the ADMIN_STATUS Object is specified for RSVP-TE in [RFC3473]. "  This ref should go a little earlier in the para, when you first use the term

"If this is not possible, a PathErr SHOULD be sent "
and
"a ResvErr may be sent"

Presumable these are "messages" or "responses"


    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Type (IANA)         |           Length              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    OAM Type   |                 Reserved                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   ~                           sub-TLVs                            ~
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Type: indicates a new type: the OAM Configuration TLV (IANA to
   assign).

Is the length syntax well known in this context?

(Gonzalo Camarillo) No Objection

(Benoît Claise) No Objection

(Spencer Dawkins) No Objection

(Stephen Farrell) No Objection

(Brian Haberman) No Objection

(Joel Jaeggli) No Objection

Comment (2014-01-21 for -12)
No email
send info
lools like -12 addressed outstanding opsdir comments.

Barry Leiba (was Discuss) No Objection

Comment (2014-02-25)
No email
send info
Than you for addressing my DISCUSS and comments in version -13.

(Pete Resnick) No Objection

(Martin Stiemerling) No Objection

(Sean Turner) No Objection

Comment (2014-01-22 for -12)
No email
send info
Thanks for clearly identifying the new security consideration and explaining how it can be mitigated.