Support as co-author.
Note that the substantive changes to the document were to remove the unused ERO
types - which was a widely supported change.
Les
> -Original Message-
> From: Lsr On Behalf Of Christian Hopps
> Sent: Monday, April 23, 2018 7:03 AM
> To:
Bravo!
Now LSR is a world class WG.
Thanx to Yingzhen for taking on this additional responsibility.
Les
From: Lsr On Behalf Of Acee Lindem (acee)
Sent: Monday, April 23, 2018 6:43 AM
To: lsr@ietf.org
Subject: [Lsr] LSR Working Group Secretary
All,
I’m delighted to
This just updates/corrects some references which was necessary as some of the
referenced content moved into a different draft.
Les
> -Original Message-
> From: Lsr On Behalf Of internet-dra...@ietf.org
> Sent: Thursday, April 19, 2018 9:42 AM
> To:
Support.
I am open to combining into one draft so long as the authors feel comfortable
that they can easily minimize the protocol specific text.
Les
From: Lsr On Behalf Of Acee Lindem (acee)
Sent: Tuesday, April 17, 2018 7:44 AM
To: lsr@ietf.org
Subject: [Lsr] LSR
are asking about.
Les
From: Uma Chunduri <uma.chund...@huawei.com>
Sent: Monday, April 16, 2018 3:28 PM
To: Les Ginsberg (ginsberg) <ginsb...@cisco.com>; Jeff Tantsura
<jefftant.i...@gmail.com>; Acee Lindem (acee) <a...@cisco.com>; Tony Li
<tony...@tony.li>
Cc: lsr@
I am not aware of any undisclosed IPR.
Les
From: Acee Lindem (acee)
Sent: Monday, April 09, 2018 12:39 PM
To: draft-ginsberg-lsr-isis-rfc7810...@ietf.org
Cc: lsr@ietf.org
Subject: IPR Call for "IS-IS Traffic Engineering (TE) Metric Extensions" -
draft-ginsberg-lsr-isis-rfc7810bis-00
a different flooding topology
from the one IGPs use today is required or we will have accomplished nothing.
Les
From: Lsr <lsr-boun...@ietf.org> On Behalf Of Robert Raszuk
Sent: Saturday, April 07, 2018 10:44 AM
To: Les Ginsberg (ginsberg) <ginsb...@cisco.com>
Cc: lsr@ietf.org; R
I think this discussion has already gone much too far in the direction of
customized flooding optimizations. Such is the nature of the engineering mind –
give us a problem to solve and we’ll come up with a plethora of solutions.
The right perspective (for me anyway) is this:
IGPs have been
orward way to identify the scope of the
content from the name - just using "-lsr-" for all documents is very
sub-optimal - and the fix for this is very easy.
Les
> -Original Message-
> From: t.petch <ie...@btconnect.com>
> Sent: Friday, April 06, 2018 3:43 AM
&
Chris -
> -Original Message-
> From: Christian Hopps <cho...@chopps.org>
> Sent: Thursday, April 05, 2018 7:32 AM
> To: Les Ginsberg (ginsberg) <ginsb...@cisco.com>
> Cc: Acee Lindem (acee) <a...@cisco.com>; lsr@ietf.org
> Subject: Re: [Lsr] FW: New Ver
-rfc7810bis” ??
Les
From: Jeff Tantsura <jefftant.i...@gmail.com>
Sent: Wednesday, April 04, 2018 1:58 PM
To: Acee Lindem (acee) <a...@cisco.com>; Tony Li <tony...@tony.li>; Les
Ginsberg (ginsberg) <ginsb...@cisco.com>
Cc: lsr@ietf.org
Subject: Re: [Lsr] FW: New Version
A strong +1 from me as well.
This is a clear example where the functional content is the same, but
differences exist in the encoding for reasons which are specific to each
protocol.
Les
> -Original Message-
> From: Lsr On Behalf Of Peter Psenak (ppsenak)
>
:33 PM
To: Qin Wu <sunse...@huawei.com>; David Ward (wardd) <wa...@cisco.com>; Spencer
Giacolone <spencer.giacal...@gmail.com>; Spencer Giacalone
<spencer.giacal...@gmail.com>; John Drake <ldr...@juniper.net>; Les Ginsberg
(ginsberg) <ginsb...@cisco.com>; Dav
I also believe the Errata should be accepted as is.
This will make IS-IS consistent with OSPF (RFC 7471) as well as the related
BGP-LS draft (draft-ietf-idr-te-pm-bgp).
Given there is evidence that implementations have differed in their
interpretations it seems important to note that we may
801 - 814 of 814 matches
Mail list logo