Re: [Lsr] Request WG adoption of TTZ
Henk Smit <henk.ietf@xs4all.nl> Thu, 16 July 2020 08:46 UTC
Return-Path: <henk.ietf@xs4all.nl>
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 8A44B3A1202 for <lsr@ietfa.amsl.com>; Thu, 16 Jul 2020 01:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=xs4all.nl
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 dcG7By7LMdb6 for <lsr@ietfa.amsl.com>; Thu, 16 Jul 2020 01:45:59 -0700 (PDT)
Received: from lb3-smtp-cloud8.xs4all.net (lb3-smtp-cloud8.xs4all.net [194.109.24.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8281A3A1201 for <lsr@ietf.org>; Thu, 16 Jul 2020 01:45:59 -0700 (PDT)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:200]) by smtp-cloud8.xs4all.net with ESMTPA id vzWcj326xNPeYvzWcjTkWy; Thu, 16 Jul 2020 10:45:54 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=s1; t=1594889154; bh=6sj8nEuIadd2xxAnbqPAnW1K1/KieXb7joFN5qQjSK4=; h=MIME-Version:Content-Type:Date:From:To:Subject:Message-ID:From: Subject; b=OMRPhkN2HsmeNYtRAwgAGQPgvl70J47KxR+ApLDE1D++SWkZAMVS+B/FyuZekedAA uEOjIP3cxPE08Uf7dhA9c/9vWkq4yzqFWaavtNOw6LipvnRhIcucYOvRKHR3Kr7BEl djY1HlzB1RtEXxfCKGYsvcPF4vABDfLwj3Odi2Ab5fsWBtsUlym1jdjIzhJOe7LaV6 VReF7rLM0HF9uZ4mEvNxAYH7QkOCPScZj8l2AgHuJ6WQCRexjKnI+ID432qSpFLy/n Xg21uvFWOgkHIOHmEIY5nj/vo8bPCnc3lD7ibU0uJaH3p8LBLf9I4MmSt41vKCpIEN gCXqkm9bAQ8SA==
Received: from knint.xs4all.nl ([83.162.203.154]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Thu, 16 Jul 2020 10:45:54 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Thu, 16 Jul 2020 10:45:54 +0200
From: Henk Smit <henk.ietf@xs4all.nl>
To: Tianran Zhou <zhoutianran@huawei.com>
Cc: Huaimo Chen <huaimo.chen@futurewei.com>, lsr@ietf.org
In-Reply-To: <d567ac957f11447b80950f70118305c6@huawei.com>
References: <MN2PR13MB31178756BB6166B2F1807CF6F2980@MN2PR13MB3117.namprd13.prod.outlook.com> <CAF4+nEHB+C8n22F-60FXYa5JXoFHxH9oDg0ANsWd4V_fdW9EiQ@mail.gmail.com> <DM6PR06MB509884AFCDB21593E2B4389DEE630@DM6PR06MB5098.namprd06.prod.outlook.com>, <BYAPR13MB243779757964C2D31BB1AEB2D9600@BYAPR13MB2437.namprd13.prod.outlook.com> <MN2PR13MB3117E81B8CA6A298742C01D1F2610@MN2PR13MB3117.namprd13.prod.outlook.com> <c1add5e4fe4e3f387e83f7d6b76db5cb@xs4all.nl> <d567ac957f11447b80950f70118305c6@huawei.com>
Message-ID: <8d0c8294b701eb8f78b7d8fe87c156c9@xs4all.nl>
X-Sender: henk.ietf@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfNAPYfwR9HXQi5SImg77XYIi/W0nQN3j5PTe5bi0eZRfltwDWA3bHG1pSpIR9gxOBCbb0lDMs8ejcsV/vwu/3xB/PoxV0JfyKduEXpLHXY1YcC/lmLZh ki2gvauMdP8C5Lq3WEUtar5skpKTYt4COQBcMph8MnkYKN/QJlRrAVvqV8zq6Gk81FfYur8wxuW558/6Yj4D7jW4rfTXmenadEy0By6KnoAnhRsjEaAu4u0s GyPl2u+2GSG1ui5u7EAEYFkz0bMF+ftLGVDw626vaWE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/hYhDoV75ty5gqpbA0lbWnfDM9CA>
Subject: Re: [Lsr] Request WG adoption of TTZ
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: Thu, 16 Jul 2020 08:46:02 -0000
Hello Tianran, Warning, long email again. > What's the criterion to evaluate the benefit? As people have asked before, did any provider or enterprise ever use rfc8099 in their network ? As I wrote, one of my criteria is rfc1925. I like technology to be understandable. I like protocols to be (relatively) easy to implement. The more unused cruft there is, the further we get away from that goal. I'll give you an example. Did you, or your company ever implement rfc2973 ? That's mesh-groups in IS-IS. I'm sure some customers put it on their wishlist. Did any provider or customer ever use it ? I asked this question at my last job, and nobody knew the answer. I suspect nobody in the world ever used mesh-groups. Around the time I got in touch with IS-IS, in spring 1996, there was a problem that was seen 2 of the 3 largest ISPs in the US (UUnet and iMCI). Both networks melted because of IS-IS. All routers in their networks were 100% cpu time running IS-IS, busy exchanging LSPs. While no progress was made. The only solution was to reboot all routers in the backbone at the same time (several hundred routers). This happened more than once in both networks. To relieve the burden of flooding, mesh-groups were implemented, and rfc2973 was written. However, a short while later I became the sole IS-IS programmer for that router vendor. I was able to reproduce the problem in the lab. I then realized what the issue was. A fix of 10 lines of extra code fixed the problem. No customer ever reported those meltdowns again. That fix was the real solution. Not writing another RFC. In the mean-time, we have an extra RFC, about mesh-groups. Every book and manual on IS-IS has to spent time explaining what mesh-groups are. Every vendor has to implement it. Even when nobody in the world is using it. Mesh-groups were a superfluous idea. What I (and many others) are saying is that we don't want to specify and implement unnecessary things. Even when nobody is using such a thing, it will live on forever. > What I see the TTZ does have benefit. Yes, TTZ and proxy-areas have benefit. Nobody is disagreeing. But what people don't like is the new concept of a zone. If you can abstract exactly one area into exactly one proxy-LSP, that is good enough for 99.9 % of cases. In OSPF it is harder to split or merge an area. In IS-IS it is a lot easier. So a network operator can design and change his areas first. And then implement proxy-areas as she/he wishes. Without much downtime. If we introduce the concept of a "zone", someone is going to have to explain that to everybody in the world who uses IS-IS. Have you ever taught a class on IS-IS to people who don't know routing protocols very well ? > I am also wandering how it hurts the protocol in the long run ? Adding stuff that nobody uses makes everything more complex. I know it seems as if the goal over the last 15 years was to make every thing more complex. So what's the problem with adding yet another RFC ? But I like simple things. henk. Tianran Zhou wrote on 2020-07-16 02:41: > > "Adding a new concept, with very little benefit, hurts the protocol in > > the long run. The ability to abstract an area, and not also a zone, is > > strong enough to be worthwhile, imho." > > Your conclusion here seems very subjective. > What's the criterion the evaluate the benefit? What I see the TTZ does > have benefit. > I am also wandering how it hurts the protocol in the long run? > .... > > Tianran
- [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Christian Hopps
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Les Ginsberg (ginsberg)
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Christian Hopps
- Re: [Lsr] Request WG adoption of TTZ tony.li
- Re: [Lsr] Request WG adoption of TTZ Les Ginsberg (ginsberg)
- Re: [Lsr] Request WG adoption of TTZ Acee Lindem (acee)
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Acee Lindem (acee)
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Les Ginsberg (ginsberg)
- Re: [Lsr] Request WG adoption of TTZ Tony Li
- Re: [Lsr] Request WG adoption of TTZ Christian Hopps
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Aijun Wang
- Re: [Lsr] Request WG adoption of TTZ tony.li
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Acee Lindem (acee)
- Re: [Lsr] Request WG adoption of TTZ Acee Lindem (acee)
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Donald Eastlake
- Re: [Lsr] Request WG adoption of TTZ LEI LIU
- Re: [Lsr] Request WG adoption of TTZ Linda Dunbar
- Re: [Lsr] Request WG adoption of TTZ Haoyu Song
- Re: [Lsr] Request WG adoption of TTZ Uma Chunduri
- Re: [Lsr] Request WG adoption of TTZ Christian Hopps
- Re: [Lsr] Request WG adoption of TTZ Christian Hopps
- Re: [Lsr] Request WG adoption of TTZ Anil Kumar
- Re: [Lsr] Request WG adoption of TTZ Liu Vic
- Re: [Lsr] Request WG adoption of TTZ Yanhe Fan
- Re: [Lsr] Request WG adoption of TTZ Toy, Mehmet
- Re: [Lsr] Request WG adoption of TTZ reta Yang
- Re: [Lsr] Request WG adoption of TTZ ruoxin huang
- Re: [Lsr] Request WG adoption of TTZ Kiran Makhijani
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Tony Li
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Tony Li
- Re: [Lsr] Request WG adoption of TTZ Linda Dunbar
- Re: [Lsr] Request WG adoption of TTZ Acee Lindem (acee)
- Re: [Lsr] Request WG adoption of TTZ Linda Dunbar
- Re: [Lsr] Request WG adoption of TTZ Acee Lindem (acee)
- Re: [Lsr] Request WG adoption of TTZ Linda Dunbar
- Re: [Lsr] Request WG adoption of TTZ Acee Lindem (acee)
- Re: [Lsr] Request WG adoption of TTZ Henk Smit
- Re: [Lsr] Request WG adoption of TTZ John E Drake
- Re: [Lsr] Request WG adoption of TTZ Les Ginsberg (ginsberg)
- Re: [Lsr] Request WG adoption of TTZ Uma Chunduri
- Re: [Lsr] Request WG adoption of TTZ Richard Li
- Re: [Lsr] Request WG adoption of TTZ Uma Chunduri
- Re: [Lsr] Request WG adoption of TTZ Acee Lindem (acee)
- Re: [Lsr] Request WG adoption of TTZ Uma Chunduri
- Re: [Lsr] Request WG adoption of TTZ Tianran Zhou
- Re: [Lsr] Request WG adoption of TTZ Henk Smit
- Re: [Lsr] Request WG adoption of TTZ Tianran Zhou
- Re: [Lsr] Request WG adoption of TTZ Christian Hopps
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ Les Ginsberg (ginsberg)
- Re: [Lsr] Request WG adoption of TTZ Tianran Zhou
- Re: [Lsr] Request WG adoption of TTZ Christian Hopps
- Re: [Lsr] Request WG adoption of TTZ Huaimo Chen
- Re: [Lsr] Request WG adoption of TTZ tony.li