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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 29 November 2017 17:46 UTC

Return-Path: <ginsberg@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 868D712869B for <isis-wg@ietfa.amsl.com>; Wed, 29 Nov 2017 09:46:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 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, 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 roVfxACbzkAZ for <isis-wg@ietfa.amsl.com>; Wed, 29 Nov 2017 09:46:08 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 772D7120726 for <isis-wg@ietf.org>; Wed, 29 Nov 2017 09:46:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8494; q=dns/txt; s=iport; t=1511977568; x=1513187168; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=aUxOlfyF4UyB9ku0VFg6uBawva4E1SVenHJbIHfEjd4=; b=JViV796RmOqFLMka7uF0cwH4ifaGCxuFiKaidK8Fpd0DMgVVD7U5TBhR 8IvdS3yJwohYx1Ku1KeyBGj4SMudbEV4zSKiM1gOVknZ9ZjK2JwUTRUIZ D6sWoawSKG0MWu6Kn84PK1ikwK/6tULyzbpG3Y6HsvGgVa8ovCK5PbSGl k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CpAAB48R5a/4MNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM8Zm4nB4N4iiCOcIF9iGqOCoIRChgLhRgCGoR6PxgBAQEBAQE?= =?us-ascii?q?BAQFrKIUfAQEBAQMBASEROgsMBAIBCBEDAQEBAwIjAwICAh8GCxQBCAgCBA4FC?= =?us-ascii?q?IoCAxUQpzGCJ4c0DYMmAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYEPgjKCCYFWgWg?= =?us-ascii?q?BgyuCa0cYgW0Pgm+CYwWKOpdWPQKHcoghhHCCH2OFLIssijmCQDuIYQIRGQGBO?= =?us-ascii?q?QEfOYFRbxUWJIIpCYJJHIFnd4hjgRQBAQE?=
X-IronPort-AV: E=Sophos;i="5.45,338,1508803200"; d="scan'208";a="37486999"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Nov 2017 17:46:07 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id vATHk7LU018838 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Nov 2017 17:46:07 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.1320.4; Wed, 29 Nov 2017 11:46:06 -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.1320.000; Wed, 29 Nov 2017 11:46:06 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>
CC: "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-msd-05.txt
Thread-Index: AQHTaQ2+Gt7i/EjlNUqkKKipBb7CWKMrfg0AgABrYQD//7g9sA==
Date: Wed, 29 Nov 2017 17:46:06 +0000
Message-ID: <1b003f4e5d164ff2be434f8a13cc0065@XCH-ALN-001.cisco.com>
References: <151195857685.8004.12938835526819242274@ietfa.amsl.com> <509fc32e21cb4a4396ce2d0ad2ecd52e@XCH-ALN-001.cisco.com> <6037974E-A9B5-4168-9126-3A0B5257B540@gmail.com>
In-Reply-To: <6037974E-A9B5-4168-9126-3A0B5257B540@gmail.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.101.15]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/bEI9qsBMBWPqIVa9swhktcHLABg>
Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-msd-05.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: Wed, 29 Nov 2017 17:46:10 -0000

Thanx Jeff - Rev 6 looks good.

   Les


> -----Original Message-----
> From: Jeff Tantsura [mailto:jefftant.ietf@gmail.com]
> Sent: Wednesday, November 29, 2017 8:03 AM
> To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>
> Cc: isis-wg@ietf.org
> Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-msd-05.txt
> 
> Thanks Les, agreed, update on the way.
> 
> Cheers,
> Jeff
> 
> -----Original Message-----
> From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
> Date: Wednesday, November 29, 2017 at 07:49
> To: "Jeff Tantsura (jefftant.ietf@gmail.com)" <jefftant.ietf@gmail.com>
> Cc: "isis-wg@ietf.org" <isis-wg@ietf.org>
> Subject: RE: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-msd-05.txt
> 
>     Jeff -
> 
>     The editorial revisions to the IANA section in V5 of the document seem
> very confusing to me.
> 
>     <snip>
>     This document includes a request to IANA to allocate sub-TLV type
>        codes for the new sub TLV proposed in Section 3 of this document from
>        IS-IS Router Capability TLV Registry as defined by [RFC7981].
> 
>        Following values have been allocated by IANA:
> 
> 
>           Value     Description                      Reference
>           -----     ---------------                  -------------
>           23        Node MSD                         This document
>           15        Link MSD                         This document
> 
>                                 Figure 3: MSD Types
> 
>        For the Link MSD, we request IANA to allocate new sub-TLV codes as
>        defined in Section 4 from Sub-TLVs for TLVs 22, 23, 141, 222 and 223
>        registry.
> 
>        Per TLV information where LINK MSD sub-TLV can be part of:
> 
> 
>                          TLV  22 23 25 141 222 223
>                               --------------------
>                               y  y  y  y   y   y
> 
>                Figure 4: TLVs where LINK MSD Sub-TLV can be present
>     <end snip>
> 
>     The revisions make it seem like both code points are associated with the
> Router Capability TLV.
>     Here is a suggested revision:
> 
>     <begin>
>     This document includes a request to IANA to allocate a sub-TLV type
>        code for the Node MSD sub TLV proposed in Section 3 of this document
> from
>        IS-IS Router Capability TLV Registry as defined by [RFC7981].
> 
>        The following value has been allocated by IANA:
> 
> 
>           Value     Description                      Reference
>           -----     ---------------                  -------------
>           23        Node MSD                         This document
> 
> 
>        This document also includes a request to IANA to allocate a sub-TLV type
> code
>       for the Link MSD sub-TLV proposed in Section 4 of this document from the
>       Sub-TLVs for TLVs 22, 23, 141, 222 and 223  registry.
> 
>        The following value has been allocated by IANA:
> 
> 
>           Value     Description                      Reference
>           -----     ---------------                  -------------
>           15        Link MSD                         This document
> 
>        Per TLV information where LINK MSD sub-TLV can be part of:
> 
> 
>                          TLV  22 23 25 141 222 223
>                               --------------------
>                               y  y  y  y   y   y
> 
>                Figure 3: TLVs where LINK MSD Sub-TLV can be present
> 
>     <end>
> 
>        Les
> 
>     > -----Original Message-----
>     > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of internet-
>     > drafts@ietf.org
>     > Sent: Wednesday, November 29, 2017 4:30 AM
>     > To: i-d-announce@ietf.org
>     > Cc: isis-wg@ietf.org
>     > Subject: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-msd-05.txt
>     >
>     >
>     > 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 WG of the IETF.
>     >
>     >         Title           : Signaling  MSD (Maximum SID Depth) using IS-IS
>     >         Authors         : Jeff Tantsura
>     >                           Uma Chunduri
>     >                           Sam Aldrin
>     >                           Les Ginsberg
>     > 	Filename        : draft-ietf-isis-segment-routing-msd-05.txt
>     > 	Pages           : 8
>     > 	Date            : 2017-11-29
>     >
>     > Abstract:
>     >    This document proposes a way to signal Maximum SID Depth (MSD)
>     >    supported by a node at node and/or link granularity by an IS-IS
>     >    Router.  In a Segment Routing (SR) enabled network a centralized
>     >    controller that programs SR tunnels needs to know the MSD supported
>     >    by the head-end at node and/or link granularity to impose the SID
>     >    stack of an appropriate depth.  MSD is relevant to the head-end of a
>     >    SR tunnel or Binding-SID anchor node where Binding-SID expansions
>     >    might result in creation of a new SID stack.
>     >
>     >
>     > The IETF datatracker status page for this draft is:
>     > https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-msd/
>     >
>     > There are also htmlized versions available at:
>     > https://tools.ietf.org/html/draft-ietf-isis-segment-routing-msd-05
>     > https://datatracker.ietf.org/doc/html/draft-ietf-isis-segment-routing-
> msd-
>     > 05
>     >
>     > A diff from the previous version is available at:
>     > https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-routing-msd-
> 05
>     >
>     >
>     > 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/
>     >
>     > _______________________________________________
>     > Isis-wg mailing list
>     > Isis-wg@ietf.org
>     > https://www.ietf.org/mailman/listinfo/isis-wg
> 
>