The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] [mpls] Re: [PWE3] New Liaison Statement,"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
The IETF response to our liaison of draft-ietf-pwe3-mpls-transport-00.txt was sent as a word document. To make sure that all members of PWE3 are able to read it, I have extracted the substantive text as ASCII. I have major concerns about the assumption of disjoint operation since I cannot see how the T-MPLS protocol prevents this. I request WG input on how to respond to this liaison. - Stewart ====== Thank you for your liaison statement “PWE3 and MPLS WG response to G.8110.1 Amendment 1”. We note your concerns with our work on T-MPLS and your draft http://www.ietf.org/internet-drafts/draft-ietf-pwe3-mpls-transport-00.txt. It appears that the work in the IETF is addressing some different requirements: “Input from network operators indicates that the key requirements is the transparent carriage of the MPLS network of one party over the MPLS network of another party, with the constraint that the MPLS design MUST NOT be changed and that the solution MUST be compatible with their existing large base of already deployed MPLS networks.” Some members of SG 15 expressed support for these requirements. However, the basis for the work in SG 15 has been the development of a packet switched network that meets all of the network operators transport operations requirements. The assumption we have made is that when deploying T-MPLS for this purpose it will be deployed on a network that is disjoint from any already deployed IP/MPLS network. Equipment developed prior to the approval of the T-MPLS Recommendations is not expected to comply with these Recommendations. Our intention in developing the suite of T-MPLS Recommendations is to define a packet based transport network technology. The design objectives of T-MPLS are: a) Follow the principles of the transport network used in other ITU-T defined transport technologies (e.g SDH, ATM, OTN). b) To use the PDU and forwarding plane processes defined by the IETF for MPLS. After the presentation of the Liaison Statement the following was noted: • T-MPLS OAM mechanisms have been developed by ITU-T G.8114/Y.1373 to provide transport-like fault and performance monitoring capabilities including alarm suppression, packet loss measurements and support of multiple ownerships • T-MPLS protection mechanisms have been developed by ITU-T G.8131 to provide transport-like protection schemes including trail and sub-network protection • The separation between the data plane and the control plane is a major requirement in transport networks An electronic copy of this liaison statement is available at: http://ties.itu.ch/ftp/public/itu-t/tsg15opticaltransport/COMMUNICATIONS/ _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls
|
|