[spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-04.txt

internet-drafts@ietf.org Thu, 16 February 2017 22:34 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: spring@ietf.org
Delivered-To: spring@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABFC1296DD; Thu, 16 Feb 2017 14:34:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148728445743.1027.18128759602323016329.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 14:34:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/-ps-SsNxZ3zbwcbGELijuhSHXDw>
Cc: spring@ietf.org
Subject: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-04.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 22:34:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Source Packet Routing in Networking of the IETF.

        Title           : Segment Routing Centralized BGP Egress Peer Engineering
        Authors         : Clarence Filsfils
                          Stefano Previdi
                          Ebben Aries
                          Dmitry Afanasiev
	Filename        : draft-ietf-spring-segment-routing-central-epe-04.txt
	Pages           : 19
	Date            : 2017-02-16

Abstract:
   Segment Routing (SR) leverages source routing.  A node steers a
   packet through a controlled set of instructions, called segments, by
   prepending the packet with an SR header.  A segment can represent any
   instruction topological or service-based.  SR allows to enforce a
   flow through any topological path and service chain while maintaining
   per-flow state only at the ingress node of the SR domain.

   The Segment Routing architecture can be directly applied to the MPLS
   dataplane with no change on the forwarding plane.  It requires minor
   extension to the existing link-state routing protocols.

   This document illustrates the application of Segment Routing to solve
   the BGP Egress Peer Engineering (BGP-EPE) requirement.  The SR-based
   BGP-EPE solution allows a centralized (SDN) controller to program any
   egress peer policy at ingress border routers or at hosts within the
   domain.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-central-epe/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-spring-segment-routing-central-epe-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-central-epe-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/