Re: FW: Next steps discussing Routing Challenges of Semantic Addressing
Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 06 May 2021 22:21 UTC
Return-Path: <brian.e.carpenter@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 1ECB03A0C2F; Thu, 6 May 2021 15:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 6NmY4W-ZzEf4; Thu, 6 May 2021 15:21:51 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 642F73A0C22; Thu, 6 May 2021 15:21:51 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id h20so4154143plr.4; Thu, 06 May 2021 15:21:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=k8j4qjUP9Im7bHoPqejYIOv3SEvXqJUtmnCieEqz+q0=; b=S+sQLV5Gxe4YLRMSPIgOFyAcdk1mDsQhua+5UP4O5iMn0MJOuSQFoqXvN3pBGF7lK1 Og66NtlutbdSfvODDfdpB/lap43Bg33x8OAVOsmP9GNXOYzTsJZTt9ikk0deA3vJqBFc u7ITJ4KoLWt1ehNXzeBhFnGrwNaTixFEZ/Cjcsak2XXAKKKwwq3QnGZCRUUs3VP5bi+H dpGS2WYRLqtAEmcWoi08+6Qd/81QGHgzO7vxv0FgVrH++KOOxRrkW98jg5K4M/GeKl/v iqZcVy3U8KAH8H9jlSZ+5DI5T8Pi6l8tgTg9n3zjsoIoVaFgkMkCOv3I/uM5992OKhXd zwfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=k8j4qjUP9Im7bHoPqejYIOv3SEvXqJUtmnCieEqz+q0=; b=OTqml8vpk75y+eXNsGHgFMEnza0hs9ovqmdEvAM+BAcG7TJHdGzdtK1uLOYdr9zzSE HaMH7cWu4MARUcQH0thes30eFjnGfm+uqTPWjeoAch53mqmmRqpxUyOX0lZ8J2YgEBXC fM8Vvhq+0N5bC4ei/vvADcA0kYoAmE4t6TCqdRWEGWjE52ULU/kk1Qv/8txXWM3nDsvd x3M0zoPos7QOVWS+MycONlKdZUe3/zY6Da71WKv+SOpwQhtgWv8NfgI47m7i4FDS67Lr uveWMNdGNUeL/m/pHUxyt40J0e0MuXXiEBl6/YNk0s38VjLI3Fojzrl2N4aN9+sAcjAN oIQg==
X-Gm-Message-State: AOAM5311Mo2tCWjt2DWVHQ/TjjmAzsAoB6Zx/197r4bu6qJhYonfQGCj LVdyynhNLQulRunNy5wc9f5leHzxESo=
X-Google-Smtp-Source: ABdhPJw5b5OuJ+h7FOcHzOWSa1hq78Wy5pWytJlE2f0xg6mx1lkKn6OWzHKbNU/Satw2o4GadSoeSA==
X-Received: by 2002:a17:902:bd09:b029:ec:7e58:a54a with SMTP id p9-20020a170902bd09b02900ec7e58a54amr6947912pls.62.1620339710424; Thu, 06 May 2021 15:21:50 -0700 (PDT)
Received: from [192.168.8.102] (115-189-97-205.mobile.spark.co.nz. [115.189.97.205]) by smtp.gmail.com with ESMTPSA id 12sm3035913pfz.205.2021.05.06.15.21.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 May 2021 15:21:49 -0700 (PDT)
Subject: Re: FW: Next steps discussing Routing Challenges of Semantic Addressing
To: Nick Hilliard <nick@foobar.org>, Robert Raszuk <robert@raszuk.net>
Cc: 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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <c1250d72-2133-95a2-c74b-8649d5aec0f3@gmail.com>
Date: Fri, 07 May 2021 10:21:44 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <0e347fa8-0071-ab1f-9872-5611a2128fcb@foobar.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/3BKGsassburh4LP8Zs2W6OhtG9w>
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: Thu, 06 May 2021 22:21:54 -0000
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.
Brian
- 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