7:07 PM
>To: Shraddha Hegde ; Acee Lindem
>
>Cc: ospf@ietf.org
>Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
>
>Hi Shraddha,
>
>On 4/20/17, 12:46 AM, "Shraddha Hegde" wrote:
>
>>Hi Acee,
>>
>>The draft does not manda
Hi Christian,
See inline.
Thank you.
On 23 апр. 2017 г., 18:17 +0300, Christian Hopps , wrote:
>
> Alexander Okonnikov writes:
>
> > Hi Christian,
> >
> > See inline.
> >
> > Thank you.
> >
> > -- Best regards, Alexander Okonnikov
> >
> > On 21 апр. 2017 г., 18:36 +0300, Christian Hopps , wrote
Alexander Okonnikov writes:
> Hi Christian,
>
> See inline.
>
> Thank you.
>
> -- Best regards, Alexander Okonnikov
>
> On 21 апр. 2017 г., 18:36 +0300, Christian Hopps , wrote:
>
> Alexander Okonnikov writes:
>
> no argument about the need of area level flooding - Router LSA with
> the max
Hi Christian,
See inline.
Thank you.
-- Best regards, Alexander Okonnikov
On 21 апр. 2017 г., 18:36 +0300, Christian Hopps , wrote:
>
> Alexander Okonnikov writes:
>
> > > no argument about the need of area level flooding - Router LSA with
> > > the max metric will be flooded within the area.
Alexander Okonnikov writes:
>> no argument about the need of area level flooding - Router LSA with
>> the max metric will be flooded within the area.
>>
>> I have read the section 7.2 several times, but I still do not
>> understand what is the purpose of the Link-Overload sub-TLV there.
>> What
sense to refer this
>>draft in draft-ietf-ospf-link-overload-06 which is ready for WG last
>>call.
>
>I wasn’t suggesting to reference either document.
>
>Thanks,
>Acee
>
>
>>
>>Rgds
>>Shraddha
>>
>>-Original Message-
>>F
..
-Original Message-
From: Peter Psenak [mailto:ppse...@cisco.com]
Sent: Friday, April 21, 2017 1:38 PM
To: Shraddha Hegde ; Acee Lindem (acee)
Cc: ospf@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
please find my comments below:
The draft
]
Sent: Friday, April 21, 2017 1:38 PM
To: Shraddha Hegde ; Acee Lindem (acee)
Cc: ospf@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
please find my comments below:
The draft defines two mechanisms:
a) signaling the link overload to the neighbor. The
@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
please find my comments below:
The draft defines two mechanisms:
a) signaling the link overload to the neighbor. The purpose is to advertise the
link with max-metric from both directions.
b) flooding
isions/reviews and is ready for WG last call.
>
> Rgds
> Shraddha
>
>
> -Original Message-
> From: OSPF [mailto:ospf-boun...@ietf.org] On Behalf Of Acee Lindem
> (acee)
> Sent: Saturday, March 18, 2017 2:28 AM
> Cc: ospf@ietf.org
> Subject: Re: [OSPF] I-D
em
Cc: ospf@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
On 4/20/17, 12:46 AM, "Shraddha Hegde" wrote:
>Hi Acee,
>
>The draft does not mandate use of RFC 4203. There are no MUST
>statements associated with the recommendati
last call.
Rgds
Shraddha
-Original Message-
From: OSPF [mailto:ospf-boun...@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Saturday, March 18, 2017 2:28 AM
Cc: ospf@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha, et al,
With respect to section 4.
r.net]
Sent: 20 April 2017 13:27
To: Ketan Talaulikar Talaulikar (ketant) ; Acee Lindem (acee)
; Acee Lindem
Cc: ospf@ietf.org
Subject: RE: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Ketan,
OSPF link overload has relevance for TE based applications as well as non-TE
application
t;Rgds
>Shraddha
>
>-Original Message-
>From: Acee Lindem (acee) [mailto:a...@cisco.com]
>Sent: Thursday, April 20, 2017 4:02 AM
>To: Acee Lindem ; Shraddha Hegde
>
>Cc: ospf@ietf.org
>Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
>
>Hi
7 10:46 AM
To: Shraddha Hegde ; Acee Lindem (acee) ;
Acee Lindem
Cc: ospf@ietf.org
Subject: RE: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
The RFC 4203 describes the usage and application of TE LSAs for GMPLS/TE use
cases. The OSPF link overload RFC is independent
: ospf@ietf.org
Subject: RE: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha/Authors,
I would like to share the following comments and feedback on this draft.
1) I did not understand the motivation for the use of link-local scoped RI LSA
for the link-overload signalling when
bject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
The only non-editorial comment that I have is that the draft references RFC
4203 as the way to learn the remote interface ID on an unnumbered link
(https://www.ietf.org/id/draft-ppsenak-ospf-lls-interface-id-00.txt
addha Hegde ; Acee Lindem (acee) ;
Acee Lindem
Cc: ospf@ietf.org
Subject: RE: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
The RFC 4203 describes the usage and application of TE LSAs for GMPLS/TE use
cases. The OSPF link overload RFC is independent of TE and hence it
uthors of the draft believe that draft has undergone multiple
>>revisions/reviews and is ready for WG last call.
>>
>> Rgds
>> Shraddha
>>
>>
>> -Original Message-
>> From: OSPF [mailto:ospf-boun...@ietf.org] On Behalf Of Acee Lindem
>&g
Lindem (acee) ;
Acee Lindem
Cc: ospf@ietf.org
Subject: RE: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
The RFC 4203 describes the usage and application of TE LSAs for GMPLS/TE use
cases. The OSPF link overload RFC is independent of TE and hence it is a
concern that an
-Original Message-
From: OSPF [mailto:ospf-boun...@ietf.org] On Behalf Of Shraddha Hegde
Sent: 20 April 2017 10:17
To: Acee Lindem (acee) ; Acee Lindem
Cc: ospf@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Acee,
The draft does not mandate use of RFC 4203
Lindem (acee) [mailto:a...@cisco.com]
Sent: Thursday, April 20, 2017 4:02 AM
To: Acee Lindem ; Shraddha Hegde
Cc: ospf@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
The only non-editorial comment that I have is that the draft references RFC
4203 as the
[mailto:ospf-boun...@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: 20 April 2017 04:02
To: Acee Lindem ; Shraddha Hegde
Cc: ospf@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha,
The only non-editorial comment that I have is that the draft references
RFC
undergone multiple
>>revisions/reviews and is ready for WG last call.
>>
>> Rgds
>> Shraddha
>>
>>
>> -Original Message-
>> From: OSPF [mailto:ospf-boun...@ietf.org] On Behalf Of Acee Lindem
>>(acee)
>> Sent: Saturday, March 18, 2017 2:28 AM
>>
t;
> -Original Message-
> From: OSPF [mailto:ospf-boun...@ietf.org] On Behalf Of Acee Lindem (acee)
> Sent: Saturday, March 18, 2017 2:28 AM
> Cc: ospf@ietf.org
> Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
>
> Hi Shraddha, et al,
>
&
: OSPF [mailto:ospf-boun...@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Saturday, March 18, 2017 2:28 AM
Cc: ospf@ietf.org
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Hi Shraddha, et al,
With respect to section 4.1, I agree that matching link endpoints in
OSPFv2
Hi Shraddha, et al,
With respect to section 4.1, I agree that matching link endpoints in
OSPFv2 requires more information. However, this is a general problem and
the remote address should be a separate OSPFv2 Link Attribute LSA TLV
rather than overloading the link overload TLV ;^)
Thanks,
Acee
O
27 matches
Mail list logo
