Re: Proposed Update to Note Well

Barry Leiba <barryleiba@computer.org> Fri, 22 June 2012 15:49 UTC

Return-Path: <barryleiba@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 8B09B21F8713; Fri, 22 Jun 2012 08:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.945
X-Spam-Level:
X-Spam-Status: No, score=-102.945 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nU2Q4ZQdpYiS; Fri, 22 Jun 2012 08:49:45 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id DBA8B21F86FE; Fri, 22 Jun 2012 08:49:44 -0700 (PDT)
Received: by qadz3 with SMTP id z3so435397qad.10 for <multiple recipients>; Fri, 22 Jun 2012 08:49:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+LD9vkcYo9LHDqINVuU069sxzY0stf/PKav306Y3Cw0=; b=YlrwVEmOSwabYnHk2/KTCp6HdEkddUqi52huUPrMW6vKqMZZFQY0p0IMbjEjtDR5px AM+reUU47qLiZkThcLEeZSgLAQcA3qTKDUTihxY5QRpqZOCuDsHtRVL8SNBNyRcqt6pa PN3vnPHZV8gCXC0cU8X3rDI4EYiphfSaCRBQLueHrcdKOlg/4L9WyrsIQdtGTPVKHxmj s7ekB4bCkEJrS2JdvUqrbm3dUp2uxnhsEunwhW5DZ25G3kWwmwUrz42d1TJ60JIZ+VyC Paodo7JheJzzOgDbobz/LDp/4TCNl5hp7TWwqS4NdEItzXGoPWmUZKGERuOboyMYEpp6 N5Fg==
MIME-Version: 1.0
Received: by 10.229.135.196 with SMTP id o4mr1310639qct.154.1340380184260; Fri, 22 Jun 2012 08:49:44 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.229.245.85 with HTTP; Fri, 22 Jun 2012 08:49:43 -0700 (PDT)
In-Reply-To: <20120622154616.GF44040@mail.yitter.info>
References: <CC09D19A.884F1%stewe@stewe.org> <4FE48B52.3080900@stpeter.im> <CALaySJ+1a13uKSLRbdUzadZLBVzrer5tkWAwoyNX-DyNLC5FTQ@mail.gmail.com> <20120622154616.GF44040@mail.yitter.info>
Date: Fri, 22 Jun 2012 11:49:43 -0400
X-Google-Sender-Auth: mw-c_Ncd8a7Ed87IZPoSt6s-uH0
Message-ID: <CALaySJ+b=DvAxEJGoo2yBMBar+1XQ0+3NhXSCd9hcLCqbT3xHQ@mail.gmail.com>
Subject: Re: Proposed Update to Note Well
From: Barry Leiba <barryleiba@computer.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Fri, 22 Jun 2012 15:49:45 -0000

> If the chairs are going to read boilerplate in meetings all week long,
> it's going to sound like such a disclaimer anyway.  I'm happy about
> the "short", but I don't understand the reason that the notice will
> need to be read out loud.  Is such a requirement the plan?  If so,
> why?

No, no... no *requirement*.  We just want it to be concise enough so
that it *can* reasonably be done.  It's kind of the test: if it's too
long for that, then it's probably too long.  The current Note Well
says what needs to be said, but makes everyone's eyes glaze over.

Barry