Hi Veerendranatha,
Please check inline below with [KT2]
-----Original Message-----
From: Veerendranatha Reddy V
<veerendranatha.reddy.v=40ericsson....@dmarc.ietf.org>
Sent: 19 August 2020 13:07
To: Ketan Talaulikar (ketant) <ket...@cisco.com>; Peter Psenak (ppsenak)
<ppse...@cisco.com>; lsr@ietf.org
Subject: RE: [Lsr] Regarding OSPF Extended Prefix Range TLV usage for
External/NSSA prefixes defined in RFC 8665
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.
[KT] What is says is "the prefix range advertisement is of type inter-area or
intra-area" (think of it as somewhat equivalent of the D bit in ISIS when
leaking across levels). That does not mean that the advertised mappings need to
be used for only for intra or inter area prefixes respectively.
[V] When we receive the range TLV received at ABR, while it is originating
opaque LSA for that range TLV across the other areas, whether it is required to
set IA or not?
[KT2] Yes - please check the RFC8665 Sec 4 - right after where the IA flag is
described.
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
[KT] I do not follow above statement - can you please try to
elaborate/re-phrase?
[V] When redistributing Prefix SID information to NSSA from other protocols ,
it may possible to generate Range TLV, if multiple prefixes can be aggregated
as range., instead of generating extended Prefix TLV for each prefix. So while
originating this range TLV, how we can differentiate whether it is intra Scope
or NSSA scope. So that when it is received at ABR, he will consider to
translate to inter area Opaque or External Opaque for that range.
[KT2] I believe Peter answered and clarified this part. There is no notion of
NSSA area or NSSA-scope flooding for the Extended Prefix Range TLV.
Thanks,
Ketan
Thanks & Regards,
Veerendranath
-----Original Message-----
From: Ketan Talaulikar (ketant) <ketant=40cisco....@dmarc.ietf.org>
Sent: Wednesday, August 19, 2020 10:27 AM
To: Veerendranatha Reddy V <veerendranatha.redd...@ericsson.com>; Peter Psenak
(ppsenak) <ppse...@cisco.com>; lsr@ietf.org
Subject: RE: [Lsr] Regarding OSPF Extended Prefix Range TLV usage for
External/NSSA prefixes defined in RFC 8665
Hi Veerendranatha,
Please check inline below.
-----Original Message-----
From: Veerendranatha Reddy V
<veerendranatha.reddy.v=40ericsson....@dmarc.ietf.org>
Sent: 19 August 2020 10:03
To: Ketan Talaulikar (ketant) <ket...@cisco.com>; Peter Psenak (ppsenak)
<ppse...@cisco.com>; lsr@ietf.org
Subject: RE: [Lsr] Regarding OSPF Extended Prefix Range TLV usage for
External/NSSA prefixes defined in RFC 8665
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.
[KT] What is says is "the prefix range advertisement is of type inter-area or
intra-area" (think of it as somewhat equivalent of the D bit in ISIS when
leaking across levels). That does not mean that the advertised mappings need to
be used for only for intra or inter area prefixes respectively.
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 [KT] I
do not follow above statement - can you please try to elaborate/re-phrase?
Thanks,
Ketan
Thanks & Regards,
Veerendranath
-----Original Message-----
From: Ketan Talaulikar (ketant) <ketant=40cisco....@dmarc.ietf.org>
Sent: Tuesday, August 18, 2020 11:28 PM
To: Peter Psenak <ppse...@cisco.com>; Veerendranatha Reddy V
<veerendranatha.redd...@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-boun...@ietf.org> On Behalf Of Peter Psenak
Sent: 18 August 2020 23:06
To: Veerendranatha Reddy V
<veerendranatha.reddy.v=40ericsson....@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
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
