x-annou...@ietf.org
Cc: lsr
Subject: Re: [Lsr] Comments on draft-ppsenak-lsr-igp-ureach-prefix-announce
[External Email. Be cautious of content]
Hi authors, WG,
I also have some comments which aligns with Ketan's first and third points as
below:
Firstly, both RFC 5305 and 5308 say that:
&quo
-ppsenak-lsr-igp-ureach-prefix-announce
Hello Authors,
Sharing some comments upfront on this draft given the packed LSR agenda.
1) There is currently no change in protocol encoding (see also further
comment), however, there are protocol procedures at the ABR being specified
using normative language
Hi Peter, Ketan,
See one inline.
On 7/28/22, 10:08 AM, "Lsr on behalf of Peter Psenak" wrote:
Hi Ketan,
On 28/07/2022 02:27, Ketan Talaulikar wrote:
> Hello Authors,
>
> Sharing some comments upfront on this draft given the packed LSR agenda.
>
> 1) There is
Hi Ketan,
On 28/07/2022 02:27, Ketan Talaulikar wrote:
Hello Authors,
Sharing some comments upfront on this draft given the packed LSR agenda.
1) There is currently no change in protocol encoding (see also further
comment), however, there are protocol procedures at the ABR being
specified
Hello Authors,
Sharing some comments upfront on this draft given the packed LSR agenda.
1) There is currently no change in protocol encoding (see also further
comment), however, there are protocol procedures at the ABR being specified
using normative language. Specifically, the text related to
