Re: New Approach For Discussing IPng

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 19 April 2021 14:43 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 271B93A3407 for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 07:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.499
X-Spam-Level:
X-Spam-Status: No, score=0.499 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 Oz1kaXTh0uZX for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 07:43:44 -0700 (PDT)
Received: from mail-yb1-f172.google.com (mail-yb1-f172.google.com [209.85.219.172]) (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 3E16A3A3408 for <ietf@ietf.org>; Mon, 19 Apr 2021 07:43:41 -0700 (PDT)
Received: by mail-yb1-f172.google.com with SMTP id c195so39017925ybf.9 for <ietf@ietf.org>; Mon, 19 Apr 2021 07:43:38 -0700 (PDT)
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=bjNRfUmRKrawWqErqgDZNk5AkNZkuQjShMjRxHMho7c=; b=jV5WdvvAzlK1wRvsaco6mbnRf/LmR+jUYcTtY6bh6c5QFwMrVApjnDFFr+Cg193LQO gUVL/rZrNM7kufgkckCyT34tK0N7gqn861FjkXgVy6i5cpNs/hK+SfYkhwbRzHfaC19W u6XXw+G0UE/wnc2Kef2Ov1gWYg81UDrF9XppEZ38h1vlcJsugB9cIjzHs+mUt4tE1ysm eFuEWMXi7khSySmYYNxrxrzDVjtPWMpZ8Gmd7uW7KeURcNQjKNU5794qSb3vM9z2i/MW JUQ1iBlu4s2vLoR8VHcjK0Uc3e3o4rRMIHgdU93rJN20w5k7b5r/oGUYVVAW04y2XgDY Novw==
X-Gm-Message-State: AOAM53029HnuDeQZbGNYHSGA9YqGrRHI+VB62CEDItQYLdqNwys/VWG9 +B6SMrZKk84PcZLHdqqYqeSBSZoDlk0MsYaVPlg=
X-Google-Smtp-Source: ABdhPJyZwwMU8uRhpiFtl5FiVCzpzo5RxJVuwnxFYXJiCRWmd9o9rq95PxEcRiFXatwttKpnWdY7b5txVYt7Kh6TcbY=
X-Received: by 2002:a25:aa90:: with SMTP id t16mr16860230ybi.56.1618843403000; Mon, 19 Apr 2021 07:43:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+LwhV01N_uuFV8TfiyegpqDLmUYwxBcmkUAGG-HfJ7vSB+Q@mail.gmail.com> <989A5048-5EA8-479B-9231-D61B646E46F5@strayalpha.com> <CAMm+Lwhy0c6G7YLx8n7Ya7psG6VxcEckk-ncKg750rscuz-Yaw@mail.gmail.com> <89f2c243-433c-fa32-7dbf-c6392fde3da6@gmail.com>
In-Reply-To: <89f2c243-433c-fa32-7dbf-c6392fde3da6@gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 19 Apr 2021 10:43:10 -0400
Message-ID: <CAMm+Lwh_0xo_MjsN_BUWzOZeahFZ96SsQohjusiA=qYo5vhcgg@mail.gmail.com>
Subject: Re: New Approach For Discussing IPng
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Joe Touch <touch@strayalpha.com>, Lloyd W <lloyd.wood@yahoo.co.uk>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fba31005c05459c6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SbfSugfmWJGNO9AxluID8b34BxM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2021 14:43:49 -0000

On Mon, Apr 19, 2021 at 12:53 AM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> I've been keeping clear of this thread, but I think Phill does remind us
> of an important point (hence the small change of subject):
>

I have also been avoiding the issue raised, But the peculiar fact that
there is so little can be done at that level in the stack did seem worth
mention...

The only scope for innovation I can see in the space is to drop the source
address from data packets... And that is not one I care to attempt for
obvious reasons even when that is exactly what I am doing at the
transport/presentation layer.



> On 19-Apr-21 15:42, Phillip Hallam-Baker wrote:
> ...
> > We keep having people coming along making these suggestions for IPv8,
> IPv10, etc. etc. and the inventors never once seem fit to ask what is so
> different about their proposal it can't be done in IPv6.
>
> Back in 1994, it had become clear that deploying new header options in
> IPv4 across the Internet was in practice impossible, however well they
> worked in the lab. Extending IPv4 was therefore theoretically possible but
> impossible in reality. So we started IPv6.
>
> 27 years later, it has become clear that deploying new extension headers
> in IPv6 across the Internet is in practice impossible, however well they
> work in the lab.
>

Like multicast, the deployment requires substantial cooperation between
commercial entities which are competitors who won't even share their
network maps...

How can we expect Internet QoS to work when ISPs can't even be bothered to
police source packet address declarations on broadband network gateways?


I do not accept everyone's interpretation of 'end to end' but I do accept
that what happens on the network and what happens on the inter-network have
to be rather different. Einar Stefferud had a good presentation explaining
why this is the case.

Where I depart from end-to-end absolutism is that I recognize the network
interfaces as being places where 'different' things can and in some cases
MUST happen. I do not want every coffee pot on my network to have full
Internet access. That would be silly and break the least privilege
principle.