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

John C Klensin <> Thu, 11 August 2016 00:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B623112B02C for <>; Wed, 10 Aug 2016 17:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.247] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PBtxv5dyEayX for <>; Wed, 10 Aug 2016 17:24:40 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4ABBD12B027 for <>; Wed, 10 Aug 2016 17:24:40 -0700 (PDT)
Received: from [] (helo=JcK-HP8200) by with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <>) id 1bXdnV-0001DW-Uq; Wed, 10 Aug 2016 20:24:33 -0400
Date: Wed, 10 Aug 2016 20:24:28 -0400
From: John C Klensin <>
To:, Sam Hartman <>, Ted Hardie <>
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
Message-ID: <D5795780B602C1FAAB0CD73D@JcK-HP8200>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
Cc: Barry Leiba <>, 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: Thu, 11 Aug 2016 00:24:42 -0000

--On Tuesday, August 09, 2016 14:33 -0700 Dave Crocker
<> wrote:

> On 8/9/2016 2:22 PM, Sam Hartman wrote:
>>  In general, I don't distinguish
>> between caps in running text, but all the screen readers I've
>> used (including even the one on Android) can distinguish caps
>> if you ask them too.

> I'd expect that change in screen reader mode to add quite a
> bit of noise the the output, as all the case changes are
> noted, where only a tiny number matter.  Low signal to noise
> like that seems likely to be distracting, at best.


Sam and others who use screen readers every day (and, I trust,
screen readers that match their needs) are much more important
than I am about this, but I have used screen readers from time
to time -- typically out of necessity at those times-- and the
knobs permit me to make settings that tell me about
ordinarily-capitalized words or not, punctuation or not,
completely capitalized words or not, etc.  So, if I set one up
that way, I can be told about MUST without being told that
"Sam", the first word in the previous sentence, starts with a
capital letter.

I don't think the draft has this quite right (see longer note
sent a short time ago), but, because I don't see the options as
limited to "case change" or not (which, would, indeed, be very
distracting in most texts), I don't see the screen reader
question as a powerful bar to what the draft suggests.