| draft-ietf-idr-bgp-sr-segtypes-ext-05.txt | draft-ietf-idr-bgp-sr-segtypes-ext-06.txt | |||
|---|---|---|---|---|
| Network Working Group K. Talaulikar, Ed. | Network Working Group K. Talaulikar, Ed. | |||
| Internet-Draft C. Filsfils | Internet-Draft C. Filsfils | |||
| Intended status: Experimental Cisco Systems | Intended status: Experimental Cisco Systems | |||
| Expires: 31 March 2025 S. Previdi | Expires: 3 May 2025 S. Previdi | |||
| Huawei Technologies | Huawei Technologies | |||
| P. Mattes | P. Mattes | |||
| Microsoft | Microsoft | |||
| D. Jain | D. Jain | |||
| 27 September 2024 | 30 October 2024 | |||
| Segment Routing Segment Types Extensions for BGP SR Policy | Segment Routing Segment Types Extensions for BGP SR Policy | |||
| draft-ietf-idr-bgp-sr-segtypes-ext-05 | draft-ietf-idr-bgp-sr-segtypes-ext-06 | |||
| Abstract | Abstract | |||
| This document specifies the signaling of additional Segment Routing | This document specifies the signaling of additional Segment Routing | |||
| Segment Types for BGP SR Policy SAFI. | Segment Types for signaling of Segment Routing (SR) Policies in BGP | |||
| using SR Policy Subsequent Address Family Identifier. | ||||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on 31 March 2025. | This Internet-Draft will expire on 3 May 2025. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2024 IETF Trust and the persons identified as the | Copyright (c) 2024 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| skipping to change at page 2, line 28 ¶ | skipping to change at page 2, line 22 ¶ | |||
| 2. Segment Type Sub-TLVs . . . . . . . . . . . . . . . . . . . . 3 | 2. Segment Type Sub-TLVs . . . . . . . . . . . . . . . . . . . . 3 | |||
| 2.1. Segment Type C . . . . . . . . . . . . . . . . . . . . . 4 | 2.1. Segment Type C . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 2.2. Segment Type D . . . . . . . . . . . . . . . . . . . . . 5 | 2.2. Segment Type D . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 2.3. Segment Type E . . . . . . . . . . . . . . . . . . . . . 5 | 2.3. Segment Type E . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 2.4. Segment Type F . . . . . . . . . . . . . . . . . . . . . 6 | 2.4. Segment Type F . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 2.5. Segment Type G . . . . . . . . . . . . . . . . . . . . . 7 | 2.5. Segment Type G . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 2.6. Segment Type H . . . . . . . . . . . . . . . . . . . . . 9 | 2.6. Segment Type H . . . . . . . . . . . . . . . . . . . . . 9 | |||
| 2.7. Segment Type I . . . . . . . . . . . . . . . . . . . . . 9 | 2.7. Segment Type I . . . . . . . . . . . . . . . . . . . . . 9 | |||
| 2.8. Segment Type J . . . . . . . . . . . . . . . . . . . . . 11 | 2.8. Segment Type J . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 2.9. Segment Type K . . . . . . . . . . . . . . . . . . . . . 12 | 2.9. Segment Type K . . . . . . . . . . . . . . . . . . . . . 12 | |||
| 2.10. Segment Flags . . . . . . . . . . . . . . . . . . . . . . 13 | 2.10. SR Policy Segment Flags . . . . . . . . . . . . . . . . . 14 | |||
| 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 | 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 | |||
| 3.1. SR Policy Segment List Sub-TLVs . . . . . . . . . . . . . 14 | 3.1. SR Policy Segment List Sub-TLVs . . . . . . . . . . . . . 15 | |||
| 3.2. SR Policy Segment Flags . . . . . . . . . . . . . . . . . 15 | 3.2. SR Policy Segment Flags . . . . . . . . . . . . . . . . . 15 | |||
| 4. Security Considerations . . . . . . . . . . . . . . . . . . . 15 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . 15 | |||
| 5. Manageability Considerations . . . . . . . . . . . . . . . . 15 | 5. Manageability Considerations . . . . . . . . . . . . . . . . 16 | |||
| 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 | 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 | |||
| 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 | 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 | |||
| 7.1. Normative References . . . . . . . . . . . . . . . . . . 15 | 7.1. Normative References . . . . . . . . . . . . . . . . . . 16 | |||
| 7.2. Informational References . . . . . . . . . . . . . . . . 17 | 7.2. Informational References . . . . . . . . . . . . . . . . 17 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 | |||
| 1. Introduction | 1. Introduction | |||
| BGP SR Policy SAFI was introduced by [I-D.ietf-idr-sr-policy-safi] | BGP Segment Routing (SR) Policy Subsequent Address Family Identifier | |||
| for the advertisement of Segment Routing (SR) Policy [RFC8402]. | (SAFI) was introduced by [I-D.ietf-idr-sr-policy-safi] for the | |||
| [I-D.ietf-idr-sr-policy-safi] introduced the base SR Segment Types A | advertisement of SR Policy [RFC8402]. [I-D.ietf-idr-sr-policy-safi] | |||
| and B as specified by the SR Policy Architecture [RFC9256]. | introduced the base SR Segment Types A and B as specified by the SR | |||
| Policy Architecture [RFC9256]. | ||||
| This document specifies the extensions for the advertisement of the | This document specifies the extensions for the advertisement of the | |||
| remaining SR Segment Types defined in [RFC9256] in the SR Policy SAFI | remaining SR Segment Types defined in [RFC9256] in the SR Policy SAFI | |||
| for both SR-MPLS [RFC8660] and SRv6 [RFC8754] [RFC8986]. | for both SR-MPLS [RFC8660] and SRv6 [RFC8754] [RFC8986]. | |||
| The extensions in this document do not impact the SR Policy | The extensions in this document do not impact the SR Policy | |||
| operations or fault management as specified in | operations or fault management as specified in | |||
| [I-D.ietf-idr-sr-policy-safi]. | [I-D.ietf-idr-sr-policy-safi]. | |||
| 1.1. Requirements Language | 1.1. Requirements Language | |||
| skipping to change at page 4, line 35 ¶ | skipping to change at page 4, line 35 ¶ | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Figure 2: Type C Segment sub-TLV | Figure 2: Type C Segment sub-TLV | |||
| where: | where: | |||
| * Type: 3. | * Type: 3. | |||
| * Length: Specifies the length of the value field (i.e., not | * Length: Specifies the length of the value field (i.e., not | |||
| including Type and Length fields) in terms of octets. The value | including Type and Length fields) in terms of octets. The value | |||
| MUST be 10 when the SR-MPLS SID is present else it MUST be 6. | MUST be 10 when the SR-MPLS SID is present, else it MUST be 6. | |||
| * Flags: 1 octet of flags as defined in Section 2.10. | * Flags: 1 octet of flags as defined in Section 2.10. | |||
| * SR Algorithm: 1 octet specifying SR Algorithm as described in | * SR Algorithm: 1 octet specifying SR Algorithm as described in | |||
| section 3.1.1 in [RFC8402] when A-Flag as defined in Section 2.10 | section 3.1.1 in [RFC8402] when A-Flag as defined in Section 2.10 | |||
| is present. SR Algorithm is used by SRPM | is present. SR Algorithm is used by SRPM | |||
| [I-D.ietf-idr-sr-policy-safi] as described in section 4 in | [I-D.ietf-idr-sr-policy-safi] as described in section 4 in | |||
| [RFC9256]. When A-Flag is not encoded, this field MUST be set to | [RFC9256]. When A-Flag is not encoded, this field MUST be set to | |||
| zero on transmission and MUST be ignored on receipt. | zero on transmission and MUST be ignored on receipt. | |||
| skipping to change at page 5, line 28 ¶ | skipping to change at page 5, line 28 ¶ | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Figure 3: Type D Segment sub-TLV | Figure 3: Type D Segment sub-TLV | |||
| where: | where: | |||
| * Type: 4 | * Type: 4 | |||
| * Length: Specifies the length of the value field (i.e., not | * Length: Specifies the length of the value field (i.e., not | |||
| including Type and Length fields) in terms of octets. The value | including Type and Length fields) in terms of octets. The value | |||
| MUST be 22 when the SR-MPLS SID is present else it MUST be 18. | MUST be 22 when the SR-MPLS SID is present, else it MUST be 18. | |||
| * Flags: 1 octet of flags as defined in Section 2.10. | * Flags: 1 octet of flags as defined in Section 2.10. | |||
| * SR Algorithm: 1 octet specifying SR Algorithm as described in | * SR Algorithm: 1 octet specifying SR Algorithm as described in | |||
| section 3.1.1 in [RFC8402] when A-Flag as defined in Section 2.10 | section 3.1.1 in [RFC8402] when A-Flag as defined in Section 2.10 | |||
| is present. SR Algorithm is used by SRPM | is present. SR Algorithm is used by SRPM | |||
| [I-D.ietf-idr-sr-policy-safi] as described in section 4 in | [I-D.ietf-idr-sr-policy-safi] as described in section 4 in | |||
| [RFC9256]. When A-Flag is not encoded, this field MUST be set to | [RFC9256]. When A-Flag is not encoded, this field MUST be set to | |||
| zero on transmission and MUST be ignored on receipt. | zero on transmission and MUST be ignored on receipt. | |||
| skipping to change at page 6, line 25 ¶ | skipping to change at page 6, line 25 ¶ | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Figure 4: Type E Segment sub-TLV | Figure 4: Type E Segment sub-TLV | |||
| where: | where: | |||
| * Type: 5. | * Type: 5. | |||
| * Length: Specifies the length of the value field (i.e., not | * Length: Specifies the length of the value field (i.e., not | |||
| including Type and Length fields) in terms of octets. The value | including Type and Length fields) in terms of octets. The value | |||
| MUST be 14 when the SR-MPLS SID is present else it MUST be 10. | MUST be 14 when the SR-MPLS SID is present, else it MUST be 10. | |||
| * Flags: 1 octet of flags as defined in Section 2.10. | * Flags: 1 octet of flags as defined in Section 2.10. | |||
| * RESERVED: 1 octet of reserved bits. This field MUST be set to | * RESERVED: 1 octet of reserved bits. This field MUST be set to | |||
| zero on transmission and MUST be ignored on receipt. | zero on transmission and MUST be ignored on receipt. | |||
| * Local Interface ID: 4 octets of interface index of local interface | * Local Interface ID: 4 octets of interface index of local interface | |||
| (refer TLV 258 of [RFC9552]). | (refer TLV 258 of [RFC9552]). | |||
| * IPv4 Node Address: a 4-octet IPv4 address representing a node. | * IPv4 Node Address: a 4-octet IPv4 address representing a node. | |||
| skipping to change at page 7, line 25 ¶ | skipping to change at page 7, line 25 ¶ | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Figure 5: Type F Segment sub-TLV | Figure 5: Type F Segment sub-TLV | |||
| where: | where: | |||
| * Type: 6. | * Type: 6. | |||
| * Length: Specifies the length of the value field (i.e., not | * Length: Specifies the length of the value field (i.e., not | |||
| including Type and Length fields) in terms of octets. The value | including Type and Length fields) in terms of octets. The value | |||
| MUST be 14 when the SR-MPLS SID is present else it MUST be 10. | MUST be 14 when the SR-MPLS SID is present, else it MUST be 10. | |||
| * Flags: 1 octet of flags as defined in Section 2.10. | * Flags: 1 octet of flags as defined in Section 2.10. | |||
| * RESERVED: 1 octet of reserved bits. This field MUST be set to | * RESERVED: 1 octet of reserved bits. This field MUST be set to | |||
| zero on transmission and MUST be ignored on receipt. | zero on transmission and MUST be ignored on receipt. | |||
| * Local IPv4 Address: a 4-octet IPv4 address representing the local | * Local IPv4 Address: a 4-octet IPv4 address representing the local | |||
| link address of the node. | link address of the node. | |||
| * Remote IPv4 Address: a 4-octet IPv4 address representing the link | * Remote IPv4 Address: a 4-octet IPv4 address representing the link | |||
| skipping to change at page 8, line 29 ¶ | skipping to change at page 8, line 29 ¶ | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Figure 6: Type G Segment sub-TLV | Figure 6: Type G Segment sub-TLV | |||
| where: | where: | |||
| * Type: 7 | * Type: 7 | |||
| * Length: Specifies the length of the value field (i.e., not | * Length: Specifies the length of the value field (i.e., not | |||
| including Type and Length fields) in terms of octets. The value | including Type and Length fields) in terms of octets. The value | |||
| MUST be 46 when the SR-MPLS SID is present else it MUST be 42. | MUST be 46 when the SR-MPLS SID is present, else it MUST be 42. | |||
| * Flags: 1 octet of flags as defined in Section 2.10. | * Flags: 1 octet of flags as defined in Section 2.10. | |||
| * RESERVED: 1 octet of reserved bits. This field MUST be set to | * RESERVED: 1 octet of reserved bits. This field MUST be set to | |||
| zero on transmission and MUST be ignored on receipt. | zero on transmission and MUST be ignored on receipt. | |||
| * Local Interface ID: 4 octets of interface index of local interface | * Local Interface ID: 4 octets of interface index of local interface | |||
| (refer TLV 258 of [RFC9552]). | (refer TLV 258 of [RFC9552]). | |||
| * IPv6 Local Node Address: a 16-octet IPv6 address representing the | * IPv6 Local Node Address: a 16-octet IPv6 address representing the | |||
| skipping to change at page 9, line 31 ¶ | skipping to change at page 9, line 31 ¶ | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Figure 7: Type H Segment sub-TLV | Figure 7: Type H Segment sub-TLV | |||
| where: | where: | |||
| * Type: 8 | * Type: 8 | |||
| * Length: Specifies the length of the value field (i.e., not | * Length: Specifies the length of the value field (i.e., not | |||
| including Type and Length fields) in terms of octets. The value | including Type and Length fields) in terms of octets. The value | |||
| MUST be 38 when the SR-MPLS SID is present else it MUST be 34. | MUST be 38 when the SR-MPLS SID is present, else it MUST be 34. | |||
| * Flags: 1 octet of flags as defined in Section 2.10. | * Flags: 1 octet of flags as defined in Section 2.10. | |||
| * RESERVED: 1 octet of reserved bits. This field MUST be set to | * RESERVED: 1 octet of reserved bits. This field MUST be set to | |||
| zero on transmission and MUST be ignored on receipt. | zero on transmission and MUST be ignored on receipt. | |||
| * Local IPv6 Address: a 16-octet IPv6 address representing the local | * Local IPv6 Address: a 16-octet IPv6 address representing the local | |||
| link address of the node. | link address of the node. | |||
| * Remote IPv6 Address: a 16-octet IPv6 address representing the link | * Remote IPv6 Address: a 16-octet IPv6 address representing the link | |||
| skipping to change at page 12, line 23 ¶ | skipping to change at page 12, line 23 ¶ | |||
| zero when the local node address and interface identifiers are | zero when the local node address and interface identifiers are | |||
| sufficient to describe the link. | sufficient to describe the link. | |||
| * IPv6 Remote Node Address: a 16-octet IPv6 address. The value MAY | * IPv6 Remote Node Address: a 16-octet IPv6 address. The value MAY | |||
| be set to zero when the local node address and interface | be set to zero when the local node address and interface | |||
| identifiers are sufficient to describe the link. | identifiers are sufficient to describe the link. | |||
| * SRv6 SID: optional, a 16-octet IPv6 address. | * SRv6 SID: optional, a 16-octet IPv6 address. | |||
| * SRv6 Endpoint Behavior and SID Structure: Optional, as defined in | * SRv6 Endpoint Behavior and SID Structure: Optional, as defined in | |||
| section 2.4.4.2.4 of [I-D.ietf-idr-sr-policy-safi]. | section 2.4.4.2.4 of [I-D.ietf-idr-sr-policy-safi]. The SRv6 | |||
| Endpoint Behavior and SID Structure MUST NOT be included when the | ||||
| SRv6 SID has not been included. | ||||
| The TLV 11 defined for the advertisement of Segment Type J in the | The TLV 11 defined for the advertisement of Segment Type J in the | |||
| early draft versions of [I-D.ietf-idr-sr-policy-safi] has been | early draft versions of [I-D.ietf-idr-sr-policy-safi] has been | |||
| deprecated to avoid backward compatibility issues. | deprecated to avoid backward compatibility issues. | |||
| 2.9. Segment Type K | 2.9. Segment Type K | |||
| The Type K Segment Sub-TLV encodes an adjacency local address, an | The Type K Segment Sub-TLV encodes an adjacency local address, an | |||
| adjacency remote address, and an optional SRv6 SID. The format is as | adjacency remote address, and an optional SRv6 SID. The format is as | |||
| follows: | follows: | |||
| skipping to change at page 13, line 31 ¶ | skipping to change at page 13, line 50 ¶ | |||
| * Local IPv6 Address: a 16-octet IPv6 address representing the local | * Local IPv6 Address: a 16-octet IPv6 address representing the local | |||
| link address of the node. | link address of the node. | |||
| * Remote IPv6 Address: a 16-octet IPv6 address representing the link | * Remote IPv6 Address: a 16-octet IPv6 address representing the link | |||
| address of the neighbor node. | address of the neighbor node. | |||
| * SRv6 SID: optional, a 16-octet IPv6 address. | * SRv6 SID: optional, a 16-octet IPv6 address. | |||
| * SRv6 Endpoint Behavior and SID Structure: Optional, as defined in | * SRv6 Endpoint Behavior and SID Structure: Optional, as defined in | |||
| section 2.4.4.2.4 of [I-D.ietf-idr-sr-policy-safi]. | section 2.4.4.2.4 of [I-D.ietf-idr-sr-policy-safi]. The SRv6 | |||
| Endpoint Behavior and SID Structure MUST NOT be included when the | ||||
| SRv6 SID has not been included. | ||||
| The TLV 12 defined for the advertisement of Segment Type K in the | The TLV 12 defined for the advertisement of Segment Type K in the | |||
| early draft versions of [I-D.ietf-idr-sr-policy-safi] has been | early draft versions of [I-D.ietf-idr-sr-policy-safi] has been | |||
| deprecated to avoid backward compatibility issues. | deprecated to avoid backward compatibility issues. | |||
| 2.10. Segment Flags | 2.10. SR Policy Segment Flags | |||
| The Segment Types sub-TLVs described above may contain the following | The Segment Types sub-TLVs described above may contain the following | |||
| flags in the "Segment Flags" field defined in | SR Policy Segment Flags [I-D.ietf-idr-sr-policy-safi] in their | |||
| [I-D.ietf-idr-sr-policy-safi]. This document introduces additional | "Flags" field. Also refer to Section 3.2. This document introduces | |||
| flags as below: | additional flags as below: | |||
| 0 1 2 3 4 5 6 7 | 0 1 2 3 4 5 6 7 | |||
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ | |||
| |V|A|S|B| | | |V|A|S|B| | | |||
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ | |||
| Figure 11: Segment Flags | Figure 11: SR Policy Segment Flags | |||
| where: | where: | |||
| V-Flag: existing flag as defined in [I-D.ietf-idr-sr-policy-safi]. | V-Flag: existing flag as defined in [I-D.ietf-idr-sr-policy-safi]. | |||
| A-Flag: This flag, when set, indicates the presence of SR | A-Flag: This flag, when set, indicates the presence of SR | |||
| Algorithm id in the "SR Algorithm" field applicable to various | Algorithm id in the "SR Algorithm" field applicable to various | |||
| Segment Types. SR Algorithm is used by SRPM | Segment Types. SR Algorithm is used by SRPM | |||
| [I-D.ietf-idr-sr-policy-safi] as described in section 4 of | [I-D.ietf-idr-sr-policy-safi] as described in section 4 of | |||
| [RFC9256]. | [RFC9256]. | |||
| skipping to change at page 15, line 34 ¶ | skipping to change at page 15, line 44 ¶ | |||
| Bit Description Reference | Bit Description Reference | |||
| ------------------------------------------------------------------ | ------------------------------------------------------------------ | |||
| 1 SR Algorithm Flag (A-Flag) This document | 1 SR Algorithm Flag (A-Flag) This document | |||
| 2 SID Specified Flag (S-Flag) This document | 2 SID Specified Flag (S-Flag) This document | |||
| Table 2: SR Policy Segment Flags | Table 2: SR Policy Segment Flags | |||
| 4. Security Considerations | 4. Security Considerations | |||
| This document does not introduce any security considerations over | The security considerations in [I-D.ietf-idr-sr-policy-safi] apply to | |||
| [I-D.ietf-idr-sr-policy-safi]. | the segment types defined in this document. No additional security | |||
| considerations are introduced in this document. | ||||
| 5. Manageability Considerations | 5. Manageability Considerations | |||
| This document does not introduce any operations and manageability | The operations and manageability considerations in | |||
| considerations over [I-D.ietf-idr-sr-policy-safi]. | [I-D.ietf-idr-sr-policy-safi] apply to the segment types defined in | |||
| this document. No additional operations and manageability | ||||
| considerations are introduced in this document. | ||||
| 6. Acknowledgments | 6. Acknowledgments | |||
| The authors of this document would like to Dan Romascanu and Stig | The authors of this document would like to Dan Romascanu, Stig | |||
| Venaas for their comments and review of this document. The authors | Venaas, and Russ Housley for their comments and review of this | |||
| would like to thank Susan Hares for her detailed shepherd review that | document. The authors would like to thank Susan Hares for her | |||
| helped in improving the document. | detailed shepherd review that helped in improving the document. | |||
| 7. References | 7. References | |||
| 7.1. Normative References | 7.1. Normative References | |||
| [I-D.ietf-idr-sr-policy-safi] | [I-D.ietf-idr-sr-policy-safi] | |||
| Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P., and | Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P., and | |||
| D. Jain, "Advertising Segment Routing Policies in BGP", | D. Jain, "Advertising Segment Routing Policies in BGP", | |||
| Work in Progress, Internet-Draft, draft-ietf-idr-sr- | Work in Progress, Internet-Draft, draft-ietf-idr-sr- | |||
| policy-safi-06, 26 July 2024, | policy-safi-09, 3 October 2024, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr- | <https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr- | |||
| policy-safi-06>. | policy-safi-09>. | |||
| [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, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
| End of changes. 24 change blocks. | ||||
| 39 lines changed or deleted | 48 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||