IETF Logo Mail Archive

Re: [spring] [mpls] working group last call for draft-ietf-spring-segment-routing

Chris Bowers <cbowers@juniper.net> Fri, 07 August 2015 15:10 UTC

Return-Path: <cbowers@juniper.net>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8035A1B2E23 for <spring@ietfa.amsl.com>; Fri, 7 Aug 2015 08:10:01 -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 yS22DhKUy0Pl for <spring@ietfa.amsl.com>; Fri, 7 Aug 2015 08:10:00 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0126.outbound.protection.outlook.com [207.46.100.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C441A8771 for <spring@ietf.org>; Fri, 7 Aug 2015 08:09:59 -0700 (PDT)
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BLUPR05MB290.namprd05.prod.outlook.com (10.141.23.24) with Microsoft SMTP Server (TLS) id 15.1.225.19; Fri, 7 Aug 2015 15:09:58 +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.01.0225.018; Fri, 7 Aug 2015 15:09:58 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [mpls] working group last call for draft-ietf-spring-segment-routing
Thread-Index: AQHQxIAkIDHQjCw+/UuSqnZYvLoEaJ4AuXBg
Date: Fri, 07 Aug 2015 15:09:58 +0000
Message-ID: <BLUPR05MB2922BCC02E2AF3D3E98BF91A9730@BLUPR05MB292.namprd05.prod.outlook.com>
References: <52A3B956-E9BD-4503-9DDD-D40314B93509@juniper.net>
In-Reply-To: <52A3B956-E9BD-4503-9DDD-D40314B93509@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cbowers@juniper.net;
x-originating-ip: [66.129.239.13]
x-microsoft-exchange-diagnostics: 1; BLUPR05MB290; 5:1og44+nU6GSKzIl9WPkEYhPml8aWSY9hj96igoCEiaHbKMfnKGzrtbmvjKbxFDbDhn4hvFgGAW8+ie+cRMASbch92/xnqwUSfk8iQq/Mend1ALsKKX/z/tNEsr8RJYlRFruV1A14mUK4OoHojWTJTQ==; 24:pUeYp95bU9bkYfuQ751DiJJX7+F23uSr1NDX6o8+f5rmuwn6KTcxQfJnRvG7M46CqZ+SvX+fLT/H+agfGVWnd6TFZ3psixisOpfdrvFxlMU=; 20:WTOJPQ5GNZWxku0diOckx0AKHkeTtVw0AWnb9MBdfZrEBQ4Pq7la++ax2zGuzMdnVYUlwT+UQqcIfjVx7n4ohA==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB290;
x-microsoft-antispam-prvs: <BLUPR05MB290094F47FA1F75F5FB5171A9730@BLUPR05MB290.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:BLUPR05MB290; BCL:0; PCL:0; RULEID:; SRVR:BLUPR05MB290;
x-forefront-prvs: 066153096A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(13464003)(40764003)(164054003)(199003)(189002)(107886002)(189998001)(5001960100002)(86362001)(110136002)(19580395003)(450100001)(92566002)(62966003)(5001830100001)(77156002)(5001860100001)(2950100001)(19580405001)(74316001)(2656002)(102836002)(87936001)(40100003)(77096005)(15975445007)(46102003)(2351001)(68736005)(2900100001)(2501003)(81156007)(33656002)(50986999)(64706001)(230783001)(66066001)(5003600100002)(5002640100001)(106356001)(105586002)(122556002)(76576001)(99286002)(106116001)(4001540100001)(10400500002)(97736004)(54356999)(76176999)(101416001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB290; H:BLUPR05MB292.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Aug 2015 15:09:58.5433 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB290
Archived-At: <http://mailarchive.ietf.org/arch/msg/spring/qOPiSA8W3Glu3uth8W-efd_EIXk>
Subject: Re: [spring] [mpls] working group last call for draft-ietf-spring-segment-routing
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: Fri, 07 Aug 2015 15:10:01 -0000

All,

It appears that section 3.6.3 of this draft which covers using the binding-sid to advertise a mirroring context got dropped between draft-ietf-spring-segment-routing-00 and draft-ietf-spring-segment-routing-01, in February.    Presumably this was done because it didn't have any text in it.  The text for the section in the draft-00 version read "TBD".

I would like to request that this section be put back into the draft.  I propose the following text for this section.

3.6.3 Mirroring Context
The Binding SID is used to advertise the context label for egress node protection. As described in draft-bowers-spring-advertising-lsps-with-sr,  a node B  providing egress node protection for a protected node A advertises a segment associated with A's context identifier using the Binding SID with the mirror context flag set .  In the event of a failure, a point of local repair (PLR) diverting traffic from A to B pushes that segment on the traffic.  B then uses that segment to interpret underlying segments or labels in the context of A.

Thanks,
Chris

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of John G. Scudder
Sent: Wednesday, July 22, 2015 8:12 AM
To: spring@ietf.org
Cc: isis@ietf.org; mpls@ietf.org; 6man@ietf.org; ospf@ietf.org
Subject: [mpls] working group last call for draft-ietf-spring-segment-routing

Dear SPRING WG (and cc MPLS, OSPF, IS-IS, 6MAN, please include SPRING in replies per the reply-to):

As we discussed at the SPRING meeting yesterday, working group last call has been requested for draft-ietf-spring-segment-routing. Please reply to the list with your comments, including although not limited to whether or not you support advancing the document to RFC. Non-authors are especially encouraged to comment.

In consideration of the fact that a number of WG calls are going on concurrently, we will end the call on August 31, 2015. 

Authors, please indicate whether you are aware of any relevant IPR and if so, whether it has been disclosed. (Please do this even if you've done it before, thanks for your help.)

Thanks,

--Bruno and John

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

v2.23.0 | Report a Bug | By Email