From cd55f8147707900ab0d14ec10bf3f91bc14b41f4 Mon Sep 17 00:00:00 2001 From: Craig Pratt Date: Tue, 10 Apr 2018 00:48:26 -0700 Subject: [PATCH 1/2] Added a small blurb referencing client range-end considerations from section 5 --- draft-ietf-httpbis-rand-access-live.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-rand-access-live.xml b/draft-ietf-httpbis-rand-access-live.xml index c482d7dfa..99cf3a79c 100644 --- a/draft-ietf-httpbis-rand-access-live.xml +++ b/draft-ietf-httpbis-rand-access-live.xml @@ -291,7 +291,7 @@ Range: bytes=1230000-999999999999 - where the last-byte-pos in the Request is much larger than the last-byte-pos returned in response to an open-ended byte-range HEAD request, as described above. + where the last-byte-pos in the Request is much larger than the last-byte-pos returned in response to an open-ended byte-range HEAD request, as described above. The client should provide a value much larger than the expected maximum size of the representation. See for range value considerations. In response, a server may indicate that it is supplying a continuously aggregating ("live") response by supplying the client request's last-byte-pos in the Content-Range response header field. From 1c2d66b65bf6504f285dbe8a0affd9044baa1c20 Mon Sep 17 00:00:00 2001 From: Craig Pratt Date: Wed, 11 Apr 2018 11:04:15 -0700 Subject: [PATCH 2/2] Cleaned up/shortened added blurb --- draft-ietf-httpbis-rand-access-live.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-rand-access-live.xml b/draft-ietf-httpbis-rand-access-live.xml index 99cf3a79c..0d7255ad6 100644 --- a/draft-ietf-httpbis-rand-access-live.xml +++ b/draft-ietf-httpbis-rand-access-live.xml @@ -291,7 +291,7 @@ Range: bytes=1230000-999999999999 - where the last-byte-pos in the Request is much larger than the last-byte-pos returned in response to an open-ended byte-range HEAD request, as described above. The client should provide a value much larger than the expected maximum size of the representation. See for range value considerations. + where the last-byte-pos in the Request is much larger than the last-byte-pos returned in response to an open-ended byte-range HEAD request, as described above, and much larger than the expected maximum size of the representation. See for range value considerations. In response, a server may indicate that it is supplying a continuously aggregating ("live") response by supplying the client request's last-byte-pos in the Content-Range response header field.