indicationofclientfaultinmpls-tpoam.pptVIP

Indication of Client Fault in MPLS-TP OAM draft-he-mpls-tp-csf-02 IETF 78th , July 25-30, 2010 Jia He (Huawei Technologies Co., Ltd.) Han Li (CMCC) Elisa Bellagamba (Ericsson) Changes from v01 to v02 Elisa Bellagamba joins as co-editor Detail the format of CSF packet Add new CSF types Add consequent actions General Overview RFC 5860[MPLS-TP OAM reqs] describes the requirement of Client Failure Indication in Section of 2.2.10. Client Signal Fail indication (CSF) 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. Format of CSF packet CSF types The connection between Node A and B recovers. Node B sends explicit failure clearance indication signals to Node C (to expedite clearance of native client) Node C clears client failure condition Next Step The editors would appreciate any comments and suggestions from the WG. Ready to become a WG document? Thanks! * The format of G-ACH follows [RFC 5586] G-ACH Channel Type : value 0xXX identifies the payload as CSF PDU. To be assigned by IANA. CSF PDU CSF Version: Set to 0; CSF Reserved 1: This field MUST be set to zero on transmission and ignored on receipt; CSF Reserved 2: This field MUST be set to zero on transmission and ignored on receipt; CSF Flags: (See next page) Total TLV Length: Total of all included TLVs. No TLVs are defined currently. The value is 0. Flag Reserved: Set to 0; Type: Set to the following values to indicate CSF types Period: CSF transmission period and can be configured. Clearance of Client Signal Fail - (CSF-Clear) 011 Client Signal Fail - Reverse Defect Indication (CSF-RDI) 010 Client Signal Fail - Forward Defect Indication (CSF-FDI) 001 Client Signal Fail - Loss of Signal (CSF-LOS) 000 Type Value A B C D CSF-LOS Failure detected between Node A and Node B (e.g. loss of signal) The MEP function in Node B initiates CSF signal to Node C