Re: IAB agendas now public

Ted Hardie <ted.ietf@gmail.com> Thu, 06 September 2018 15:40 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB094130EBF for <ietf@ietfa.amsl.com>; Thu, 6 Sep 2018 08:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tyy7o9W73zSE for <ietf@ietfa.amsl.com>; Thu, 6 Sep 2018 08:40:50 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 55653130E9C for <ietf@ietf.org>; Thu, 6 Sep 2018 08:40:48 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id k12-v6so21338232oiw.8 for <ietf@ietf.org>; Thu, 06 Sep 2018 08:40:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=x7tJ9sc12eJlSzLa2bNt+dxGt778vFxKI4JqBji+43M=; b=TQCvBYPgefntIRpy2RqfWduffWmOPHh597L51kVI53rjDHuz0E6sW4w3/l1rxRRkr3 RF51xpWyMo26koMwSOzbRkzH+snH3pppFmhk7C1upa5OFrbwZ2QyNjLO8rspezUt1Yle givp7pMzdXo55MlfMe/ENAqtl2ZMnTmc6qqd0T5zSz/8im8TIIZpLhDgGx7gI6J64E3H V3jgrPAWZlK+abIBUNXUQUdbTGEyn5co1k+wVyHKS5YlXuCKoF+qmakAlA+cx7qrpM+V mFqz9F07YrIBC3YOwuagFGkrvzScxtQVRn1MtkvdtzU7ZGsexseQqrMGYRG+vxSi3uh4 4Obw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=x7tJ9sc12eJlSzLa2bNt+dxGt778vFxKI4JqBji+43M=; b=DyAbN3qDOCBqIryX9/PZOW/9ejeYl1+sxEwZoeOuKG7vanxq72Wf3+N92yVjdpo6/M UDuCNraY9bKhCgg0dISIlivsw8PaHiIWdGJ7iIDjQXGn6c0UYmQEogM754P3fUnb+M/G 6qLbReTicmbvVB1WWdflD2FNip1gtWKP3adzR7Sh/7aPczW4C1aMdAERy4xthjXfhDtD /O4E0ZdXiqkoeCPn2Pt80s28oMzlEgKgZUE5SAfP1RuF4i8LBSU2TFEpDoaS2gN054jG SyrZI1CNV8zOmPCxMNWeYMSnDxegKwbUaVpS216vvNgX3vYs/DZrzyxtkdM7OZ5lblTA 3Vow==
X-Gm-Message-State: APzg51B52ZLsxLYUyFmRhT9DMHr2TFMmhWFO0XMvrz9bLH+i1jict7D3 3vDXegTzmAGyP12jdaVIIFdbubdPiFkSg5HZivuvg12Z
X-Google-Smtp-Source: ANB0VdbewvmM0v3XDZmJYrLAMMWTjE2KFRtJ6KwR5k9hf1yEwOhArbLt8sv4Ym0Q3GtJ274Tq6iYc3VTUnmj3e/0Ayk=
X-Received: by 2002:aca:171a:: with SMTP id j26-v6mr3081204oii.277.1536248447262; Thu, 06 Sep 2018 08:40:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:6a15:0:0:0:0:0 with HTTP; Thu, 6 Sep 2018 08:40:16 -0700 (PDT)
In-Reply-To: <m2o9dau7ti.wl-randy@psg.com>
References: <b4afddcc-e8dc-9bd8-03d3-6374c29c4749@iab.org> <m2a7ownhl0.wl-randy@psg.com> <BC35696A-D4A6-47EA-A85C-EB472E42596E@lucidvision.com> <CA+9kkMCGNpFQGwEYZzn3CcOAdz_-GGMCP-N4jX_YuJ8tri0Bxw@mail.gmail.com> <fffabcb8-ee6f-d90b-f661-9011088b892b@gmail.com> <m2a7ovmzgk.wl-randy@psg.com> <9FA1C537-0B62-431F-B059-03C0813890CE@lucidvision.com> <m28t4fmyop.wl-randy@psg.com> <f4a99017-5483-2744-5f35-17620e123743@gmail.com> <3aed4068-a822-c5e6-c21d-b472f3e30373@huitema.net> <m2o9dau7ti.wl-randy@psg.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 06 Sep 2018 08:40:16 -0700
Message-ID: <CA+9kkMBXjTL0zumH4rhbJYJV=n25o1s+O-NBqUMHZj8Da-x2Rw@mail.gmail.com>
Subject: Re: IAB agendas now public
To: Randy Bush <randy@psg.com>
Cc: Christian Huitema <huitema@huitema.net>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fc6529057535b6a2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X6k982U2fxI91JrPyftHGzxCGnQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2018 15:40:59 -0000

On Thu, Sep 6, 2018 at 5:30 AM, Randy Bush <randy@psg.com> wrote:

> so holding a secret meeting within a closed meeting to discuss a bof on
> the rfc series is
>   o perfectly fine
>   o a lapse of judgement (of course i have none of those :)
>   o a lapse of process
>   o your ad goes here?
>

Randy,

If you refer to the minutes of the previous meetings you'll see:

10. Feedback from the Independent Stream Editorial Board

The IAB discussed feedback from the Independent Stream Editorial Board on
proposed changes to the Independent Stream. The IAB will discuss this
further next week when Heather Flanagan is available to join the IAB meeting

on 5/9, followed by:

5. Independent Stream

The IAB discussed the future of the Independent Stream and how to frame
that discussion with the community.

Martin Thomson noted that the conversation was not about closing the
Independent Stream, but about trying to find ways to remove some of the
confusion about what counts as a standard and what documents are actually
produced by the IETF.

Jari Arkko added he does not want to see publication of documents made more
difficult or add obstacles to publishing research.

After the discussion, Martin Thomson, Ted Hardie, Melinda Shore, and
Suzanne Woolf agreed to write up a BOF proposal for IETF 102 to discuss an
experiment with the community for publishing IAB, IRTF, and IS documents
with an identifier other than “RFC.” A new mailing list will be created to
go with the BOF proposal.

on 5/11.

There were also a number of previous discussions, including at the joint
IESG and IAB retreat.

The 5/30 meeting had this in executive session because I wanted it to have
the balance of time in the meeting; the item before it needed to be an
executive session (personnel issue):

8. Executive Session: RZERC Appointment

The IAB’s appointment to the RZERC was discussed in an executive session.
9. Executive Session: RFC++ BoF proposal

The RFC++ BOF Proposal was discussed in an executive session.

As a result, it ended up in executive session, since calling people back
into the meeting once you have gone into executive session is impractical.
  I recognized that at the time and was okay with it, because of some of
the discussion was who to request act as chair.  That is, again, a
personnel issue.

I understand that you may disagree with the decision to hold any part of a
meeting in executive session, and if it that was a lapse in judgement, it
was mine.

regards,

Ted