Re: [Lsr] Regarding OSPF Extended Prefix Range TLV usage for External/NSSA prefixes defined in RFC 8665

Veerendranatha Reddy V <veerendranatha.reddy.v@ericsson.com> Wed, 19 August 2020 04:33 UTC

Return-Path: <veerendranatha.reddy.v@ericsson.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 5617B3A116F for <lsr@ietfa.amsl.com>; Tue, 18 Aug 2020 21:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 mK76ly0ybV9A for <lsr@ietfa.amsl.com>; Tue, 18 Aug 2020 21:33:26 -0700 (PDT)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2081.outbound.protection.outlook.com [40.107.21.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AA4E3A1170 for <lsr@ietf.org>; Tue, 18 Aug 2020 21:33:25 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Z5R/Um6QiEzvTqo6ZtEkNFd4+LnSXTPOZ69lNr2Un9l4R44VQ1IRN8BGfJpd8G5dSxxHrSnLgY7nvhxVYh3B1LvFotvadqoU7twVXz0lyucLhsYvwO5nOVahFrjLsEsWlirTVsbXAYOaQgFgwz95Bdmz5hrH+aowjTO3FF3d3Ez6GOtHcCBtbf7kp/UQqGz7YRiHmVtykd/fv2ize24uXdJJ5cE3naBwmGLtREjzgB6BtAwFdWarVEbs2+nK0RLAQbLEPfwalG8LwSk28QwJ+qJqcpDxYsDBxBZALgVerFBrfMN/mOhYhwxfizpjp4DQAJt576aZ72ZpX8++W6FYdQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fdNItw0ScWlRLOjaYHJFsNL2u4dtvaMLWDv+SxfO8Cc=; b=L17J10dvQbJT/uL+6lTGF++k/QGpDwhAZdAPFMZC5XfVr5F7TySIdNPzfH6FXzHeYkIBSIDjMjAHSr2MaQUFlFvwLb2g18ETOm65q+5S7z+e4aeaHS7anta+9bO0azusLLI1dpB8MEAJZutb1N9WpA+uKFUoIWdR1FSpFtQf09Droma5jp8CJVk4iqdU5eN4dWuGcnXHbytAfyAzc2WtuRB8WUKXYtZFrdwPlFqpTVF+IDST68Q65/zB9OZFYBdpq6afHl043fNQTCvO20XL0xP4fJUYTN/n4ewqHQ9mR0/FuRlqba3yhOxJD46UXn1IuGiUTZ2nsrEd/S5a/IQUgw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fdNItw0ScWlRLOjaYHJFsNL2u4dtvaMLWDv+SxfO8Cc=; b=YiCF5T42BSCJL0uy4o5Awo/YGXfWKVzUQnrbwvRoNo/vxBPufMnaPidEM1cbjL5uOwYlf4+MNhB89/qur6ewXL1o0Lr1uTIUxR4MHDOpg1HGeBKEdEkHSXFkmZy/wuGYVOXZ/M2jfVEgMgut/GStwtsvMzQKAAKv0u0xhrnKR64=
Received: from DB7PR07MB3914.eurprd07.prod.outlook.com (2603:10a6:5:c::25) by DB6PR0701MB2279.eurprd07.prod.outlook.com (2603:10a6:4:50::6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3305.10; Wed, 19 Aug 2020 04:33:18 +0000
Received: from DB7PR07MB3914.eurprd07.prod.outlook.com ([fe80::50fa:d892:934f:190c]) by DB7PR07MB3914.eurprd07.prod.outlook.com ([fe80::50fa:d892:934f:190c%3]) with mapi id 15.20.3305.021; Wed, 19 Aug 2020 04:33:18 +0000
From: Veerendranatha Reddy V <veerendranatha.reddy.v@ericsson.com>
To: "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, Peter Psenak <ppsenak@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Regarding OSPF Extended Prefix Range TLV usage for External/NSSA prefixes defined in RFC 8665
Thread-Index: AdZ1bLVZomK+AP1qRgqOeyJr1fTjrwAGU2iAAABLkeAAFmiU4A==
Date: Wed, 19 Aug 2020 04:33:18 +0000
Message-ID: <DB7PR07MB3914AB432758DA51B94DEFE9BB5D0@DB7PR07MB3914.eurprd07.prod.outlook.com>
References: <DB7PR07MB3914AA1BF15E141673DF1E11BB5C0@DB7PR07MB3914.eurprd07.prod.outlook.com> <bb8d3f97-ec52-a91d-c3d6-896f86f498c1@cisco.com> <MW3PR11MB45708EA52FB3AA8E1BB8F199C15C0@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB45708EA52FB3AA8E1BB8F199C15C0@MW3PR11MB4570.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [103.210.133.150]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d4e142db-a254-4a1a-007b-08d843f8ff67
x-ms-traffictypediagnostic: DB6PR0701MB2279:
x-microsoft-antispam-prvs: <DB6PR0701MB2279A5D5377CE63FBB57DF6ABB5D0@DB6PR0701MB2279.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: HekPl2M2u1Wnsdar86NpBVg1INBf1c/mhigP7vxXHME5hO5x+UH/hdUWIbvd0aR5mH/UzoER/LSqkJWMvGc5th499Qohji/WLk/0p5gEuSX2LOFCkq4qbWcCUR4I+jEGBa4IbVTtMiDgHWGH5ORGbyhTVKxMAAaSpiVF3a53GFnCz7jVHs3cJ2ZnkjuUbq35nIFs9ckgl9RQWL2pHSPyio7e/IZ4YwDNTTnHRzjnT3qsH07ZUkN247nVpHyFIyUWEyrAITUD64qDi/GAz7LuSwjRTIwhxjj5/FrPN1QBHZ52i2FQ30eKixOa//wHYDGCv/EtidxE67YKGJMeCSvCfDp0zRl9TMqCFhjVc8IPN2Y/r8lU5KBUAVIpuWBZPJIQWGSiPMII9RY4x+rcJG1asQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR07MB3914.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(136003)(346002)(376002)(396003)(39860400002)(8936002)(110136005)(26005)(7696005)(2906002)(55016002)(66946007)(66476007)(64756008)(478600001)(66446008)(66556008)(53546011)(6506007)(966005)(71200400001)(9686003)(76116006)(186003)(316002)(66574015)(8676002)(83380400001)(5660300002)(33656002)(86362001)(52536014); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: g7IncqNob2wSSn19oDiSmvU548GCWibPdMe8LT8sZrb25OVJGFR5A4gGCrAASBcX+ogX4qiJ0qtmicsVqcINAf8nHbvlDbv0fIF+I3CAm5rLUkVBKUP5yo8s3z/qsKlcNMGpULI0KGyUe+L+ceYV/QKHrWJHev2DgIUCmftn7HASxTePpRrSy3OQ39p6GlWVt9O2Zx/KQThoDJ43SxcrLW+U35bzuqxImWUwoOq4cieB0/9I7PY1uBZJZL/T/WIUZMM047FR8BoMMumq+baIu8+dDF0lvkFvl9nyefCsO2Fj9f3s7isGpBk6gemRHK4ChyXfay0JrSOZF+nl/hBch5f+PdLyklkjU6n3b7hZu/jFHw00egX+3jpVu71uc3qJZC5JBWgg6frruwx90cx6PvCk0nD8evHYEcByF/h8i3YH7NJ7bAzF6vnaOn8ra7dXBkVkB6H316W/ngHGHlQAhHQze+kL5h4MZZ4K+CCaBJrj3HmHofJjSYvAgpc2SYntzy4nFYQQfGTjofNefb7bcJTCxYgkVXFzp1DQ7EaxGLXgNVsvX3ZAj7jo1ReuHmpngUDxpTljcV7Lw1Bv1tvAu6ks810rB45x1lgrj9Myy/YI2TIOGR1MV9gCW0ltaiYPfHzPEGhBHtwiiRncKNtFGw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB7PR07MB3914.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d4e142db-a254-4a1a-007b-08d843f8ff67
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2020 04:33:18.7976 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: VTaesabM7KR3bLjW608jhpiYtFk8Hfna32mr0eRYEWW9RYquONR3Pp2+8MiuMbo+lib7y8WMKj9E1XY+mgJA2uCwthaTw6Kt4dh02TOOUfiRztKauVatTUgd0qPjcq2L
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2279
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/b88XGF_U1hhQQoMFVQYYmyxz1PM>
X-Mailman-Approved-At: Wed, 19 Aug 2020 03:52:02 -0700
Subject: Re: [Lsr] Regarding OSPF Extended Prefix Range TLV usage for External/NSSA prefixes defined in RFC 8665
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, 19 Aug 2020 04:33:28 -0000

Hi Ketan,
Please find the response in line.
The IA flag in the OSPF Extended Prefix Range TLV does not indicate that the prefix-SID mapping advertised via it is for use for only intra or inter area prefixes. The mappings can be used for assignment of SIDs for ALL types of OSPF prefixes - regardless of the IA bit.
The IA flag is only to prevent looping during flooding of area-scoped LSAs with OSPF Extended Prefix Range TLVs when they are propagated across areas.

[V] As per RFC,
IA-Flag:  Inter-Area Flag.  If set, advertisement is of
               inter-area type.  An Area Border Router (ABR) that is
               advertising the OSPF Extended Prefix Range TLV between
               areas MUST set this bit.
I thought, when prefix Ranges with SID are advertised from Intra to Inter, we need to set this flag. So that it indicates the prefixes are of inter area type. Please let me know if my understanding is not correct.


When OSPF Extended Prefix Range TLVs are advertised using AS-scope, the NSSA notion does not apply for them and does not restrict their flooding into or from NSSA areas (or stub areas for that matter).
[V] If ASBR is part of NSSA, and if we redistributed Prefix SIDs learnt form other protocols or other instance of OSPF, and those prefixes are result of Range TLV  in that protocol, we can apply range in dest  ospf instance 

Thanks & Regards,
Veerendranath


-----Original Message-----
From: Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org> 
Sent: Tuesday, August 18, 2020 11:28 PM
To: Peter Psenak <ppsenak@cisco.com>; Veerendranatha Reddy V <veerendranatha.reddy.v@ericsson.com>; lsr@ietf.org
Subject: RE: [Lsr] Regarding OSPF Extended Prefix Range TLV usage for External/NSSA prefixes defined in RFC 8665

The IA flag in the OSPF Extended Prefix Range TLV does not indicate that the prefix-SID mapping advertised via it is for use for only intra or inter area prefixes. The mappings can be used for assignment of SIDs for ALL types of OSPF prefixes - regardless of the IA bit.

The IA flag is only to prevent looping during flooding of area-scoped LSAs with OSPF Extended Prefix Range TLVs when they are propagated across areas.

When OSPF Extended Prefix Range TLVs are advertised using AS-scope, the NSSA notion does not apply for them and does not restrict their flooding into or from NSSA areas (or stub areas for that matter).

I am not sure if that answers your question.

Thanks,
Ketan

-----Original Message-----
From: Lsr <lsr-bounces@ietf.org> On Behalf Of Peter Psenak
Sent: 18 August 2020 23:06
To: Veerendranatha Reddy V <veerendranatha.reddy.v=40ericsson.com@dmarc.ietf.org>; lsr@ietf.org
Subject: Re: [Lsr] Regarding OSPF Extended Prefix Range TLV usage for External/NSSA prefixes defined in RFC 8665

Veerendranath,

On 18/08/2020 16:40, Veerendranatha Reddy V wrote:
> Hi Authors, All,
> 
> OSPF Extended Prefix Range TLV defined in RFC 8665 has IA flag to 
> distinguish between Intra and Inter Area scope prefixes.
> 
> Whether any restrictions to not to use Prefix Range TLV for 
> external/NSSA prefixes ?

I don't see how you can use OSPF Extended Prefix Range TLV for NSSA, the usage of OSPF Extended Prefix Range TLV has only been defined in the context of RFC 8665.

thanks,
Peter


> 
> For External Prefixes, we can able to use  Prefix Range TLV  by using 
> LSA type (based on AS scope Opaque Type , so the TLV is for External
> Prefixes)
> 
> But If we need to use the Prefix Range TLV for NSSA prefixes (Type-7) 
> , which are in area scope, there is no flag/route-type field in this 
> TLV to distinguish between Intra or NSSA prefixes( as IA flag will not 
> be set anyway).
> 
> Thanks & Regards,
> 
> Veerendranath
> 

_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr