Re: [Isis-wg] New Version Notification for draft-ginsberg-isis-te-app-03.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Fri, 23 June 2017 07:11 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 749C112E048 for <isis-wg@ietfa.amsl.com>; Fri, 23 Jun 2017 00:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 EB50MS3RHjWj for <isis-wg@ietfa.amsl.com>; Fri, 23 Jun 2017 00:11:02 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2D5212E046 for <isis-wg@ietf.org>; Fri, 23 Jun 2017 00:11:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10364; q=dns/txt; s=iport; t=1498201862; x=1499411462; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=bSdIORRYxjH5OGHMJkacPvRcD6Gb39tDDVw9hR14dCE=; b=FauT/n43/oQy3p1LhXNyeQwCk7RE+N53J/ffemgAJwWge/NKQLcXV21S xnylIpInHXXq3Sr0ok8wakhaDDVCwZ6IZtULT/uP74TxDcM/s92tVtie6 4TuFH+gsTqrZB/7SiYa3SqxWLs7lyKg39NBMtC5TvFcxX8Zub+Q3CWmgC I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CZAAA7vkxZ/5RdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1higQ0HjX6RYZV4ghEhC4V4AoMHPxgBAgEBAQEBAQFrKIUYAQE?= =?us-ascii?q?BAQIBAQE4NAkHBwQCAQgRBAEBAR4JBycLFAkIAgQBEgiKHAgQrzyLaQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAR2DJ4NMgWCDJYMmgRUSAUIGhUgFkEGOIgKHMYwnghJ?= =?us-ascii?q?WhHKKPpUVAR84fwt0FR8qhw92hniBI4ENAQEB?=
X-IronPort-AV: E=Sophos;i="5.39,376,1493683200"; d="scan'208";a="261461689"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jun 2017 07:11:01 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v5N7B16M024211 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 23 Jun 2017 07:11:01 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 23 Jun 2017 02:11:00 -0500
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.1210.000; Fri, 23 Jun 2017 02:11:00 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "Peter Psenak (ppsenak)" <ppsenak@cisco.com>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: [Isis-wg] New Version Notification for draft-ginsberg-isis-te-app-03.txt
Thread-Index: AQHS6c/fhaqyHEjha0Wjn2wHyRM0CqItztVwgAEfgyCAAFzjgIABg48AgAAmhdCAAWb4AP//raqw
Date: Fri, 23 Jun 2017 07:11:00 +0000
Message-ID: <8e067614a802461fa14ea29ac020c748@XCH-ALN-001.cisco.com>
References: <149796821052.23693.7098486846561359870.idtracker@ietfa.amsl.com> <1b6e7697f8634a0c9d901442a9b028da@XCH-ALN-001.cisco.com> <8220_1498030951_594A2367_8220_41_1_9E32478DFA9976438E7A22F69B08FF921E9C901A@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <594A2969.9030501@cisco.com> <8875_1498115717_594B6E84_8875_64_1_9E32478DFA9976438E7A22F69B08FF921E9CAA59@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <e932880796c5474b9843c62f1113b2af@XCH-ALN-001.cisco.com> <13538_1498201077_594CBBF5_13538_397_1_9E32478DFA9976438E7A22F69B08FF921E9CB4A3@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <13538_1498201077_594CBBF5_13538_397_1_9E32478DFA9976438E7A22F69B08FF921E9CB4A3@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
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.69.226]
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/il9hiijAw2AjshmLhnzcFXnzuKo>
Subject: Re: [Isis-wg] New Version Notification for draft-ginsberg-isis-te-app-03.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: Fri, 23 Jun 2017 07:11:05 -0000

Stephane -

I do understand what you have asked for - please understand my point.

If something is outside the scope of the specification then the specification MUST NOT: infer, recommend, suggest, imply, or otherwise comment...

The specification has provided support for advertising User Defined Apps - you can use this space as you wish without violating the specification. And someone else can use the space in a way different than you choose to do - and they also will not be violating the specification.

   Les


> -----Original Message-----
> From: stephane.litkowski@orange.com
> [mailto:stephane.litkowski@orange.com]
> Sent: Thursday, June 22, 2017 11:58 PM
> To: Les Ginsberg (ginsberg); Peter Psenak (ppsenak); isis-wg@ietf.org
> Subject: RE: [Isis-wg] New Version Notification for draft-ginsberg-isis-te-app-
> 03.txt
> 
> My point is not to tell what to do with UDAs. It is to tell that standard
> applications MAY not use standard bits.
> 
> 
> -----Original Message-----
> From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
> Sent: Thursday, June 22, 2017 16:36
> To: LITKOWSKI Stephane OBS/OINIS; Peter Psenak (ppsenak); isis-
> wg@ietf.org
> Subject: RE: [Isis-wg] New Version Notification for draft-ginsberg-isis-te-app-
> 03.txt
> 
> Stephane -
> 
> > -----Original Message-----
> > From: stephane.litkowski@orange.com
> > [mailto:stephane.litkowski@orange.com]
> > Sent: Thursday, June 22, 2017 12:15 AM
> > To: Peter Psenak (ppsenak); Les Ginsberg (ginsberg); isis-wg@ietf.org
> > Subject: RE: [Isis-wg] New Version Notification for
> > draft-ginsberg-isis-te-app- 03.txt
> >
> > Hi Peter,
> >
> > Thanks for your feedback, few comments inline
> >
> > -----Original Message-----
> > From: Peter Psenak [mailto:ppsenak@cisco.com]
> > Sent: Wednesday, June 21, 2017 10:08
> > To: LITKOWSKI Stephane OBS/OINIS; Les Ginsberg (ginsberg); isis-
> > wg@ietf.org
> > Subject: Re: [Isis-wg] New Version Notification for
> > draft-ginsberg-isis-te-app- 03.txt
> >
> > Hi Stephane,
> >
> > On 21/06/17 09:42 , stephane.litkowski@orange.com wrote:
> > > Hi Les,
> > >
> > > The proposal has a better shape. Still two comments:
> > > - As mentioned earlier, please precise that LFA means any flavor of
> > > LFA
> > (LFA,rLFA,dLFA,TILFA...).
> >
> > I would just say any flavor of LFA. Not all LFA types are defined in
> > IETF documents.
> > [SLI] I agree, "any flavor" works
> >
> > > - I would also like to see that "standard" applications may also use
> > > UDAs
> > instead of the standard bit and possibility two sets of attributes
> > (two UDAs or
> > 1 std + 1 UDA): one example could be having an SR-TE tunnel using a
> > particular set of attributes, and another SR-TE tunnel using another
> > set of attributes.
> >
> > nobody is preventing you to do that. You can map any application to a
> > UDA bits.
> >
> > [SLI] Yes, but nothings tells that it is also allowed. I just want
> > this point to be clear in the text.
> >
> [Les:] The draft explicitly states that the use of UDA bits is outside the
> purview of any standards body. It would be unwise - and contradictory - to
> then start specifying how UDA bits can/cannot be used. The whole point of
> UDA is that it is up to the user to decide what the bits mean.
> 
> You clearly have some ideas about how you want to use them - but it is not
> the role of any specification to comment on your ideas any more than
> anyone else's ideas.
> 
> I think it is necessary for the draft to remain silent in this area.
> 
>    Les
> 
> >
> > thanks,
> > Peter
> >
> > >
> > > Brgds,
> > >
> > > Stephane
> > >
> > > -----Original Message-----
> > > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Les
> > > Ginsberg (ginsberg)
> > > Sent: Tuesday, June 20, 2017 16:30
> > > To: isis-wg@ietf.org
> > > Subject: [Isis-wg] FW: New Version Notification for
> > > draft-ginsberg-isis-te-app-03.txt
> > >
> > > Folks -
> > >
> > > This new version adds support for using a set of link attribute
> > advertisements for ANY application - something which the OSPF
> > companion draft (draft-ppsenak-ospf-te-link-attr-reuse) supports.
> > > It also aligns the encoding so that is similar to that defined in
> > > the OSPF
> > draft.
> > >
> > >      Les
> > >
> > >
> > > -----Original Message-----
> > > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > > Sent: Tuesday, June 20, 2017 7:17 AM
> > > To: Wim Henderickx; Stefano Previdi; Peter Psenak (ppsenak); Les
> > > Ginsberg (ginsberg)
> > > Subject: New Version Notification for
> > > draft-ginsberg-isis-te-app-03.txt
> > >
> > >
> > > A new version of I-D, draft-ginsberg-isis-te-app-03.txt has been
> > successfully submitted by Les Ginsberg and posted to the IETF repository.
> > >
> > > Name:		draft-ginsberg-isis-te-app
> > > Revision:	03
> > > Title:		IS-IS TE Attributes per application
> > > Document date:	2017-06-20
> > > Group:		Individual Submission
> > > Pages:		15
> > > URL:            https://www.ietf.org/internet-drafts/draft-ginsberg-isis-te-
> app-
> > 03.txt
> > > Status:         https://datatracker.ietf.org/doc/draft-ginsberg-isis-te-app/
> > > Htmlized:       https://tools.ietf.org/html/draft-ginsberg-isis-te-app-03
> > > Htmlized:       https://datatracker.ietf.org/doc/html/draft-ginsberg-isis-te-
> > app-03
> > > Diff:           https://www.ietf.org/rfcdiff?url2=draft-ginsberg-isis-te-app-03
> > >
> > > Abstract:
> > >     Existing traffic engineering related link attribute advertisements
> > >     have been defined and are used in RSVP-TE deployments.  In cases
> > >     where multiple applications wish to make use of these link attributes
> > >     the current advertisements do not support application specific values
> > >     for a given attribute nor do they support indication of which
> > >     applications are using the advertised value for a given link.
> > >
> > >     This draft introduces new link attribute advertisements which address
> > >     both of these shortcomings.  It also discusses backwards
> > >     compatibility issues and how to minimize duplicate advertisements in
> > >     the presence of routers which do not support the extensions defined
> > >     in this document.
> > >
> > >
> > >
> > >
> > >
> > > 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.
> > >
> > > The IETF Secretariat
> > >
> > > _______________________________________________
> > > Isis-wg mailing list
> > > Isis-wg@ietf.org
> > > https://www.ietf.org/mailman/listinfo/isis-wg
> > >
> > >
> >
> __________________________________________________________
> > ____________
> > > ___________________________________________________
> > >
> > > Ce message et ses pieces jointes peuvent contenir des informations
> > > confidentielles ou privilegiees et ne doivent donc pas etre
> > > diffuses, exploites ou copies sans autorisation. Si vous avez recu
> > > ce message par erreur, veuillez le signaler a l'expediteur et le
> > > detruire ainsi que les
> > pieces jointes. Les messages electroniques etant susceptibles
> > d'alteration, Orange decline toute responsabilite si ce message a ete
> > altere, deforme ou falsifie. Merci.
> > >
> > > This message and its attachments may contain confidential or
> > > privileged information that may be protected by law; they should not
> > > be
> > distributed, used or copied without authorisation.
> > > If you have received this email in error, please notify the sender
> > > and delete
> > this message and its attachments.
> > > As emails may be altered, Orange is not liable for messages that
> > > have been
> > modified, changed or falsified.
> > > Thank you.
> > >
> > > _______________________________________________
> > > Isis-wg mailing list
> > > Isis-wg@ietf.org
> > > https://www.ietf.org/mailman/listinfo/isis-wg
> > > .
> > >
> >
> >
> >
> __________________________________________________________
> >
> __________________________________________________________
> > _____
> >
> > Ce message et ses pieces jointes peuvent contenir des informations
> > confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
> > exploites ou copies sans autorisation. Si vous avez recu ce message
> > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi
> > que les pieces jointes. Les messages electroniques etant susceptibles
> > d'alteration, Orange decline toute responsabilite si ce message a ete altere,
> deforme ou falsifie. Merci.
> >
> > This message and its attachments may contain confidential or
> > privileged information that may be protected by law; they should not
> > be distributed, used or copied without authorisation.
> > If you have received this email in error, please notify the sender and
> > delete this message and its attachments.
> > As emails may be altered, Orange is not liable for messages that have
> > been modified, changed or falsified.
> > Thank you.
> 
> 
> __________________________________________________________
> __________________________________________________________
> _____
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites
> ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez
> le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les
> messages electroniques etant susceptibles d'alteration, Orange decline toute
> responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed,
> used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.