Re: [Lsr] LSR Working Group Adoption Call for "Hierarchical IS-IS" - draft-li-lsr-isis-hierarchical-isis-01

Huaimo Chen <huaimo.chen@futurewei.com> Mon, 19 August 2019 14:27 UTC

Return-Path: <huaimo.chen@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 314A21200F3 for <lsr@ietfa.amsl.com>; Mon, 19 Aug 2019 07:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=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 znjcS260k74G for <lsr@ietfa.amsl.com>; Mon, 19 Aug 2019 07:27:36 -0700 (PDT)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-co1nam05on0712.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe50::712]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E49C1200B5 for <lsr@ietf.org>; Mon, 19 Aug 2019 07:27:36 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bp+iAqywf13qnYwWs87euYd5sLB0kLc9uP4wmAMCGjVP0+6HrhJ9R7tdNEQarw/bN/RyXgVY4R3YSikh8aEGkUDkRVRkYBXLFNJFs4etr0E1RVM94Jv/luCC2dc6w9/Gokltc/DHsrq+UcIz1C4ELchZ+XE7BIdWl1wlyDujTkbM5RlRcWYQ7gym4wsZKrZIlRUIzisM1PKSPfwugG/i7Oms0BvTWwSUwWkigdmj2LZKByXwdds7VOAJNzVrZQoONx0DErd52k1lEw0sr9rAVjpl02Vwas9WxO9NKYuiQBi0W9ogotU/2zW/7gVqv8rXY64/vdcu4GR7/WoF+IpQuw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DYV5xQxAhC7U8b1QRJ96KUudslfQKz8a/YWQYhdcHyA=; b=AzQmattctg838SoMGDOI4ulesG79XbiR8yYzXK4KYsLylgWs94ozxIqS23uNTrc9Zq683ODYoTa9bgmuvjkDpkd4QakZG089nxlAqgwlrjx4Y8JP1QRmp5WFnmpz3yW4kpzffZink9tQSf2q0Ws9YvbC8a+1qnFtve8Ccm3pqyDt+C6lk61AgGmEhYmcaaozCBwOXWU68LZnHJV9qDtiI72/mUCDFDRbESLse8x7UJDRyTBzY+DY/I/Wf2QcKbGfVelIaj3dXPI33ZqY41Ss/zr8HHJPSkEp14VJm11IgWFosAIvaepf2SQpeN1noityX8t3UYvko3eyAM/hl/JWzg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
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=DYV5xQxAhC7U8b1QRJ96KUudslfQKz8a/YWQYhdcHyA=; b=mpSCVhkifErTpNRuBeQ8nMi4PqyHNC6QomzYC0zPx/GaT2104wUmj65kM0E770GKdZPkJTZV0OPbb4BRRXyp8G5oCuIwAs7SrhsyZNmKcxC7wKnHRvcUJhGDeu/nMT2HfEQPTCO+kptkfvdwMI8qSc/t0pbvzm6mnY/SxKcylU0=
Received: from BY5PR13MB3459.namprd13.prod.outlook.com (10.255.137.159) by BY5PR13MB3094.namprd13.prod.outlook.com (10.255.162.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.12; Mon, 19 Aug 2019 14:27:33 +0000
Received: from BY5PR13MB3459.namprd13.prod.outlook.com ([fe80::f122:6ec9:1cb9:8972]) by BY5PR13MB3459.namprd13.prod.outlook.com ([fe80::f122:6ec9:1cb9:8972%7]) with mapi id 15.20.2199.011; Mon, 19 Aug 2019 14:27:33 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: LSR Working Group Adoption Call for "Hierarchical IS-IS" - draft-li-lsr-isis-hierarchical-isis-01
Thread-Index: AQHVURraLOii8Ni+80mn+fcAdO3zAqcCjoCA
Date: Mon, 19 Aug 2019 14:27:32 +0000
Message-ID: <BY5PR13MB3459D8CA48EBF7B98B1ED37EF2A80@BY5PR13MB3459.namprd13.prod.outlook.com>
References: <8BAFFDB4-62B0-4018-966E-6861D89D0BD1@cisco.com>
In-Reply-To: <8BAFFDB4-62B0-4018-966E-6861D89D0BD1@cisco.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=huaimo.chen@futurewei.com;
x-originating-ip: [12.111.81.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 63493517-3360-4c76-9594-08d724b15fce
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BY5PR13MB3094;
x-ms-traffictypediagnostic: BY5PR13MB3094:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BY5PR13MB3094BC8C8EFB534EB4534FC1F2A80@BY5PR13MB3094.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0134AD334F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(346002)(366004)(39840400004)(396003)(136003)(189003)(199004)(66476007)(66446008)(64756008)(66556008)(52536014)(71200400001)(71190400001)(790700001)(76116006)(8936002)(99286004)(66946007)(2501003)(74316002)(6306002)(6436002)(476003)(11346002)(486006)(66066001)(53936002)(6246003)(55016002)(446003)(5660300002)(9686003)(25786009)(33656002)(54896002)(186003)(53546011)(102836004)(44832011)(8676002)(81156014)(81166006)(26005)(14454004)(7736002)(478600001)(316002)(6116002)(86362001)(7696005)(256004)(76176011)(2906002)(3846002)(110136005)(229853002)(6506007); DIR:OUT; SFP:1102; SCL:1; SRVR:BY5PR13MB3094; H:BY5PR13MB3459.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: fh0P4AznRx+z/gK+oSY5xRlBy/YwWwX5ZA4n4YUXJ47kwiohqG46kWiDIJ6wuIZgT/Ng+JQFKrlz02VfngLshdarg8BfPOfAHTyl5YprNOXsgvs3ysYJEhZdT5qCJ3+WCRrxaJoTCPDO0Gx222Wm6KZaH8zWKgFXHWur6BBE+xHOrgpkb/NPnNiAlsmaX9HNm98/RGClQ4ZHjYbroxD28zHZMizPvZNjE8spHcUDeWCb4W6db4wqH0AAV/hhuin0nzuY++yfQnc7tpIgeN0mXnfAGm0kOoExskxcGzpzN91j0eB+zi4QT4qaKljama2HCOSJGpq4X+aaINWUjpjQ16bSn6z8mPB9bGv8Q5JfPLHCsNYNbt+WOtMObwoUs7Ap6UA8gBkyWC/bfYZfnzsvLDPYn1YIPL9bRMdbGf208nE=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BY5PR13MB3459D8CA48EBF7B98B1ED37EF2A80BY5PR13MB3459namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 63493517-3360-4c76-9594-08d724b15fce
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2019 14:27:32.8741 (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: BQshEQIiuxwjMrZLzF+cFOx9nYFdgH5JLr0u/xv33qbjPCBYvPH2jqzID74Db6sySddNfTkdc8KcppydM1KSnA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR13MB3094
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/CdMNyuBqVTKrkUgE4fXZx0rg014>
Subject: Re: [Lsr] LSR Working Group Adoption Call for "Hierarchical IS-IS" - draft-li-lsr-isis-hierarchical-isis-01
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: Mon, 19 Aug 2019 14:27:40 -0000

Support and have the following comments:


  1.  It seems not necessary to have 8 levels of hierarchies. 3 or at most 4 levels of hierarchies should be enough. IS-IS with 3 levels of hierarchies may support a network with 1k*1k*1k nodes, which is about 10^9 = 1 billion nodes. IS-IS with 4 levels of hierarchies may support a network with 1k*1k*1k*1k nodes, which is about 10^12 = 1 trillion nodes.
  2.  For PDU type, section 2.2 of the draft proposes to use 8 bits (all three reserved bits plus the 5 bits for the existing PDU type). It seems better to use 6 bits (one reserved bit plus the 5 bits for the existing PDU type). Adding one reserved bit into the PDU Type allows people to define 32 new PDU types, which is enough for the new PDU types needed for new hierarchies.
  3.  Section 3 “Additional PDUs” of the draft, defines 6 new PDU Types for ’Level n LAN IS to IS hello PDU’ (Ln-LAN-HELLO-PDU), where n is 3, 4, 5, 6, 7, and 8. In addition, the following new PDU Types should be defined (considering at most 4 levels of hierarchies):
     *   2 new PDU Types for ‘’Level n LSP”, where n is 3, and 4
     *   2 new PDU Types for ‘’Level n CSNP”, where n is 3, and 4
     *   2 new PDU Types for ‘’Level n PSNP”, where n is 3, and 4
  4.  On a broadcast interface, Level 1 LSPs are multicast through MAC 0x0180.c200.0014 (which is called AllL1ISs), and Level 2 LSPs are multicast through MAC 0x0180.c200.0015 (which is called AllL2ISs). It seems that Level n LSPs should be multicast through AllLnISs, where n is 3, and 4 (considering at most 4 levels of hierarchies), thus
     *   2 new MAC should be assigned to AllLnISs, where n is 3, and 4.
  5.  The existing DIS for a broadcast interface periodically multicast through AllL1ISs and AllL2ISs a Complete SNP (CSNP). It seems that the DIS should be extended to periodically multicast a CSNP through AllLnISs, where n is 1, 2, 3, and 4 (considering at most 4 levels of hierarchies).
  6.  When there may be 3 or more levels of hierarchies, is it allowed to have 3 or more levels (consecutive) configured on an interface? It seems that there is no description about this in the draft.

Best Regards,
Huaimo

From: Lsr <lsr-bounces@ietf.org> On Behalf Of Acee Lindem (acee)
Sent: Monday, August 12, 2019 10:33 AM
To: lsr@ietf.org
Subject: [Lsr] LSR Working Group Adoption Call for "Hierarchical IS-IS" - draft-li-lsr-isis-hierarchical-isis-01

This begins a two week LSR Working Group Adoption Poll for the "Hierarchical IS-IS" - draft-li-lsr-isis-hierarchical-isis-01. The poll will end at 12:00 AM UTC on August 27th, 2019. Please indicate your support of objection on this list prior to the end of the adoption poll.

Thanks,
Acee