--- 1/draft-ietf-idr-bgp-prefix-sid-05.txt 2017-06-16 11:13:11.670786195 -0700 +++ 2/draft-ietf-idr-bgp-prefix-sid-06.txt 2017-06-16 11:13:11.706787061 -0700 @@ -1,34 +1,35 @@ IDR S. Previdi, Ed. Internet-Draft C. Filsfils Intended status: Standards Track A. Lindem -Expires: October 22, 2017 A. Sreekantiah +Expires: December 18, 2017 A. Sreekantiah Cisco Systems H. Gredler RtBrick Inc. - April 20, 2017 + June 16, 2017 Segment Routing Prefix SID extensions for BGP - draft-ietf-idr-bgp-prefix-sid-05 + draft-ietf-idr-bgp-prefix-sid-06 Abstract Segment Routing (SR) architecture allows a node to steer a packet flow through any topological path and service chain by leveraging source routing. The ingress node prepends a SR header to a packet containing a set of segment identifiers (SID). Each SID represents a topological or a service-based instruction. Per-flow state is maintained only at the ingress node of the SR domain. - This document describes the BGP extension for announcing BGP Prefix - Segment Identifier (BGP Prefix-SID) information. + This document defines a new optional, transitive BGP attribute for + announcing BGP Prefix Segment Identifiers (BGP Prefix-SID) + information. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119] only when they appear in all upper case. They may also appear in lower or mixed case as English words, without any normative meaning. Status of This Memo @@ -38,21 +39,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on October 22, 2017. + This Internet-Draft will expire on December 18, 2017. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -107,22 +108,22 @@ SID consists of a label while when SR is applied to the IPv6 dataplane the SID consists of an IPv6 address. A BGP-Prefix Segment (and its BGP Prefix-SID), is a BGP segment attached to a BGP prefix. A BGP Prefix-SID is always a global SID ([I-D.ietf-spring-segment-routing]) within the SR/BGP domain (i.e., the set of Autonomous Systems under a common administration and control and where SR is used) and identifies an instruction to forward the packet over the ECMP-aware best-path computed by BGP to the related prefix. The BGP Prefix-SID is the identifier of the BGP - prefix segment. In this document we always refer to the BGP segment - as the BGP Prefix-SID. + prefix segment. In this document, we always refer to the BGP Segment + by the BGP Prefix-SID. This document describes the BGP extension to signal the BGP Prefix- SID. Specifically, this document defines a new BGP attribute known as the BGP Prefix-SID attribute and specifies the rules to originate, receive and handle error conditions of the new attribute. As described in [I-D.ietf-spring-segment-routing-msdc], the BGP Prefix-SID attribute defined in this document can be attached to prefixes from AFI/SAFI: @@ -345,23 +346,22 @@ multiple of 6. o Flags: 16 bits of flags. None is defined in this document. Flags MUST be clear on transmission an MUST be ignored at reception. o SRGB: 3 octets of base followed by 3 octets of range. Note that the SRGB field MAY appear multiple times. If the SRGB field appears multiple times, the SRGB consists of multiple ranges. The Originator SRGB TLV contains the SRGB of the node originating the - prefix to which the BGP Prefix-SID is attached and MUST be kept in - the Prefix-SID Attribute unchanged during the propagation of the BGP - update. + prefix to which the BGP Prefix-SID is attached. The Originator SRGB + TLV MUST NOT be changed during the propagation of the BGP update. The originator SRGB describes the SRGB of the node where the BGP Prefix SID is attached. It is used to build segment routing policies when different SRGB's are used in the fabric ([I-D.ietf-spring-segment-routing-msdc]). The originator SRGB may only appear on Prefix-SID attribute attached to prefixes of SAFI 4 (labeled unicast, [RFC3107]). 4. Receiving BGP-Prefix-SID Attribute @@ -642,24 +642,24 @@ 12.2. Informative References [I-D.ietf-idr-bgp-ls-segment-routing-ext] Previdi, S., Psenak, P., Filsfils, C., Gredler, H., Chen, M., and j. jefftant@gmail.com, "BGP Link-State extensions for Segment Routing", draft-ietf-idr-bgp-ls-segment- routing-ext-01 (work in progress), February 2017. [I-D.ietf-idr-bgpls-segment-routing-epe] - Previdi, S., Filsfils, C., Patel, K., Ray, S., Dong, J., - and M. Chen, "Segment Routing BGP Egress Peer Engineering - BGP-LS Extensions", draft-ietf-idr-bgpls-segment-routing- - epe-11 (work in progress), March 2017. + Previdi, S., Filsfils, C., Patel, K., Ray, S., and J. + Dong, "BGP-LS extensions for Segment Routing BGP Egress + Peer Engineering", draft-ietf-idr-bgpls-segment-routing- + epe-12 (work in progress), April 2017. [I-D.ietf-spring-segment-routing-msdc] Filsfils, C., Previdi, S., Mitchell, J., Aries, E., and P. Lapukhov, "BGP-Prefix Segment in large-scale data centers", draft-ietf-spring-segment-routing-msdc-04 (work in progress), March 2017. [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, January 2007, @@ -668,40 +668,38 @@ [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and S. Ray, "North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP", RFC 7752, DOI 10.17487/RFC7752, March 2016, . Authors' Addresses Stefano Previdi (editor) Cisco Systems - Via Del Serafico, 200 - Rome 00142 - Italy + IT - Email: sprevidi@cisco.com + Email: stefano@previdi.net Clarence Filsfils Cisco Systems Brussels Belgium Email: cfilsfils@cisco.com + Acee Lindem Cisco Systems 170 W. Tasman Drive San Jose, CA 95124 95134 USA Email: acee@cisco.com - Arjun Sreekantiah Cisco Systems 170 W. Tasman Drive San Jose, CA 95124 95134 USA Email: asreekan@cisco.com Hannes Gredler RtBrick Inc.