Hi Robert, inlines

From: Lsr <[email protected]> on behalf of Robert Raszuk <[email protected]>
Date: Monday, August 28, 2023 at 12:00 PM
To: "Hassan, Shehzad" <[email protected]>, Daniel Bernier 
<[email protected]>
Cc: lsr <[email protected]>, "[email protected]" 
<[email protected]>
Subject: [EXT]Re: [Lsr] Working Group Adoption of "IGP Unreachable Prefix 
Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft 
name)

Hi Shehzad & Daniel,

I support this work as it is key for summarization in an SRv6/IPv6 network.

Are you not going to advertise and leak across your IGP domain any of the SRv6 
extensions as described in https://datatracker.ietf.org/doc/rfc9352/ for the 
PEs ?
[DV] No, there’s no need to leak and advertise. For an SRv6 network, we are 
summarizing locators and loopback (should be derived from locator 0). This 
makes the routing domain “opaque”.

And if you do, is there still some use case for UPA ?

Perhaps I am missing something but how would those extensions survive 
summarization ?


Thx,
Robert
Cheers,
Dan

> On Aug 23, 2023, at 4:07 PM, Acee Lindem 
> <[email protected]<mailto:[email protected]>> wrote:
>
> LSR Working Group,
>
> This begins the working group adoption call for “IGP Unreachable Prefix 
> Announcement” - draft-ppsenak-lsr-igp-unreach-prefix-announce-04.
> Please indicate your support or objection on this list prior to September 
> 7th, 2023.
>
> Thanks,
> Acee
> ------------------------------------------------------------------------------
> External Email: Please use caution when opening links and attachments / 
> Courriel externe: Soyez prudent avec les liens et documents joints
>
_______________________________________________
Lsr mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/lsr
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to