70 likes | 225 Views
Indication of Client Fault in MPLS-TP OAM. draft-he-mpls-tp-csf-02 IETF 7 9 th , November 7 - 12 , 2010 Jia He (Huawei Technologies Co., Ltd.) Han Li (CMCC) Elisa Bellagamba (Ericsson). History. v00 was presented in IETF 75th meeting in PWE3 WG
E N D
Indication of Client Fault in MPLS-TP OAM draft-he-mpls-tp-csf-02 IETF 79th , November7-12, 2010 Jia He (Huawei Technologies Co., Ltd.) Han Li (CMCC) Elisa Bellagamba (Ericsson)
History • v00 was presented in IETF 75th meeting in PWE3 WG • together with "draft-martini-pwe3-static-pw-status-00", with the assumption that these two drafts may be solving the same problem • v01 was presented in IETF 76th meeting in MPLS WG (MPLS-TP session) • agreed as under the scope of MPLS-TP • v02 was presented in IETF 78th meeting in MPLS WG (MPLS-TP session) • Questions come again about the requirements and the relationship between draft-he-mpls-tp-csf and draft-ietf-pwe3-static-pw-status
Requirement • Similar as the requirements for other MPLS-TP OAM functions, the requirement of Client Fault Indication function is defined in RFC 5860[MPLS-TP OAM reqs] (Section 2.2.10). • The MPLS-TP OAM toolset MUST provide a function to enable the propagation, from edge to edge of an MPLS-TP network, of information pertaining to a client (i.e., external to the MPLS-TP network) defect or fault condition detected at an End Point of a PW or LSP, if the client layer OAM functionality does not provide an alarm notification/propagation functionality. • Client Signal Fail indication (CSF) is such a toolthat provides a function to enable a MEP to propagate a client failure indication to its peer MEP across a MPLS-TP network in case the client service itself does not support propagation of its failure status.
Summary of draft-he-mpls-tp-csf • draft-he-mpls-tp-csf defines CSF PDU and procedure to meet MPLS-TP OAM requirements that can be transmitted on • LSP; • IP and MPLS labeled services as the clients of MPLS-TP; or • or PW • PW-based services as the clients of MPLS-TP • MPLS-TP CSF OAM packets share common forwarding of the user packets. • RFC 5921 defines 4 different type of MPLS-TP clients • Emulated Service • PW over LSP • IP over LSP • IP
Differences between draft-he-mpls-tp-csfand draft-ietf-pwe3-static-pw-status
Proposed Solutions • Proposal 1 • Keep the description in draft-he-mpls-tp-csf about CSF signal transmitted on PW when MPLS-TP clients are PW-based services aligned with AC fault status transmitted on PW as described in draft-ietf-pwe3-static-pw-status; • Keep the description about CSF signal transmitted on LSP in draft-he-mpls-tp-csf when MPLS-TP clients are IP and MPLS labeled services • Proposal 2 • Keep two separate drafts • draft-he-mpls-tp-csf for MPLS-TP environment, dealing with only client fault indication to be transmitted on PWs or LSPs; • draft-ietf-pwe3-static-pw-status for static PW, dealing with all the PW status to be transmitted on PWs only • Other proposals?
Next Step • The editors would appreciate guidance from the Chairs and the group. • Ready to become a WG document?