se.
>
> Apologies for the noise.
>
> Les
>
>> -Original Message-
>> From: Acee Lindem
>> Sent: Monday, March 4, 2024 12:56 PM
>> To: Les Ginsberg (ginsberg)
>> Cc: Tony Przygienda ; lsr
>> Subject: Re: [Lsr] bunch comments on https://data
Tony Przygienda ; lsr
> Subject: Re: [Lsr] bunch comments on https://datatracker.ietf.org/doc/draft-
> ietf-lsr-ospf-admin-tags
>
> Hi Les,
>
> > On Mar 4, 2024, at 15:48, Les Ginsberg (ginsberg)
> wrote:
> >
> > Acee -
> >
> > Consider two ABRs propaga
Les
>
>
>> -Original Message-
>> From: Acee Lindem
>> Sent: Monday, March 4, 2024 12:12 PM
>> To: Les Ginsberg (ginsberg)
>> Cc: Tony Przygienda ; lsr
>> Subject: Re: [Lsr] bunch comments on https://datatracker.ietf.org/doc/draft-
>> ietf-
rzygienda ; lsr
> Subject: Re: [Lsr] bunch comments on https://datatracker.ietf.org/doc/draft-
> ietf-lsr-ospf-admin-tags
>
> Hi Les,
>
> > On Mar 3, 2024, at 11:41 PM, Les Ginsberg (ginsberg)
> wrote:
> >
> > Not overly complicate things...
> >
> > The requ
>
> Les
>
>
>> -Original Message-
>> From: Acee Lindem
>> Sent: Friday, March 1, 2024 10:27 AM
>> To: Tony Przygienda
>> Cc: Les Ginsberg (ginsberg) ; lsr
>> Subject: Re: [Lsr] bunch comments on https://datatracker.ietf.org/do
> Sent: Friday, March 1, 2024 10:27 AM
> To: Tony Przygienda
> Cc: Les Ginsberg (ginsberg) ; lsr
> Subject: Re: [Lsr] bunch comments on https://datatracker.ietf.org/doc/draft-
> ietf-lsr-ospf-admin-tags
>
> At the risk of complication, I've added text to clarify the o
y what it means it doesn't carry one. No
>>> biggie, I just edged onto this when reading it ...
>>> >
>>> > if authors are not interested in making the spec tighter, closing
>>> possible holes then I just pipe out of course ...
>>> >
>>> >
>> >
>> > -- tony
>> >
>> > On Thu, Feb 29, 2024 at 8:01 PM Les Ginsberg (ginsberg) <
>> ginsb...@cisco.com> wrote:
>> > Tony –
>> > In the spirit of a friendly discussion…
>> > From: Lsr On Behalf Of Tony Przygienda
&g
> On Thu, Feb 29, 2024 at 8:01 PM Les Ginsberg (ginsberg) <
> ginsb...@cisco.com> wrote:
> > Tony –
> > In the spirit of a friendly discussion…
> > From: Lsr On Behalf Of Tony Przygienda
> > Sent: Thursday, February 29, 2024 10:33 AM
> > To: Acee Lindem
tony
>
> On Thu, Feb 29, 2024 at 8:01 PM Les Ginsberg (ginsberg)
> wrote:
> Tony –
> In the spirit of a friendly discussion…
> From: Lsr On Behalf Of Tony Przygienda
> Sent: Thursday, February 29, 2024 10:33 AM
> To: Acee Lindem
> Cc: lsr
> Subject: Re: [Lsr] bunch
> *Cc:* lsr
> *Subject:* Re: [Lsr] bunch comments on
> https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-admin-tags
>
>
>
> 1. you can easily rectify by saying, if you have tags for same prefix
> from multiple nodes you prefere lowest router ID or maybe "sort on ro
Tony –
In the spirit of a friendly discussion…
From: Lsr On Behalf Of Tony Przygienda
Sent: Thursday, February 29, 2024 10:33 AM
To: Acee Lindem
Cc: lsr
Subject: Re: [Lsr] bunch comments on
https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-admin-tags
1. you can easily rectify by saying
1. you can easily rectify by saying, if you have tags for same prefix from
multiple nodes you prefere lowest router ID or maybe "sort on router id and
then interleave" or something. depending how much of fully fledged
specification you want here
2. we miss each other. I just say this sub-TLV
Hi Tony,
> On Feb 28, 2024, at 2:01 AM, Tony Przygienda wrote:
>
> hey Acee, inline
>
>
> On Wed, Feb 28, 2024 at 3:30 AM Acee Lindem wrote:
> Hi Tony,
>
> Thanks for the review.
>
>> On Feb 27, 2024, at 04:51, Tony Przygienda wrote:
>>
>> Reading the draft quickly, here's bunch of
hey Acee, inline
On Wed, Feb 28, 2024 at 3:30 AM Acee Lindem wrote:
> Hi Tony,
>
> Thanks for the review.
>
> On Feb 27, 2024, at 04:51, Tony Przygienda wrote:
>
> Reading the draft quickly, here's bunch of observations
>
> "
>
>An OSPF router supporting this specification MUST be able to
Hi Tony,
Thanks for the review.
> On Feb 27, 2024, at 04:51, Tony Przygienda wrote:
>
> Reading the draft quickly, here's bunch of observations
>
> "
>
>An OSPF router supporting this specification MUST be able to
>advertise and interpret at least one 32-bit tag for all type of
>
Reading the draft quickly, here's bunch of observations
"
An OSPF router supporting this specification MUST be able to
advertise and interpret at least one 32-bit tag for all type of
prefixes. An OSPF router supporting this specification MAY be able
to advertise and propagate
17 matches
Mail list logo
