[spring] Fwd: New Version Notification for draft-filsfils-spring-sr-recursing-info-00.txt

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Mon, 19 October 2015 07:00 UTC

From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: New Version Notification for draft-filsfils-spring-sr-recursing-info-00.txt
Thread-Index: AQHRCjr/HVAKSAPNOECDUmiAfMylMA==
Date: Mon, 19 Oct 2015 07:00:23 +0000
Message-ID: <9C0B3975-2D25-404E-9CA4-2AA66767B23B@cisco.com>
References: <20151019065443.9025.32082.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.160.150]
Content-Type: multipart/alternative; boundary="_000_9C0B39752D25404E9CA42AA66767B23Bciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/spring/45gaC1MtKCszHPGrQQTzUiD_A-E>
Subject: [spring] Fwd: New Version Notification for draft-filsfils-spring-sr-recursing-info-00.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Mon, 19 Oct 2015 07:00:45 -0000

FYI,

this is the proposal for carrying traffic using a common sid among prefixes.
It covers multiple use cases that have been described on the email thread exchanged a couple of weeks ago.

s.



Begin forwarded message:

From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Subject: New Version Notification for draft-filsfils-spring-sr-recursing-info-00.txt
Date: October 19, 2015 at 8:54:43 AM GMT+2
To: Stefano Previdi <sprevidi@cisco.com<mailto:sprevidi@cisco.com>>, Clarence Filsfils <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>, Peter Psenak <ppsenak@cisco.com<mailto:ppsenak@cisco.com>>, Stefano Previdi <sprevidi@cisco.com<mailto:sprevidi@cisco.com>>, Clarence Filsfils <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>, Peter Psenak <ppsenak@cisco.com<mailto:ppsenak@cisco.com>>


A new version of I-D, draft-filsfils-spring-sr-recursing-info-00.txt
has been successfully submitted by Stefano Previdi and posted to the
IETF repository.

Name: draft-filsfils-spring-sr-recursing-info
Revision: 00
Title: Segment Routing Recursive Information
Document date: 2015-10-18
Group: Individual Submission
Pages: 8
URL:            https://www.ietf.org/internet-drafts/draft-filsfils-spring-sr-recursing-info-00.txt
Status:         https://datatracker.ietf.org/doc/draft-filsfils-spring-sr-recursing-info/
Htmlized:       https://tools.ietf.org/html/draft-filsfils-spring-sr-recursing-info-00


Abstract:
  Segment Routing (SR) allows for a flexible definition of end-to-end
  paths within IGP topologies by encoding paths as sequences of
  topological sub-paths, called "segments".  These segments are
  advertised by the link-state routing protocols (IS-IS and OSPF).

  There are use cases where it is desirable to utilize a SID associated
  with a given node in order to transport traffic destined to different
  local services supported by such node.  This document defines the
  mechanism to do so and illustrates it.





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<http://tools.ietf.org>.

The IETF Secretariat

[spring] Fwd: New Version Notification for draft-… Stefano Previdi (sprevidi)