Re: [Lsr] I-D Action: draft-ietf-isis-segment-routing-extensions-21.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 03 December 2018 21:10 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA4012D4E8 for <lsr@ietfa.amsl.com>; Mon, 3 Dec 2018 13:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.961
X-Spam-Level:
X-Spam-Status: No, score=-15.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 aYqyKGlkea7U for <lsr@ietfa.amsl.com>; Mon, 3 Dec 2018 13:10:16 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 801BC1294D7 for <lsr@ietf.org>; Mon, 3 Dec 2018 13:10:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3514; q=dns/txt; s=iport; t=1543871416; x=1545081016; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Z/RFwxKQ7MCyQzY2PkLnZ40Rl+gjMVoQh7pFYKR/Beg=; b=iD9Iwcn9AGrm4BxP1mYevn4XjlDcVwN0hf+9fhuynvFaR7RI9+PIT52K k5LxTVTCUUNXqSsoeddc/sZJKAnhYQtaSpBudGkQcSlt0ehGaPzn8cjBg FnaWjUkoIo37v40LeS58B9c2FYrowl8FXBx7IyHyOyUR9uNCohdcAU3L6 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAAAPmwVc/5FdJa1jGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGCA2aBAicKjAeOGpdIFIFmCwEBGA2ERwKDRyI0CQ0BAwEBAgEBAm0cAQuFPAEBAQEDAQE4NBcEAgEIEQQBAR8QJwsdCAIEEwiDGoIBD6drhDECDkCFKowcF4FAP4EQAYMSgx4BAQIBARaBFAESAUWFNQKgQAkChn6KNCCBW02ERIo6iQSEZYpdAhEUgScfOGRxcBUaIYJsCYIeF4hehT9BMYkjgR+BHwEB
X-IronPort-AV: E=Sophos;i="5.56,311,1539648000"; d="scan'208";a="208348237"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Dec 2018 21:10:15 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id wB3LAFav015831 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <lsr@ietf.org>; Mon, 3 Dec 2018 21:10:15 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 3 Dec 2018 15:10:14 -0600
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1395.000; Mon, 3 Dec 2018 15:10:14 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] I-D Action: draft-ietf-isis-segment-routing-extensions-21.txt
Thread-Index: AQHUi0uWth584XEsvEa+ugxA+j0KjaVtgSzg
Date: Mon, 03 Dec 2018 21:10:14 +0000
Message-ID: <6dfac2e26e11486fa7c083c227106a3f@XCH-ALN-001.cisco.com>
References: <154387096645.5028.17933031132037240009@ietfa.amsl.com>
In-Reply-To: <154387096645.5028.17933031132037240009@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: [10.24.67.88]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/xq7ZluiQU0LWis0nA6-sg-yDCJY>
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-segment-routing-extensions-21.txt
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2018 21:10:20 -0000

(Resending w/o the ID announce list - please post any replies against this email please)

Folks -

Authors of 

https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/
https://datatracker.ietf.org/doc/draft-ietf-ospf-segment-routing-extensions/
https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-segment-routing-extensions/

received private comments that the specification of the use of the V and L bits in prefix/adjacency SID advertisements differed between the three drafts.
Although the differences were not conflicting it might have been confusing to readers of the three specifications and suggest (unintentionally) that the three protocols used these bits in different ways.

To eliminate any confusion we have updated all three of these drafts. They all now explicitly state which combinations of V and L bits are valid, what each combination means, and require that invalid combinations MUST be discarded on receive.

We emphasize that this is not a specification change - but a clarification. We believe all existing implementations are compatible with the revised language.

   Les (on behalf of all the drafts)

> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
> Sent: Monday, December 03, 2018 1:03 PM
> To: i-d-announce@ietf.org
> Cc: lsr@ietf.org
> Subject: [Lsr] I-D Action: draft-ietf-isis-segment-routing-extensions-21.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Link State Routing WG of the IETF.
> 
>         Title           : IS-IS Extensions for Segment Routing
>         Authors         : Stefano Previdi
>                           Les Ginsberg
>                           Clarence Filsfils
>                           Ahmed Bashandy
>                           Hannes Gredler
>                           Bruno Decraene
> 	Filename        : draft-ietf-isis-segment-routing-extensions-21.txt
> 	Pages           : 34
> 	Date            : 2018-12-03
> 
> 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).
> 
>    This draft describes the necessary IS-IS extensions that need to be
>    introduced for Segment Routing operating on an MPLS data-plane.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-21
> https://datatracker.ietf.org/doc/html/draft-ietf-isis-segment-routing-
> extensions-21
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-routing-
> extensions-21
> 
> 
> 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/
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr