Re: [Lsr] Proposed Errata for RFCs 8919/8920

Peter Psenak <ppsenak@cisco.com> Thu, 17 June 2021 14:55 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 5988E3A232B for <lsr@ietfa.amsl.com>; Thu, 17 Jun 2021 07:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.597
X-Spam-Level:
X-Spam-Status: No, score=-12.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_NONE=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 E38D5Rsm4sUO for <lsr@ietfa.amsl.com>; Thu, 17 Jun 2021 07:55:28 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20DF83A2325 for <lsr@ietf.org>; Thu, 17 Jun 2021 07:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16824; q=dns/txt; s=iport; t=1623941728; x=1625151328; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=SpfEyjBze2pLZzCVyHZkzURMpO5giljum008myL3goE=; b=Jn0oQAst2WwrJNYZfsDJWlyi19Bd6A2PGdNrXM0B2+ClUibGNQISROei jG4DpkcKaLVmKX8guAkNHWopC3mTB0kOQZ7nNJFyIrfxQrdUEbLgMPKsn T4gagPWl4tvqws2MIWBYSmLUuvggKkW+yrrm4YJvFNWt8ugkGas4vkYEO I=;
X-IronPort-AV: E=Sophos;i="5.83,280,1616457600"; d="scan'208";a="34603686"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 Jun 2021 14:55:26 +0000
Received: from [10.147.24.27] ([10.147.24.27]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id 15HEtPC8004651; Thu, 17 Jun 2021 14:55:25 GMT
To: "Selderslaghs, Rudy (Nokia - BE/Antwerp)" <rudy.selderslaghs@nokia.com>, Shraddha Hegde <shraddha=40juniper.net@dmarc.ietf.org>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>, "lsr@ietf.org" <lsr@ietf.org>
Cc: DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com>
References: <BY5PR11MB4337B8FB7707B24DDE302182C1309@BY5PR11MB4337.namprd11.prod.outlook.com> <CY4PR05MB357627C26A90AE7E9C5C89F7D50F9@CY4PR05MB3576.namprd05.prod.outlook.com> <AM0PR07MB6386EEAFB141820A4B1C5844E00F9@AM0PR07MB6386.eurprd07.prod.outlook.com> <BY5PR11MB433748CF078EAF485FD12641C10F9@BY5PR11MB4337.namprd11.prod.outlook.com> <CY4PR05MB35760AF7195C31E25E920A4FD50E9@CY4PR05MB3576.namprd05.prod.outlook.com> <AM0PR07MB6321150D75F6077E0EE51C8AE80E9@AM0PR07MB6321.eurprd07.prod.outlook.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <0e74e67e-35d0-8d44-3e38-0c9452543ea9@cisco.com>
Date: Thu, 17 Jun 2021 16:55:25 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <AM0PR07MB6321150D75F6077E0EE51C8AE80E9@AM0PR07MB6321.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.147.24.27, [10.147.24.27]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/bO4WUsbHYs6D_qUQAi3HjAfMAXw>
Subject: Re: [Lsr] Proposed Errata for RFCs 8919/8920
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: Thu, 17 Jun 2021 14:55:34 -0000

Hi Rudy,

please see inline:

On 17/06/2021 15:38, Selderslaghs, Rudy (Nokia - BE/Antwerp) wrote:
> Hi Les,
> 
> The question remains whether an ISIS Appl-Spec-SRLG TLV with SABML 0 and 
> UDABML 0 means that it is valid for all applications or not.
> 
> This is currently not specified in RFC8919.
> 
> Secondly the approach to handle ISIS Appl-Spec-SRLG TLVs independently 
> from ASLA sub-TLVs in the context of overruling “All-Appl” attributes, 
> creates confusion in BGP-LS in my opinion.
> 
> Take the following example with TLV’s belonging to the same link:
> 
> IS-Neighbors TLV
> 
>           ASLA TLV
> 
>                   SABML 0, UDABML 0 (= All Appl)
> 
>                   TE-Metric 20
> 
> Appl-Spec-SRLG TLV
> 
>           SABML 1, UDABML 0, Bitmap SR-Policy
> 
>           SRLG 1
> 
> Following your answer, SR-Policy has to use TE-Metric 20 and SRLG 1.
> 
> Now suppose that the node that receives this ISIS advertisement has to 
> pass this on to a server via BGP-LS, this will be the result:
> 
> Link Attributes:
> 
>          ASLA TLV
> 
>                  SABML 0, UDABML 0 (= All Appl)
> 
>                  TE-Metric 20
> 
>          ASLA TLV
> 
>                  SABML 1, UDABML 0, Bitmap SR-Policy
> 
>                  SRLG 1
> 
> The server that receives this BGP-LS advertisement, has to take into 
> account that it comes from the ISIS protocol in order to treat the ASLA 
> TLV with SRLG info independently (as ISIS is supposed to do). I.e. the 
> ASLA TLV with SRLG info does not overrule the first ASLA TLV and the 
> server has to use TE-Metric 20 and SRLG 1 for SR-Policy.
> 
> If the server would receive the same BGP-LS advertisement  for the OSPF 
> protocol, it can only use SRLG 1 for SR-Policy, because the second ASLA 
> TLV overrules the first one in line with the OSPF rules.
> 
> I think this is confusing and that it is more consistent to treat an 
> ISIS Appl-Spec-SRLG TLV as an ASLA TLV in the context of overruling of 
> “All-Appl” attributes.
> 
> The fact that ISIS transports SRLG info via a separate TLV seems no 
> reason to me to treat it independent of ASLA TLV’s.

the above problem is the result of the different encoding of the same 
data in ISIS and BGP-LS.

 From the ISIS perspective, there are two independent TLVs:

a) Application-Specific Link Attributes TLV
b) Application-Specific SRLG TLV

Each of these carry it's own Application Identifier Bit Mask and carry 
disjoint set of attributes. We clearly can not mix these TLVs together.

BGP-LS only has the single Application Specific Link Attributes TLV, 
that is mixing SRLGs with other link attributes.

To be able to interpret the BGP-LS data on the receiver in a protocol 
independent way, the BGP-LS originator would have to 'translate' the 
ISIS AS SRLGs consistently with the BGP-LS encoding - that would have to 
be done in draft-ietf-idr-bgp-ls-app-specific-attr. We will work on that 
and update that draft.

 From the ISIS perspective the behavior is unchanged - the 
Application-Specific SRLG TLVs have to be treated independently of the 
Application-Specific Link Attributes TLVs.

thanks,
Peter

> 
> Thanks,
> 
> Rudy
> 
> *From:*Lsr <lsr-bounces@ietf.org> *On Behalf Of *Shraddha Hegde
> *Sent:* Thursday, June 17, 2021 7:14 AM
> *To:* Les Ginsberg (ginsberg) <ginsberg@cisco.com>; Van De Velde, Gunter 
> (Nokia - BE/Antwerp) <gunter.van_de_velde@nokia.com>; lsr@ietf.org
> *Cc:* DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com>
> *Subject:* Re: [Lsr] Proposed Errata for RFCs 8919/8920
> 
> Les,
> 
>> Whether ASLA sub-TLV is present in IS-Neighbor TLV and whether it has zero-length ABM on non-zero-length ABM is irrelevant to the use of ASLA SRLG TLV – and vice versa.
> 
> Can you state this explicitly in the document?
> 
> Rgds
> 
> Shraddha
> 
> Juniper Business Use Only
> 
> *From:*Les Ginsberg (ginsberg) <ginsberg@cisco.com 
> <mailto:ginsberg@cisco.com>>
> *Sent:* Wednesday, June 16, 2021 10:31 PM
> *To:* Van De Velde, Gunter (Nokia - BE/Antwerp) 
> <gunter.van_de_velde@nokia.com <mailto:gunter.van_de_velde@nokia.com>>; 
> Shraddha Hegde <shraddha@juniper.net <mailto:shraddha@juniper.net>>; 
> lsr@ietf.org <mailto:lsr@ietf.org>
> *Cc:* DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com 
> <mailto:bruno.decraene@orange.com>>
> *Subject:* RE: Proposed Errata for RFCs 8919/8920
> 
> *[External Email. Be cautious of content]*
> 
> Gunter –
> 
> There is no relationship between the ASLA SRLG TLV and IS-Neighbor TLV.
> 
> I do not understand why you would think that there is.
> 
> Whether ASLA sub-TLV is present in IS-Neighbor TLV and whether it has 
> zero-length ABM on non-zero-length ABM is irrelevant to the use of ASLA 
> SRLG TLV – and vice versa.
> 
>     Les
> 
> *From:*Van De Velde, Gunter (Nokia - BE/Antwerp) 
> <gunter.van_de_velde@nokia.com <mailto:gunter.van_de_velde@nokia.com>>
> *Sent:* Wednesday, June 16, 2021 9:07 AM
> *To:* Shraddha Hegde <shraddha@juniper.net 
> <mailto:shraddha@juniper.net>>; Les Ginsberg (ginsberg) 
> <ginsberg@cisco.com <mailto:ginsberg@cisco.com>>; lsr@ietf.org 
> <mailto:lsr@ietf.org>
> *Cc:* DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com 
> <mailto:bruno.decraene@orange.com>>
> *Subject:* RE: Proposed Errata for RFCs 8919/8920
> 
> Another item of ambiguity is whether “wildcarding” applies also to the 
> ISIS TE-Appl-Spec-SRLG TLV.
> 
> It seems that the RFC8919 does not specify it.
> 
> Note: for OSPF the wildcarding also applies to SRLG info because it is 
> transported via the same container TLV as the other TE attributes.
> 
> _Example 1_
> 
> TE-IS-NBRs TLV
> 
>       Link x
> 
>            ASLA TLV
> 
>                SABML 0, UDABML 0 (= All Appl)
> 
> TE-Metric 20
> 
> TE-Appl-Spec-SRLG TLV
> 
> Link x
> 
>      SABML 1, UDABML 0, Bitmap Flex-Algo
> 
>     SRLG 1 2 3
> 
> Should TE-Metric 20 be used for Flex-Algo or not ?
> 
> In other words, is the wildcard ASLA TLV overruled by the specific 
> TE-Appl-Spec_SRLG TLV or not ?
> 
> _Example 2_
> 
> Maybe this is an invalid example if wildcarding does not apply for the 
> TE-Appl-SRLG TLV.
> 
> TE-IS-NBRs
> 
>       Link x
> 
>            ASLA TLV
> 
> SABML 1, UDABML 0, Bitmap Flex-Algo
> 
>                TE-Metric 20
> 
> TE-Appl-Spec-SRLG
> 
>      Link x
> 
> SABML 0, UDABML 0 (= All Appl)
> 
>     SRLG 1 2 3
> 
> Should SRLG 1 2 3 be used for Flex-Algo or not ?
> 
> What is your opinion ?
> 
> G/
> 
> *From:*Shraddha Hegde <shraddha@juniper.net <mailto:shraddha@juniper.net>>
> *Sent:* Wednesday, June 16, 2021 4:46 PM
> *To:* Les Ginsberg (ginsberg) <ginsberg=40cisco.com@dmarc.ietf.org 
> <mailto:ginsberg=40cisco.com@dmarc.ietf.org>>; lsr@ietf.org 
> <mailto:lsr@ietf.org>
> *Cc:* DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com 
> <mailto:bruno.decraene@orange.com>>; Van De Velde, Gunter (Nokia - 
> BE/Antwerp) <gunter.van_de_velde@nokia.com 
> <mailto:gunter.van_de_velde@nokia.com>>
> *Subject:* RE: Proposed Errata for RFCs 8919/8920
> 
> Hi,
> 
> I think that there may still be some ambiguity arising from the text 
> below due to the fact that
> 
> There are attributes such as maximum-link-bandwidth which have special 
> behaviour mentioned in later sections.
> 
> "Link attributes MAY be advertised associated with zero-length 
> Application Identifier Bit Masks for both standard applications and 
> user-defined applications.
> Such advertisements MUST be used by standard applications and/or user 
> defined applications when no link attribute advertisements with a 
> non-zero-length
> Application Identifier Bit Mask and a matching Application Identifier 
> Bit set are present for a given link. Otherwise, such advertisements 
> MUST NOT be used."
> 
> 
> 
> For example, If max link bandwidth attribute comes in a
> Zero length SABM & UDABM and we have a Flex-algo specific ASLA
> that does not have the max-link-bandwidth advertised, can
> Flex-algo use max-link-bandwidth attribute?
> 
> My interpretation from modified text for ISIS is that,  it cannot use it.
> I think there is no harm in re-iterating in order to avoid people 
> reading is differently.
> 
> 
> Link attributes MAY be advertised associated with zero-length 
> Application Identifier Bit Masks for both standard applications and 
> user-defined applications.
> Such advertisements MUST be used by standard applications and/or user 
> defined applications when no link attribute advertisements with a 
> non-zero-length
> Application Identifier Bit Mask and a matching Application Identifier 
> Bit set are present for a given link. Otherwise, such advertisements 
> MUST NOT be used.
> *In other words,
> When an application specific link Attribute sub-TLV is advertised with 
> one or more specific
> standard application or user defined application bits set, all link 
> attributes that are allowed in ASLA MUST
> be used from the ASLA sub-TLVs having that specific application bit set.
> For the purposes of such applications, link attributes MUST NOT be used from
> ASLA sub-TLV with zero SABM & UDABM length*.
> 
> Rgds
> 
> Shraddha
> 
> Juniper Business Use Only
> 
> *From:*Lsr <lsr-bounces@ietf.org <mailto:lsr-bounces@ietf.org>> *On 
> Behalf Of *Les Ginsberg (ginsberg)
> *Sent:* Tuesday, June 15, 2021 8:55 PM
> *To:* lsr@ietf.org <mailto:lsr@ietf.org>
> *Cc:* DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com 
> <mailto:bruno.decraene@orange.com>>; Van De Velde, Gunter (Nokia - 
> BE/Antwerp) <gunter.van_de_velde@nokia.com 
> <mailto:gunter.van_de_velde@nokia.com>>
> *Subject:* [Lsr] Proposed Errata for RFCs 8919/8920
> 
> *[External Email. Be cautious of content]*
> 
> Folks -
> 
> Recent discussions on the list have highlighted some unintentional 
> ambiguity in how ASLA advertisements are to be used. Please see 
> https://mailarchive.ietf.org/arch/msg/lsr/prSLJDkMUnHm6h7VuCdn_Q7-1vg/ 
> <https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/lsr/prSLJDkMUnHm6h7VuCdn_Q7-1vg/__;!!NEt6yMaO-gk!RK_eZNNu1y0aJvAqIaNwHTIFAjHWFJwW1UqyOO8ACxB0kof3jmD_dRkiPkbVLJyA$>
> 
> The following proposed Errata address this ambiguity and aligns language 
> in the two RFCs.
> 
> We welcome comments on the proposed Errata before officially filing them.
> 
>    Les and Peter
> 
> /Errata Explanation/
> 
> //
> 
> /Both RFC 8919 and RFC 8920 define advertising link attributes with zero 
> length Standard Application Bit Mask (SABM) and zero length User Defined 
> Application Bit Mask (UDABM) /
> 
> /as a means of advertising link attributes that can be used by any 
> application. However, the text uses the word "permitted", suggesting 
> that the use of such advertisements is "optional". /
> 
> /Such an interpretation could lead to interoperability issues and is not 
> what was intended./
> 
> //
> 
> /The replacement text below makes explicit the specific conditions when 
> such advertisements MUST be used and the specific conditions under which 
> they MUST NOT be used./
> 
> //
> 
> */RFC 8919 Section 4.2:/*
> 
> //
> 
> /OLD/
> 
> //
> 
> */"If link attributes are advertised associated with zero-length 
> Application Identifier Bit Masks for both standard applications and 
> user-defined applications, /*
> 
> */then any standard application and/or any user-defined application is 
> permitted to use that set of link attributes so long as there is not 
> another set of attributes/*
> 
> */advertised on that same link that is associated with a non-zero-length 
> Application Identifier Bit Mask with a matching Application Identifier 
> Bit set."/*
> 
> //
> 
> /NEW/
> 
> //
> 
> */"Link attributes MAY be advertised associated with zero-length 
> Application Identifier Bit Masks for both standard applications and 
> user-defined applications. /*
> 
> */Such advertisements MUST be used by standard applications and/or user 
> defined applications when no link attribute advertisements with a 
> non-zero-length /*
> 
> */Application Identifier Bit Mask and a matching Application Identifier 
> Bit set are present for a given link. Otherwise, such advertisements 
> MUST NOT be used."/*
> 
> //
> 
> */RFC 8919 Section 6.2/*
> 
> //
> 
> /OLD/
> 
> //
> 
> */"Link attribute advertisements associated with zero-length Application 
> Identifier Bit Masks for both standard applications and user-defined 
> applications are usable/*
> 
> */by any application, subject to the restrictions specified in Section 
> 4.2. If support for a new application is introduced on any node in a 
> network in the presence of such/*
> 
> */advertisements, these advertisements are permitted to be used by the 
> new application. If this is not what is intended, then existing 
> advertisements MUST be readvertised/*
> 
> */with an explicit set of applications specified before a new 
> application is introduced."/*
> 
> //
> 
> //
> 
> /NEW/
> 
> //
> 
> */"Link attribute advertisements associated with zero-length Application 
> Identifier Bit Masks for both standard applications and user-defined 
> applications are usable /*
> 
> */by any application, subject to the restrictions specified in Section 
> 4.2. If support for a new application is introduced on any node in a 
> network in the presence of such /*
> 
> */advertisements, the new application will use these advertisements, 
> when the aforementioned restrictions are met. If this is not what is 
> intended, then existing /*
> 
> */advertisements MUST be readvertised with an explicit set of 
> applications specified before a new application is introduced."/*
> 
> *//*
> 
> *//*
> 
> //
> 
> */RFC 8920 Section 5/*
> 
> *//*
> 
> /OLD/
> 
> //
> 
> */"If link attributes are advertised with zero-length Application 
> Identifier Bit Masks for both standard applications and user-defined 
> applications, /*
> 
> */then any standard application and/or any user-defined application is 
> permitted to use that set of link attributes. If support for a new 
> application /*
> 
> */is introduced on any node in a network in the presence of such 
> advertisements, these advertisements are permitted to be used by the new /*
> 
> */application. If this is not what is intended, then existing 
> advertisements MUST be readvertised with an explicit set of applications 
> specified /*
> 
> */before a new application is introduced./*
> 
> *//*
> 
> */An application-specific advertisement (Application Identifier Bit Mask 
> with a matching Application Identifier Bit set) for an attribute MUST /*
> 
> */always be preferred over the advertisement of the same attribute with 
> the zero-length Application Identifier Bit Masks for both standard /*
> 
> */applications and user-defined applications on the same link."/*
> 
> *//*
> 
> /NEW/
> 
> //
> 
> */"Link attributes MAY be advertised associated with zero-length 
> Application Identifier Bit Masks for both standard applications and 
> user-defined applications. /*
> 
> */Such advertisements MUST be used by standard applications and/or user 
> defined applications when no link attribute advertisements with a 
> non-zero-length /*
> 
> */Application Identifier Bit Mask and a matching Application Identifier 
> Bit set are present for a given link. Otherwise, such advertisements 
> MUST NOT be used."/*
> 
> //
> 
> //
> 
> //
> 
> */RFC 8920 New Section between 12.1 and 12.2. Current sections following 
> this new section will need to be renumbered./*
> 
> //
> 
> //
> 
> */12.2 Use of Zero-Length Application Identifier Bit Masks/*
> 
> *//*
> 
> */"Link attribute advertisements associated with zero-length Application 
> Identifier Bit Masks for both standard applications and user-defined 
> applications are usable /*
> 
> */by any application, subject to the restrictions specified in Section 
> 5. If support for a new application is introduced on any node in a 
> network in the presence of such /*
> 
> */advertisements, the new application will use these advertisements, 
> when the aforementioned restrictions are met. If this is not what is 
> intended, then existing /*
> 
> */advertisements MUST be readvertised with an explicit set of 
> applications specified before a new application is introduced."/*
> 
> //
> 
> //
>