IETF Logo Mail Archive

Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF

Dave Cridland <dave@cridland.net> Tue, 22 September 2009 20:14 UTC

Return-Path: <dave@cridland.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2ECB53A6822 for <ietf@core3.amsl.com>; Tue, 22 Sep 2009 13:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level:
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpWuw41mTp9p for <ietf@core3.amsl.com>; Tue, 22 Sep 2009 13:14:53 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 926363A6800 for <ietf@ietf.org>; Tue, 22 Sep 2009 13:14:52 -0700 (PDT)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <SrkwdQBdm6Je@peirce.dave.cridland.net>; Tue, 22 Sep 2009 21:15:50 +0100
X-SMTP-Protocol-Errors: NORDNS
Subject: Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF
References: <4568491E-A8CA-4089-84C7-2D555F929204@americafree.tv> <D8E4F187-9C2D-4AB5-8F41-AB7C8EE1CB52@tzi.org> <290DDBB5C78B808A31DBD1CD@PST.JCK.COM> <alpine.LFD.1.10.0909181454200.28905@newtla.xelerance.com> <4AB91330.3000505@nostrum.com> <4AB91CF2.90100@stpeter.im>
In-Reply-To: <4AB91CF2.90100@stpeter.im>
MIME-Version: 1.0
Message-Id: <24280.1253650567.977180@puncture>
Date: Tue, 22 Sep 2009 21:16:07 +0100
From: Dave Cridland <dave@cridland.net>
To: Peter Saint-Andre <stpeter@stpeter.im>, IETF-Discussion <ietf@ietf.org>, Adam Roach <adam@nostrum.com>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 22 Sep 2009 20:14:54 -0000

On Tue Sep 22 19:52:34 2009, Peter Saint-Andre wrote:
> (I suppose that other SDOs and conference organizers have tried to  
> work
> around this restriction in various ways, but it seems irresponsible  
> to
> do so by ignoring the restriction altogether and letting presenters  
> say
> anything they want, given the organizational liability that is
> stipulated in the restriction. The IETF could claim that what  
> presenters
> say at WG sessions, plenaries, and the like is outside the control  
> of
> the IETF, but I think that is skating on rather thin ice.)

Having attended only XSF and OMA aside from IETF, I'm not sure  
whether the IETF and XSF are essentially unique is trying to provide  
remote participation, either - the OMA certainly doesn't.

I reiterate - if I wished to grind my political axe against the PRC,  
I would do so via the Jabber chatrooms. IETF meetings increasingly  
rely on these, and should they be deliberately used to raise issues  
with which the PRC would be uncomfortable, I see very little in the  
way of mitigation or remedy which I would, in turn, be comfortable  
with.

The physical meeting I'm fine with in China. I'm pretty sure the  
bizarre - to Western eyes - rules and regulations can be dealt with  
in such a way that actual impact to the IETF meeting is minimized,  
and the benefits of the location - Chinese engineering knowledge, etc  
- would outweigh the disadvantages.

But I'm concerned that only a couple of us have raised the potential  
impact on remote participation - can I ask what steps are being taken  
to minimize impact there?

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

v2.23.0 | Report a Bug | By Email