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

Peter Psenak <ppsenak@cisco.com> Tue, 15 May 2018 09:33 UTC

Return-Path: <ppsenak@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 A7B2712DA27 for <lsr@ietfa.amsl.com>; Tue, 15 May 2018 02:33:29 -0700 (PDT)
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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=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 BXfkR-Gn6hOE for <lsr@ietfa.amsl.com>; Tue, 15 May 2018 02:33:27 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0D6212D7F9 for <lsr@ietf.org>; Tue, 15 May 2018 02:33:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4456; q=dns/txt; s=iport; t=1526376807; x=1527586407; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WQ8YZnYImwHR9PoIDLgXu6lzRNw3RaiNMtxDLuxmPDA=; b=P3Sq9n+FeUTF6No3TT3GQ8He0A8FGhNuTAWjEuufrultti/MR6YPINM+ jJiQeaH5z/ODvZ56cX4gH1iZqI0I/b0iz7LLvRMkIyeWGZ+dLVAd2mmDT Ao8ZQ1sOzxBESYe1uifFH/U+sgE031cKfxMh/kAbxa+nr/B/tPz2adP5G I=;
X-IronPort-AV: E=Sophos;i="5.49,403,1520899200"; d="scan'208";a="3848935"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 May 2018 09:33:25 +0000
Received: from [10.147.24.18] ([10.147.24.18]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w4F9XNSd025307; Tue, 15 May 2018 09:33:24 GMT
Message-ID: <5AFAA965.2020308@cisco.com>
Date: Tue, 15 May 2018 11:33:25 +0200
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Christian Hopps <chopps@chopps.org>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
CC: "lsr@ietf.org" <lsr@ietf.org>
References: <152599973361.10651.12984126140632073221@ietfa.amsl.com> <a1522cde71f94291b49eedde5f48a468@XCH-ALN-001.cisco.com> <87mux1wb7p.fsf@chopps.org>
In-Reply-To: <87mux1wb7p.fsf@chopps.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/YNxr_H-gOpYGwM13uP5RikSqLcA>
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-segment-routing-msd-11.txt
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 15 May 2018 09:33:29 -0000

Hi Chris,

On 15/05/18 10:54 , Christian Hopps wrote:
>
> Hi Les,
>
> I was going over the 2 SR-MSD documents (IS-IS and OSPF) just wondering
> how viable it would be and if we should combine them.
>
> In any case doing the diff highlighted a couple issues in the IS-IS
> version.
>
> Issue: Under both the Node and Link sub-tlv's the MSD type (1?) is not
> actually mentioned, only the "MSD value", if one was pedantic it would
> mean that regardless of the type the value was always the same,
> certainly not what is intended. :)
>
> Issue: The OSPF version adds text about what to do in the presence of
> multiple instances of the same TLV. This highlighted the fact that the
> IS-IS draft doesn't do this, but also doesn't talk about there only
> being 1 allowed.
>
> Maybe Issue: We've got 2 drafts creating the same sub-[-sub]-tlv MSD
> type registry. I fully agree that we should only have one registry, but
> it's interesting that we'll have 2 publications that create and
> reference it. Also, where does this registry go in IANA? There are
> distinct IS-IS, OSPFv2 and OSPFv3 pages that contain the IANA registries
> for each protocol. Should we create a new shared LSR or IGP page? Anyway
> this might be a reason to combine the 2 documents.

there is one already:
https://www.iana.org/assignments/igp-parameters/igp-parameters.xhtml

I agree that we need registry to be created in only one of the documents 
and have other reference it, unless we merge these two drafts.


thanks,
Peter

>
> While somewhat inelegant we could probably avoid any need to re-Last
> Call if the combination was basically a cut and paste operation.
>
> Thanks,
> Chris.
>
> Les Ginsberg (ginsberg) <ginsberg@cisco.com> writes:
>
>> This is a minor editorial revision to make the draft consistent w
>> draft-ietf-ospf-segment-routing-msd-12.
>>
>>    Les
>>
>>> -----Original Message-----
>>> From: Lsr <lsr-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
>>> Sent: Thursday, May 10, 2018 5:49 PM
>>> To: i-d-announce@ietf.org
>>> Cc: lsr@ietf.org
>>> Subject: [Lsr] I-D Action: draft-ietf-isis-segment-routing-msd-11.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           : Signaling MSD (Maximum SID Depth) using IS-IS
>>>         Authors         : Jeff Tantsura
>>>                           Uma Chunduri
>>>                           Sam Aldrin
>>>                           Les Ginsberg
>>>     Filename        : draft-ietf-isis-segment-routing-msd-11.txt
>>>     Pages           : 9
>>>     Date            : 2018-05-10
>>>
>>> Abstract:
>>>    This document defines a way for an IS-IS Router to advertise multiple
>>>    types of supported Maximum SID Depths (MSDs) at node and/or link
>>>    granularity.  Such advertisements allow entities (e.g., centralized
>>>    controllers) to determine whether a particular SID stack can be
>>>    supported in a given network.  This document only defines one type of
>>>    MSD maximum label imposition, but defines an encoding that can
>>>    support other MSD types.
>>>
>>>
>>> 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-11
>>> https://datatracker.ietf.org/doc/html/draft-ietf-isis-segment-routing-msd-
>>>
>>> 11
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-routing-msd-11
>>>
>>>
>>> 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
>>
>> _______________________________________________
>> Lsr mailing list
>> Lsr@ietf.org
>> https://www.ietf.org/mailman/listinfo/lsr
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
> .
>