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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 29 November 2017 15:49 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 8038F127843 for <isis-wg@ietfa.amsl.com>; Wed, 29 Nov 2017 07:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NO_DNS_FOR_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, 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 EsefJqbZPtYr for <isis-wg@ietfa.amsl.com>; Wed, 29 Nov 2017 07:49:03 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F183D1275C5 for <isis-wg@ietf.org>; Wed, 29 Nov 2017 07:49:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4839; q=dns/txt; s=iport; t=1511970542; x=1513180142; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=EU6gVd5L5HzATU/Ebx80Ph5z5UZvq6iFw8wS+RCJSIM=; b=hpPXKo/+4Q9N1EKqyAIDobWRzIX0LZKOb+bdhOCTo0cJ9g10NHJTxWge AtcQ/2+x0j9zgrHCwLVJ4IZXZzbuQb8Qs0PbeVCedxjWAofMixUbqgHeJ WDH4wAyoY0BnYVPymRQYAxriAJaRPdRai/yxNTLMYILsr4OhrSY1aIk/o k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CpAADw1R5a/4wNJK1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMOLmZuJweOGI5wgX2WdIIRChgNhRYChRQ/GAEBAQEBAQEBAWs?= =?us-ascii?q?ohR8BAQEBAwEBODQLDAQCAQgRBAEBHwkHJwsUCQgCBA4FCIoaEKk2imcBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEdg0GCCYFWgWgBgyuDMhiBfIVSBYo6mBMCh3KNEYI?= =?us-ascii?q?fY4UsiyyMeYkcAhEZAYE5AR85gVFvFRYkgikJgkkcgWd3iGOBFAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.44,473,1505779200"; d="scan'208";a="329431126"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Nov 2017 15:49:01 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id vATFn0DN026851 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Nov 2017 15:49:00 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 29 Nov 2017 09:48:59 -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 09:48:59 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Jeff Tantsura (jefftant.ietf@gmail.com)" <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/EjlNUqkKKipBb7CWKMrfg0A
Date: Wed, 29 Nov 2017 15:48:59 +0000
Message-ID: <509fc32e21cb4a4396ce2d0ad2ecd52e@XCH-ALN-001.cisco.com>
References: <151195857685.8004.12938835526819242274@ietfa.amsl.com>
In-Reply-To: <151195857685.8004.12938835526819242274@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.101.15]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/H3z1-1pEbxrpTMVfwq9zQ_r1P4o>
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 15:49:04 -0000

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