host	fresh	stale	total
*.facebook.com	790	1,483	2,273
*.google.com	373	630	1,003

- Some Hypertext Transfer Protocol (HTTP) Clients use byte-range requests (Range requests using the "bytes" Range Unit) to transfer select portions of large representations. And in some cases large representations require content to be continuously or periodically appended - such as representations consisting of live audio or video sources, blockchain databases, and log files. Clients cannot access the appended/live content using a Range request with the bytes range unit using the currently defined byte-range semantics without accepting performance or behavior sacrifices which are not acceptable for many applications. + Some Hypertext Transfer Protocol (HTTP) clients use byte-range requests (Range requests using the "bytes" Range Unit) to transfer select portions of large representations. And in some cases large representations require content to be continuously or periodically appended - such as representations consisting of live audio or video sources, blockchain databases, and log files. clients cannot access the appended/live content using a Range request with the bytes range unit using the currently defined byte-range semantics without accepting performance or behavior sacrifices which are not acceptable for many applications. "client" needs to be capitalized at the start of a sentence :) > - To accommodate byte-range requests on large representations which have data appended over time efficiently and with low latency, this recommendation defines semantics whereby the HTTP Client performs byte-range requests using a combination of open-ended byte-range HEAD requests and GET requests using "Large Value" last-byte-pos values. + This document describes a usage model for range requests which enables + efficient retrieval of representations that are appended to over time + by utilizing large values and associated semantics for communicating https://grammarpartyblog.com/2012/01/17/use-versus-utilize/ > - + This document recommends a two-step process for accessing resources + that have indeterminate length representations. + + Two steps are necessary because of limitations with the Range request + header and the Content-Range response header fields. A server cannot + know from a range request that a client wishes to receive a response + that does not have a definite end. More critically, the header fields + do not allow the server to signal that a resource has indeterminate + length without also providing a fixed portion of the resource. + + A client first learns that the resource has a representation of + indeterminate length by requesting a range of the resource. The server + responds with the range that is available, but indicates that the + length of the representation is unknown using the existing + Content-Range syntax. See Section 2.1 for details and examples. for the section reference. > + + A client first learns that the resource has a representation of + indeterminate length by requesting a range of the resource. The server + responds with the range that is available, but indicates that the + length of the representation is unknown using the existing + Content-Range syntax. See Section 2.1 for details and examples. + + Once the client knows the resource has indeterminate length, it can + request a range with a very large end position from the resource. The + client chooses an explicit end value larger than can be transferred in + the foreseeable term. A server which supports range requests of + indeterminate length signals its understanding of the client's + indeterminate range request by indicating that the range it is + providing has a range end that exactly matches the client's requested + range end rather than a range that is bounded by what is currently + available. See Sections 2.2 and 2.3 for details. xrefs > - could return + will return maybe "will return a range covering only those bytes that are currently available:" > @@ -390,7 +423,9 @@

- One potential issue with this recommendation is related to the use of very-large last-byte-pos values. Some Client and Server implementations may not be prepared to deal with byte position values of 2^^63 and beyond. So in applications where there's no expectation that the representation will ever exceed 2^^63, a value smaller than this value should be used as the Very Large last-byte-pos in a byte-seek request or content-range response. + One potential issue with this recommendation is related to the use of very-large last-byte-pos values. Some client and server implementations may not be prepared to deal with byte position values of 2^^63 and beyond. So in applications where there's no expectation that the representation will ever exceed 2^^63, a value smaller than this value should be used as the Very Large last-byte-pos in a byte-seek request or content-range response. + + Also, some implementations (e.g. JavaScript-based clients and servers) are not able to represent all values beyond 2^^53. So similarly, if there's no expectation that a representation will ever exceed 2^^63 bytes, values smaller than this limit should be used for the last-byte-pos in byte-range requests. it's less about representation for this, but about ease of parsing I think that the second value here could be 2^53 instead of 2^63. > @@ -210,24 +232,26 @@ byte-range-spec = first-byte-pos "-" [ last-byte-pos ] - which allows a Client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A Server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a Client-issued HEAD request performed against a continuously aggregating representation hosted on a Server could contain a byte-range header of the form: + which allows a client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a client-issued HEAD request performed against a continuously aggregating representation hosted on a server could contain a byte-range header of the form: The "must" here is incorrect. It can provide the entire representation (for instance, if it didn't support range requests). Maybe "might". > @@ -210,24 +232,26 @@ byte-range-spec = first-byte-pos "-" [ last-byte-pos ] - which allows a Client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A Server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a Client-issued HEAD request performed against a continuously aggregating representation hosted on a Server could contain a byte-range header of the form: + which allows a client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a client-issued HEAD request performed against a continuously aggregating representation hosted on a server could contain a byte-range header of the form: Finally, the client doesn't necessarily know that the resource is continuously aggregating. Maybe just say "For example, a client issues a request for an indefinite range of bytes as follows:" -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/414#pullrequestreview-75585363 ----==_mimepart_5a04c48038566_6ee53fd8b7b58f2c3641d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson approved this pull request.

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -166,16 +166,22 @@
     
     <section anchor="introduction" title="Introduction">
         <t>
-             Some Hypertext Transfer Protocol (HTTP) Clients use byte-range requests (Range requests using the "bytes" Range Unit) to transfer select portions of large representations. And in some cases large representations require content to be continuously or periodically appended - such as representations consisting of live audio or video sources, blockchain databases, and log files. Clients cannot access the appended/live content using a Range request with the bytes range unit using the currently defined byte-range semantics without accepting performance or behavior sacrifices which are not acceptable for many applications.
+             Some Hypertext Transfer Protocol (HTTP) clients use byte-range requests (Range requests using the "bytes" Range Unit) to transfer select portions of large representations. And in some cases large representations require content to be continuously or periodically appended - such as representations consisting of live audio or video sources, blockchain databases, and log files. clients cannot access the appended/live content using a Range request with the bytes range unit using the currently defined byte-range semantics without accepting performance or behavior sacrifices which are not acceptable for many applications.

"client" needs to be capitalized at the start of a sentence :)

In draft-ietf-httpbis-rand-access-live.xml:

>          </t>
         <t>
-			To accommodate byte-range requests on large representations which have data appended over time efficiently and with low latency, this recommendation defines semantics whereby the HTTP Client performs byte-range requests using a combination of open-ended byte-range HEAD requests and GET requests using "Large Value" last-byte-pos values.
+            This document describes a usage model for range requests which enables
+            efficient retrieval of representations that are appended to over time
+            by utilizing large values and associated semantics for communicating

https://grammarpartyblog.com/2012/01/17/use-versus-utilize/

In draft-ietf-httpbis-rand-access-live.xml:

> -       </list>
+            This document recommends a two-step process for accessing resources
+            that have indeterminate length representations.
+            
+            Two steps are necessary because of limitations with the Range request
+            header and the Content-Range response header fields. A server cannot
+            know from a range request that a client wishes to receive a response
+            that does not have a definite end. More critically, the header fields
+            do not allow the server to signal that a resource has indeterminate
+            length without also providing a fixed portion of the resource.
+
+            A client first learns that the resource has a representation of
+            indeterminate length by requesting a range of the resource. The server
+            responds with the range that is available, but indicates that the
+            length of the representation is unknown using the existing
+            Content-Range syntax. See Section 2.1 for details and examples.

for the section reference.

In draft-ietf-httpbis-rand-access-live.xml:

> +
+            A client first learns that the resource has a representation of
+            indeterminate length by requesting a range of the resource. The server
+            responds with the range that is available, but indicates that the
+            length of the representation is unknown using the existing
+            Content-Range syntax. See Section 2.1 for details and examples.
+
+            Once the client knows the resource has indeterminate length, it can
+            request a range with a very large end position from the resource. The
+            client chooses an explicit end value larger than can be transferred in
+            the foreseeable term. A server which supports range requests of
+            indeterminate length signals its understanding of the client's
+            indeterminate range request by indicating that the range it is
+            providing has a range end that exactly matches the client's requested
+            range end rather than a range that is bounded by what is currently
+            available. See Sections 2.2 and 2.3 for details.

xrefs

In draft-ietf-httpbis-rand-access-live.xml:

>  </artwork></figure>
       <t>
-        could return
+        will return

maybe "will return a range covering only those bytes that are currently available:"

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -390,7 +423,9 @@
 
     <section anchor="Security" title="Security Considerations">
         <t>
-      One potential issue with this recommendation is related to the use of very-large last-byte-pos values. Some Client and Server implementations may not be prepared to deal with byte position values of 2^^63 and beyond. So in applications where there's no expectation that the representation will ever exceed 2^^63, a value smaller than this value should be used as the Very Large last-byte-pos in a byte-seek request or content-range response.
+      One potential issue with this recommendation is related to the use of very-large last-byte-pos values. Some client and server implementations may not be prepared to deal with byte position values of 2^^63 and beyond. So in applications where there's no expectation that the representation will ever exceed 2^^63, a value smaller than this value should be used as the Very Large last-byte-pos in a byte-seek request or content-range response.
+      
+      Also, some implementations (e.g. JavaScript-based clients and servers) are not able to represent all values beyond 2^^53. So similarly, if there's no expectation that a representation will ever exceed 2^^63 bytes, values smaller than this limit should be used for the last-byte-pos in byte-range requests.

it's less about representation for this, but about ease of parsing

I think that the second value here could be 2^53 instead of 2^63.

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -210,24 +232,26 @@
    byte-range-spec = first-byte-pos "-" [ last-byte-pos ]
 </artwork></figure>
       <t>
-      which allows a Client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A Server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a Client-issued HEAD request performed against a continuously aggregating representation hosted on a Server could contain a byte-range header of the form:
+      which allows a client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a client-issued HEAD request performed against a continuously aggregating representation hosted on a server could contain a byte-range header of the form:

The "must" here is incorrect. It can provide the entire representation (for instance, if it didn't support range requests). Maybe "might".

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -210,24 +232,26 @@
    byte-range-spec = first-byte-pos "-" [ last-byte-pos ]
 </artwork></figure>
       <t>
-      which allows a Client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A Server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a Client-issued HEAD request performed against a continuously aggregating representation hosted on a Server could contain a byte-range header of the form:
+      which allows a client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a client-issued HEAD request performed against a continuously aggregating representation hosted on a server could contain a byte-range header of the form:

Finally, the client doesn't necessarily know that the resource is continuously aggregating. Maybe just say "For example, a client issues a request for an indefinite range of bytes as follows:"

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a04c48038566_6ee53fd8b7b58f2c3641d0-- From nobody Fri Nov 10 02:27:34 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=OlhAvphNZlhygE7H3Kc/v/RVa8E=; b=N2j+xqJP1ys0/Wsl YW0CyQueKo9CsTLv4eqYaNxAjBPe5KtmJ0Jfw2p2lho6zWo7CCcuYntD2cLTpj9O dN5IijA8Cv8peBEDaZBUhU1U9QA54w4NeXG8Zj5Db+6dnP2lqjalrwQ75390pskV Tt2ED9GIIOuiXKvYjVI1QodXvlE= Date: Fri, 10 Nov 2017 10:27:30 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Incorporated comments from MartinT and some of my own edits to draft-ietf-httpbis-rand-access-live (#414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a057f11a697c_62413fef23180f2c2228c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 10:27:32 -0000 ----==_mimepart_5a057f11a697c_62413fef23180f2c2228c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit craigpratt commented on this pull request. > @@ -166,16 +166,22 @@

@craigpratt commented on this pull request.

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -166,16 +166,22 @@
     
     <section anchor="introduction" title="Introduction">
         <t>
-             Some Hypertext Transfer Protocol (HTTP) Clients use byte-range requests (Range requests using the "bytes" Range Unit) to transfer select portions of large representations. And in some cases large representations require content to be continuously or periodically appended - such as representations consisting of live audio or video sources, blockchain databases, and log files. Clients cannot access the appended/live content using a Range request with the bytes range unit using the currently defined byte-range semantics without accepting performance or behavior sacrifices which are not acceptable for many applications.
+             Some Hypertext Transfer Protocol (HTTP) clients use byte-range requests (Range requests using the "bytes" Range Unit) to transfer select portions of large representations. And in some cases large representations require content to be continuously or periodically appended - such as representations consisting of live audio or video sources, blockchain databases, and log files. clients cannot access the appended/live content using a Range request with the bytes range unit using the currently defined byte-range semantics without accepting performance or behavior sacrifices which are not acceptable for many applications.

Yeah - I think I recall hearing that rule in an English class once...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a057f11a697c_62413fef23180f2c2228c8-- From nobody Fri Nov 10 02:29:12 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.396 X-Spam-Level: X-Spam-Status: No, score=-3.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=uRfxvScsWzte6ZhSDNOUG4MQRMM=; b=L15OKv4MvmjxVeCh 9/MhRUpPjZkDKnv3klqtOlRN/34wcKhGrI/2C8kHTM3XY70xsy7Nu1w0yfTeNTqc 0JxpgAXO+6dy17qOC5lw6TAJmxW3FVZmws2N57Al4XZvvM3xdJDP+7RQ7fCpwbWX OI8W+hv/NZXmFe+nTOaTK2fqTTY= Date: Fri, 10 Nov 2017 10:29:08 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Incorporated comments from MartinT and some of my own edits to draft-ietf-httpbis-rand-access-live (#414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a057f7434360_62283fef23180f2c133359"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 10:29:11 -0000 ----==_mimepart_5a057f7434360_62283fef23180f2c133359 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit craigpratt commented on this pull request. > - To accommodate byte-range requests on large representations which have data appended over time efficiently and with low latency, this recommendation defines semantics whereby the HTTP Client performs byte-range requests using a combination of open-ended byte-range HEAD requests and GET requests using "Large Value" last-byte-pos values. + This document describes a usage model for range requests which enables + efficient retrieval of representations that are appended to over time + by utilizing large values and associated semantics for communicating Guess I never really thought about it that much. No problem with changing it. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/414#discussion_r150200934 ----==_mimepart_5a057f7434360_62283fef23180f2c133359 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@craigpratt commented on this pull request.

In draft-ietf-httpbis-rand-access-live.xml:

>          </t>
         <t>
-			To accommodate byte-range requests on large representations which have data appended over time efficiently and with low latency, this recommendation defines semantics whereby the HTTP Client performs byte-range requests using a combination of open-ended byte-range HEAD requests and GET requests using "Large Value" last-byte-pos values.
+            This document describes a usage model for range requests which enables
+            efficient retrieval of representations that are appended to over time
+            by utilizing large values and associated semantics for communicating

Guess I never really thought about it that much. No problem with changing it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a057f7434360_62283fef23180f2c133359-- From nobody Fri Nov 10 02:31:08 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=PYtxQOKdi4USX99cS92gjx5narY=; b=CmCMIqSfWlBQ1PyI n4VqsPjRkfe4BBjvfFhb148mtCpgjJ6G+hHRHRTU5+ra5KSPtMLNWo2pWz1QKL4m w9fNHh0z6KTj0XpGwBEVnxdjvC+bt7zf/lo44co5mf+qDe5LiFdgg//Gqaj1RUg7 +/ceTzjS5YVJszVonYB0TqEEWE8= Date: Fri, 10 Nov 2017 10:31:02 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Incorporated comments from MartinT and some of my own edits to draft-ietf-httpbis-rand-access-live (#414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a057fe5842da_4b4d3fa9b9afcf382885ed"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 10:31:05 -0000 ----==_mimepart_5a057fe5842da_4b4d3fa9b9afcf382885ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit craigpratt commented on this pull request. > @@ -210,24 +232,26 @@ byte-range-spec = first-byte-pos "-" [ last-byte-pos ] - which allows a Client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A Server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a Client-issued HEAD request performed against a continuously aggregating representation hosted on a Server could contain a byte-range header of the form: + which allows a client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a client-issued HEAD request performed against a continuously aggregating representation hosted on a server could contain a byte-range header of the form: ok - simplified the setup... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/414#discussion_r150201306 ----==_mimepart_5a057fe5842da_4b4d3fa9b9afcf382885ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@craigpratt commented on this pull request.

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -210,24 +232,26 @@
    byte-range-spec = first-byte-pos "-" [ last-byte-pos ]
 </artwork></figure>
       <t>
-      which allows a Client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A Server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a Client-issued HEAD request performed against a continuously aggregating representation hosted on a Server could contain a byte-range header of the form:
+      which allows a client to send a HEAD request with a first-byte-pos and leave last-byte-pos absent. A server that receives a satisfiable byte-range request (with first-byte-pos smaller than the current representation length) must respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example, a client-issued HEAD request performed against a continuously aggregating representation hosted on a server could contain a byte-range header of the form:

ok - simplified the setup...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a057fe5842da_4b4d3fa9b9afcf382885ed-- From nobody Fri Nov 10 02:31:12 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.182 X-Spam-Level: X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=uqNzLw/t+Z0fVJYcahfzO04IOvE=; b=ZBQvQ/+HY0grR1QQ uh7q4LeX2C5OGlNgDDS/u1jbHK/IZBGALh/cJDYY5yXrHomqnaEo84B+ovVzxdFO fvda+9ME9ruXChcxkX0A66Yuv5IQmqBDJx9ZPRTrXvr85u614gq2YPnfQgniiHfc R+xpqsNdFvagN/UGk7j7bgXxA70= Date: Fri, 10 Nov 2017 10:31:02 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Incorporated comments from MartinT and some of my own edits to draft-ietf-httpbis-rand-access-live (#414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a057fe67ddcc_ade43fa8107c2f34201562"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 10:31:06 -0000 ----==_mimepart_5a057fe67ddcc_ade43fa8107c2f34201562 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit craigpratt commented on this pull request. > - could return + will return fixed -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/414#discussion_r150201314 ----==_mimepart_5a057fe67ddcc_ade43fa8107c2f34201562 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@craigpratt commented on this pull request.

In draft-ietf-httpbis-rand-access-live.xml:

>  </artwork></figure>
       <t>
-        could return
+        will return

fixed

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a057fe67ddcc_ade43fa8107c2f34201562-- From nobody Fri Nov 10 02:32:04 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=0hVarPxQJoGcFJvK7RmjARp53TU=; b=MmOANnt68JG5uAho z9Tkp0tkUVc4B4loweOJdLB4b4dCRmkH0oo2bvzYhcf+YJ1+EoXUUi3p8J+VWX2Q FlymhyjzShUWQMULWLGcjXiw2aaoYHgcUldnJlFGjACO5Xz/kQu4CleQRAHypcFd FgCFz+3GBOeWsqRrKRdWXdxFv2U= Date: Fri, 10 Nov 2017 10:31:59 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Incorporated comments from MartinT and some of my own edits to draft-ietf-httpbis-rand-access-live (#414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a05801ed033a_924f3fa299bd4f2c128165"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 10:32:03 -0000 ----==_mimepart_5a05801ed033a_924f3fa299bd4f2c128165 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit craigpratt commented on this pull request. > @@ -390,7 +423,9 @@

@craigpratt commented on this pull request.

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -390,7 +423,9 @@
 
     <section anchor="Security" title="Security Considerations">
         <t>
-      One potential issue with this recommendation is related to the use of very-large last-byte-pos values. Some Client and Server implementations may not be prepared to deal with byte position values of 2^^63 and beyond. So in applications where there's no expectation that the representation will ever exceed 2^^63, a value smaller than this value should be used as the Very Large last-byte-pos in a byte-seek request or content-range response.
+      One potential issue with this recommendation is related to the use of very-large last-byte-pos values. Some client and server implementations may not be prepared to deal with byte position values of 2^^63 and beyond. So in applications where there's no expectation that the representation will ever exceed 2^^63, a value smaller than this value should be used as the Very Large last-byte-pos in a byte-seek request or content-range response.
+      
+      Also, some implementations (e.g. JavaScript-based clients and servers) are not able to represent all values beyond 2^^53. So similarly, if there's no expectation that a representation will ever exceed 2^^63 bytes, values smaller than this limit should be used for the last-byte-pos in byte-range requests.

fixed

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a05801ed033a_924f3fa299bd4f2c128165-- From nobody Fri Nov 10 02:49:23 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=yZOe3CgpQSDbgIai8R+Uhm0bScI=; b=d9ACTqcBtQAcitYn Xjeq2m+bEe6Qte2jCub07WRauQw0l0UjsYdzXJaAxKklFExb16ChnpBOeHJSuRBu /HAQ2BnFIHAYeZSnh7u/aWc5hAexxSatQJ9bDttxzZVSroqF5kIN8O5Zy3j+Zj+H i5mozmftFaCCEai8EF9gcxLYP08= Date: Fri, 10 Nov 2017 10:49:18 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Incorporated comments from MartinT and some of my own edits to draft-ietf-httpbis-rand-access-live (#414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a05842e8d3df_45143ff7e8936f281675aa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 10:49:21 -0000 ----==_mimepart_5a05842e8d3df_45143ff7e8936f281675aa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @craigpratt pushed 1 commit. 28aebf0 Incorporated a few more suggested edits and fixed some xrefs -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/414/files/21b611b6ad20334af2ac2cc855c0c7a2c3c267c3..28aebf005b5060c2260ce90c6af9765289850a1d ----==_mimepart_5a05842e8d3df_45143ff7e8936f281675aa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@craigpratt pushed 1 commit.

28aebf0 Incorporated a few more suggested edits and fixed some xrefs

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a05842e8d3df_45143ff7e8936f281675aa-- From nobody Fri Nov 10 02:57:05 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=h1RtnBvzeiiHljhwTQhj+ndNlTs=; b=pstFZwu1H9CMcv+R 7TXfTNKEjQ+K6+X8xO5rXrAocw7zJL5KhoC+nb2fxv91PuSv8aschbo5x/y5Thv9 UZMXzhEIlMp0pHFWmj3YaVbUqFduCQNc0pKVTCL65aF+8+bwgUPnxtWNPKmW7Wtd zSLjy/bn4eGdPALeF6XhmEEXsC8= Date: Fri, 10 Nov 2017 10:57:02 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Incorporated comments from MartinT and some of my own edits to draft-ietf-httpbis-rand-access-live (#414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0585fdec4a0_26c03f969ba4af301531f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 10:57:04 -0000 ----==_mimepart_5a0585fdec4a0_26c03f969ba4af301531f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #414. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/414#event-1335835766 ----==_mimepart_5a0585fdec4a0_26c03f969ba4af301531f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #414.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a0585fdec4a0_26c03f969ba4af301531f3-- From nobody Fri Nov 10 03:11:03 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=cfOIHTrB2fSWcZvFm9OT48VElDA=; b=jf1O/ghh+WYo8hHv 8vtVJEofpFEwTWViEF8rGTKTtTzvHZqUvSMEcm7gN6XeYd0TRtInOi9IpXnuYY// /N+GpNFCIfCmEFE76MeWoQ7XaaRn5qS7Had/1yso2rvD8pfH50SMiOiQJFe6C9ZS Z43YCYdrru3mWTZrWHLaXGaNdkE= Date: Fri, 10 Nov 2017 11:10:59 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] ABNF reference (#415) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a058942b0ce8_26b73f969ba4af30286336"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 11:11:02 -0000 ----==_mimepart_5a058942b0ce8_26b73f969ba4af30286336 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 1) It should be RFC 5234, not RFC 4234 2) If it's there, it should actually be mentioned somewhere in the spec. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/415 ----==_mimepart_5a058942b0ce8_26b73f969ba4af30286336 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

It should be RFC 5234, not RFC 4234
If it's there, it should actually be mentioned somewhere in the spec.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a058942b0ce8_26b73f969ba4af30286336-- From nobody Sun Nov 12 06:10:06 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.8 X-Spam-Level: X-Spam-Status: No, score=-4.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=5t+YDZ1nnW1eUKG0diMf4GqsHiw=; b=u/2pB/aiPiJLnGfZ cynNEYj+Of+ca23M7KRiDCWWqkwu1xyLj+ui7Qq+xIuSB+iGfQ7WszPSGk1Fv8/S cAvCxgNurcEePKg0r1IuPlkwkrUmC1zF7bqmFWyVUm6Crh1v6mE1jJwVedqJnYYv /BcuYp9SwNff8xjGI+fa0fo3D0o= Date: Sun, 12 Nov 2017 14:09:58 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a085635f3ab8_713f3f8c8a1e4f2823155c6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2017 14:10:04 -0000 ----==_mimepart_5a085635f3ab8_713f3f8c8a1e4f2823155c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sebdeckers requested changes on this pull request. Feedback based on WIP implementation of cuckoo filters for cache digest: https://gitlab.com/http2/cache-digest-koel > -### Computing a Hash Value {#hash} +* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}} +* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null); +* `digest-value` + +1. Let `f` be the value of the first byte of `digest-value`. +3. Let `N` be the value of the second to fifth bytes of `digest-value` in big endian form. +4. Let `key` be the return value of {{key}} with `URL` and `ETag` as inputs. +5. Let `h1` be the return value of {{hash}} with `key` and `N` as inputs. +6. Let `fingerprint` be the return value of {{fingerprint}} with `key`, `N` and `f` as inputs. +7. Let `h2` be the return value of {{hash}} with `fingerprint` and `N` as inputs, XORed with `h1`. +8. Let `h` be `h1`. +9. Let `position_start` be 40 + `h` * `f`. +10. Let `position_end` be `position_start` + `f` * `b`. `b` is not defined > -`hash-value` can be computed using the following algorithm: +1. Let `hash-value` be the return value of {{hash}} with `key` and `N` as inputs. +2. Let `h` be the number of bits in `hash-value` +3. Let `fingerprint-value` be 0 +4. While `fingerprint-value` is 0 and `h` > `f`: + 4.1. Let `fingerprint-value` be the `f` least significant bits of `hash-value`. + 4.2. Let `hash-value` be the the `h`-`f` most significant bits of `hash-value`. + 4.3. `h` -= `f` This code feels inconsistent with the writing style used throughout. Would suggest: > Substract `f` from `h`. > +Given the following inputs: + +* `key`, an array of characters. +* `N`, an integer + +`hash-value` can be computed using the following algorithm: + +1. Let `hash-value` be the SHA-256 message digest {{RFC6234}} of `key`, expressed as an integer. +2. Return `hash-value` modulo N. This is difficult to do in JavaScript where uint operations are typically still limited to 32 bits. The truncation in the previous proposal (step 4) is more compatible and, if I understand correctly, achieves the same objective. Can this be changed to something that does not require 512 bit integer modulo? > -* `URL`, an array of characters -* `ETag`, an array of characters -* `validators`, a boolean +* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}. +* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null). +* `digest-value`, an array of bits. + +1. Let `f` be the value of the first byte of `digest-value`. +3. Let `N` be the value of the second to fifth bytes of `digest-value` in big endian form. +4. Let `key` be the return value of {{key}} with `URL` and `ETag` as inputs. +5. Let `h1` be the return value of {{hash}} with `key` and `N` as inputs. +6. Let `fingerprint` be the return value of {{fingerprint}} with `key`, `N` and `f` as inputs. +7. Let `h2` be the return value of {{hash}} with `fingerprint` and `N` as inputs, XORed with `h1`. +8. Let `h` be `h1`. +9. Let `position_start` be 40 + `h` * `f`. +10. Let `position_end` be `position_start` + `f` * `b`. `b` is not defined > -* `digest-value`, an array of bits -* `URL`, an array of characters -* `ETag`, an array of characters -* `validators`, a boolean +* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}. +* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null). >From an implementor's perspective, it would help me to understand this if examples were provided. > @@ -99,10 +102,9 @@ allows a stream to be cancelled by a client using a RST_STREAM frame in this sit is still at least one round trip of potentially wasted capacity even then. This specification defines a HTTP/2 frame type to allow clients to inform the server of their -cache's contents using a Golomb-Rice Coded Set {{Rice}}. Servers can then use this to inform their +cache's contents using a Cuckoo-fliter {{Cuckoo}} based digest. Servers can then use this to inform their typo: `filter` > CACHE_DIGEST has no defined meaning when sent from servers, and SHOULD be ignored by clients. -### Computing the Digest-Value {#computing} +### Creating a digest {#creating} +Given the following inputs: +* `P`, an integer smaller than 256, that indicates the probability of a false positive that is acceptable, expressed as `1/2\*\*P`. +* `N`, an integer that represents the number of entries - a prime number smaller than 2\*\*32 + +1. Let `f` be the number of bits per fingerprint, calculated as `P + 3` +2. Let `b` be the bucket size, defined as 4 +3. Let `bytes` be `f`*`N`*`b`/8 rounded up to the nearest integer Markdown escaping issue makes `N` italic and hides the `*` characters. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#pullrequestreview-75959915 ----==_mimepart_5a085635f3ab8_713f3f8c8a1e4f2823155c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@sebdeckers requested changes on this pull request.

Feedback based on WIP implementation of cuckoo filters for cache digest: https://gitlab.com/http2/cache-digest-koel

In draft-ietf-httpbis-cache-digest.md:

>  
-### Computing a Hash Value {#hash}
+* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}
+* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null);
+* `digest-value`
+
+1. Let `f` be the value of the first byte of `digest-value`.
+3. Let `N` be the value of the second to fifth bytes of `digest-value` in big endian form.
+4. Let `key` be the return value of {{key}} with `URL` and `ETag` as inputs.
+5. Let `h1` be the return value of {{hash}} with `key` and `N` as inputs.
+6. Let `fingerprint` be the return value of {{fingerprint}} with `key`, `N` and `f` as inputs.
+7. Let `h2` be the return value of {{hash}} with `fingerprint` and `N` as inputs, XORed with `h1`.
+8. Let `h` be `h1`.
+9. Let `position_start` be 40 + `h` * `f`.
+10. Let `position_end` be `position_start` + `f` * `b`.

b is not defined

In draft-ietf-httpbis-cache-digest.md:

>  
-`hash-value` can be computed using the following algorithm:
+1. Let `hash-value` be the return value of {{hash}} with `key` and `N` as inputs.
+2. Let `h` be the number of bits in `hash-value`
+3. Let `fingerprint-value` be 0
+4. While `fingerprint-value` is 0 and `h` > `f`:
+    4.1. Let `fingerprint-value` be the `f` least significant bits of `hash-value`.
+    4.2. Let `hash-value` be the the `h`-`f` most significant bits of `hash-value`.
+    4.3. `h` -= `f`

This code feels inconsistent with the writing style used throughout. Would suggest:

Substract f from h.

In draft-ietf-httpbis-cache-digest.md:

>  
+Given the following inputs:
+
+* `key`, an array of characters.
+* `N`, an integer
+
+`hash-value` can be computed using the following algorithm:
+
+1. Let `hash-value` be the SHA-256 message digest {{RFC6234}} of `key`, expressed as an integer.
+2. Return `hash-value` modulo N.

This is difficult to do in JavaScript where uint operations are typically still limited to 32 bits. The truncation in the previous proposal (step 4) is more compatible and, if I understand correctly, achieves the same objective. Can this be changed to something that does not require 512 bit integer modulo?

In draft-ietf-httpbis-cache-digest.md:

> -* `URL`, an array of characters
-* `ETag`, an array of characters
-* `validators`, a boolean
+* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}.
+* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null).
+* `digest-value`, an array of bits.
+
+1. Let `f` be the value of the first byte of `digest-value`.
+3. Let `N` be the value of the second to fifth bytes of `digest-value` in big endian form.
+4. Let `key` be the return value of {{key}} with `URL` and `ETag` as inputs.
+5. Let `h1` be the return value of {{hash}} with `key` and `N` as inputs.
+6. Let `fingerprint` be the return value of {{fingerprint}} with `key`, `N` and `f` as inputs.
+7. Let `h2` be the return value of {{hash}} with `fingerprint` and `N` as inputs, XORed with `h1`.
+8. Let `h` be `h1`.
+9. Let `position_start` be 40 + `h` * `f`.
+10. Let `position_end` be `position_start` + `f` * `b`.

b is not defined

In draft-ietf-httpbis-cache-digest.md:

>  
-* `digest-value`, an array of bits
-* `URL`, an array of characters
-* `ETag`, an array of characters
-* `validators`, a boolean
+* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}.
+* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null).

From an implementor's perspective, it would help me to understand this if examples were provided.

In draft-ietf-httpbis-cache-digest.md:

> @@ -99,10 +102,9 @@ allows a stream to be cancelled by a client using a RST_STREAM frame in this sit
 is still at least one round trip of potentially wasted capacity even then.
 
 This specification defines a HTTP/2 frame type to allow clients to inform the server of their
-cache's contents using a Golomb-Rice Coded Set {{Rice}}. Servers can then use this to inform their
+cache's contents using a Cuckoo-fliter {{Cuckoo}} based digest. Servers can then use this to inform their

typo: filter

In draft-ietf-httpbis-cache-digest.md:

>  
 CACHE_DIGEST has no defined meaning when sent from servers, and SHOULD be ignored by clients.
 
 
-### Computing the Digest-Value {#computing}
+### Creating a digest {#creating}
+Given the following inputs:
+* `P`, an integer smaller than 256, that indicates the probability of a false positive that is acceptable, expressed as `1/2\*\*P`.
+* `N`, an integer that represents the number of entries - a prime number smaller than 2\*\*32
+
+1. Let `f` be the number of bits per fingerprint, calculated as `P + 3`
+2. Let `b` be the bucket size, defined as 4
+3. Let `bytes` be `f`*`N`*`b`/8 rounded up to the nearest integer

Markdown escaping issue makes N italic and hides the * characters.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a085635f3ab8_713f3f8c8a1e4f2823155c6-- From nobody Sun Nov 12 08:13:52 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=4pLM+gyxsGCaEFmPNsXegLVSwmo=; b=jVwdQOTYjK7cToM5 F68hPCvqboV504HzlcUnKu1TzFpiR6h9EgBdi03dST87mi4hxwFGIjCq0z0CrH5Z w7dpQVqToUlK03aDUFUpFW+wiCgv4kHSVsALIbH1qgIIoiH3YowVjr6NDnHzarSu TZk352vZcAsQMdXeQwUijBVC1M0= Date: Sun, 12 Nov 2017 16:13:47 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Expect-CT should be extended with concept of test reports (#416) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a08733aae5a9_ca23fc321bcaf382177146"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2017 16:13:50 -0000 ----==_mimepart_5a08733aae5a9_ca23fc321bcaf382177146 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Here's my use case: I am developing a testing tool (Hardenize), which analyses web site configuration and tries to determine if everything is in order. If I see Expect-CT on a site I need to know if the configured reporting endpoint is operational. It's all to easy for a reporting endpoint to break for whatever reason and without anyone noticing. I think this will be especially problematic for Expect-CT, which I would expect to be a "quiet" header. To that end, I'd like to submit a test report and examine the response. For this to work properly, we need 1) an ability to indicate that a report is being submitted for testing purposes only and 2) for the server to be able to signal if the report is being accepted. With 1, the server can process the test response as it would a real one, but MAY delete it afterwards. With 2, the testing tool can determine if the endpoint is working correctly. For #2, the RFC could be extended with section 3.3 Receiving a violation report, which could say that servers should respond with 200 if they are happy and able to receive a report for the indicated hostname, 4xx if there's something's wrong with the report (e.g., the indicated hostname is not known to the server), and 5xx if there is some other problem. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/416 ----==_mimepart_5a08733aae5a9_ca23fc321bcaf382177146 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Here's my use case: I am developing a testing tool (Hardenize), which analyses web site configuration and tries to determine if everything is in order. If I see Expect-CT on a site I need to know if the configured reporting endpoint is operational. It's all to easy for a reporting endpoint to break for whatever reason and without anyone noticing. I think this will be especially problematic for Expect-CT, which I would expect to be a "quiet" header.

To that end, I'd like to submit a test report and examine the response. For this to work properly, we need 1) an ability to indicate that a report is being submitted for testing purposes only and 2) for the server to be able to signal if the report is being accepted. With 1, the server can process the test response as it would a real one, but MAY delete it afterwards. With 2, the testing tool can determine if the endpoint is working correctly.

For #2, the RFC could be extended with section 3.3 Receiving a violation report, which could say that servers should respond with 200 if they are happy and able to receive a report for the indicated hostname, 4xx if there's something's wrong with the report (e.g., the indicated hostname is not known to the server), and 5xx if there is some other problem.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a08733aae5a9_ca23fc321bcaf382177146-- From nobody Sun Nov 12 08:20:07 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=VuC62wVyfL8nSDSXjQsQPjrXoCc=; b=t2Si1yShS9Dgij2a W3ntQcK087RpbCFWwcQbdy/FO4rBFelVTD+Qlec2/dsVIliQerVgq8p9JYmCLic9 lJ2nKeWb8rGg2BR2gOkCGTnn2/aVf85G9MdgCzOY7FKBuIa0BEDwXnXfvTDjdsRB usUrMfpFBm9ejVQZldyRF3V5VWk= Date: Sun, 12 Nov 2017 16:20:03 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Expect-CT reports should indicate failure mode (report only or enforcing) (#417) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0874b31d97e_62683fa3c431ef2826027f4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2017 16:20:05 -0000 ----==_mimepart_5a0874b31d97e_62683fa3c431ef2826027f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From an operational perspective, site operators need to be able to distinguish if Expect-CT failure caused access to the site to be denied. In any organisation of non-trivial size it's likely that there will be a mixture of sites with report-only and enforcing policies. Thus, not all reports are equal. A failure of enforcing Expect-CT needs to be treated with urgency and perhaps an immediate action. Failures of report-only policies are not urgent and can be reviewed from time to time during normal working hours. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/417 ----==_mimepart_5a0874b31d97e_62683fa3c431ef2826027f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

From an operational perspective, site operators need to be able to distinguish if Expect-CT failure caused access to the site to be denied. In any organisation of non-trivial size it's likely that there will be a mixture of sites with report-only and enforcing policies. Thus, not all reports are equal. A failure of enforcing Expect-CT needs to be treated with urgency and perhaps an immediate action. Failures of report-only policies are not urgent and can be reviewed from time to time during normal working hours.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a0874b31d97e_62683fa3c431ef2826027f4-- From nobody Mon Nov 13 01:56:05 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.615 X-Spam-Level: X-Spam-Status: No, score=-0.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=F2nnmRrVy+0pYs1yU5hLpxD3BPg=; b=mNW1QbiZkSfyGr/9 hgY5Z+rrh7PhYswnxZUmRKZKNRmz6c71dcQTX9a1oq/M1L35zi4Xh4lrKwbhtK0Y 5XhTmmKPlHpSpD20SQ9e339oPGIP8mzraUPVPcEgIiGwtymJoiUyeoWI8Ng1E1of 55OaxwCX+KwvTTiLpQ+aa+IBGgs= Date: Mon, 13 Nov 2017 09:56:02 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a096c314097b_304b3f7ee4df0f2862466d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2017 09:56:04 -0000 ----==_mimepart_5a096c314097b_304b3f7ee4df0f2862466d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > +Given the following inputs: + +* `key`, an array of characters. +* `N`, an integer + +`hash-value` can be computed using the following algorithm: + +1. Let `hash-value` be the SHA-256 message digest {{RFC6234}} of `key`, expressed as an integer. +2. Return `hash-value` modulo N. I wonder if the need for an integer modulo is due to an error in the specification. The text in the PR states that `N` is `a prime number smaller than 2\*\*32`. Could it be the case that N is something to be defined as 2^N? If that is the case, the modulo operation can be implemented by using bitwise AND. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#discussion_r150489909 ----==_mimepart_5a096c314097b_304b3f7ee4df0f2862466d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-httpbis-cache-digest.md:

>  
+Given the following inputs:
+
+* `key`, an array of characters.
+* `N`, an integer
+
+`hash-value` can be computed using the following algorithm:
+
+1. Let `hash-value` be the SHA-256 message digest {{RFC6234}} of `key`, expressed as an integer.
+2. Return `hash-value` modulo N.

I wonder if the need for an integer modulo is due to an error in the specification.

The text in the PR states that N is a prime number smaller than 2\*\*32. Could it be the case that N is something to be defined as 2^N?

If that is the case, the modulo operation can be implemented by using bitwise AND.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a096c314097b_304b3f7ee4df0f2862466d-- From nobody Mon Nov 13 20:56:34 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=C8YLlk13CeLz8zvFma98S9uC17U=; b=oAaTS/VSoPMlW0dp yjx+wzPyhTTQUzZ17HUcZq+A1FujQLfyHL3IExfaRclqMiFRLv3oJjZW5m+YHAOr Tj9dh5P3GXyE8S700Q80Q0aVC5sOXi2pIn25j4oPI6AAYD0+5HHVLu19uZ/K//vJ Ebnb3DHRrDcstDA6aiPQeHFWKAE= Date: Tue, 14 Nov 2017 04:56:32 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0a777f51fc8_6b663f98ef596f3811167c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 04:56:34 -0000 ----==_mimepart_5a0a777f51fc8_6b663f98ef596f3811167c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss pushed 2 commits. f4bf0a5 define b afdbca9 Review comments -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/413/files/375600c7439cf57fb6d2baff5f0f97a1d0e701f6..afdbca9a7761c0a47077358ec964bedec443057e ----==_mimepart_5a0a777f51fc8_6b663f98ef596f3811167c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss pushed 2 commits.

f4bf0a5 define b
afdbca9 Review comments

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a0a777f51fc8_6b663f98ef596f3811167c-- From nobody Mon Nov 13 20:56:46 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.799 X-Spam-Level: X-Spam-Status: No, score=-4.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=3iYcoPKrGM4Aet0qsNaZ1PtDaWY=; b=lREir8fVaP1vDhOk 75KyVXUhmFkrAfdqApB41WjXDrDbqmrHko8iQJq0h7Oc7/T89qnybR6Ja8OsRf2l QYnsYvuxULjycJ+KR1p0RXNfR4bnncWCLUKfgAT1STe64rYjXIKG/B7p2IGM4Doe wD58y8wlIYBjkmUs18p65nBByAM= Date: Tue, 14 Nov 2017 04:56:42 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0a778a776ad_69d33fd499194f301381a9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 04:56:45 -0000 ----==_mimepart_5a0a778a776ad_69d33fd499194f301381a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit yoavweiss commented on this pull request. > -* `digest-value`, an array of bits -* `URL`, an array of characters -* `ETag`, an array of characters -* `validators`, a boolean +* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}. +* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null). Examples for URL and ETag? Or something else? > +Given the following inputs: + +* `key`, an array of characters. +* `N`, an integer + +`hash-value` can be computed using the following algorithm: + +1. Let `hash-value` be the SHA-256 message digest {{RFC6234}} of `key`, expressed as an integer. +2. Return `hash-value` modulo N. OK, I'll truncate the hash before the modulo operation. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#discussion_r150734811 ----==_mimepart_5a0a778a776ad_69d33fd499194f301381a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss commented on this pull request.

In draft-ietf-httpbis-cache-digest.md:

>  
-* `digest-value`, an array of bits
-* `URL`, an array of characters
-* `ETag`, an array of characters
-* `validators`, a boolean
+* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}.
+* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null).

Examples for URL and ETag? Or something else?

In draft-ietf-httpbis-cache-digest.md:

>  
+Given the following inputs:
+
+* `key`, an array of characters.
+* `N`, an integer
+
+`hash-value` can be computed using the following algorithm:
+
+1. Let `hash-value` be the SHA-256 message digest {{RFC6234}} of `key`, expressed as an integer.
+2. Return `hash-value` modulo N.

OK, I'll truncate the hash before the modulo operation.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a0a778a776ad_69d33fd499194f301381a9-- From nobody Mon Nov 13 21:20:07 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=5J3gT0la+B5eLaFpuqbFPpteCRg=; b=emNt2zvnZZskjAcF 0h8xK9Y6MPAlOpqiOG3Wa4PLII9zh//p6B1DQFEaMaSKQB1IFgN4ugNFzcXbTH8o doTzHAH1XixY2czUUPOeUenktfRvOtRPZieYQflhcE00cePdaW0Yw4uqKzR7jmqP kjnhYfHZA4/VAQySSCKWdRoKB/o= Date: Tue, 14 Nov 2017 05:20:03 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0a7d031d254_7d593feda22c0f2c186419"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 05:20:06 -0000 ----==_mimepart_5a0a7d031d254_7d593feda22c0f2c186419 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sebdeckers commented on this pull request. > -* `digest-value`, an array of bits -* `URL`, an array of characters -* `ETag`, an array of characters -* `validators`, a boolean +* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}. +* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null). ETag Btw just noticed a typo on line 321: `of a cached response` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#discussion_r150739944 ----==_mimepart_5a0a7d031d254_7d593feda22c0f2c186419 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@sebdeckers commented on this pull request.

In draft-ietf-httpbis-cache-digest.md:

>  
-* `digest-value`, an array of bits
-* `URL`, an array of characters
-* `ETag`, an array of characters
-* `validators`, a boolean
+* `URL` a string corresponding to the Effective Request URI ({{RFC7230}}, Section 5.5) of a cached response {{RFC7234}}.
+* `ETag` a string corresponding to the entity-tag {{RFC7232}} if a cached response {{RFC7234}} (if the ETag is available; otherwise, null).

ETag

Btw just noticed a typo on line 321: of a cached response

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a0a7d031d254_7d593feda22c0f2c186419-- From nobody Mon Nov 13 21:31:08 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=T6pfuvtG5mKZRK8AcPJcKI6qt4M=; b=babvVzyWBY/B3L6p y7qEe5ItsW9WxGXeKX08H4+C4uhHQ+UNV+pyCtwPxf650pVm1iozR50gGf0DJtec 93fkIM7G4hduf6mf1XVFEMnlp4Ivh2HAfSVAxjZP0aA9/6wEWBoNBkjj+E9HPq6D +99EgL0funk+OPrugVup0emhU7c= Date: Tue, 14 Nov 2017 05:31:04 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0a7f97b377a_16b403fd759f56f3434207c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 05:31:06 -0000 ----==_mimepart_5a0a7f97b377a_16b403fd759f56f3434207c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss pushed 1 commit. 01a726a Typo -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/413/files/afdbca9a7761c0a47077358ec964bedec443057e..01a726a18807332d3752ca2b178b9da70adc85ad ----==_mimepart_5a0a7f97b377a_16b403fd759f56f3434207c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss pushed 1 commit.

01a726a Typo

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a0a7f97b377a_16b403fd759f56f3434207c-- From nobody Mon Nov 13 21:41:41 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=V/J3wpQRtSsx9/v3UVkr4lyvgis=; b=bKffqqgbfb+wFInT wf4/FL53j8H46Ww1TCpN9NnHO2kvXxRe5PDw9ntD6tPHfmx8gHqEaJQhznl+edPc MTkVdA3h452hehP7CMYSUpy7t7YN8a4sk7x7aC+svvztOM6oTGvOmnncMFnM4SNp 46vq0h2sEP2dbwwho2yQ5WZPcjY= Date: Tue, 14 Nov 2017 05:41:37 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0a8211b0c35_5d93fdcbe502f281071d1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 05:41:40 -0000 ----==_mimepart_5a0a8211b0c35_5d93fdcbe502f281071d1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss pushed 1 commit. 10b5b14 Style issues in `fingerprint` -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/413/files/01a726a18807332d3752ca2b178b9da70adc85ad..10b5b14e4c74ba77240af55ecd770aae3ce066a3 ----==_mimepart_5a0a8211b0c35_5d93fdcbe502f281071d1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss pushed 1 commit.

10b5b14 Style issues in `fingerprint`

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a0a8211b0c35_5d93fdcbe502f281071d1-- From nobody Mon Nov 13 22:01:53 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=kN2oXziXrOaL1FTuB8vizFEa5L0=; b=AHevN/0D/OjC8qQd 50Ol4LRoPzfzd/ZKkThkMZOjxhj47H0fBeuFPOBJ3rSK5oUPx2X9ykntFBYnBGWS biKiIsusr38Lkb+ZmLV9T5ZnDh1exb8kzUH9ssRAsFuvUjZvw0733vDTQSklTF2K qrEIZKm3ZfSW7LuBSN3Khxz3Ahw= Date: Tue, 14 Nov 2017 06:01:40 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0a86c416314_19093fbe5f2c2f38157248"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 06:01:47 -0000 ----==_mimepart_5a0a86c416314_19093fbe5f2c2f38157248 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss pushed 1 commit. d32c533 Fix wrong hash reference in fingerprint creation -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/413/files/10b5b14e4c74ba77240af55ecd770aae3ce066a3..d32c5332e86abfcaac6afaaf667508586f56aa87 ----==_mimepart_5a0a86c416314_19093fbe5f2c2f38157248 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss pushed 1 commit.

d32c533 Fix wrong hash reference in fingerprint creation

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a0a86c416314_19093fbe5f2c2f38157248-- From nobody Tue Nov 14 23:49:30 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.401 X-Spam-Level: X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=2xx7dka2VkKvqTksI1yJc3N180s=; b=ZoegUzU9eHLbayt/ JmCvFKQQ9szzLLOt4XztMyBuzJYYawKJn3TNVCP/rBiFsV6CqXD69MdYY5M/+b6D 5z+EY9Jdyn0696qr8eV0TqbunaxhyUqHttRlP8BIaJzJpDCN2QkL1ruz2K8cnrYC xNvhKPnVtpRevWuzRqYLKz6ogOM= Date: Wed, 15 Nov 2017 07:49:26 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0bf1869a685_2bc63fb23bfbcf349226f0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 07:49:28 -0000 ----==_mimepart_5a0bf1869a685_2bc63fb23bfbcf349226f0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss pushed 1 commit. c90f9b4 Define hashing of fingerprint -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/413/files/d32c5332e86abfcaac6afaaf667508586f56aa87..c90f9b4bc014efde6c843de8f9768dfb50d4d21d ----==_mimepart_5a0bf1869a685_2bc63fb23bfbcf349226f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss pushed 1 commit.

c90f9b4 Define hashing of fingerprint

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a0bf1869a685_2bc63fb23bfbcf349226f0-- From nobody Wed Nov 15 00:10:45 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.798 X-Spam-Level: X-Spam-Status: No, score=-4.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=xGV6SemJfChJ0E/aOaFRusWcxqk=; b=D2czwMp1XHDhosXT ahm9O9vNx6SS9ehzByYmJO7eiTqeilFqE3AOMXa8r8G6lCeiaS4JF7zOAmosW18K xTMlBralf8KTBVwYvJgrV80jFRnoDpcYdlUu6FdTp0kGECovukYMKtBViAi/IFAR ig6NqrTBrucZTFp+Igol8C7zYHw= Date: Wed, 15 Nov 2017 08:10:39 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0bf67eb9516_4cd3fccfa142f3811790b3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 08:10:44 -0000 ----==_mimepart_5a0bf67eb9516_4cd3fccfa142f3811790b3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sebdeckers commented on this pull request. > @@ -204,20 +204,21 @@ Given the following inputs: 4. Let `key` be the return value of {{key}} with `URL` and `ETag` as inputs. 5. Let `h1` be the return value of {{hash}} with `key` and `N` as inputs. 6. Let `fingerprint` be the return value of {{fingerprint}} with `key`, `N` and `f` as inputs. -7. Let `h2` be the return value of {{hash}} with `fingerprint` and `N` as inputs, XORed with `h1`. -8. Let `h` be either `h1` or `h2`, picked in random. -9. Let `position_start` be 40 + `h` * `f`. -10. Let `position_end` be `position_start` + `f` \* `b`. -11. While `position_start` < `position_end`: +7. Let `fingerprint-string` be the value of `fingerprint` in base 10, expressed as a string. @yoavweiss Curious... May I ask why this change? I don't see any issues with it. Just don't understand what it means. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#pullrequestreview-76700285 ----==_mimepart_5a0bf67eb9516_4cd3fccfa142f3811790b3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@sebdeckers commented on this pull request.

In draft-ietf-httpbis-cache-digest.md:

> @@ -204,20 +204,21 @@ Given the following inputs:
 4. Let `key` be the return value of {{key}} with `URL` and `ETag` as inputs.
 5. Let `h1` be the return value of {{hash}} with `key` and `N` as inputs.
 6. Let `fingerprint` be the return value of {{fingerprint}} with `key`, `N` and `f` as inputs.
-7. Let `h2` be the return value of {{hash}} with `fingerprint` and `N` as inputs, XORed with `h1`.
-8. Let `h` be either `h1` or `h2`, picked in random.
-9. Let `position_start` be 40 + `h` * `f`.
-10. Let `position_end` be `position_start` + `f` \* `b`.
-11. While `position_start` < `position_end`:
+7. Let `fingerprint-string` be the value of `fingerprint` in base 10, expressed as a string.

@yoavweiss Curious... May I ask why this change? I don't see any issues with it. Just don't understand what it means.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a0bf67eb9516_4cd3fccfa142f3811790b3-- From nobody Wed Nov 15 00:15:02 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.018 X-Spam-Level: X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=7dA84JZwMf+kIggpaxeih/+ZSD8=; b=kzVUbpJvktbiIt8k nAEX9DWJWHbYVemeYneguYDpx8VSksdAwLrIQG8mumCLzb0DDTJgn8LG8+6KzqS3 Xi6y8OL0nlb3Bf+QmMs3JjeJfoCH3FFxiQMcMkjCoOogJuuScCSldfT1I36K0Url 20BzRhRUOoMMZCYd0CRFMc/NoKU= Date: Wed, 15 Nov 2017 08:14:57 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0bf78120b5b_60da3febd36e4f344254d7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 08:15:00 -0000 ----==_mimepart_5a0bf78120b5b_60da3febd36e4f344254d7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit yoavweiss commented on this pull request. > @@ -204,20 +204,21 @@ Given the following inputs: 4. Let `key` be the return value of {{key}} with `URL` and `ETag` as inputs. 5. Let `h1` be the return value of {{hash}} with `key` and `N` as inputs. 6. Let `fingerprint` be the return value of {{fingerprint}} with `key`, `N` and `f` as inputs. -7. Let `h2` be the return value of {{hash}} with `fingerprint` and `N` as inputs, XORed with `h1`. -8. Let `h` be either `h1` or `h2`, picked in random. -9. Let `position_start` be 40 + `h` * `f`. -10. Let `position_end` be `position_start` + `f` \* `b`. -11. While `position_start` < `position_end`: +7. Let `fingerprint-string` be the value of `fingerprint` in base 10, expressed as a string. It defines a way to convert fingerprint into a string, so that we can apply {{hash}} on it -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#discussion_r151057154 ----==_mimepart_5a0bf78120b5b_60da3febd36e4f344254d7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss commented on this pull request.

In draft-ietf-httpbis-cache-digest.md:

> @@ -204,20 +204,21 @@ Given the following inputs:
 4. Let `key` be the return value of {{key}} with `URL` and `ETag` as inputs.
 5. Let `h1` be the return value of {{hash}} with `key` and `N` as inputs.
 6. Let `fingerprint` be the return value of {{fingerprint}} with `key`, `N` and `f` as inputs.
-7. Let `h2` be the return value of {{hash}} with `fingerprint` and `N` as inputs, XORed with `h1`.
-8. Let `h` be either `h1` or `h2`, picked in random.
-9. Let `position_start` be 40 + `h` * `f`.
-10. Let `position_end` be `position_start` + `f` \* `b`.
-11. While `position_start` < `position_end`:
+7. Let `fingerprint-string` be the value of `fingerprint` in base 10, expressed as a string.

It defines a way to convert fingerprint into a string, so that we can apply {{hash}} on it

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a0bf78120b5b_60da3febd36e4f344254d7-- From nobody Wed Nov 15 02:52:12 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=mLmVp2pxyt5Llvsl3WuKkjwZ6GM=; b=YH9v8DzFMyJJiQiJ YyUWBLRTyhkFGTSCHm2VxaXh/pbmmX9mTpvNiuFMdm5yXy3CSNbb/0FDpyjZ7WzK 6oZ9UgGnXVnQeuioPxNrbyHDp68+QlXtjX+iwvI83XqRXshzrnaGxSNkeQhG1cnx JOSqWeaJsuGJ2IB0+guIGLFw5Zo= Date: Wed, 15 Nov 2017 10:52:03 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0c1c53180fd_22263fc1d345ef285664a6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 10:52:06 -0000 ----==_mimepart_5a0c1c53180fd_22263fc1d345ef285664a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I've got a incomplete initial reference implementation at https://github.com/yoavweiss/cache-digests-cuckoo It doesn't yet include removal and querying (that's what I'll be adding next), but I did run it on a list of ~3250 URL (which I got out of my main profile chrome://cache/) and it seems to be creating reasonable sized digests. One more advantage, the digests seem to be highly compressible when sparse. Results so far: Digest with 1021 entries (so room for ~4K URLs): 5621 in-memory, 5233 gzipped (when filled with 3250 URLs). Digest with 2503 entries (so room for ~10K URLs): 13772 in-memory, 6879 gzipped (same 3250 URLs). Digest with 7919 entries (so room for ~31K URLs): 43560 in-memory, 9984 gzipped (same 3250 URLs). In practice, I think ~1000 entries is most probably enough, but it's good to know we can increase the digest size (to avoid having to recreate it), without significant over-the-wire penalty. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#issuecomment-344556687 ----==_mimepart_5a0c1c53180fd_22263fc1d345ef285664a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I've got a incomplete initial reference implementation at https://github.com/yoavweis= s/cache-digests-cuckoo

It doesn't yet include removal and querying (that's what I'll be adding = next), but I did run it on a list of ~3250 URL (which I got out of my main = profile chrome://cache/) and it seems to be creating reasonable sized diges= ts. One more advantage, the digests seem to be highly compressible when spa= rse.

Results so far:
Digest with 1021 entries (so room for ~4K URLs): 5621 in-memory, 5233 gzipp= ed (when filled with 3250 URLs).
Digest with 2503 entries (so room for ~10K URLs): 13772 in-memory, 6879 gzi= pped (same 3250 URLs).
Digest with 7919 entries (so room for ~31K URLs): 43560 in-memory, 9984 gzi= pped (same 3250 URLs).

In practice, I think ~1000 entries is most probably enough, but it's goo= d to know we can increase the digest size (to avoid having to recreate it),= without significant over-the-wire penalty.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.

= ----==_mimepart_5a0c1c53180fd_22263fc1d345ef285664a6-- From nobody Wed Nov 15 03:07:12 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.401 X-Spam-Level: X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=oYY9BGbEIJnOkIyPFo6dX9EaprA=; b=GHhoVbKCaL5fb48t JCMC9ihamgPcXV5xhsDFBPnvKXem19UV0URhYaNElxQrQrFgvcvR3JYtmnR0ZDgx qRnQDqnmD7HtLaL9oCSqg7vARiKq+TUdS5vZKpgl2s+SUy32hV33vFeZGst2fXNF 0oZUxjaxB1iPPtDz6bOqi9QFJQM= Date: Wed, 15 Nov 2017 11:06:29 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0c1fb5185ff_45573f9e2a726f343677f5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 11:07:11 -0000 ----==_mimepart_5a0c1fb5185ff_45573f9e2a726f343677f5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss pushed 2 commits. 7729e54 remove N from fingerprint c4167e6 Fix querying -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/413/files/c90f9b4bc014efde6c843de8f9768dfb50d4d21d..c4167e6ff7c26d44572587322ed028a1e159b4bf ----==_mimepart_5a0c1fb5185ff_45573f9e2a726f343677f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss pushed 2 commits.

7729e54 remove N from fingerprint
c4167e6 Fix querying

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a0c1fb5185ff_45573f9e2a726f343677f5-- From nobody Thu Nov 16 01:28:43 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=EEFe9woEd+UEqmLQkXHMUjl4ybs=; b=W++hNfZkDg0+uG2c xuZdNhd1kFZqBnhcbRTo63DgGM8SOJqsu+NVpZ6P+or1H0YzB8vDJnpCqQzeg5Rf lduPuu9f39DqXZiACJGdA1o8Shuffe+wQFwbgOpAxBiUu1Cb7i7Q4aPvmSXH/AzN mVx3gjYHN60vvJP9NlfaxoVm0dw= Date: Thu, 16 Nov 2017 09:28:40 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0d5a4796e0f_72803fb4d42f6f342036a2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 09:28:42 -0000 ----==_mimepart_5a0d5a4796e0f_72803fb4d42f6f342036a2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss pushed 1 commit. 88859e7 Fixed allocation issues and fixed style -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/413/files/c4167e6ff7c26d44572587322ed028a1e159b4bf..88859e7881a707005537f6a75e2b4fd7ae6ddeca ----==_mimepart_5a0d5a4796e0f_72803fb4d42f6f342036a2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss pushed 1 commit.

88859e7 Fixed allocation issues and fixed style

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a0d5a4796e0f_72803fb4d42f6f342036a2-- From nobody Thu Nov 16 07:04:00 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ooyevLOZIGBHgimBTDb2E5LBlN8=; b=RHGyygyM8p2Yml+/ XNHLBqgPSL3DBpNUA2Gwp3iw4XEmpRfhclc4rD+68GIcaswIz8QZt+fSufhmHkRu MsRYImlu3s3PGZEmOgs3oiN2pglgY0Rt3Nu8/SNZxnI+PTE3+PRimgjeGAA5PY3R RUmKZAG4X95Z3iVTc5IYYs0OBCs= Date: Thu, 16 Nov 2017 15:03:52 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0da8d752ed0_211ab3fd5099ecf28265757"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 15:03:58 -0000 ----==_mimepart_5a0da8d752ed0_211ab3fd5099ecf28265757 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit OK, I now have a complete reference implementation and it seems to be working fine. It also exposed an issue with the initial algorithm, forcing table allocation to accommodate a power of 2 number of entries. Latest results for 3250 URLs taken from my cache: |Number of entries | Full capacity |Digest memory size | Digest gzipped size| |-------------------|----------------------|--------------------|--------------------| |1021 | 4084 |5637 | 5248 | |2019 | 8076 | 11269 | 7031 | |4027 | 16108|22533 | 8663 | One note: the 1021 entries table had 35 collisions, so it seems like it's insufficient for that number of URLs, unless we're willing to absorb extra pushes for ~1% of the resources. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#issuecomment-344949750 ----==_mimepart_5a0da8d752ed0_211ab3fd5099ecf28265757 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

OK, I now have a complete reference implementation and it seems to be wo= rking fine. It also exposed an issue with the initial algorithm, forcing ta= ble allocation to accommodate a power of 2 number of entries.

Latest results for 3250 URLs taken from my cache:

Number of entries	Full capacity	Digest memory size	Digest gzipped size
1021	4084	5637	5248
2019	8076	11269	7031
4027	16108	22533	8663

One note: the 1021 entries table had 35 collisions, so it seems like it'= s insufficient for that number of URLs, unless we're willing to absorb extr= a pushes for ~1% of the resources.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.

= ----==_mimepart_5a0da8d752ed0_211ab3fd5099ecf28265757-- From nobody Thu Nov 16 14:38:09 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=mFzmyDRvjPFOd1oMJV+v13ip+ts=; b=Mc0KWwX6wvL4zDgy vqRdBIWAw1c2oyhWMeOdhIhLEU+T1CdMTY89PzUVIxB1NesiDbbWgNP4zyLXXKXk x5R/h5m7ij0YamEnuhU6qQWDcMLbdMLD46ijMAKHujm7bx9g/P2H16zNqSJ0lSbf bMZ/0x8bG6HZ+l1sVEvb+26UUls= Date: Thu, 16 Nov 2017 22:38:04 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0e134c956b9_5a903faa2462cf3871740"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 22:38:08 -0000 ----==_mimepart_5a0e134c956b9_5a903faa2462cf3871740 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss Interesting! It's good to know that we have numbers now. What is the value of P (the false positive ratio) that you used? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#issuecomment-345085721 ----==_mimepart_5a0e134c956b9_5a903faa2462cf3871740 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@yoavweiss Interesting! It's good to know that we have numbers now.

What is the value of P (the false positive ratio) that you used?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a0e134c956b9_5a903faa2462cf3871740-- From nobody Thu Nov 16 15:54:18 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=+y5gjV9UQ0MH5vVO6ydH19ESA9E=; b=IEtyohYxYhmfoFUm YGdrtPzXHZY23QnKz0MdpMVAuusP19tsc2lwpoENkSwzLpElCA65dC8CduuT7f66 MRbCn9cMNpAcTuAUqB5c7vAieWeynK4i2hgl94lyqjO5ciKKfQap57KdPCl/EAA6 CILtJgUvoX43jHN86UUZGPQDlPk= Date: Thu, 16 Nov 2017 23:54:13 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [Cache Digests] Switch digest to cuckoo filters, to enable O(1) removal (#413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a0e2525688f6_20f13fa93e820f381179a5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 23:54:16 -0000 ----==_mimepart_5a0e2525688f6_20f13fa93e820f381179a5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit P=8 (so 1/256 false positive) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/413#issuecomment-345101411 ----==_mimepart_5a0e2525688f6_20f13fa93e820f381179a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

P=8 (so 1/256 false positive)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a0e2525688f6_20f13fa93e820f381179a5-- From nobody Thu Nov 16 16:20:06 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=LTYWogHC1tpP1ZtlbhcHtfiZMRk=; b=DrkTDbynSnuc01yZ kLkIC4qifqBAwnLZidpagQNxrFSmzRb9ratAFOyPG1SFB5daDooH8b0RnbJMcgyC 4yEtoPMAzT6L9xLrsrFXTmP0bVPZcZrIotRWRq5lVDCOqCFiSyOpRpCUeMJE8e6u x44j5W7AxcY7kIMDaMuV5j4+2oQ= Date: Fri, 17 Nov 2017 00:18:30 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: -

- HEAD /resource HTTP/1.1 - Range: bytes=0- +

+HEAD /resource HTTP/1.1 +Host: example.com +Range: bytes=0- + Do you think the blank lines at the end of the examples are really necessary? (Presume the intent is to show the terminating \n\n?) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/421#pullrequestreview-78994038 ----==_mimepart_5a18dd555aeab_3d5c3fd1c820af384113b0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@craigpratt commented on this pull request.

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -238,16 +239,18 @@
       representation length) may respond with a 206 status code (Partial Content) with a Content-Range
       header indicating the currently satisfiable byte range. For example:
       </t>
-<figure><artwork type="example">
-      HEAD /resource HTTP/1.1
-      Range: bytes=0-
+<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="    ">
+HEAD /resource HTTP/1.1
+Host: example.com
+Range: bytes=0-
+

Do you think the blank lines at the end of the examples are really necessary? (Presume the intent is to show the terminating \n\n?)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a18dd555aeab_3d5c3fd1c820af384113b0-- From nobody Fri Nov 24 20:32:10 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=cr87ECkibjIPrNz+Wi84O7Gp5MM=; b=kiC+yT6yD7ubPgOA J4OVevxUaFEE1fzxQltbEE5HpAsk3lKzgJR6NGkHR2ZqioY+udMOP918dRHsGMrd Gn4YAiV+Lc2rFXVDhpmbcuhnPGXkjtrAWBxavd29+yqqNiNLS4/k7q9D8QWFzfqu j0pKRnS0mqODe8QDCE+cqYexL3I= Date: Sat, 25 Nov 2017 04:32:06 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] tune use of ABNF (closes #415) (#422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a18f245c3362_4c183fafe23cef342590c4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 04:32:08 -0000 ----==_mimepart_5a18f245c3362_4c183fafe23cef342590c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #422. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/422#event-1357719079 ----==_mimepart_5a18f245c3362_4c183fafe23cef342590c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #422.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a18f245c3362_4c183fafe23cef342590c4-- From nobody Fri Nov 24 20:32:18 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Hkdcb++9R01S0Q8z+fA1yGOASPs=; b=rdKrIjkiXHbASWsq 7FVrEGJIA8TcDTI9pDS+o06Iw1bnxsi0phiNF7ZMMwL3G3b6UGD3BHU8jk9x3JvU yqO5mJdBL7TINc4Oh5p+Bj42CgIvfG6SWeOzFgMc4f1uNGu2Ty0KDnNpDkQfC8Br Mkdh7gvx9srhZKvW4oTmwBQUaIk= Date: Sat, 25 Nov 2017 04:32:07 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] ABNF reference (#415) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a18f246a0ce0_5c883ff27ea52f34108711"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 04:32:10 -0000 ----==_mimepart_5a18f246a0ce0_5c883ff27ea52f34108711 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #415 via da5f2105a7cec502078f4a089c2979535dc50e9c. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/415#event-1357719088 ----==_mimepart_5a18f246a0ce0_5c883ff27ea52f34108711 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #415 via da5f210.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a18f246a0ce0_5c883ff27ea52f34108711-- From nobody Fri Nov 24 20:32:58 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=+wvOlDp0qVEZ5MaNRQg92/i+EhE=; b=cFJOFn7SRdP/nNSA 3Benp9g2FBCvFDV62XI6/zqSGGzxWa9i8r1Yzr6hMoycG7Awlw/N37CwpuUsQoIa KsNhHSWyLzMUZ0EmTAGyHNDQUlJLiJ/IEU2w485iA2z3iJKtQ1GuvUTvjgLVuLKV IdIiW7FvjbnSTM0r0wjVDcz/jDw= Date: Sat, 25 Nov 2017 04:32:54 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] remove unneeded abbreviated title (#424) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a18f2761347a_4c153fafe23cef3453449f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 04:32:56 -0000 ----==_mimepart_5a18f2761347a_4c153fafe23cef3453449f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #424. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/424#event-1357719297 ----==_mimepart_5a18f2761347a_4c153fafe23cef3453449f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #424.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a18f2761347a_4c153fafe23cef3453449f-- From nobody Sat Nov 25 03:27:10 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=/nMpR51CLrDuvolc2pWhiYneWck=; b=W9ys2vLX08Q1lPKj mzgV5q+QFQNpIF02H2n7e3OEL2dGNSDR+VFY1dJzriy0gJOuXlFt1C4VUHIFgTG+ DoVhvOjRFbgpjKlgAYfeXEglO92d/i4OO0B57daT+qxg7cI2LJiTw+kM5x1Fj82Q SWM1SqPW9DzOppx1qJZtpRWZXQg= Date: Sat, 25 Nov 2017 11:27:05 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Tune HTTP examples (#421) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a19538978fd7_295e3fc19da54f306358ae"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 11:27:08 -0000 ----==_mimepart_5a19538978fd7_295e3fc19da54f306358ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit reschke commented on this pull request. > @@ -238,16 +239,18 @@ representation length) may respond with a 206 status code (Partial Content) with a Content-Range header indicating the currently satisfiable byte range. For example: -

- HEAD /resource HTTP/1.1 - Range: bytes=0- +

+HEAD /resource HTTP/1.1 +Host: example.com +Range: bytes=0- + We do it in the base specs as well... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/421#discussion_r153044037 ----==_mimepart_5a19538978fd7_295e3fc19da54f306358ae Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@reschke commented on this pull request.

In draft-ietf-httpbis-rand-access-live.xml:

> @@ -238,16 +239,18 @@
       representation length) may respond with a 206 status code (Partial Content) with a Content-Range
       header indicating the currently satisfiable byte range. For example:
       </t>
-<figure><artwork type="example">
-      HEAD /resource HTTP/1.1
-      Range: bytes=0-
+<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="    ">
+HEAD /resource HTTP/1.1
+Host: example.com
+Range: bytes=0-
+

We do it in the base specs as well...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a19538978fd7_295e3fc19da54f306358ae-- From nobody Sun Nov 26 07:41:19 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=/N3YjRn0Bi3iuGU2fyWEatUQMCs=; b=jk+rTgcYMUKD6q5j xnypjssqKQKr+0cXzcpd2Ms2U92pkZ0IBp9EXX0Fn5zeDvEo23x/NlmscDs1MBrf iQlWUn5Xyg0G0JTpWAAhW6s8D9ZGmz53f4jxE+RAVqlHUYHtKP/R8wXFtoxy0Pq3 aaHTgYPdYEXrr7n/FxygGJ1hmQg= Date: Sun, 26 Nov 2017 15:41:15 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] cite rfc 7233 early, and make references more specific (#425) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1ae09b18b46_21c83f96c872cf38546525"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 15:41:18 -0000 ----==_mimepart_5a1ae09b18b46_21c83f96c872cf38546525 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/425 -- Commit Summary -- * cite rfc 7233 early, and make references more specific -- File Changes -- M draft-ietf-httpbis-rand-access-live.xml (11) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/425.patch https://github.com/httpwg/http-extensions/pull/425.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/425 ----==_mimepart_5a1ae09b18b46_21c83f96c872cf38546525 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

You can view, comment on, or merge this pull request online at:

https://github.com/httpwg/http-extensions/pull/425

Commit Summary

cite rfc 7233 early, and make references more specific

File Changes

M draft-ietf-httpbis-rand-access-live.xml (11)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1ae09b18b46_21c83f96c872cf38546525-- From nobody Sun Nov 26 07:46:30 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=spllPoXo9WkFp5gbxOpvCkQQvVA=; b=Ga++GVFkFY8vDrqt WfftKwz+kjvMtNU7tw5/gofVMJNzp8GPY/LIqApJvvxCrzFzy1ZxTztqjp8MVfZV IRoG8q4qaYs/JnfXuFRsXGOTWoqkQgq6BGxdmUxo2JCjhqZDaItrsyIzS7e5YZXj wyceffo4I5sfZ0Dr/KRTB4xiGys= Date: Sun, 26 Nov 2017 15:45:53 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] add missing paragraph breaks (#426) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1ae1b0dafe2_3e7d3f7e36f06f382248cf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 15:46:28 -0000 ----==_mimepart_5a1ae1b0dafe2_3e7d3f7e36f06f382248cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/426 -- Commit Summary -- * add missing paragraph breaks -- File Changes -- M draft-ietf-httpbis-rand-access-live.xml (6) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/426.patch https://github.com/httpwg/http-extensions/pull/426.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/426 ----==_mimepart_5a1ae1b0dafe2_3e7d3f7e36f06f382248cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

You can view, comment on, or merge this pull request online at:

https://github.com/httpwg/http-extensions/pull/426

Commit Summary

add missing paragraph breaks

File Changes

M draft-ietf-httpbis-rand-access-live.xml (6)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1ae1b0dafe2_3e7d3f7e36f06f382248cf-- From nobody Sun Nov 26 08:10:49 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.396 X-Spam-Level: X-Spam-Status: No, score=-3.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=MA6CesvE7sx/ijYTk7g3bAZFAMM=; b=c2mCBKxh0CCk/SId Cxy8O/MJzMltsEk8GigS5s6STwhFa4a7XDzUuXZWconjLW5pn4SC2pRlWqWKnmEG U37WyQWbhlWKvg7n0VpFFWxayr7UAnqxmWYIR1E8zhdHAbqiTNkFi0afOrgTtx9B yx8LjVS1+cTHi8ux6BhAOZJnAKM= Date: Sun, 26 Nov 2017 16:10:46 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Expand acronyms and cite HLS and DASH (#427) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1ae785d590d_22183fa3cd3d8f286234da"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 16:10:48 -0000 ----==_mimepart_5a1ae785d590d_22183fa3cd3d8f286234da Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/427 -- Commit Summary -- * Expand acronyms and cite HLS and DASH -- File Changes -- M draft-ietf-httpbis-rand-access-live.xml (13) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/427.patch https://github.com/httpwg/http-extensions/pull/427.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/427 ----==_mimepart_5a1ae785d590d_22183fa3cd3d8f286234da Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

You can view, comment on, or merge this pull request online at:

https://github.com/httpwg/http-extensions/pull/427

Commit Summary

Expand acronyms and cite HLS and DASH

File Changes

M draft-ietf-httpbis-rand-access-live.xml (13)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1ae785d590d_22183fa3cd3d8f286234da-- From nobody Sun Nov 26 14:49:59 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.396 X-Spam-Level: X-Spam-Status: No, score=-3.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=xfeYqBKXWERH+K5Ps5oO5eV6Ces=; b=SX8j6p10bye8+o4d FjKx6OfhvPthYrWwpMJaDf1uBGVtqjHpey2Al0ZZCvP2d8qn68n/t5roLghQOztz zm64CKSBt0AynygPSOLuAjYsDWUefDkLOHnTjzGLtA1tWrt0/RE9oB897QKBlQAn Hq0J4xat3SYOdDmQRg8MS3+Bxp0= Date: Sun, 26 Nov 2017 22:49:55 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Be more definite about early data (#428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1b4512e8d05_68ac3f8a9b074f302913b7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 22:49:58 -0000 ----==_mimepart_5a1b4512e8d05_68ac3f8a9b074f302913b7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This makes mitigation mandatory. Either receive a signal that early data is safe for the given resource, or apply the mitigations. That's consistent with the other text. You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/428 -- Commit Summary -- * Be more definite about early data -- File Changes -- M draft-ietf-httpbis-replay.md (7) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/428.patch https://github.com/httpwg/http-extensions/pull/428.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/428 ----==_mimepart_5a1b4512e8d05_68ac3f8a9b074f302913b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This makes mitigation mandatory. Either receive a signal that early data is safe for the given resource, or apply the mitigations. That's consistent with the other text.

You can view, comment on, or merge this pull request online at:

https://github.com/httpwg/http-extensions/pull/428

Commit Summary

Be more definite about early data

File Changes

M draft-ietf-httpbis-replay.md (7)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1b4512e8d05_68ac3f8a9b074f302913b7-- From nobody Sun Nov 26 14:51:32 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=vkWCb1Hqi5xANXrd84pPS2SgPZc=; b=qt44t3LPrjoa4n5i kOMJ+flQT1FFbMOvctR+iCLV/r+mYBo1DnuAFXC4aN1NWXyrl+clweEn6e4f2sv6 ha7ejlskgAHbu+FuLslkxOB2Iv1T04Uddhoe5NhtSFA/SWkNMBC2NeTZjNJjtL7f gl3QXMIgJBqH9u14Yqo6+Lcl8Qg= Date: Sun, 26 Nov 2017 22:51:27 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Clarify intermediary TLS role better (#429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1b456ea65b0_a153fda32eeef341252f8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 22:51:30 -0000 ----==_mimepart_5a1b456ea65b0_a153fda32eeef341252f8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think that these are the main places where we weren't clear enough about the relevant TLS role. You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/429 -- Commit Summary -- * Clarify intermediary TLS role better -- File Changes -- M draft-ietf-httpbis-replay.md (9) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/429.patch https://github.com/httpwg/http-extensions/pull/429.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/429 ----==_mimepart_5a1b456ea65b0_a153fda32eeef341252f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I think that these are the main places where we weren't clear enough about the relevant TLS role.

You can view, comment on, or merge this pull request online at:

https://github.com/httpwg/http-extensions/pull/429

Commit Summary

Clarify intermediary TLS role better

File Changes

M draft-ietf-httpbis-replay.md (9)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1b456ea65b0_a153fda32eeef341252f8-- From nobody Sun Nov 26 14:58:24 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=vED7yWwuen/iQwicRx6x5TBFytQ=; b=FZW/2NrqdVKiFx/h lkH336dKNmZuL+HKv6SUJQBQ5g6nUBCzxj6EvpHsoBy8aZ0Fe4BtENBV2MRb7VMg FbmYjlg90DG2a4uxmlQhjx34CcrZolB6ehs9Q01cNhGkcjxlLfQqrWPrOoN2IchG NF9YtJx+CWZapjXUaspCXyNRnwo= Date: Sun, 26 Nov 2017 22:58:20 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] New abstract (#430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1b470c55654_2b5a3fe78f986f283094c7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 22:58:23 -0000 ----==_mimepart_5a1b470c55654_2b5a3fe78f986f283094c7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit John Mattsson pointed out that we didn't really discuss the risks of use of early data. That's fair, but we don't need to. This rewrites the abstract. You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/430 -- Commit Summary -- * New abstract -- File Changes -- M draft-ietf-httpbis-replay.md (8) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/430.patch https://github.com/httpwg/http-extensions/pull/430.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/430 ----==_mimepart_5a1b470c55654_2b5a3fe78f986f283094c7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

John Mattsson pointed out that we didn't really discuss the risks of use of early data. That's fair, but we don't need to. This rewrites the abstract.

You can view, comment on, or merge this pull request online at:

https://github.com/httpwg/http-extensions/pull/430

Commit Summary

New abstract

File Changes

M draft-ietf-httpbis-replay.md (8)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1b470c55654_2b5a3fe78f986f283094c7-- From nobody Sun Nov 26 15:06:43 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=LuEQpLSifjqUGVYiNohvzbpTEYg=; b=lGvB+SZPLIEte0MM 0Z1r7lIfacryqIGjmR/3YvYr8vU8y3mQ85HjvK35acqW0jbTs2cTQwsUFxwbjR4K YL2fsS0d6PiBSRSEGoilYSF+nuXuSTbawUcjWyihKCwoh+PqatwvhUmmO7MKxDH1 uAR1QTz8ifX6x+005i+b8FflgTQ= Date: Sun, 26 Nov 2017 23:06:21 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] missing a word (#431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1b48ed4a9f_2fc843fed9f31cf282279f2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 23:06:42 -0000 ----==_mimepart_5a1b48ed4a9f_2fc843fed9f31cf282279f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Enjoy. You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/431 -- Commit Summary -- * application data -- File Changes -- M draft-ietf-httpbis-replay.md (8) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/431.patch https://github.com/httpwg/http-extensions/pull/431.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/431 ----==_mimepart_5a1b48ed4a9f_2fc843fed9f31cf282279f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Enjoy.

You can view, comment on, or merge this pull request online at:

https://github.com/httpwg/http-extensions/pull/431

Commit Summary

application data

File Changes

M draft-ietf-httpbis-replay.md (8)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1b48ed4a9f_2fc843fed9f31cf282279f2-- From nobody Mon Nov 27 01:52:22 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=mH8JV9HcJABZtXgISOwwlmFPgiM=; b=I7QyZ8MRr42itDvr 9tl8oBtSYuRqa8E/eD58vLNw1x1QQkKz60IxBsak8OdOrcVqgc70R3ka/cJ4p9GA tUGV1SUkyi4+awUeAtMnw4Hj76Sfdmcx/Q6I0ZhGoca0QTK6ZDdR0ipZU+g0VbiZ ncwwM8ctbpedbWitJl6v3r2fG68= Date: Mon, 27 Nov 2017 09:52:18 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Be more definite about early data (#428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1be051a7a10_59933fcc1f02af284573d9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 09:52:20 -0000 ----==_mimepart_5a1be051a7a10_59933fcc1f02af284573d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit LGTM -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/428#issuecomment-347131238 ----==_mimepart_5a1be051a7a10_59933fcc1f02af284573d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

LGTM

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1be051a7a10_59933fcc1f02af284573d9-- From nobody Mon Nov 27 01:54:09 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=5ZmcKfdlUQPyc8WwnPGxI3JsDCM=; b=a6DNGXL866k+4H1O ceMyWFiG1ADZ/wNQrwnhFh2dbaPEavsIVagz9vOgpBEfXZJ8MmRAhMrdIviIKpwU Xc/McjWSJDOk/PC3kgjR+Gz3ITd0EMcphYoCIRZyAXeAL/4fq6Q/fyKZzNqLUKFZ FfOX/R46zesqVhrRTuIaoXvPp0A= Date: Mon, 27 Nov 2017 09:53:37 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Clarify intermediary TLS role better (#429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1be0a0d0b43_48e63fd3766a0f34296490"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 09:54:06 -0000 ----==_mimepart_5a1be0a0d0b43_48e63fd3766a0f34296490 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit LGTM -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/429#issuecomment-347131575 ----==_mimepart_5a1be0a0d0b43_48e63fd3766a0f34296490 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

LGTM

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1be0a0d0b43_48e63fd3766a0f34296490-- From nobody Mon Nov 27 01:55:54 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=l9db5jwKR/+DWu+X4oJPXqohDfw=; b=lOb1oQLXjiOAb6ES 9cIIYSSuV6me5f3KVpVHyWwF4wjuw6/5QW2CWq69A1VAQf0XXMdOBMQT6uqtRM/8 MaNenpbVzNjWTM2PyPHJjlpk3jb37Ux6ZgMBKxt3BNJc49teEJ7/QE1fCELlXEt7 xjhjz+aFJGBwqiJq1GLHC8/RCgw= Date: Mon, 27 Nov 2017 09:55:29 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] New abstract (#430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1be110ee52d_399f3fde49ee0f2c49248b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 09:55:53 -0000 ----==_mimepart_5a1be110ee52d_399f3fde49ee0f2c49248b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Just one fix : s/mechanisms that allows/mechanisms that allow/ Nice overall. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/430#issuecomment-347132072 ----==_mimepart_5a1be110ee52d_399f3fde49ee0f2c49248b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Just one fix : s/mechanisms that allows/mechanisms that allow/
Nice overall.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1be110ee52d_399f3fde49ee0f2c49248b-- From nobody Mon Nov 27 02:27:46 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=XoUe2xHnjEo4YMjzJasLtoA0HlU=; b=LszChcwRifhCLW8I oAwzAbqS2c00ngAUnRHLSIBo9A5YUJROuLBU6QQRkxi7k5550cMj7Cgw0q/2CADE A+fJqtV0tRTg/E1BCO3KNWRmKc0Jq+k1YCAdJWwqFnkA+BGqfZRrJrfobnPTe4qd RhYS08ZOSbB8/Fcp7gcUD9PsYKU= Date: Mon, 27 Nov 2017 10:27:43 +0000 (UTC) To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] New abstract (#430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1be89f389ec_8753f925b490f344581ba"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 10:27:46 -0000 ----==_mimepart_5a1be89f389ec_8753f925b490f344581ba Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 8c22103 Plural fix -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/430/files/88996b61c0683e33729081410b541f1e1305ebf8..8c22103787de0e16d66fbc446f7b6e2473710a08 ----==_mimepart_5a1be89f389ec_8753f925b490f344581ba Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

8c22103 Plural fix

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a1be89f389ec_8753f925b490f344581ba-- From nobody Mon Nov 27 07:21:51 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=kdnX0nt9MiHMTrBdxIC+2p2rmzs=; b=o2buRiQ77nLrJokr kq9pefGYf3rNoO3x77eNjnOG6q2XXdHFOYlYGN5tXhpOlLD+DSjvsF0F5mwJ5rOO Z80qPLkXUHXXaWlg6uAyDkvI23Md5hvbX+WxZscdM0klIDG+yx+xvLcDyInHoEUO 5Fw+8A5oIGv0gn5+Oye2gV5Vscg= Date: Mon, 27 Nov 2017 15:21:47 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Minor editorial fixes for Expect-CT (#432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1c2d8aecb74_12253fdead156f28221849"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 15:21:50 -0000 ----==_mimepart_5a1c2d8aecb74_12253fdead156f28221849 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit /cc @estark37 You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/432 -- Commit Summary -- * Fix typo by -> be * Fix indentation in list * Add missing 'to' -- File Changes -- M draft-ietf-httpbis-expect-ct.md (24) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/432.patch https://github.com/httpwg/http-extensions/pull/432.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/432 ----==_mimepart_5a1c2d8aecb74_12253fdead156f28221849 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

/cc @estark37

You can view, comment on, or merge this pull request online at:

https://github.com/httpwg/http-extensions/pull/432

Commit Summary

Fix typo by -> be
Fix indentation in list
Add missing 'to'

File Changes

M draft-ietf-httpbis-expect-ct.md (24)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a1c2d8aecb74_12253fdead156f28221849-- From nobody Mon Nov 27 08:52:39 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=e772BrYLoXVVbYVglvUo2d7wSZY=; b=oNmVYDq9HMB9tWDN qyyx+B/jfHddcSI1jW1fk90REeTuZ+ebBi+OlnRKVUCDR+oZYv6/qiFwOxql8agm EA0c3ypnbgd9Q6T4vZpLFbPAMq9SyMHTEyOjKvSrMlIG7AgoJAHHGnoV3NoCGAEZ boSl1wSWZpggCCEEVGpFeSBhEh0= Date: Mon, 27 Nov 2017 16:52:35 +0000 (UTC) To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Accept-CH-Lifetime privacy concerns (#372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a1c42d2e3ea3_36ba3fc1e37c6f342404f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list tracking: Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 16:52:38 -0000 ----==_mimepart_5a1c42d2e3ea3_36ba3fc1e37c6f342404f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks, Ilya! I re-read the spec with your changes and I also think it's a significant improvement, particularly when it comes to binding subresource hints to the opt-in origin, hindering cross-origin linking between 1p sites which don't use `Accept-CH`. My main outstanding worry is indeed the "hint delegation" issue you mentioned above: specifically, the fact that opting an origin into receiving hints still results in sending hints on subresources by default if the 3p also opts in, potentially giving it information about the referring page that it wouldn't currently receive. Similarly, such 3p origins hosting subresources used by an `Accept-CH`-enabled origin would start getting hints which disclose a few bits of information about the user and could be used for opportunistic linking across 1p visits to different `Accept-CH`-enabled origins. I like the idea of using Feature Policy to control this, but it's doubtful that developers would understand the privacy benefit of restricting subresource hints via FP, which means they wouldn't take action to prevent them from being sent. What do you think about flipping this around and only sending hints on 3p subresource requests if the origin is explicitly whitelisted via Feature Policy? This would be a direct signal from the developer that they want to trust the third-party, and might be more in line with the interests of both the first-party and the user. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/372#issuecomment-347245677 ----==_mimepart_5a1c42d2e3ea3_36ba3fc1e37c6f342404f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thanks, Ilya! I re-read the spec with your changes and I also think it's= a significant improvement, particularly when it comes to binding subresour= ce hints to the opt-in origin, hindering cross-origin linking between 1p si= tes which don't use Accept-CH.

My main outstanding worry is indeed the "hint delegation" issue you ment= ioned above: specifically, the fact that opting an origin into receiving hi= nts still results in sending hints on subresources by default if the 3p als= o opts in, potentially giving it information about the referring page that = it wouldn't currently receive. Similarly, such 3p origins hosting subresour= ces used by an Accept-CH-enabled origin would start getting hi= nts which disclose a few bits of information about the user and could be us= ed for opportunistic linking across 1p visits to different Accept-CH<= /code>-enabled origins.


I like the idea of using Feature Policy to control this, but it's doubtf=
ul that developers would understand the privacy benefit of restricting subr=
esource hints via FP, which means they wouldn't take action to prevent them=
 from being sent. What do you think about flipping this around and only sen=
ding hints on 3p subresource requests if the origin is explicitly whitelist=
ed via Feature Policy? This would be a direct signal from the developer tha=
t they want to trust the third-party, and might be more in line with the in=
terests of both the first-party and the user.

&mda=
sh;
You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, view it on GitHub, or <=
a href=3D"https://github.com/notifications/unsubscribe-auth/AORpyCTMQqgUqL7=
bv0tt0b8E1nfk3yDaks5s6ujSgaJpZM4Oc7TI">mute the thread.


  
  




=

----==_mimepart_5a1c42d2e3ea3_36ba3fc1e37c6f342404f--


From nobody Mon Nov 27 09:07:28 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level: 
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=CT4MWtaSeLu6F7QAGAZHlMoC7Ts=; b=NCX9yTPGAB4AzcBV w8JBdXNe7Y764tu59XEYO6w717vwWGZDHSlb2JqXeFZHwGoUysjVpAmMNcD2zuqr s8QCUECSD4ffZSFOVj/22QBaemwRG8ZH2k6TBXGwQ8TX1GFAOdy9YRv/f4PqRO/j ZgngeJu7bDZZkjjZ1VodbY/Xjhw=
Date: Mon, 27 Nov 2017 17:07:22 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] Accept-CH-Lifetime privacy concerns (#372)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1c464a38951_32b53fd8b94fcf28332252"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 27 Nov 2017 17:07:27 -0000

----==_mimepart_5a1c464a38951_32b53fd8b94fcf28332252
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

> What do you think about flipping this around and only sending hints on 3p subresource requests if the origin is explicitly whitelisted via Feature Policy? This would be a direct signal from the developer that they want to trust the third-party, and might be more in line with the interests of both the first-party and the user.

I'd be supportive of restricting third party access by default and providing a Feature Policy explicit opt-in to specific third-party domains that the origin trusts. 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/372#issuecomment-347251182
----==_mimepart_5a1c464a38951_32b53fd8b94fcf28332252
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable


What do you think about flipping this around and only sending hints on 3=
p subresource requests if the origin is explicitly whitelisted via Feature =
Policy? This would be a direct signal from the developer that they want to =
trust the third-party, and might be more in line with the interests of both=
 the first-party and the user.

I'd be supportive of restricting third party access by default and provi=
ding a Feature Policy explicit opt-in to specific third-party domains that =
the origin trusts.

&mda=
sh;
You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, view it on GitHub, or <=
a href=3D"https://github.com/notifications/unsubscribe-auth/AORpyAE3_F5_6OS=
6P2Gnj1O7_FCz2Dvfks5s6uxKgaJpZM4Oc7TI">mute the thread.


  
  




=

----==_mimepart_5a1c464a38951_32b53fd8b94fcf28332252--


From nobody Mon Nov 27 17:38:24 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.473
X-Spam-Level: 
X-Spam-Status: No, score=-0.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=cVpg7xV0IagMY/LRTFr4xZ+6Btk=; b=Djo1G/dTbzQUK3pS /2yeGOVvcyzDdeCjxfEm06I+K9mB4xXkXYlL5im61lQ7slKulv8/tepGtKHQMlsD cg1+QIUqZWGJTSLQEAH4d3zGiRVJX8F2mPefmzG8fZUAuArb/PkHN6ofFrvUprTc 2mHrk0rryWwwDvFMm6bnNcXEQqo=
Date: Tue, 28 Nov 2017 01:38:20 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] prune boilerplate (#346)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1cbe0c5a303_272833fc3ed63af3816472c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 01:38:23 -0000

----==_mimepart_5a1cbe0c5a303_272833fc3ed63af3816472c
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

OBE

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/346#issuecomment-347385613
----==_mimepart_5a1cbe0c5a303_272833fc3ed63af3816472c
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

OBE

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1cbe0c5a303_272833fc3ed63af3816472c--


From nobody Mon Nov 27 17:38:30 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=XqU8NSgwcgzSCMBUt9kCd6lfxZU=; b=odEcDFMTueCctyNR bN2aKLJzbqtFkN6GiqxzXgA6ktPWDcy/APSJdYI3sNmNrNbGeUdIdF9FhRngvgSE n3gOHRLGDIA4+wQg5RWHxpOm2bBQS7PsQSe/JrxjNgEDdh5VhFIF00TMU5knZWWY nWH6c6V2kYssl+wmEFYHilhy1+Y=
Date: Tue, 28 Nov 2017 01:38:21 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] prune boilerplate (#346)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1cbe0c908f9_6e843fa914f0ef2c2926da"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 01:38:24 -0000

----==_mimepart_5a1cbe0c908f9_6e843fa914f0ef2c2926da
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Closed #346.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/346#event-1360472130
----==_mimepart_5a1cbe0c908f9_6e843fa914f0ef2c2926da
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Closed #346.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1cbe0c908f9_6e843fa914f0ef2c2926da--


From nobody Mon Nov 27 18:01:49 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=R3OehQHB0pzruY1eJoYU9HQdRcY=; b=QOr+9geEEUi9IjB2 0YeQL+pTmxJYgYP/f878Q9L+KfUJySDIhaynFUoX+m/FniBhFsjni6cUcNZx+4/+ rQunYHZJZESazhetJlhYYFzd0YF+Jtlw/BzpX0+jrnd9N4ZZ6Q/B9sLQKMB/GAU/ Hx9Y8oOymNopLil6RGvlEZ4yxM0=
Date: Tue, 28 Nov 2017 02:01:37 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] Length limits on types (#433)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1cc380dcea4_2f8e3fed6e012f341826bb"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 02:01:48 -0000

----==_mimepart_5a1cc380dcea4_2f8e3fed6e012f341826bb
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

The current draft puts specific size limits on each type (e.g., lengths of strings, number of items in an array).

The rationale for including (generous) limits is that header authors often don't specify any limits, which puts implementations in an awkward position of deciding how much is "too much", leading to interoperability problems.

Ideally each header author would define their own limits, tighter limits where necessary, making these a catch-all. 

With that said, two questions:

1)  Should we have such limits?

2) If so, are the current limits correct? 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/433
----==_mimepart_5a1cc380dcea4_2f8e3fed6e012f341826bb
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

The current draft puts specific size limits on each type (e.g., lengths of strings, number of items in an array).
The rationale for including (generous) limits is that header authors often don't specify any limits, which puts implementations in an awkward position of deciding how much is "too much", leading to interoperability problems.
Ideally each header author would define their own limits, tighter limits where necessary, making these a catch-all.
With that said, two questions:


Should we have such limits?


If so, are the current limits correct?



—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1cc380dcea4_2f8e3fed6e012f341826bb--


From nobody Mon Nov 27 18:03:35 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=A0Cz9t4d9laEzYnGtQoUAvhsWeg=; b=tPGUCJfvr85GK7gL 3Zrl8HI0HMF0P6sB2glXnzLzPHVahgDc+Bxvual45ksVxmN1QaFK9I1Hwpg+nDcF tmWEh+Ta298GoDTFgBAjiISCcu01hi+I4ojNqObtqU2qlBZFOty0oT46z1wHtruX r2blBTaM0R56Y0Vxql9ss5jqHJY=
Date: Tue, 28 Nov 2017 02:03:31 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] Number(s) (#434)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1cc3f2d94dc_4aff3fdde3a34f348347c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 02:03:35 -0000

----==_mimepart_5a1cc3f2d94dc_4aff3fdde3a34f348347c
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

There's been a wide-ranging discussion of numbers on-list.

I *think* the current proposal is to define separate int and float type, with the former probably being 64 bits, and the latter probably being something like what's in the current draft. Both probably signed (?).

Future number types might be defined, but these should catch the majority of cases.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/434
----==_mimepart_5a1cc3f2d94dc_4aff3fdde3a34f348347c
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

There's been a wide-ranging discussion of numbers on-list.
I think the current proposal is to define separate int and float type, with the former probably being 64 bits, and the latter probably being something like what's in the current draft. Both probably signed (?).
Future number types might be defined, but these should catch the majority of cases.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1cc3f2d94dc_4aff3fdde3a34f348347c--


From nobody Mon Nov 27 18:12:44 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.473
X-Spam-Level: 
X-Spam-Status: No, score=-0.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=KmAhI2R5mhh81sVsbD3m3urnO88=; b=fh+aUyvLvnOS8QSV zjEH3ryKABeETet9QdbKIIX6wSwRORv9KgYrJeejh2GiaLEV2rhKia5YC6HmAqSL k0tvMxmZHa0MLVIJjRBgk6PUT9kVKaadoDzSa1qcptPnllKzthoY8+li5LHjrQXD Fz87xfCWxM+DBj/6OQTHBNcnyps=
Date: Tue, 28 Nov 2017 02:12:41 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] Ordering on parameters (#435)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1cc61988678_38fe3fcd071d0f381374d4"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 02:12:43 -0000

----==_mimepart_5a1cc61988678_38fe3fcd071d0f381374d4
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Should parameters on parameterised labels be ordered or unordered?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/435
----==_mimepart_5a1cc61988678_38fe3fcd071d0f381374d4
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Should parameters on parameterised labels be ordered or unordered?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1cc61988678_38fe3fcd071d0f381374d4--


From nobody Mon Nov 27 18:14:12 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ijHAX84Jbpo0z0eRbROUBDYlxtU=; b=UELABdT4WBTCy9Xy dBwZNbub3MKj6XGOOPN4lBM2bN0LRjdI2zcgXWt/5mlE60nNBN7+UPJ+RIUh+aZa VURIiShkDQXsZJyvwZIQ0rsqXxZtuvNh+ijZ2HPucGCRBkQTsYHY8tp+q68h88Z9 FvRXc7kqe+ewwuUo6LKnNhUDHBU=
Date: Tue, 28 Nov 2017 02:14:07 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] Trailing garbage (#436)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1cc66f727c2_4e8c3fdd43418f388766b"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 02:14:10 -0000

----==_mimepart_5a1cc66f727c2_4e8c3fdd43418f388766b
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

>From Alex R on list:

AFAICT, the top-level parsing algorithm in Section 3 is missing a
catch-all rule for trailing garbage. For example, right now, the
following malformed Item header field will pass all checks and return a
"valid" String to the caller. It should throw a "trailing garbage" error
instead.

 Foo: "valid" garbage!

When fixing that, tolerating trailing BWS may be a good idea.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/436
----==_mimepart_5a1cc66f727c2_4e8c3fdd43418f388766b
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

From Alex R on list:
AFAICT, the top-level parsing algorithm in Section 3 is missing a

catch-all rule for trailing garbage. For example, right now, the

following malformed Item header field will pass all checks and return a

"valid" String to the caller. It should throw a "trailing garbage" error

instead.
Foo: "valid" garbage!
When fixing that, tolerating trailing BWS may be a good idea.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1cc66f727c2_4e8c3fdd43418f388766b--


From nobody Mon Nov 27 18:14:56 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=2bSUj75HRekZlA6kA7KruRuyims=; b=OVW3VDBGp+VkbWtN 6SEMVtcVbO3q0FEJRp/6xXFv9yaAo2oq0cAi1he42HkmC5IPB+Nki95UM6lBkJ6R jPZKbYsw/M3KbmZaSXpnUJAJqQl+iRYKRZs6iRWOVMoszuIdsv/lnmYudiBw8NpR i+P+kB7GQLXAusRehQZ0unq2F1U=
Date: Tue, 28 Nov 2017 02:14:48 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] Combining headers and list length (#437)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1cc697ba95e_2213fc525800f282547b7"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 02:14:55 -0000

----==_mimepart_5a1cc697ba95e_2213fc525800f282547b7
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

>From Alex R on list:

I understand the desire to limit this specification to parsing a single
header field or equivalent, leaving the Pandora box of combining
same-name fields closed. However, this honorable approach complicates
placing interoperability limits on the number of list members: An
application that parses individual fields (and possibly never combines
the results!) may not hit the limit that an application combining raw
value strings before parsing would hit.

IMHO, we should explicitly say something (conservative) about this
problem so that header generators know how the limits may be applied.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/437
----==_mimepart_5a1cc697ba95e_2213fc525800f282547b7
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

From Alex R on list:
I understand the desire to limit this specification to parsing a single

header field or equivalent, leaving the Pandora box of combining

same-name fields closed. However, this honorable approach complicates

placing interoperability limits on the number of list members: An

application that parses individual fields (and possibly never combines

the results!) may not hit the limit that an application combining raw

value strings before parsing would hit.
IMHO, we should explicitly say something (conservative) about this

problem so that header generators know how the limits may be applied.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1cc697ba95e_2213fc525800f282547b7--


From nobody Tue Nov 28 09:27:26 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=CibKd0UaJMEU/jLUWxICdMtYgrw=; b=terokGiz5wfF6X8u bIA5RZs0UNzhylimkP5MA8nES1eH6unvi2uEEI/NCfnQlO22ktWAqVMTlq6Fs63h kWXR2upVcwqYpCFIQ2MN+TNWSVGhesJcOn5J3AvXd0BkGOMO0UNR4DrXn+hGHDBC Tc6uiC2vGtPYPsY6zOagGO4KFu8=
Date: Tue, 28 Nov 2017 17:27:23 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] ORIGIN-compliant clients and legacy servers (#438)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1d9c7b84a6c_2473fc017f16f282608df"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 17:27:26 -0000

----==_mimepart_5a1d9c7b84a6c_2473fc017f16f282608df
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The text in 2.4 says....

> Once an Origin Set has been initialized... [lots of stuff]
>
> Additionally, clients MAY avoid consulting DNS to establish the connectio=
n=E2=80=99s authority for new requests; however, those that do so face new =
risks, as explained in Section 4.

I think part of our issue with how Edge implemented coalescing without cons=
idering DNS arises from the fact that this "Additionally" isn't clearly tie=
d to being something that clients do "Once an Origin Set has been initializ=
ed" versus something that clients do in addition to the above behavior.

--=20
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/438=

----==_mimepart_5a1d9c7b84a6c_2473fc017f16f282608df
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The text in 2.4 says....

Once an Origin Set has been initialized... [lots of stuff]
Additionally, clients MAY avoid consulting DNS to establish the connecti=
on=E2=80=99s authority for new requests; however, those that do so face new=
 risks, as explained in Section 4.

I think part of our issue with how Edge implemented coalescing without c=
onsidering DNS arises from the fact that this "Additionally" isn't clearly =
tied to being something that clients do "Once an Origin Set has been initia=
lized" versus something that clients do in addition to the above behavior.<=
/p>

&mda=
sh;
You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, view it on GitHub, or mute the thread.


  
  




=

----==_mimepart_5a1d9c7b84a6c_2473fc017f16f282608df--


From nobody Tue Nov 28 10:21:51 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.018
X-Spam-Level: 
X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=X4Jrqc/XkI8R2G6OMgtfcmBQ0yc=; b=pY7iQa1HYLSjW9M0 ITMRSyNeCAFRCXz0fCGR0TgxxHXQQf1fV+3YSuwS07GhvX6+qTdpTsNZfqe6+Kc9 lrc4frJpcoD150t6dNe82K1R3b+0xVmGVE3Z4V24jiVMeUxeye7R5Mh1FCNJqksO NsLsZEYM1FrOUU2cqdoH/Rf7d6w=
Date: Tue, 28 Nov 2017 18:21:46 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] Explicitly scope to Origin Set (#439)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1da939e5220_31153f82103e6f3051981c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Nov 2017 18:21:49 -0000

----==_mimepart_5a1da939e5220_31153f82103e6f3051981c
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Fixes #438.
You can view, comment on, or merge this pull request online at:

  https://github.com/httpwg/http-extensions/pull/439

-- Commit Summary --

  * Explicitly scope to Origin Set

-- File Changes --

    M draft-ietf-httpbis-origin-frame.md (3)

-- Patch Links --

https://github.com/httpwg/http-extensions/pull/439.patch
https://github.com/httpwg/http-extensions/pull/439.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/439

----==_mimepart_5a1da939e5220_31153f82103e6f3051981c
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Fixes #438.



You can view, comment on, or merge this pull request online at:
  https://github.com/httpwg/http-extensions/pull/439

Commit Summary

  Explicitly scope to Origin Set


File Changes

  
    M
    draft-ietf-httpbis-origin-frame.md
    (3)
  


Patch Links:

  https://github.com/httpwg/http-extensions/pull/439.patch
  https://github.com/httpwg/http-extensions/pull/439.diff


—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  






----==_mimepart_5a1da939e5220_31153f82103e6f3051981c--


From nobody Tue Nov 28 16:32:16 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.402
X-Spam-Level: 
X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=PddAgk/TiAPbCtrn4m3pNWg5pRY=; b=XQLXmHs7omg7jDWn BUTNbIVcjifpJRwzzbN7FsQGoJFANtpmV1xhTi22f3zWBHzwucjU2f3odbQx5Ix8 OS0rhmssIxgwtillt9pv6SUxkSdczjT4BSwU7YWZcmqPlJ232Iz49l2tgimPusJb a2KHVoDt8MxoiSDqvjq/xBpvelA=
Date: Wed, 29 Nov 2017 00:32:14 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] Explicitly scope to Origin Set (#439)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1e000dd5dfb_5ae03fc1c2860f38585354"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Nov 2017 00:32:16 -0000

----==_mimepart_5a1e000dd5dfb_5ae03fc1c2860f38585354
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #439.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/439#event-1362574645
----==_mimepart_5a1e000dd5dfb_5ae03fc1c2860f38585354
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #439.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1e000dd5dfb_5ae03fc1c2860f38585354--


From nobody Tue Nov 28 16:32:25 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.402
X-Spam-Level: 
X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ZW6PA4YEjUdERuHLMuX4yYmWfL8=; b=uHh/QSLH498ueFql 2rDo3jvKbUN5wtGOXO34CGCfltgxutTV6z0gYcwegHV4Th3+Hh+0FGSH0geAlyMA SKX4rsOj00BnL6R+/6v+WfScImI4AYovw2eudQngM8BbunpQ3q39hFkIngc2lxiq hL+GiTLZiVCwzkWD1Aw0iq/bMic=
Date: Wed, 29 Nov 2017 00:32:14 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] ORIGIN-compliant clients and legacy servers (#438)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1e000e6213c_78d43fcd6f746f2c33482c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Nov 2017 00:32:17 -0000

----==_mimepart_5a1e000e6213c_78d43fcd6f746f2c33482c
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Closed #438 via #439.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/438#event-1362574651
----==_mimepart_5a1e000e6213c_78d43fcd6f746f2c33482c
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Closed #438 via #439.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1e000e6213c_78d43fcd6f746f2c33482c--


From nobody Wed Nov 29 01:18:37 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.396
X-Spam-Level: 
X-Spam-Status: No, score=-3.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=JZWEev/ND0pY3mBVUqZdTN6iXxY=; b=dKuoUItRwUdrkVbg qlKParbqYfwkvIWepGCd0YOnejI5ZGgx3rqNpG6QkVX9qORZQLr2/2Lj7L5skVls Hv1ZLyPc9gPxeHgSZv+UB4Aqdcx832y1gujat+hAjGFm5IoRcTaTC/Ze0gISvcEP wYH8NfbPru3i2N8+4wDkL22OtPg=
Date: Wed, 29 Nov 2017 09:18:32 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] Nits from Ben Kaduk's review (#440)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1e7b67e7f2e_1a1403fc3a1220f34160522"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Nov 2017 09:18:35 -0000

----==_mimepart_5a1e7b67e7f2e_1a1403fc3a1220f34160522
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Hopefully none of this collides with other PRs in flight.
You can view, comment on, or merge this pull request online at:

  https://github.com/httpwg/http-extensions/pull/440

-- Commit Summary --

  * Remove buffering text for 1.1
  * Don't make a special point about h2 preface
  * Reword to make distinction between mitigate and disable clear
  * Disabling early data is wise

-- File Changes --

    M draft-ietf-httpbis-replay.md (21)

-- Patch Links --

https://github.com/httpwg/http-extensions/pull/440.patch
https://github.com/httpwg/http-extensions/pull/440.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/440

----==_mimepart_5a1e7b67e7f2e_1a1403fc3a1220f34160522
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Hopefully none of this collides with other PRs in flight.



You can view, comment on, or merge this pull request online at:
  https://github.com/httpwg/http-extensions/pull/440

Commit Summary

  Remove buffering text for 1.1
  Don't make a special point about h2 preface
  Reword to make distinction between mitigate and disable clear
  Disabling early data is wise


File Changes

  
    M
    draft-ietf-httpbis-replay.md
    (21)
  


Patch Links:

  https://github.com/httpwg/http-extensions/pull/440.patch
  https://github.com/httpwg/http-extensions/pull/440.diff


—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  






----==_mimepart_5a1e7b67e7f2e_1a1403fc3a1220f34160522--


From nobody Wed Nov 29 01:23:24 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.402
X-Spam-Level: 
X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=CVOvgCnIr3HeRUO5kWcRdJ7T9CI=; b=tqwo9f6A3uxdYiGy cb2V+IWYH3+pYPbS87t5TkVCQzJzxcvfPv67NPW+p8EB1MPbeFDrR1DbqWo0IWQg xkVi1Eq95k1o/EQPFFkT+ZJWC+aTWQYfLQHDy7vr34SfZzbvU6Wjv7HYRo/1mP3s eMT9a6KEybXu1tnPLnhJV5WpJZY=
Date: Wed, 29 Nov 2017 09:23:19 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] Nits from Ben Kaduk's review (#440)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1e7c8774926_113e3f8c98dc0f28229337"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Nov 2017 09:23:23 -0000

----==_mimepart_5a1e7c8774926_113e3f8c98dc0f28229337
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I think it's fine with this. Adding a bit of pragmatism as you did in the last commit also reminds that the low cost of retrying is not worth a lot of trouble :-)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/440#issuecomment-347800678
----==_mimepart_5a1e7c8774926_113e3f8c98dc0f28229337
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I think it's fine with this. Adding a bit of pragmatism as you did in the last commit also reminds that the low cost of retrying is not worth a lot of trouble :-)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a1e7c8774926_113e3f8c98dc0f28229337--


From nobody Thu Nov 30 08:30:20 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.615
X-Spam-Level: 
X-Spam-Status: No, score=-0.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ROA0m+Jn30Tdj8jQ77BtOe+rOzU=; b=WdT6TYCe+J4XQiqE XU73q40n9KiqmpajZz21iUCrOnUDhag1K6tbUI4fEhThx2xdBi8M+tdJB+9BwAMW l8wakyT+LlBF6pZROwxZrcEcu+68RxrZE1RSIJXK9wO/tOuuTbo7rDg8RhyoGvzl qgHtwd1n5eq4X6JP+o4ls6iM9P4=
Date: Thu, 30 Nov 2017 16:30:16 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] RFC6265bis: Shouldn't the browser evict non-HttpOnly cookies first to avoid overwrite from JavaScript? (#441)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a203217a91be_62c83ff8c048cf301462bd"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 30 Nov 2017 16:30:18 -0000

----==_mimepart_5a203217a91be_62c83ff8c048cf301462bd
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

The current draft prevents cookies marked as 'Secure' from being overwritten or evicted from a non-secure origin (e.g., section 5.4), but it does nothing to prevent JavaScript from overwriting a cookie marked as 'HttpOnly' by evicting it from the cookie store. In current browsers it's therefore possible to tamper with the integrity of cookies marked with HttpOnly from JavaScript (e.g., XSS attack) despite the specification stating access should be restricted from non-HTTP APIs. 

In my view we should protect both confidentiality and integrity for HttpOnly cookies, which could be done by adding a condition that cookies without the HttpOnly attribute should be evicted first when set from a non-HTTP API (e.g., JavaScript).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/441
----==_mimepart_5a203217a91be_62c83ff8c048cf301462bd
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

The current draft prevents cookies marked as 'Secure' from being overwritten or evicted from a non-secure origin (e.g., section 5.4), but it does nothing to prevent JavaScript from overwriting a cookie marked as 'HttpOnly' by evicting it from the cookie store. In current browsers it's therefore possible to tamper with the integrity of cookies marked with HttpOnly from JavaScript (e.g., XSS attack) despite the specification stating access should be restricted from non-HTTP APIs.
In my view we should protect both confidentiality and integrity for HttpOnly cookies, which could be done by adding a condition that cookies without the HttpOnly attribute should be evicted first when set from a non-HTTP API (e.g., JavaScript).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a203217a91be_62c83ff8c048cf301462bd--


From nobody Thu Nov 30 16:08:07 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Vr+M83xivosmiju0+ZU580WQRCs=; b=UZi5UAnrZPUegQfJ gVPicY/UoGTmzwpBaBAycQvp4WSwTc0iNuOkIIuZeEiyhr9XBrcKX533+hA08PU+ YAHiW8yL2LZhcYiUr2e2p+UJeD9/32N3tVqFG893wy+R0qjhkfvxldjUjAR7PuEO 99MubI+KuJE6YFGzN6+7Vx8dCj8=
Date: Fri, 01 Dec 2017 00:08:02 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] Be more definite about early data (#428)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a209d6224726_67c43f809e244f38189923"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 01 Dec 2017 00:08:06 -0000

----==_mimepart_5a209d6224726_67c43f809e244f38189923
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #428.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/428#event-1366772894
----==_mimepart_5a209d6224726_67c43f809e244f38189923
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #428.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a209d6224726_67c43f809e244f38189923--


From nobody Thu Nov 30 16:08:17 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.881
X-Spam-Level: 
X-Spam-Status: No, score=-4.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Date: Thu, 30 Nov 2017 16:08:11 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512086891; bh=EZszqKRqH9kecP8zTiaEJbhMUyq5LFJsS5qVJLkGLeQ=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=w1FtDINCfyq9tXASQ9jzSNXwxWp5s6CPB6IJlPYMyG2H1YUTMAYn0qXSA5qaZh+Us 973kXQTD5ljgfBUs78vGWRTjh2syk/yIoH1NqiFJZftOaD8LLAw4bmwrGcmx6CC2G/ qa2+YWxsWP9UxVvZ94j9CCJou5WwASZtvJNf04aQ=
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] Clarify intermediary TLS role better (#429)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a209d6b48472_19743f90559bef2c2939fc"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 01 Dec 2017 00:08:15 -0000

----==_mimepart_5a209d6b48472_19743f90559bef2c2939fc
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #429.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/429#event-1366773059
----==_mimepart_5a209d6b48472_19743f90559bef2c2939fc
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #429.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a209d6b48472_19743f90559bef2c2939fc--


From nobody Thu Nov 30 16:08:25 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=avgHCjD7ZWN1o3lcB8KfQUlO77E=; b=Ll7iBYtYf+RbCzHx dBmDvtm4QgQxf+4Ql7qCqtaNMII9ZLguUgIPbqFG3zdh4xOYSNwQB3wY40ZmeT6C peO0q/+i3lAq+2pdxAPQsDgE+21XWfh9QBPbs5e7KUWMbe87BSKylT/STAuCftL5 QpS6DiXoOK+8NQCaCix21hKgQ0k=
Date: Fri, 01 Dec 2017 00:08:20 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] New abstract (#430)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a209d73e7098_1b65f3fe84dc3cf382926ad"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 01 Dec 2017 00:08:22 -0000

----==_mimepart_5a209d73e7098_1b65f3fe84dc3cf382926ad
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #430.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/430#event-1366773193
----==_mimepart_5a209d73e7098_1b65f3fe84dc3cf382926ad
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #430.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a209d73e7098_1b65f3fe84dc3cf382926ad--


From nobody Thu Nov 30 16:08:32 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=hMmyA9NLfkrQvkDcVIOGeVWP11Y=; b=u3yIAPN5NYvuaWwL tlWyQe//HrxgI5uxJCS8DrQpleD2RtuJPUSSIqPOZ/YnsQ+FRu4RfnLBbGRUb+5i KJk11RNbz9sKmYvnj026z7RWykZtoMVuEuqwEn/x1xDlF9zAJrv0/gE+9znzASKi jjaN/5f0gtLCIIgyQTslNbX01Mg=
Date: Fri, 01 Dec 2017 00:08:28 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] missing a word (#431)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a209d7c6c723_7c903facd8a16f344689d3"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 01 Dec 2017 00:08:31 -0000

----==_mimepart_5a209d7c6c723_7c903facd8a16f344689d3
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #431.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/431#event-1366773334
----==_mimepart_5a209d7c6c723_7c903facd8a16f344689d3
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #431.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a209d7c6c723_7c903facd8a16f344689d3--


From nobody Thu Nov 30 16:09:15 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level: 
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=T94xPwlxcB4V2ZvkLsvxHbkmY3k=; b=H+Ud2LM9chaiMcTr A0ECZmE3uhIFOFEz3pys37jql6HSRgR/Ba7E02tHeBZvRa3F/Ur02nY4ErkpDLS1 7Yei6UKB6x4bdofhGnXJaQ9fFEpDwtrnGGR6qQGwp4IhiR6WMAXS9UOSN7CClVZR Cm7OgLLEfeLKBQFTari/Kj8GDX4=
Date: Fri, 01 Dec 2017 00:09:11 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] Nits from Ben Kaduk's review (#440)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a209da6c0db0_588e3f8897598f30181272"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 01 Dec 2017 00:09:13 -0000

----==_mimepart_5a209da6c0db0_588e3f8897598f30181272
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #440.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/440#event-1366774070
----==_mimepart_5a209da6c0db0_588e3f8897598f30181272
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #440.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a209da6c0db0_588e3f8897598f30181272--


From nobody Thu Nov 30 16:16:55 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.396
X-Spam-Level: 
X-Spam-Status: No, score=-3.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=hmljXq+16hhwTOTYqdlBSOduYQk=; b=k9WhbusPnBKlKskz fX3M3NXSztJRMzvnAFqn4YG0octZ22pKgYWmas2SLK7/0TsZJBUKWg5q6vRlov6j nu+X5ehTiA/pDYZVZhGtetpp0u+B8og6Nwmqm7LIzRva169ZuolQxH03V0sdgx1g Cm/FsjlV1s5mNfM6MnJNNLnMMTA=
Date: Fri, 01 Dec 2017 00:16:52 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
Subject: [httpwg/http-extensions] Clarify what to do with out-of-order early data (#442)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a209f7444579_621b3f84e0d00f30789f"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 01 Dec 2017 00:16:55 -0000

----==_mimepart_5a209f7444579_621b3f84e0d00f30789f
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

In response to review by @vasilvv.
You can view, comment on, or merge this pull request online at:

  https://github.com/httpwg/http-extensions/pull/442

-- Commit Summary --

  * Clarify what to do with out-of-order early data

-- File Changes --

    M draft-ietf-httpbis-replay.md (9)

-- Patch Links --

https://github.com/httpwg/http-extensions/pull/442.patch
https://github.com/httpwg/http-extensions/pull/442.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/442

----==_mimepart_5a209f7444579_621b3f84e0d00f30789f
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

In response to review by @vasilvv.



You can view, comment on, or merge this pull request online at:
  https://github.com/httpwg/http-extensions/pull/442

Commit Summary

  Clarify what to do with out-of-order early data


File Changes

  
    M
    draft-ietf-httpbis-replay.md
    (9)
  


Patch Links:

  https://github.com/httpwg/http-extensions/pull/442.patch
  https://github.com/httpwg/http-extensions/pull/442.diff


—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  






----==_mimepart_5a209f7444579_621b3f84e0d00f30789f--


From nobody Thu Nov 30 21:50:21 2017
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.474
X-Spam-Level: 
X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;  h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=np1+oKG0UZOqKCyYrviR2tAcqos=; b=SKRX8+5qEaxRYLvt 34hUUhC1RBHDtcvGPrKwtuhR2hnqws1M2tBCGKS9l5qTh1eQTK/jxklFymJkbbyF sHSNXW1ecispw4cwyFwfXreCYk/CHkbNNDMQ0P85+FoaU0VSOPJd8tpYfsAL20eK rG/uTLWBqqh4aPbwsuhv7/q0K+0=
Date: Fri, 01 Dec 2017 05:50:17 +0000 (UTC)
To: httpwg/http-extensions 
Cc: Subscribed 
In-Reply-To: 
References: 
Subject: Re: [httpwg/http-extensions] Clarify what to do with out-of-order early data (#442)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a20ed99fbf5_80c3fb5ebb30f341532a9"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: 
Message-ID: 
From: HTTP issue updates 
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 01 Dec 2017 05:50:19 -0000

----==_mimepart_5a20ed99fbf5_80c3fb5ebb30f341532a9
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

It' indeed slightly clearer like this.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/442#issuecomment-348407744
----==_mimepart_5a20ed99fbf5_80c3fb5ebb30f341532a9
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

It' indeed slightly clearer like this.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


  
  





----==_mimepart_5a20ed99fbf5_80c3fb5ebb30f341532a9--