Last Call Review of draft-ietf-ccamp-oam-configuration-fwk-11

Request Review of draft-ietf-ccamp-oam-configuration-fwk
Requested rev. no specific revision (document currently at 13)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-01-05
Requested 2013-12-12
Authors Attila Takacs, Don Fedyk, He Jia
Draft last updated 2013-12-30
Completed reviews Genart Last Call review of -11 by David Black (diff)
Genart Telechat review of -12 by David Black (diff)
Secdir Last Call review of -11 by Magnus Nystrom (diff)
Opsdir Last Call review of -11 by Warren Kumari (diff)
Assignment Reviewer David Black 
State Completed
Review review-ietf-ccamp-oam-configuration-fwk-11-genart-lc-black-2013-12-30
Reviewed rev. 11 (document currently at 13)
Review result Ready with Nits
Review completed: 2013-12-30


One additional nit - Don Fedyk's email address listed in the draft does not work.


> -----Original Message-----
> From: Black, David
> Sent: Sunday, December 29, 2013 9:46 PM
> To: General Area Review Team (gen-art at; attila.takacs at;
> donald.fedyk at; hejia at
> Cc: Black, David; adrian at; ccamp at; ietf at
> Subject: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-11
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <>.
> Please resolve these comments along with any other Last Call comments
> you may receive.
> Document: draft-ietf-ccamp-oam-configuration-fwk-11
> Reviewer: David L. Black
> Review Date: December 29, 2013
> IETF LC End Date: January 5, 2014
> Summary: This draft is basically ready for publication, but has nits that
> should be fixed before publication.
> This draft describes the GMPLS framework for signaling OAM configuration,
> and specifies additional RSVP elements to support that signaling.  Knowledge
> of RSVP, and specifically RSVP-TE is assumed; beyond that, the draft is
> complete, although it is very detailed - see editorial comment below on
> Section 3.
> Nits/editorial comments:
> Sections 3.1-3.3 dive into the details very quickly.  They would be easier to
> understand if there was an overview paragraph near the start of Section 3 that
> describes the roles of the two ADMIN_STATUS flags and the two LSP Attributes
> flags in OAM configuration (establishment, change/adjustment, deletion) before
> the current text that contains the details of RSVP message processing.
> There are a number of instances of "(IANA to assign)" in section 4 that the
> RFC Editor will need to remove - an RFC Editor note to that effect should
> be inserted at the start of Section 4.
> Section 4.5 is necessarily incomplete on P2MP considerations, because (as
> it says) "P2MP OAM mechanisms are very specific to the data plane technology".
> It would be helpful if section 4.5 contained language indicating what a
> specific data plane specification should include to completely specify
> P2MP OAM configuration for that data plane.
> idnits 2.13.01 didn't find anything that needs attention.
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> at        Mobile: +1 (978) 394-7754
> ----------------------------------------------------