Re: [77attendees] Ad hoc meetings (Was: Re: Bar BoF: ip traceback)

Melinda Shore <shore@arsc.edu> Wed, 31 March 2010 00:27 UTC

Return-Path: <shore@arsc.edu>
X-Original-To: 77attendees@core3.amsl.com
Delivered-To: 77attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3AD9D3A6AC2 for <77attendees@core3.amsl.com>; Tue, 30 Mar 2010 17:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.222
X-Spam-Level:
X-Spam-Status: No, score=-1.222 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001]
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 9RLH49OSAXyx for <77attendees@core3.amsl.com>; Tue, 30 Mar 2010 17:27:05 -0700 (PDT)
Received: from arsc.edu (mail1.arsc.edu [IPv6:2001:480:150:75::229]) by core3.amsl.com (Postfix) with ESMTP id 0AB703A6C44 for <77attendees@ietf.org>; Tue, 30 Mar 2010 17:27:00 -0700 (PDT)
Received: from viking-e0.arsc.edu (viking-e0.arsc.edu [IPv6:2001:480:150:860:223:32ff:feda:4a52]) by arsc.edu (20090828.ARSC) with ESMTP id o2V0RQ8R027647; Tue, 30 Mar 2010 16:27:26 -0800 (AKDT)
Message-Id: <55877914-044B-49D0-AF4A-B140427FFC82@arsc.edu>
From: Melinda Shore <shore@arsc.edu>
To: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <4B9BDDA0-863F-4DA3-A902-9D8068B1EC8E@americafree.tv>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 30 Mar 2010 16:27:26 -0800
References: <4BA8BCE3.5020309@is.naist.jp> <4BA95B6A.5040707@is.naist.jp> <4BAB0464.2010307@is.naist.jp> <4BAB7A4D.7070904@piuha.net> <8133D17D-D9B6-40A6-AE9B-80BF90A5223D@checkpoint.com> <050005AF2D0F493AB38639A33748E8D6@china.huawei.com> <8B0A9FCBB9832F43971E38010638454F03E24ED320@SISPE7MB1.commscope.com> <4BABD0B2.9050003@piuha.net> <4BABDB19.8060403@gmail.com> <027f01cacc69$4847ae10$d8d70a30$@org> <23E6E51A-5D3B-4F94-B32F-7F3545003E03@cisco.com> <53720E57-D96D-458A-8178-5CC3DB496FAD@nokia.com> <4BAC239C.4060004@gmail.com> <A6562703-7EF4-4B9E-9E78-AB30F804DD45@tzi.org> <4BB0B975.7040100@joelhalpern.com> <DADD7EAD88AB484D8CCC328D40214CCD0167972D37@EXPO10.exchange.mit.edu> <m2k4stbq9g.wl%randy@psg.com> <4BB24841.2080109@cisco.com> <4BB25142.20904@gmail.com> <4BB26010.9090405@gmail.com> <CDF5BB9C-F2D1-4146-B2E1-F7FD5CC39829@americafree.tv> <B0456F98-4E7D-4547-9BB7-E826275B243D@arsc.edu> <4B9BDDA0-863F-4DA3-A902-9D8068B1EC8E@americafree.tv>
X-Mailer: Apple Mail (2.936)
X-CanIt-Geo: No geolocation information available for 2001:480:150:860:223:32ff:feda:4a52
X-CanItPRO-Stream: default
X-Canit-Stats-ID: Bayes signature not available
X-Scanned-By: CanIt (www . roaringpenguin . com) on IPv6:2001:480:150:75::167
Cc: 77attendees@ietf.org
Subject: Re: [77attendees] Ad hoc meetings (Was: Re: Bar BoF: ip traceback)
X-BeenThere: 77attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <77attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/77attendees>, <mailto:77attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/77attendees>
List-Post: <mailto:77attendees@ietf.org>
List-Help: <mailto:77attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/77attendees>, <mailto:77attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2010 00:27:06 -0000

On Mar 30, 2010, at 4:17 PM, Marshall Eubanks wrote:
> 'any statement made within the context of an IETF activity is  
> considered an "IETF Contribution".'

I think this is pushing the definition a bit and leaves
the organization open to DOS attacks from nutters.  If
Paul and I are chatting informally in the hallway at an
IETF meeting, it's happening within the context of an
IETF activity but certainly not an IETF contribution.
If someone organizes a hallway chat with a bunch of
people and they end up in an empty meeting room, I really
don't think that's an IETF contribution.  It's not an
IETF contribution until it becomes, you know, a
*contribution* and not just conversation.  I agree that
the line is fuzzy but I don't think it's *that* fuzzy.

And I think we're not in accord on the AD thing.  A
bar bof needn't involve an AD.  I'm beginning to think we
should ask them to stay far, far away.  *Far* away.

> If you want a deeper reason, the IETF has rules for a reason and it  
> is important that those rules cannot be evaded by, e.g., taking the  
> activity off-site and having it in a restaurant.

A design team is operating within the guidelines provided
by a working group and is an IETF activity.  A bunch of
people getting together and hammering out ideas about something
that might perhaps someday become an IETF activity?  That
doesn't seem as obvious to me as I guess it seems to you.

Melinda