Hi,
Comments arising from my AD review and from discussion on the TEAS mailing list.
Please address these with other last call comments you receive.
You need to split the Authors' Addresses section and move out all those
not on the current front page to be present in a Contributors section.
---
You seem to have the name of RFC 6205 in the references section a bit
wrong!
---
Do you really mean that you are updating 6205? That is the document
that defines lambda labels.
It has no mention of G.709 despite what you say in the Abstract. This
seems a little odd.
What is more, I don't see any discussion of updates to the label format
or usage in the document although Section 4 does say
[RFC6205] defines the label format as applicable to LSC capable
device. This document extends [RFC6205] as make its label format
applicable also to WSON-LSC capable devices.
I don't think that applying the label to WSON without changing its
meaning or the way it is used is really an "update".
---
Section 2 has FOADM, but it is not used in the document.
You need to hyphenate "Cross Connect" unless you are really angry :-)
---
Section 3 gives a caption to a list
List 1. WSON Signal Characteristics
I've not seen that before in an I-D, and since you don't refer to the
list by name, I suggest you just delete this.
---
I wish you hadn't suggested explicit values for the two new Error Codes
in 4.2.2 and 6. But we'll see what IANA says during IETF last call.
---
During the review of draft-ietf-teas-lsp-attribute-ro it was noted that rules
are needed about where in an ERO the sub-objects are allowed, and that these
rules are dependent on the TLVs included in the sub-objects.
The following text was suggested:
The WSON Processing HOP Attribute TLV with ResourceBlockInfo MUST be
present after an explicit Hop addressing an TE Router ID identifying a
specific node or a Link ID identifying an incoming TE link. it MUST NOT be
present after a loose, abstract node, Link ID identifying an outgoing TE
link, Component Interface ID or Label.
The WSON Processing HOP Attribute TLV with WavelengthSelection only MUST
be present after an explicit Hop addressing an TE Router ID identifying a
specific node, a Link ID identifying an incoming TE link, loose hop,
abstract node, Link ID identifying an outgoing TE lin or Component
Interface ID. it MUST NOT be present after a Label.
The WavelengthSelection may apply starting at an abstract node, but not
after a label (as no selection is possible)
-----Original Message-----
From: IETF-Announce [mailto:ietf-announce-bounces(_at_)ietf(_dot_)org] On
Behalf Of The
IESG
Sent: 04 March 2015 15:07
To: IETF-Announce
Cc: ccamp(_at_)ietf(_dot_)org
Subject: Last Call: <draft-ietf-ccamp-wson-signaling-09.txt> (Signaling
Extensions
for Wavelength Switched Optical Networks) to Proposed Standard
The IESG has received a request from the Common Control and Measurement
Plane WG (ccamp) to consider the following document:
- 'Signaling Extensions for Wavelength Switched Optical Networks'
<draft-ietf-ccamp-wson-signaling-09.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2015-03-18.