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

Michael Richardson <> Wed, 10 August 2016 14:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5AC0812D103 for <>; Wed, 10 Aug 2016 07:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id twigaPk4le5M for <>; Wed, 10 Aug 2016 07:56:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D451C12D0FB for <>; Wed, 10 Aug 2016 07:56:41 -0700 (PDT)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id C22362009E; Wed, 10 Aug 2016 11:07:22 -0400 (EDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id DE194638BE; Wed, 10 Aug 2016 10:56:40 -0400 (EDT)
From: Michael Richardson <>
To: Barry Leiba <>
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
In-Reply-To: <>
References: <> <> <> <>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 10 Aug 2016 10:56:40 -0400
Message-ID: <>
Archived-At: <>
Cc: IETF discussion list <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Aug 2016 14:56:43 -0000

Barry Leiba <> wrote:
    >> So as I understand it, documents which adhere to rfc2119-update will
    >> cite BCP14 and the RFCXXXX which this document will have?
    >> or will it cite RFC2119 and RFCXXXX?
    >> Are you suggesting that we should be citing BCP14 though?

    > Is there really something unclear about the boilerplate update in
    > Section 2?:

No, maybe not unclear, but maybe I just didn't grok the [] clearly at first.
So, we would have [RFC2119] and [RFCxxxx] in my references, but not BCP14.

    >> It seems that retaining section 1.1 might be worth it.

    > Perhaps, though I don't think it really has archival value.  Do others
    > think it should be retained?

I don't feel strongly that it MUST be retained, just that it SHOULD.

    >> 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 also have some illusion that web browsers might soon render XML directly
via something like XSLT rather than doing this offline. )

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-