IETF Logo Mail Archive

Re: [Add] Proposed charter and BoF request for IETF 106

Michael Richardson <mcr@sandelman.ca> Thu, 10 October 2019 11:46 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB57120C0E for <add@ietfa.amsl.com>; Thu, 10 Oct 2019 04:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Edp7PeOVDCgd for <add@ietfa.amsl.com>; Thu, 10 Oct 2019 04:46:18 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EF19120C0A for <add@ietf.org>; Thu, 10 Oct 2019 04:46:18 -0700 (PDT)
Received: from dooku.sandelman.ca (business-178-015-097-209.static.arcor-ip.net [178.15.97.209]) by relay.sandelman.ca (Postfix) with ESMTPS id DE4411F47F for <add@ietf.org>; Thu, 10 Oct 2019 11:46:16 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 4D565346B; Thu, 10 Oct 2019 13:47:05 +0200 (CEST)
From: Michael Richardson <mcr@sandelman.ca>
To: add@ietf.org
In-reply-to: <7B345BCE-F23A-47F7-95EB-2201F57F84E7@fugue.com>
References: <CALaySJ+r0WAt+=33cV73q88KKc+gj3O6LtfcLxFOhDjcLP+U3A@mail.gmail.com> <7B345BCE-F23A-47F7-95EB-2201F57F84E7@fugue.com>
Comments: In-reply-to Ted Lemon <mellon@fugue.com> message dated "Wed, 09 Oct 2019 10:16:59 -0400."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 Oct 2019 13:47:05 +0200
Message-ID: <4265.1570708025@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/NQGUpnefxUmWLuef3ACd_w32O8Q>
Subject: Re: [Add] Proposed charter and BoF request for IETF 106
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2019 11:46:20 -0000

Ted Lemon <mellon@fugue.com> wrote:
    > If the proposal was half baked due to hurry, maybe the right approach
    > is to wait until March. If you really think it’s urgent, you could do
    > it as a virtual BoF in January.  That’s what the IESG would say to me
    > if I proposed something that was too rushed.

I think that we need to have the WG-forming BOF at 106, so that in March (which
will be better attended) we can actually hit the ground running with a WG.

Most of the WG charter arguments are going to happen on the list.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email