--- 1/draft-ietf-idr-bgp-prefix-sid-03.txt 2016-12-12 05:13:15.819894684 -0800 +++ 2/draft-ietf-idr-bgp-prefix-sid-04.txt 2016-12-12 05:13:15.851895467 -0800 @@ -1,25 +1,25 @@ IDR S. Previdi, Ed. Internet-Draft C. Filsfils Intended status: Standards Track A. Lindem -Expires: December 18, 2016 K. Patel +Expires: June 15, 2017 K. Patel A. Sreekantiah Cisco Systems S. Ray Unaffiliated H. Gredler - Individual - June 16, 2016 + RtBrick Inc. + December 12, 2016 Segment Routing Prefix SID extensions for BGP - draft-ietf-idr-bgp-prefix-sid-03 + draft-ietf-idr-bgp-prefix-sid-04 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 "segments". Each segment represents a topological or a service-based instruction. Per-flow state is maintained only at the ingress node of the SR domain. @@ -42,21 +42,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 December 18, 2016. + This Internet-Draft will expire on June 15, 2017. Copyright Notice Copyright (c) 2016 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 @@ -181,21 +181,21 @@ [I-D.ietf-idr-bgpls-segment-routing-epe]. If the BGP speakers are not all configured with the same SRGB, and if traffic-engineering within the SR domain is required, each node may be required to advertise its local SRGB in addition to the topological information. This documents assumes that BGP-LS is the preferred method for collecting both topological, peer segments and SRGB information through [RFC7752], [I-D.ietf-idr-bgpls-segment-routing-epe] and - [I-D.gredler-idr-bgp-ls-segment-routing-ext]. However, as an + [I-D.ietf-idr-bgp-ls-segment-routing-ext]. However, as an optional alternative for the advertisement of the local SRGB without the topology nor the peer SID's, hence without applicability for TE, the Originator SRGB TLV of the prefix-SID attribute, is specified in Section 4.3 of this document. The index L_I is a 32 bit offset in the SRGB. Each BGP speaker derives its local MPLS label, L, by adding L_I to the start value of its own SRGB, and programs L in its MPLS dataplane as its incoming/local label for the prefix. See Section 5.1 for more details. @@ -597,60 +597,62 @@ Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2006, . [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. Patel, "Revised Error Handling for BGP UPDATE Messages", RFC 7606, DOI 10.17487/RFC7606, August 2015, . 12.2. Informative References - [I-D.gredler-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-gredler-idr-bgp-ls-segment- - routing-ext-02 (work in progress), June 2016. - [I-D.ietf-6man-segment-routing-header] Previdi, S., Filsfils, C., Field, B., Leung, I., Linkova, J., Aries, E., Kosugi, T., Vyncke, E., and D. Lebrun, "IPv6 Segment Routing Header (SRH)", draft-ietf-6man- - segment-routing-header-01 (work in progress), March 2016. + segment-routing-header-02 (work in progress), September + 2016. + + [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-00 (work in progress), November 2016. [I-D.ietf-idr-bgpls-segment-routing-epe] Previdi, S., Filsfils, C., Ray, S., Patel, K., Dong, J., and M. Chen, "Segment Routing BGP Egress Peer Engineering BGP-LS Extensions", draft-ietf-idr-bgpls-segment-routing- - epe-05 (work in progress), May 2016. + epe-06 (work in progress), November 2016. [I-D.ietf-ospf-segment-routing-extensions] Psenak, P., Previdi, S., Filsfils, C., Gredler, H., Shakir, R., Henderickx, W., and J. Tantsura, "OSPF Extensions for Segment Routing", draft-ietf-ospf-segment- - routing-extensions-08 (work in progress), April 2016. + routing-extensions-10 (work in progress), October 2016. [I-D.ietf-spring-segment-routing] Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., and R. Shakir, "Segment Routing Architecture", draft-ietf- - spring-segment-routing-08 (work in progress), May 2016. + spring-segment-routing-10 (work in progress), November + 2016. [I-D.ietf-spring-segment-routing-central-epe] - Filsfils, C., Previdi, S., Aries, E., Ginsburg, D., and D. - Afanasiev, "Segment Routing Centralized BGP Peer - Engineering", draft-ietf-spring-segment-routing-central- - epe-01 (work in progress), March 2016. + Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev, + "Segment Routing Centralized BGP Peer Engineering", draft- + ietf-spring-segment-routing-central-epe-03 (work in + progress), November 2016. [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-01 (work - in progress), April 2016. + centers", draft-ietf-spring-segment-routing-msdc-02 (work + in progress), October 2016. [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, January 2007, . [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, @@ -681,28 +683,27 @@ Email: acee@cisco.com Keyur Patel Cisco Systems 170 W. Tasman Drive San Jose, CA 95124 95134 USA Email: keyupate@cisco.com - Arjun Sreekantiah Cisco Systems 170 W. Tasman Drive San Jose, CA 95124 95134 USA Email: asreekan@cisco.com + Saikat Ray Unaffiliated Email: raysaikat@gmail.com Hannes Gredler - Individual - AT + RtBrick Inc. - Email: hannes@gredler.at + Email: hannes@rtbrick.com