Liaison statement
LS53 - Review of the MPLS-TP Requirements draft
Additional information about IETF liaison relationships is available on the
IETF webpage
and the
Internet Architecture Board liaison webpage.
| State | Posted |
|---|---|
| Submitted Date | 2009-06-04 |
| From Group | ITU-T-SG-15 |
| From Contact | Hiroshi Ota |
| To Group | MEAD |
| To Contacts | loa@pi.nu |
| Cc | sob@harvard.edu stbryant@cisco.com rcallon@juniper.net adrian.farrel@huawei.com yoichi.maeda@ntt-at.co.jp sjtrowbridge@alcatel-lucent.com mead@ietf.org |
| Response Contact | tsbsg15@itu.int greg.jones@itu.int hiroshi.ota@itu.int |
| Technical Contact | Ghani.Abbas@ericsson.com hhelvoort@huawei.com malcolm.betts@huawei.com hklam@alcatel-lucent.com |
| Purpose | For information |
| Attachments | LS53 - Review of the MPLS-TP Requirements draft - pdf |
| Body |
Thank you for providing the MPLS-TP requirements (draft-ietf-mpls-tp-requirements-08.txt) for our review. We support the approval of this draft provided that you implement the changes listed below: 1 Requirement 59: Item c should be moved from requirement 59 to a separate requirement since it is not part of the SLA 2 Requirement 70: Should be moved to the restoration section (2.8.2). Currently, it is under the protection section. 3 Requirement 66 D: The term "backtracking" should be defined, this should be included in the rosetta draft. 4 Ring protection section 2.8.6.1 : The paragraph below requirement e, replace the words in "this section" with “section 2.8.6.1" and replace the words "expressed above" by "requirements expressed in sections 2.8 up to section 2.8.6.1" 5 Requirement 107B: Replace the current text with following: It SHOULD protect against multiple failures |