Subject: [Lsr] Fwd: New Version Notification for draft-li-lsr-isis-area-proxy-01.txt

From: [email-masked]
Date: Tue, 24 Dec 2019 16:36:11 -0800

Ho ho ho!

An update for you:
- Added MT support.
- Added SR support.
- Many little clarifications and tweaks.

Comments and questions to the authors, please.

Happy holidays,
Tony

p.s. Yes, it’s still a “hack”.  No, I still haven’t seen anything better.

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-li-lsr-isis-area-proxy-01.txt
> Date: December 24, 2019 at 4:32:12 PM PST
> To: "Yunxia Chen" <[email-masked]>, "Sarah Chen" <[email-masked]>, "Tony Li" <[email-masked]>
> 
> 
> A new version of I-D, draft-li-lsr-isis-area-proxy-01.txt
> has been successfully submitted by Tony Li and posted to the
> IETF repository.
> 
> Name:		draft-li-lsr-isis-area-proxy
> Revision:	01
> Title:		Area Proxy for IS-IS
> Document date:	2019-12-24
> Group:		Individual Submission
> Pages:		17
> URL:            https://www.ietf.org/internet-drafts/draft-li-lsr-isis-area-proxy-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-li-lsr-isis-area-proxy/
> Htmlized:       https://tools.ietf.org/html/draft-li-lsr-isis-area-proxy-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-li-lsr-isis-area-proxy
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-li-lsr-isis-area-proxy-01
> 
> 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.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
>