Hi Tony & WG,

The changes which went into sections 4.3.2 & 4.4.13 do address my
suggestions made earlier to the list. So I do support the current version.

With the option of having a configurable area prefix this delivers quite a
powerful extension.

Also the current text says:

"Other uses of the Area SID are outside the scope of this document. "

Maybe we could state instead:

Other uses of the Area SID and area prefix are outside the scope of this
document.

Many thx,
R.


On Mon, Aug 24, 2020 at 7:02 PM <tony...@tony.li> wrote:

>
> Hi folks,
>
> This updated draft has been published for a few weeks now.  We would like
> to solicit your opinion on this.  In particular, we have changed the
> encoding of the Area SID.  Do you find this encoding adequate and
> appropriate?
>
> Thanks,
> Tony
>
>
> Begin forwarded message:
>
> *From: *internet-dra...@ietf.org
> *Subject: **I-D Action: draft-ietf-lsr-isis-area-proxy-03.txt*
> *Date: *August 5, 2020 at 1:17:39 PM PDT
> *To: *<i-d-annou...@ietf.org>
> *Cc: *lsr@ietf.org
> *Reply-To: *internet-dra...@ietf.org, lsr@ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Link State Routing WG of the IETF.
>
>        Title           : Area Proxy for IS-IS
>        Authors         : Tony Li
>                          Sarah Chen
>                          Vivek Ilangovan
>                          Gyan S. Mishra
> Filename        : draft-ietf-lsr-isis-area-proxy-03.txt
> Pages           : 19
> Date            : 2020-08-05
>
> Abstract:
>   Link state routing protocols have hierarchical abstraction already
>   built into them.  However, when lower levels are used for transit,
>   they must expose their internal topologies to each other, leading to
>   scale issues.
>
>   To avoid this, this document discusses extensions to the IS-IS
>   routing protocol that would allow level 1 areas to provide transit,
>   yet only inject an abstraction of the level 1 topology into level 2.
>   Each level 1 area is represented as a single level 2 node, thereby
>   enabling greater scale.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-area-proxy/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-lsr-isis-area-proxy-03
> https://datatracker.ietf.org/doc/html/draft-ietf-lsr-isis-area-proxy-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-lsr-isis-area-proxy-03
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> _______________________________________________
> I-D-Announce mailing list
> i-d-annou...@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to