Re: [Lsr] LSR WG Adoption Poll for "IS-IS Topology-Transparent Zone" - draft-chen-isis-ttz-11.txt

[Huaimo Chen <[e-mail]>]

Hi Robert,

>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 ?

[HC]: TTZ provides users flexibility to define a zone and abstract the zone to a single node for scalability. Users can define a zone (a block of an area) and the zone can be any block of the area that users decide. Thus, using TTZ seems simpler than using Areas for scalability. It uses less planning effort and less configurations.
For example, given a big L1 area (say area A1) connected to backbone, users can define a zone in area A1 and abstract it to a node for scalability. When area A1 is split into two L1 areas A11 and A12 using Areas, the planning effort includes two parts: 1) determining the boundary of A11 and A12 and 2) selecting a router for Attach bit. Since users can define any block of area A1 as a zone, the block for A11 can be defined as a zone and abstracted to a single node.
The planning effort using TTZ is just the first part of the planning effort using Areas, and is less.
For less configurations using TTZ, refer to
https://mailarchive.ietf.org/arch/msg/lsr/NxNJRUulSnGaR5PNBJv5x1kxUTw/

Best Regards,
Huaimo
________________________________
From: Robert Raszuk <[e-mail]>
Sent: Wednesday, September 2, 2020 4:53 AM
To: Huaimo Chen <[e-mail]>
Cc: [e-mail] <[e-mail]>; Les Ginsberg (ginsberg) <ginsberg=[e-mail]>; Les Ginsberg <[e-mail]>; [e-mail] <[e-mail]>; Acee Lindem (acee) <acee=[e-mail]>
Subject: Re: [Lsr] LSR WG Adoption Poll for "IS-IS Topology-Transparent Zone" - draft-chen-isis-ttz-11.txt


> 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 <[e-mail]<mailto:[e-mail]>> 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 <[e-mail]<mailto:[e-mail]>> on behalf of [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Sent: Wednesday, September 2, 2020 12:09 AM
To: Huaimo Chen <[e-mail]<mailto:[e-mail]>>
Cc: Les Ginsberg <[e-mail]<mailto:[e-mail]>>; Les Ginsberg (ginsberg) <ginsberg=[e-mail]<mailto:[e-mail]>>; Acee Lindem (acee) <acee=[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
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
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/lsr<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flsr&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C346e8ba1b8b140e581ab08d84f1db372%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637346336293628016&sdata=0f4iui6ePeVSWMnsved8IdE7zKpKkWm0veMoHOcSuZ4%3D&reserved=0>