Re: 6MAN Agenda for IETF 109

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 08 November 2020 18:43 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 ACC813A0799 for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 10:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.67
X-Spam-Level: *
X-Spam-Status: No, score=1.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, FREEMAIL_REPLY=1, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=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 IaQPn-7LQd-7 for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 10:43:30 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 E1D2C3A0779 for <ipv6@ietf.org>; Sun, 8 Nov 2020 10:43:29 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A8IhSvs037514 for <ipv6@ietf.org>; Sun, 8 Nov 2020 19:43:28 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 13C9A203A08 for <ipv6@ietf.org>; Sun, 8 Nov 2020 19:43:28 +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 09C6A202771 for <ipv6@ietf.org>; Sun, 8 Nov 2020 19:43:28 +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 0A8IhRaE025464 for <ipv6@ietf.org>; Sun, 8 Nov 2020 19:43:27 +0100
Subject: Re: 6MAN Agenda for IETF 109
To: ipv6@ietf.org
References: <CABNhwV3yxvK-ukHxe9Abaso1daVKO1qreFxiQ981=S0gBPorqA@mail.gmail.com> <1A06280C-97EE-4B0A-9E71-ACAAFEA37399@employees.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c90aca53-d0f7-efc9-3937-99abed392421@gmail.com>
Date: Sun, 08 Nov 2020 19:43:27 +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: <1A06280C-97EE-4B0A-9E71-ACAAFEA37399@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/KDp3T5QjBBbJR_gUAWUkFpOhIF8>
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:43:32 -0000

So we end up with two presentations in two WGs about the same problem?

Alex

Le 08/11/2020 à 19:16, Ole Troan a écrit :
> I would expect the v6ops chairs would like a presentation, but let me 
> not presuppose how they want to run that session.
> 
> Cheers
> Ole
> 
>> On 8 Nov 2020, at 19:00, Gyan Mishra <hayabusagsm@gmail.com> wrote:
>>
>> 
>>
>>
>> On Sun, Nov 8, 2020 at 12:58 PM Gyan Mishra <hayabusagsm@gmail.com 
>> <mailto:hayabusagsm@gmail.com>> wrote:
>>
>>
>>
>>     On Sun, Nov 8, 2020 at 12:35 PM <otroan@employees.org
>>     <mailto:otroan@employees.org>> wrote:
>>
>>         Hi Gyan,
>>
>>         > As we have had thus far and ongoing quite a bit of
>>         discussion on variable slaac can we add this to the agenda. 
>>         We can also expand the scope of discussion as to all use cases
>>         related to slaac longer prefix lengths and how it can be
>>         beneficial per the “Extending a /64” new thread.  I can start
>>         the discussion and we can take it from there.
>>
>>         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.
>>
>>
>>         Gyan> Agreed but G-Extend the 64 bit boundary
>>
>>
>>
>>         <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>.
>>
>>
>>         Gyan> Sounds good.  Will have the draft authors join in on the
>>     discussion.
>>
>>
>>     Should I put together a presentation for the discussion or will it 
>> be ad-hoc.
>>
>>
>>
>>         Best regards,
>>         Ole
>>
>>     -- 
>>
>>     <http://www.verizon.com/>
>>
>>     *Gyan Mishra*
>>
>>     /Network Solutions A//rchitect /
>>
>>     /M 301 502-1347
>>     13101 Columbia Pike
>>     /Silver Spring, MD
>>
>>
>> -- 
>>
>> <http://www.verizon.com/>
>>
>> *Gyan Mishra*
>>
>> /Network Solutions A//rchitect /
>>
>> /M 301 502-1347
>> 13101 Columbia Pike
>> /Silver Spring, MD
>>
>>
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>