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

Barry Leiba <> Mon, 08 July 2019 14:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 55C8E12027D; Mon, 8 Jul 2019 07:54:15 -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 ZpJFuJz4_2LS; Mon, 8 Jul 2019 07:54:13 -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 18FD1120285; Mon, 8 Jul 2019 07:54:02 -0700 (PDT)
Received: by with SMTP id k20so35828186ios.10; Mon, 08 Jul 2019 07:54:02 -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; bh=jW4kQ6Wh3eerleZSEii/lexzRJS9jUtx3lF1Hwz/NDY=; b=IDOAmuwEeYf/fGWqda4VtbNKCc7T5twoCnmmq085g+s+Q9EOXGZ3bhPIcCQToUO+ck s/L/PyA9FSZKWg6+BrIWaE2ZuHbdayCmyJnWFhL2CjHyoq2MKonJITN5j9gGTfLiO1TK +Rd1rrpt+/Yk/PxHnjhdlKcQOc0nJBI3HGemR0ss2l9U2AoR6fbSvOgL/7vcQAxwfQ70 0uzNTrU9HTvBgacr5kxjZ94lGWHbLs0fMQVJJ93BY4S+ux1dHoGM0WjQsJGSmQnn7BI5 m4MlzW8FsjRrWNobnXfo8KYj+pbjyuOVCg9Sv56/vwWzL2xFhJx79jmnIAV0EzUK/syg Qx4A==
X-Gm-Message-State: APjAAAXU6/xHU2jY/lmZyR0R/8bOfHHquJ5E3VBU2UrR+Y5eqHBR2fN3 dHCBq0YBCS/9rCknAkfg2B6IlBhEZJu7+HSVAIo=
X-Google-Smtp-Source: APXvYqzQ2kRWNBsJVP3v2hhXy6o01uA1kfcrWDtFK4l/qvHzsbC20LG3EVFTnPr5HH3RcdwaXHfBBYYv9DtyMgrob00=
X-Received: by 2002:a05:6602:2248:: with SMTP id o8mr19248744ioo.90.1562597640878; Mon, 08 Jul 2019 07:54:00 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Barry Leiba <>
Date: Mon, 8 Jul 2019 10:53:49 -0400
Message-ID: <>
To: Brian E Carpenter <>
Cc: Bob Hinden <>, IASA 2 WG <>, Alissa Cooper <>,, IESG <>,, Jon Peterson <>
Content-Type: text/plain; charset="UTF-8"
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: Mon, 08 Jul 2019 14:54:24 -0000

And, so, back to this.

Repeating from the other thread: my goal here is not to get in the way
of approving this very important document, nor to make any process
change.  My goal is to get clarity on something that I think is at
best unclear.

What "exception", exactly, is the text in the second half of Section
3.8 trying to make?  How is it possible for the NomCom to fill the
vacated IAB slot without informing the community that it's doing so?
And if it informs the community, how is it possible to do that without
announcing the resignation of the IAB member?

It's possible that the fix to this issue is simply a sentence that
better explains what's meant by "the following exception".  But the
following text doesn't make it clear to me, and instead seems
impossible to comply with.  Please help me understand.


On Sun, Jun 30, 2019 at 8:20 PM Barry Leiba <> wrote:
> 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:
> >
> >
> > 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