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

Jeff Tantsura <jefftant.ietf@gmail.com> Wed, 29 November 2017 16:02 UTC

Return-Path: <jefftant.ietf@gmail.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 3DB66126BF3 for <isis-wg@ietfa.amsl.com>; Wed, 29 Nov 2017 08:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 sKMSDH_eRyro for <isis-wg@ietfa.amsl.com>; Wed, 29 Nov 2017 08:02:36 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8A86127867 for <isis-wg@ietf.org>; Wed, 29 Nov 2017 08:02:35 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id f9so7000209wmh.0 for <isis-wg@ietf.org>; Wed, 29 Nov 2017 08:02:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=jRAZaLfgQ41n2spEuq1aj05hLbTK3E/0zlwCaAa290g=; b=XOym9UJJIPA0aftsRrTYy15TIlL/n22xhRDpn4I3C7xiW90dJSitnad29xtZBFsiin t6FjsDTb63iDCTzw8OUfhF9e5d49bWi1l0OZSpBlI/CpjPxrBGwNjxny2CpwlJP5sR+j Os1RlW19k2GwOepYYedpB/unAi55nkTMFMcMFof4gPoe2mYICsk7MUfBlh85Aljt4LHD tjdPfZKuv6bLmNee6HJiz+poaAK1fakfeoozwP+p1pDXRfSOeQUcVXBjj57q7UtFUn8l 36JVqNcEnZX2WR6+Q4Guy9TQ8oxYnolGjpIJHzzHR3m6oaKKDXebM315c+0W5QsnP8ID de4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=jRAZaLfgQ41n2spEuq1aj05hLbTK3E/0zlwCaAa290g=; b=c4TcvPFbeBmKHUfHJuEDPiBio4EkdcGneZ1D+s4hpRYlqtkkionY+Wy5syr9ZDtpnJ TyiW/fJX5zl1irsHm8zod5RLSRlqMEMC4BGHAsq4Oxn+QoOfrmg+3MJ4ByrskO9/4+2o zNdMwKdhpeLdii63wZxJbdfClivqdzUQcOp/o2B7HlrCMa02Ih0MZyZYrSggNClL7S9p tElIlS8fsPJKZZdM2H3xVWC6BjxLdQ4wv0eeSYj1Fz2NaAzpItb81Dw3kdDIOIf89L3g P5He9rYKEkLZtvKu2eSY9EYlyKjITRuFmnWyLxtGjCfxVa9b8wbj03ybftciOKwnbaN4 LtVA==
X-Gm-Message-State: AJaThX48sWIzUputXLRaiIKSMo1AUYoY6wk5EUGj7UjbkRYtYGH9OG/Q 4duizgpF2tiZy36i/eAWtvNLF+eb
X-Google-Smtp-Source: AGs4zMZEQPmcEaYvfjwTIUoUjlb4DZFI279BQEmcASsxlxa/C5nXPJrRgfYogaEqSnP1tfIja6kT6w==
X-Received: by 10.80.137.147 with SMTP id g19mr8351168edg.293.1511971354438; Wed, 29 Nov 2017 08:02:34 -0800 (PST)
Received: from [10.103.249.65] ([195.219.17.131]) by smtp.gmail.com with ESMTPSA id r1sm1778756edb.71.2017.11.29.08.02.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Nov 2017 08:02:33 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.28.0.171108
Date: Wed, 29 Nov 2017 08:02:38 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
CC: "isis-wg@ietf.org" <isis-wg@ietf.org>
Message-ID: <6037974E-A9B5-4168-9126-3A0B5257B540@gmail.com>
Thread-Topic: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-msd-05.txt
References: <151195857685.8004.12938835526819242274@ietfa.amsl.com> <509fc32e21cb4a4396ce2d0ad2ecd52e@XCH-ALN-001.cisco.com>
In-Reply-To: <509fc32e21cb4a4396ce2d0ad2ecd52e@XCH-ALN-001.cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/96i0-48FE_p-5yX4AnLdowKA3ys>
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 16:02:39 -0000

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