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

Marshall Eubanks <tme@americafree.tv> Wed, 31 March 2010 00:46 UTC

Return-Path: <tme@americafree.tv>
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 A66223A68F1 for <77attendees@core3.amsl.com>; Tue, 30 Mar 2010 17:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.562
X-Spam-Level:
X-Spam-Status: No, score=-0.562 tagged_above=-999 required=5 tests=[AWL=0.907, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 rQntL7wIz7wV for <77attendees@core3.amsl.com>; Tue, 30 Mar 2010 17:46:47 -0700 (PDT)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id AF9343A6A91 for <77attendees@ietf.org>; Tue, 30 Mar 2010 17:46:43 -0700 (PDT)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 94813672B5B9; Tue, 30 Mar 2010 20:47:13 -0400 (EDT)
Message-Id: <05185732-545E-4FC6-A87F-A2F35C7B4B60@americafree.tv>
From: Marshall Eubanks <tme@americafree.tv>
To: joel.jaeggli@nokia.com
In-Reply-To: <FE14C16A26F361409AB2A1D6DAA3590658662DA1D7@NOK-EUMSG-04.mgdnok.nokia.com>
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 20:47:13 -0400
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> <FE14C16A26F361409AB2A1D6DAA3590658662DA1D7@NOK-EUMSG-04.mgdnok.nokia.com>
X-Mailer: Apple Mail (2.936)
Cc: hardjono@MIT.EDU, scott.brim@gmail.com, 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:46:47 -0000

On Mar 30, 2010, at 7:44 PM, <joel.jaeggli@nokia.com> wrote:

>> They are subject to the Note Well. That is certainly a rule.
>>
>> Regards
>> Marshall
>
> That is exactly the sort of scope creep that should be avoided by  
> not formalizing an otherwise informal activity at the IETF.
>
> An informal exchange between two or more parties who happen to be at  
> an IETF meeting is not an IETF contribution unless covered by one of  
> the six note well bullets, we shouldn't need a seventh.
>

If you and I want to get together in a Bar or other location, sure,  
that is not subject to the Note Well.

If you and I want to clear our get-together with an AD, arrange the  
schedule so that the AD can be present, host the meeting in an IETF  
room, set up an IETF mailing list to facilitate discussions, and post  
the list, room, meeting time and location to an IETF list to increase  
interest and attandance then, yes, I would argue that this is an IETF  
activity and is subject to the note well.

Let's look at IETF-77, at the first hits on an email search for "bar  
bof."

Clouds : Meeting Doodle poll posted to the IETF list. An IETF hosted  
mail list set up.
Bar BoF on Location Coherence : Announced on IETF list.  Held in an  
IETF meeting room.

Bar BoF: ip traceback : Announced on IETF list. Held in an IETF  
meeting room.

Internet Registration Bar BOF : Announced on IETF list. Held in an  
IETF meeting room.

I think that illustrates the point.

BTW, when I chaired a Bar Bof, the AD wanted me to announce that the  
Note Well applied.

Regards

Marshall