Re: [Lsr] [Last-Call] Opsdir telechat review of draft-ietf-ospf-te-link-attr-reuse-14

"Scott O. Bradner" <sob@sobco.com> Wed, 17 June 2020 15:53 UTC

Return-Path: <sob@sobco.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 CC3B63A0934; Wed, 17 Jun 2020 08:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 K1Qtw7CIicSz; Wed, 17 Jun 2020 08:53:01 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 7647C3A0929; Wed, 17 Jun 2020 08:53:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 70A6B390D969; Wed, 17 Jun 2020 11:52:59 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjrAALhrahni; Wed, 17 Jun 2020 11:52:54 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id BEDED390D957; Wed, 17 Jun 2020 11:52:54 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <BY5PR11MB433750F06C97392138FBC6FCC19A0@BY5PR11MB4337.namprd11.prod.outlook.com>
Date: Wed, 17 Jun 2020 11:52:54 -0400
Cc: "Rob Wilton (rwilton)" <rwilton@cisco.com>, Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>, Benjamin Kaduk <kaduk@mit.edu>, "lsr@ietf.org" <lsr@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-ospf-te-link-attr-reuse.all@ietf.org" <draft-ietf-ospf-te-link-attr-reuse.all@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8B23389-F0DF-4566-B201-ACB5AA04CE97@sobco.com>
References: <159216255398.11973.1707971108773200684@ietfa.amsl.com> <a26e9fc3-5abc-b992-ade1-940a32054aec@cisco.com> <BBE540DC-3B08-4E0E-89A3-E472C6F4EA52@sobco.com> <MN2PR11MB43663988FDD9EEEB446E87EAB59A0@MN2PR11MB4366.namprd11.prod.outlook.com> <BY5PR11MB433750F06C97392138FBC6FCC19A0@BY5PR11MB4337.namprd11.prod.outlook.com>
To: "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/_IF4cyy8B9ZeVkfVJWqwwKWbCRQ>
Subject: Re: [Lsr] [Last-Call] Opsdir telechat review of draft-ietf-ospf-te-link-attr-reuse-14
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 17 Jun 2020 15:53:04 -0000

I'm fine if both documents have the text

thanks


Scott

> On Jun 17, 2020, at 10:56 AM, Les Ginsberg (ginsberg) <ginsberg=40cisco.com@dmarc.ietf.org> wrote:
> 
> Rob -
> 
> IS-IS draft currently states:
> 
> "User Defined Application Identifier Bits have no relationship to
>   Standard Application Identifier Bits and are not managed by IANA or
>   any other standards body."
> 
> (OSPF has this text also.)
> 
> I am happy enough to include an additional statement similar to the OSPF text below in Section 4.
> 
> Scott can speak for himself of course - but not clear to me that this really satisfies him since his comment was on the OSPF draft that already had this text.
> 
> And not clear that this would make Ben (copied) any more comfortable since his concern (clarified in his most recent post) is about discussing allocation of the UDA bit space.
> 
> But I will add the text - it makes the two drafts closer in content - which has been an ongoing goal during the review process.
> 
> Thanx.
> 
>   Les
> 
> 
>> -----Original Message-----
>> From: Rob Wilton (rwilton) <rwilton@cisco.com>
>> Sent: Wednesday, June 17, 2020 5:09 AM
>> To: Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>; Les Ginsberg
>> (ginsberg) <ginsberg@cisco.com>
>> Cc: lsr@ietf.org; draft-ietf-ospf-te-link-attr-reuse.all@ietf.org; ops-
>> dir@ietf.org; last-call@ietf.org; Scott O. Bradner <sob@sobco.com>
>> Subject: RE: [Last-Call] Opsdir telechat review of draft-ietf-ospf-te-link-attr-
>> reuse-14
>> 
>> Hi Les,
>> 
>> Would you be opposed to adding text similar to the OSPF paragraph below to
>> the ISIS draft?
>> 
>> I think that the OSPF draft does a better job of first introducing UDAs.  Having
>> just looked at the ISIS draft, it does seem to somewhat assume that the
>> reader will just know what they are ...
>> 
>> I understand that this should resolve Scott's concerns.
>> 
>> Regards,
>> Rob
>> 
>> 
>>> -----Original Message-----
>>> From: last-call <last-call-bounces@ietf.org> On Behalf Of Scott O. Bradner
>>> Sent: 15 June 2020 11:17
>>> To: Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>
>>> Cc: lsr@ietf.org; draft-ietf-ospf-te-link-attr-reuse.all@ietf.org; ops-
>>> dir@ietf.org; last-call@ietf.org
>>> Subject: Re: [Last-Call] Opsdir telechat review of draft-ietf-ospf-te-
>>> link-attr-reuse-14
>>> 
>>> that looks just fine to me - thanks
>>> 
>>> Scott
>>> 
>>>> On Jun 15, 2020, at 5:14 AM, Peter Psenak
>>> <ppsenak=40cisco.com@dmarc.ietf.org> wrote:
>>>> 
>>>> Hi Scott.
>>>> 
>>>> there is a following text in the OSPF draft:
>>>> 
>>>> "On top of advertising the link attributes for standardized
>>>>  applications, link attributes can be advertised for the purpose of
>>>>  applications that are not standardized.  We call such an
>>>>  application a "User Defined Application" or "UDA".  These
>>>>  applications are not subject to standardization and are outside of
>>>>  the scope of this specification."
>>>> 
>>>> Feel free to propose an additional text if you feel above is not
>>> sufficient.
>>>> 
>>>> thanks,
>>>> Peter
>>>> 
>>>> 
>>>> 
>>>> On 14/06/2020 21:22, Scott Bradner via Datatracker wrote:
>>>>> Reviewer: Scott Bradner
>>>>> Review result: Ready
>>>>> I have reviewed the latest version of this document and my earlier
>>> issues have
>>>>> been resolved at least well enough for teh document to be considered
>>> ready for
>>>>> publication.
>>>>> that said I still do not see where "User Defined Application
>>> Identifier" is
>>>>> actually cleanly defined - one can read carefully and determine but it
>>> would be
>>>>> easier on the reader to just say that it is a field that can be used to
>>>>> indicate the use of one or more non-standard applications within some
>>> scope
>>>>> (network, subnet, link, organization, ... not sure what scopes are
>>> meaningful
>>>>> here but it does not seem that a User Defined Application Identifier
>>> would be a
>>>>> global (between network operators) value
>>>>> Scott
>>>> 
>>>> --
>>>> last-call mailing list
>>>> last-call@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/last-call
>>> 
>>> --
>>> last-call mailing list
>>> last-call@ietf.org
>>> https://www.ietf.org/mailman/listinfo/last-call
> 
> -- 
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call