Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-13.txt

"Acee Lindem (acee)" <acee@cisco.com> Fri, 30 June 2017 12:05 UTC

Return-Path: <acee@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 291CF129468 for <isis-wg@ietfa.amsl.com>; Fri, 30 Jun 2017 05:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 N7dFsKu0lXvZ for <isis-wg@ietfa.amsl.com>; Fri, 30 Jun 2017 05:05:51 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0D3F127B73 for <isis-wg@ietf.org>; Fri, 30 Jun 2017 05:05:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6630; q=dns/txt; s=iport; t=1498824351; x=1500033951; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=hKDlufUakKAnwwuq+w3uzGVFHL7s16p2GixqPut18hI=; b=Qj3hrECAXzejkIl62xe8gF2zLvG8oa/i5lAVvBqwpFgX1eqp84ZeaBbn cAaUzRmgem/NdveFOCBEupfdwUXDNOHFuhHsTNxkPcJqZBo01vMhi6USu XvQe3TckFE7TU4kFczJoIO8W24YUXenkHGyIbPRSXQIkHFVPNauZEmFWi 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CYAAA6PlZZ/5tdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1ljgQ4HjX6RapV7ghEhDYVuAhqCfD8YAQIBAQEBAQEBayiFGAE?= =?us-ascii?q?BAgIBAQEhETMHFwYBCA4DBAEBAQICIwMCBCULFAEICgQBEgmKHggQs1CCJotAA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEBHYELghyFLAGDJIMmgUQXD4JtgmEFnnoCh0K?= =?us-ascii?q?MOoIMVoR0ikSMF4kVAR84gQp1FR8qhRMcgWZ2AYgcgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.40,286,1496102400"; d="scan'208";a="264361980"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jun 2017 12:05:50 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v5UC5oIG031748 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 30 Jun 2017 12:05:50 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 30 Jun 2017 08:05:49 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Fri, 30 Jun 2017 08:05:49 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Chris Bowers <cbowers@juniper.net>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "isis-wg@ietf.org list" <isis-wg@ietf.org>
Thread-Topic: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-13.txt
Thread-Index: AQHS8Zk2Duefvns0sEilbGdM4ZRVGw==
Date: Fri, 30 Jun 2017 12:05:49 +0000
Message-ID: <D57BB605.B6DDC%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E2506D6C88A15148AE440CDE0FC8FFCC@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/WO3T8aqBuHjN7pPyc62T7YvillU>
Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-13.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 12:05:54 -0000

Hi Chris, 

There was a protracted discussion on what SR sub-TLVs are actually
implemented. Did you and colleagues familiar with the usage you describe
below miss this entirely???

Here is the first E-mail from the IS-IS list archive:
https://mailarchive.ietf.org/arch/msg/isis-wg/KPMgDBoOek0LI-wFFupSFnWrbbo

Thanks,
Acee

On 6/30/17, 7:51 AM, "Isis-wg on behalf of Chris Bowers"
<isis-wg-bounces@ietf.org on behalf of cbowers@juniper.net> wrote:

>Stefano,
> 
>Among the changes between draft-ietf-isis-segment-routing-extensions-12
>and -13 is the removal of the SID/Label sub-TLV from the SID/Label
>Binding TLV.
> 
>I don't agree with this change.  The SID/Label sub-TLV is used in the
>SID/Label Binding TLV when the Mirror Context flag is set in the
>SID/Label Binding TLV.  The use of the Mirroring Context Segment is
>described in section 5 of draft-ietf-spring-segment-routing-12.  There is
>at least one implementation using the encoding described in the versions
>of the draft up to and including
>draft-ietf-isis-segment-routing-extensions-12, where the SID/Label
>sub-TLV carries the label information for the mirror context in the
>SID/Label Binding TLV.  The SID/Label sub-TLV has the appropriate
>characteristics for this application.
> 
>I also noticed a separate issue in that the IANA considerations section
>(both before and after the changes in -13) does not capture the use of
>the SID/Label Sub-TLV in the SR Local Block Sub-TLV.  Presumably when the
>SID/Label Sub-TLV is used in the SR Local Block Sub-TLV, its type is the
>same as when it is used in the SID/Label Binding TLV and the
>Multi-Topology Segment Identifier / Label Binding TLV.  If so, this
>should be reflected in the definition of the new sub-TLV registry.
> 
>Thanks,
>Chris
>
>
>-----Original Message-----
>From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Stefano
>Previdi (sprevidi)
>Sent: Monday, June 19, 2017 10:27 PM
>To: isis-wg@ietf.org list <isis-wg@ietf.org>
>Subject: Re: [Isis-wg] I-D Action:
>draft-ietf-isis-segment-routing-extensions-13.txt
>
>All,
>
>in tis version we removed the ERO subTLVs of the Binding SID TLV and
>fixed some other minor inconsistencies.
>
>Thanks.
>s.
>
>
>> On Jun 19, 2017, at 10:25 PM, internet-drafts@ietf.org wrote:
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>>directories.
>> This draft is a work item of the IS-IS for IP Internets of the IETF.
>> 
>>        Title           : IS-IS Extensions for Segment Routing
>>        Authors         : Stefano Previdi
>>                          Clarence Filsfils
>>                          Ahmed Bashandy
>>                          Hannes Gredler
>>                          Stephane Litkowski
>>                          Bruno Decraene
>>                          Jeff Tantsura
>> 	Filename        : draft-ietf-isis-segment-routing-extensions-13.txt
>> 	Pages           : 33
>> 	Date            : 2017-06-19
>> 
>> 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-exten
>> sions/
>> 
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions
>> -13
>> https://datatracker.ietf.org/doc/html/draft-ietf-isis-segment-routing-
>> extensions-13
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-routing-exte
>> nsions-13
>> 
>> 
>> 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/
>> 
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html or
>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www.ietf.org/mailman/listinfo/isis-wg
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www.ietf.org/mailman/listinfo/isis-wg