Re: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?

Erik Kline <ek.ietf@gmail.com> Wed, 27 May 2020 21:40 UTC

Return-Path: <ek.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62733A0879; Wed, 27 May 2020 14:40:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 17w6C9TiipSf; Wed, 27 May 2020 14:40:44 -0700 (PDT)
Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (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 BC3913A0C84; Wed, 27 May 2020 14:40:44 -0700 (PDT)
Received: by mail-oi1-x230.google.com with SMTP id y85so23039888oie.11; Wed, 27 May 2020 14:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=V6OmjEZrVkEGOUUfeQsQSsB28SGXMS4L+eHe4nCezTU=; b=snckSOQLX/v2iuN6lCaeziOJZLB+3/NUNjPzP9McNJegohd2+IKZ6J2WM4y7zVbjcg 0oSdCf5mXB1L11bPXGhyZgoV93xp3OAIUlE438k+f3RGNWiLjtk8ulm2W7riW+o/KTgJ q8XceB7L4NhKu4rN/u4VKHyK4T86uH2dsQG//9oY6aF2wU4P2tsVzbSoh/ggy4j9ZAEE yqCY0o6piz+9K0NRjDOqaqRXnWFT9G3cazzZfHmNbQYTkg0Oar/S3mlGmmprdqmFUvJ5 ArATL/7QTebuVHnqxTj7DuEVnjarZ5Xzf8jPiAMEDefHxfuEeXvIdgNItjkZrTuwMjGG j1TA==
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:content-transfer-encoding; bh=V6OmjEZrVkEGOUUfeQsQSsB28SGXMS4L+eHe4nCezTU=; b=RPzaP81Lz0AuV45SkzgYRnggXoe35roI2nVG132GvywLJLmdwbuEzLbff208wTp6nY xXO5/0jTTuo3qAIe2M8+V7J2o532cxqm1PRRJpqIhok9Z7TiT2x5UeSUeSS0tkPFGH0y PKkerv2EQsbf34Yuq77hpZGSqBwBaRKfY2YILd9BlVvDMI3On9nCHIu/FJNLUzNj2YDB R3KEVBoR9T8Aq7cGFmRNVEOqOS0uZy674DnUS1f0/iAavuG8Z1ZP+0xVmCuCtjpRkzUg 8TcmHQy4fOovo+7s5wHYyRonPFqbZ6XYo7yiC+QyKzPysS8Rrjyg3tjoIh3jBavbB2o3 RItw==
X-Gm-Message-State: AOAM531VnCyJf6s6UUjsxhO5ooCMVwUbfsLY9qgJc0329HPwyXD5zIKT P80xmfdsVjS1LLns27FJsmNu/1wr/NLr1R5JboA=
X-Google-Smtp-Source: ABdhPJxJCDD6sjZBbsNFYnNjJaBnErdaoppBUTcgZWYU9ceCcg/srtiNnAEeEpIEIpInv5/ZTltKiUKfgLykOBjJURs=
X-Received: by 2002:aca:48d7:: with SMTP id v206mr164446oia.97.1590615642340; Wed, 27 May 2020 14:40:42 -0700 (PDT)
MIME-Version: 1.0
References: <75BF2317-5D28-4038-ABB1-31C588ACD165@cisco.com> <DM6PR05MB6348D86E8BE339067C5238E4AEB10@DM6PR05MB6348.namprd05.prod.outlook.com> <30C37AC0-B03A-45B1-BE0F-7E185361BBBC@liquidtelecom.com> <64e6b98b01c64ec8b699c065bc7ee9e0@boeing.com> <94DF5577-4DCC-4491-A12B-21EAC214172F@cisco.com>
In-Reply-To: <94DF5577-4DCC-4491-A12B-21EAC214172F@cisco.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Wed, 27 May 2020 14:40:31 -0700
Message-ID: <CAMGpriURYBukqQOgnnkySjrQXgeWY+XJVD=d3rOnvVUOLC-E1w@mail.gmail.com>
Subject: Re: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
To: "Zafar Ali (zali)" <zali=40cisco.com@dmarc.ietf.org>
Cc: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, Andrew Alston <Andrew.Alston@liquidtelecom.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>, Sander Steffann <sander@steffann.nl>, "spring@ietf.org" <spring@ietf.org>, 6man <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/NAhZ2aNqnqWLGSBNHAfhPiLIuZw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 May 2020 21:40:48 -0000

There are actual, meaningful differences to be contemplated; folks
with no operational MPLS in there networks might not want to be forced
to start.


On Wed, May 27, 2020 at 2:20 PM Zafar Ali (zali)
<zali=40cisco.com@dmarc.ietf.org> wrote:
>
> Fred,
>
>
>
> Is there any IETF requirement document for OMNI and AERO (I am sorry I am not aware of the technology but very much interested in learning)?
>
> Do we have some documents describing the scale you would need?
>
> Have the associated WG analyzed existing solutions?
>
> Have they feed the results of the above to 6man WG?
>
>
>
> All other routing header types have had requirements and designs from dedicated working groups with expertise in the area.
>
> Why should CRH be an exception, especially when there are multiple competing solutions in 6man and Spring?
>
>
>
> Thanks
>
>
>
> Regards … Zafar
>
>
>
> From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
> Date: Wednesday, May 27, 2020 at 4:33 PM
> To: Andrew Alston <Andrew.Alston@liquidtelecom.com>om>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>rg>, "Zafar Ali (zali)" <zali@cisco.com>om>, "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>om>, Sander Steffann <sander@steffann.nl>
> Cc: "spring@ietf.org" <spring@ietf.org>rg>, 6man <6man@ietf.org>
> Subject: RE: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
>
>
>
> As I said, I want to use CRH for OMNI and AERO; I don't want the term "MPLS" to appear
>
> either in my documents or in any documents mine cite. The 16-bit CRIDs in CRH are very
>
> handy for coding ULA Subnet Router Anycast addresses such as fd80::/16, fd81::/16,
>
> fd82::/16, etc., and the 32-bit CRIDs are very handy for coding the administrative address
>
> suffixes of fd80::/96. So, CRH gives everything I need (and nothing I don’t need) for
>
> successfully spanning the (potentially) multiple segments of the AERO link.
>
>
>
> Thanks - Fred
>
>
>
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Andrew Alston
> Sent: Wednesday, May 27, 2020 1:19 PM
> To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>rg>; Zafar Ali (zali) <zali@cisco.com>om>; Henderickx, Wim (Nokia - BE/Antwerp) <wim.henderickx@nokia.com>om>; Sander Steffann <sander@steffann.nl>
> Cc: spring@ietf.org; 6man <6man@ietf.org>
> Subject: Re: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
>
>
>
> What I find so bizarre is –
>
>
>
> You have an multiple operators – who have clearly said – we want this – we see advantage of this.  Yet still the obstructionism and denialism continues.  The “not invented here” syndrome seems to run deep – and email after email is patently ignored from the very people who have to buy the hardware.  Reference is made to Montreal – yet the emails that stated the use cases after it went by with no response.  No technical objections ever show up – other than – we don’t want this and you haven’t given us this mythical architecture document – which was yet another non-technical response that seems so clearly designed to stall any innovation that doesn’t come from one source.
>
>
>
> All I see from the operator perspective here is obstructionism and stalling in a desperate attempt to block anything that could be a threat to what was dreamed up by someone else.  It is almost as if there is fear that the market may choose something other than what was designed – and that fear is driving this stance of throw everything we hav against the wall and hope that something sticks – because the technical arguments have failed time and again.
>
>
>
> This pitbull approach certainly doesn’t garner any respect for me, does not help to promote srv6 which seems to be what you want and in fact convinces me more every day that CRH is the right move – where I can built on top of it without the obstructionism of a vendor that seems to have zero interest in what mysef and other operators are clearly stating over and over again.
>
>
>
> Yet again – I support crh – I’ve deployed CRH – CRH works for us – and we still continue to support it.  And irrespective of if it is adopted – the development of it will continue – and it will exist – the only question is – do we end up with something that the market wants outside of the auspices of the IETF – or do we end up with something that is properly standardized, because this level of obstructionism will not prevent the development.
>
>
>
> Can we actually get back to proper technical reasoning?
>
>
>
> Thanks
>
>
>
> Andrew
>
>
>
>
>
> From: ipv6 <ipv6-bounces@ietf.org> on behalf of Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
> Date: Wednesday, 27 May 2020 at 23:07
> To: "Zafar Ali (zali)" <zali@cisco.com>om>, "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>om>, Sander Steffann <sander@steffann.nl>
> Cc: 6man <6man@ietf.org>rg>, "spring@ietf.org" <spring@ietf.org>
> Subject: RE: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
>
>
>
> Zafar,
>
>
>
> Why all the passion about stopping the CRH? Does it break any existing standard? Does it consume any scarce resource?
>
>
>
> You might argue that there is a scarcity of Routing header type numbers. But that would be a very short argument. You might argue that WG resources are scarce, and that it would take too much time to review this fourteen page document. But that argument might take more time than the document review.
>
>
>
> In your email, below, you mention “the hardware and software investment from vendors”. Is that the scarce resource?
>
>
>
> Vendors are not obliged to implement every draft that is adopted as a WG item. Generally, the marketplace drives product roadmaps.
>
>
>
> If the only resource we are protecting is vendor investment, the long-standing practice of due diligence should be tempered by operator demand. The IETF should not pretend to understand operator requirements better than the operators themselves.
>
>
>
> Why not let the marketplace decide whether it needs a CRH?
>
>
>
>                                                                                             Ron
>
>
>
>
>
>
>
>
>
>
>
> Juniper Business Use Only
>
> From: Zafar Ali (zali) <zali@cisco.com>
> Sent: Wednesday, May 27, 2020 3:19 PM
> To: Henderickx, Wim (Nokia - BE/Antwerp) <wim.henderickx@nokia.com>om>; Sander Steffann <sander@steffann.nl>
> Cc: Mach Chen <mach.chen@huawei.com>om>; Ron Bonica <rbonica@juniper.net>et>; Chengli (Cheng Li) <c.l@huawei.com>om>; 6man <6man@ietf.org>rg>; spring@ietf.org; Zafar Ali (zali) <zali@cisco.com>
> Subject: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
>
>
>
> [External Email. Be cautious of content]
>
>
>
> WH> My position remains that RFC8663 is a valid alternative and is available; I am against WG adoption of CRH.
>
>
>
> The industry widely supports RFC8663.
>
>
>
> Instead of denying the evidence, could the CRH authors and proponents finally understand that people are not opposed to new ideas?
>
>
>
> People are reminding a long-standing practice of the IETF process. Before tackling a new piece of work, a working group must perform a due diligence on
>
> whether this new work is redundant with respect to existing IETF protocols,
> whether this new work would deliver genuine benefits and use-cases.
>
>
>
> It is factually and logically clear to the working-group that the currently submitted CRH documents.
>
> fail to position CRH with respect to existing standard widely supported by the industry (e.g., RFC8663)
> fail to isolate new benefit or use-case [1]
>
>
>
> This positive collaborative feedback was already given in SPRING.
>
> The CRH authors may change this analysis. They need to document 1 and 2.
>
>
>
> Why did the CRH authors not leverage this guidance in SPRING WG?
>
> This was also the chair's guidance in Montreal [2] and Singapore [3]
>
>
>
> All the lengthy discussions and debates on the mailing list could be avoided if only the CRH authors would tackle 1 and 2.
>
>
>
> The CRH authors must tackle 1 and 2.
>
>
>
> This is the best way to justify a/the work from the IETF community and b/ the hardware and software investment from vendors.
> True benefits must be present to justify such a significant engineering investment (new data-pane, new control-plane).
>
>
>
> Thanks
>
>
>
> Regards … Zafar
>
>
>
> [1] https://mailarchive.ietf.org/arch/msg/ipv6/W3gO-dni2tB4nG9e13QsJnjFgG8/
>
> [2] https://etherpad.ietf.org:9009/p/notes-ietf-105-spring?useMonospaceFont=true
>
> [3] https://mailarchive.ietf.org/arch/msg/ipv6/aWkqPfpvDRyjrW8snR8TCohxcBg/
>
>
>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------