| draft-ietf-idr-bgp-prefix-sid-23.txt | draft-ietf-idr-bgp-prefix-sid-24.txt | |||
|---|---|---|---|---|
| skipping to change at page 1, line 14 ¶ | skipping to change at page 1, line 14 ¶ | |||
| Internet-Draft C. Filsfils | Internet-Draft C. Filsfils | |||
| Intended status: Standards Track A. Lindem, Ed. | Intended status: Standards Track A. Lindem, Ed. | |||
| Expires: December 16, 2018 Cisco Systems | Expires: December 16, 2018 Cisco Systems | |||
| A. Sreekantiah | A. Sreekantiah | |||
| H. Gredler | H. Gredler | |||
| RtBrick Inc. | RtBrick Inc. | |||
| June 14, 2018 | June 14, 2018 | |||
| Segment Routing Prefix SID extensions for BGP | Segment Routing Prefix SID extensions for BGP | |||
| draft-ietf-idr-bgp-prefix-sid-23 | draft-ietf-idr-bgp-prefix-sid-24 | |||
| Abstract | Abstract | |||
| The Segment Routing (SR) architecture allows a node to steer a packet | The Segment Routing (SR) architecture allows a node to steer a packet | |||
| flow through any topological path and service chain by leveraging | flow through any topological path and service chain by leveraging | |||
| source routing. The ingress node prepends an SR header to a packet | source routing. The ingress node prepends an SR header to a packet | |||
| containing a set of segment identifiers (SID). Each SID represents a | containing a set of segment identifiers (SID). Each SID represents a | |||
| topological or a service-based instruction. Per-flow state is | topological or a service-based instruction. Per-flow state is | |||
| maintained only on the ingress node of the SR domain. An SR domain | maintained only on the ingress node of the SR domain. An SR domain | |||
| is defined as a single administrative domain for global SID | is defined as a single administrative domain for global SID | |||
| skipping to change at page 11, line 38 ¶ | skipping to change at page 11, line 38 ¶ | |||
| 40 BGP Prefix-SID (TEMPORARY - registered 2015-09-30, expires | 40 BGP Prefix-SID (TEMPORARY - registered 2015-09-30, expires | |||
| 2016-09-30) [draft-ietf-idr-bgp-prefix-sid] | 2016-09-30) [draft-ietf-idr-bgp-prefix-sid] | |||
| This document defines 3 TLVs for the BGP Prefix-SID attribute. These | This document defines 3 TLVs for the BGP Prefix-SID attribute. These | |||
| TLVs need to be registered with IANA. We request IANA to create a | TLVs need to be registered with IANA. We request IANA to create a | |||
| registry for BGP Prefix-SID Attribute TLVs as follows: | registry for BGP Prefix-SID Attribute TLVs as follows: | |||
| Under "Border Gateway Protocol (BGP) Parameters" registry, "BGP | Under "Border Gateway Protocol (BGP) Parameters" registry, "BGP | |||
| Prefix-SID TLV Types" Reference: draft-ietf-idr-bgp-prefix-sid | Prefix-SID TLV Types" Reference: draft-ietf-idr-bgp-prefix-sid | |||
| Registration Procedure(s): Values 1-254 First Come First Served | Registration Procedure(s): Values 1-254 - Expert Review as defined in | |||
| (FCFS), Value 0 and 255 reserved | [RFC8126], Value 0 and 255 reserved | |||
| Value Type Reference | Value Type Reference | |||
| 0 Reserved this document | 0 Reserved this document | |||
| 1 Label-Index this document | 1 Label-Index this document | |||
| 2 Deprecated this document | 2 Deprecated this document | |||
| 3 Originator SRGB this document | 3 Originator SRGB this document | |||
| 4-254 Unassigned | 4-254 Unassigned | |||
| 255 Reserved this document | 255 Reserved this document | |||
| This document also requests creation of the "BGP Prefix-SID Label- | This document also requests creation of the "BGP Prefix-SID Label- | |||
| Index TLV Flags" registry under the "Border Gateway Protocol (BGP) | Index TLV Flags" registry under the "Border Gateway Protocol (BGP) | |||
| Parameters" registry, Reference: draft-ietf-idr-bgp-prefix-sid. | Parameters" registry, Reference: draft-ietf-idr-bgp-prefix-sid. | |||
| Initially, this 16-bit flags registry will be empty. Flag bits will | Initially, this 16-bit flags registry will be empty. The | |||
| be allocated First Come First Served (FCFS) consistent with the BGP | registration policy for flag bits will Expert Review [RFC8126] | |||
| Prefix-SID TLV Types registry. | consistent with the BGP Prefix-SID TLV Types registry. | |||
| Finally, this document requests creation of the "BGP Prefix-SID | Finally, this document requests creation of the "BGP Prefix-SID | |||
| Originator SRGB TLV Flags" registry under the "Border Gateway | Originator SRGB TLV Flags" registry under the "Border Gateway | |||
| Protocol (BGP) Parameters" registry, Reference: draft-ietf-idr-bgp- | Protocol (BGP) Parameters" registry, Reference: draft-ietf-idr-bgp- | |||
| prefix-sid. Initially, this 16-bit flags registry will be empty. | prefix-sid. Initially, this 16-bit flags registry will be empty. | |||
| Flag bits will be allocated First Come First Served (FCFS) consistent | The registration policy for flag bits will Expert Review [RFC8126] | |||
| with the BGP Prefix-SID TLV Types registry. | consistent with the BGP Prefix-SID TLV Types registry. | |||
| 8. Manageability Considerations | 8. Manageability Considerations | |||
| This document defines a BGP attribute to address use cases such as | This document defines a BGP attribute to address use cases such as | |||
| the one described in [I-D.ietf-spring-segment-routing-msdc]. It is | the one described in [I-D.ietf-spring-segment-routing-msdc]. It is | |||
| assumed that advertisement of the BGP Prefix-SID attribute is | assumed that advertisement of the BGP Prefix-SID attribute is | |||
| controlled by the operator in order to: | controlled by the operator in order to: | |||
| o Prevent undesired origination/advertisement of the BGP Prefix-SID | o Prevent undesired origination/advertisement of the BGP Prefix-SID | |||
| attribute. By default, a BGP Prefix-SID attribute SHOULD NOT be | attribute. By default, a BGP Prefix-SID attribute SHOULD NOT be | |||
| skipping to change at page 15, line 10 ¶ | skipping to change at page 15, line 10 ¶ | |||
| [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. | [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. | |||
| Patel, "Revised Error Handling for BGP UPDATE Messages", | Patel, "Revised Error Handling for BGP UPDATE Messages", | |||
| RFC 7606, DOI 10.17487/RFC7606, August 2015, | RFC 7606, DOI 10.17487/RFC7606, August 2015, | |||
| <https://www.rfc-editor.org/info/rfc7606>. | <https://www.rfc-editor.org/info/rfc7606>. | |||
| [RFC7911] Walton, D., Retana, A., Chen, E., and J. Scudder, | [RFC7911] Walton, D., Retana, A., Chen, E., and J. Scudder, | |||
| "Advertisement of Multiple Paths in BGP", RFC 7911, | "Advertisement of Multiple Paths in BGP", RFC 7911, | |||
| DOI 10.17487/RFC7911, July 2016, <https://www.rfc- | DOI 10.17487/RFC7911, July 2016, <https://www.rfc- | |||
| editor.org/info/rfc7911>. | editor.org/info/rfc7911>. | |||
| [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | ||||
| Writing an IANA Considerations Section in RFCs", BCP 26, | ||||
| RFC 8126, DOI 10.17487/RFC8126, June 2017, | ||||
| <https://www.rfc-editor.org/info/rfc8126>. | ||||
| [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>. | |||
| [RFC8205] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol | [RFC8205] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol | |||
| Specification", RFC 8205, DOI 10.17487/RFC8205, September | Specification", RFC 8205, DOI 10.17487/RFC8205, September | |||
| 2017, <https://www.rfc-editor.org/info/rfc8205>. | 2017, <https://www.rfc-editor.org/info/rfc8205>. | |||
| [RFC8277] Rosen, E., "Using BGP to Bind MPLS Labels to Address | [RFC8277] Rosen, E., "Using BGP to Bind MPLS Labels to Address | |||
| Prefixes", RFC 8277, DOI 10.17487/RFC8277, October 2017, | Prefixes", RFC 8277, DOI 10.17487/RFC8277, October 2017, | |||
| End of changes. 5 change blocks. | ||||
| 8 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||