draft-rkhd-mpls-tp-sd-00-IETF.pptVIP

draft-rkhd-mpls-tp-sd-03 IETF 81 Jul 2011 Rafi Ram (rafir@) Daniel Cohn (danielc@) Masahiro Daikoku (ms-daikoku@) Ma Yuxia (ma.yuxia@) Yang Jian (yang.jian@) Alessandro D’Alessandro (alessandro.dalessandro@telecomitalia.it) Background This draft provides guidelines for signal degrade fault condition detection SD is a trigger for transport path (LSP, PW) protection SD detection from server/sub-layer MEP Proposes using MPLS-TP OAM message to indicate SD condition detection Updates (1) Change intended status to informational Changed LSP references to “transport path” Added text to explain that common purpose of the SD detection guidelines is that SD should reflect physical error conditions (e.g. low rx power, dispersion, bad connections), rather than non-physical error conditions (e.g. congestion, CPU overload) Updates (2) New SD detection guidelines Signal degrade conditions MUST be monitored by the lowest server layer or sub-layer that is not terminated between monitoring points Method for determining signal degrade SHOULD allow to localize links that contribute to signal degrade Method for determining signal degrade MUST be able to exit signal degrade condition when error rate returns to normal condition Method for determining signal degrade condition MUST be scalable Minor changes to other SD detection guidelines Updates (3) Consider a scenario where the lower-layer BER in each link traversed by the transport path is below the SD threshold, but the accumulated BER is above the threshold Relevant for lower-layer technologies where errored information is discarded (e.g. Ethernet) To support SD detection in these scenarios, nodes detecting high error rate MAY optionally include measured BER in link degradation fault messages Transport path client MEP declares SD based on the sum of received BER values Updates (4) Recommend using encapsulation and mechanism defined in draft-ietf-mpls-tp-fault to send link degradation fault indicati