Re: IPv4 EH proposal

Stewart Bryant <stewart.bryant@gmail.com> Mon, 09 September 2019 18:34 UTC

Return-Path: <stewart.bryant@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 13A34120811 for <ipv6@ietfa.amsl.com>; Mon, 9 Sep 2019 11:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 f4DacIYtA5z2 for <ipv6@ietfa.amsl.com>; Mon, 9 Sep 2019 11:34:52 -0700 (PDT)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (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 96A1712022D for <ipv6@ietf.org>; Mon, 9 Sep 2019 11:34:52 -0700 (PDT)
Received: by mail-ot1-x32d.google.com with SMTP id g19so13667851otg.13 for <ipv6@ietf.org>; Mon, 09 Sep 2019 11:34:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=/dX+zkn9aIsmWrMIUtqL+71bGJQS4WQYZC63fNF2ITw=; b=bfGiZiFP5IlX9j0oADwH24a0sJPJKBA9NWOHvnU37Y4u3kRM+5dXUd+IF1HMzd4wOE 7VLUcIAqnlNx+UTaLIyaB3XsoRvBBAV7VIBVvi28cgCxVc/a6tjqTzRrE5Uto9cd9gj4 uBrJ5JVmkwCKN6lLmrhQ81GSjYdQlCLBcbW+duhKptJfa2DLU03wkJfkGGEEPpkBpyGV OxZkha14mmH3y714HOqJ/C+cg9U4pbELG29ByLvryQUmUleUyE1fzMX+psKAHlogjH+0 lh7tPLV+PjnUKNm2G5aWOFSliqvb8VK2D9SLY8fTV+ktAQ8P1qNc/OT+zJQgOWd7MfPV 5CJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/dX+zkn9aIsmWrMIUtqL+71bGJQS4WQYZC63fNF2ITw=; b=Q4h4p51+9py4ztaTq4PP0XPPhfNdr8CJRnNrObW+Xc7+ZkT8ggpS/LTnPl2sV5IafA Ggw3LXJdS2gsn0+W7Zcy2Y0LX7BddnRrcRPwBQKiN/U2ScLcGCpOLQlBkAPRSPuhfGMR PVeaFiRqMEy1RY020QHgBAinH/S07wHm19WdO3zhF3/R6EWiR4mrCpSJASoOkWmrAWgW RLGIYZL9h+BFMVVClIfsC5dFIaujSQ3w4rBawf8d1HVVMXsAY+pNlGh55U53NZ7e2iWn mMoZKt3MBUeftZydK6cfFWnfMb0fmlmeBCSr/fDziOytjj6ZYB/AVJ/ENYoBa/96MFuk S6Ew==
X-Gm-Message-State: APjAAAXkV6EOcXmTR9+mh+s/TOylQBdOI47w1/Edy5L6SsdeOT4lReGn QZLHCf62uxLxDj9V07JR5f2COPqLkV4=
X-Google-Smtp-Source: APXvYqyWmUXANU2ssOhr5ey/2edlo93xI5n3sFuNktr4jpqaZmF7qDfnQQpEZgUxyKVATLOdwrU7YQ==
X-Received: by 2002:a9d:6f8a:: with SMTP id h10mr2281278otq.226.1568054091540; Mon, 09 Sep 2019 11:34:51 -0700 (PDT)
Received: from [100.65.100.175] ([206.16.17.231]) by smtp.gmail.com with ESMTPSA id v2sm1007252oix.48.2019.09.09.11.34.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Sep 2019 11:34:50 -0700 (PDT)
Subject: Re: IPv4 EH proposal
To: Lee Howard <lee@asgard.org>, ipv6@ietf.org
References: <BYAPR05MB5463153B47BFE83350C566E7AEBA0@BYAPR05MB5463.namprd05.prod.outlook.com> <CA+b+ERm4x072JQZQovX0MVcea3=0DOCSESopAXj_SE1vMi8qkQ@mail.gmail.com> <06CF729DA0D6854E8C1E5121AC3330DFAE9362F9@dggemm529-mbs.china.huawei.com> <CAO42Z2y-hq71wr9ogzmn2=rO0xySy63iXhNXrFDuqO7r5Pwa7A@mail.gmail.com> <CAOj+MMFN5pbaVePWrJA61jd7f9d_2bU-Nu9oppFDsAc_B7APDw@mail.gmail.com> <CAO42Z2x4-9-1YseuyqnCRh7c+J-zb2ksGXpk_Hs17H5uLz4Hvg@mail.gmail.com> <CAOj+MMHHMdGm6Qea4E1ugQBrSYFr7e-FgP+pxoErhEwRR9GwKw@mail.gmail.com> <e31311de-6db5-8172-fbdd-11b461a330c8@asgard.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <daeebebe-65a2-c499-5112-058f3ab46fda@gmail.com>
Date: Mon, 09 Sep 2019 19:35:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <e31311de-6db5-8172-fbdd-11b461a330c8@asgard.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pP7PizC1XN8J54uSgl0MjfGqXKI>
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: Mon, 09 Sep 2019 18:34:54 -0000

Without commenting on the specific technical proposal.

IPv4 is still critical infrastructure in many organizations.

We have to maintain it until its natural death. If we neglect the 
maintenance, or worse try to euthanise it, it will end up either 
explicitly or implicitly being maintained by another organization.

We would thus be wise to actively maintain IPv4 for as long as users 
need us to, rather than to risk loosing control of it and its future 
developments.

- Stewart


On 07/09/2019 16:01, Lee Howard wrote:
> IPv4 is dying. Let it go gracefully.
> 
> I'm completely opposed to any extensions to the IPv4 specification. By 
> the time the feature set is code complpete, QA'd, and ready for general 
> release, 80% of the world will be using IPv6.
> 
> Specific to this case, I have a very hard time understanding the 
> business/engineering case where it would be optimal to implement these 
> extensions rather than deploy IPv6, where they already exist.
> 
> Lee
> 
> On 9/7/19 7:32 AM, Robert Raszuk wrote:
>> /* Adjusting the subject to reflect the topic */
>>
>> Ok ... I looked at the new wave of mails in wrong order :)
>>
>> I like this proposal:
>>
>> https://tools.ietf.org/html/draft-herbert-ipv4-eh-01
>>
>> And have absolutely nothing against progressing it further - it looks 
>> on the surface to be more efficient then sr-mpls over IP - but how 
>> many bits are we saving needs to be calculated to state if cost of 
>> introducing new encoding justifies the additional control plane, 
>> protocol and platform efforts
>>
>> In fact if we would get to the consensus of using SRH with SID & BSID 
>> to be of fixed 20 bits it can reuse a lot of mechanism build for 
>> sr-mpls in any commercial router.
>>
>>  It is just a bit amazing that insertion of EHs into IPv4 would be 
>> less problematic that in the case of IPv6 :) Maybe due to allowed 
>> fragmentation.
>>
>> As to the host dropping packets due to unknown protocol - let's 
>> observe that SR domain would clean such EH before passing packets 
>> further.
>>
>> Many thx,
>> R.
>>
>>
>>
>> On Sat, Sep 7, 2019 at 1:14 PM Mark Smith <markzzzsmith@gmail.com 
>> <mailto:markzzzsmith@gmail.com>> wrote:
>>
>>     On Sat, 7 Sep 2019 at 19:56, Robert Raszuk <robert@raszuk.net
>>     <mailto:robert@raszuk.net>> wrote:
>>     >
>>     > > It's tempting to write up SR over IPv4
>>     >
>>     > You don't have to write anything ... it is already written and
>>     looks like moving fwd :)
>>     >
>>     > https://tools.ietf.org/html/draft-ietf-mpls-sr-over-ip-07
>>     >
>>
>>     That's tunnelling MPLS over SR over IPv4. I'm talking about native SR
>>     over IPv4 e.g. "SRv4".
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests:https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>