draft-ietf-spring-segment-routing-central-epe-09.txt   draft-ietf-spring-segment-routing-central-epe-10.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet-Draft S. Previdi Internet-Draft S. Previdi
Intended status: Informational G. Dawra, Ed. Intended status: Informational G. Dawra, Ed.
Expires: June 24, 2018 Cisco Systems, Inc. Expires: June 24, 2018 Cisco Systems, Inc.
E. Aries E. Aries
Juniper Networks Juniper Networks
D. Afanasiev D. Afanasiev
Yandex Yandex
December 21, 2017 December 21, 2017
Segment Routing Centralized BGP Egress Peer Engineering Segment Routing Centralized BGP Egress Peer Engineering
draft-ietf-spring-segment-routing-central-epe-09 draft-ietf-spring-segment-routing-central-epe-10
Abstract Abstract
Segment Routing (SR) leverages source routing. A node steers a Segment Routing (SR) leverages source routing. A node steers a
packet through a controlled set of instructions, called segments, by packet through a controlled set of instructions, called segments, by
prepending the packet with an SR header. A segment can represent any prepending the packet with an SR header. A segment can represent any
instruction topological or service-based. SR allows to enforce a instruction topological or service-based. SR allows to enforce a
flow through any topological path while maintaining per-flow state flow through any topological path while maintaining per-flow state
only at the ingress node of the SR domain. only at the ingress node of the SR domain.
skipping to change at page 15, line 6 skipping to change at page 15, line 6
o Next-Hop: the selected egress border router: C. o Next-Hop: the selected egress border router: C.
o Label: the selected egress peer: 1042. o Label: the selected egress peer: 1042.
o Route-Target: selecting the appropriate VRF at the ingress router. o Route-Target: selecting the appropriate VRF at the ingress router.
o AS path: reflecting the selected valid AS path. o AS path: reflecting the selected valid AS path.
o Some BGP policy to ensure it will be selected as best by the o Some BGP policy to ensure it will be selected as best by the
ingress router. Note that as discussed in RFC 8277 section 5, the ingress router in the related VRF.
comparison of labeled and unlabeled unicast BGP route is
implementation dependent and hence may require an implementation
specific policy on each ingress router in the related VRF.
The related VRF must be preconfigured. A VRF fallback to the main The related VRF must be preconfigured. A VRF fallback to the main
FIB might be beneficial to avoid replicating all the "normal" FIB might be beneficial to avoid replicating all the "normal"
Internet paths in each VRF. Internet paths in each VRF.
6. IPv6 Dataplane 6. IPv6 Dataplane
The described solution is applicable to IPv6, either with MPLS-based The described solution is applicable to IPv6, either with MPLS-based
or IPv6-Native segments. In both cases, the same three steps of the or IPv6-Native segments. In both cases, the same three steps of the
solution are applicable: solution are applicable:
 End of changes. 2 change blocks. 
5 lines changed or deleted 2 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/