IETF Logo Mail Archive

Re: [79all] IETF Badge

Dave CROCKER <dhc2@dcrocker.net> Thu, 11 November 2010 11:01 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 84D383A69FB; Thu, 11 Nov 2010 03:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.569
X-Spam-Level:
X-Spam-Status: No, score=-6.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 IedQGOOUEM9P; Thu, 11 Nov 2010 03:01:13 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 8DF433A69EE; Thu, 11 Nov 2010 03:01:13 -0800 (PST)
Received: from [130.129.69.41] (dhcp-4529.meeting.ietf.org [130.129.69.41]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oABB1VCg028202 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 11 Nov 2010 03:01:39 -0800
Message-ID: <4CDBCD06.2020108@dcrocker.net>
Date: Thu, 11 Nov 2010 19:01:26 +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: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: [79all] IETF Badge
References: <alpine.BSF.2.00.1011090344110.46514@fledge.watson.org> <CD5674C3CD99574EBA7432465FC13C1B2202288A0B@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288A0B@DC-US1MBEX4.global.avaya.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 03:01:40 -0800 (PST)
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "ietf@ietf.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 11:01:14 -0000

On 11/11/2010 6:44 PM, Worley, Dale R (Dale) wrote:
> Is it a change in practice?  My impression is that all IETF events require a badge for admission, although I suppose the practice may have been more lax than the policy.


It is a change in practice.  It is not a change in formal requirement.

This has (always?) been an unenforced requirement.(*)

(I'm offering a factual point, but not commenting on the issues being raised, 
other than to find myself thinking that these are interesting issues that 
warrant clarity and maybe clarification.)

d/

(*) In some arenas, long-term failure to enforce a rule negates the rule.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

v2.23.0 | Report a Bug | By Email