Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Internet Architecture Board <email@example.com>, RFC Editor <firstname.lastname@example.org>, ccamp mailing list <email@example.com>, ccamp chair <firstname.lastname@example.org> Subject: Protocol Action: 'Generalized Labels for Lambda-Switching Capable Label Switching Routers' to Proposed Standard (draft-ietf-ccamp-gmpls-g-694-lambda-labels-11.txt) The IESG has approved the following document: - 'Generalized Labels for Lambda-Switching Capable Label Switching Routers' (draft-ietf-ccamp-gmpls-g-694-lambda-labels-11.txt) as a Proposed Standard This document is the product of the Common Control and Measurement Plane Working Group. The IESG contact persons are Adrian Farrel and Stewart Bryant. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ccamp-gmpls-g-694-lambda-labels/
Technical Summary This document is a companion to the Generalized Multi-Protocol Label Switching (GMPLS) signaling. [RFC3471] defined that a wavelength label (section 188.8.131.52) "only has significance between two neighbors" and global wavelength semantics is not considered. In order to facilitate interoperability in a network composed of lambda switch-capable equipment, this document defines a standard lambda label format, which is compliant with both [G.694.1](DWDM-grid) and [G.694.2](CWDM-grid). Working Group Summary This document received much attention and discussion in its early revisions. The document has been largely stable for quite some time, mainly needing revisions as part of the publication process. Document Quality There have been no public statements related to intent to implement, but the portions of the extensions are now being used as part of the GMPLS tool set and are expected to implemented (at least) in those contexts. The label format and information have been discussed in depth with ITU-T Q6/15 including at a joint meeting. Personnel Lou Berger (email@example.com) is the Document Shepherd. Adrian Farrel (firstname.lastname@example.org) is the Responsible AD.