From nobody Tue Nov 1 03:31:46 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.596 X-Spam-Level: X-Spam-Status: No, score=-5.596 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_HI=-5, 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 Date: Tue, 01 Nov 2016 03:31:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1477996301; bh=9GD2RkPg6ARAitVOU+5LS0EBM2EoyPfGJOPWf6QPUNA=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=0DfFnAEiITLmJKwWhuvAehULUyvyTK1Q9dnlTpwuNKwUw1NYcE75jiCwUYCD1M/vO 71wmqbhYvX9A8wRGLwQTbQ50MMy67mELg5TNCNxITxpn2/2UDvPaBU5dI1pKADhasY RymwtcaxemVU9HRcwubwCYhQPGv4HKz3lqtGYMuI= To: httpwg/http-extensions Subject: [httpwg/http-extensions] remove bogus "!" (#258) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58186f0d7c986_17533fc619d5f2b823586b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 10:31:44 -0000 ----==_mimepart_58186f0d7c986_17533fc619d5f2b823586b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit it leads to kramdown warnings ("overwriting RFC...."). You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/258 -- Commit Summary -- * remove bogus "!" -- File Changes -- M draft-ietf-httpbis-cache-digest.md (2) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/258.patch https://github.com/httpwg/http-extensions/pull/258.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/258 ----==_mimepart_58186f0d7c986_17533fc619d5f2b823586b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

it leads to kramdown warnings ("overwriting RFC....").


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

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

Commit Summary

  • remove bogus "!"

File Changes

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_58186f0d7c986_17533fc619d5f2b823586b-- From nobody Tue Nov 1 05:24:41 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.882 X-Spam-Level: X-Spam-Status: No, score=-4.882 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Tue, 01 Nov 2016 05:24:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1478003076; bh=r3QthZjl5WOkN4LBY4fDWmCwSWGaG681n747RRM+ooY=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=svVfExtv1RbThZHTucxYMlEorlm0A6Q4iTaULBxbhAE5pK5LUqmZvWPtYTI42rZE1 /QaRPHpcysQtcs6YtvIqWcXfEw3m+P/lermVSDTYP/fOYYNux/ZEdZlExroaHCkyDK oJ9ZKdj5NrklRvAG0l7A/e3+t1D6SVUtjXZ7H7zY= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] remove bogus "!" (#258) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5818898453edd_2ac503f8f79e612a08353d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 12:24:39 -0000 ----==_mimepart_5818898453edd_2ac503f8f79e612a08353d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #258. -- 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/258#event-843272139 ----==_mimepart_5818898453edd_2ac503f8f79e612a08353d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #258.


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_5818898453edd_2ac503f8f79e612a08353d0-- From nobody Tue Nov 1 18:13:51 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.596 X-Spam-Level: X-Spam-Status: No, score=-5.596 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_HI=-5, 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 Date: Tue, 01 Nov 2016 18:13:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1478049226; bh=QIncDoE6VDaXzrvjuCU5JODp9SG0CEPh5OMB1dvdOmM=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=IIzfhH7eTERimPh2YjOwtkQX4XCFaDODX1y/uNT0AvUg+JMyNKcvexO+RFDr8F0R4 W9fxLCrX6cX+Qso54O4y5fJLD1wEmXPg3RAWD4G3NcVKbIRZel9iSx22glE9KHnZPl 2J01ojFlUUBf9zE+KGwNysLPgkX3Yz7iWv8d2oqk= To: httpwg/http-extensions Subject: [httpwg/http-extensions] Fix examples (#259) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58193dcac4bf2_11423f82b0af72c017086a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2016 01:13:50 -0000 ----==_mimepart_58193dcac4bf2_11423f82b0af72c017086a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Somehow I managed to mess up the examples royally. They were kinda valid, but the rs and id fields didn't match the rest of the example. You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/259 -- Commit Summary -- * Fix examples -- File Changes -- M draft-ietf-httpbis-encryption-encoding.md (9) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/259.patch https://github.com/httpwg/http-extensions/pull/259.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/259 ----==_mimepart_58193dcac4bf2_11423f82b0af72c017086a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Somehow I managed to mess up the examples royally. They were kinda valid, but the rs and id fields didn't match the rest of the example.


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

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

Commit Summary

  • Fix examples

File Changes

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_58193dcac4bf2_11423f82b0af72c017086a-- From nobody Tue Nov 1 18:21:51 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 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, 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 Date: Tue, 01 Nov 2016 18:21:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1478049707; bh=/adrFXU+hITr67LSkXp4hz1O8+e+utbpTYQT1rof/yw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NKI7l2pvGCj7P2+qn20ghMA+VHdFeGyWpII9q3zWI0paqYR/pb46pR4IyoROT5rpC 1mb1i6ch4k8RqwT0oOdy6F8aC4Uqd7DOPykiyFBGqKKAiPGRvOiE8kEAvci9o/MCiu c/XMsOMtOFAcbxyiciF4nF6ZLJ4HF3TWZJMVVfnU= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Fix examples (#259) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58193fab9a74f_4b153fb565e7b29c94473"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Push Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2016 01:21:49 -0000 ----==_mimepart_58193fab9a74f_4b153fb565e7b29c94473 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. d53076e Add intermediate values, expand explanation of examples -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/259/files/6c26164981de428b675413b6ec4d4becb7ae51ec..d53076e246cd5e4bb71e304110f10751b62a03c0 ----==_mimepart_58193fab9a74f_4b153fb565e7b29c94473 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • d53076e Add intermediate values, expand explanation of examples


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

----==_mimepart_58193fab9a74f_4b153fb565e7b29c94473-- From nobody Tue Nov 1 18:25:30 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 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, 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 Date: Tue, 01 Nov 2016 18:25:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1478049926; bh=baF9D8GWGdzxC7N5hBrNBGhD1hbQLnW2ExQUOIUlw1E=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Sneb4gh6mxhlq+QHHYsKhkyR5I5idbAwLYsHfSGSlBJf7dTb6rO+EAiL6e+e0n5hM 7DDnBDVHa2n/vEgu5wspQT95GxS+27mHx6THLVWHCD/y00y8oQ8qEWh+bSFFgEvBSV 6LNmkV05BDR0/ErBYdC+5tEqkf+YZmtrcd7IUpAw= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Fix examples (#259) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58194086e3ad3_34fb3fb0cf7d92bc1261af"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Push Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2016 01:25:29 -0000 ----==_mimepart_58194086e3ad3_34fb3fb0cf7d92bc1261af Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 4cd62c9 More expansion on the examples -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/259/files/d53076e246cd5e4bb71e304110f10751b62a03c0..4cd62c9fb0b6a99adeac72afc006fec7df833075 ----==_mimepart_58194086e3ad3_34fb3fb0cf7d92bc1261af Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 4cd62c9 More expansion on the examples


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

----==_mimepart_58194086e3ad3_34fb3fb0cf7d92bc1261af-- From nobody Tue Nov 1 20:25:25 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.596 X-Spam-Level: X-Spam-Status: No, score=-5.596 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_HI=-5, 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 Date: Tue, 01 Nov 2016 20:25:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1478057121; bh=xjPpvSrJcwXqF+/0sVRLMWX1cjIxtBBTJYaoTI0bmVk=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1OduLJb2GgWDUtVp7Cx9RadzLyrnlHl99lo3g0TI8WbHMm0xdZCTPbAC332NPuejh 3tcPD6/GuOek503SMrQWJ+d9HWbWoCkG4eAsqDTlqXJ3P5ViKjLs4M/kPOzMi7b2eQ /tER8FM1vBo3VXs3ZfKz/LJ9fCuUvi3+aMJmdp0Q= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] remove bogus "!" (#258) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58195ca1e34f9_66803fb0cf7d92bc1323227"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2016 03:25:24 -0000 ----==_mimepart_58195ca1e34f9_66803fb0cf7d92bc1323227 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @reschke, there are two ways to add references in the kramdown variant of markdown. Adding "x" to the appropriate references block and then using `{{x}}`, OR using `{{?x}}` (informative) or `{{!x}}` (normative). The warning comes about because the references block already contains "x", or because the reference is being used inconsistently (mixing styles is bad). -- 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/258#issuecomment-257762277 ----==_mimepart_58195ca1e34f9_66803fb0cf7d92bc1323227 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@reschke= , there are two ways to add references in the kramdown variant of mar= kdown. Adding "x" to the appropriate references block and then using {{x}}, OR using {{?x}} (informative) or {{!x= }} (normative).

The warning comes about because the references block already contains = "x", or because the reference is being used inconsistently (mixing styles= is bad).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub= , or mute the thread.

= ----==_mimepart_58195ca1e34f9_66803fb0cf7d92bc1323227-- From nobody Wed Nov 2 20:55:31 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -6.999 X-Spam-Level: X-Spam-Status: No, score=-6.999 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_DNSWL_HI=-5, 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 Date: Wed, 02 Nov 2016 20:55:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1478145319; bh=mIGNXKY70My0IFmeCaWRrE9RMxUunqBn/ztYo8K/w2E=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=m3DZvloL7YKcv1QXlY2I4dahz67gWd3HE3gSYWkvkvRS1vteF2hkfnEwFc0oxmwlj HRcL2u9KNtBwjSHPMuTfxon+K6aBe9aA0lcQv9q5VT1IvzQSzYEhBadfAlGgWBC2P7 S5zrTk2UGAQYCkgqY3fXdF7GOZdiMT9XGyAl9vAw= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Try to explain and justify the use of the absolute form in HTTP/1.1 (#257) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_581ab527a2fcd_2e263f9d307bb29c1954ed"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 03:55:26 -0000 ----==_mimepart_581ab527a2fcd_2e263f9d307bb29c1954ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -102,8 +102,14 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S An origin server that supports the resolution of `http` URIs can indicate support for this specification by providing an alternative service advertisement {{RFC7838}} for a protocol -identifier that uses TLS, such as `h2` {{RFC7540}}, or `http/1.1` {{?RFC7301}}. Note that HTTP/1.1 -requests MUST use the absolute form (see Section 5.3.2 of {{RFC7230}}). +identifier that uses TLS, such as `h2` {{RFC7540}}, or `http/1.1` {{?RFC7301}}. + +Requests for `http` resources using TLS MUST include the scheme in the request. HTTP/2 requires +this and provides the `:scheme` pseudo-header field for this purpose. HTTP/1.1 provides no such +field, and even prohibits the use of the absolute form for requests that are sent directly to an +origin server (see Section 5.3.1 of {{RFC7230}}). This document overrides that requirement for +requests with the `http` scheme that are sent over TLS; these requests MUST be made using the +absolute form as though the server were a proxy. OK, I tried :) So what is our rationale for excluding h1? That it doesn't carry an explicit scheme? -- 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/257 ----==_mimepart_581ab527a2fcd_2e263f9d307bb29c1954ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.


In draft-ietf-httpbis-http2-encryption.md:

> @@ -102,8 +102,14 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S
 
 An origin server that supports the resolution of `http` URIs can indicate support for this
 specification by providing an alternative service advertisement {{RFC7838}} for a protocol
-identifier that uses TLS, such as `h2` {{RFC7540}}, or `http/1.1` {{?RFC7301}}.  Note that HTTP/1.1
-requests MUST use the absolute form (see Section 5.3.2 of {{RFC7230}}).
+identifier that uses TLS, such as `h2` {{RFC7540}}, or `http/1.1` {{?RFC7301}}.
+
+Requests for `http` resources using TLS MUST include the scheme in the request.  HTTP/2 requires
+this and provides the `:scheme` pseudo-header field for this purpose.  HTTP/1.1 provides no such
+field, and even prohibits the use of the absolute form for requests that are sent directly to an
+origin server (see Section 5.3.1 of {{RFC7230}}).  This document overrides that requirement for
+requests with the `http` scheme that are sent over TLS; these requests MUST be made using the
+absolute form as though the server were a proxy.
 

OK, I tried :) So what is our rationale for excluding h1? That it doesn't carry an explicit scheme?


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_581ab527a2fcd_2e263f9d307bb29c1954ed-- From nobody Wed Nov 2 21:12:49 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.882 X-Spam-Level: X-Spam-Status: No, score=-4.882 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Wed, 02 Nov 2016 21:12:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1478146365; bh=2klJsnosCb8ovQrl09YBA67sgX2ESjduZaqm0RE3cZs=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pL3m92tEQSRP3j/ez+7HxJHL7TG/4oiu+vLlZQqGdxFQ7YeXXVbKxdvS1jq4lvNsa VAhXhJ4ODw9/m89fXYxzXG7meG6zMUiPNyPhZz+tjcwVVRg4Ij785hzotH/jP9I7lY DD4RmNACClobmiWYfuWzrMyyeQ5fL6b9GRb3b1kY= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Try to explain and justify the use of the absolute form in HTTP/1.1 (#257) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_581ab93d725f0_6fea3fc8eb58b29c792ad"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 04:12:48 -0000 ----==_mimepart_581ab93d725f0_6fea3fc8eb58b29c792ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #257. -- 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/257#event-845909877 ----==_mimepart_581ab93d725f0_6fea3fc8eb58b29c792ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #257.


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_581ab93d725f0_6fea3fc8eb58b29c792ad-- From nobody Tue Nov 8 00:29:57 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.954 X-Spam-Level: X-Spam-Status: No, score=-4.954 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_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Tue, 08 Nov 2016 00:29:52 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1478593792; bh=r97Xk5w+JPERpu24FeLorQ3qekoGc2ph2HDDHdtWkqI=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Q03UAka7OVzPImfLTEVcqbEGP8RoHI7j24LwBCYYzv3rtX5SUm2Em1sf3C25/JMNK qNCDKNoRYX+9ew4HQN1x3jlauGo6RoEFRiirDXklYehnL8M+NeouE1dvYbFtEHwHPV SOY38/D5dvR8DWw2gkn8K6tlJ6idVdeRlEJLuBOc= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Client hints: add support for hinting Display Gamut / Color Profile (#263) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58218d004ef2c_2a023ffa355732c0176763"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 08:29:55 -0000 ----==_mimepart_58218d004ef2c_2a023ffa355732c0176763 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The spec is past WGLC, so adding new hints right now might be bad timing. -- 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/263#issuecomment-259075398 ----==_mimepart_58218d004ef2c_2a023ffa355732c0176763 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The spec is past WGLC, so adding new hints right now might be bad timing.


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_58218d004ef2c_2a023ffa355732c0176763-- From nobody Sun Nov 13 07:37:40 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.001 X-Spam-Level: X-Spam-Status: No, score=-7.001 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 Date: Sun, 13 Nov 2016 07:37:35 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479051455; bh=8jYFsAZxrJLzE5ormWhoFuegKPWTWe/hqFBJZ/XzncA=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=v8/4XqByd7ZBV7ktKALqCCSV6vM9gDSXjG5mgidy0R2pVe6m4Yd4iuJgLW+RCmOps VdyRVpmNGgCzYsjakBiFG4BJ/43g9HXAU1tCz8cBXmgI2iADHRWu3WIhdyaEftvB0c 60T6GeGb6oJIog9StxtLFrMDnnUPE8Yzdrfm0CYM= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Advice for ServiceWorker implementation (#256) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582888bf4e182_7a333f9f5a06d130173334"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2016 15:37:38 -0000 ----==_mimepart_582888bf4e182_7a333f9f5a06d130173334 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FYI/FWIW I've just implemented this spec via a service worker. - NPM: https://www.npmjs.com/package/cache-digest-immutable - Code: https://gitlab.com/sebdeckers/cache-digest-immutable It would be nice if the spec clarified and defined the following. (I deduced it from @kazuho 's server and serviceworker implementations.) - HTTP header is called `cache-digest`. This is a very handy alternative to the HTTP2 frame which service workers can't access currently. - Base64 encoding must not be padded with `=` trailing. - String equivalent of the `COMPLETE` (0x2) flag for the HTTP header is `complete` and appended as `... base64 ...; complete` (note the semicolon and white space) Additionally more examples would be welcome, to aid implementors in validating their support. In particular the etags concatenation is unclear to me from the referenced 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/256#issuecomment-260193259 ----==_mimepart_582888bf4e182_7a333f9f5a06d130173334 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

FYI/FWIW I've just implemented this spec via a service worker.

It would be nice if the spec clarified and defined the following. (I d= educed it from @kazuho 's server and serviceworker implementations.)

  • HTTP header is called cache-digest. This is a very handy= alternative to the HTTP2 frame which service workers can't access curren= tly.
  • Base64 encoding must not be padded with =3D trailing.
  • String equivalent of the COMPLETE (0x2) flag for the HTT= P header is complete and appended as ... base64 ...; c= omplete (note the semicolon and white space)

Additionally more examples would be welcome, to aid implementors in va= lidating their support. In particular the etags concatenation is unclear = to me from the referenced spec.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_582888bf4e182_7a333f9f5a06d130173334-- From nobody Sun Nov 13 16:58:05 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.882 X-Spam-Level: X-Spam-Status: No, score=-4.882 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Sun, 13 Nov 2016 16:58:00 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479085080; bh=zCgAuJgACINtwg+0rkEhw0tjO9fCWzr7gr2IKJ1FTMM=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YCyXO74K3e9kMh55RhtvwMV4sWDj+wDGsxqpBW3ahDlY+dpopS3SHdim9cfXQTsTw ZISIts7QzczPB3bKX0PpO8MzJnZ7KGBghkAjyHBpZ1aL0UqJfmNBXInRfwN/XMZMXW A4hFTHU5Lm38qn8e/S7HuZhBPC1mFufKn0u3tgXw= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expand on motivation for the encoding (#213) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58290c1895b7d_28eb3f877b6851407626ed"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 00:58:03 -0000 ----==_mimepart_58290c1895b7d_28eb3f877b6851407626ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I believe this can be closed with the changes in https://github.com/httpwg/http-extensions/commit/5ec7eed4fa2c941a34e868117ef2fb634d8d506e -- 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/213#issuecomment-260226699 ----==_mimepart_58290c1895b7d_28eb3f877b6851407626ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I believe this can be closed with the changes in 5ec7eed


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_58290c1895b7d_28eb3f877b6851407626ed-- From nobody Sun Nov 13 17:56:51 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.001 X-Spam-Level: X-Spam-Status: No, score=-7.001 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 Date: Sun, 13 Nov 2016 17:56:47 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479088607; bh=iVlvELutOZm32BsJcriTlQ0ivy2qaA3fW41pz12chKk=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=m3aPzU9j3IdIp8L9D6Kl4kOzMVPgFNGRSkdVI9IP6Gv8teT74do3d5MZEYiiKPfsC BdVmuqWYdVDVrND16Vo+Ld0RB+pZbO4Oi6L44yUX6S6WZJEsaCs3XCzOYrPcrctZ7K B4ZcY1PpNMuqNttXLElygVLzHf/m07z9BCEvmnZY= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Overhead in cache digest algorithm (#264) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582919df75f48_60ba3fad0a03b1406711cf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 01:56:50 -0000 ----==_mimepart_582919df75f48_60ba3fad0a03b1406711cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thank you for your suggestions. > __De-dupe URLs before hashing them__ Is it likely that there'd be lot of freshly-cached (or stale-cached) responses sharing the same URL? My assumption is that the answer is no, and that we do not need to recommend deduping the URLs before hashing (note: deduplication after hashing and truncating would still be necessary even if you dedupe the URLs beforehand). If the answer is yes, then we should consider including additional keys into the hash context so that the server can more correctly identify what is being cached. > __Trim URL origin__ I agree that we can trim the origin part of the URL, since in the latest draft we have an origin field for every CACHE_DIGEST frame. -- 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/264#issuecomment-260231689 ----==_mimepart_582919df75f48_60ba3fad0a03b1406711cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thank you for your suggestions.

De-dupe URLs before hashing them

Is it likely that there'd be lot of freshly-cached (or stale-cached) r= esponses sharing the same URL?

My assumption is that the answer is no, and that we do not need to rec= ommend deduping the URLs before hashing (note: deduplication after hashin= g and truncating would still be necessary even if you dedupe the URLs bef= orehand).

If the answer is yes, then we should consider including additional key= s into the hash context so that the server can more correctly identify wh= at is being cached.

Trim URL origin

I agree that we can trim the origin part of the URL, since in the late= st draft we have an origin field for every CACHE_DIGEST frame.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_582919df75f48_60ba3fad0a03b1406711cf-- From nobody Mon Nov 14 00:32:52 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.597 X-Spam-Level: X-Spam-Status: No, score=-5.597 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Mon, 14 Nov 2016 00:24:37 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479111877; bh=td+9n2FhvV8oQCq7g0wwqJef3MvFkUF5r9V7m+Ulnzo=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xS/Vsw/tCBBiea957Tms1CZTqsvkO9tE6+Y32r/WgyEAUSQqlsGpJrc4gvgRKu9zV sazp6BjF6Fbx10R6SMyztcO+w2E8KnIH7/dtjiDtsj7JVTKRbL30+CG3Cr6E7WcPFI ZZ4Wk/IIoymufEnTzdPMtflA6Lnu6hClzzKa5Py0= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Digest algorithm (#228) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582974c563728_51be3f9d83a55130383060"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 08:32:51 -0000 ----==_mimepart_582974c563728_51be3f9d83a55130383060 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit When using small values, 50-100 bytes of a typical URL (w/o origin), I do not see significant performance difference between sha256 and xxhash64 using pure JavaScript implementations in the browser. YMMV. Code & results: https://gitlab.com/sebdeckers/fingerprinting-benchmarks -- 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/228#issuecomment-260274787 ----==_mimepart_582974c563728_51be3f9d83a55130383060 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

When using small values, 50-100 bytes of a typical URL (w/o origin), I= do not see significant performance difference between sha256 and xxhash6= 4 using pure JavaScript implementations in the browser. YMMV.

Code & results:
https= ://gitlab.com/sebdeckers/fingerprinting-benchmarks

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_582974c563728_51be3f9d83a55130383060-- From nobody Mon Nov 14 20:45:47 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 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_HI=-5, 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 Date: Mon, 14 Nov 2016 20:45:31 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479185131; bh=w6PTDidP4QjHKHnXTijj/6ziwl8QYtVYCkMfarV2adI=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y2u6YBc0C8erpKz1H8euQOG+r17P3LxY+meWAIzdxclz2lJ6OwUtKEwHSpj1xBeyR Qdqpoa+oJMZ6zX5QY16+oJdnYM8AjRrosUjmtWuQ11oKYfL1mLCi1dV374kdeWaKhn fH6kc1zFoUNfYOFknXWLH1DIbeUwbSj4iN7UfjfM= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Fix examples (#259) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582a92ebeeb4b_ef83fcecb7d91302350d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 04:45:34 -0000 ----==_mimepart_582a92ebeeb4b_ef83fcecb7d91302350d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Superceded by other changes. -- 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/259#issuecomment-260546248 ----==_mimepart_582a92ebeeb4b_ef83fcecb7d91302350d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Superceded by other changes.


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_582a92ebeeb4b_ef83fcecb7d91302350d0-- From nobody Tue Nov 15 22:33:12 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 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_HI=-5, 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 Date: Tue, 15 Nov 2016 22:33:05 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479277985; bh=nckcc4G69iBQvu6pEuskitrT4tmc7iKGFArMnWdk7LQ=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=z86QVcvkmtLZ4ABewdswUbOozDdwCSnffuL4w+rBJvFT0A0ZkZH7mZIc0XP6126Kj dYDP1n731121ur3yjI53bur9vIcEU1W8htEtC8UGc4q9eJq9X7N4ZSkI8E+TX1YS+a tA6KJSFNWZrm/jVrLzR86GkwLeVi0tXOPMRYLXdc= To: httpwg/http-extensions Subject: [httpwg/http-extensions] 'parmname' (#266) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582bfda1490cf_57683fc8b136f13c653649"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2016 06:33:10 -0000 ----==_mimepart_582bfda1490cf_57683fc8b136f13c653649 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ... occurs twice in the current draft, without much context. Should it be removed? -- 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/266 ----==_mimepart_582bfda1490cf_57683fc8b136f13c653649 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

... occurs twice in the current draft, without much context. Should it be removed?


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_582bfda1490cf_57683fc8b136f13c653649-- From nobody Tue Nov 15 22:40:48 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.097 X-Spam-Level: X-Spam-Status: No, score=-5.097 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Tue, 15 Nov 2016 22:40:42 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479278442; bh=1b1barX19E7fRo1AAPG/SP1cxKxXqLaI8ReUitswQuE=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=16wGUJUNo7SvToQqwQRrTgxDj7T9OgcwV6IB63r+PBoH6FJQaD4XrvBPgGS1pSUxA T10rI6H0VJM5BWcUUVsjRnFKpPlww4pS0HVCZUWCz2QhKm9LsUsOyDxQxp1nzL7/0j fVV/5+x2p9k9n+8VeGPOGBbj1Xi+ZvaepHsW6fSw= To: httpwg/http-extensions Subject: [httpwg/http-extensions] Give us something to hang onto (#267) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582bff6ae7898_51de3f8ee449313c92874d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2016 06:40:45 -0000 ----==_mimepart_582bff6ae7898_51de3f8ee449313c92874d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In working on RFC5988bis, I'm referring to this spec, and finding it's difficult to talk about the concepts, because so much has been pared back. In particular: * [ ] There isn't any prose reference to the "*" form of the attribute name; it only occurs in examples. One would assume that this is the normative way to invoke this encoding, but it isn't specified. * [ ] A distinct name for the encoding would help; right now, the best I can do is "the encoding specified in RFC5987bis". * [ ] The examples of how to use this in header specifications needs to be deeper. -- 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/267 ----==_mimepart_582bff6ae7898_51de3f8ee449313c92874d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In working on RFC5988bis, I'm referring to this spec, and finding it's difficult to talk about the concepts, because so much has been pared back.

In particular:

  • There isn't any prose reference to the "*" form of the attribute name; it only occurs in examples. One would assume that this is the normative way to invoke this encoding, but it isn't specified.
  • A distinct name for the encoding would help; right now, the best I can do is "the encoding specified in RFC5987bis".
  • The examples of how to use this in header specifications needs to be deeper.


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_582bff6ae7898_51de3f8ee449313c92874d-- From nobody Wed Nov 16 02:19:47 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.474 X-Spam-Level: X-Spam-Status: No, score=-5.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_HI=-5, 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 Date: Wed, 16 Nov 2016 02:19:42 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479291582; bh=OunAPUmnxZm4hRbvJd19dSACHqgYaTe00drZ5LfYgGc=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Y+R76qOCDKtjGuamk8UbtwMlaGfRBfB/+1MsooMCw6ox6UwmZrfqU+xJpWHx7onp3 UjsJRYuyeeL6dJXQl20It5oxUfi5a+3+yBIWCa2ycn374oV1Gbvw8UUjHTzDpixElu gcUFThAuTDj+dFS4ucjFVLUc+iV4/SZnmwa2W0IY= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Give us something to hang onto (#267) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582c32be2b897_cf03f8b3f84f13413429"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2016 10:19:45 -0000 ----==_mimepart_582c32be2b897_cf03f8b3f84f13413429 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit "nape"? (non-ASCII P. E.) -- 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/267#issuecomment-260908286 ----==_mimepart_582c32be2b897_cf03f8b3f84f13413429 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

"nape"? (non-ASCII P. E.)


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_582c32be2b897_cf03f8b3f84f13413429-- From nobody Wed Nov 16 16:46:08 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 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, 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 Date: Wed, 16 Nov 2016 16:46:04 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479343564; bh=Uz5wUYp6lG0pRH/kEpaSr8jMbdU2x8cNJLCMCVeSqYE=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QwUT1LySi+kiXi0DmkYo78QU71d+r5t/sKPpIRzH0V8ViNFd2PShIKsBmuLIC/g7F 0aZ3sAu+b8kI6TO/rM+MvU8nDvNpAfil0ItDZRK259RlyNtjO4cswLcqt0xZojpNOC zL0n1TGOa8HTqg1aeVm6+Ts90wFPBHl7JwSlJCjY= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expand on motivation for the encoding (#213) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582cfdcc78624_3ba23f9b596b3134735358"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 00:46:07 -0000 ----==_mimepart_582cfdcc78624_3ba23f9b596b3134735358 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #213. -- 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/213#event-862055497 ----==_mimepart_582cfdcc78624_3ba23f9b596b3134735358 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #213.


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_582cfdcc78624_3ba23f9b596b3134735358-- From nobody Wed Nov 16 22:27:58 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.954 X-Spam-Level: X-Spam-Status: No, score=-4.954 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_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Wed, 16 Nov 2016 22:27:53 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479364073; bh=qnoEdjcsq/1dowV0pa8jzyLKF383R8tikVTs895EK2s=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FaqsqUaf0+l+jGJ45xl7mgaqfU5joerWOgy5YF5tU8yKVYNFeU4hBrKmH+en1vsXL q0TKsA0VmzIiH1lMsy10pk+4F3dTLYAPhmFQKJeJ1pg2f7BgI8XDdjuU84kbyIZ8pi sNHo6aQNm2PE/lRqHmWilsxH4KlIrAaIcydgPFyQ= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Give us something to hang onto (#267) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582d4de950ebf_27423f9faff3913c14470a1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 06:27:56 -0000 ----==_mimepart_582d4de950ebf_27423f9faff3913c14470a1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Nape is an English word, a bit odd to use as a name. IPE? -- 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/267#issuecomment-261166568 ----==_mimepart_582d4de950ebf_27423f9faff3913c14470a1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Nape is an English word, a bit odd to use as a name. IPE?


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_582d4de950ebf_27423f9faff3913c14470a1-- From nobody Wed Nov 16 22:29:13 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.474 X-Spam-Level: X-Spam-Status: No, score=-5.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_HI=-5, 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 Date: Wed, 16 Nov 2016 22:29:10 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479364150; bh=6F9HxdXkkRUXWgYctzZnvZBJKpfxo3BXoFHn8FdDNwo=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FHCsAZJ2gFwYRJjDUXjMDi4zRLAXQm+rjI22O6H6sKPKlzqmzx+EO+Cr95SNQZpU+ K3v7pYtP2fG+edrthsRXgVHXLZhSGF6ExSx2g1wkv3HcxygBO4SVAU/9v5qENNv0DX apyGkp9ox1tP5iNMzKNDySpQnZbczOFErGZHrVq0= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Give us something to hang onto (#267) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582d4e366caa2_97f3fa64cd3d13c352215"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 06:29:13 -0000 ----==_mimepart_582d4e366caa2_97f3fa64cd3d13c352215 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sgtm I should use that everywhere then, including the title, right? -- 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/267#issuecomment-261166758 ----==_mimepart_582d4e366caa2_97f3fa64cd3d13c352215 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

sgtm

I should use that everywhere then, including the title, right?


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_582d4e366caa2_97f3fa64cd3d13c352215-- From nobody Thu Nov 17 04:55:59 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7 X-Spam-Level: X-Spam-Status: No, score=-7 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_HI=-5, 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 Date: Thu, 17 Nov 2016 04:55:54 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479387354; bh=udZqgCMbM19snMKrbJaFE8AfjKEUk/u332Dv0Js6HIo=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=dammKw5q/g+jtAQBD4b49d2sbWUKZgtqjQ93MHIt+dK3U6Zm3d0Zx0KeqZ4fLX6e0 WF1SzFpjn/l0+bshDUm8GwBF0AfMk+yyGDbdSKFar4SdSBzyjIDsxo2rDbKPWebnLm CsOHi6eMv6zoyFlZt3mbwlPaj0X1WABGaODED3+M= To: httpwg/http-extensions Subject: [httpwg/http-extensions] Enabling O(1) removal from digest (#268) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582da8daa442_16883fdf593e91302649fb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 12:55:57 -0000 ----==_mimepart_582da8daa442_16883fdf593e91302649fb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Current spec is using Golomb-coded sets as the algorithm to create digests. While they show great space-efficiency, Golomb-coded sets do not enable O(1) removal from the digest, which means from a browser implementation perspective, the browser would have to calculate the hash for each host upon connection creation. That poses a couple of issues from an implementation perspective: * Calculating the hash on each connection establishment may be expensive. That part seems inherent to the algorithm and not likely to be optimized away. * Calculating the hash requires per-host indexing. That part is just a limitation of many current cache implementations. A cache digest algorithm that enables O(1) removal (as well as addition) to the digest would enable us to move away from those limitations: * Browsers can calculate a per-host digest once, then keep updating it as resources are added to the cache as well as when resources are removed from the cache. No need for per-host indexing. - In order to do that, browsers would need to persist digests along with the cache * Upon connection establishment, the browser can just send the ready-made digest to the server. Win! During the HTTPWS, counting bloom filters were mentioned as an O(1) removal algorithm, but they are extremely inefficient when it comes to space. (~4 times bigger than bloom filters) Turns out, [Cuckoo filters](https://www.cs.cmu.edu/~binfan/papers/login_cuckoofilter.pdf) enable O(1) removal while being more space efficient than bloom filters. While they are slightly bigger than Golomb-coded sets based digests, the cheaper runtime costs can make up for that deficiency. /cc @kazuho @mnot @cbentzel @mcmanus -- 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/268 ----==_mimepart_582da8daa442_16883fdf593e91302649fb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Current spec is using Golomb-coded sets as the algorithm to create digests.

While they show great space-efficiency, Golomb-coded sets do not enable O(1) removal from the digest, which means from a browser implementation perspective, the browser would have to calculate the hash for each host upon connection creation.

That poses a couple of issues from an implementation perspective:

  • Calculating the hash on each connection establishment may be expensive. That part seems inherent to the algorithm and not likely to be optimized away.
  • Calculating the hash requires per-host indexing. That part is just a limitation of many current cache implementations.

A cache digest algorithm that enables O(1) removal (as well as addition) to the digest would enable us to move away from those limitations:

  • Browsers can calculate a per-host digest once, then keep updating it as resources are added to the cache as well as when resources are removed from the cache. No need for per-host indexing.
    • In order to do that, browsers would need to persist digests along with the cache
  • Upon connection establishment, the browser can just send the ready-made digest to the server. Win!

During the HTTPWS, counting bloom filters were mentioned as an O(1) removal algorithm, but they are extremely inefficient when it comes to space. (~4 times bigger than bloom filters)

Turns out, Cuckoo filters enable O(1) removal while being more space efficient than bloom filters. While they are slightly bigger than Golomb-coded sets based digests, the cheaper runtime costs can make up for that deficiency.

/cc @kazuho @mnot @cbentzel @mcmanus


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_582da8daa442_16883fdf593e91302649fb-- From nobody Thu Nov 17 05:09:13 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -6.5 X-Spam-Level: X-Spam-Status: No, score=-6.5 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_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Thu, 17 Nov 2016 05:09:09 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479388149; bh=nKNvHXs475p/b1FJUaDRcgGfY4foGrb3KBe5BG98DwY=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BpmmOXEUnJ8Qsh6bWeiTrk9Aln0WVDf3dvd0CIwipKqA+HOlpIiXfFePJ6NhQh8yX 7ID2t+YXhA0e9FUYksJpPKc86J8DeovOXNDKNJpUikX89TiWs75yEvUjKR11WUP3M3 afESDHDiMLhWPvb9oYxCi272suLDTiWrd2uPl18g= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Enabling O(1) removal from digest (#268) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582dabf5d1500_7fa43faf0598d138352742"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 13:09:12 -0000 ----==_mimepart_582dabf5d1500_7fa43faf0598d138352742 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thank you for opening the issue. I think we should adopt a method that can be implemented by web browsers easily, as long as the digest remains fairly compact. Regarding the size of the digest, I have no objection for choosing Cuckoo Filters. However, I am not sure if the proposed method would work as expected. > Browsers can calculate a per-host digest once, then keep updating it as resources are added to the cache as well as when resources are removed from the cache. There are two digests (i.e. fresh and stale) for every host. You need to update the digests when the state of a cached response changes from fresh to stale, by evicting the entry from the fresh digest and inserting it to the stale digest. Is that possible? Also, if it is possible to maintain a per-origin Cuckoo Filter that is kept in sync with the cached resources, I think it would also be possible to maintain a per-host list of cached URLs as well. Anyways, let me state that I'm very delighted to see people looking into how Cache Digests can be implemented within the web browser. I was considering of polishing up my ServiceWorker implementation, but maybe I should spend time in looking into the browsers 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/issues/268#issuecomment-261242398 ----==_mimepart_582dabf5d1500_7fa43faf0598d138352742 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thank you for opening the issue. I think we should adopt a method that= can be implemented by web browsers easily, as long as the digest remains= fairly compact. Regarding the size of the digest, I have no objection fo= r choosing Cuckoo Filters.

However, I am not sure if the proposed method would work as expected.<= /p>

Browsers can calculate a per-host digest once, then keep updating it a= s resources are added to the cache as well as when resources are removed = from the cache.

There are two digests (i.e. fresh and stale) for every host. You need = to update the digests when the state of a cached response changes from fr= esh to stale, by evicting the entry from the fresh digest and inserting i= t to the stale digest.

Is that possible?

Also, if it is possible to maintain a per-origin Cuckoo Filter that is= kept in sync with the cached resources, I think it would also be possibl= e to maintain a per-host list of cached URLs as well.

Anyways, let me state that I'm very delighted to see people looking in= to how Cache Digests can be implemented within the web browser. I was con= sidering of polishing up my ServiceWorker implementation, but maybe I sho= uld spend time in looking into the browsers as well.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_582dabf5d1500_7fa43faf0598d138352742-- From nobody Thu Nov 17 05:29:00 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -6.5 X-Spam-Level: X-Spam-Status: No, score=-6.5 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_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Thu, 17 Nov 2016 05:28:55 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479389335; bh=+47P7d4Hc7UnmB+vOEHNktdRqbgid+JImWf3TP7wfIo=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zB+f0A+mwjXoh8v8Z8nG59o2LzdVeztMsxm+0sxu1SnAcdRPLKx33TECJ/EJ0TTuS /ml1D2v2LebSSJ0HRx1JVElP2hPlLacAjSVHfSdV3oSZ/THLaVSJuWFAPrQ3v9nxkx XoY+fvmE9bdXTaR6/reYobVsNKbL71soBK0ziVMs= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Enabling O(1) removal from digest (#268) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582db097ba5f8_27453fb82b94f13832392"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 13:28:59 -0000 ----==_mimepart_582db097ba5f8_27453fb82b94f13832392 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > There are two digests (i.e. fresh and stale) for every host. You need to update the digests when the state of a cached response changes from fresh to stale, by evicting the entry from the fresh digest and inserting it to the stale digest. Hmm, that would indeed increase complexity as I believe the cache is not aware of resources going into the "stale" state unless they're queried. (@cbentzel & @mcmanus - please correct me if I'm wrong). Is there any reason we can't use a single digest with URL+ETag (so use the ETags also for fresh resources) to avoid that complexity? Are there any downsides to that? -- 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/268#issuecomment-261246217 ----==_mimepart_582db097ba5f8_27453fb82b94f13832392 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

There are two digests (i.e. fresh and stale) for every host. You need = to update the digests when the state of a cached response changes from fr= esh to stale, by evicting the entry from the fresh digest and inserting i= t to the stale digest.

Hmm, that would indeed increase complexity as I believe the cache is n= ot aware of resources going into the "stale" state unless they're queried= . (@cbentz= el & @mcmanus - please correct me if I'm wrong).

Is there any reason we can't use a single digest with URL+ETag (so use= the ETags also for fresh resources) to avoid that complexity? Are there = any downsides to that?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_582db097ba5f8_27453fb82b94f13832392-- From nobody Thu Nov 17 06:05:57 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -6.501 X-Spam-Level: X-Spam-Status: No, score=-6.501 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Thu, 17 Nov 2016 06:05:51 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479391551; bh=Hn20hLa25LXPhGOKRjIvZLVl4B7sVVS8KGBz8nGaCSg=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pybI6ohqlWHpuy6eV6uzdcXo7RTMNx2sE/9gRG3AUnCTBI6aEzLfhciVl9PvGQe2F zicBMi3+T2qq7ZIOLZoondUu71MEynnMOIrmz0TQ+xNs/IP61n61hYxdwqelGB22DE U5IOWZSsXrc6gdmgk5VP+REWOZwcFOu7Pmmy05NU= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Enabling O(1) removal from digest (#268) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582db93f90334_13143f9f7480313c5523e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 14:05:56 -0000 ----==_mimepart_582db93f90334_13143f9f7480313c5523e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @yoavweiss > Is there any reason we can't use a single digest with URL+ETag (so use the ETags also for fresh resources) to avoid that complexity? Are there any downsides to that? It is true that you could use URL+ETag as a key of fresh digests (though server implementations might become slightly complicated). However, it is still desirable to be able to distinguish if whether a resource is freshly cached or stale-cached, since the server behavior needs to be different for the two. For freshly cached resources, there is no need to push anything. For stale-cached resources, the server needs to push 304. If the client sends a single digest covering both freshly and stale-cached resources, then the server would need to either push nothing for both of them (which means that client would issue conditional requests for stale-cached responses that it need to use), or push 304 for both of them (which means that the server would send 304 for even the freshly cached resources). Note also that we haven't agreed on whether if sending a digest of stale responses is worth the extra bandwidth, or how we should push 304. Last time I looked into my Firefox's cache, the number of cached objects were as follows: |domain|total objects|fresh objects| | --- | --- | --- | |*.facebook.com|2273|790| |*.google.com|1003|373| As you can see, fresh objects consists about 1/3 of the total objects cached for a domain. Sending a digest for all objects would roughly triple the size of the digest from when we just send the digest for freshly-cached objects. Considering the fact that assets critical to the rendering path is likely marked as fresh, it would make sense to just send the digest for freshly cached objects. -- 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/268#issuecomment-261254539 ----==_mimepart_582db93f90334_13143f9f7480313c5523e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@yoavw= eiss

Is there any reason we can't use a single digest with URL+ETag (so use= the ETags also for fresh resources) to avoid that complexity? Are there = any downsides to that?

It is true that you could use URL+ETag as a key of fresh digests (thou= gh server implementations might become slightly complicated).

However, it is still desirable to be able to distinguish if whether a = resource is freshly cached or stale-cached, since the server behavior nee= ds to be different for the two. For freshly cached resources, there is no= need to push anything. For stale-cached resources, the server needs to p= ush 304.

If the client sends a single digest covering both freshly and stale-ca= ched resources, then the server would need to either push nothing for bot= h of them (which means that client would issue conditional requests for s= tale-cached responses that it need to use), or push 304 for both of them = (which means that the server would send 304 for even the freshly cached r= esources).

Note also that we haven't agreed on whether if sending a digest of sta= le responses is worth the extra bandwidth, or how we should push 304.

=

Last time I looked into my Firefox's cache, the number of cached objec= ts were as follows:

domain total objects fresh objects
*.facebook.com 2273 790
*.google.com 1003 373

As you can see, fresh objects consists about 1/3 of the total objects = cached for a domain. Sending a digest for all objects would roughly tripl= e the size of the digest from when we just send the digest for freshly-ca= ched objects.

Considering the fact that assets critical to the rendering path is lik= ely marked as fresh, it would make sense to just send the digest for fres= hly cached objects.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_582db93f90334_13143f9f7480313c5523e-- From nobody Fri Nov 18 07:59:13 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.001 X-Spam-Level: X-Spam-Status: No, score=-7.001 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 Date: Fri, 18 Nov 2016 07:59:08 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479484748; bh=mdB4CEhlDejkTsu0rX05DAGk1rzFL3qrn2H8wsZi3VQ=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lMF8Rea9XX5h2QjGQMOM2gwqulwk2FtnUjDUoriT8gpDNn9vdCPx25wsUMpyhNs54 Ks5rVDg6qibmrAloS+5BZ+uUFFRIGm5m8i6M0bnURMKsRx6Vg8GIB1yAxkCjb6nVEQ Y7rexDAFb25GNcDIyi2c2xgdIMDna0fM4CIvHGS0= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Enabling O(1) removal from digest (#268) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_582f254cc2d10_77313ff4bb88f140689a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 15:59:11 -0000 ----==_mimepart_582f254cc2d10_77313ff4bb88f140689a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > In addition to my previous comments, I think you cannot expand an existing Cuckoo Filter. > > In other words, every time the number of resources that need to be tracked doubles (or halves), you would need to reconstruct a new Cuckoo Filter (of the adjusted size) by iterating through the cache entries. I do not think that is something you would like to do. My understanding from the Cuckoo filter and [Cuckoo hashing](http://www.it-c.dk/people/pagh/papers/cuckoo-jour.pdf) papers is that this expansion is taken into consideration in the amortized complexity analysis. Even if you look at the worst case, such expansion's cost is O(N), which is asymptotically similar to the cost GCS incur on every connection establishment. -- 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/268#issuecomment-261567356 ----==_mimepart_582f254cc2d10_77313ff4bb88f140689a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In addition to my previous comments, I think you cannot expand an exis= ting Cuckoo Filter.

In other words, every time the number of resources that need to be tra= cked doubles (or halves), you would need to reconstruct a new Cuckoo Filt= er (of the adjusted size) by iterating through the cache entries. I do no= t think that is something you would like to do.

My understanding from the Cuckoo filter and Cuckoo hashing papers is that= this expansion is taken into consideration in the amortized complexity a= nalysis. Even if you look at the worst case, such expansion's cost is O(N= ), which is asymptotically similar to the cost GCS incur on every connect= ion establishment.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_582f254cc2d10_77313ff4bb88f140689a-- From nobody Sun Nov 20 00:05:32 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.001 X-Spam-Level: X-Spam-Status: No, score=-7.001 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 Date: Sun, 20 Nov 2016 00:05:28 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479629128; bh=3TdN0tqRPI5f0CoXaSl76WMxJTgnFN1kJ+eGvdt6WLg=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=U8F+zTDayXTQ6kg+fw/eZsfxKpL4CY3Ag9AbdvZtFPjdqnEfiTf+rPMM/B4JcH3C8 px6JRG+qxbbKx0vAOPkU91tNrWmZyUamZCmbPEVfzygxSmYvbOkKBTEftyWt4PoDhm bZPUWHoNNBTshi66zSz947ouU75gR8aobHFhMrF4= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Enabling O(1) removal from digest (#268) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_583159488d8ea_604d3fab1030913442257d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 08:05:31 -0000 ----==_mimepart_583159488d8ea_604d3fab1030913442257d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > However, in a Cuckoo Filter, there is no such reference. Therefore, to (re)build a Cuckoo Filter, you would need to use some pre-existing structure in the browser cache to iterate through the objects belonging to a specific origin. However, under premise that there is no per-origin index (note: we are considering the use of Cookie Filters since we do not want to introduce such index), we would need to iterate through the entire cache. That would indeed be a serious handicap to the Cuckoo filter approach. Fortunately, browsers can extend the basic Cuckoo filter implementation to also store the full crypto hashes or other references to the stored objects on top of storing fingerprints. This extra info won't be sent up as part of the Cuckoo filter, but can be used locally to extend it in O(N) complexity. Such references to the actual stored objects can also allow periodic (potentially out-of-band) O(N) calculation to create a stale resources filter that would make it easier to push 304s. -- 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/268#issuecomment-261764848 ----==_mimepart_583159488d8ea_604d3fab1030913442257d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

However, in a Cuckoo Filter, there is no such reference. Therefore, to= (re)build a Cuckoo Filter, you would need to use some pre-existing struc= ture in the browser cache to iterate through the objects belonging to a s= pecific origin. However, under premise that there is no per-origin index = (note: we are considering the use of Cookie Filters since we do not want = to introduce such index), we would need to iterate through the entire cac= he.

That would indeed be a serious handicap to the Cuckoo filter approach.=
Fortunately, browsers can extend the basic Cuckoo filter implementation t= o also store the full crypto hashes or other references to the stored obj= ects on top of storing fingerprints.

This extra info won't be sent up as part of the Cuckoo filter, but can= be used locally to extend it in O(N) complexity.

Such references to the actual stored objects can also allow periodic (= potentially out-of-band) O(N) calculation to create a stale resources fil= ter that would make it easier to push 304s.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_583159488d8ea_604d3fab1030913442257d-- From nobody Sun Nov 20 18:10:36 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.383 X-Spam-Level: X-Spam-Status: No, score=-5.383 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_MSPIKE_H2=-0.001, 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 Date: Sun, 20 Nov 2016 18:10:33 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479694233; bh=fi57RYGJpFTVtcmP+c09Ha8SohsCWNEu4urWx0WCtEg=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CjkWJiRkyY9I+iWq04aL87EOWFnRX5G+YfP+vvrive2UBXNUTYZPa1/JXXyIPZ1Gc 4YHClX4vk+Z0iptKfUCKXOKjzMZi7G3/1QhqlfA73VOjr8E+sUUWim14K0tF9CXUd6 SjBbjisFROJH4+YAo4BPzROtMWNc7+5o4mJEkL3E= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Exclude HTTP/1.1 (#262) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_583257994e863_1695a3f92eaba114012907"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 02:10:35 -0000 ----==_mimepart_583257994e863_1695a3f92eaba114012907 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #262. -- 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/262#event-865821848 ----==_mimepart_583257994e863_1695a3f92eaba114012907 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #262.


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_583257994e863_1695a3f92eaba114012907-- From nobody Sun Nov 20 18:10:58 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 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, 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 Date: Sun, 20 Nov 2016 18:10:55 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479694255; bh=k2lqtsPlJsRcuDWKkdZVYIUYbOkAU3dVbAKmPfxmjqo=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BwaHRHG8BYqNk+KMYF0jYY30+IvmQrTkGegFLTpu4uSu9K+tISWPCdRHaPwAUHXuL gBo20VVATiWe/lSa/B60iZD6PaJnx4pS2mgnSsxqEnXQBvIGJ1pYLcGZnxfvinucjI bMKJhxxMoJziDQwSud9zL7TuUSiwVWqPcDrqqP/E= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] https origins are no longer relevant for http-opportunistic resources (#261) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_583257afd3c02_625e3fc2fa86b134546562"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 02:10:58 -0000 ----==_mimepart_583257afd3c02_625e3fc2fa86b134546562 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #261. -- 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/261#event-865822049 ----==_mimepart_583257afd3c02_625e3fc2fa86b134546562 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #261.


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_583257afd3c02_625e3fc2fa86b134546562-- From nobody Sun Nov 20 18:11:35 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.383 X-Spam-Level: X-Spam-Status: No, score=-5.383 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_MSPIKE_H2=-0.001, 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 Date: Sun, 20 Nov 2016 18:11:32 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479694292; bh=vq1+xFG53xkb4cgdZ2UzzmqKz3L/jHgjsKtFmknqzqw=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YBPTkMCUKj62OybYtMqKFxPrJ1/pLDs/PmULafxG+tq+Jxy6lTqNtfuzsAc3e/WmJ B9cEfX9gfq0AjYhFQFTUuURfk2SJyua8WFz+m3XtjpmS6JIEh/gvk6izR0QEmPWf3d q8Nz50i/DvhgNWrf3FSlL/lqzMkD568S7ZVez3HU= To: httpwg/http-extensions In-Reply-To: References: Subject: =?UTF-8?Q?Re:_[httpwg/http-extensions]_The_=22mixed-scheme=22?= =?UTF-8?Q?_field_is_probably_needed_when_you_make_any_request=E2=80=A6?= =?UTF-8?Q?_=28#242=29?= Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_583257d4768f3_b423f8424f9913c2771b3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 02:11:34 -0000 ----==_mimepart_583257d4768f3_b423f8424f9913c2771b3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #242. -- 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/242#event-865822336 ----==_mimepart_583257d4768f3_b423f8424f9913c2771b3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #242.


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_583257d4768f3_b423f8424f9913c2771b3-- From nobody Sun Nov 20 18:13:05 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.383 X-Spam-Level: X-Spam-Status: No, score=-5.383 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_MSPIKE_H2=-0.001, 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 Date: Sun, 20 Nov 2016 18:13:01 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479694381; bh=nxzJ6KxFFy+XAl/5lh34X2UqNY+bzdd0YICxikkdArE=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xs19wmbWAwdb3NE3FyaTSp9MqyXX8igS7mDkQdmYTL8+l9etKLkQGxZJ6BU98f9LS IxWkS09xpyKECabqqyEfjuyTykb9y17g1NnHwgLoxUO4f3JOqk8pPbXm67In0+M5aj aD8adUhXzaIXCy9xr6BP/LJKWnsH1u5BgFfk+D3E= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] require .well-known/http-opportunistic (#235) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5832582d5f84b_21733fcc85be1130437955"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 02:13:03 -0000 ----==_mimepart_5832582d5f84b_21733fcc85be1130437955 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mcmanus let me know if this isn't clear in the latest version. I think that we're OK. -- 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/235#issuecomment-261826457 ----==_mimepart_5832582d5f84b_21733fcc85be1130437955 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mcmanus let me know if this isn't clear in the latest version. I think that we're OK.


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_5832582d5f84b_21733fcc85be1130437955-- From nobody Sun Nov 20 18:13:19 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.383 X-Spam-Level: X-Spam-Status: No, score=-5.383 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_MSPIKE_H2=-0.001, 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 Date: Sun, 20 Nov 2016 18:13:15 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479694395; bh=RZ3hS543pUiUHSpEhZEONq5oslRsnGQTYsdSJc1p/G4=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fawJVlG66tx9ssR56FTAj2/eonhphKZz6QpeV0GnbVmdZ40NNGx4xSgWDkLYU5H9s Cl3v6I0+Xr93VgYuLEVA8RMXZRafGdxjXv1vDul2yMTQ5It1qZLXxSQXAE2rGWqcQ/ uqW4XGvoxFuUL8ixvA+qT48oynHwTk96iuKEDV8c= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] require tls auth (#234) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5832583bcc401_3d6f3fa13a99113016454e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 02:13:17 -0000 ----==_mimepart_5832583bcc401_3d6f3fa13a99113016454e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #234. -- 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/234#event-865823237 ----==_mimepart_5832583bcc401_3d6f3fa13a99113016454e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #234.


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_5832583bcc401_3d6f3fa13a99113016454e-- From nobody Sun Nov 20 18:13:32 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 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_HI=-5, 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 Date: Sun, 20 Nov 2016 18:13:29 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479694409; bh=aDmNavOlxlun3eCbnglHrc4BtdueHo/zHQ2T+cNXq2M=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uYD/F3nR0jmrwJA4p8EYGxrUiltcmRq+rnaT8V+03Gbo/zi2iRkasEo5Y6pM3P1Id PqAM2Wg5FZLtHqG/30GFSK3WlQJ5mfNUziwn+LL5aUk7SMzNTjbTd5tKYJ8gpMn8af hM8uCAYlonjEQ9jBCIbs4Acn8EF6bnYwduxTxS90= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Provide rules for handling duplicate keys (#205) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58325849bb3ec_1bf3fd8859ad13c37127f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 02:13:31 -0000 ----==_mimepart_58325849bb3ec_1bf3fd8859ad13c37127f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This has been 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/205#issuecomment-261826506 ----==_mimepart_58325849bb3ec_1bf3fd8859ad13c37127f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This has been 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_58325849bb3ec_1bf3fd8859ad13c37127f-- From nobody Sun Nov 20 18:13:35 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.902 X-Spam-Level: X-Spam-Status: No, score=-4.902 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Sun, 20 Nov 2016 18:13:30 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479694410; bh=l/dxj7WE4pS8374l/a1l1aXmy1CVecc78HiYWPkkn4o=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=A47xheGecrestEHXkPDfMZEpG4ShTqarEC6bvURpKwFr8/UpFjtf+hC7RYJhrcvT/ WJsXOBmxsX/iZUrGL9x/aM3IxP0cy6FSdTm8bHpYMGCbAn9X1thPnEcmnswxs7cH+V q1urFDTgN5maKztsStSd4topC6MguTwyPUYYy0HQ= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Provide rules for handling duplicate keys (#205) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5832584a19b1_68733ff7ad5fb13c296973"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 02:13:31 -0000 ----==_mimepart_5832584a19b1_68733ff7ad5fb13c296973 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #205. -- 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/205#event-865823368 ----==_mimepart_5832584a19b1_68733ff7ad5fb13c296973 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #205.


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_5832584a19b1_68733ff7ad5fb13c296973-- From nobody Sun Nov 20 18:22:42 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.455 X-Spam-Level: X-Spam-Status: No, score=-5.455 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 Date: Sun, 20 Nov 2016 18:22:39 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479694959; bh=Xbp2EIirqFCyFx2rD/5xqo7my6wFP9UbDO0uhXQa3aI=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=elt7EhL8wLeW6sFiwSe9hghqYpRdTo0f6y0xloMQElPUi8+rH9gnk4T/G5EsrRVTP IbO9tEO7FgCYdH6+GCNpiWkND+F9NUwU1otnFzirN4AstkePO78Ahudf5zswXFc8BB vlTpib04uo8UM3P1bzfoYjxctMZNC09N0GYTlyAE= To: httpwg/http-extensions Subject: [httpwg/http-extensions] mixed schemes (#269) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58325a6f6a65b_2a7d3ff5ef70513c1864f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 02:22:41 -0000 ----==_mimepart_58325a6f6a65b_2a7d3ff5ef70513c1864f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Can we coalesce http and https? The implication from everything we've said is "yes", but Erik remains reluctant. -- 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/269 ----==_mimepart_58325a6f6a65b_2a7d3ff5ef70513c1864f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Can we coalesce http and https? The implication from everything we've said is "yes", but Erik remains reluctant.


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_58325a6f6a65b_2a7d3ff5ef70513c1864f3-- From nobody Sun Nov 20 19:30:15 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.383 X-Spam-Level: X-Spam-Status: No, score=-5.383 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_MSPIKE_H2=-0.001, 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 Date: Sun, 20 Nov 2016 19:30:12 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479699012; bh=jg5YyVHXu3SB7n+fIE7ocuM54r+Ml9waadgM2OjzRMg=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pGmWALGBt48fUWywNSUJfcjSouSLbC/M0Tad5Lkh3HxY5W7BF27aVOMaevbTM84iY 0JmHALcMaY2cqcuZOHZlAVuj3IORT4KTIpKbbpEPKrwywM2mvnWceNZE3n3hcm5veu pDDIWQtn2BSPKWV8gQmttt68+0BcQsaGAYZFdngI= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Don't allow clients to send http and https requests coalesced. (#270) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58326a44342f0_6d273fb5430a313c13261ef"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Push Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 03:30:14 -0000 ----==_mimepart_58326a44342f0_6d273fb5430a313c13261ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 68891a4 Forbid coalescing of all forms -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/270/files/1642b4a8d7517b72dca7cb697688252f50b22480..68891a45fcdcaeecfed28089a2e564afe7aa30f7 ----==_mimepart_58326a44342f0_6d273fb5430a313c13261ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 68891a4 Forbid coalescing of all forms


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

----==_mimepart_58326a44342f0_6d273fb5430a313c13261ef-- From nobody Mon Nov 21 00:43:16 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.001 X-Spam-Level: X-Spam-Status: No, score=-7.001 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 Date: Mon, 21 Nov 2016 00:43:11 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479717791; bh=D+mqa4RE/h9QZkTNQpe9d/QOdryZs8tA0IKsleI5pfA=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fZjr/u5mfVYQObwdtPil3Qxg3PuhxSSgH8SX3TwndKiO5b81IUEk42lse+amC+06V Gl9lobYYnulDlS+IMjZMZnsWYOl94alc+SrTLojJJlhaqOGUR0Nr7PZzkOsU6srR81 jQ40RRc6NGbOJTJeAolZhmCe9EnjLUs53Rge1JEA= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Client hints: add support for hinting Display Gamut / Color Profile (#263) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5832b39f7164c_8173f93e656f130255331"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 08:43:14 -0000 ----==_mimepart_5832b39f7164c_8173f93e656f130255331 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @igrigorik Exactly. Still the poll numbers are not high but we can expect them to go wild next year since most manufactured displays are now wide-color. We can expect something alike to the Retina/Non-Retina race revolution. > Color-Gamut + Content-Color-Gamut: I think this makes sense. Yes, this would cover 95% of use cases, and spec-wise it should be simple enough. So, even for simple cases, this CH spec addition is close to a `MUST` for responsive color optimisation. Why? Because `wide-gamut` is one of things those things that cannot even be guessed by *User Agent*: there is no info about the display on the string. So this spec is gonna be the only way to advertise to the server in an automated way. > @color-profile.. I'm still trying to grok. From what I can tell right now, it accepts a URL to a profile, plus a rendering intent. Do we have some concrete examples of how we expect developers to use this? Yes, I agree the use cases for `color-profile` are few, thus I don't see this one as `MUST`, however a `nice to have` one. The use cases I see for this are minor but: 1) To override a photo ICC profile (ie. it was wrong in the first place) 2) To specify a ICC profile for a photo that had ICC stripped - or didn't had one in the first place (ie. it was removed by some "optimisation" tool like [jpegoptim](http://www.kokkonen.net/tjko/src/man/jpegoptim.txt) or [ImageOptim](https://imageoptim.com/color-profiles.html)) So yeah I can guess mostly photographer / design websites would make use of this one. Note that, at least [CSS Level 4](https://www.w3.org/TR/css-color-4/#at-ruledef-profile), doesn't need to include the URL for the profile since its predefined in two cases: `DCI-P3` and `Rec.2020`. > Does this prevent us from publishing a new "replacement" draft? How do we advance these things forward? I don't know about this *WG particular timing interests*, however having `Color-Gamut + Content-Color-Gamut` in the spec as soon as possible would give Browser vendors enough time and pave the way to implement it smoothly. Be either an addition to CH or a different spec. For **consistency** it makes sense to be a part of the CH spec though, just like `DPR`. I can understand well why some don't see the *urge for it*: you need to have a `wide-color` hardware first to *see* the need, but we can be sure that almost **any smartphone or computer display that you get in 2017 is gonna be a `wide-color` one**. -- 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/263#issuecomment-261876846 ----==_mimepart_5832b39f7164c_8173f93e656f130255331 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@igrig= orik Exactly.
Still the poll numbers are not high but we can expect them to go wild nex= t year since most manufactured displays are now wide-color. We can expect= something alike to the Retina/Non-Retina race revolution.

Color-Gamut + Content-Color-Gamut: I think this makes sense.

Yes, this would cover 95% of use cases, and spec-wise it should be sim= ple enough.

So, even for simple cases, this CH spec addition is close to a M= UST for responsive color optimisation. Why? Because wide-gam= ut is one of things those things that cannot even be guessed by User Agent: there is no info about the display on the string. So t= his spec is gonna be the only way to advertise to the server in an automa= ted way.

@color-profile.. I'm still trying to grok. From what I can tell right = now, it accepts a URL to a profile, plus a rendering intent. Do we have s= ome concrete examples of how we expect developers to use this?
Yes, I agree the use cases for color-profile are few, thus I= don't see this one as MUST, however a nice to have one.

The use cases I see for this are minor but:

  1. To override a photo ICC profile (ie. it was wrong in the first place)=
  2. To specify a ICC profile for a photo that had ICC stripped - or didn'= t had one in the first place (ie. it was removed by some "optimisation" t= ool like j= pegoptim or Im= ageOptim)

So yeah I can guess mostly photographer / design websites would make u= se of this one.
Note that, at least CSS Level 4, doesn't need to include the URL for the pro= file since its predefined in two cases: DCI-P3 and Rec= .2020.

Does this prevent us from publishing a new "replacement" draft? How do= we advance these things forward?

I don't know about this WG particular timing interests,
however having Color-Gamut + Content-Color-Gamut in the spec= as soon as possible would give Browser vendors enough time and pave the = way to implement it smoothly.
Be either an addition to CH or a different spec. For consistency<= /strong> it makes sense to be a part of the CH spec though, just like DPR
.

I can understand well why some don't see the urge for it:
= you need to have a wide-color hardware first to see= the need,
but we can be sure that almost any smartphone or computer display= that you get in 2017 is gonna be a wide-color one.=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_5832b39f7164c_8173f93e656f130255331-- From nobody Mon Nov 21 14:04:15 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.402 X-Spam-Level: X-Spam-Status: No, score=-5.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_HI=-5, 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 Date: Mon, 21 Nov 2016 14:04:11 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479765851; bh=wJBSAbQPUa6GedeODgeFITBaHXTapjUwrGNl7ePmchE=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GJF4j65soK7ooDei3Qt+/pKU3ZtFr5UD1HilSzGPnzYxGumEsgiQS/ttdSh53N96x s04qwl2SGKrCfIQwRzKEZFhe/trywYcnyPwHGCJJOrA+nb3WSAWKrHaTw9/AHAvztK l4rf7T0BMq3SCgSeg3fDb+TYttrnHTD9RK6OFCB4= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Don't allow clients to send http and https requests coalesced. (#270) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58336f5b84347_33193ff9b75f51406831c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 22:04:14 -0000 ----==_mimepart_58336f5b84347_33193ff9b75f51406831c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit the pull request is fine by me. I do wonder if we shouldn't make the json a tad more complicated to allow for a reasonable mixed definition in the future. But an unreasonable one is obviously possible :) -- 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/270#issuecomment-262082078 ----==_mimepart_58336f5b84347_33193ff9b75f51406831c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

the pull request is fine by me. I do wonder if we shouldn't make the j= son a tad more complicated to allow for a reasonable mixed definition in = the future. But an unreasonable one is obviously possible :)

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub= , or mute the thread.

= ----==_mimepart_58336f5b84347_33193ff9b75f51406831c8-- From nobody Mon Nov 21 14:15:36 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.097 X-Spam-Level: X-Spam-Status: No, score=-5.097 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Mon, 21 Nov 2016 14:15:33 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479766533; bh=o1oD/7gn2jP6abUQWn2Hrr4EeERh39iuY/03dm3YtII=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rmMOXnw0KdT/Ly/PUF1yUGDIzh4Sg3zRxr+C5ruZZFCFQ+afaj6XeoIfeMsG4BLG8 5eMERFhSblLunKhAwCwde/cpyCgCus8GB8+S1btxY35DaWnRSKM+QI76Bcrn9lZeJp YBg0FSHxozKmgyezkVS1MXA719xRvCKW7RxM7tE0= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Client hints: add support for hinting Display Gamut / Color Profile (#263) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5833720523bf1_18c43f94c20c31401557db"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 22:15:35 -0000 ----==_mimepart_5833720523bf1_18c43f94c20c31401557db Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Just to be clear -- there's no guarantee that the WG will adopt such a document; it depends on getting consensus to adopt, which in turn often depends on implementer interest. That's not to dissuade you from writing a document; however, the next logical step would be to engage with implementers (probably, Chrome) to see if they want to support it, not to create a standard in hopes of getting it implemented. -- 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/263#issuecomment-262084829 ----==_mimepart_5833720523bf1_18c43f94c20c31401557db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Just to be clear -- there's no guarantee that the WG will adopt such a= document; it depends on getting consensus to adopt, which in turn often = depends on implementer interest. That's not to dissuade you from writing = a document; however, the next logical step would be to engage with implem= enters (probably, Chrome) to see if they want to support it, not to creat= e a standard in hopes of getting it implemented.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_5833720523bf1_18c43f94c20c31401557db-- From nobody Tue Nov 22 05:51:49 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.383 X-Spam-Level: X-Spam-Status: No, score=-5.383 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_MSPIKE_H2=-0.001, 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 Date: Tue, 22 Nov 2016 05:51:44 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479822704; bh=+lxxje9A0JZMB4kuK8JXzb7JP3N0RIr9LVPhSLK+hYA=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XihiTvXh+lj1n97+D5iUWfnvag7FdQVrcFxRcVxfZ0UQXwxZSSVKQuVjnyLpPXsLF FLKSWrcjT59K4439srEgV1sUNXYR5PcwGV39LujK3lJI/KylyqJ+/6P5vGhDL6YmQS Axm6F4JjGrqYDV9Tl9nGcOQWYolNzVrflXlKH6JA= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [6265bis] Add double-keying policy example to "Third-party cookies" section (#248) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58344d70492be_68f63fdaaa195130267159b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 13:51:47 -0000 ----==_mimepart_58344d70492be_68f63fdaaa195130267159b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It would be useful to have an attribute in the Set-Cookie header so origins can specify double keying if the user agent supports it. Set-Cookie: {name}={value};doubleKeyed;hhpOnly etc.... -- 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/248#issuecomment-262245328 ----==_mimepart_58344d70492be_68f63fdaaa195130267159b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It would be useful to have an attribute in the Set-Cookie header so or= igins can specify double keying if the user agent supports it.

Set-Cookie: {name}=3D{value};doubleKeyed;hhpOnly etc....

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_58344d70492be_68f63fdaaa195130267159b-- From nobody Tue Nov 22 05:54:04 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 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_HI=-5, 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 Date: Tue, 22 Nov 2016 05:54:01 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479822841; bh=lRs8B9QSN0HuNxAele9+KBteSoE5zz/hiKzgn8IrBqI=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=H4cpCabn/q9km1uXa7WaA5Vm3PGznt5107wJY/+strsQlVHpcvT+BUDuzqluQT0ze A8wgZm5qAEX+CiG6yE3Apa01FKEypWUazt+yXCQOnyMhdXHKntm2C85ga5gkP04Y8i EB/l7D0kFyt6U//tL7KAN9U3VVFdSsIN7flawKHg= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [6265bis] Add double-keying policy example to "Third-party cookies" section (#248) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58344df9439f2_2d1e3ff35a9b1134257942"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 13:54:03 -0000 ----==_mimepart_58344df9439f2_2d1e3ff35a9b1134257942 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Woops Set-Cookie: {name}={value};doubleKeyed;httpOnly;secure etc.... -- 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/248#issuecomment-262245876 ----==_mimepart_58344df9439f2_2d1e3ff35a9b1134257942 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Woops

Set-Cookie: {name}={value};doubleKeyed;httpOnly;secure etc....


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_58344df9439f2_2d1e3ff35a9b1134257942-- From nobody Tue Nov 22 18:21:12 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 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, 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 Date: Tue, 22 Nov 2016 18:21:08 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1479867668; bh=6rMAD7BiXITuRL627Rwcn3gipFXqM5mD+qx+A3Wa/T0=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=anF/mgRDfh4l3NwvLh32qvs38nGvQwvFdHAYPwCcP4fvLH+nxARdY/Kv6FsKdT2O/ qRzftan7e9kZbsxQLjv9ZHvTQQsQyUJrhGZrKcgJp/gpjZr3bcnPSTVaVxbrBNup24 Y6U018JrFHNbD4f/o685Lsa9MUUH7T64ZamOXKQk= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [6265bis] Add double-keying policy example to "Third-party cookies" section (#248) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5834fd1452c51_29ca3fad3bdef134730548"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2016 02:21:11 -0000 ----==_mimepart_5834fd1452c51_29ca3fad3bdef134730548 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Isn't that effectively what SameSite is? http://httpwg.org/http-extensions/draft-ietf-httpbis-cookie-same-site.html -- 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/248#issuecomment-262421206 ----==_mimepart_5834fd1452c51_29ca3fad3bdef134730548 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Isn't that effectively what SameSite is?

http://httpwg.org/http-extensions/draft-ietf-httpbis-cookie-same-site.html


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_5834fd1452c51_29ca3fad3bdef134730548-- From nobody Wed Nov 23 10:30:06 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -1.88 X-Spam-Level: X-Spam-Status: No, score=-1.88 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_H2=-0.001, RP_MATCHES_RCVD=-1.497, 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; d=github.com; h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=S+TjVvR5FeiqgHSpg08AqaJ1s7I=; b=plco4I/19eQOmG3c viAkpqRifASZCwcfKnQVNYUiHB2HAsHVRtmwIxFDGEODxxCenhDlCr3qb+gW6gFc Lj5ZCfT/TZ6MqhgS9JSWyOydmtQRur+T2ua52U7We47A0a8PL3AQcZPZfp85kRwC jnztXDjy4lL8CTcZ6ZObuazIXG8= Date: Wed, 23 Nov 2016 10:29:51 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] consistency in IANA considerations (#241) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5835e01f66de8_9753f922672914012041d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2016 18:30:05 -0000 ----==_mimepart_5835e01f66de8_9753f922672914012041d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #241. -- 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/241#event-870130185 ----==_mimepart_5835e01f66de8_9753f922672914012041d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #241.


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_5835e01f66de8_9753f922672914012041d-- From nobody Wed Nov 23 10:30:48 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 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, RP_MATCHES_RCVD=-1.497, 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; d=github.com; h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Ht9i4wyXSEVAeFCODJE7H27rG4U=; b=ruEpyC3T2kZYY3X1 L///Dghs6Rlg/RH11zAOC6FDGAnW9YMtFH3aohpit7BhQdrPAj3mPvD5f+EsiFDH M/jDZeShuJVwaufjfb95BnZt3dvlEluCWy7Go3/+klU49fGMvL0WU9B3mqRmqPrC PpU1zv73EbPlQ0BFGaCeMkxO/II= Date: Wed, 23 Nov 2016 10:30:44 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] update reference to CR-css-values-3 (#239) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5835e0542def5_54fa3ff54071b1306786a6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2016 18:30:47 -0000 ----==_mimepart_5835e0542def5_54fa3ff54071b1306786a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @reschke I'm inclined to close this as wontfix.. since this breaks the build and I'm not sure how to work around 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/239#issuecomment-262595654 ----==_mimepart_5835e0542def5_54fa3ff54071b1306786a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@reschke I'm inclined to close this as wontfix.. since this breaks the build and I'm not sure how to work around 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_5835e0542def5_54fa3ff54071b1306786a6-- From nobody Thu Nov 24 11:36:11 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.001 X-Spam-Level: X-Spam-Status: No, score=-7.001 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 Date: Thu, 24 Nov 2016 11:36:07 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1480016167; bh=2Q412WdD55HdrckRwOApy9U9lBTTL8UpLujmvou+AbQ=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AkvWMvYfu2XsNWoVLLOsxxc/A7V54Xhg4Y1mXXbQKfgqP/GtR0psZy3GS7eFzcx3J u5kQMR8R4B+ketJygfsztOR1lixXlCVVn2rTy8TcnNVjqyHN0s+5dkGoJ2uj35EFgU 4+lOTAZPtQqOvzVDPO6AQSrcOQNv1ENV/lIVGl1k= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] [6265bis] Add double-keying policy example to "Third-party cookies" section (#248) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58374127c348d_2f303fc5d9807134160774"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 19:36:10 -0000 ----==_mimepart_58374127c348d_2f303fc5d9807134160774 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually, after thinking about it, it's not the same. The SameSite attribute says only send this cookie in a request when it is same origin as the top-level browsing context - effectively the server is asking for a "third-party cookie block" for this cookie. I was thinking of the doubleKeyed cookie idea where there is a separate cookie store for the parent contexts, which would allow a lot of functionality but mitigate cross-origin tracking. If this supported as a user option in the UA why not extend it as a server option also allowing sites to help protect user's privacy. Maybe there is a halfway house where you could constrain sending back cookies to same context i.e. the chain of descendent origins is the same as when the cookie was stored toplevel.com->widgit.com->cookiedwidgit.com is not "same context" as other-toplevel.com->cookiedwidgit.com etc. -- 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/248#issuecomment-262836047 ----==_mimepart_58374127c348d_2f303fc5d9807134160774 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Actually, after thinking about it, it's not the same.

The SameSite attribute says only send this cookie in a request when it= is same origin as the top-level browsing context - effectively the serve= r is asking for a "third-party cookie block" for this cookie.

I was thinking of the doubleKeyed cookie idea where there is a separat= e cookie store for the parent contexts, which would allow a lot of functi= onality but mitigate cross-origin tracking. If this supported as a user o= ption in the UA why not extend it as a server option also allowing sites = to help protect user's privacy.

Maybe there is a halfway house where you could constrain sending back = cookies to same context i.e. the chain of descendent origins is the same = as when the cookie was stored

toplevel.com->widgit.com->cookiedwidgit.com
is not "same context" as
other-toplevel.com->cookiedwidgit.com etc.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

=
= ----==_mimepart_58374127c348d_2f303fc5d9807134160774-- From nobody Thu Nov 24 17:16:12 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, 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; 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=e9t/3/FY/X/sESmnpi994DxGgkk=; b=NarwphYAl8r33awb BQQv5YR1UnZmzOKzG47VL7jbOj7pvtf/OdfsknjqHZxxOm05lFLwm7DVIZaJo9iw DWfy+jc1ovxyH0RTtlLtAzGhqooFdsi/0LbBHb7nf6lv6dvxAPHNANdKPfJjWTVd s7ygUKxOUK10Xd+G+FlGAvePiqQ= Date: Thu, 24 Nov 2016 17:16:04 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Remove Crypto-Key header field (#273) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_583790d4e8e5c_3cda3ff1bc9011342823d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Push Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2016 01:16:10 -0000 ----==_mimepart_583790d4e8e5c_3cda3ff1bc9011342823d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 31d7838 address ekr's review comments -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/273/files/d7547e1bff2d23e93e9402d186506c432555b0f8..31d78384ee237cf86023c73f3e74674fc896097c ----==_mimepart_583790d4e8e5c_3cda3ff1bc9011342823d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 31d7838 address ekr's review comments


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

----==_mimepart_583790d4e8e5c_3cda3ff1bc9011342823d0-- From nobody Fri Nov 25 11:39:40 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -1.952 X-Spam-Level: X-Spam-Status: No, score=-1.952 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_H2=-0.001, RP_MATCHES_RCVD=-1.497, 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; d=github.com; h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=p9DWkbNdCncuef8iDCMzJAbncQM=; b=J55LzyifMwaN97FN LvDdIQlcMqqUDyc58qJxHrjto4LfR7ccZtr5jhinzum9QODZDpMFLm9M9BOEshI3 8eZuXt2VAQChsOO7XDMZwbAd0YI0kp928C59IR5LrX545S8I3qsSXoIyO8Faosu8 B31KscOdPZ31AP6VT/kLCLyzzDA= Date: Fri, 25 Nov 2016 11:39:36 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Remove Crypto-Key header field (#273) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_583893783e51c_218013fb4a644513416557f9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2016 19:39:39 -0000 ----==_mimepart_583893783e51c_218013fb4a644513416557f9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This looks OK, except for whatever build error you have -- 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/273#issuecomment-263015035 ----==_mimepart_583893783e51c_218013fb4a644513416557f9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This looks OK, except for whatever build error you have


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_583893783e51c_218013fb4a644513416557f9-- From nobody Fri Nov 25 11:40:51 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.798 X-Spam-Level: X-Spam-Status: No, score=-5.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_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.497, 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; d=github.com; h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=uA3xEQB/zkyuElnMvpnpxtDSMiQ=; b=m3zVMh91Oxg7GEYg cAhbUJYiG5T6Cjk9ijZ13MZv+KixI6QsPCrbu63JI8g2tF6yGd7JTe80N8HasBhA pRIQaTpXrsodC+EwzMrPNpZTnhzcgDRrVtSTPqn/OC0ikFQW/3XNtKeQvyUN2555 MKgSGQju4b8zJnG1ombBKN/7af8= Date: Fri, 25 Nov 2016 11:40:47 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Advice on padding strategy (#272) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_583893bf32e52_59c03fb4a6445134785f5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2016 19:40:50 -0000 ----==_mimepart_583893bf32e52_59c03fb4a6445134785f5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr requested changes on this pull request. > @@ -535,6 +535,14 @@ provides. Alternatively, splitting up content into segments and storing the separately might reduce exposure. HTTP/2 {{?RFC7540}} combined with TLS {{?RFC5246}} might be used to hide the size of individual messages. +Developing a padding strategy is difficult. A good padding strategy can depend +on context. Common strategies include padding to a small set of fixed lengths, +padding to multiples of a values, or padding to powers of 2. Even a good +strategy can still cause size information to leak if processing activity of a +recipient can be observed. This is especially good if the trailing records of +a message contain only padding. To minimize this information, non-padding data I am guessing "good " is not the word you want here. Perhaps "true"? > @@ -535,6 +535,14 @@ provides. Alternatively, splitting up content into segments and storing the separately might reduce exposure. HTTP/2 {{?RFC7540}} combined with TLS {{?RFC5246}} might be used to hide the size of individual messages. +Developing a padding strategy is difficult. A good padding strategy can depend +on context. Common strategies include padding to a small set of fixed lengths, +padding to multiples of a values, or padding to powers of 2. Even a good +strategy can still cause size information to leak if processing activity of a +recipient can be observed. This is especially good if the trailing records of +a message contain only padding. To minimize this information, non-padding data +can be evenly distributed between records. Perhaps something slightly stronger like "should" or "MAY WISH TO" -- 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/272#pullrequestreview-10198065 ----==_mimepart_583893bf32e52_59c03fb4a6445134785f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr requested changes on this pull request.


In draft-ietf-httpbis-encryption-encoding.md:

> @@ -535,6 +535,14 @@ provides.  Alternatively, splitting up content into segments and storing the
 separately might reduce exposure. HTTP/2 {{?RFC7540}} combined with TLS
 {{?RFC5246}} might be used to hide the size of individual messages.
 
+Developing a padding strategy is difficult.  A good padding strategy can depend
+on context.  Common strategies include padding to a small set of fixed lengths,
+padding to multiples of a values, or padding to powers of 2.  Even a good
+strategy can still cause size information to leak if processing activity of a
+recipient can be observed.  This is especially good if the trailing records of
+a message contain only padding.  To minimize this information, non-padding data

I am guessing "good " is not the word you want here. Perhaps "true"?


In draft-ietf-httpbis-encryption-encoding.md:

> @@ -535,6 +535,14 @@ provides.  Alternatively, splitting up content into segments and storing the
 separately might reduce exposure. HTTP/2 {{?RFC7540}} combined with TLS
 {{?RFC5246}} might be used to hide the size of individual messages.
 
+Developing a padding strategy is difficult.  A good padding strategy can depend
+on context.  Common strategies include padding to a small set of fixed lengths,
+padding to multiples of a values, or padding to powers of 2.  Even a good
+strategy can still cause size information to leak if processing activity of a
+recipient can be observed.  This is especially good if the trailing records of
+a message contain only padding.  To minimize this information, non-padding data
+can be evenly distributed between records.

Perhaps something slightly stronger like "should" or "MAY WISH TO"


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_583893bf32e52_59c03fb4a6445134785f5-- From nobody Wed Nov 30 17:21:13 2016 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -6.502 X-Spam-Level: X-Spam-Status: No, score=-6.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, 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 Date: Wed, 30 Nov 2016 17:21:06 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1480555266; bh=moUaWjjw0u3q8pyYRDXdxXsIjBaR0Id9kFhpOsu3Bi0=; h=From:To:Subject:From; b=E+EDUra8p6mygZgQQaidDzZvJRIZ1IqhhbHeqP5cVMojAviiJ/Se8q7VQKgBJoAT+ Wm8HJTd7R1Lvs00E0RGp7yaUidyZTfD6RXlqiuGk6X0iQUz7BTS9oORql3edMMtExU 83Qg3h6eH/iwgIEdS4pfggLdD7vKH7zKSN3BrI4A= To: HTTP Working Group issues account , HTTP Working Group issues account Subject: [GitHub] Your password has changed Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2016 01:21:09 -0000 Hello httpwg-issues, We wanted to let you know that your GitHub password was changed. If you did not perform this action, you can recover access by entering httpwg-issues@mnot.net into the form at https://github.com/password_reset. To see this and other security events for your account, visit https://github.com/settings/security. If you run into problems, please contact support by visiting https://github.com/contact or replying to this email. Please do not reply to this email with your password. We will never ask for your password, and we strongly discourage you from sharing it with anyone.