draft-ietf-idr-bgp-prefix-sid-03.txt   draft-ietf-idr-bgp-prefix-sid-04.txt 
IDR S. Previdi, Ed. IDR S. Previdi, Ed.
Internet-Draft C. Filsfils Internet-Draft C. Filsfils
Intended status: Standards Track A. Lindem Intended status: Standards Track A. Lindem
Expires: December 18, 2016 K. Patel Expires: June 15, 2017 K. Patel
A. Sreekantiah A. Sreekantiah
Cisco Systems Cisco Systems
S. Ray S. Ray
Unaffiliated Unaffiliated
H. Gredler H. Gredler
Individual RtBrick Inc.
June 16, 2016 December 12, 2016
Segment Routing Prefix SID extensions for BGP Segment Routing Prefix SID extensions for BGP
draft-ietf-idr-bgp-prefix-sid-03 draft-ietf-idr-bgp-prefix-sid-04
Abstract Abstract
Segment Routing (SR) architecture allows a node to steer a packet 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 a SR header to a packet source routing. The ingress node prepends a SR header to a packet
containing a set of "segments". Each segment represents a containing a set of "segments". Each segment represents a
topological or a service-based instruction. Per-flow state is topological or a service-based instruction. Per-flow state is
maintained only at the ingress node of the SR domain. maintained only at 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 December 18, 2016. This Internet-Draft will expire on June 15, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 4, line 52 skipping to change at page 4, line 52
[I-D.ietf-idr-bgpls-segment-routing-epe]. [I-D.ietf-idr-bgpls-segment-routing-epe].
If the BGP speakers are not all configured with the same SRGB, and If the BGP speakers are not all configured with the same SRGB, and
if traffic-engineering within the SR domain is required, each node if traffic-engineering within the SR domain is required, each node
may be required to advertise its local SRGB in addition to the may be required to advertise its local SRGB in addition to the
topological information. topological information.
This documents assumes that BGP-LS is the preferred method for This documents assumes that BGP-LS is the preferred method for
collecting both topological, peer segments and SRGB information collecting both topological, peer segments and SRGB information
through [RFC7752], [I-D.ietf-idr-bgpls-segment-routing-epe] and 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 optional alternative for the advertisement of the local SRGB
without the topology nor the peer SID's, hence without without the topology nor the peer SID's, hence without
applicability for TE, the Originator SRGB TLV of the prefix-SID applicability for TE, the Originator SRGB TLV of the prefix-SID
attribute, is specified in Section 4.3 of this document. 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 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 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 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 incoming/local label for the prefix. See Section 5.1 for more
details. details.
skipping to change at page 13, line 48 skipping to change at page 14, line 5
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <http://www.rfc-editor.org/info/rfc4364>. 2006, <http://www.rfc-editor.org/info/rfc4364>.
[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,
<http://www.rfc-editor.org/info/rfc7606>. <http://www.rfc-editor.org/info/rfc7606>.
12.2. Informative References 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] [I-D.ietf-6man-segment-routing-header]
Previdi, S., Filsfils, C., Field, B., Leung, I., Linkova, Previdi, S., Filsfils, C., Field, B., Leung, I., Linkova,
J., Aries, E., Kosugi, T., Vyncke, E., and D. Lebrun, J., Aries, E., Kosugi, T., Vyncke, E., and D. Lebrun,
"IPv6 Segment Routing Header (SRH)", draft-ietf-6man- "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] [I-D.ietf-idr-bgpls-segment-routing-epe]
Previdi, S., Filsfils, C., Ray, S., Patel, K., Dong, J., Previdi, S., Filsfils, C., Ray, S., Patel, K., Dong, J.,
and M. Chen, "Segment Routing BGP Egress Peer Engineering and M. Chen, "Segment Routing BGP Egress Peer Engineering
BGP-LS Extensions", draft-ietf-idr-bgpls-segment-routing- 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] [I-D.ietf-ospf-segment-routing-extensions]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H., Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., and J. Tantsura, "OSPF Shakir, R., Henderickx, W., and J. Tantsura, "OSPF
Extensions for Segment Routing", draft-ietf-ospf-segment- 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] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
and R. Shakir, "Segment Routing Architecture", draft-ietf- 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] [I-D.ietf-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Aries, E., Ginsburg, D., and D. Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev,
Afanasiev, "Segment Routing Centralized BGP Peer "Segment Routing Centralized BGP Peer Engineering", draft-
Engineering", draft-ietf-spring-segment-routing-central- ietf-spring-segment-routing-central-epe-03 (work in
epe-01 (work in progress), March 2016. progress), November 2016.
[I-D.ietf-spring-segment-routing-msdc] [I-D.ietf-spring-segment-routing-msdc]
Filsfils, C., Previdi, S., Mitchell, J., Aries, E., and P. Filsfils, C., Previdi, S., Mitchell, J., Aries, E., and P.
Lapukhov, "BGP-Prefix Segment in large-scale data Lapukhov, "BGP-Prefix Segment in large-scale data
centers", draft-ietf-spring-segment-routing-msdc-01 (work centers", draft-ietf-spring-segment-routing-msdc-02 (work
in progress), April 2016. in progress), October 2016.
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760,
DOI 10.17487/RFC4760, January 2007, DOI 10.17487/RFC4760, January 2007,
<http://www.rfc-editor.org/info/rfc4760>. <http://www.rfc-editor.org/info/rfc4760>.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
skipping to change at page 15, line 37 skipping to change at page 16, line 4
Email: acee@cisco.com Email: acee@cisco.com
Keyur Patel Keyur Patel
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95124 95134 San Jose, CA 95124 95134
USA USA
Email: keyupate@cisco.com Email: keyupate@cisco.com
Arjun Sreekantiah Arjun Sreekantiah
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95124 95134 San Jose, CA 95124 95134
USA USA
Email: asreekan@cisco.com Email: asreekan@cisco.com
Saikat Ray Saikat Ray
Unaffiliated Unaffiliated
Email: raysaikat@gmail.com Email: raysaikat@gmail.com
Hannes Gredler Hannes Gredler
Individual RtBrick Inc.
AT
Email: hannes@gredler.at Email: hannes@rtbrick.com
 End of changes. 16 change blocks. 
25 lines changed or deleted 26 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/