Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc7437bis-07: (with DISCUSS and COMMENT)

Barry Leiba <barryleiba@computer.org> Mon, 01 July 2019 00:20 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3C41201DA; Sun, 30 Jun 2019 17:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, 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 TQtUkHtXmavp; Sun, 30 Jun 2019 17:20:15 -0700 (PDT)
Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (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 3247D1201E3; Sun, 30 Jun 2019 17:20:15 -0700 (PDT)
Received: by mail-io1-f47.google.com with SMTP id u19so16198405ior.9; Sun, 30 Jun 2019 17:20:15 -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:cc; bh=Ky5aEgAjhQaLZMb5t67pkeev2uWF2OJL/v5qQX5sUMc=; b=ZIr5tPWRRe6eQwiVhKn8BNkGr05F+HBlRl55WoTzVKD7bxdGjLLOJq53SYdvJeUFm8 pNR4nliV5kr5R/1O2zUxK97FQPIE9W5oa++ep1+b/4F40WOzZnp2C9RmaNAbnpeYX/c3 0yvg3KmO3b359XZKUvkjK+NQSlDWRu+qrdOblTzS5EbiCnrQhxoad4L1yegB2WjlOSyA ErfjsTWPZM8yr8fi7bW9lXC1gb16C9UQfKkQ3vXD8bPS7BZ1ecaNKZyvy3nc7jaKz5+u Yjf4xPz9fFibUqfIlW/spExKj96xAPtWznXVdlmbYt77PEZ5dQM6G1OjH35JLCP96j2e 66uQ==
X-Gm-Message-State: APjAAAUWRIhFIz8Rc7m7FLwOaMTOhFNBz+AH5nMWIxJ7MYHWi+bgpboi BkgjZT8CY/kZwy5m5t+pi2VHNdWgA+0HBRFhB0g=
X-Google-Smtp-Source: APXvYqwGJyLMf7vbilBQb32Irc61vcRHaEuw57LeGbal0AiQU60SAj4z4Y1La5RimgnTSDRAA1bUTz3Ga9HATOa90Ls=
X-Received: by 2002:a02:b710:: with SMTP id g16mr24862699jam.88.1561940414067; Sun, 30 Jun 2019 17:20:14 -0700 (PDT)
MIME-Version: 1.0
References: <156141779186.17522.6942767062911073521.idtracker@ietfa.amsl.com> <1C131171-0ABE-4DB1-BEB7-03E765B1E6C6@cooperw.in> <CALaySJKHut1EL_eKQ5rhSXFeF6_+EizwcHdhxhieRy3D3dzQwg@mail.gmail.com> <F15F78D3-2257-4F1B-B832-D9C7CC47E512@gmail.com> <CALaySJK+=W6FwMcHJ-nuyZFmvukMN_GUh6qDAWvwHnizyZqy9A@mail.gmail.com> <4710C519-37CC-4586-83E7-02776889370F@gmail.com> <CALaySJ+1q4jrFk9+g=kwk86Lc=GMpFniFWXoNYsidOL6F_uZag@mail.gmail.com> <cc578052-6be1-6a5a-f05f-2bf38d3210dc@gmail.com>
In-Reply-To: <cc578052-6be1-6a5a-f05f-2bf38d3210dc@gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Sun, 30 Jun 2019 20:20:03 -0400
Message-ID: <CALaySJ+64zmmbtYy4P+ke9q78MdrKitDCNk=8ErtoD7HzeLY_Q@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IASA 2 WG <iasa20@ietf.org>, Alissa Cooper <alissa@cooperw.in>, iasa2-chairs@ietf.org, IESG <iesg@ietf.org>, draft-ietf-iasa2-rfc7437bis@ietf.org, Jon Peterson <jon.peterson@team.neustar>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/OSN8o3DlBQ9vM7U3PerUl6wayIM>
Subject: Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc7437bis-07: (with DISCUSS and COMMENT)
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2019 00:20:17 -0000

Hi, Brian.

> > Maybe what I really don't understand is the exception that allows the
> > replacement process to be done before the vacancy is announced.
>
> I don't believe that is the intention. I think the intention was to describe
> exactly what happened in 2013:
> https://mailarchive.ietf.org/arch/msg/ietf-announce/ogw1xIIrxXN-ExzUmordL1uXetk
> https://mailarchive.ietf.org/arch/msg/ietf-announce/EwBi_PHbPs3a4CqJwYDjObb2VSc
> i.e. an hour or so after an IAB member was announced as a new AD, NomCom
> started the mid-term vacancy process. (I assume that in the intervening hour,
> the IAB member resigned and the IAB duly informed NomCom of the vacancy.)
>
> In other words "The process [...] of filling the seat" includes a call for
> nominations, as it did in 2013. (The fact that it happened in May rather
> than before the MArch IETF is beside the point, I think.)
>
> I think that in this sentence:
> "The resignation may remain confidential to the IAB,
>  IAOC, IESG, and nominating committee until the confirmed candidate is
>  announced for the new position."
> the phrase "the new position" means (in the 2013 case) the Transport AD
> position. Filling in the unknowns, the sentence reads:
> "Spencer's resignation from the IAB may remain confidential to the IAB,
>  IAOC, IESG, and nominating committee until Spencer is announced as
>  the new Transport AD."

Sure, but that's not what the text says:

   It is consistent with these rules for the announcements of a
   resignation of a sitting member of the IAB and of the confirmed
   candidate for the mid-term vacancy created by that sitting member on
   the IAB to all occur at the same time

Putting the 2013 specifics into that:

   It is consistent with these rules for the announcements of a
   resignation of a Spencer from the IAB and **of the confirmed
   candidate to replace Spencer** to all occur at the same time

That second part is very different from the announcement of Spencer as
TSV AD (which I agree is no problem at all).  Having it as I've
inserted the 2013 specifics implies that Spencer's replacement on the
IAB was selected without letting community know that it was happening.

Barry