> people need to spend their time in deciding where is the boundary between the two areas
Oh then I perhaps completely missed the value and power of TTZ. It seems that in TTZ instead of careful planning of your abstractions the plan is to randomly create zones and see what happens - is this right reading of your explanation ? Many thx, R. On Wed, Sep 2, 2020 at 6:58 AM Huaimo Chen <huaimo.c...@futurewei.com> wrote: > Hi Tony, > > It seems that splitting L1 area A1 into two L1 areas A11 and A12 > cannot be automated without people's planning. Some people need to spend > their time in deciding where is the boundary between the two areas and > selecting a router in the backbone domain for Attach bit for one of the two > areas. These corresponds to step 1) and 3) for using Areas. > > Best Regards, > Huaimo > ------------------------------ > *From:* Tony Li <tony1ath...@gmail.com> on behalf of tony...@tony.li < > tony...@tony.li> > *Sent:* Wednesday, September 2, 2020 12:09 AM > *To:* Huaimo Chen <huaimo.c...@futurewei.com> > *Cc:* Les Ginsberg <ginsb...@cisco.com>; Les Ginsberg (ginsberg) > <ginsberg=40cisco....@dmarc.ietf.org>; Acee Lindem (acee) <acee= > 40cisco....@dmarc.ietf.org>; lsr@ietf.org <lsr@ietf.org> > *Subject:* Re: [Lsr] LSR WG Adoption Poll for "IS-IS Topology-Transparent > Zone" - draft-chen-isis-ttz-11.txt > > > Hi Huaimo, > > Assume that a big L1 area (say Area A1) is connected to backbone > domain. > Let us compare TTZ and Areas for scalability. > > Using TTZ, we need two steps below: > 1) configure a piece of Area A1, named P1, as a zone; and > 2) transfer P1 to a virtual node using one command or two. > > Using Areas, we need four steps below to split Area A1 into two L1 > areas A11 and A12: > 1) configure the edges between A11 and A12 as L2/L1 to backbone domain; > 2) add/configure a new area address on the routers in target Area A12; > 3) configure Attach bit for A11 or A12; and > 4) delete the old area address from the routers in Area A12. > > Using TTZ is simpler than using Areas. > > > > I’m not quite sure I follow you. Are you arguing that simplicity is > achieved through the minimum number of configuration steps? > > If so, I’d like to introduce you to Arista CVP, our management platform, > where all of this can be easily automated: 1 step. > > Tony > > > _______________________________________________ > 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
