Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details

joel jaeggli <joelja@bogus.com> Thu, 31 March 2016 23:20 UTC

Return-Path: <joelja@bogus.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 13FF912D526 for <ietf@ietfa.amsl.com>; Thu, 31 Mar 2016 16:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 wdrMYY9fCHb4 for <ietf@ietfa.amsl.com>; Thu, 31 Mar 2016 16:20:48 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3575012D560 for <ietf@ietf.org>; Thu, 31 Mar 2016 16:20:48 -0700 (PDT)
Received: from mb-2.local ([64.88.227.134]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u2VNKVJb046252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 31 Mar 2016 23:20:43 GMT (envelope-from joelja@bogus.com)
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
To: John C Klensin <john-ietf@jck.com>, Melinda Shore <melinda.shore@nomountain.net>, ietf@ietf.org
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <b982c83c-7de7-516e-11be-0fe7522a93ed@bogus.com>
Date: Thu, 31 Mar 2016 16:20:25 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Br0Ru74fPmvEH3cDLCRDFHRqk2IfG3R5r"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CfbcZJBwExe0YvQbAaaxhi_rzxI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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, 31 Mar 2016 23:20:50 -0000

On 3/31/16 11:29 AM, John C Klensin wrote:

> A registration requirement for remote participants is a major
> policy change and one for people who merely want to passively
> observe is something I believe the community has several times
> concluded is inappropriate given privacy, etc., concerns.  So,
> who made this decision and how?  Unless the answer involves a
> community discussion and Last Call or equivalent process that I
> missed (and apparently Melinda did too), if the answer to "who
> decided" involves anyone in the IETF Leadership, would they
> please offer to resign?

I think you are accusing the community selected committee members of
malfeasance. At least now we are clear on where we stand.

We have advanced No BCP or standards track document to describe
requirements or procedures for the operation of remote participation nor
should we IMHO unless:

We view it as a core function of the IETF activiity.

It is mature enough that the thing we describe is neither obsoleted or
overtaken by events or at least is not focused on the technology and
method of delivery before the document is published.