Re: 6MAN Agenda for IETF 109
Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 16 November 2020 23:08 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 DBCF13A163D; Mon, 16 Nov 2020 15:08:22 -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 37ejKDtYNeSZ; Mon, 16 Nov 2020 15:08:21 -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 2138B3A13EF; Mon, 16 Nov 2020 15:08:20 -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 0AGN8Ihw049125; Tue, 17 Nov 2020 00:08:18 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6A763207AAF; Tue, 17 Nov 2020 00:08:18 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 5A79B2063BA; Tue, 17 Nov 2020 00:08:18 +0100 (CET)
Received: from [10.11.240.254] ([10.11.240.254]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AGN8Hio023664; Tue, 17 Nov 2020 00:08:18 +0100
Subject: Re: 6MAN Agenda for IETF 109
To: Gyan Mishra <hayabusagsm@gmail.com>, IPv6 Operations <v6ops@ietf.org>
Cc: ipv6@ietf.org
References: <CABNhwV3yxvK-ukHxe9Abaso1daVKO1qreFxiQ981=S0gBPorqA@mail.gmail.com> <1A06280C-97EE-4B0A-9E71-ACAAFEA37399@employees.org> <CABNhwV2kZhZ6+CsyG-qMdNWyzefhCjpJ6MCrJty8quGA1tMZog@mail.gmail.com> <32b092f1-cb36-a3cc-ca47-ae8edf45e780@gmail.com> <CABNhwV1mDZt-yEvVt88v84M_4+E29wT5YtUdxadjPkYKX6612A@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <f59ba091-5b49-ba6a-af34-6a96da77af7e@gmail.com>
Date: Tue, 17 Nov 2020 00:08:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
MIME-Version: 1.0
In-Reply-To: <CABNhwV1mDZt-yEvVt88v84M_4+E29wT5YtUdxadjPkYKX6612A@mail.gmail.com>
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/u5UeJkkc4pXJnav6i6buYQ50qyo>
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, 16 Nov 2020 23:08:23 -0000
Just to make sure, The v6ops WG meeting will be on Thursday, the 19th, starting at 10am Paris time. I dont know what is your large city nearby, Gyan. I am saying this because I noticed 'IST' in the agenda, and I suppose that is not right. Alex Le 08/11/2020 à 21:01, Gyan Mishra a écrit : > > So we are already on the agenda for v6ops. > > Great! > > Gyan > On Sun, Nov 8, 2020 at 2:21 PM Alexandre Petrescu > <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote: > > (for my part, I think v6ops WG already has the problem statement draft > in the agenda; it was posted > https://www.ietf.org/proceedings/109/agenda/agenda-109-v6ops-04 > <https://www.ietf.org/proceedings/109/agenda/agenda-109-v6ops-04>) > > For more precision, the title in the agenda would add '... - A Problem > Statement'. > > So I think it's fine there. > > Alex > > Le 08/11/2020 à 20:06, Gyan Mishra a écrit : > > > > Fred & Ron > > > > See thread below. Should I put together a presentation for v6ops > per > > below to review the problem. > > > > Gyan > > > > On Sun, Nov 8, 2020 at 1:16 PM Ole Troan <otroan@employees.org > <mailto:otroan@employees.org> > > <mailto:otroan@employees.org <mailto:otroan@employees.org>>> wrote: > > > > 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 > <mailto:hayabusagsm@gmail.com> > >> <mailto:hayabusagsm@gmail.com > <mailto:hayabusagsm@gmail.com>>> wrote: > >> > >> > >> > >> > >> On Sun, Nov 8, 2020 at 12:58 PM Gyan Mishra > <hayabusagsm@gmail.com <mailto:hayabusagsm@gmail.com> > >> <mailto:hayabusagsm@gmail.com > <mailto:hayabusagsm@gmail.com>>> wrote: > >> > >> > >> > >> On Sun, Nov 8, 2020 at 12:35 PM <otroan@employees.org > <mailto:otroan@employees.org> > >> <mailto: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/ <http://www.verizon.com/>> > >> > >> *Gyan Mishra* > >> > >> /Network Solutions A//rchitect / > >> > >> /M 301 502-1347 > >> 13101 Columbia Pike > >> > <https://www.google.com/maps/search/13101+Columbia+Pike+Silver+Spring,+MD?entry=gmail&source=g <https://www.google.com/maps/search/13101+Columbia+Pike+Silver+Spring,+MD?entry=gmail&source=g>> > >> > >> /Silver Spring, MD > >> > <https://www.google.com/maps/search/13101+Columbia+Pike+Silver+Spring,+MD?entry=gmail&source=g <https://www.google.com/maps/search/13101+Columbia+Pike+Silver+Spring,+MD?entry=gmail&source=g>> > >> > >> > >> -- > >> > >> <http://www.verizon.com/ <http://www.verizon.com/>> > >> > >> *Gyan Mishra* > >> > >> /Network Solutions A//rchitect / > >> > >> /M 301 502-1347 > >> 13101 Columbia Pike > >> > <https://www.google.com/maps/search/13101+Columbia+Pike+Silver+Spring,+MD?entry=gmail&source=g <https://www.google.com/maps/search/13101+Columbia+Pike+Silver+Spring,+MD?entry=gmail&source=g>> > >> > >> /Silver Spring, MD > >> > <https://www.google.com/maps/search/13101+Columbia+Pike+Silver+Spring,+MD?entry=gmail&source=g <https://www.google.com/maps/search/13101+Columbia+Pike+Silver+Spring,+MD?entry=gmail&source=g>> > >> > >> > > -- > > > > <http://www.verizon.com/ <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 <mailto:ipv6@ietf.org> > > Administrative Requests: > https://www.ietf.org/mailman/listinfo/ipv6 > <https://www.ietf.org/mailman/listinfo/ipv6> > > -------------------------------------------------------------------- > > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org <mailto:ipv6@ietf.org> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > <https://www.ietf.org/mailman/listinfo/ipv6> > -------------------------------------------------------------------- > > -- > > <http://www.verizon.com/> > > *Gyan Mishra* > > /Network Solutions A//rchitect / > > /M 301 502-1347 > 13101 Columbia Pike > /Silver Spring, MD > >
- 6MAN Agenda for IETF 109 Bob Hinden
- Re: 6MAN Agenda for IETF 109 Gyan Mishra
- Re: 6MAN Agenda for IETF 109 otroan
- Re: 6MAN Agenda for IETF 109 Gyan Mishra
- Re: 6MAN Agenda for IETF 109 Gyan Mishra
- Re: 6MAN Agenda for IETF 109 Ole Troan
- Re: 6MAN Agenda for IETF 109 Alexandre Petrescu
- Re: 6MAN Agenda for IETF 109 Alexandre Petrescu
- Re: 6MAN Agenda for IETF 109 Gyan Mishra
- Re: 6MAN Agenda for IETF 109 Gyan Mishra
- Re: 6MAN Agenda for IETF 109 Alexandre Petrescu
- Re: 6MAN Agenda for IETF 109 Gyan Mishra
- Revised 6MAN Agenda for IETF 109 Bob Hinden
- Re: Revised 6MAN Agenda for IETF 109 Bob Hinden
- Re: 6MAN Agenda for IETF 109 Alexandre Petrescu
- Re: 6MAN Agenda for IETF 109 Gyan Mishra