Re: New Approach For Discussing IPng

Tom Beecher <beecher@beecher.cc> Mon, 19 April 2021 13:45 UTC

Return-Path: <beecher@beecher.cc>
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 2AE763A3225 for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 06:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=beecher.cc
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 XIn6L8AJDCBG for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 06:45:24 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 12B713A3224 for <ietf@ietf.org>; Mon, 19 Apr 2021 06:45:23 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id 101-20020a9d0d6e0000b02902816815ff62so26673104oti.9 for <ietf@ietf.org>; Mon, 19 Apr 2021 06:45:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beecher.cc; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2gbzdzzl6GbBtRJ2djklyjwYcypAVxVQsZKv7T3qtV8=; b=CrvGgBUF/T3GOWv76lbjF0GPKl07qFX1samOAgZxCBQOEgstv4822hwyfEINqce6s4 wdolEWDHIVaXsdxDGQKnpA3LoVMfEA252Tv7ok36M5pUMy7TXJDXflHpKrQxlxSrYWnH Grq9TTrNvSNSOugHNO3u6wCuBBhh/CrZ5Tp6RBpLLQ14kvvBniXq+Exvn9GnONCMK2j3 egA30w3AsmwnyrfOQGzJxOAHKu3ouzHnhQcBSNggNIOu08j4lQz9R9NFa6JblF2k4Jjt ZevPqROs7P4y0ktVvqMVh66AOks9VynVMfuZIcGZkrN1847W2YnLAaBR0CMAfdpfJwZT DD4w==
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=2gbzdzzl6GbBtRJ2djklyjwYcypAVxVQsZKv7T3qtV8=; b=YBukfvbzZGjODRItOvmk6No9TuJwtijGpBaGY5flSzlt4+dgn7Svod9bJ+g9vkvBZ5 kDG5sfua31rLBLtoQgtkeK0Ud++uvRW6DjwmOvDIjnFYQ1h34h5AdU3UwsilSyGYEqTY 33rSWQ11VtChBuJKGuuS8eHGDU/d37e8sPzrcljRxSuQ9wwxpSchBlSYN/etvIknncA5 sce/Ib1b6hkrWWTHJHLveTGVC+Rqiu6E7Rg5RbPIdF0FXlS2m3LAqRejpRNut0CNYnfY 4sO6YbGX6urTPiYbHhtSu+tISid1/+838iZ8xSWQHbLSzftxGt6hEM0NF0NG82EAfmVG LYww==
X-Gm-Message-State: AOAM532AmXzCtkQTfmDASptD5SP5/Bj+ABIUqdCZ8qkQWIwtc4Kq7bgj Wni6l8HdE0Y6W6z32OjQG4rzmHO0mU0C6qplVSw+4g==
X-Google-Smtp-Source: ABdhPJz/lBJSm6wZ9wDXtbjvDlUyk1JIi5tkAWtfHu23wVPc/kO5ZBFzMGfXsysIlwgMlYJ9kOqYb9Va1Xu9i4u4lpg=
X-Received: by 2002:a05:6830:16c8:: with SMTP id l8mr4652621otr.56.1618839922357; Mon, 19 Apr 2021 06:45:22 -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> <AM7PR03MB6594B91C2C731546BC059D1CAE499@AM7PR03MB6594.eurprd03.prod.outlook.com>
In-Reply-To: <AM7PR03MB6594B91C2C731546BC059D1CAE499@AM7PR03MB6594.eurprd03.prod.outlook.com>
From: Tom Beecher <beecher@beecher.cc>
Date: Mon, 19 Apr 2021 09:45:11 -0400
Message-ID: <CAL9Qcx7E8fx4fEsnbxogXpAeut9h_ZzknCfu_hLRrUQWqEXcAQ@mail.gmail.com>
Subject: Re: New Approach For Discussing IPng
To: Khaled Omar <eng.khaled.omar@outlook.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Phillip Hallam-Baker <phill@hallambaker.com>, Joe Touch <touch@strayalpha.com>, Lloyd W <lloyd.wood@yahoo.co.uk>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000085472b05c0538a3d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yGLbVv4OL7iEaJinT7M4LuDVJkg>
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 13:45:29 -0000

>
> How VPN tunnels works in reality?! I think it works by first encrypting
> the original packet, THEN, "adding a new source and destination addresses
> to the packet", this is what I'm asking for to allow IPv10 concept works.
>

That would be an accurate description of tunnel mode IPSEC. If that is what
you are proposing, numerous v4/v6 tunneling standards are already defined
and are well developed.

On Mon, Apr 19, 2021 at 7:30 AM Khaled Omar <eng.khaled.omar@outlook.com>
wrote:

> Hi Brian,
>
> >> 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.
>
> How VPN tunnels works in reality?! I think it works by first encrypting
> the original packet, THEN, "adding a new source and destination addresses
> to the packet", this is what I'm asking for to allow IPv10 concept works.
>
> Regards,
>
> Khaled
>
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: Monday, April 19, 2021 6:53 AM
> To: Phillip Hallam-Baker <phill@hallambaker.com>; Joe Touch <
> touch@strayalpha.com>
> Cc: Lloyd W <lloyd.wood@yahoo.co.uk>; IETF Discussion Mailing List <
> ietf@ietf.org>
> Subject: New Approach For Discussing IPng
>
> 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):
> 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.
>
> There's little prospect that things would be different if we repeat the
> experiment.
>
> > The whole point of the Internet is the narrow waist is really simple.
>
> As it is written: "The function in question can completely and correctly
> be implemented only with the knowledge and help of the application standing
> at the endpoints of the communication system. Therefore, providing that
> questioned function as a feature of the communication system itself is not
> possible."
>
> (What about deterministic networking? Indeed, that requires support as a
> feature of the communication system. Therefore, it will never happen across
> the Internet as a whole.)
>
>     Brian
>
>
>
>