Re: Network Tokens and HBH option
Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Mon, 13 July 2020 18:06 UTC
Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 B39393A161E for <ipv6@ietfa.amsl.com>; Mon, 13 Jul 2020 11:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.631
X-Spam-Level:
X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.267, SPF_HELO_NONE=0.001, SPF_NONE=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 vN10qwWwtcwW for <ipv6@ietfa.amsl.com>; Mon, 13 Jul 2020 11:06:42 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDA113A1610 for <ipv6@ietf.org>; Mon, 13 Jul 2020 11:06:41 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1jv2qT-00007aC; Mon, 13 Jul 2020 20:06:29 +0200
Message-Id: <m1jv2qT-00007aC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Network Tokens and HBH option
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <CALx6S35sXX6J75dzQH=hN7pC5=9wZP=o6SqOMpivGPtOdo+YNQ@mail.gmail.com> <CAKD1Yr2iUA9SWJoNsDNFdNYDksKcw8YE2oSB1eJBfy9hiJXb4g@mail.gmail.com> <20200713153422.GZ42197@faui48f.informatik.uni-erlangen.de>
In-reply-to: Your message of "Mon, 13 Jul 2020 17:34:22 +0200 ." <20200713153422.GZ42197@faui48f.informatik.uni-erlangen.de>
Date: Mon, 13 Jul 2020 20:06:28 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qGpVhmg1IgF2iPRROJScXVc4u8c>
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, 13 Jul 2020 18:06:44 -0000
>We have started to look at some of the problems we see in the current network >headers in draft-bryant-arch-fwd-layer-ps. We have refrained in that spec >to do ore than problem analysis. Would love to see feedback about that doc. I think this draft could benefit from a companion draft that describes a good solution to the stated requirements that completely ignores IPv6 and IPv6-related constraints. A next step would be to have a draft that describes a solution within the IPv6 space and compares it to the best case solution. Then it gets interesting. An economic impact analysis of proposed changes to IPv6. Which parties need to change, and of those parties, which parties have little benefit from the new features. For example, if all hosts would have to change to support variable length IP address, then that is very unlikely to happen. If on other hand some link type would send IPv6 packets in a funny way, then that may be a lot easier to coordinate. One more thing, I think it would be nice to have a (working)group that creates protocols and prototype implementations without any constraints. In particular working prototypes are often required to convince people that some radical idea is actually worth the effort of making major changes to existing protocols.
- Network Tokens and HBH option Tom Herbert
- Re: Network Tokens and HBH option Erik Kline
- Re: Network Tokens and HBH option Yiannis Yiakoumis
- Re: Network Tokens and HBH option Lorenzo Colitti
- Re: Network Tokens and HBH option Yiannis Yiakoumis
- Re: Network Tokens and HBH option Toerless Eckert
- Re: Network Tokens and HBH option Tom Herbert
- Re: Network Tokens and HBH option Tom Herbert
- Re: Network Tokens and HBH option Philip Homburg
- Re: Network Tokens and HBH option Tom Herbert