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

Barry Leiba <barryleiba@computer.org> Thu, 10 October 2019 12:08 UTC

Return-Path: <barryleiba@gmail.com>
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 4E47B120C57 for <add@ietfa.amsl.com>; Thu, 10 Oct 2019 05:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.477
X-Spam-Level:
X-Spam-Status: No, score=-1.477 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.172, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 e6_R9x3QMF6w for <add@ietfa.amsl.com>; Thu, 10 Oct 2019 05:08:41 -0700 (PDT)
Received: from mail-io1-f46.google.com (mail-io1-f46.google.com [209.85.166.46]) (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 AE771120C34 for <add@ietf.org>; Thu, 10 Oct 2019 05:08:41 -0700 (PDT)
Received: by mail-io1-f46.google.com with SMTP id q1so13133225ion.1 for <add@ietf.org>; Thu, 10 Oct 2019 05:08:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=VnrcaPI2sg4PuuJ2Rrh7Tunpy0hygD50RgajMPiFB3I=; b=uejTakC4sPjezqV2pl0E6m0GB9OeSoaxcqR6gxzyi62/3aJRGEkzenqA2Lw+V9nvQM pdQtc33ZbS7qZ8ZbiN7jDBPFcfJ3/GaWtvp3/eUtnO/rBsEpLPy9J9lmSCslGz0XMKt6 4oA0R6Sm/b5ON+owKr1l1JIbBSivrqAn0x/FJDuJC0sSTOa2Ni0CCAMZEryFyELcLZXO 5o7o4/w3hPB1NcUiH6VRNLlAYt1aN+n/Xv9DdiBZsZiQBPctx419VEBTKgCb5sPvDHMg L7UtBchc+ko2D7WA9MPjyAIhtnyqeEV70hqdlbyGsWlU0IDEJyxdRidnMlY2cWaiLjiR MRkA==
X-Gm-Message-State: APjAAAWcYhRcS0rj4l2vBwNc+2laUjplNGICbTLzIoCSfKCHHPmU4luz 7aimYtpAgacFw0QxBpRKyhWpqIkZekNmyVsNUef5mN3F
X-Google-Smtp-Source: APXvYqzyVn5gagbNtwcz7Yo1h6t3p7I6JwxI+kAT/K+w0cXYpu/iZ7anbV5zk2w15N6Mfy88OCuZz70NaPmH6VhEU9A=
X-Received: by 2002:a92:490f:: with SMTP id w15mr379680ila.187.1570709320462; Thu, 10 Oct 2019 05:08:40 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.gmail.com> <4050.1570707771@dooku.sandelman.ca> <CALaySJ+6CwsDCkbT+hRrtmZjvmmfmVhVLeF=wS0WB2HHOKuebQ@mail.gmail.com>
In-Reply-To: <CALaySJ+6CwsDCkbT+hRrtmZjvmmfmVhVLeF=wS0WB2HHOKuebQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 10 Oct 2019 14:08:29 +0200
Message-ID: <CALaySJKVeKE3AjJWgV0rgWs_JavjcFMsoodbnUYr75+Tug14nw@mail.gmail.com>
To: ADD Mailing list <add@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/OoeyR9GiRZDN2WXmdJ-9aKs0Q7k>
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 12:08:43 -0000

Further following up on the more general thing (a BoF and charter proposal):

I'll stress that what's out there in the BoF wiki is a proposed
starting point -- it represents the IESG's trying to be helpful in
getting concrete charter discussion started.  It's not a finished
charter that's being lobbed at the community, and we *want* you to
discuss it and refine it, to throw parts of it away and add other
things that you need.  Please *do* start that discussion -- we'll
discuss it at the BoF, but we should wait until the BoF to work on it.
Have at it.

For that matter, even having a BoF in Singapore isn't set in stone: if
you, the community, think we've erred in assuming that a BoF now is
the best approach, and we get rough consensus on that, we can easily
cancel the BoF between now and then.

This really *is* out to the community for discussion and consensus.
Let's figure out, together, what the best way is to make progress on
useful documentation here.

Barry

On Thu, Oct 10, 2019 at 1:47 PM Barry Leiba <barryleiba@computer.org> wrote:
>
> The intention is to put work items into an appropriate working group,
> also considering the other work the relevant working groups are doing.
> That means that we'd have to look at where this (ABCD) charter ends
> up, whether we do or don't decide to recharter DPRIVE to tweak
> anything (we don't currently plan to, but it might turn out to be
> helpful), and how much workload there is here and there.
>
> So, yes, it's possible that things that might look like they fit into
> DPRIVE now would be better done in ABCD.  We'll have to make that
> decision after we see the final charter.
>
> Barry
>
> On Thu, Oct 10, 2019 at 1:42 PM Michael Richardson
> <mcr+ietf@sandelman.ca> wrote:
> >
> >
> > Barry Leiba <barryleiba@computer.org> wrote:
> >     > The IESG has worked up a proposal for a possible working group, which
> >     > we're tentatively calling "ABCD", for "Application Behavior Considering
> >     > DNS".  We can discuss the charter proposal here, and expect to approve
> >     > a working-group-forming BoF for Singapore.
> >
> >     > I realize that the charter proposal isn't going to please everyone (and
> >     > perhaps will please no one), but it's something that, at a first level
> >     > of review, the IESG accepts and will likely want to move forward with.
> >
> > Let me reply here before having read the thread.
> >
> > My impression is that ABCD will act as an architecture group for the problem
> > with DNSOP (OPS Area), DPRIVE (INT Area), and DOH (ART area) providing
> > specific technologies.
> >
> > It seems that many of the discovery/configuration protocols which are
> > appearing in DPRIVE from Tiru/Dan/me, and Tommy and Thomas would fit into
> > ABCD rather than DPRIVE.
> >
> > Please confirm that this is your intention?
> >
> > --
> > ]               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    [
> >