Liaison statement
Update to "MPLS-TP NM Req-03 Avaiable (ref # 004.02)" (ref 04.003)
Additional information about IETF liaison relationships is available on the
IETF webpage
and the
Internet Architecture Board liaison webpage.
State | Posted |
---|---|
Submitted Date | 2009-09-04 |
From Group | mpls |
From Contact | Loa Andersson |
To Groups | ITU-T-SG-15-Q10, ITU-T-SG-15-Q12, ITU-T-SG-15-Q14, ITU-T-SG-15-Q9 |
To Contacts | greg.jones@itu.int |
Cc | yoichi.maeda@ntt-at.co.jp greg.jones@itu.int ghani.abbas@ericsson.com hhelvoort@huawei.com malcolm.betts@huawei.com hklam@alcatel-lucent.com tsbg15@itu.int ahmpls-tp@lists.itu.int loa.andersson@ericsson.com adrian.farrel@huawei.com rcallon@juniper.net paf@cisco.com housley@vigilsec.com olaf@NLnetLabs.nl rbonica@juniper.net mpls-tp@ietf.org mead@ietf.org |
Response Contact | loa.andersson@ericsson.com |
Technical Contact | loa.andersson@ericsson.com |
Purpose | For information |
Attachments | (None) |
Body |
This liaison is to inform you that an editing error were detected in version -03 of the MPLS NM Requirements, this has been corrected in version -04 of the document as follows: In Appendix A bullet #2 OLD 2. The CCh may be provided by a link in the transport network that is terminated at the ends of the DCC and which is capable of encapsulating and terminating packets of the management protocols. For example, in MPLS-TP a single-hop LSP might be established between two adjacent nodes, and that LSP might be capable of carrying IP traffic. Management traffic can then be inserted into the link in an LSP parallel to the LSPs that carry user traffic. NEW 2. The CCh may be provided by a link in the transport network that is terminated at the ends of the CCh and which is capable of encapsulating and terminating packets of the management protocols. For example, in MPLS-TP a single-hop LSP might be established between two adjacent nodes, and that LSP might be capable of carrying IP traffic. Management traffic can then be inserted into the link in an LSP parallel to the LSPs that carry user traffic. And in Appendix A bullet #5 OLD 5. The CCh may provided by a dedicated channel associated with the data link. For example, the generic associated label (GAL) [13] may be used to label DCC traffic being exchanged on a data link between adjacent transport nodes, potentially in the absence of any data LSP between those nodes. NEW 5. The CCh may provided by a dedicated channel associated with the data link. For example, the generic associated label (GAL) [13] may be used to label CCh traffic being exchanged on a data link between adjacent transport nodes, potentially in the absence of any data LSP between those nodes. Since we believe this is a very minor change we do not think this will require any extra time, but will expect your response on our liaison "MPLS-TP NM Req-03 Avaiable (ref # 004.02)" on Sep 15, and will, if positive, interprete as if we can go ahead request publication of version -04 of the document as an RFC on the standards track. Loa Andersson Co-Chair of the MPLS WG Chair of the IETF MEAD team |