Re: [urn] normative language -- a new convention

Barry Leiba <barryleiba@computer.org> Fri, 18 May 2012 16:44 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94D8221F854B for <urn@ietfa.amsl.com>; Fri, 18 May 2012 09:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.823
X-Spam-Level:
X-Spam-Status: No, score=-102.823 tagged_above=-999 required=5 tests=[AWL=-0.146, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 cT0vXFLVFn5L for <urn@ietfa.amsl.com>; Fri, 18 May 2012 09:44:16 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF9121F8540 for <urn@ietf.org>; Fri, 18 May 2012 09:44:15 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so2562262lbb.31 for <urn@ietf.org>; Fri, 18 May 2012 09:44:14 -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; bh=q2AOhRXz1W7jP96AMKzP/g0BGRJuK8v+Pm62jGw8UJo=; b=KlzUG7Aua41rvwyY2poIh/lOKBcMgZC6QxGgLDJu19E3qpJnA2bwk8BVmrzD92KCf1 f1BFisCec4JJfPZrwmSuB00QKt+9sK0gwihQsNm9GRl+nxUXl4Pw4UtMXpaTP4Piq+el MaeD0DOEyJXJ0bOZg8vOcXa6rfLTGrD/NrHWlEFkea2Ul8HyTrFTrF4PEmGhd57RSxOT kp4shHCNMqgjp8zrdMufYldP+F9shpwalFn9ucLMB1Vqfzri6O9H8zIn9di4SWaMyWfD gTAX8sfNS25OmzAgDFapZzqIOw5at4h0E1gsgLbFS93UbUgKTjF6q+wnwhS5Uu1dVD6v zXjQ==
MIME-Version: 1.0
Received: by 10.112.101.105 with SMTP id ff9mr5065906lbb.44.1337359454603; Fri, 18 May 2012 09:44:14 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.7.7 with HTTP; Fri, 18 May 2012 09:44:14 -0700 (PDT)
In-Reply-To: <201205180833.KAA24888@TR-Sys.de>
References: <201205180833.KAA24888@TR-Sys.de>
Date: Fri, 18 May 2012 12:44:14 -0400
X-Google-Sender-Auth: dQZOEv9R1ryoKjLmyz58Fy1qwvs
Message-ID: <CAC4RtVDYmVJyPUvy1+V0oaZK+6YoKFbehgSO_h-6-GtEP-1qPg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Alfred Hönes <ah@tr-sys.de>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: urn@ietf.org
Subject: Re: [urn] normative language -- a new convention
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2012 16:44:16 -0000

Alfred,

> <speaking both as an individual and as a co-chair>

As the responsible AD, I am at a loss to understand how it's at all
appropriate for you to make this suggestion as chair.  Please explain
specifically where the authority to do that comes from.

> With the approval of the IESG, RFC 6329 (published in April 2012)
> has introduced a new convention (see Section 3 of that RFC), and
> I suggest that we liberally adopt this method for our WG documents:

As a participant, I suggest that this is a very bad idea.  Using ALL
CAPS vs lower case is controversial enough -- see the thread I started
the other day on ietf@ietf.org:
https://www.ietf.org/mail-archive/web/ietf/current/msg73338.html

And note that Marshall Eubanks referred this thread to that one this morning.

Given that there's already no consensus on using "MUST" and "SHOULD"
vs "must" and "should", I would be very hesitant to advocate the
widespread addition of "Must" and "Should" with yet different nuances.
 I urge you not to go there.

In any case, I urge anyone who cares about this issue to pursue it on
the IETF discussion list, in the thread I linked to above, and not to
discuss it here.

Barry, Applications Area Director