Skip to main content

Telechat Review of draft-ietf-ccamp-ospf-availability-extension-08

Request Review of draft-ietf-ccamp-ospf-availability-extension
Requested revision No specific revision (document currently at 13)
Type Telechat Review
Team Ops Directorate (opsdir)
Deadline 2017-01-03
Requested 2016-11-29
Authors Hao Long , Min Ye , Greg Mirsky , Alessandro D'Alessandro , Himanshu C. Shah
I-D last updated 2017-02-05
Completed reviews Genart Last Call review of -07 by Jouni Korhonen (diff)
Secdir Last Call review of -07 by Rifaat Shekh-Yusef (diff)
Rtgdir Early review of -05 by Jonathan Hardwick (diff)
Genart Telechat review of -08 by Jouni Korhonen (diff)
Opsdir Telechat review of -08 by Mehmet Ersue (diff)
Genart Telechat review of -09 by Jouni Korhonen (diff)
Genart Telechat review of -10 by Jouni Korhonen (diff)
Assignment Reviewer Mehmet Ersue
State Completed
Request Telechat review on draft-ietf-ccamp-ospf-availability-extension by Ops Directorate Assigned
Reviewed revision 08 (document currently at 13)
Result Has nits
Completed 2017-02-05
I reviewed the document "OSPF-TE Link Availability Extension for Links with
Variable Discrete Bandwidth"
(draft-ietf-ccamp-ospf-availability-extension-08.txt) as part of the
Operational directorate's ongoing effort to review all IETF documents being
processed by the IESG. These comments were written primarily for the benefit of
the operational area directors. Document editors and WG chairs should treat
these comments just like any other last call comments.

Intended status: Standards Track
Current IESG state: AD is watching
IANA State: IANA OK - Actions Needed

The document introduces an optional Interface Switching Capability Descriptor
(ISCD) Availability sub-TLV to extend the GMPLS Open Shortest Path First (OSPF)
routing protocol for TE links with variable discrete bandwidth. It has been
recently extended to make it generic to apply to multiple technologies.

There are a few minor nits in the document:
The text in section 2 line 2 is misspelled: "include a< availability,
bandwidth> information list in its OSPF" s/e(s).The/e(s). The/

The document has been written with a proper language.
I think the document does not cause any issue related to operations and
management and can be published.