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

Robert Raszuk <robert@raszuk.net> Mon, 19 August 2019 15:06 UTC

Return-Path: <robert@raszuk.net>
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 E65701200D7 for <lsr@ietfa.amsl.com>; Mon, 19 Aug 2019 08:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 8R-LNklqmMrY for <lsr@ietfa.amsl.com>; Mon, 19 Aug 2019 08:06:55 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E9EB120096 for <lsr@ietf.org>; Mon, 19 Aug 2019 08:06:55 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id i4so2219707qtj.8 for <lsr@ietf.org>; Mon, 19 Aug 2019 08:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rTSM61jYn2h004dc8O+lZFaOHV07g6V4TPsfaU0K9jI=; b=c8vdb5YPAyB4mApQSgT6KnbL+K65dJOvrBqhgKR1I89WZ1LUenPrr58IEQE2lL5ubb VJnNQoiuNola7xDbv+wKDCQrSU95fJ8/D6nJ1ODod8BdSU2S1JDfALnup6Rn22Fzvj17 ew2Gajgc9L0KaV8lT1q0W4wMaWSPBl5dpUV3qFO4pHyQUTKacN/0n5Pj2yFDOCsLMLZx Pk7lyz69lOaoQAuANOs9kDC/+gxISWFuwJsunTae7U4cwc4RpU02ernaS9pMICniC4nt B+9Ow3KIYKbIipT/LHul9DGueRgFnZwNI9ahgm6ZV4sSqwZcCFFXGglJ5TqgE1n/Smds 7TbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rTSM61jYn2h004dc8O+lZFaOHV07g6V4TPsfaU0K9jI=; b=iGBtBZ8o0NlCtx1V7USSxxttdc50e5QaVHzu91oB/Wj+Uu62y4jQ8nCY+0/+KBW7VT YTmSHwRQ07MC65j3Tw3BUIccvzCk6Xlni7oRWM848Z6GGnaDwvQaYbrBYRi57iuFlgIv /JZDl5Q4dUZ7LJwzgU+YXMVU68U0tV+Uau2E2NiOfn/YRlYoeAz6rtfXjxOAPQnSsURN idv2xhuPHtmGYS3q8KAKRaiOwav7ASNLmDsDL0EcW/5V1htk2Wv0L4JQA8n81zcNq3ZG ztoBVxC1QT8YC93ZmiuQ3IATulRmFOgJfPF7hDyIEA4E1BIwEg5RRNlkOV7XLFKuVP+2 VWwg==
X-Gm-Message-State: APjAAAW5DY/iwhAqBSDpbkmQCMPdIyQTRAE5muYNlptGUo1mdV39rxex opZhCTqCA28ed/3D3KZIcmKeNexHq5WrkDbciqyUaA==
X-Google-Smtp-Source: APXvYqw3SJTqPx68zurH+mJBadydC5bIPhDnydhkA0nTzXPsmdQ8cgnxuXCNhLEHPt0UhodfKjiquGS2gxr2qhwnfQo=
X-Received: by 2002:ad4:4562:: with SMTP id o2mr11108086qvu.116.1566227214277; Mon, 19 Aug 2019 08:06:54 -0700 (PDT)
MIME-Version: 1.0
References: <8BAFFDB4-62B0-4018-966E-6861D89D0BD1@cisco.com> <BY5PR13MB3459D8CA48EBF7B98B1ED37EF2A80@BY5PR13MB3459.namprd13.prod.outlook.com>
In-Reply-To: <BY5PR13MB3459D8CA48EBF7B98B1ED37EF2A80@BY5PR13MB3459.namprd13.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 19 Aug 2019 17:06:42 +0200
Message-ID: <CAOj+MMGEGW2fpydr+eeuDnT=9MNC90+4pGQQpgzDuCSv0yNpLw@mail.gmail.com>
To: Huaimo Chen <huaimo.chen@futurewei.com>
Cc: "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000beaf24059079b0b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/z1OBbkIes-A-FO1bZB4ovzK35cY>
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 15:06:58 -0000

Hi Huaimo,

Ad 1 - Let me observe that constructing hierarchy is not always driven by
number of nodes in a given level can safely support. One could indeed build
a global flat link state network in single level/area if only looking at
number of nodes. But in number of cases benefits from hierarchy could be
seen in reduced flooding radius and enforced summarization. Hint:  me why
my routers in Sydney have to be aware about link flap in POP in Toronto ?

Ad 6 - Interesting .. I asked the same question to authors offline :)

Thx,
R.




On Mon, Aug 19, 2019 at 4:27 PM Huaimo Chen <huaimo.chen@futurewei.com>
wrote:

> 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):
>       1. 2 new PDU Types for ‘’Level n LSP”, where n is 3, and 4
>       2. 2 new PDU Types for ‘’Level n CSNP”, where n is 3, and 4
>       3. 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
>       1. 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
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>