IETF Logo Mail Archive

Re: Applying "Note Well" to side meetings

Phillip Hallam-Baker <hallam@gmail.com> Sun, 21 July 2019 01:57 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFF1F12027E for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2019 18:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BAbUnuTRI--I for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2019 18:57:26 -0700 (PDT)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B6E4120241 for <ietf@ietf.org>; Sat, 20 Jul 2019 18:57:26 -0700 (PDT)
Received: by mail-ot1-x335.google.com with SMTP id y20so20704268otk.7 for <ietf@ietf.org>; Sat, 20 Jul 2019 18:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=SbtBkvl9XNsAgobqH3rn3WhYA0llRsS3kytEx4TEYL4=; b=ni+/MOxXDk+AjD9xcno+zFYoq5JTGpF+FQFZI/7Vwp7FMPEtbc+NmvKmOVWMmG3iNk 9axsiDIIEBGnmt9rgE1bPdq6zHzet0ty/C2fVx0mwD8GFdX6pWnNup6bn5mfoXmO//cu TSvh3L09UtMy0GGzdd18t+hvZ5jtpdfjQVN/fKjiEYqyBp4eELT5BlDW/8WWukvsYs+o nUQUUYL/8ilzTwxX3aUoJos5gIxMmBQt4dazUDEVWaG97wyg0EjP7IhjdzFeG2rVYqze dFu6GEPyMLmv3sswBTtOQA4hSdQVuwAEhGVJcmr19TQpct+SRwviZ5g6Le7ZeBy03v9F c4Bg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :mime-version; bh=SbtBkvl9XNsAgobqH3rn3WhYA0llRsS3kytEx4TEYL4=; b=e6zBbEOC7M90c3gLw76Wd1m3ngy2DuGemDyTaZ2lL8+DCOql8n80dnpi01NlhU9koh GYPAbrMekz1V7xM7uY3PIhIQTGEbw/9WOIwbqVh/J0mCIagMRjsSId4r4zwPICT75LBW xKdoneQDD/Dnuop6hFjtIm+QxHHWWlVwW6XR6P/xGq6naHu84VBd5GmNnPd2aZEX+Hu5 g9fZxPd6HdTRNudgKBdPWkbDcCkN1+CHxtM56H4MYD39w0CK3Lxlr1Rndtq1pEjcx6+/ gUpapcAeIHTDeEX8qGMOJMT0SkZdr9COjcp41SHzoz+ZYXHpnvT5flczCPU2PiZOpUHN +mhA==
X-Gm-Message-State: APjAAAXlMNUw86ls84m4ldL/uRIeoJyRb6IVeLYUxhjqCwR6di6ha3mm CoE1rK7kTGJYkRIb++2mwZenD4N+e9M=
X-Google-Smtp-Source: APXvYqyDGpWfjsiDnT4FTtGFirWhCUH42etzbLVJoLPM/fzn8CBgAMFk+rsH2jf6Kvbp392GSmpn2Q==
X-Received: by 2002:a05:6830:1542:: with SMTP id l2mr7151164otp.241.1563674245546; Sat, 20 Jul 2019 18:57:25 -0700 (PDT)
Received: from DM6PR14MB2827.namprd14.prod.outlook.com ([2603:1036:301:20d4::5]) by smtp.gmail.com with ESMTPSA id e10sm11051923oie.37.2019.07.20.18.57.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 20 Jul 2019 18:57:25 -0700 (PDT)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'IETF Rinse Repeat' <ietf@ietf.org>
Subject: Re: Applying "Note Well" to side meetings
Thread-Topic: Applying "Note Well" to side meetings
Thread-Index: ASQ5OCRkA65Q5r+63gpZw88zHIsCJuIMXutU
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Sun, 21 Jul 2019 01:57:24 +0000
Message-ID: <DM6PR14MB282741D8727A72156457555AF8C50@DM6PR14MB2827.namprd14.prod.outlook.com>
References: <007b01d53f2f$ef335830$cd9a0890$@olddog.co.uk>
In-Reply-To: <007b01d53f2f$ef335830$cd9a0890$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DM6PR14MB282741D8727A72156457555AF8C50DM6PR14MB2827namp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fjltCnHllDuf0I6_q6SqTMVWt5o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 21 Jul 2019 01:57:35 -0000

It was my understanding that note well always applied


________________________________
From: ietf <ietf-bounces@ietf.org> on behalf of Adrian Farrel <adrian@olddog.co.uk>
Sent: Saturday, July 20, 2019 3:19 PM
To: 'IETF Rinse Repeat'
Subject: Applying "Note Well" to side meetings

Hi,

Normally [1] when we have a "bar BoF" (also known as a "side meeting") we do
not apply the terms of the "Note Well" [2]. We have usually considered bar
BoFs to be outside the IETF because the IETF has no control over who meets
and drinks.

However, this time around, the side meetings are somewhat more formal with
room bookings and projectors and advertisements and so on.

So, does the Note Well apply to these side meetings?

Apologies if I missed an email on this: I sometimes don't focus as much as I
should.

Thanks,
Adrian

[1] For some practical definition of "normal"
[2] https://www.ietf.org/about/note-well/
--
Read some fairy stories for adults of all ages
.. Tales from the Wood
.. More Tales from the Wood
.. Tales from Beyond the Wood
.. Tales from the Castle
Get them on line https://www.feedaread.com/profiles/8604/
Or buy a signed copy from me by post
*** Stop me in the corridor at IETF-105 to get a copy ***

v2.23.0 | Report a Bug | By Email