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

Peter Psenak <ppsenak@cisco.com> Wed, 19 August 2020 08:09 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 4FEEA3A110A for <lsr@ietfa.amsl.com>; Wed, 19 Aug 2020 01:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.55
X-Spam-Level:
X-Spam-Status: No, score=-10.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.949, 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 rmMg3FFUuIXE for <lsr@ietfa.amsl.com>; Wed, 19 Aug 2020 01:09:07 -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 37A983A1113 for <lsr@ietf.org>; Wed, 19 Aug 2020 01:09:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3026; q=dns/txt; s=iport; t=1597824547; x=1599034147; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=TrTNYmQZcH0YLLozlUfEbGGBe4KNc4/Vm4A9i3ujb+w=; b=Rs0G2X1BGP55Ml5Jd32k6LbaSZbs3fVbxGeK3SX6dUeAXZbZN/Qi4uxq PUeR11AMOKWD8nQZ043Z3ufYegN2yIPUHpekrS4jTyO5RD+jOhldUWplV 0bdUCNCOa/X2AblojjQOJJSTgc2lMY7v5lykAvll0XVcZHuESXX+3V+A8 o=;
X-IPAS-Result: A0AaAAAa3Txf/xbLJq1fGgEBAQEBAQEBAQEDAQEBARIBAQEBAgIBAQEBQIE5AgEBAQELAYNtASASLIQ3iQGHfSWcFwsBAQEOLwQBAYRMAoIhJTcGDgIDAQEBAwIDAQEBAQUBAQECAQYEbYVohXEBAQEDASMPAQVGBwQLEQQBAQECAh8HAgJPCAYBDAYCAQGDIoJdILBvdoEyhVKDZoFAgQ4qAY05gUE/gREnDIIvLj6BBIFYBIR0gmAEti+CbIMMlwkFBwMekWaOPZI7n2iBaSSBVzMaCBsVgyRQGQ2OKwwLFI4SPwMwAjUCBgEJAQEDCZBeAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.76,330,1592870400"; d="scan'208";a="26435711"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Aug 2020 08:09:03 +0000
Received: from [10.60.140.51] (ams-ppsenak-nitro2.cisco.com [10.60.140.51]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTP id 07J8928u003664; Wed, 19 Aug 2020 08:09:03 GMT
To: Veerendranatha Reddy V <veerendranatha.reddy.v=40ericsson.com@dmarc.ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
References: <DB7PR07MB3914AA1BF15E141673DF1E11BB5C0@DB7PR07MB3914.eurprd07.prod.outlook.com> <bb8d3f97-ec52-a91d-c3d6-896f86f498c1@cisco.com> <DB7PR07MB391403D0C9880296BD80D692BB5D0@DB7PR07MB3914.eurprd07.prod.outlook.com> <35fa1a89-0512-051b-a4d5-655fcaa8d7f3@cisco.com> <DB7PR07MB3914052EB5D289B2DD96917DBB5D0@DB7PR07MB3914.eurprd07.prod.outlook.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <22dc4c32-1d81-4665-1568-bfa165e9462f@cisco.com>
Date: Wed, 19 Aug 2020 10:09:02 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <DB7PR07MB3914052EB5D289B2DD96917DBB5D0@DB7PR07MB3914.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.60.140.51, ams-ppsenak-nitro2.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/9QSuzBbirKwiTpfn1N8GxkIw6a8>
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 08:09:09 -0000

Veerendranath,

On 19/08/2020 10:03, Veerendranatha Reddy V wrote:
> Hi Peter,
> It is not related to SRMS.
> If there exist ISIS/OSPF or two instances of OSPF in same device, and all are supporting ST, then I can redistribute SR Prefix information to OSPF from other OSPF instance or from ISIS.

yes, you can.

> In this case, I may use range TLV to reduce the number of Prefix TLVs, by using  Range TLV, if prefixes and SID are able to convert to Range TLV.

you would have to generate one somewhere (on ABR?), but it would not be 
of NSSA type.

Peter


> 
> Thanks & Regards,
> Veerendranath
> 
> 
> -----Original Message-----
> From: Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>
> Sent: Wednesday, August 19, 2020 1:23 PM
> To: 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
> 
> Hi Veerendranatha,
> 
> On 19/08/2020 06:23, Veerendranatha Reddy V wrote:
>> Hi Peter,
>> While redistributing prefix Sid for the prefixes from other protocols (Ex: from ISIS or other OSPF instances), we can consider as range TLV for the prefixes which are advertised in the range TLV in that protocol.
> 
> I don't follow. Are you talking about redistribution of SRMS advertisement between protocols? Such thing has not been defined.
> 
> thanks,
> Peter
> 
> 
>> If it is NSSA, then we need to advertise these redistributed prefixes as area scope, so Range TLV also need to be part of area scope Opaque LSA.
>>
>> Thanks & Regards,
>> Veerendranath
>>
>> -----Original Message-----
>> From: Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>
>> Sent: Tuesday, August 18, 2020 11:06 PM
>> To: 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
>>
>> 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
>>>
>>
>>
>>
> 
> 
>