Re: [Lsr] Enhancement related to Area Leader Sub-TLV

Huaimo Chen <hchen@futurewei.com> Wed, 29 May 2019 05:02 UTC

Return-Path: <hchen@futurewei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBEA1200F7 for <lsr@ietfa.amsl.com>; Tue, 28 May 2019 22:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UISqGkumMyTu for <lsr@ietfa.amsl.com>; Tue, 28 May 2019 22:02:13 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-eopbgr820115.outbound.protection.outlook.com [40.107.82.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3FC5120047 for <lsr@ietf.org>; Tue, 28 May 2019 22:02:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SZX1Pmv5XxUWDM9k+6J+pPsRGNYyOiEicxqRHz9T4sE=; b=B/8N9A1tssq86KNJhYR4e+U1wwW3Ut8g5dUfc6A32OH/bLM8cxdJNZ4qXBtDzbs0eK2HCxbl+XAX2BQXg8erMNI99GWYe1+YT1klzfLi7uM8MGXpmbLHaJ20AKGlWdgNeHDoowu7nft8KmGRzukRM6MF/UC2D87CQxaK1X7JbfU=
Received: from MN2PR13MB3470.namprd13.prod.outlook.com (10.255.237.83) by MN2PR13MB3440.namprd13.prod.outlook.com (10.255.237.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.8; Wed, 29 May 2019 05:02:08 +0000
Received: from MN2PR13MB3470.namprd13.prod.outlook.com ([fe80::b125:6fc1:69df:68b1]) by MN2PR13MB3470.namprd13.prod.outlook.com ([fe80::b125:6fc1:69df:68b1%7]) with mapi id 15.20.1943.015; Wed, 29 May 2019 05:02:08 +0000
From: Huaimo Chen <hchen@futurewei.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Enhancement related to Area Leader Sub-TLV
Thread-Index: AQHVEnBx76G1LJb8GEmtrIB+eKBaE6Z6wX6AgAUXy1qAANM6gIAA4fAN
Date: Wed, 29 May 2019 05:02:08 +0000
Message-ID: <MN2PR13MB3470038A8417F66CD76FD25BA31F0@MN2PR13MB3470.namprd13.prod.outlook.com>
References: <MN2PR13MB3470FB2091E28D9EB98A230AA3020@MN2PR13MB3470.namprd13.prod.outlook.com>, <55DE9C76-90FB-4EF1-B64B-DDED154F15C9@tony.li> <MN2PR13MB3470011BC47D57EDF1DFB19AA31E0@MN2PR13MB3470.namprd13.prod.outlook.com>, <BYAPR11MB36381BDE7F6F49C03AA595F2C11E0@BYAPR11MB3638.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB36381BDE7F6F49C03AA595F2C11E0@BYAPR11MB3638.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hchen@futurewei.com;
x-originating-ip: [12.111.81.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 47e1abc8-58ca-4cb7-bec1-08d6e3f2cd2c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB3440;
x-ms-traffictypediagnostic: MN2PR13MB3440:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR13MB34405D6D104DEFB5C085A706A31F0@MN2PR13MB3440.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0052308DC6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(39850400004)(136003)(376002)(366004)(189003)(199004)(81166006)(81156014)(91956017)(476003)(966005)(7696005)(76116006)(68736007)(76176011)(1015004)(74316002)(446003)(8676002)(14454004)(7736002)(66946007)(8936002)(86362001)(5024004)(11346002)(6916009)(486006)(6506007)(6246003)(99286004)(53946003)(73956011)(4326008)(26005)(53936002)(53546011)(6606003)(186003)(25786009)(102836004)(52536014)(5660300002)(236005)(64756008)(229853002)(66476007)(66446008)(6116002)(6306002)(54896002)(66556008)(71190400001)(316002)(2906002)(33656002)(3846002)(256004)(508600001)(606006)(9686003)(561944003)(66066001)(6436002)(19627405001)(55016002)(71200400001)(579004)(559001); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3440; H:MN2PR13MB3470.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: TjdfEhZpzX3F0pSQjxuNjmiNtWLgYKcbG5OknYrcd2w7HJPL5qsVWY2KV6eD65VRzjMN9gOX6viXlmyyl+xb04RF1Wic34A4mNgpQZ52iWgkopUQ+zpiN6xVzXErP+pntfP9/sD+1AdGniTuhErwaMtLEq+wGjfts0N3TJSmFI2sNRunpArYK3OgMPzjibPF8urvUlktSSpJ3ESWvXs3+KkIKm9qFATt/Qz+FatPyRltvcZyyTi3cw+ZsvHI8uNgloas65EUBMwWOcWHm+ofS2vaQS+DWZ6F6Y1wq4NuBACOcn6uFF4Z+XmNZ6ZqtFXdUq0VwEqMoFYFgOGRYflEuBpO2DaBV+kZc61tApB85TNlg929rfWzi2m7HOjsGJ8lxgU6tHCTsXX4Zd6l6PDB/fGb+wtN6zlUnJKhKigvhOo=
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3470038A8417F66CD76FD25BA31F0MN2PR13MB3470namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 47e1abc8-58ca-4cb7-bec1-08d6e3f2cd2c
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2019 05:02:08.0997 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hchen@futurewei.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3440
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/GqJ3ryXKOLvvtGiipk7EJHjtDgw>
Subject: Re: [Lsr] Enhancement related to Area Leader Sub-TLV
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2019 05:02:17 -0000

Hi Les,


    It seems that it is OK for only the leader advertises Area Leader sub-TLV. After the old/current leader is down, a new leader will be elected and the new leader will advertises Area Leader sub-TLV.


    After moving priority (one byte) from Area Leader sub-TLV to Dynamic Flooding Sub-TLV, the saving on space when every node advertises a priority is (N-1)*S1 – N, where N is the number of nodes in the area, S1 is the size of Area Leader Sub-TLV. S1 is 4 in IS-IS; S1 is 8 in OSPF.  For N = 1000 and IS-IS, the saving is (1000-1)*4 - 1000 = 2996 (bytes). For N = 1000 and OSPF, the saving is (1000-1)*8 - 1000 = 6992 (bytes).

    When only one node advertises a priority, (N – 1) bytes more is used.


Best Regards,
Huaimo
________________________________
From: Les Ginsberg (ginsberg) <ginsberg@cisco.com>;
Sent: Tuesday, May 28, 2019 11:19 AM
To: Huaimo Chen; tony.li@tony.li
Cc: lsr@ietf.org
Subject: RE: Enhancement related to Area Leader Sub-TLV


Huaimo –



It is highly undesirable that there only be one Area Leader sub-TLV advertisement. The latest version of the draft (V2) highlights this. Please see https://tools.ietf.org/html/draft-ietf-lsr-dynamic-flooding-02#section-6.8.10<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-lsr-dynamic-flooding-02%23section-6.8.10&data=02%7C01%7Chchen%40futurewei.com%7C87445d2f426045f3417a08d6e37fd84a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C636946535570312948&sdata=QxjYmBay0G6mMHqaxUWARJDcpkOsv1tTphJCze%2FcwJs%3D&reserved=0>



You have also not responded to Tony’s point that we do not expect ALL nodes to advertise Area Leader Sub-TLV – which means the savings you calculate below isn’t real.



   Les





From: Lsr <lsr-bounces@ietf.org>; On Behalf Of Huaimo Chen
Sent: Monday, May 27, 2019 7:50 PM
To: tony.li@tony.li
Cc: lsr@ietf.org
Subject: Re: [Lsr] Enhancement related to Area Leader Sub-TLV



Hi Tony,



    Thank you for your explanations.



    After moving one byte for the priority from Area Leader Sub-TLV to Dynamic Flooding Sub-TLV, only one Area Leader Sub-TLV is advertised. For an area with N nodes supporting both centralized and distributed mode, my understanding is below.



    Before moving, each of N nodes may advertise an Area Leader Sub-TLV and a Dynamic Flooding Sub-TLV. After moving, only the leader node advertises a (Updated) Area Leader Sub-TLV. Thus (N - 1) Area Leader Sub-TLVs are saved, which use space of (N-1)*S1 bytes, where S1 is the size of Area Leader Sub-TLV. Each of N nodes may advertise a (Updated) Dynamic Flooding Sub-TLV, which has one extra byte for the priority. Thus N bytes are used.



    The saving on space after moving should be (N-1)*S1 - N. S1 is 4 in IS-IS; S1 is 8 in OSPF.

For N = 1000 and IS-IS, the saving is (1000-1)*4 - 1000 = 2996 (bytes)

For N = 1000 and OSPF, the saving is (1000-1)*8 - 1000 = 6992 (bytes)

Best Regards,

Huaimo

________________________________

From: Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>> on behalf of tony.li@tony.li<mailto:tony.li@tony.li> <tony.li@tony.li<mailto:tony.li@tony.li>>
Sent: Friday, May 24, 2019 4:56 PM
To: Huaimo Chen
Cc: lsr@ietf.org<mailto:lsr@ietf.org>
Subject: Re: Enhancement related to Area Leader Sub-TLV





Hi Huaimo,



Thank you for your proposal.



The area leader sub-tlv is only advertised by systems that are willing to be area leader.  Presumably, that’s not necessarily all of the ones who support dynamic flooding.  Thus, what you’re proposing moves one byte from one TLV into another TLV that will be more commonly used. So your proposal actually consumes more LSP space.



The intention here is that the candidates for area leader advertise the Area Leader Sub-TLV.  All nodes that support dynamic flooding would advertise the Dynamic Flooding Sub-TLV.

Since the priority is part of the Area Leader election, it makes sense for it to be part of the Area Leader Sub-TLV.



Regards,

Tony



p.s. IS-IS does not depend on word-alignment, so we typically do not leave reserved bytes in our TLV formats. OSPF is a different kettle of fish… :-)





On May 24, 2019, at 1:44 PM, Huaimo Chen <hchen@futurewei.com<mailto:hchen@futurewei.com>> wrote:



Hi Tony,



     An enhancement related to Area Leader Sub-TLV is briefed below for discussions.  A .pdf file is attached in the case that the formats below are messed up.



The leader of an area advertises an Area Leader Sub-TLV to indicate/instruct whether centralized or distributed mode is to be used by all the nodes in the area (Algorithm = 0: centralized mode; Algorithm = N (N>0): distributed mode and N is the algorithm to be used by every node to compute flooding topology).



Currently for IS-IS, IS-IS Area Leader Sub-TLV below is used by each of the nodes to advertise its priority for becoming the leader

    0                   1                   2                   3

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |     Type      |     Length    | Priority      |   Algorithm   |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                     (Current) IS-IS Area Leader Sub-TLV



It seems hard to understand that every node uses an Area Leader Sub-TLV to advertise its priority for becoming the leader, and at the same time to indicate/instruct whether centralized or distributed mode is to be used by all the nodes in the area.



When every node advertises an Area Leader Sub-TLV, only one for indication/instruction for flooding reduction mode is used, and all the others are not used, which consume space and processing time.



An enhancement is to let every node advertise its priority for becoming the leader and the algorithms that it supports though using a Dynamic Flooding Sub-TLV, and only the leader advertise the indication for the flooding reduction mode. To achieve this, some changes to the two Sub-TLVs and the texts related to the Sub-TLVs should be made.



For IS-IS, IS-IS Area Leader Sub-TLV is updated as follows (Priority is removed)

    0                   1                   2                   3

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |     Type      |     Length    | Reserved      |   Algorithm   |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                                   (Updated) IS-IS Area Leader Sub-TLV



The Priority is added into IS-IS Dynamic Flooding Sub-TLV. The current IS-IS Dynamic Flooding Sub-TLV

    0                   1                   2                   3

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |     Type      |     Length    | Algorithm...  |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                   (Current) IS-IS Dynamic Flooding Sub-TLV



is changed to:

    0                   1                   2                   3

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |     Type      |     Length    | Priority       |Algorithm...  |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                   (Updated) IS-IS Dynamic Flooding Sub-TLV



Similarly for OSPF, the current OSPF Area Leader Sub-TLV below

       0                   1                   2                   3

       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |              Type             |             Length            |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |    Priority   |   Algorithm   |            Reserved           |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                                   (Current) OSPF Area Leader Sub-TLV

is changed to

       0                   1                   2                   3

       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |              Type             |             Length            |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |    Reserved   |   Algorithm   |            Reserved           |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                                   (Updated) OSPF Area Leader Sub-TLV



The current OSPF Dynamic Flooding Sub-TLV below

       0                   1                   2                   3

       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |              Type             |             Length            |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      | Algorithm ... |                                               |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                      (Current) OSPF Dynamic Flooding Sub-TLV

is changed to

       0                   1                   2                   3

       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |              Type             |             Length            |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |    Priority   | Algorithm ... |                               |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                      (Updated) OSPF Dynamic Flooding Sub-TLV





Best Regards,

Huaimo



<EnhanceOnAdvertisePriority4Leader.pdf>