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

Barry Leiba <> Tue, 09 July 2019 19:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D9719120362; Tue, 9 Jul 2019 12:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.107
X-Spam-Status: No, score=-0.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.247, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, PDS_NO_HELO_DNS=1.295, 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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rIC4vAg7cRGY; Tue, 9 Jul 2019 12:28:20 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 82F50120291; Tue, 9 Jul 2019 12:28:20 -0700 (PDT)
Received: by with SMTP id i10so45587903iol.13; Tue, 09 Jul 2019 12:28:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=UtCtT5TUoSMxeTd7OIL/I8w7tuEBWboAjhTRE85u5gg=; b=EgfzNf5oaYHxin6igEsjwo7wTRx1RAqbyir88pVSD07h3iquXZtZBmvPVZ4wKVZX/H c73k401xEVFBDPq5taNZM8oj1OwzB82kEN5VNxmrHBJ/OiCqozD+BqQKELiZazHtY91c ue1HlSlpAD2Ak+THIzBTYvDmpjvD+Mj6RpFo8RtMuuThJAncj9dZRaJFo1WlWQq2hwLH xOxORWPexQPvpKpKkvUaQo2lRTmpct+sfbgFBOM14nZNRQdJ2tIdVxiI+REGeo8zgW7+ +YJRC8T2lBCjcKfms8dzHiEgcOrwmGYhgYJ0hTM6/u33NkG8SU5t+cbHlm26v/acocPc NYMg==
X-Gm-Message-State: APjAAAWgxeuBywimlULWv7sb9mhkA8488JP689vFkGKQj/8gJZCXht4t NgfKAGrFx1RhICFno2YxL2w3eoXzoOt7h8yScoc=
X-Google-Smtp-Source: APXvYqwS2nFEMCqWjXK1JBHeOTORZn2GskG452H24DdjsJvfbqsCldyyQY/yCpvgqmZWlOTiPDlVrDpbnj49sEmSPOQ=
X-Received: by 2002:a02:c80d:: with SMTP id p13mr30166938jao.59.1562700499331; Tue, 09 Jul 2019 12:28:19 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Barry Leiba <>
Date: Tue, 9 Jul 2019 15:28:07 -0400
Message-ID: <>
To: Alissa Cooper <>, Bob Hinden <>
Cc: IASA 2 WG <>,, IESG <>,, Jon Peterson <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc7437bis-07: (with DISCUSS and COMMENT)
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?= <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 09 Jul 2019 19:28:22 -0000

I have added my suggested text, below, to my ballot and moved the
whole thing from the DISCUSS section to the COMMENT section.  I've
also changed my ballot to "yes", reflecting the importance I see in
having this document approved.

I'd still like to see the clarification I propose made, but I'm OK
with accepting the judgment of Bob and Alissa, and we now have
something on record to point to if there should actually be any
confusion about applying the IAB-vacancy exception before the whole
process is revised again.

I'll repeat that I appreciate the work in making the updates here, and
the discussion that finally led to my understanding the issue that I
had found unclear.


On Mon, Jul 8, 2019 at 11:24 AM Barry Leiba <> wrote:
> > The exception in the document seems consistent with the following hypothetical situation:
> >
> > The nomcom for year 2035-2036 has been seated. Alice has been on the
> > IAB for one year. She is also a nominee for an AD position in the Foo
> > area. There are also six open positions on the IAB.
> >
> > The nomcom does its deliberations and selects Alice to be the next Foo
> > AD. They also select six people to serve on the IAB. They send the IESG
> > slate to the IAB for confirmation and the IAB, with Alice recused,
> > confirms the slate. Alice resigns from her position on the IAB. The IAB
> > chair informs the nomcom of the mid-term vacancy created by Alice
> > resigning. The nomcom selects a seventh candidate to serve on the IAB
> > (since they have a pool of nominees and filling the vacancy is a
> > responsibility of the 2035-2036 nomcom) and sends the IAB slate to the
> > ISOC BoT for confirmation. The announcements of the confirmed slates
> > and of Alice’s resignation from the IAB then happen simultaneously.
> >
> > I think this is different from the 2013 situation because all of the
> > events are taking place during the established nomcom timeline for
> > getting people seated by the first IETF meeting of the year, so the IAB
> > candidate pool for 2036 is still “active,” so to speak.
> OK... then you're saying that in the case that the NomCom has not yet
> announce the IAB slate, the exception says that they can fill an extra
> IAB position without advertising that to the community, because
> there's already a bunch of people who put their names in for IAB
> positions and there's no reason to think that knowing that there's one
> more open position will matter.
> I get that, and, understanding it, I do agree that that was the intent
> of that text.
> May I suggest, then, the following edit to make it clear?:
>    However, the following exception is permitted in the case where the
>    candidate for an open position is currently a sitting member of the
>    IAB.
>    However, an exception is permitted in the case where the
>    candidate for an open position is currently a sitting member of the
>    IAB.  Because there is already a pool of candidates for a set of IAB
>    positions, the NomCom does not a need to inform the community
>    explicitly that one more position is becoming available, so par of the
>    process can overlap.
> Tweak as necessary, but does that work?  Alissa, Bob, others, what do you think?
> Barry