The Working Group last call has completed and we have received IPR responses
from all the authors. We have some comments from the Routing Directorate review
on the corresponding IS-IS draft. I will hold off requesting publication in
case the comments are also applicable to this version. Thanks,
t;Signaling Entropy Label
Capability and Entropy Readable Label-stack Depth Using OSPF" -
draft-ietf-ospf-mpls-elc-08
>Because the intra-area link topology is not exposed across areas or to other
>protocols.
Agreed Acee.
But just looking this again then:
Not really clear why ELC is
>Because the intra-area link topology is not exposed across areas or to other
>protocols.
Agreed Acee.
But just looking this again then:
1. Not really clear why ELC is required in Section 4, when it’s confirmed
from Stephane’s email (Sept 4th 2019) ERLD covers both reading + doing and
Hi Uma,
From: Uma Chunduri
Date: Tuesday, September 10, 2019 at 2:43 PM
To: Acee Lindem , "lsr@ietf.org"
Cc: "m...@ietf.org" , "lsr-...@ietf.org" ,
"draft-ietf-ospf-mpls-...@ietf.org"
Subject: RE: Working Group Last Call for "Signaling Entropy Label Capability
and Entropy Readable
Support.
One question to authors:
On E bit in section 4: The motivation seems to extend this in Prefix
attributes is for inter-area consideration and advertised per every local host
prefix (link) .
Is there any specific reason why link
MSD is not
Hi Acee,
support as co-author.
thanks,
Peter
On 30/08/2019 21:42, Acee Lindem (acee) wrote:
We’ve gone through a number of iterations with these ELC drafts and I
believe they are ready and meets all the use case requirements. Note
that “Entropy Label for Spring tunnels” –
acee)
Sent: Friday, August 30, 2019 9:42 PM
To: lsr@ietf.org
Cc: m...@ietf.org; lsr-...@ietf.org; draft-ietf-ospf-mpls-...@ietf.org
Subject: [Lsr] Working Group Last Call for "Signaling Entropy Label Capability
and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08
ntropy Label
> Capability and Entropy Readable Label-stack Depth Using OSPF" -
> draft-ietf-ospf-mpls-elc-08
>
> We’ve gone through a number of iterations with these ELC drafts and I believe
> they are ready and meets all the use case requirements. Note that “Entropy
> L
; lsr-...@ietf.org; draft-ietf-ospf-mpls-...@ietf.org
Subject: [Lsr] Working Group Last Call for "Signaling Entropy Label Capability
and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08
We’ve gone through a number of iterations with these ELC drafts and
, 2019 at 3:42 PM
To: "lsr@ietf.org"
Cc: "m...@ietf.org" , "lsr-...@ietf.org" ,
"draft-ietf-ospf-mpls-...@ietf.org"
Subject: [Lsr] Working Group Last Call for "Signaling Entropy Label Capability
and Entropy Readable Label-stack Depth Using OSPF"
We’ve gone through a number of iterations with these ELC drafts and I believe
they are ready and meets all the use case requirements. Note that “Entropy
Label for Spring tunnels” – draft-ietf-mpls-spring-entropy-label-12 is on the
RFC editor’s queue.
This begins a two week last call for the
11 matches
Mail list logo
