draft-ietf-mpls-tp-linear-protection-05.txt   draft-ietf-mpls-tp-linear-protection-06.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: September 14, 2011 N. Sprecher, Ed. Expires: September 14, 2011 N. Sprecher, Ed.
Nokia Siemens Networks Nokia Siemens Networks
A. Fulignoli, Ed. A. Fulignoli, Ed.
Ericsson Ericsson
Y. Weingarten Y. Weingarten
Nokia Siemens Networks Nokia Siemens Networks
March 13, 2011 March 13, 2011
MPLS-TP Linear Protection MPLS-TP Linear Protection
draft-ietf-mpls-tp-linear-protection-05.txt draft-ietf-mpls-tp-linear-protection-06.txt
Abstract Abstract
The Transport Profile for Multiprotocol Label Switching (MPLS-TP) is The Transport Profile for Multiprotocol Label Switching (MPLS-TP) is
being specified jointly by IETF and ITU-T. This document addresses being specified jointly by IETF and ITU-T. This document addresses
the functionality described in the MPLS-TP Survivability Framework the functionality described in the MPLS-TP Survivability Framework
document [SurvivFwk] and defines a protocol that may be used to document [SurvivFwk] and defines a protocol that may be used to
fulfill the function of the Protection State Coordination for linear fulfill the function of the Protection State Coordination for linear
protection, as described in that document. protection, as described in that document.
skipping to change at page 35, line 42 skipping to change at page 35, line 42
[5] If the SF being cleared is SF-P, Transition to N. If it's SF-W, [5] If the SF being cleared is SF-P, Transition to N. If it's SF-W,
ignore the clear. ignore the clear.
[6] Remain in current state (UA:x:R), if the SFc corresponds to a [6] Remain in current state (UA:x:R), if the SFc corresponds to a
previous SF then begin transmitting NR(0,0). previous SF then begin transmitting NR(0,0).
[7] If domain configured for revertive behavior transition to WTR, [7] If domain configured for revertive behavior transition to WTR,
else transition to DNR else transition to DNR
[7] Remain in PA:F:R and transmit NR(0,1) [8] Remain in PA:F:R and transmit NR(0,1)
[8] Remain in WTR, send NR(0,1) [9] Remain in WTR, send NR(0,1)
[9] Transition to UA:LO:R continue sending SF(0,0) [10] Transition to UA:LO:R continue sending SF(0,0)
[10] Transition to UA:LO:R and send SF(1,0) [11] Transition to UA:LO:R and send SF(1,0)
[11] Transition to UA and send SF(1,0) [12] Transition to UA and send SF(1,0)
[12] Transition to PF:W:R and send NR(0,1) [13] Transition to PF:W:R and send NR(0,1)
[13] Transition to WTR state and continue to send the current [14] Transition to WTR state and continue to send the current
message. message.
[14] Transition to DNR state and continue to send the current [15] Transition to DNR state and continue to send the current
message. message.
[15] Transition to N state and continue to send the current message. [16] Transition to N state and continue to send the current message.
[16] If the receiving node's WTR timer is running, maintain current [17] If the receiving node's WTR timer is running, maintain current
state and message. If the WTR timer is stopped, transition to N. state and message. If the WTR timer is stopped, transition to N.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., [RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N.,
 End of changes. 11 change blocks. 
11 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/