Re: 6MAN Agenda for IETF 109

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 08 November 2020 18:35 UTC

Return-Path: <alexandre.petrescu@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 B199F3A0639 for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 10:35:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.67
X-Spam-Level:
X-Spam-Status: No, score=0.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=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 GoZy_SN3D6XC for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 10:35:09 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DB4B3A05D0 for <ipv6@ietf.org>; Sun, 8 Nov 2020 10:35:08 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A8IZ6Cm016861 for <ipv6@ietf.org>; Sun, 8 Nov 2020 19:35:06 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id EEA2C202713 for <ipv6@ietf.org>; Sun, 8 Nov 2020 19:35:05 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E49AA203B75 for <ipv6@ietf.org>; Sun, 8 Nov 2020 19:35:05 +0100 (CET)
Received: from [10.11.240.104] ([10.11.240.104]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A8IZ5Yx024645 for <ipv6@ietf.org>; Sun, 8 Nov 2020 19:35:05 +0100
Subject: Re: 6MAN Agenda for IETF 109
To: ipv6@ietf.org
References: <79251783-8235-4EE6-8659-66C8E52735A3@gmail.com> <CABNhwV2o22usnWm=jbkDZ3Gdu9vACyBPAQ1kGj+Pyaxp1Y5z=A@mail.gmail.com> <D9BADCAB-2342-4E29-9002-25842E884C77@employees.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <db0386db-b53a-74e5-fa89-5e1b6ca91431@gmail.com>
Date: Sun, 08 Nov 2020 19:35:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.1
MIME-Version: 1.0
In-Reply-To: <D9BADCAB-2342-4E29-9002-25842E884C77@employees.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nH4ye2KXx5KEyMFz6V-aU0mH6gU>
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: Sun, 08 Nov 2020 18:35:11 -0000


Le 08/11/2020 à 18:35, otroan@employees.org a écrit :
[...]
> The "Extending a /64" thread (which I in hindsight see is poorly 
> named) is not about longer prefix lengths. It is about exploring 
> solutions to the problem of extending a network assigned with a 
> single /64 with multiple links.

We come down to playing with terms.

I understand one might want to stay within the IID-64 square.

In that sense, the Variable SLAAC might also be driven towards a new
configuration mechanism where the IID is still 64 but some sub-IIDs and
sub-prefixes might act differently.  This new term 'Sub-IID' is made to
accommodate.

In that sense, yes, the problem of "Extending a /64" is a relevant
problem, even if one names it otherwise.

A name of the problem could also be "64-bound Extended Networking".

Alex

> 
> <chair-hat>Bob and I had a discussion with the chairs of v6ops,
> where we agreed to have the "what is the operational problem"
> discussion over in v6ops.</chair-hat>.
> 
> Best regards, Ole 
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative 
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>