I have read this draft and support its publication as an Informational RFC.
Thanks,
Donald
===
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
2386 Panoramic Circle, Apopka, FL 32703 USA
d3e...@gmail.com
On Mon, Jan 8, 2024 at 5:50 PM Acee Lindem wrote:
> This
Hi Les,
See below at
On Wed, Mar 3, 2021 at 3:47 PM Les Ginsberg (ginsberg)
wrote:
> Donald -
>
> Thanx for your careful review and your support of the draft.
> Replies inline.
>
> > -Original Message-
> > From: Lsr On Behalf Of Donald Eastlake
> > S
Hi,
I have a few comments. Sorry to send these so late in the process. I
support publication of this draft regardless of whether any action is
taken on my comments.
1. Since there are non-allocation actions, I suggest that the first
sentence of Section 6 be more like "IANA is requested to take
Hi,
Here are some comments on draft-ietf-lsr-isis-ttz. These are not in
any particular order.
Section 1.1, the requirements language section should be updated to the
current wording that references RFC 8174.
Towards the end of Section 4.1.3, I'm not sure exactly what an "LS ID"
is and what it
I support working group adoption of this draft as experimental.
Thanks,
Donald
===
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
2386 Panoramic Circle, Apopka, FL 32703 USA
d3e...@gmail.com
On Tue, Aug 18, 2020 at 10:17 AM Acee Lindem (acee) wrote:
>
>
> Based
I support adoption of the IS-IS TTZ draft.
It seems more flexible and capable although some
editorial/nomenclature improvements in the draft would be good. I will
send some more detailed suggestions to the authors.
Thanks,
Donald
===
Donald E. Eastlake 3rd
Hi,
On Sat, Mar 24, 2018 at 6:57 AM, Robert Raszuk wrote:
> Dear Authors,
>
> Let me just ask one little question
>
> It seems that ISIS protocol already meets a "Link State Over Ethernet"
> definition so why to invent anything new here ?
My thought also.
> If you don't