[OSPF] FW: New Version Notification for draft-bowers-spring-advertising-lsps-with-sr-00.txt

Chris Bowers <cbowers@juniper.net> Fri, 26 September 2014 14:10 UTC

Return-Path: <cbowers@juniper.net>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 386731A8897; Fri, 26 Sep 2014 07:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzRxc25ng86w; Fri, 26 Sep 2014 07:10:47 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0105.outbound.protection.outlook.com [65.55.169.105]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC7E91A6FA9; Fri, 26 Sep 2014 07:10:46 -0700 (PDT)
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BLUPR05MB289.namprd05.prod.outlook.com (10.141.23.19) with Microsoft SMTP Server (TLS) id 15.0.1039.15; Fri, 26 Sep 2014 14:10:44 +0000
Received: from BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) by BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) with mapi id 15.00.1039.011; Fri, 26 Sep 2014 14:10:44 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "spring@ietf.org" <spring@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: New Version Notification for draft-bowers-spring-advertising-lsps-with-sr-00.txt
Thread-Index: AQHP2OvQFL5Yiqc+HkqeM+vB/XjqmZwTYirA
Date: Fri, 26 Sep 2014 14:10:44 +0000
Message-ID: <82ba0346d2de44b7ac3533328012fa7d@BLUPR05MB292.namprd05.prod.outlook.com>
References: <20140925180907.27662.88544.idtracker@ietfa.amsl.com>
In-Reply-To: <20140925180907.27662.88544.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [66.129.239.11]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB289;
x-forefront-prvs: 03468CBA43
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(37854004)(199003)(377454003)(377424004)(189002)(13464003)(83322001)(2201001)(19580395003)(19580405001)(92566001)(101416001)(76482002)(105586002)(106116001)(31966008)(85306004)(64706001)(4396001)(15202345003)(86362001)(79102003)(81542003)(81342003)(74662003)(80022003)(120916001)(66066001)(46102003)(20776003)(95666004)(74502003)(10300001)(87936001)(85852003)(108616004)(77982003)(99286002)(107046002)(83072002)(107886001)(15975445006)(99396003)(2656002)(54356999)(230783001)(76176999)(2501002)(21056001)(74316001)(76576001)(50986999)(97736003)(33646002)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB289; H:BLUPR05MB292.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/N_zTrEAcLzshjsa2EHI5jkJBjwI
Subject: [OSPF] FW: New Version Notification for draft-bowers-spring-advertising-lsps-with-sr-00.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2014 14:10:49 -0000

This document describes several use cases for using segment routing to advertise label bindings corresponding to LSPs.

At the ISIS WG meeting in Toronto as well as follow-up discussion on the ISIS and SPRING lists, several people agreed that there is a need for a separate (or additional) document in the SPRING WG covering Binding TLV use cases that can referenced from both ISIS and OSPF protocol extensions documents, in order to allow the protocol extensions documents to focus on bits and bytes.

This document is an attempt to address that need.  Comments are welcome.

Chris

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, September 25, 2014 1:09 PM
To: Uma Chunduri; Hannes Gredler; Chris Bowers; Chris Bowers; Uma Chunduri; Hannes Gredler
Subject: New Version Notification for draft-bowers-spring-advertising-lsps-with-sr-00.txt


A new version of I-D, draft-bowers-spring-advertising-lsps-with-sr-00.txt
has been successfully submitted by Chris Bowers and posted to the IETF repository.

Name:		draft-bowers-spring-advertising-lsps-with-sr
Revision:	00
Title:		Advertising LSPs with Segment Routing
Document date:	2014-09-25
Group:		Individual Submission
Pages:		14
URL:            http://www.ietf.org/internet-drafts/draft-bowers-spring-advertising-lsps-with-sr-00.txt
Status:         https://datatracker.ietf.org/doc/draft-bowers-spring-advertising-lsps-with-sr/
Htmlized:       http://tools.ietf.org/html/draft-bowers-spring-advertising-lsps-with-sr-00


Abstract:
   Segment routing uses globally-known labels to accomplish forwarding
   along shortest paths, and label stacks to accomplish explicit routing
   along arbitrary paths.  These labels are advertised using an IGP.
   This draft describes how label bindings corresponding to RSVP, LDP,
   BGP labeled-unicast, and static LSPs are advertised in segment
   routing and how these labels can be combined with other segment
   routing labels to create forwarding paths.  This draft also describes
   how context labels for egress node protection are advertised in using
   segment routing IGP extensions.

                                                                                  


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.

The IETF Secretariat