IETF Logo Mail Archive

Re: [79all] IETF Badge

Dave CROCKER <dhc2@dcrocker.net> Thu, 11 November 2010 15:19 UTC

Return-Path: <dhc2@dcrocker.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 832863A687C; Thu, 11 Nov 2010 07:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level:
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 sd4RcTd249cP; Thu, 11 Nov 2010 07:19:17 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 899C73A683F; Thu, 11 Nov 2010 07:19:17 -0800 (PST)
Received: from [10.1.87.158] ([124.193.12.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oABFJavY012298 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 11 Nov 2010 07:19:45 -0800
Message-ID: <4CDC0984.60805@dcrocker.net>
Date: Thu, 11 Nov 2010 23:19:32 +0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: [79all] IETF Badge
References: <alpine.BSF.2.00.1011090344110.46514@fledge.watson.org> <Pine.GSO.4.63.1011110103450.3692@pita.cisco.com> <4CDBC1A1.7020500@stpeter.im> <Pine.GSO.4.63.1011110330360.9937@pita.cisco.com>
In-Reply-To: <Pine.GSO.4.63.1011110330360.9937@pita.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 11 Nov 2010 07:19:46 -0800 (PST)
Cc: iaoc@ietf.org, Samuel Weiler <weiler+ietf@watson.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Thu, 11 Nov 2010 15:19:18 -0000

On 11/11/2010 7:38 PM, Ole Jacobsen wrote:
> And having to display your badge = "dictate how we run our meetings" ???

Having a local organization dictate any procedure to the IETF is a matter of 
substance.

What if they dictated no breaks, or that we bring our own toilet paper or that 
we begin our meeting by having everyone stand up and do a brief set of 
exercises, or that we pledge allegiance to the national flag, or ...

Each of these is an existing "local custom" somewhere.

The underlying point is that some local customs are benign for the IETF and 
others are not and others are in a grey zone.  Certainly anything involving a 
change in habitual IETF security procedures can be expected to be a sensitive 
matter.

That does not automatically make checking badges bad or unacceptable, but it 
does warrant raising a flag.  As I recall, the challenge at the microphone 
included the observation that this was done without notice, for example.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

v2.23.0 | Report a Bug | By Email