Re: FW: Next steps discussing Routing Challenges of Semantic Addressing
Nick Hilliard <nick@foobar.org> Fri, 07 May 2021 11:57 UTC
Return-Path: <nick@foobar.org>
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 631083A1E10; Fri, 7 May 2021 04:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 pvGIVyk6wJjc; Fri, 7 May 2021 04:57:44 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43E293A1DFB; Fri, 7 May 2021 04:56:48 -0700 (PDT)
X-Envelope-To: 6man@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 147BuiEX022671 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 May 2021 12:56:44 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
Subject: Re: FW: Next steps discussing Routing Challenges of Semantic Addressing
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Robert Raszuk <robert@raszuk.net>, 6man <6man@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
References: <4f22f9591c0a48d1a351f52318cd3319@boeing.com> <CAOj+MMHxh5UmUsPOmun+XGPcBK0=AGLzSpx7Nemni1WzPnta9w@mail.gmail.com> <0e347fa8-0071-ab1f-9872-5611a2128fcb@foobar.org> <c1250d72-2133-95a2-c74b-8649d5aec0f3@gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <c50ade33-c754-da95-bd71-2fa2d106c9ef@foobar.org>
Date: Fri, 07 May 2021 12:56:42 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.48
MIME-Version: 1.0
In-Reply-To: <c1250d72-2133-95a2-c74b-8649d5aec0f3@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/E1p4Rq0gliIT7EugIwYV9TUAhWo>
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: Fri, 07 May 2021 11:57:47 -0000
Brian E Carpenter wrote on 06/05/2021 23:21: > On 07-May-21 08:34, Nick Hilliard wrote: >> Robert Raszuk wrote on 06/05/2021 21:04: >>> May I ask why this topic is being taken outside of IETF ? >>> >>> Is it so difficult to create a new list ? Or is this so off topic to say >>> ipv6 or 6man lists that it can not be discussed there ? >> >> briefly: >> >> 1. yes >> 2. no >> 3. yes > > 4. It's an IRTF topic anyway. On the separate mailing list thing, these are ideas which need a bit of blue-sky thinking, so there really isn't an issue using a separate mail server for it. The most productive discussions often happen with wild ideas thrown around over a coffee with notes written on the back of a paper napkin, so neither the IRTF nor the IETF need to feel insecure that any initial discussions are happening elsewhere. If there's an outcome which is worth pursuing, that'll be the time when people will naturally move it over to I*TF. Nick
- FW: Next steps discussing Routing Challenges of S… Manfredi (US), Albert E
- Re: FW: Next steps discussing Routing Challenges … Robert Raszuk
- Re: FW: Next steps discussing Routing Challenges … Alexandre Petrescu
- Re: FW: Next steps discussing Routing Challenges … Nick Hilliard
- Re: FW: Next steps discussing Routing Challenges … Brian E Carpenter
- RE: FW: Next steps discussing Routing Challenges … Dirk Trossen
- Re: FW: Next steps discussing Routing Challenges … Nick Hilliard
- Re: FW: Next steps discussing Routing Challenges … Robert Raszuk
- Re: FW: Next steps discussing Routing Challenges … Nick Hilliard