| draft-ietf-mpls-tp-aps-updates-04v3.txt | draft-ietf-mpls-tp-aps-updates-04v3output.txt | |||
|---|---|---|---|---|
| skipping to change at page 2, line 27 | skipping to change at page 2, line 27 | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 | 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 | |||
| 3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 4. Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | 4. Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 4.1. Initialization Behavior . . . . . . . . . . . . . . . . . 4 | 4.1. Initialization Behavior . . . . . . . . . . . . . . . . . 4 | |||
| 4.2. State Transition Modification . . . . . . . . . . . . . . 5 | 4.2. State Transition Modification . . . . . . . . . . . . . . 5 | |||
| 4.3. Operation related to State Transition Table Lookup . . . 6 | 4.3. Operation related to State Transition Table Lookup . . . 6 | |||
| 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 | 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 | |||
| 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 | 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 | 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 | 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 | 8.1. Normative References . . . . . . . . . . . . . . . . . . 7 | |||
| 8.2. Informative References . . . . . . . . . . . . . . . . . 8 | 8.2. Informative References . . . . . . . . . . . . . . . . . 8 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 1. Introduction | 1. Introduction | |||
| MPLS Transport Profile (MPLS-TP) linear protection in Automatic | MPLS Transport Profile (MPLS-TP) linear protection in Automatic | |||
| Protection Switching (APS) mode is defined in RFC 7271 [RFC7271]. It | Protection Switching (APS) mode is defined in RFC 7271 [RFC7271]. It | |||
| defines a set of alternate and additional mechanisms to perform some | defines a set of alternate and additional mechanisms to perform some | |||
| of the functions of linear protection described in RFC 6378 | of the functions of linear protection described in RFC 6378 | |||
| [RFC6378]. The actions performed at initialization of the Protection | [RFC6378]. The actions performed at initialization of the Protection | |||
| skipping to change at page 7, line 5 | skipping to change at page 6, line 40 | |||
| o When the local SF-P is cleared and the priorities of the local and | o When the local SF-P is cleared and the priorities of the local and | |||
| remote requests are re-evaluated, the last received remote message | remote requests are re-evaluated, the last received remote message | |||
| may not be valid any more due to the previous failure of the | may not be valid any more due to the previous failure of the | |||
| protection path. Therefore, the last received message MUST be | protection path. Therefore, the last received message MUST be | |||
| treated as if it were NR and only the local request shall be | treated as if it were NR and only the local request shall be | |||
| evaluated. | evaluated. | |||
| The last paragraph in Section 11 of [RFC7271] is modified as follows: | The last paragraph in Section 11 of [RFC7271] is modified as follows: | |||
| --------- | Ol | |||
| Old text: | -- | |||
| --------- | In | |||
| In the state transition tables below, the letter 'i' stands for | "i | |||
| "ignore" and is an indication to remain in the current state and | co | |||
| continue transmitting the current PSC message. | Ne | |||
| --------- | In | |||
| New text: | gl | |||
| --------- | ||||
| In the state transition tables below, the letter 'i' is the | ||||
| "ignore" flag, and if it is set it means that the top-priority | ||||
| global request is ignored. | ||||
| If re-evaluation is triggered, it is checked if the ignore flag is | If re-evaluation is triggered, it is checked if the ignore flag is | |||
| set. If it is, the state machine will transit to the supposed state, | set. If it is, the state machine will transit to the supposed state, | |||
| which can be Normal or DNR as indicated in the footnotes to the | which can be Normal or DNR as indicated in the footnotes to the state | |||
| state transition tables. If the ignore flag is not set, the state | transition tables. If the ignore flag is not set, the state machine | |||
| machine will transit to the state indicated in the cell of the state | will transit to the state indicated in the cell of the state | |||
| transition table. | transition table. | |||
| If re-evaluation is not triggered, it is checked if the ignore flag | If re-evaluation is not triggered, it is checked if the ignore flag | |||
| is set. If it is, the state machine will remain in the current state, | is set. If it is, the state machine will remain in the current | |||
| and the current PSC message continues to be transmitted. If the | state, and the current PSC message continues to be transmitted. If | |||
| ignore flag is not set, the state machine will transit to the state | the ignore flag is not set, the state machine will transit to the | |||
| indicated in the cell of the state transition table. | state indicated in the cell of the state transition table. | |||
| 5. Security Considerations | 5. Security Considerations | |||
| No specific security issue is raised in addition to those ones | No specific security issue is raised in addition to those ones | |||
| already documented in [RFC7271]. It may be noted that tightening the | already documented in [RFC7271]. It may be noted that tightening the | |||
| description of initializing behavior may help to protect networks | description of initializing behavior may help to protect networks | |||
| from re-start attacks. | from re-start attacks. | |||
| 6. IANA Considerations | 6. IANA Considerations | |||
| skipping to change at page 8, line 34 | skipping to change at page 8, line 17 | |||
| [RFC6378] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher, | [RFC6378] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher, | |||
| N., and A. Fulignoli, Ed., "MPLS Transport Profile (MPLS- | N., and A. Fulignoli, Ed., "MPLS Transport Profile (MPLS- | |||
| TP) Linear Protection", RFC 6378, DOI 10.17487/RFC6378, | TP) Linear Protection", RFC 6378, DOI 10.17487/RFC6378, | |||
| October 2011, <http://www.rfc-editor.org/info/rfc6378>. | October 2011, <http://www.rfc-editor.org/info/rfc6378>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Jeong-dong Ryoo | Jeong-dong Ryoo | |||
| ETRI | ETRI | |||
| EMail: ryoo@etri.re.kr | Email: ryoo@etri.re.kr | |||
| Taesik Cheung | Taesik Cheung | |||
| ETRI | ETRI | |||
| EMail: cts@etri.re.kr | Email: cts@etri.re.kr | |||
| Huub Van Helvoort | Huub Van Helvoort | |||
| Hai Gaoming BV | Hai Gaoming BV | |||
| EMail: huubatwork@gmail.com | Email: huubatwork@gmail.com | |||
| Italo Busi | Italo Busi | |||
| Huawei Technologies | Huawei Technologies | |||
| EMail: Italo.Busi@huawei.com | Email: Italo.Busi@huawei.com | |||
| Guangjuan Wen | Guangjuan Wen | |||
| Huawei Technologies | Huawei Technologies | |||
| EMail: wenguangjuan@huawei.com | Email: wenguangjuan@huawei.com | |||
| End of changes. 9 change blocks. | ||||
| 26 lines changed or deleted | 23 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/ | ||||