Re: New Version Notification for draft-leiba-rfc2119-update-00.txt

Dave Cridland <dave@cridland.net> Wed, 10 August 2016 16:38 UTC

Return-Path: <dave@cridland.net>
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 665C412D81E for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2016 09:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
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 it32zgqkMiJI for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2016 09:38:04 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 6576A12D832 for <ietf@ietf.org>; Wed, 10 Aug 2016 09:38:00 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id o80so115935427wme.1 for <ietf@ietf.org>; Wed, 10 Aug 2016 09:38:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4WcgJ5eVeWM+CIespo/mClsyb2rs6Ipnh5P42AbNbFE=; b=Np3g4l26A8SI+dDogSKir98Is4B1cUEbel9b4oU5Xs5vMkWtmYx/zmdXLCsm9T4kck EuHpsr74pVF6llH4TapvS4fbtspZL6+9q5FJxKU/Am9vXsjg9XWXRy3wa+5gLEu2Qnv5 rtgK7059G2A0t3Z7b2FFU4K2zthK8uZOCnEKI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4WcgJ5eVeWM+CIespo/mClsyb2rs6Ipnh5P42AbNbFE=; b=PmAc8YkyM2pOWgLdPLW3FmfbNw3t46rLBT+Q5Ag/Pv/HtJI0MQ11Jl/rTAty00XXL5 kaIn0VsM2f19w1TkN49n1WynRGVTLYh1eJW2QTC1rUJWq7Hz0c93w0RUskFTGLUHgeAs sGQAulXXBzSfV0jACM56XT4bYxySY4uYZ96AKwHyjl0S1/F9tmQ11P7e4ObE65EdvBD+ U6CS2fGIpjkFOLJpljApXsmVVU45YxPPaHJG28EP9qQ5lVN+M/AFQ8moiPvgib3dahp9 fu6AGNxwleaf/6/IRSN2OTleOtSwx7cOmay8GxJHjMfeB4hQGip8hARtIeW2jXh6Y7o6 9Mnw==
X-Gm-Message-State: AEkoouuavVcRT5YL5h/oc3Y5INbW2e7GI3ZOhnhqNuoadQYIQMhvIV7HcTt+U07mKCVqpx+d8boNvgEQTsClRUMo
X-Received: by 10.194.41.194 with SMTP id h2mr5735531wjl.2.1470847078825; Wed, 10 Aug 2016 09:37:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.127.76 with HTTP; Wed, 10 Aug 2016 09:37:57 -0700 (PDT)
In-Reply-To: <CALaySJJfBUa4D_UZvGUa2PNtuCaC-PJ2sb=F1Zy_jb=UomO4Dg@mail.gmail.com>
References: <147077254472.30640.13738163813175851232.idtracker@ietfa.amsl.com> <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com> <15076.1470795966@obiwan.sandelman.ca> <CALaySJKKTY7-mCry5W6LRVaNjgCSZ+2HoUk40RNAd5Nuz0HC_g@mail.gmail.com> <11066.1470841000@obiwan.sandelman.ca> <CALaySJJfBUa4D_UZvGUa2PNtuCaC-PJ2sb=F1Zy_jb=UomO4Dg@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Wed, 10 Aug 2016 17:37:57 +0100
Message-ID: <CAKHUCzxL2v5xHKEJovmS-nWZYE=-cwF3Vqp0=Wp5HAnuiofp9w@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NN9z7BUre0xy8wXJvaxYy_SGUgM>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 10 Aug 2016 16:38:05 -0000

On 10 August 2016 at 17:06, Barry Leiba <barryleiba@computer.org> wrote:
>>     >> XML format and screen readers.
>>     >>
>>     >> I have not looked deeply into the final RFC-format XML spec.
>>     >> Does it already markup SHOULD/MUST/MAY in some useful way?
>>     >> Could it?  If it does, should this document point out this?
>>
>>     > That's a good point, and I will look into what this might need to say
>>     > with respect to the XML markup.
>>
>> Thank you!
>> I think that markup on these keywords would help screen readers if they learn
>> to use the XML instead.
>
> I have checked, and I propose this change to the draft:
>
> OLD
>
>    === NEW ===
>    In many standards track documents several words are used to signify
>    the requirements in the specification.  These words are often
>    capitalized, as shown below, but they do not have to be.  This
>    document defines how these words are interpreted in IETF documents
>    when the words are capitalized.
>
> NEW
>
>    === NEW ===
>    In many standards track documents several words are used to signify
>    the requirements in the specification.  These words are often
>    capitalized, as shown below, but they do not have to be.  This
>    document defines how these words are interpreted in IETF documents
>    when the words are capitalized and/or marked as <bcp14> in the
>    XML source (see [draft-iab-xml2rfc], Section 2.9).
>
> END
>

You also need to change the text for authors to include in this case.
A document will (one hopes) use either CAPITALIZATION or
<bcp14>markup</bcp14> but not a mixture. I'd propose, therefore, that
two sets of text be offered for use by authors. The alternate might
be:

      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
and
      "<bcp14>MAY</bcp14>" in this document are to be interpreted as
described in
      BCP 14 <xref anchor="RFC2119"/>,<xref anchor="RFCxxxx"/> when,
and only when, they appear
      styled as shown.</t>


> The reference to draft-iab-xml2rfc would be informative.  Comments?
>
> Barry
>