draft-ietf-httpbis-rand-access-live-02, "2.2. Byte-Range Requests Beyond the Randomly Accessible Byte Range"

• From: Julian Reschke <julian.reschke@gmx.de>
• Date: Sat, 30 Dec 2017 16:21:04 +0100
• To: ietf-http-wg@w3.org
• Message-ID: <fbca5fe2-b492-0cc7-04dd-9c2dc1c87262@gmx.de>

<https://www.greenbytes.de/tech/webdav/draft-ietf-httpbis-rand-access-live-02.html#rfc.section.2.2>:

"Once a client has determined that a representation has an indeterminate 
length and established the byte range that can be accessed, it may want 
to perform a request with a start position within the 
randomly-accessible content range and an end position at an indefinite 
"live" point - a point where the byte-range GET request is fulfilled 
on-demand as the content is aggregated."

There are multiple instances of "may" (as opposed to "MAY") in the 
document. Historically, this has led to confusion whether this was a 
BCP14 keyword or not.

There are (at least) two ways to address this:

- avoid "may", here "might" would work equally well

- invoke RFC 8174; example: 
<https://www.greenbytes.de/tech/webdav/rfc8259.html#rfc.section.1.1>

(also check for other lowercase BCP14 keywords...)

Best regards, Julian

Received on Saturday, 30 December 2017 15:21:38 UTC