| < draft-ietf-idr-bgp-prefix-sid-18.txt | draft-ietf-idr-bgp-prefix-sid-19.txt > | |||
|---|---|---|---|---|
| IDR S. Previdi, Ed. | IDR S. Previdi, Ed. | |||
| Internet-Draft C. Filsfils | Internet-Draft C. Filsfils | |||
| Intended status: Standards Track A. Lindem, Ed. | Intended status: Standards Track A. Lindem, Ed. | |||
| Expires: September 28, 2018 Cisco Systems | Expires: October 9, 2018 Cisco Systems | |||
| A. Sreekantiah | A. Sreekantiah | |||
| H. Gredler | H. Gredler | |||
| RtBrick Inc. | RtBrick Inc. | |||
| March 27, 2018 | April 7, 2018 | |||
| Segment Routing Prefix SID extensions for BGP | Segment Routing Prefix SID extensions for BGP | |||
| draft-ietf-idr-bgp-prefix-sid-18 | draft-ietf-idr-bgp-prefix-sid-19 | |||
| 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. | maintained only on the ingress node of the SR domain. | |||
| skipping to change at page 2, line 7 ¶ | skipping to change at page 2, line 7 ¶ | |||
| 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 http://datatracker.ietf.org/drafts/current/. | Drafts is at http://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 September 28, 2018. | This Internet-Draft will expire on October 9, 2018. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 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 | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 39 ¶ | skipping to change at page 2, line 39 ¶ | |||
| 3. BGP Prefix-SID Attribute . . . . . . . . . . . . . . . . . . 5 | 3. BGP Prefix-SID Attribute . . . . . . . . . . . . . . . . . . 5 | |||
| 3.1. Label-Index TLV . . . . . . . . . . . . . . . . . . . . . 6 | 3.1. Label-Index TLV . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 3.2. Originator SRGB TLV . . . . . . . . . . . . . . . . . . . 6 | 3.2. Originator SRGB TLV . . . . . . . . . . . . . . . . . . . 6 | |||
| 4. Receiving BGP Prefix-SID Attribute . . . . . . . . . . . . . 8 | 4. Receiving BGP Prefix-SID Attribute . . . . . . . . . . . . . 8 | |||
| 4.1. MPLS Dataplane: Labeled Unicast . . . . . . . . . . . . . 8 | 4.1. MPLS Dataplane: Labeled Unicast . . . . . . . . . . . . . 8 | |||
| 5. Advertising BGP Prefix-SID Attribute . . . . . . . . . . . . 10 | 5. Advertising BGP Prefix-SID Attribute . . . . . . . . . . . . 10 | |||
| 5.1. MPLS Dataplane: Labeled Unicast . . . . . . . . . . . . . 10 | 5.1. MPLS Dataplane: Labeled Unicast . . . . . . . . . . . . . 10 | |||
| 6. Error Handling of BGP Prefix-SID Attribute . . . . . . . . . 11 | 6. Error Handling of BGP Prefix-SID Attribute . . . . . . . . . 11 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 8. Manageability Considerations . . . . . . . . . . . . . . . . 12 | 8. Manageability Considerations . . . . . . . . . . . . . . . . 12 | |||
| 9. Security Considerations . . . . . . . . . . . . . . . . . . . 12 | 9. Security Considerations . . . . . . . . . . . . . . . . . . . 13 | |||
| 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 | 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 | |||
| 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 | 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 | |||
| 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 | 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 | |||
| 12.1. Normative References . . . . . . . . . . . . . . . . . . 14 | 12.1. Normative References . . . . . . . . . . . . . . . . . . 14 | |||
| 12.2. Informative References . . . . . . . . . . . . . . . . . 15 | 12.2. Informative References . . . . . . . . . . . . . . . . . 15 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 | |||
| 1. Introduction | 1. Introduction | |||
| The Segment Routing (SR) architecture leverages the source routing | The Segment Routing (SR) architecture leverages the source routing | |||
| skipping to change at page 12, line 12 ¶ | skipping to change at page 12, line 12 ¶ | |||
| Registration Procedure(s): Values 1-254 First Come First Served | Registration Procedure(s): Values 1-254 First Come First Served | |||
| (FCFS), Value 0 and 255 reserved | (FCFS), 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 creates a registry for the 16 bits of flags in the | This document also requests creation of the "BGP Prefix-SID Label- | |||
| Label-Index TLV. Initially, the registry will be empty. Flag bits | Index TLV Flags" registry under the "Border Gateway Protocol (BGP) | |||
| will be allocated First Come First Served (FCFS) consistent with the | Parameters" registry, Reference: draft-ietf-idr-bgp-prefix-sid. | |||
| BGP-SID TLV Types registry. | Initially, this 16 bit flags registry will be empty. Flag bits will | |||
| be allocated First Come First Served (FCFS) consistent with the BGP- | ||||
| SID TLV Types registry. | ||||
| Finally, this document creates a registry for the 16 bits of flags in | Finally, this document requests creation of the "BGP Prefix-SID | |||
| the SRGB Originator TLV. Initially, the registry will be empty. | Originator SRGB TLV Flags" registry under the "Border Gateway | |||
| Protocol (BGP) Parameters" registry, Reference: draft-ietf-idr-bgp- | ||||
| prefix-sid. Initially, this 16 bit flags registry will be empty. | ||||
| Flag bits will be allocated First Come First Served (FCFS) consistent | Flag bits will be allocated First Come First Served (FCFS) consistent | |||
| with the BGP-SID TLV Types registry. | with the BGP-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: | |||
| skipping to change at page 14, line 27 ¶ | skipping to change at page 14, line 33 ¶ | |||
| [I-D.ietf-spring-segment-routing] | [I-D.ietf-spring-segment-routing] | |||
| Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., | Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., | |||
| Litkowski, S., and R. Shakir, "Segment Routing | Litkowski, S., and R. Shakir, "Segment Routing | |||
| Architecture", draft-ietf-spring-segment-routing-15 (work | Architecture", draft-ietf-spring-segment-routing-15 (work | |||
| in progress), January 2018. | in progress), January 2018. | |||
| [I-D.ietf-spring-segment-routing-mpls] | [I-D.ietf-spring-segment-routing-mpls] | |||
| Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., | Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., | |||
| Litkowski, S., and R. Shakir, "Segment Routing with MPLS | Litkowski, S., and R. Shakir, "Segment Routing with MPLS | |||
| data plane", draft-ietf-spring-segment-routing-mpls-12 | data plane", draft-ietf-spring-segment-routing-mpls-13 | |||
| (work in progress), February 2018. | (work in progress), April 2018. | |||
| [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, <https://www.rfc- | DOI 10.17487/RFC2119, March 1997, <https://www.rfc- | |||
| editor.org/info/rfc2119>. | editor.org/info/rfc2119>. | |||
| [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A | [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A | |||
| Border Gateway Protocol 4 (BGP-4)", RFC 4271, | Border Gateway Protocol 4 (BGP-4)", RFC 4271, | |||
| DOI 10.17487/RFC4271, January 2006, <https://www.rfc- | DOI 10.17487/RFC4271, January 2006, <https://www.rfc- | |||
| editor.org/info/rfc4271>. | editor.org/info/rfc4271>. | |||
| End of changes. 8 change blocks. | ||||
| 13 lines changed or deleted | 17 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||