| rfc9705v3.txt | rfc9705.txt | |||
|---|---|---|---|---|
| skipping to change at line 105 ¶ | skipping to change at line 105 ¶ | |||
| 4.4.1. Sending the Conditional PathTear | 4.4.1. Sending the Conditional PathTear | |||
| 4.4.2. Processing the Conditional PathTear | 4.4.2. Processing the Conditional PathTear | |||
| 4.4.3. CONDITIONS Object | 4.4.3. CONDITIONS Object | |||
| 4.5. Remote State Teardown | 4.5. Remote State Teardown | |||
| 4.5.1. PLR Behavior on Local Repair Failure | 4.5.1. PLR Behavior on Local Repair Failure | |||
| 4.5.2. PLR Behavior on Resv RRO Change | 4.5.2. PLR Behavior on Resv RRO Change | |||
| 4.5.3. LSP Preemption During Local Repair | 4.5.3. LSP Preemption During Local Repair | |||
| 4.5.3.1. Preemption on LP-MP After PHOP Link Failure | 4.5.3.1. Preemption on LP-MP After PHOP Link Failure | |||
| 4.5.3.2. Preemption on NP-MP After PHOP Link Failure | 4.5.3.2. Preemption on NP-MP After PHOP Link Failure | |||
| 4.6. Backward Compatibility Procedures | 4.6. Backward Compatibility Procedures | |||
| 4.6.1. Detecting Support for Refresh-Interval Independent | 4.6.1. Detecting Support for Refresh-Interval Independent RSVP | |||
| RSVP-TE FRR | FRR | |||
| 4.6.2. Procedures for Backward Compatibility | 4.6.2. Procedures for Backward Compatibility | |||
| 4.6.2.1. Lack of Support on Downstream Nodes | 4.6.2.1. Lack of Support on Downstream Nodes | |||
| 4.6.2.2. Lack of Support on Upstream Nodes | 4.6.2.2. Lack of Support on Upstream Nodes | |||
| 4.6.2.3. Incremental Deployment | 4.6.2.3. Incremental Deployment | |||
| 4.7. Consequences of Advertising RI-RSVP Without RI-RSVP-FRR | 4.7. Consequences of Advertising RI-RSVP Without RI-RSVP-FRR | |||
| 5. Security Considerations | 5. Security Considerations | |||
| 6. IANA Considerations | 6. IANA Considerations | |||
| 6.1. CONDITIONS Object | 6.1. CONDITIONS Object | |||
| 7. References | 7. References | |||
| 7.1. Normative References | 7.1. Normative References | |||
| skipping to change at line 915 ¶ | skipping to change at line 915 ¶ | |||
| RSB states on receiving a PathTear from C. | RSB states on receiving a PathTear from C. | |||
| 4. B starts backup LSP signaling to D. However, as D does not have | 4. B starts backup LSP signaling to D. However, as D does not have | |||
| the LSP state, it will reject the backup LSP Path message and | the LSP state, it will reject the backup LSP Path message and | |||
| send a PathErr to B. | send a PathErr to B. | |||
| 5. B will delete its reservation and send a ResvTear to A. | 5. B will delete its reservation and send a ResvTear to A. | |||
| 4.6. Backward Compatibility Procedures | 4.6. Backward Compatibility Procedures | |||
| "Refresh-Interval Independent RSVP-TE FRR" and "RI-RSVP-FRR" refer to | "Refresh-Interval Independent RSVP FRR" and "RI-RSVP-FRR" refer to | |||
| the set of procedures defined in this document to eliminate the | the set of procedures defined in this document to eliminate the | |||
| reliance on periodic refreshes. The extensions proposed in RSVP-TE | reliance on periodic refreshes. The extensions proposed in RSVP-TE | |||
| Summary FRR [RFC8796] may apply to implementations that do not | Summary FRR [RFC8796] may apply to implementations that do not | |||
| support RI-RSVP-FRR. On the other hand, RI-RSVP-FRR extensions | support RI-RSVP-FRR. On the other hand, RI-RSVP-FRR extensions | |||
| relating to LSP state cleanup, namely Conditional and "Remote" | relating to LSP state cleanup, namely Conditional and "Remote" | |||
| PathTears, require support from one-hop and two-hop neighboring nodes | PathTears, require support from one-hop and two-hop neighboring nodes | |||
| along the LSP. Thus, procedures that fall under the LSP state | along the LSP. Thus, procedures that fall under the LSP state | |||
| cleanup category MUST NOT be turned on if any of the nodes involved | cleanup category MUST NOT be turned on if any of the nodes involved | |||
| in the node protection FRR (i.e., the PLR, the MP, and the | in the node protection FRR (i.e., the PLR, the MP, and the | |||
| intermediate node in the case of NP) do not support RI-RSVP-FRR | intermediate node in the case of NP) do not support RI-RSVP-FRR | |||
| extensions. Note that for LSPs requesting link protection, only the | extensions. Note that for LSPs requesting link protection, only the | |||
| PLR and the LP-MP MUST support the extensions. | PLR and the LP-MP MUST support the extensions. | |||
| 4.6.1. Detecting Support for Refresh-Interval Independent RSVP-TE FRR | 4.6.1. Detecting Support for Refresh-Interval Independent RSVP FRR | |||
| An implementation supporting RI-RSVP-FRR extensions MUST set the RI- | An implementation supporting RI-RSVP-FRR extensions MUST set the RI- | |||
| RSVP Capable flag in the CAPABILITY object carried in Hello messages | RSVP Capable flag in the CAPABILITY object carried in Hello messages | |||
| as specified in RSVP-TE Scaling Techniques [RFC8370]. If an | as specified in RSVP-TE Scaling Techniques [RFC8370]. If an | |||
| implementation does not set the flag even if it supports RI-RSVP-FRR | implementation does not set the flag even if it supports RI-RSVP-FRR | |||
| extensions, then its neighbors will view the node as any node that | extensions, then its neighbors will view the node as any node that | |||
| does not support the extensions. | does not support the extensions. | |||
| * As nodes supporting the RI-RSVP-FRR extensions initiate Node-ID- | * As nodes supporting the RI-RSVP-FRR extensions initiate Node-ID- | |||
| based signaling adjacency with all immediate neighbors, such a | based signaling adjacency with all immediate neighbors, such a | |||
| End of changes. 3 change blocks. | ||||
| 4 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||