IETF Logo Mail Archive

Re: Applying "Note Well" to side meetings

Nico Williams <nico@cryptonector.com> Mon, 22 July 2019 17:27 UTC

Return-Path: <nico@cryptonector.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 1A7F7120192 for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 10:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=cryptonector.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 0mL-mZFtoHte for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 10:27:37 -0700 (PDT)
Received: from cheetah.birch.relay.mailchannels.net (cheetah.birch.relay.mailchannels.net [23.83.209.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FEDB120159 for <ietf@ietf.org>; Mon, 22 Jul 2019 10:27:37 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id B31AE140905; Mon, 22 Jul 2019 17:27:35 +0000 (UTC)
Received: from pdx1-sub0-mail-a62.g.dreamhost.com (100-96-92-226.trex.outbound.svc.cluster.local [100.96.92.226]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 23498142A24; Mon, 22 Jul 2019 17:27:35 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a62.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.3); Mon, 22 Jul 2019 17:27:35 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Squirrel-Hook: 2a45ae3871ffcec7_1563816455489_1985268742
X-MC-Loop-Signature: 1563816455489:4157622608
X-MC-Ingress-Time: 1563816455488
Received: from pdx1-sub0-mail-a62.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a62.g.dreamhost.com (Postfix) with ESMTP id 47FB78399B; Mon, 22 Jul 2019 10:27:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=aQx+pusKuQOkUkm24IqNrCi5sM8=; b=bBACgTGhxnX KEBBS6Q338dOGEq6NGukGgc5/wUpnReXIv2UPaKd6hXXu7YSOjMzTkE2usT+U0vL anMW0AetsQ7dMQhg/gINSMPQTwWBKtps6Am06p4cfiIendiEEadby9rtcpzprFFb CPMJ9PnxZ0IlvmwNzMunZUvlgtLLVL8E=
Received: from localhost (sdzac10-108-1-nat.nje.twosigma.com [8.2.105.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a62.g.dreamhost.com (Postfix) with ESMTPSA id 32C2283996; Mon, 22 Jul 2019 10:27:29 -0700 (PDT)
Date: Mon, 22 Jul 2019 12:27:27 -0500
X-DH-BACKEND: pdx1-sub0-mail-a62
From: Nico Williams <nico@cryptonector.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Richard Barnes <rlb@ipv.sx>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Applying "Note Well" to side meetings
Message-ID: <20190722172726.GL24576@localhost>
References: <007b01d53f2f$ef335830$cd9a0890$@olddog.co.uk> <DM6PR14MB282741D8727A72156457555AF8C50@DM6PR14MB2827.namprd14.prod.outlook.com> <63AC1040-37C8-4DAA-B222-1F166D333CF7@akamai.com> <CAL02cgRxxic78LeDKonAFMJKAuuXtYeZnScVJ6MXyPZFaZt7wA@mail.gmail.com> <20190722155714.GK24576@localhost> <f01c71ef-eaf4-f1ea-fc8c-24826c1e1ff9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <f01c71ef-eaf4-f1ea-fc8c-24826c1e1ff9@gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduvddrjeeggdduudeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtugfgjggfsehtkeertddtreejnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecukfhppeekrddvrddutdehrddujeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpeekrddvrddutdehrddujedprhgvthhurhhnqdhprghthheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqedpmhgrihhlfhhrohhmpehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmpdhnrhgtphhtthhopehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yX4LdhSI-U1cM-aNCFgACdBwTV0>
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: Mon, 22 Jul 2019 17:27:40 -0000

On Tue, Jul 23, 2019 at 05:13:28AM +1200, Brian E Carpenter wrote:
> On 23-Jul-19 03:57, Nico Williams wrote:
> > On Sun, Jul 21, 2019 at 06:25:12AM -0400, Richard Barnes wrote:
> >> Maybe folks could provide a citation for this?  Because I have exactly the
> >> opposite impression — that the Note Well only applies in contexts where it
> >> is explicitly stated that it does, e.g., official sessions.
> > 
> > I've long understood that Note Well applies when and only when
> > ('WWHEN'?) it is invoked, 
> 
> No. It's only a reminder of the IETF rules, and the rules apply to
> all IETF activities -- all "contributions" in the IPR disclosure case.
> See the earlier responses in this thread.

Thanks.  However, it's still the case that outside official IETF
meetings (interim and otherwise), Note Well applies WWHEN invoked --
surely it must be.

Nico
--

v2.23.0 | Report a Bug | By Email