From nobody Wed Mar 1 19:58:33 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.021 X-Spam-Level: X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Llh4MKctrMTilJYeG7eFCzSSC4M=; b=dR8CI0o9O6+uyBOL uLdwVlkzoXZ+qVux/KBaPixOf5XPIUzm9rgrZCRfzpMzTG4Zp8iSsVMxHOA+rWxk uBlvJ3c/N6QEjBnSIqLXmkjSGPAviw5GBcPlRhpa/pKENx4u4C+TIppL8yixAFpd NgShmIvRur28WAYE+Np/aK4fYCg= Date: Wed, 01 Mar 2017 19:58:08 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Allow servers to specify max-age in the client hints header (#306) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58b798508e009_322a3f8a9d635c385143c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 02 Mar 2017 03:58:31 -0000 ----==_mimepart_58b798508e009_322a3f8a9d635c385143c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Making this a new directive in `Accept-CH` is a bit problematic, since that header field is defined as a list of header field names. It's technically possible, you just would get into situations where you have to switch your parser based upon the format of the directive, and reserve keywords that now can't be used as headers (and thus, have to register them as headers -- see `Connection`). You *could* do it as a new header, though -- e.g., `Accept-CH-Lifetime: 3600` or similar. That has the additional benefit that it can be introduced later if there's need for it, and we decide not to do it now. @igrigorik, what do you think? Keeping in mind that we're doing this spec primarily to document what one (albeit big) implementation is doing, hence its Experimental status, is Chrome interested in implementing this? If not, I'd suggest we close this issue; if it's interesting in the future, it's relatively easy to add that new header. All of that said -- I *do* think there's a bit of an issue remaining with how the applicability of `Accept-CH` is scoped. I'll open a separate issue for 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/306#issuecomment-283549512 ----==_mimepart_58b798508e009_322a3f8a9d635c385143c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Making this a new directive in Accept-CH is a bit problemat= ic, since that header field is defined as a list of header field names. It'= s technically possible, you just would get into situations where you have t= o switch your parser based upon the format of the directive, and reserve ke= ywords that now can't be used as headers (and thus, have to register them a= s headers -- see Connection).

You could do it as a new header, though -- e.g.,

Accept-CH-Lifetime: 3600

or similar.

That has the additional benefit that it can be introduced later if there= 's need for it, and we decide not to do it now.

@igrigor= ik, what do you think? Keeping in mind that we're doing this spec prima= rily to document what one (albeit big) implementation is doing, hence its E= xperimental status, is Chrome interested in implementing this?

If not, I'd suggest we close this issue; if it's interesting in the futu= re, it's relatively easy to add that new header.

All of that said -- I do think there's a bit of an issue remain= ing with how the applicability of Accept-CH is scoped. I'll op= en a separate issue for that.

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

= ----==_mimepart_58b798508e009_322a3f8a9d635c385143c-- From nobody Wed Mar 1 20:09:46 2017 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: Wed, 01 Mar 2017 20:09:41 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488427781; bh=XuXHRNBVnwuyOANHOLatjE3EkJ5JiarcuVCtmj9Okh4=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=karbTHwu/sHbHPAmRZTppPAoHNQD06Q3mtbSt6RiyPx+LDW3COtYxCFEUDo7rMMro fdSnmtey1K3VzfoxM8TXQ4Ui4aBDayAlUuFkVhBX0oNCgBpj3xaDPlTQwu1JgmFjf9 eT4tuPkSuVV3E8XfTxATmaNosXxo6ksmX/gmfDgk= To: httpwg/http-extensions Subject: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58b79b05da502_721e3ff50d4a9c2c1923a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 02 Mar 2017 04:09:44 -0000 ----==_mimepart_58b79b05da502_721e3ff50d4a9c2c1923a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The `Accept-CH` response header is defined as: > When a client receives Accept-CH, or if it is capable of processing the HTML response and finds an equivalent HTML meta element, it can treat it as a signal that the server is interested in receiving the Client-Hint header fields that match the advertised field-values; subsequent requests initiated to the same server and, optionally any subresource requests initiated as a result of processing the response from the server that includes the Accept-CH opt-in, can include the Client-Hint header fields that match the advertised field-values. > > For example, based on Accept-CH example above, a user agent could append DPR, Width, Viewport-Width, and Downlink header fields to all subresource requests initiated by the page constructed from the response. Alternatively, a client can treat advertised support as a persistent origin preference and append same header fields on all future requests initiated to and by the resources associated with that origin. "All future requests" is a long time indeed. While of course the client isn't going to literally do that (eventually it'll be garbage collected, or the user will reset state, or the machine will be recycled), from a server-side perspective, it'd be nice to have *some* level of control over how bloated your requests get. Additionally, having `Accept-CH` possibly indicate that future references *to* **and** *from* this origin seems like a pretty broad brush to be painting with. While Chrome might make some reasonable decisions about tradeoffs here (and probably needs some wiggle room), if this ever does get implemented elsewhere, this broadness and freedom is a recipe for bad interop and worse server-side headaches. So, can we nail this down at all? The most conservative approach is: "Send CH headers on subrequests generated by this content, please." However, the above also says "subsequent requests initiated to the same server" in the primary spot; the case above is relegated to "optionally." Personally, my preference would be to drop "subsequent requests initiated to the same server and, optionally" and the corresponding text in the example below it. The primary use case for CH as I understand it is serving appropriate subresources, NOT dynamically modifying HTML, so that should do the trick. Am I missing something, @igrigorik? Regardless of that, "server" is used very loosely above; I think you mean "origin", right? And "can" should probably be "MAY". CC @yoavweiss -- 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/307 ----==_mimepart_58b79b05da502_721e3ff50d4a9c2c1923a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The Accept-CH response header is defined as:

When a client receives Accept-CH, or if it is capable of processing the HTML response and finds an equivalent HTML meta element, it can treat it as a signal that the server is interested in receiving the Client-Hint header fields that match the advertised field-values; subsequent requests initiated to the same server and, optionally any subresource requests initiated as a result of processing the response from the server that includes the Accept-CH opt-in, can include the Client-Hint header fields that match the advertised field-values.

For example, based on Accept-CH example above, a user agent could append DPR, Width, Viewport-Width, and Downlink header fields to all subresource requests initiated by the page constructed from the response. Alternatively, a client can treat advertised support as a persistent origin preference and append same header fields on all future requests initiated to and by the resources associated with that origin.

"All future requests" is a long time indeed. While of course the client isn't going to literally do that (eventually it'll be garbage collected, or the user will reset state, or the machine will be recycled), from a server-side perspective, it'd be nice to have some level of control over how bloated your requests get.

Additionally, having Accept-CH possibly indicate that future references to and from this origin seems like a pretty broad brush to be painting with. While Chrome might make some reasonable decisions about tradeoffs here (and probably needs some wiggle room), if this ever does get implemented elsewhere, this broadness and freedom is a recipe for bad interop and worse server-side headaches.

So, can we nail this down at all?

The most conservative approach is:

"Send CH headers on subrequests generated by this content, please."

However, the above also says "subsequent requests initiated to the same server" in the primary spot; the case above is relegated to "optionally."

Personally, my preference would be to drop "subsequent requests initiated to the same server and, optionally" and the corresponding text in the example below it. The primary use case for CH as I understand it is serving appropriate subresources, NOT dynamically modifying HTML, so that should do the trick.

Am I missing something, @igrigorik?

Regardless of that, "server" is used very loosely above; I think you mean "origin", right? And "can" should probably be "MAY".

CC @yoavweiss

—
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_58b79b05da502_721e3ff50d4a9c2c1923a-- From nobody Wed Mar 1 20:37:36 2017 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: Wed, 01 Mar 2017 20:37:32 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488429452; bh=j3UOOjFVokiN4VFdBPjHCnfi2j/JmfOHD5yq4fjoBLI=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=buCLAyb+pFMvl/AI0MwCfVE25E81lIYQOpnkx3NvxM5P0BeMWTzEqyBGhzm/norCy 1YM+xhI6ImSJ1lnN+0EkOzlfwOWLyc+eU/eHCuq/K51Z9yHBfJ7dUaZLoW3F0Aos+s tWcCvCqsAt4y5tVeO7gROEale6fbX+BjlTr604+4= To: httpwg/http-extensions Subject: [httpwg/http-extensions] CH editorial (#308) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58b7a18ccf4ac_63543f80fa0b9c3470122"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 02 Mar 2017 04:37:35 -0000 ----==_mimepart_58b7a18ccf4ac_63543f80fa0b9c3470122 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Taking a run through the spec before we sent it upstairs, a few suggestio= ns -- * In the abstract, `s/clients/user agents/g` (proxies aren't going to gen= erate them, and shouldn't try) * Introduction - you might get complaints about the "UA" abbreviation; sp= ell out as `User-Agent`? * Section 2 - "Each one conveys a list of client preferences" -- are they= all list-based? * 2.2 - "Servers respond with an optimized response based on one or more = received hints from the client." -- awkward; suggest: "When presented wit= h a request that contains one or more client hint headers, servers can op= timise the response based upon the information in them." * 2.2 - "used hint" --> "hint used" * 2.2 - "emit" --> "generate" (has meaning in HTTP) * 2.2 "confirm the property of the response, such that the client can adj= ust its processing" --> "convey related values to aid client processing" * Sections 3-7: These feel like they should all be in their own subsectio= n. Also, would you consider changing "client hint" in each title to "head= er field"? That will emphasise that they're just regular headers, not som= e new class of thing (I continue to be concerned that people think these = are magical because they are called Client Hints). * Section 7: "New token and extension token values can only be defined by= revisions of this specification" --> "New token and extension token valu= es can be defined by updates to this specification." (IETF-specific word= ing) * Section 9: "Client Hints defined in this specification do not expose ne= w information about the user=E2=80=99s environment beyond what is already= available to, and can be communicated by, the application at runtime via= JavaScript and CSS." --> "The request header fields defined in this spec= ification expose information that is already available to Web application= s in the browser runtime itself (e.g., using JavaScript and CSS)." * Section 9: "However, implementors should consider the privacy implicati= ons of various methods to enable delivery of Client Hints - see =E2=80=9C= Sending Client Hints=E2=80=9D section." --> "However, servers that gather= this information through such mechanisms are typically observable (e.g.,= you can see that they're using JavaScript to gather it), whereas servers= ' use of the header fields introduced by this specification is not observ= able. Section 2.1 discusses potential mitigations." = * Section 9: "might reduce such fingerprinting risks" --> "can help mitig= ate the risk of such fingerprinting." * Section 9: "The implementers can..." --> "Implementers ought to..." * Section 9: "...advertised: require..." --> "...advertised. For example,= they could require..." -- = 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/308= ----==_mimepart_58b7a18ccf4ac_63543f80fa0b9c3470122 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Taking a run through the spec before we sent it upstairs, a few sugges= tions --

  • In the abstract, s/clients/user agents/g (proxies aren't= going to generate them, and shouldn't try)
  • Introduction - you might get complaints about the "UA" abbreviation; = spell out as User-Agent?
  • Section 2 - "Each one conveys a list of client preferences" -- are th= ey all list-based?
  • 2.2 - "Servers respond with an optimized response based on one or mor= e received hints from the client." -- awkward; suggest: "When presented w= ith a request that contains one or more client hint headers, servers can = optimise the response based upon the information in them."
  • 2.2 - "used hint" --> "hint used"
  • 2.2 - "emit" --> "generate" (has meaning in HTTP)
  • 2.2 "confirm the property of the response, such that the client can a= djust its processing" --> "convey related values to aid client process= ing"
  • Sections 3-7: These feel like they should all be in their own subsect= ion. Also, would you consider changing "client hint" in each title to "he= ader field"? That will emphasise that they're just regular headers, not s= ome new class of thing (I continue to be concerned that people think thes= e are magical because they are called Client Hints).
  • Section 7: "New token and extension token values can only be defined = by revisions of this specification" --> "New token and extension token= values can be defined by updates to this specification." (IETF-specific= wording)
  • Section 9: "Client Hints defined in this specification do not expose = new information about the user=E2=80=99s environment beyond what is alrea= dy available to, and can be communicated by, the application at runtime v= ia JavaScript and CSS." --> "The request header fields defined in this= specification expose information that is already available to Web applic= ations in the browser runtime itself (e.g., using JavaScript and CSS)."
  • Section 9: "However, implementors should consider the privacy implica= tions of various methods to enable delivery of Client Hints - see =E2=80=9C= Sending Client Hints=E2=80=9D section." --> "However, servers that gat= her this information through such mechanisms are typically observable (e.= g., you can see that they're using JavaScript to gather it), whereas serv= ers' use of the header fields introduced by this specification is not obs= ervable. Section 2.1 discusses potential mitigations."
  • Section 9: "might reduce such fingerprinting risks" --> "can help = mitigate the risk of such fingerprinting."
  • Section 9: "The implementers can..." --> "Implementers ought to...= "
  • Section 9: "...advertised: require..." --> "...advertised. For exa= mple, they could require..."

&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.3D""

= ----==_mimepart_58b7a18ccf4ac_63543f80fa0b9c3470122-- From nobody Wed Mar 1 20:37:48 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.456 X-Spam-Level: X-Spam-Status: No, score=-0.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Gx7NCOErVSOeJXe0doN1Z/FPctw=; b=jnpThvZHPctDY50x tEtuT9RcRGj1nk3D2l9+My9hH8EdBf5D1pPyjQjGMEPdKQ8OnpFhne77fjqmdSle t19HONI8nrmG27pkd92O+T4GjxFF3dydm/m4oAtpWJtV0FnZMfO9V32GgSbT1gC9 G2oQdvW79YlxLyWmpugdRZBBPrc= Date: Wed, 01 Mar 2017 20:37:38 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] CH editorial (#308) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58b7a1926e6d9_71673ff946e31c3036930"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 02 Mar 2017 04:37:40 -0000 ----==_mimepart_58b7a1926e6d9_71673ff946e31c3036930 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ping @igrigorik -- 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/308#issuecomment-283554170 ----==_mimepart_58b7a1926e6d9_71673ff946e31c3036930 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

ping @igrigorik

—
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_58b7a1926e6d9_71673ff946e31c3036930-- From nobody Thu Mar 2 20:05:36 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Si3kb336Tde3Uqx2IrWZxUeZGwU=; b=mVVXtIjJi5kOsweC TDBoBo6TLmlHHWK9y8yC9rM7NhUOqnFMlH5oSIBB9kYxqbQGyBcwGMxXp4wvg2n7 Eqqjr9HNWUX0xTQxMXkWE23ZKcm+CyIt2RQ7hvdx3YRJcw7r2tNxJGprD5xHJG51 35hwY8D/rX+5we+oDXQlNM13gL4= Date: Thu, 02 Mar 2017 20:05:32 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] 5987bis writeup (#271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58b8eb8cce321_55be3f96b7e97c3489611"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 03 Mar 2017 04:05:35 -0000 ----==_mimepart_58b8eb8cce321_55be3f96b7e97c3489611 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #271. -- 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/271#event-984821894 ----==_mimepart_58b8eb8cce321_55be3f96b7e97c3489611 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #271.

—
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_58b8eb8cce321_55be3f96b7e97c3489611-- From nobody Thu Mar 2 20:09:33 2017 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Thu, 02 Mar 2017 20:09:30 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488514170; bh=6dZXVKeMoF6T6ZSdc0K7glaCtEoSkIf1GBMtF9eYGq4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZBO7yU2A+/MfITy0CgMGaqZF4PT3Ki9iWdv9KQh9xZt6BpwURahG+ymWC4gBctcae H0PAgB07g/tMQHYZY/Pd7eF0fe3V15XNCrekUVfzHqb7go+3lXiMdEi2TVTh73H+IU L+3s1JQeBtwyEKH3wAltehyhYH7awCSG2WB5BEJU= 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_58b8ec7aa6ce6_642b3f9b3e60dc2c568ba"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 03 Mar 2017 04:09:33 -0000 ----==_mimepart_58b8ec7aa6ce6_642b3f9b3e60dc2c568ba Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #267. -- 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#event-984824209 ----==_mimepart_58b8ec7aa6ce6_642b3f9b3e60dc2c568ba Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #267.

—
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_58b8ec7aa6ce6_642b3f9b3e60dc2c568ba-- From nobody Fri Mar 3 17:13:34 2017 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, 03 Mar 2017 17:13:30 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488590010; bh=1WrX6uNGkhNYf9VftU7Jm+LzZB8U/JxZipCLPqCL5qY=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pJtr8P7yto2ZBBEGV/IBaQwujJyowYZgq9aWCIRRJfhysUmK1y0a0HaK+qOfpaULA JJz2EUqWSPGNeXsC4gtCja8RjYF7RlazOSssHaLnGOR/f5NXUEr9Ph8oGkjnK6ki+z V5P7IdiPGBlykxsGA94OKTmxz/rQqmTlTqu10emA= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58ba14ba5d0df_a003ff9a13abc386101f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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: Sat, 04 Mar 2017 01:13:33 -0000 ----==_mimepart_58ba14ba5d0df_a003ff9a13abc386101f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > The primary use case for CH as I understand it is serving appropriate subresources, NOT dynamically modifying HTML, so that should do the trick. With the benefit of few years of experience, absence of hints on the initial request has proven to be a major limitation that prevented wider adoption. In practice, many of the most critical decisions about page format are made when the HTML is generated -- e.g. whether you should serve "light" version of the page, picking resource density, ..., and feature-detecting support for CH to begin with. In short, we do need to allow hints on navigation responses. > "Send CH headers on subrequests generated by this content, please." I think that's a reasonable definition for `Accept-CH`, iff we also combine it with `Accept-CH-Lifetime` proposed in https://github.com/httpwg/http-extensions/issues/306 to cover the case for initial navigation. Concretely, the proposal here would be: - Scope down `Accept-CH` to "subsequent requests generated by this content" - Define `Accept-CH-Lifetime` to allow opt-in to be remembered for specified period of time. - When this is present, opt-in applies for all content that belongs to the origin. -- 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/307#issuecomment-284113236 ----==_mimepart_58ba14ba5d0df_a003ff9a13abc386101f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The primary use case for CH as I understand it is serving appropriate = subresources, NOT dynamically modifying HTML, so that should do the trick= .

With the benefit of few years of experience, absence of hints on the i= nitial request has proven to be a major limitation that prevented wider a= doption. In practice, many of the most critical decisions about page form= at are made when the HTML is generated -- e.g. whether you should serve "= light" version of the page, picking resource density, ..., and feature-de= tecting support for CH to begin with. In short, we do need to allow hints= on navigation responses.

"Send CH headers on subrequests generated by this content, please."

I think that's a reasonable definition for Accept-CH, iff= we also combine it with Accept-CH-Lifetime proposed in #306 to c= over the case for initial navigation. Concretely, the proposal here would= be:

  • Scope down Accept-CH to "subsequent requests generated b= y this content"
  • Define Accept-CH-Lifetime to allow opt-in to be remember= ed for specified period of time.
    • When this is present, opt-in applies for all content that belongs to = the origin.

&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_58ba14ba5d0df_a003ff9a13abc386101f-- From nobody Fri Mar 3 17:15:12 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.021 X-Spam-Level: X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=c7xGcFVWpg2rSqYg1MjFDLufupI=; b=ew2S3mFbnFBbuhgr yVYCATwgUxbOxIITMSgEAI04GO4hyyj0erIVRWfztjLWxK2ApzglFVeB0bbP3e43 +ViUU/gvC6Nzals5rXM88nyvkxFgu1/Bx+tJ7X3qNHt3JNuGiFcbfNOyh+ZgXlGm y2Sr65LzTev23Pgc7Hngdc4C0+s= Date: Fri, 03 Mar 2017 17:15:02 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Allow servers to specify max-age in the client hints header (#306) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58ba1516b4e9a_62c83fb33cc67c3814768b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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: Sat, 04 Mar 2017 01:15:11 -0000 ----==_mimepart_58ba1516b4e9a_62c83fb33cc67c3814768b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable My long-term hope is that this entire discussion is a no-op and origin poli= cy will give us the right primitives (see https://github.com/WICG/origin-po= licy/issues/12) to solve this in a generic way for all opt-in behaviors. Th= at said, there *is* interest in implementing this in Chrome=E2=80=94 tarunb= an@ is driving that work=E2=80=94and we need an alternative mechanism until= OP is a thing. I agree with Mark that `Accept-CH-Lifetime` is better solution. The seconda= ry benefit, as I see it, is that we can also no-op it later once Origin Pol= icy becomes available. More details in https://github.com/httpwg/http-exten= sions/issues/307#issuecomment-284113236. --=20 You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/306#issuecomment-284113395= ----==_mimepart_58ba1516b4e9a_62c83fb33cc67c3814768b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

My long-term hope is that this entire discussion is a no-op and origin p= olicy will give us the right primitives (see WICG/origin-policy#12) to solve this in a generic w= ay for all opt-in behaviors. That said, there is interest in imple= menting this in Chrome=E2=80=94 tarunban@ is driving that work=E2=80=94and = we need an alternative mechanism until OP is a thing.

I agree with Mark that Accept-CH-Lifetime is better solutio= n. The secondary benefit, as I see it, is that we can also no-op it later o= nce Origin Policy becomes available. More details in #307 (comment).

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

= ----==_mimepart_58ba1516b4e9a_62c83fb33cc67c3814768b-- From nobody Fri Mar 3 17:20:27 2017 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_IMAGE_ONLY_32=0.001, 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, 03 Mar 2017 17:20:24 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488590424; bh=0qiePKekRlFcM1T4tgngCH8fPZjapaN6TqdxhXmnXS4=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=FetLP5AKZ0r9SajCaZXo9XSsADWK0xifgYxe8HJEsQ6NYctnLZqc1j2KHDuaWNE9l qJFrBMk2KkM3NRn+Nff1GRJj50y3vs0+d9rj7Igg74BFE6YHCXH57qsXnD+IR+07C9 tdUyFhfPNkFhe5KjyVKG4APNwCRSAd8m4wzPysDI= To: httpwg/http-extensions Subject: [httpwg/http-extensions] Editorial cleanup and improvements (#309) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58ba1658e596_77d13f8412cafc302067bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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: Sat, 04 Mar 2017 01:20:26 -0000 ----==_mimepart_58ba1658e596_77d13f8412cafc302067bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closes https://github.com/httpwg/http-extensions/issues/308. You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/309 -- Commit Summary -- * Editorial cleanup and improvements -- File Changes -- M draft-ietf-httpbis-client-hints.md (32) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/309.patch https://github.com/httpwg/http-extensions/pull/309.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/309 ----==_mimepart_58ba1658e596_77d13f8412cafc302067bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closes #308.

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

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

Commit Summary

  • Editorial cleanup and improvements

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_58ba1658e596_77d13f8412cafc302067bf-- From nobody Fri Mar 3 17:20:46 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=fhfLkZkSuGG54zjXJx8LWl2UuZ8=; b=IzMkSuq1Rc2/G3YC hnQOhn2zp4okZWzPRILsFvV+cuda+fstTd+VYoi2sx3YWX5gD5dg7X7dlSVfCBMW kVTjjhvjvByZ3MmW/lApVtzZAVezBGxRuGnYJaj1JmhWbHxrOgVgoOUXNWutJ1JX 2QMQ6EIdEFV33M1/NjPtBWJhuUs= Date: Fri, 03 Mar 2017 17:20:42 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] CH editorial (#308) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58ba166af22ec_77ed3f8412cafc30146733"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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: Sat, 04 Mar 2017 01:20:46 -0000 ----==_mimepart_58ba166af22ec_77ed3f8412cafc30146733 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks for the thorough review Mark! > In the abstract, s/clients/user agents/g (proxies aren't going to generate them, and shouldn't try) I'm building an iOS/Android app and want to use CH.. "user agent" doesn't seem to fit? I'd prefer to keep it inclusive. > Introduction - you might get complaints about the "UA" abbreviation; spell out as User-Agent? We do define it at the start: "User-Agent (UA; Section 5.5.3 of {{RFC7231}})" -- Opened PR to address the rest: https://github.com/httpwg/http-extensions/pull/309 -- 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/308#issuecomment-284114072 ----==_mimepart_58ba166af22ec_77ed3f8412cafc30146733 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thanks for the thorough review Mark!

In the abstract, s/clients/user agents/g (proxies aren't going to genera= te them, and shouldn't try)

I'm building an iOS/Android app and want to use CH.. "user agent" doesn'= t seem to fit? I'd prefer to keep it inclusive.

Introduction - you might get complaints about the "UA" abbreviation; spe= ll out as User-Agent?

We do define it at the start: "User-Agent (UA; Section 5.5.3 of {{RFC723= 1}})"

--

Opened PR to address the rest: #309

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

= ----==_mimepart_58ba166af22ec_77ed3f8412cafc30146733-- From nobody Sat Mar 4 03:50:35 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.002 X-Spam-Level: X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=vpizxnF8kcNZVOGCre+Bqu65x+U=; b=Z6ckP/EumgW5JPhw fVaTSvQ/drytNGbaTEEI2XHmnpm1Ft2beG65JaxxtHcvqW4cRIN8/l/0kirTADEK 4ou/c+P80POeNPJqUA7XS+5nAqwSCMuyX2m4Aty3hehj0ScKZTAfeCHmXnppduo/ kOs55ltExWRlda8jZZRTmN6pVDU= Date: Sat, 04 Mar 2017 03:50:31 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58baaa0778cc1_a043f86e6975c3c36299d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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: Sat, 04 Mar 2017 11:50:34 -0000 ----==_mimepart_58baaa0778cc1_a043f86e6975c3c36299d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit DNT has a mechanism for determining if the DNT:0 header sent to subresources, a JS API for specifying "site-specific" consent. This also can specify lifetime by having an "expires" or "maxAge" property in the parameter dictionary for the call. The TPWG has discussed using cookies as a more generic method, but the SOP gets in the way (you cannot limit the state to a top level context). The Accept-CH header is similarly determining stateful site-specific behaviour for subresources, perhaps this points to a generalised solution? Especially as there are privacy/user control issues in common? I am thinking about a well-known cookie prefix (as proposed for RFC6265bis) that would cause the cookie to be sent to subresources in the cookie header, but only within the context of the parent that placed it. The existence of particular forms of this well-known cookie could then determine UA behaviour (such as sending Client Hints to subresources). Implementation would be simpler because the expiry procedures are already in place. A further advantage would then be that the state is automatically contained in the UAs cookie store, accessible to existing privacy oriented UA UIs and extensions, increasing transparency. For example: Set-Cookie: __SRAccept-CH=DPR;expires=Sat, 05 Mar 2017 00:00:00 GMT -- 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/307#issuecomment-284146721 ----==_mimepart_58baaa0778cc1_a043f86e6975c3c36299d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

DNT has a mechanism for determining if the DNT:0 header sent to subresou= rces, a JS API for specifying "site-specific" consent. This also can specif= y lifetime by having an "expires" or "maxAge" property in the parameter dic= tionary for the call.

The TPWG has discussed using cookies as a more generic method, but the S= OP gets in the way (you cannot limit the state to a top level context).

The Accept-CH header is similarly determining stateful site-specific beh= aviour for subresources, perhaps this points to a generalised solution? Esp= ecially as there are privacy/user control issues in common?

I am thinking about a well-known cookie prefix (as proposed for RFC6265b= is) that would cause the cookie to be sent to subresources in the cookie he= ader, but only within the context of the parent that placed it. The existen= ce of particular forms of this well-known cookie could then determine UA be= haviour (such as sending Client Hints to subresources).

Implementation would be simpler because the expiry procedures are alread= y in place.

A further advantage would then be that the state is automatically contai= ned in the UAs cookie store, accessible to existing privacy oriented UA UIs= and extensions, increasing transparency.

For example:

Set-Cookie: __SRAccept-CH=3DDPR;expires=3DSat, 05 Mar 2017 00:00:00 GMT<= /p>

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

= ----==_mimepart_58baaa0778cc1_a043f86e6975c3c36299d-- From nobody Sun Mar 5 17:41:12 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.598 X-Spam-Level: X-Spam-Status: No, score=-0.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=GRBnw+hoCJXObkSeXW8u+FAPQPo=; b=uLwMY4CsYZ0BZ5iE RjO1Lcb/U6o3iXL8k6oijBPR8whwH26sab/kes5O4T25k6BZYPlIznTnspFKWkEQ w8wlZxy8XD7L1LOBE464nyqZQHfhimQvffiC5lJtGBYdV3vNLW3zqBe7Hc92VSCB /c8/ejNQQuPJq3a4M2I5gp98wnI= Date: Sun, 05 Mar 2017 17:41:08 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] CH editorial (#308) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bcbe347232_7c2d3f7fb69e9c2c592d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 06 Mar 2017 01:41:11 -0000 ----==_mimepart_58bcbe347232_7c2d3f7fb69e9c2c592d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit "client" and "user agent" are defined terms in HTTP; client covers *anything* that sends a request, including proxies, whereas user agent is only the originator of requests -- regardless of whether it's a Web browser or app. (this is not the WHATWG :) I saw that you defined the abbreviation, but I suspect the RFC editor is going to change it; all other HTTP RFCs use the phrase "user agent." Besides which, "User-Agent" is the name of the header field, further confusing things. -- 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/308#issuecomment-284282772 ----==_mimepart_58bcbe347232_7c2d3f7fb69e9c2c592d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

"client" and "user agent" are defined terms in HTTP; client covers a= nything that sends a request, including proxies, whereas user agent is= only the originator of requests -- regardless of whether it's a Web browse= r or app.

(this is not the WHATWG :)

I saw that you defined the abbreviation, but I suspect the RFC editor is= going to change it; all other HTTP RFCs use the phrase "user agent." Besid= es which, "User-Agent" is the name of the header field, further confusing t= hings.

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

= ----==_mimepart_58bcbe347232_7c2d3f7fb69e9c2c592d-- From nobody Sun Mar 5 17:45:33 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.475 X-Spam-Level: X-Spam-Status: No, score=-0.475 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=C+LDgMVMfTyq4Bh5R9NhmZ+yiW0=; b=w/ABmbGJcjQka5KO VD4PeMxo4eoug1yIuv/2MtBn8HLRKgaXAPLgGu2XfpmucHKFtsmXAwjLCszNDrS3 kAauzizQS/EMmHNHd6tjteg9enogL+47tfIuJcwmy/Ser9GHdC5q2WDgNqC3JjpI V7An/kFv+xKtlsCzWM9aJI8nTaQ= Date: Sun, 05 Mar 2017 17:45:29 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Editorial cleanup and improvements (#309) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bcbf3937f4_172f3fb7fb779c3076651"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 06 Mar 2017 01:45:31 -0000 ----==_mimepart_58bcbf3937f4_172f3fb7fb779c3076651 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mnot approved this pull request. LGTM; see answers to first two questions on original issue. -- 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/309#pullrequestreview-25164684 ----==_mimepart_58bcbf3937f4_172f3fb7fb779c3076651 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mnot approved this pull request.

LGTM; see answers to first two questions on original issue.

—
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_58bcbf3937f4_172f3fb7fb779c3076651-- From nobody Sun Mar 5 21:40:39 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.021 X-Spam-Level: X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=dzURi4nqgaRbRzhWkVBP0hpDPaA=; b=B46Rytej3fGoH5Dk jOenyaml+P4zoNVxZvtOo9T+ohe+cY+NitcCc7GJHvcNb3fjGdmX+ZFYEdi0kNvM zKZPuptVOfLEISOLN38sjoEBcI7VFND5/FSYSR3qwxWj4YLTitdk9f2BjlspNt2y zfyFx0myZC+oj34hka4Hhd4QbQE= Date: Sun, 05 Mar 2017 21:40:35 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bcf65376b9_4f433fd17ff33c304112e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 06 Mar 2017 05:40:39 -0000 ----==_mimepart_58bcf65376b9_4f433fd17ff33c304112e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @igrigorik - Just thinking through doing this, a couple of questions -- It seems like there are a lot of potential dimensions that the server's preferences for sending CH could vary -- e.g., same-origin vs. third-party, navigation vs. subresource, etc. Are we offering the right capability (all requests from a given origin) here? Will having one `Accept-CH` policy for an entire origin work? What if different resources need different headers? How should clients behave when they get conflicting lists of headers and/or lifetimes for a given origin? Using a cache to determine whether to sent hint headers means that the initial navigation request to a given origin won't have them, so any behaviour that depends on them will need a fallback. Is that just going to be "serve the heavier page", or something more complex? -- 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/307#issuecomment-284307644 ----==_mimepart_58bcf65376b9_4f433fd17ff33c304112e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@igrigor= ik - Just thinking through doing this, a couple of questions --

It seems like there are a lot of potential dimensions that the server's = preferences for sending CH could vary -- e.g., same-origin vs. third-party,= navigation vs. subresource, etc. Are we offering the right capability (all= requests from a given origin) here?

Will having one Accept-CH policy for an entire origin work?= What if different resources need different headers? How should clients beh= ave when they get conflicting lists of headers and/or lifetimes for a given= origin?

Using a cache to determine whether to sent hint headers means that the i= nitial navigation request to a given origin won't have them, so any behavio= ur that depends on them will need a fallback. Is that just going to be "ser= ve the heavier page", or something more complex?

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

= ----==_mimepart_58bcf65376b9_4f433fd17ff33c304112e-- From nobody Mon Mar 6 04:42:35 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.384 X-Spam-Level: X-Spam-Status: No, score=-0.384 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=E/64Q3l+R4Bs++08zrrRJmR0dvY=; b=GlWniGHQq+tdHJaD 39B/Hw6XElr6sm5EScyhZpN6mCDgh86GWIHgmGKQqiZbAli0dvBBEDXZ7JLx0sIH rJjAn288iPNOdYuQbMGxgniNBtN0r7j36KSyGcrd4smq9xwMNi8NRkh30v36vuIz A3wpXNn1SRGroxj8WM2AAT+BoO8= Date: Mon, 06 Mar 2017 04:42:29 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Editorial cleanup and improvements (#309) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bd5935d8b41_1f003fa27337dc3c3093ef"; 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, 06 Mar 2017 12:42:33 -0000 ----==_mimepart_58bd5935d8b41_1f003fa27337dc3c3093ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @igrigorik pushed 1 commit. 49a1f27 cleanup client vs user agent use -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/309/files/f5f3f8a62aea3593d682e55bf4a5170b6f9c84b4..49a1f278e79a1457c89ff49381f1ca7ff7f09d04 ----==_mimepart_58bd5935d8b41_1f003fa27337dc3c3093ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igrigorik pushed 1 commit.

  • 49a1f27 cleanup client vs user agent use

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

----==_mimepart_58bd5935d8b41_1f003fa27337dc3c3093ef-- From nobody Mon Mar 6 04:43:01 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.456 X-Spam-Level: X-Spam-Status: No, score=-0.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=MyCbQI5wJ8hnl96dCgmb4J+jrCE=; b=M7SaX5dIdEulMzrF 6o1YXQJsG0tz6BKHMVzf6VK1wYAqPvWnbRj53CRMRgBetbWzBcmHQ99AUFbp9dCj LvrwafsHytKhqYJkvlC1WYG1k3bzKng913G464I4mc2WS7E2fLnOEdQl8BlGTb1/ YRMjH25S8SmQTXY8zgjsyMqoS7Q= Date: Mon, 06 Mar 2017 04:42:56 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Editorial cleanup and improvements (#309) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bd5950b8f31_60b43f7ef9a6bc3083517"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 06 Mar 2017 12:42:59 -0000 ----==_mimepart_58bd5950b8f31_60b43f7ef9a6bc3083517 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mnot thanks, updated -- ptal. -- 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/309#issuecomment-284385924 ----==_mimepart_58bd5950b8f31_60b43f7ef9a6bc3083517 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mnot thanks, updated -- ptal.

—
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_58bd5950b8f31_60b43f7ef9a6bc3083517-- From nobody Mon Mar 6 04:51:18 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.002 X-Spam-Level: X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=TRyX/ByFkSjRcuFVE1sI3fdUIt0=; b=QwANNlNlgY2Ib6Xn g1YmEmoH081Bbt54I0AxdO3tfx4QWM9llgQwYzhtmEY/+F/4M5K6y5dz+yk9B4Yi 2ghWdBwimo+ewoNHQu7bIEPQY+f0Ky8i+/JV4Y69RlB75/0leaZF8vmQF0fHauWS kYZwwehfqcMHVihZmnOEA63Hm5o= Date: Mon, 06 Mar 2017 04:51:14 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bd5b42890fb_43743fcbe3f3bc38208683"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 06 Mar 2017 12:51:17 -0000 ----==_mimepart_58bd5b42890fb_43743fcbe3f3bc38208683 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > It seems like there are a lot of potential dimensions that the server's preferences for sending CH could vary -- e.g., same-origin vs. third-party, navigation vs. subresource, etc. Are we offering the right capability (all requests from a given origin) here? Based on the experience and feedback so far.. yes. It's the simplest strategy that covers all the use cases, and everything else just adds more configuration and implementation complexity. > Will having one Accept-CH policy for an entire origin work? What if different resources need different headers? How should clients behave when they get conflicting lists of headers and/or lifetimes for a given origin? Last registration wins, similar to HSTS. > Using a cache to determine whether to sent hint headers means that the initial navigation request to a given origin won't have them, so any behaviour that depends on them will need a fallback. Is that just going to be "serve the heavier page", or something more complex? The former. Practically speaking, sites can't rely on CH hints being available from every browser in any case, so they need a fallback strategy regardless. -- 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/307#issuecomment-284387675 ----==_mimepart_58bd5b42890fb_43743fcbe3f3bc38208683 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It seems like there are a lot of potential dimensions that the server's = preferences for sending CH could vary -- e.g., same-origin vs. third-party,= navigation vs. subresource, etc. Are we offering the right capability (all= requests from a given origin) here?

Based on the experience and feedback so far.. yes. It's the simplest str= ategy that covers all the use cases, and everything else just adds more con= figuration and implementation complexity.

Will having one Accept-CH policy for an entire origin work? What if diff= erent resources need different headers? How should clients behave when they= get conflicting lists of headers and/or lifetimes for a given origin?

Last registration wins, similar to HSTS.

Using a cache to determine whether to sent hint headers means that the i= nitial navigation request to a given origin won't have them, so any behavio= ur that depends on them will need a fallback. Is that just going to be "ser= ve the heavier page", or something more complex?

The former. Practically speaking, sites can't rely on CH hints being ava= ilable from every browser in any case, so they need a fallback strategy reg= ardless.

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

= ----==_mimepart_58bd5b42890fb_43743fcbe3f3bc38208683-- From nobody Mon Mar 6 05:31:29 2017 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, 06 Mar 2017 05:31:24 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488807084; bh=YOeSpD7N3gBlNQOOvU+L8wleNIFFyXSf1DOrTlQfYCw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2XuLgfNR2BRfW8V4qzjN+hKZ+iaw8Ax+fqtKwBW5s2/78UbD/83sg7vlnJntuyPI+ 7+T9kkzc1wcV8HDT5vKXirsv6U0Y5eRK7BGkKxhetK9OWUWOQuXpDNbdgnSVeF6h6t POpwj18XJdvzmyTbXPoLtXdjrRycLZ5ci06aDgew= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Allow servers to specify max-age in the client hints header (#306) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bd64acc2200_6c583fc6bf55fc381639ac"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 06 Mar 2017 13:31:28 -0000 ----==_mimepart_58bd64acc2200_6c583fc6bf55fc381639ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Disclaimer: I'm new here, so please forgive possible naivety :) Thinking about this issue and other kinds of scoping mechanisms (`max-age` directives in Cache Control, Cookies or HSTS, well-known Origin Policy files etc.), I was wondering whether we could try to attach directives to manage site properties (such as CH scope) in both time "and space" to the TLS scope. A TLS certificate is a necessary prerequisite for many HTTP/Web extensions. E.g. HSTS headers are ignored without a validated certificate. We could limit the possible lifespan of any time-bound directive to the remaining TTL of the certificate. Say my LE certificate expires in 30 days; the user agent could store the CH settings for exactly this time span. Usually certificates are renewed before the expire. This should allow user agents to revalidate and reschedule the property expiry well before they expire. The same could apply to HSTS or other properties. A user agent may use this site/origin property until the certificate expires, and it must be revalidated at the next contact thereafter. The spatial scope of the certificate is somewhat boring, because it usually covers a whole origin in sense of `/` on a certain domain name. However, wildcard certificates or ones with more than one common name could be used to tie together a bunch of hostnames. We could use that as an outer bound for origin properties. More generally, could we transfer properties such as [Origin Policies](https://wicg.github.io/origin-policy/) or HSTS directives as part of the TLS handshake in an [ALPN](https://tools.ietf.org/html/rfc7301)-like fashion? This would enable the server to communicate transfer rules to the user agent before the first request on HTTP level is carried out. -- 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/306#issuecomment-284396118 ----==_mimepart_58bd64acc2200_6c583fc6bf55fc381639ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Disclaimer: I'm new here, so please forgive possible naivety :)

Thinking about this issue and other kinds of scoping mechanisms (max-age directives in Cache Control, Cookies or HSTS, well-known = Origin Policy files etc.), I was wondering whether we could try to attach= directives to manage site properties (such as CH scope) in both time "an= d space" to the TLS scope.

A TLS certificate is a necessary prerequisite for many HTTP/Web extens= ions. E.g. HSTS headers are ignored without a validated certificate. We c= ould limit the possible lifespan of any time-bound directive to the remai= ning TTL of the certificate. Say my LE certificate expires in 30 days; th= e user agent could store the CH settings for exactly this time span. Usu= ally certificates are renewed before the expire. This should allow user a= gents to revalidate and reschedule the property expiry well before they e= xpire. The same could apply to HSTS or other properties. A user agent may= use this site/origin property until the certificate expires, and it must= be revalidated at the next contact thereafter.

The spatial scope of the certificate is somewhat boring, because it us= ually covers a whole origin in sense of / on a certain domai= n name. However, wildcard certificates or ones with more than one common = name could be used to tie together a bunch of hostnames. We could use tha= t as an outer bound for origin properties.

More generally, could we transfer properties such as Origin Policies or HSTS directives a= s part of the TLS handshake in an ALPN-like fashion? This would enable the server to communica= te transfer rules to the user agent before the first request on HTTP leve= l is carried out.

&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_58bd64acc2200_6c583fc6bf55fc381639ac-- From nobody Tue Mar 7 04:16:50 2017 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Tue, 07 Mar 2017 04:16:45 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488889005; bh=70yj+OPuZEnCA+PJbZYXS8fEYMEkqN5zy0hfONQH53I=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jhrXyJB40bL3Zz3RSIGSp0FP0trXxBqXi/dPVJqN3vmtOqWFsSG1mc2eQavkVFMJA kVx/Et267lwRaiHi9r71GROeUrwOH71Fmt8r+QMSp9WFdg8smf1n9G44f5N4GcplaZ d7TJGwsXD8WDcB55/CfmqLw5xbqpmXKnS+e6NUb0= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Allow servers to specify max-age in the client hints header (#306) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bea4adc6986_6a363fbf8484bc2c2744e4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 07 Mar 2017 12:16:49 -0000 ----==_mimepart_58bea4adc6986_6a363fbf8484bc2c2744e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @filex interesting idea, but I don't think we want to couple certificate lifetime to other settings.. there is no reason why cert lifetime is representative of the content lifetime transported over the TLS tunnel. -- 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/306#issuecomment-284705948 ----==_mimepart_58bea4adc6986_6a363fbf8484bc2c2744e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@filex= interesting idea, but I don't think we want to couple certificate lifeti= me to other settings.. there is no reason why cert lifetime is representa= tive of the content lifetime transported over the TLS tunnel.

&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_58bea4adc6986_6a363fbf8484bc2c2744e4-- From nobody Tue Mar 7 19:53:16 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.617 X-Spam-Level: X-Spam-Status: No, score=-0.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=CUiBdhvAtdiFmfuy1P1GfNRyE+s=; b=iqD5WK+SGpW4GMci 3JGAjpYe+rlkSiunuoPOj1Y5h30DLnm6zOXV1gvW9OEWbrznUnc4Bvzk8gz4P4pd g2oqulvntuD5LDJojfz+3WBMcq566UpraM4CYEpZ5R6dFQthxlyDwC9sG9q1gTVX 5V5swoPy9c9c9x7GGMTqNZLdl6w= Date: Tue, 07 Mar 2017 19:53:11 -0800 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Allow servers to specify max-age in the client hints header (#306) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58bf8027d4eca_27943f958bacdc34185654"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 08 Mar 2017 03:53:14 -0000 ----==_mimepart_58bf8027d4eca_27943f958bacdc34185654 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @filex, you will find that there is a great deal of reluctance to do that sort of thing. If we were to start doing that, then we would create another reason to lengthen the validity period of certificates. That's bad for security. In other words, is an *advantage* to have a logical separation of details of the authentication mechanism from the management of state. -- 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/306#issuecomment-284939422 ----==_mimepart_58bf8027d4eca_27943f958bacdc34185654 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@filex, = you will find that there is a great deal of reluctance to do that sort of t= hing. If we were to start doing that, then we would create another reason = to lengthen the validity period of certificates. That's bad for security.<= /p>

In other words, is an advantage to have a logical separation of= details of the authentication mechanism from the management of state.

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

= ----==_mimepart_58bf8027d4eca_27943f958bacdc34185654-- From nobody Sat Mar 11 09:40:43 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: 0.599 X-Spam-Level: X-Spam-Status: No, score=0.599 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=0.7, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=iw0/jwER+/m0KAFnB8eiJpGpRJM=; b=BSJ13u2/aUoyLBY3 sisGViO5ajM2O8rQkxzYMa98k3tYULxml+hIPhB4mBLePnKsiUsxZ9kjJp/DND4/ +1NSHAYlbJG+24QkzEIHKmJT/3efxgQ1UxD7SXVOFpdvjRQLruL5oPydaoD8urVE AknN5vTnfuctnP0Um/f0bhUJ0uY= Date: Sat, 11 Mar 2017 09:40:38 -0800 To: httpwg/http-extensions Subject: [httpwg/http-extensions] RFC 7515 (base64url) is only used in examples and can be moved to informative (#310) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c4369679262_19a83faaa5173c2c22062d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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: Sat, 11 Mar 2017 17:40:42 -0000 ----==_mimepart_58c4369679262_19a83faaa5173c2c22062d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit -- 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/310 ----==_mimepart_58c4369679262_19a83faaa5173c2c22062d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

—
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_58c4369679262_19a83faaa5173c2c22062d-- From nobody Sun Mar 12 17:12:33 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.384 X-Spam-Level: X-Spam-Status: No, score=-0.384 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=g0o1VqoViZn9H2CoK7Py3UzkCJc=; b=dDn+BbpibsQ/AQgH NDvFxwSEq4HgyztzrHfoe3PO1L5fNozC/btBJ2ELzSeDMiGIUwP+MTZKr2JoMBjd S2UHbjxUznMOEDU3k1AMxdTSU7pZeKbTDwRy/aBz2nbsxCgRLDnjueI0ZVyFeng6 AEIDJn7ucKhA+srWQPiu1XHcfq0= Date: Sun, 12 Mar 2017 17:12:29 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] RFC 7515 (base64url) is only used in examples and can be moved to informative (#310) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c5e3ede6307_74953fb3fb83bc30192159"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 00:12:32 -0000 ----==_mimepart_58c5e3ede6307_74953fb3fb83bc30192159 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #310 via e943e904bdfb2cf5e5d443405a998ec314c07015. -- 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/310#event-996524912 ----==_mimepart_58c5e3ede6307_74953fb3fb83bc30192159 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #310 via e943e90.

—
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_58c5e3ede6307_74953fb3fb83bc30192159-- From nobody Mon Mar 13 09:16:55 2017 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Mon, 13 Mar 2017 09:16:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489421807; bh=VhkInhoDRBWQEkjnIsNmUDkVJMiY/5/Uw1tBy1SGgcc=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UT9XFreddjnqILxtmFArHSXgUqRifuQrAXUvSWY2Yg1O+9vutmqBVeZX3V5Iq3nmc OEi9/fv+EzUv/i50AWWa+0Zx6SrNYp4D6Ihf94j3ajCC3vTp1z5JqvyyhqR42QaBCg /HUEo2Ai9uroDV/WWIT3sABc1yjfaZdrdoyStx3w= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] The inverse of immutable (#288) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6c5eef2c07_62ca3fc2edf9bc2c11612"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 16:16:54 -0000 ----==_mimepart_58c6c5eef2c07_62ca3fc2edf9bc2c11612 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I can imagine such an extension, but its not this one and this one isn't incompatible with adding such a thing in a separate draft. immutable is based on running code and I'm not comfortable expanding that scope here. -- 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/288#issuecomment-286157927 ----==_mimepart_58c6c5eef2c07_62ca3fc2edf9bc2c11612 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I can imagine such an extension, but its not this one and this one isn= 't incompatible with adding such a thing in a separate draft. immutable i= s based on running code and I'm not comfortable expanding that scope here= .

&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_58c6c5eef2c07_62ca3fc2edf9bc2c11612-- From nobody Mon Mar 13 09:26:23 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.383 X-Spam-Level: X-Spam-Status: No, score=-0.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_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=M/WRte+eYpYTq/d7o/E/n1n+N94=; b=CvwB0melqI1K11yE NRXZct5rO2XSsbwDdrBwBsO7xFzv0eCuq7fGT3Hfrr90W48F5T0C5YvQxI496nr2 XgpiEeVerxJ/wTFnbHBALbZQ8XzCm/TDB/SOY91MBuYkB4Y1UBPVW7de1d9+oHMD xWWbmQoSF6Jnoql1L6LxweaL2hM= Date: Mon, 13 Mar 2017 09:26:12 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Immutable editorial (#287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6c824a27a2_2b663f9cdf25fc2c1519fd"; 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, 13 Mar 2017 16:26:19 -0000 ----==_mimepart_58c6c824a27a2_2b663f9cdf25fc2c1519fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mcmanus pushed 1 commit. 1c29668 Merge branch 'master' into immutable-editorial -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/287/files/4923ad83f38d0b278a1823b40d7000073db1a679..1c2966821a2c2bfd6319dad90e61fc1fb662f074 ----==_mimepart_58c6c824a27a2_2b663f9cdf25fc2c1519fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mcmanus pushed 1 commit.

  • 1c29668 Merge branch 'master' into immutable-editorial

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

----==_mimepart_58c6c824a27a2_2b663f9cdf25fc2c1519fd-- From nobody Mon Mar 13 09:26:39 2017 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Mon, 13 Mar 2017 09:26:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489422393; bh=66w2K7Uzlq5sVAj5sZ7sYcNT7ON7pLAGMQXRNEsBmdU=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MMzmWvWOa2oi8J0BBjqM1jHniOa/jsyJ850dH9MkLBmJPSi9OkeGRqkApboCD29Ay 3fCHZiYvZOqUUrlyn/R2TJ1vg37QXcvtJtenxrFJiWwXPGsjHuRo/rkJ0B0+GTyL4B 0TC0wcbtJ4F3DO9wrg5E1xF8uIks99uZM+5y4ThE= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Immutable editorial (#287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6c839e02a7_21143fb611523c3811910"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 16:26:39 -0000 ----==_mimepart_58c6c839e02a7_21143fb611523c3811910 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit thanks for this -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/287#issuecomment-286161197 ----==_mimepart_58c6c839e02a7_21143fb611523c3811910 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

thanks for this

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

----==_mimepart_58c6c839e02a7_21143fb611523c3811910-- From nobody Mon Mar 13 09:29:08 2017 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Mon, 13 Mar 2017 09:29:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489422543; bh=hiY/7asquApT8YYwyVfrgT6KU68k8M+otZ7kzcsxzlw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1Vv/IGSUpw5DIyzajUX+/b357D+dErQwjUkTDgwuG16hiDuylTbu8+jVciYpTYcOC LkjVQP0MnKyiwvMFJl/k9aBNLRNrG5xklw2Hls+1jfAA2Mwg1KOCzov30IvUzUVvlI T0MP1BphOO65xgW9hS2Chv+2fzyg9icBxIbsyESc= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] About Intermediaries (#290) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6c8cfbc3bd_4c283febc648bc2c443012"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 16:29:06 -0000 ----==_mimepart_58c6c8cfbc3bd_4c283febc648bc2c443012 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #290. -- 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/290#event-997557038 ----==_mimepart_58c6c8cfbc3bd_4c283febc648bc2c443012 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #290.

—
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_58c6c8cfbc3bd_4c283febc648bc2c443012-- From nobody Mon Mar 13 09:29:11 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.455 X-Spam-Level: X-Spam-Status: No, score=-0.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_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=AFsG40bU9BIYRpBcEW3W0mk7Qek=; b=n0va+QErjyLodF6Z WOMOo3bR5DgwHKR8LsK1o4t5xNBGlQWR/Db1Y/kvYzQBd64Pf5kuvf6T8exV+i20 Si3gPZvJzGmwDuFU5+4Mf2slQNfsjvFeIleGTXVMKKdI4xiDQoHqMc5k1mkjGrQ0 UvSeAGjPUwND7Y0iet5gad3zDqk= Date: Mon, 13 Mar 2017 09:29:03 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] About Intermediaries (#290) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6c8cf7aa5a_6f4a3f9cdf25fc2c29716b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 16:29:07 -0000 ----==_mimepart_58c6c8cf7aa5a_6f4a3f9cdf25fc2c29716b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit https://github.com/httpwg/http-extensions/commit/fdc18b2ae5fee1e2a2540ca8d71ba0ed2553104b -- 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/290#issuecomment-286162050 ----==_mimepart_58c6c8cf7aa5a_6f4a3f9cdf25fc2c29716b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

fdc18b2

—
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_58c6c8cf7aa5a_6f4a3f9cdf25fc2c29716b-- From nobody Mon Mar 13 09:29:59 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=R7dV/3CjJPeVlEZ0m+NS4bCngDk=; b=qg8NyOYwgDYctnii pDrit/e4wFugFOHvErb0gJBCxeo2wmFUILa23WN5FkTsqmFTeN7CuKKR+UxwLpF/ PfWVMfFHEIl6K4Nnb7w96xk1cwsYqSieu2EhUBsePsJsGm/xo48J9psqSaJcbcbW f5GUtL63RrrcqdHJjUfI6NHNcOA= Date: Mon, 13 Mar 2017 09:29:48 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] immutable definition (#289) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6c8fc3e152_3c933fc2edf9bc2c1701c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 16:29:50 -0000 ----==_mimepart_58c6c8fc3e152_3c933fc2edf9bc2c1701c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #289. -- 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/289#event-997558540 ----==_mimepart_58c6c8fc3e152_3c933fc2edf9bc2c1701c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #289.

—
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_58c6c8fc3e152_3c933fc2edf9bc2c1701c8-- From nobody Mon Mar 13 09:30:01 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.453 X-Spam-Level: X-Spam-Status: No, score=-5.453 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Mon, 13 Mar 2017 09:29:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489422588; bh=/f6DfuDIdPXstESq9se8ZEmJhCEDXSAVGmJ9+nC3Wpw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Gmrso2zHXiApxmyr9+NiXdRqbzKclHO9TVP3okEYRKEHn7eCgCBbzOnQhJUeHtv4J ws+C+VdVg1xW6vFdXkF0oMfT0aPFaf6tnwkkLa3OGPhg9jjHcBoCVrvnVAYgmH0hya 99uyIKSEqj3x70eiJTHl2U13GpPXoe23o8fq7FL0= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] immutable definition (#289) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6c8fc59b23_2ce53fe49f171c2c1203f2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 16:29:52 -0000 ----==_mimepart_58c6c8fc59b23_2ce53fe49f171c2c1203f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit https://github.com/httpwg/http-extensions/commit/dd7a9513d21b5e4c8a4571c909828bf002afaabe -- 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/289#issuecomment-286162316 ----==_mimepart_58c6c8fc59b23_2ce53fe49f171c2c1203f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

dd7a951

—
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_58c6c8fc59b23_2ce53fe49f171c2c1203f2-- From nobody Mon Mar 13 09:31:51 2017 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Mon, 13 Mar 2017 09:31:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489422707; bh=598iClWbDaMV1eCo1PfEu66OqWuFjvznBJRZhcwjtkU=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lmO24GMtxTyJYC7kFYQv4dM6VF4YIJ0qQ3oPvXmbemB7lZ4E8WJglO74rnMKl40Z8 5rIJccIt9vZWoUjiWi78L6OaXd3S2Q3JSxOsjYanJ/aA86aG+Ahr8bJGkXrSZuADSc WM5ld8p2sRHVcuhH/HDgHFk7mvh20dORCJzhKfzk= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Immutable editorial (#287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6c973e6ef9_71723fe49f171c2c267157"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 16:31:50 -0000 ----==_mimepart_58c6c973e6ef9_71723fe49f171c2c267157 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #287. -- 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/287#event-997562309 ----==_mimepart_58c6c973e6ef9_71723fe49f171c2c267157 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #287.

—
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_58c6c973e6ef9_71723fe49f171c2c267157-- From nobody Mon Mar 13 12:51:42 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.597 X-Spam-Level: X-Spam-Status: No, score=-0.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_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=eESRA8u1DWJ1E2Dq8nWXEjPIHWA=; b=hDudeZo/L+3skv7D KEaVqYNJqwUUBwameASayp7lFrS/kCTMOl3cz/251JOuFgQs7jtjEkIxZSuhZxw2 bN13g9fqQN4i2VtCtxtz9LU21ktC34V5t7vEosIWz8lbKtRlSTeaHDL07Jro9RnJ s6Rp0KgrC14SlxaMyPelmAbh+Ic= Date: Mon, 13 Mar 2017 12:51:26 -0700 To: httpwg/http-extensions Subject: [httpwg/http-extensions] immutable: fix typo (#311) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6f83e207bd_6aff3fb2d146fc301498b5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 19:51:39 -0000 ----==_mimepart_58c6f83e207bd_6aff3fb2d146fc301498b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/311 -- Commit Summary -- * immutable: fix typo -- File Changes -- M draft-ietf-httpbis-immutable.md (2) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/311.patch https://github.com/httpwg/http-extensions/pull/311.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/311 ----==_mimepart_58c6f83e207bd_6aff3fb2d146fc301498b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

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

Commit Summary

  • immutable: fix typo

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_58c6f83e207bd_6aff3fb2d146fc301498b5-- From nobody Mon Mar 13 12:59:19 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.383 X-Spam-Level: X-Spam-Status: No, score=-0.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_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Z5y7egHhk+pfcf9QwDDAuwJAVsk=; b=WmdkTEalQwMewntF JNBsNFT4fidMIssr0UIObkGeOBxCH+XK7ZseYMIz5/xrkWIfCBl3nlkGBXkHtk/f 8awaCydN7Gtp76oJFaOyh0++H5TgHmFzoDB4ggjINNmgbyv5IBhg84TYUAWpOEFL gPzXoH+zPH28gCgLwgeaq6OCWWQ= Date: Mon, 13 Mar 2017 12:59:01 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] immutable: fix typo (#311) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6fa05f1cbf_4e93fb73a717c2c1075bb"; 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, 13 Mar 2017 19:59:17 -0000 ----==_mimepart_58c6fa05f1cbf_4e93fb73a717c2c1075bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @vfaronov pushed 1 commit. 5f43419 immutable: fix typo -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/311/files/7eb8433f729dfb10c743adae522bb21d97a65926..5f4341993d96b4e4c9321b9403d836e8d2d334ff ----==_mimepart_58c6fa05f1cbf_4e93fb73a717c2c1075bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@vfaronov pushed 1 commit.

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

----==_mimepart_58c6fa05f1cbf_4e93fb73a717c2c1075bb-- From nobody Mon Mar 13 13:01:22 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.383 X-Spam-Level: X-Spam-Status: No, score=-0.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_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Zz5YBzTikFuExlNG24+TCxMTUlM=; b=m+61b9Nps4bik1L1 lgXndpghdbXnB7FFASVvbhXl4P52gxjamyeBC9TZEO8dP0i461bWuhuLKJQQSchM m8hTTiK5ZA3Y6sZ98aLlCusqa8L2N3KVzy3HDXKhbhe3diavdAHzTMzcTJsZc0jr Zz4f5yfyOTdjQ8WPQ5XCAuM0ANc= Date: Mon, 13 Mar 2017 13:00:35 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] immutable: fix typo (#311) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6fa63c0ced_30673fbe1bc29c3c4503c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 20:01:20 -0000 ----==_mimepart_58c6fa63c0ced_30673fbe1bc29c3c4503c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #311. -- 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/311#event-997916302 ----==_mimepart_58c6fa63c0ced_30673fbe1bc29c3c4503c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #311.

—
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_58c6fa63c0ced_30673fbe1bc29c3c4503c-- From nobody Mon Mar 13 13:01:28 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.455 X-Spam-Level: X-Spam-Status: No, score=-0.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_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=W6DakHu+9s7zHwiPlrzbfjdCrTE=; b=CuJJYP0ead/+t/QE nNMmkfWkyvu3PUYNPuBVYPN+3i4O5+8fc3pj3FgaaIIRLBcXJYIpMe4uj8z+R2Au aQjpmKSq0sDwuATecddhHzCUS+VqV2CEkttAd8NnKIXSUWCp25WWsDdmE1dkYYEW KWNLynKDI5GmYZ3Sin08XsQ6IZU= Date: Mon, 13 Mar 2017 13:00:36 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] immutable: fix typo (#311) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c6fa645816a_36ec3fb0eb23fc2c122440"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 13 Mar 2017 20:01:24 -0000 ----==_mimepart_58c6fa645816a_36ec3fb0eb23fc2c122440 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ty -- 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/311#issuecomment-286225652 ----==_mimepart_58c6fa645816a_36ec3fb0eb23fc2c122440 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

ty

—
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_58c6fa645816a_36ec3fb0eb23fc2c122440-- From nobody Mon Mar 13 17:11:50 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=7J5mSGaiFbCy8bt8pVTOOakh31U=; b=dgLhkHoGk9N3/Rqz aT1J2s+ONwsV9YsHX3O5lfi2EMEQCHPga4ueY63Y2qmXqGybUJ/iC4KwVJAi5we1 1jG+r7NV9RVoJdiXrGxtI5dtO+iWK+CQJc4LDa3TJpHapqVgB9+k/Ycd+6sC6blE mYbXv+dC+HVFsNES94wI9ZtqKWg= Date: Mon, 13 Mar 2017 17:11:46 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] issue 290 - clarify intermediary language (editorial) (fdc18b2) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c73542b8aed_385c3fda39255c30137144"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 14 Mar 2017 00:11:49 -0000 ----==_mimepart_58c73542b8aed_385c3fda39255c30137144 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit when -- 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/commit/fdc18b2ae5fee1e2a2540ca8d71ba0ed2553104b#commitcomment-21301582 ----==_mimepart_58c73542b8aed_385c3fda39255c30137144 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

when

—
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_58c73542b8aed_385c3fda39255c30137144-- From nobody Mon Mar 13 17:16:26 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=zHjr6n8Wxyr8qPaT4MNHXJCFfpc=; b=tGHhO4fMPkHCryiA 2X7889PsaQQq1QfCGoW/Ux0MWaDiQbP5ZdzsKmWfadVaoLL/LZrJ7g+0YqJHKos7 gU8JcnMbBUhkk5zNiNxqP6+Ka8gH4txDqAQ40ChDeBRyYmCPMF7rbCMHGZpJxjXf jWMRInv6W/C5kWjhy3ijGoyBgA8= Date: Mon, 13 Mar 2017 17:16:22 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] The inverse of immutable (#288) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c73656ac7a6_5ad3ff285c5fc302338f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 14 Mar 2017 00:16:25 -0000 ----==_mimepart_58c73656ac7a6_5ad3ff285c5fc302338f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #288. -- 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/288#event-998237460 ----==_mimepart_58c73656ac7a6_5ad3ff285c5fc302338f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #288.

—
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_58c73656ac7a6_5ad3ff285c5fc302338f3-- From nobody Mon Mar 13 17:16:34 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.455 X-Spam-Level: X-Spam-Status: No, score=-0.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_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=cy45SoVvbkfhGaXEJTBIB196DmQ=; b=ZqBz2mJWTxwDKxEL Ea508fbe6dS+2Is2gVdYEoJmwP5iflh9IbfEUNMuFVLFn+3RqtINy4PSkhtJktRs xiZFPJc3vrfTEeIjzn0ofuNMjn0znbfBVW2zljxhr8YOZ8kzfyAs/P8MQIRlpitJ j+jvBsu+1RByGDt9KTgtxKE/Kss= Date: Mon, 13 Mar 2017 17:16:22 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] The inverse of immutable (#288) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c73656a6076_1fd83fee12c29c381472e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 14 Mar 2017 00:16:33 -0000 ----==_mimepart_58c73656a6076_1fd83fee12c29c381472e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Makes sense. If anyone needs this, we can revisit. -- 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/288#issuecomment-286283522 ----==_mimepart_58c73656a6076_1fd83fee12c29c381472e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Makes sense. If anyone needs this, we can revisit.

—
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_58c73656a6076_1fd83fee12c29c381472e-- From nobody Mon Mar 13 17:27:30 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.453 X-Spam-Level: X-Spam-Status: No, score=-5.453 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Mon, 13 Mar 2017 17:27:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489451246; bh=CaMMV8jeDjlF5XvDhBdr6YGC/W0RyARoox8HvihF5Hw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y7X8k9kUZ3z5UbM+KdskugBa1RCr73QaBEZ2UjUFjr6cpRxuK4pM7NbYsjN7bWsdD ZB5L8Lu7/+wiJK51RRUEvpd6Clck/9/cL2GqQO03fTlgH8dcnewAU+o5CWXTzp3KdH 9LX4+4loHWiUkmTSKhFmN7qVf/r+X5yRzu5fXEH8= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] issue 290 - clarify intermediary language (editorial) (fdc18b2) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c738eed1dbf_8c33fc9ca2e5c38446455"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 14 Mar 2017 00:27:29 -0000 ----==_mimepart_58c738eed1dbf_8c33fc9ca2e5c38446455 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit already fixed in pr 311. thanks -- 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/commit/fdc18b2ae5fee1e2a2540ca8d71ba0ed2553104b#commitcomment-21301729 ----==_mimepart_58c738eed1dbf_8c33fc9ca2e5c38446455 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

already fixed in pr 311. thanks

—
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_58c738eed1dbf_8c33fc9ca2e5c38446455-- From nobody Tue Mar 14 00:07:50 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.456 X-Spam-Level: X-Spam-Status: No, score=-0.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=43KgLEp5QLAhhTtBfx1CeX8Z5ds=; b=rl5UdnutX7VsSdzq Cb9q7jeZ/GudFFtKUKHLvTVjiYY+o20D3XTHlfL6VHeQeQ+YNMWCaVJZYwg/txSF 6LgTLcAvyFLGl1O/e7K+kYBOsKVY8urAed1hikSdsMD2sy7Fl20sfCIZavx7ckt+ d6AlFFJxj9M7gOFsbSe0bfAZtnA= Date: Tue, 14 Mar 2017 00:07:45 -0700 To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Editorial cleanup and improvements (#309) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c796c1af2ef_147b3ffd2cfc7c2c10444"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 14 Mar 2017 07:07:48 -0000 ----==_mimepart_58c796c1af2ef_147b3ffd2cfc7c2c10444 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks! -- 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/309#issuecomment-286339482 ----==_mimepart_58c796c1af2ef_147b3ffd2cfc7c2c10444 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Thanks!

—
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_58c796c1af2ef_147b3ffd2cfc7c2c10444-- From nobody Tue Mar 14 01:03:11 2017 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, 14 Mar 2017 01:03:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489478586; bh=/JeLY6JrLhIH30uu8KTit+qlXdLIPY+rRqxa2JTMxXY=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EwFH2Z2D1HUDYp5XkiUjJVHkDguHtbGRsok0Npf+IsrY+JsBrVZRG/vWR/awWChs8 oBSx9jBykoAh+Y0qIVDWcAko8Zfogw7XX/F1CwAdmjsjhLWu4BXAhsx3wUCSa0xNKX x2D/b4LY9MmCYMXuuKQ+cJZ2DZPTtAGCxyGK/fqc= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Editorial cleanup and improvements (#309) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c7a3baada81_20173fc6c9049c3012442e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 14 Mar 2017 08:03:09 -0000 ----==_mimepart_58c7a3baada81_20173fc6c9049c3012442e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #309. -- 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/309#event-998578848 ----==_mimepart_58c7a3baada81_20173fc6c9049c3012442e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #309.

—
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_58c7a3baada81_20173fc6c9049c3012442e-- From nobody Tue Mar 14 01:10:50 2017 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=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Tue, 14 Mar 2017 01:03:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489478586; bh=G1nPYhX56NGUEG4vHFAAIEL9vjf39+vK+jYxAXY9gxg=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r8OWJCj3khwRu5a1cQx/s40nARnEhSw4Ue7lPr3K+ZEWQFtzBvwNLrkzpigpeqWCi 297Jy0mPnmpLuvq+jehhUFzLpITVXNf/eAbas6PgGa7956NBErgxfrfzc6m8YISeQT at0hFdxtb5xVQ9Mnxw5UaqljnWu0vHwUxjEZwRss= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [httpwg/http-extensions] CH editorial (#308) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c7a3ba9fb4d_4153f815ca67c38109ed"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Cc: Subscribed 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, 14 Mar 2017 08:10:50 -0000 ----==_mimepart_58c7a3ba9fb4d_4153f815ca67c38109ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #308 via #309. -- 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/308#event-998578846 ----==_mimepart_58c7a3ba9fb4d_4153f815ca67c38109ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #308 via #309.

—
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_58c7a3ba9fb4d_4153f815ca67c38109ed-- From nobody Tue Mar 14 14:25:51 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: 1.161 X-Spam-Level: * X-Spam-Status: No, score=1.161 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=uUeulL/n3qiBDl/MhLLsIXHX8ts=; b=T/Ez31WQKVdRao9h HxPTb1R+oHSqgGjWuLCrrs9YHQRGNgXTYHWEIJwHGMfWYRqOI+puQnBI0hjhj0Eb FlzKHoCLVcD8AwLShK1MvRrC9hEEt3GNtvEuyujN2XRX/pY30x1EKODMX1wVabuF WPTiOHKpztFrPO09nq7WQOVXkCE= Date: Tue, 14 Mar 2017 14:25:46 -0700 To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Expect-CT report-uri should be quoted (#312) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c85fda1ead0_24df3fb9da053c2c1133cc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2017 21:25:50 -0000 ----==_mimepart_58c85fda1ead0_24df3fb9da053c2c1133cc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The report-uri syntax in Section 2.1.1 should quote the `absolute-URI`. This would most closely match HPKP, for which the report-uri syntax is not specified but all given examples are quoted. (https://tools.ietf.org/html/rfc7469#section-2.1.5) -- 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/312 ----==_mimepart_58c85fda1ead0_24df3fb9da053c2c1133cc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The report-uri syntax in Section 2.1.1 should quote the absolute-URI. This would most closely match HPKP, for which the report-uri syntax is not specified but all given examples are quoted. (https://tools.ietf.org/html/rfc7469#section-2.1.5)

—
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_58c85fda1ead0_24df3fb9da053c2c1133cc-- From nobody Tue Mar 14 14:29:54 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.17 X-Spam-Level: X-Spam-Status: No, score=-7.17 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=0.726, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.796, 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, 14 Mar 2017 14:29:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489526989; bh=nOFLgUFMr046LrkqRkFlNZQ+bUiLvZ525V+UIBxYPOY=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EimV7sYWj5UQRyQ1LukXQZJyxZ9DbeimaOzseHyweMkRaXMkswk/VHN23cfW1Csfa tOyS/XR2dBKbUjkgs4BucWdnfzQiu1Gt1C/bS+yYxAyufA3aIKa8lBwlZOtJlj5VY6 UIGJP/94A1MbX+6MSD0cyMfVfaxrKpV0IGgmuVeU= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT report-uri should be quoted (#312) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58c860cda0fd0_28f73f85e6f45c30119771"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2017 21:29:52 -0000 ----==_mimepart_58c860cda0fd0_28f73f85e6f45c30119771 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually, it should be silent on this. Any parameter should take *either* token *or* quoted-string, without exception. If the type of the parameter always requires to use quoted-string, that's fine and is something the sender needs to be aware of. That said, it should not be enforced in the grammar. -- 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/312#issuecomment-286566829 ----==_mimepart_58c860cda0fd0_28f73f85e6f45c30119771 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Actually, it should be silent on this.

Any parameter should take either token or quoted-str= ing, without exception.

If the type of the parameter always requires to use quoted-string, tha= t's fine and is something the sender needs to be aware of. That said, it = should not be enforced in the grammar.

&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_58c860cda0fd0_28f73f85e6f45c30119771-- From nobody Fri Mar 17 10:44:00 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -6.498 X-Spam-Level: X-Spam-Status: No, score=-6.498 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_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 17 Mar 2017 10:43:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489772635; bh=INq/eyiJ44pQ6Fd6iNegC9nFS9AV9VImdnhxsA2ixWM=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Rg1irEB18XqzaBOTJ1+ymRcptvH33/JNlVsPNoMEC3GMUJcW4cOhvKDC5avl401Cw Corh4nPrjwQfee5fU+IesywAyPekJA5UZxt0LS6Bi+ORauPoAbq48/JyBTvAHUC8Qv Fg9obeh/VAqhWzFNGiuKiVUsOWLzZ1ZYvERbEcc4= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58cc205bc2767_79493fd877dddc38315698"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 17:43:58 -0000 ----==_mimepart_58cc205bc2767_79493fd877dddc38315698 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mnot @mikewest would love to hear your thoughts on the cookie opt-in idea floated above. `Set-Cookie: __Secure-Accept-CH=DPR; Secure; Path=/images; Expires=` - It does provides more flexibility than the origin wide opt-in -- e.g. customizable by path, etc. - It's visible to the user and subject to all other cookie policies and workflows. Do we have any other precedents that use cookies for feature opt-ins? Any gotchas with going down this path, spec/layering and implementation wise? It's also unclear to me whether we'd really need to invent new prefixes.. hoping the answer is "no". -- 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/307#issuecomment-287423778 ----==_mimepart_58cc205bc2767_79493fd877dddc38315698 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mnot <= a href=3D"https://github.com/mikewest" class=3D"user-mention">@mikewest would love to hear your thoughts on the cookie opt-in idea floated abo= ve.

Set-Cookie: __Secure-Accept-CH=3DDPR; Secure; Path=3D/images; Ex= pires=3D<date>

  • It does provides more flexibility than the origin wide opt-in -- e.g.= customizable by path, etc.
  • It's visible to the user and subject to all other cookie policies and= workflows.

Do we have any other precedents that use cookies for feature opt-ins? = Any gotchas with going down this path, spec/layering and implementation w= ise? It's also unclear to me whether we'd really need to invent new prefi= xes.. hoping the answer is "no".

&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_58cc205bc2767_79493fd877dddc38315698-- From nobody Fri Mar 17 12:07:17 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -9.295 X-Spam-Level: X-Spam-Status: No, score=-9.295 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=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 17 Mar 2017 12:07:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489777632; bh=MdGjE+UviqVv7x8XGCxTEGen1nPTXUXwnvgbVWt67Ws=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=arXbQuacCP/2i61P8/xmQ7n1ExLzTn91OF19/HhePV3a2DmVQW+QDCBdu3+ni/vA7 RYj4XTSeQfx9gFIgITkxNBGIKKgzphm3m2pHOgqhJY8t9vXy+EnnPQPu3g1m1Gy2r9 9Vh9Y657xhG//PIzBYICmmnLBH7NIoRVk6axYlvY= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58cc33e076cb_7af3f85d18e7c2c27261"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 19:07:16 -0000 ----==_mimepart_58cc33e076cb_7af3f85d18e7c2c27261 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From a practical perspective, this sounds expensive if we need to consult the cookie monster for every request. I suspect that we'd internally need to turn this into something like HSTS where we store the pins distinctly from cookies, at which point we lose much of the elegance of the proposal, I think. >From a theoretical perspective, this is breaking new ground. We don't have any other special-purpose cookies that I know of. We'd need to reserve the name in some way (which is absolutely doable, if odd). Also, cookies have terrible scoping rules. The less eTLD+1 we have, the better, from my perspective. >From a pinning perspective, spelling the pin as `Set-Cookie` vs `Set-CH-Disposition` or something is not terribly concerning. The server is expressing a preference, and we're caching it locally. The general idea of pinning that kind of preference seems fine to me. I'd prefer to see it done via origin policy, but I still haven't found anyone to implement that (nor have I addressed @mnot's feedback on the spec... :( ). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/307#issuecomment-287445118 ----==_mimepart_58cc33e076cb_7af3f85d18e7c2c27261 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

From a practical perspective, this sounds expensive if we need to cons= ult the cookie monster for every request. I suspect that we'd internally = need to turn this into something like HSTS where we store the pins distin= ctly from cookies, at which point we lose much of the elegance of the pro= posal, I think.

From a theoretical perspective, this is breaking new ground. We don't = have any other special-purpose cookies that I know of. We'd need to reser= ve the name in some way (which is absolutely doable, if odd). Also, cooki= es have terrible scoping rules. The less eTLD+1 we have, the better, from= my perspective.

From a pinning perspective, spelling the pin as Set-Cookie vs Set-CH-Disposition or something is not terribly concern= ing. The server is expressing a preference, and we're caching it locally.= The general idea of pinning that kind of preference seems fine to me. I'= d prefer to see it done via origin policy, but I still haven't found anyo= ne to implement that (nor have I addressed @mnot's feedback on the 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_58cc33e076cb_7af3f85d18e7c2c27261-- From nobody Fri Mar 17 14:22:02 2017 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_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 17 Mar 2017 14:21:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489785717; bh=jKCM0oKjKPRV0qJ6zfWlC9Q58WjN4zckVQvElF7XfKs=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r4hKFbMx5Fy2zB6Cv4F8AGFa1DlhYkGp8DVcrXpjCaLypjMqWGw4remn6pzLIO95d MpdM1lml9dOSOgzEFy2gTciZKRRHYGQl6gc01ABEg2XtYGeEIlC66zsQpoDeCsCLKz +ttx5zhfEcwWXu8ZY5SjRci3r9kxK4TrK2reXGbo= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58cc5374a0209_1cd33fb2328abc3025872b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 21:22:00 -0000 ----==_mimepart_58cc5374a0209_1cd33fb2328abc3025872b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > From a practical perspective, this sounds expensive if we need to consult the cookie monster for every request. I suspect that we'd internally need to turn this into something like HSTS where we store the pins distinctly from cookies, at which point we lose much of the elegance of the proposal, I think. Right, you confirmed my main worry. Solving this problem via cookies is doable, but brings a lot of unrelated complexity that I'd much rather avoid. I'm inclined to keep things simple and... - Define a standalone `Accept-CH-Lifetime`, as proposed in https://github.com/httpwg/http-extensions/issues/306#issuecomment-283549512 - Give it origin-wide scope -- no subpaths, etc. - Pin expires based on specified lifetime, or whenever cookies are cleared. - When we ship Origin Policy developers can just move the pin into their policy and everything will continue working as before. I'll take a run at a PR for the above. -- 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/307#issuecomment-287474419 ----==_mimepart_58cc5374a0209_1cd33fb2328abc3025872b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

From a practical perspective, this sounds expensive if we need to cons= ult the cookie monster for every request. I suspect that we'd internally = need to turn this into something like HSTS where we store the pins distin= ctly from cookies, at which point we lose much of the elegance of the pro= posal, I think.

Right, you confirmed my main worry. Solving this problem via cookies i= s doable, but brings a lot of unrelated complexity that I'd much rather a= void. I'm inclined to keep things simple and...

  • Define a standalone Accept-CH-Lifetime, as proposed in <= a href=3D"https://github.com/httpwg/http-extensions/issues/306#issuecomme= nt-283549512" class=3D"issue-link js-issue-link" data-url=3D"https://gith= ub.com/httpwg/http-extensions/issues/306" data-id=3D"210405491" data-erro= r-text=3D"Failed to load issue title" data-permission-text=3D"Issue title= is private">#306 (comment)
    • Give it origin-wide scope -- no subpaths, etc.
    • Pin expires based on specified lifetime, or whenever cookies are clea= red.
  • When we ship Origin Policy developers can just move the pin into thei= r policy and everything will continue working as before.

I'll take a run at a PR for the above.

&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_58cc5374a0209_1cd33fb2328abc3025872b-- From nobody Fri Mar 17 15:28:08 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.795 X-Spam-Level: X-Spam-Status: No, score=-4.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=A6gVm6WagOI5AnKwR3nNh1g7oIo=; b=gD93tGuQOr2BKrha nGGJ9TokFHC5g/cldkiiHeFrIy8vxUdJmk+EEjzvGEq//npTvzXGUc9+6jyjW4GW ao7SFnA/LajN1qjbMPVJwDEo8bOXIyRvgyv8og/F4KZwWuPKjRpzn6VC28DLCJiH swuzfop/dgUpg0X7x4MjACXki1o= Date: Fri, 17 Mar 2017 15:28:04 -0700 To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] define Accept-CH-Lifetime (#313) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58cc62f44f68d_76d3f840e349c30122563"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 22:28:08 -0000 ----==_mimepart_58cc62f44f68d_76d3f840e349c30122563 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closes #307 and #306. You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/313 -- Commit Summary -- * define Accept-CH-Lifetime -- File Changes -- M draft-ietf-httpbis-client-hints.md (46) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/313.patch https://github.com/httpwg/http-extensions/pull/313.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/313 ----==_mimepart_58cc62f44f68d_76d3f840e349c30122563 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closes #307 and #306.

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

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

Commit Summary

  • define Accept-CH-Lifetime

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_58cc62f44f68d_76d3f840e349c30122563-- From nobody Fri Mar 17 15:28:44 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.381 X-Spam-Level: X-Spam-Status: No, score=-5.381 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 17 Mar 2017 15:28:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489789720; bh=XEUoBZ5ugRGH62SZln3thedQg9u/5txKAK322janC0k=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Bl/GF5JpRw9asJbfHFuWXR986wOVKEzDFly3Jm5PgEUDJln4leLv9GbrydWvxJyyH lRzQc0HXo2INcMrjsYN4B5kd27DmtjjsooOufAR23FHXMtaygUr+3uT2QE7mNv/9gZ zOGQzGCghgwknoBCxsKwVscuzOEoy3tEWzKmZ8Qg= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Allow servers to specify max-age in the client hints header (#306) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58cc6318612d5_759a3fb60b6d1c3413043"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 22:28:43 -0000 ----==_mimepart_58cc6318612d5_759a3fb60b6d1c3413043 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit First run at `Accept-CH-Lifetime`: https://github.com/httpwg/http-extensions/pull/313 - ptal. -- 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/306#issuecomment-287486917 ----==_mimepart_58cc6318612d5_759a3fb60b6d1c3413043 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

First run at Accept-CH-Lifetime: #313 - ptal.

—
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_58cc6318612d5_759a3fb60b6d1c3413043-- From nobody Fri Mar 17 15:28:57 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -8.177 X-Spam-Level: X-Spam-Status: No, score=-8.177 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=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 17 Mar 2017 15:28:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489789731; bh=Vv4mHB7OV/EsQFNC+aPj4l5AjBVGklfZbppls9lA5TA=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Yn2jiz0J/0dqoYng+CXn4LSybTOBYhHdrsaNPZBI7XmSY3EB3UX+CS1RvvlMLw9FC 2/JHguvXuw8J6x3Vt4M2EtYgmsFCMPqhhsPeFbPmr/71WYHyFeHwT8KmvBz0TIqyOj JUoxVmqJC9PmlS1K6IUjV4jM8UBSYEXmKX94+IxA= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58cc6323d1a13_73c3f840e349c30110188"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 22:28:54 -0000 ----==_mimepart_58cc6323d1a13_73c3f840e349c30110188 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit First run at `Accept-CH-Lifetime`: https://github.com/httpwg/http-extensions/pull/313 - ptal. -- 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/307#issuecomment-287486957 ----==_mimepart_58cc6323d1a13_73c3f840e349c30110188 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

First run at Accept-CH-Lifetime: #313 - ptal.

—
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_58cc6323d1a13_73c3f840e349c30110188-- From nobody Sat Mar 18 02:14:35 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.797 X-Spam-Level: X-Spam-Status: No, score=-4.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=CRLwu6kZi/NGHvAa4nKNm8OT+OI=; b=lvvnq4+7IiUOP2i7 z9/Swvf/1NyR0bn0EW3BtEnLVI8p48gx2wc+3eirrN3L8sBOrduRh+tWcP+LiBOi zstzRlI+lgztzB3F4oikIWsNPDl69AYLiLLLPxmn96j0qZsVaP1ln+DOMUsqKIAO pk7l98WjStoU6xhb2Kpog8pLe+g= Date: Sat, 18 Mar 2017 02:14:30 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58ccfa76d5153_57213fa998e29c2c798ad"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2017 09:14:34 -0000 ----==_mimepart_58ccfa76d5153_57213fa998e29c2c798ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Doesn't "the cookie monster" have to be consulted anyway for every request? If only to work out what to put in the Cookie header? My idea was mainly to give users (and privacy protection extensions) the ability to detect the existence of the CH state by keeping it in the same place as cookies, where there already exist UIs etc. for seeing/dealing with them. If a parallel system is implemented to manage CH state (with expiry etc.) then there would also be a need for similar UIs, API to support extensions etc. For cookies that already exists. It is true the scoping rules are horrible, but they do not need to be used for these special prefixes. The "secure" attribute already restricts scoping for some cookies. -- 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/307#issuecomment-287528345 ----==_mimepart_58ccfa76d5153_57213fa998e29c2c798ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Doesn't "the cookie monster" have to be consulted anyway for every reque= st? If only to work out what to put in the Cookie header?

My idea was mainly to give users (and privacy protection extensions) t= he ability to detect the existence of the CH state by keeping it in the sam= e place as cookies, where there already exist UIs etc. for seeing/dealing w= ith them.

If a parallel system is implemented to manage CH state (with expiry etc.= ) then there would also be a need for similar UIs, API to support extension= s etc. For cookies that already exists.

It is true the scoping rules are horrible, but they do not need to be us= ed for these special prefixes. The "secure" attribute already restricts sco= ping for some cookies.

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

= ----==_mimepart_58ccfa76d5153_57213fa998e29c2c798ad-- From nobody Mon Mar 20 07:40:50 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.393 X-Spam-Level: X-Spam-Status: No, score=-3.393 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=8ygvJnFcX3uOm1AlAKpn7uFsp6w=; b=PQFhCEhwv7vJlllk x3kS7NwfvD1RTg1Hp6lQaDKE6xoPnUNSQIXavIKNwNhU+6AnD9vXZl7y8stwIedM RkvLmg2XuAlSbaHZOom5hRt2Gyqkm2blLn+g7qspGw/51DKZzpaFb4/rr2wJhXa+ ShS3jOYvj5hpfNLSpGunvcB/pSU= Date: Mon, 20 Mar 2017 07:40:45 -0700 To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] origin frame race condition (not the obvious one) (#314) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58cfe9ed1c393_79a43fe54e08bc2c2132fa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2017 14:40:49 -0000 ----==_mimepart_58cfe9ed1c393_79a43fe54e08bc2c2132fa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 7540 has coalescing rules that are overruled by Origin frames - we all know that can't take effect until the origin frame(s) have been received at the client - so that's the basic race condition that we're comfortable with. But because the origin set is done one origin in one frame at a time, and there is no End-of-Set marker on it, the set can become initialized before it is complete upon receipt of the first frame. Initialization means any origin that will soon be in the set but has not yet been processed will not be coalesced onto this connection even if it meets the rules of 7540.. that's the state that is intended at the end of origin set processing, but this interim state seems counterproductive. The easiest thing to do seems to be to create some kind of checkpoint flag that means 'generation done for now'. -- 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/314 ----==_mimepart_58cfe9ed1c393_79a43fe54e08bc2c2132fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

7540 has coalescing rules that are overruled by Origin frames - we all know that can't take effect until the origin frame(s) have been received at the client - so that's the basic race condition that we're comfortable with.

But because the origin set is done one origin in one frame at a time, and there is no End-of-Set marker on it, the set can become initialized before it is complete upon receipt of the first frame. Initialization means any origin that will soon be in the set but has not yet been processed will not be coalesced onto this connection even if it meets the rules of 7540.. that's the state that is intended at the end of origin set processing, but this interim state seems counterproductive.

The easiest thing to do seems to be to create some kind of checkpoint flag that means 'generation done for now'.

—
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_58cfe9ed1c393_79a43fe54e08bc2c2132fa-- From nobody Mon Mar 20 15:48:02 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -9.795 X-Spam-Level: X-Spam-Status: No, score=-9.795 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=-2.796, 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, 20 Mar 2017 15:47:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490050077; bh=F8XigdkCupKSaog85f2J+rUKy1tp+KnANsjCiQaRaIg=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=o4XXXRlkVc9/x/hforAqgcECJp1iPNoUqbwZKskq6Ja+s36H/94u9LDq3sB0wor5r BXd9qFu4dMeqhJFiNyoyIseh+r+rpe39cgwSk8TCTsriJS0Vo4JRzzzACMDqoNGLWa B1YaJNKkDYZP/1WAHgCw8ZE8yLdjHEnetfY+Xndo= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] origin frame race condition (not the obvious one) (#314) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d05c1d6174c_44213f9af80cbc3c169685"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2017 22:48:01 -0000 ----==_mimepart_58d05c1d6174c_44213f9af80cbc3c169685 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It's not one-origin-per-frame; it can contain many. I think we've discussed this; both for Origin and Cache Digest. The problem is that if the COMPLETE (or whatever we call it) flag isn't set, how long does the client wait around for? We'd have to be very careful to make sure that the semantics are "more ORIGIN frames immediately following", rather than "wait around, I might have some more for you in a bit." Given that an ORIGIN frame can convey quite a few origins (unless you've restricted maximum frame size) is this enough of an issue to justify the mechanism? -- 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/314#issuecomment-287922128 ----==_mimepart_58d05c1d6174c_44213f9af80cbc3c169685 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It's not one-origin-per-frame; it can contain many.

I think we've discussed this; both for Origin and Cache Digest. The pr= oblem is that if the COMPLETE (or whatever we call it) flag isn't set, ho= w long does the client wait around for? We'd have to be very careful to m= ake sure that the semantics are "more ORIGIN frames immediately following= ", rather than "wait around, I might have some more for you in a bit."

Given that an ORIGIN frame can convey quite a few origins (unless you'= ve restricted maximum frame size) is this enough of an issue to justify t= he mechanism?

&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_58d05c1d6174c_44213f9af80cbc3c169685-- From nobody Mon Mar 20 16:52:35 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -9.795 X-Spam-Level: X-Spam-Status: No, score=-9.795 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=-2.796, 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, 20 Mar 2017 16:52:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490053951; bh=dIxFUiSeaIuetbLopMrJjxwDq0HLE9vl+JCf0/FgI8o=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gohstPrIFfj2TJUF64EvA1zNvb1/aXmG7+wkF5uH1YSRkz3bkxapIPNbWbC1JnUec QqqaOnicg2lVOvOy5XCCq80beEA83qeNoP5Y012vpOmwIsQWZRVf7MgppKMdQZWLu3 ygWTyXdK1KPyFJsMSHUdNs2ejKg1gwo7h8dE/zYk= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] origin frame race condition (not the obvious one) (#314) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d06b3f3b1d8_549f3fdc31ccdc2c964c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2017 23:52:34 -0000 ----==_mimepart_58d06b3f3b1d8_549f3fdc31ccdc2c964c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hmm, without a COMPLETE signal, the client might not coalesce even if it could. That's suboptimal but it resolves fairly quickly once ORIGIN arrives. The client can interrupt an in-progress connection attempt and coalesce once it learns the new origin. As @mnot observes, if you add a COMPLETE signal, the client can know that it might wait (by testing that the server is authenticated for the origin), but how long does it wait? I think that I would rather just fall back to the non-coalescing mode and interrupt if the ORIGIN frame arrives in time. Note that in 1-RTT TLS 1.3 the server speaks first, so the race can be reduced somewhat. -- 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/314#issuecomment-287934237 ----==_mimepart_58d06b3f3b1d8_549f3fdc31ccdc2c964c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hmm, without a COMPLETE signal, the client might not coalesce even if = it could. That's suboptimal but it resolves fairly quickly once ORIGIN a= rrives. The client can interrupt an in-progress connection attempt and c= oalesce once it learns the new origin.

As @mnot observes, if you add a COMPLETE signal, the client can know that it mig= ht wait (by testing that the server is authenticated for the origin), but= how long does it wait? I think that I would rather just fall back to th= e non-coalescing mode and interrupt if the ORIGIN frame arrives in time.<= /p>

Note that in 1-RTT TLS 1.3 the server speaks first, so the race can be= reduced somewhat.

&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_58d06b6dafbee_58cf3ff6b5d9bc3c1073b7-- From nobody Mon Mar 20 17:22:31 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=xzZFHTqTDAM73rfmzwlUO/Ul3Y8=; b=rUdVu1Em7kSaiK++ 9XxjsqZ2Ql9NDgvKXQOUGJyXRUnEKy8Il56ga0hV4aekXNUXUF212WQJsOXJ3zLA ZWSzaofb9HTG5+dp/FF1WZiscpHTM3KTP0xDSFi9FIcy6kwR/8abA3P/IK8U4pP+ si6UHBByksddI/+1oC5JyuXF6PM= Date: Mon, 20 Mar 2017 17:22:25 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] origin frames and 0-RTT (#315) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d07241bf717_2d0d3f926dea3c308411b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 00:22:31 -0000 ----==_mimepart_58d07241bf717_2d0d3f926dea3c308411b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Dup of #291. -- 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/315#issuecomment-287938934 ----==_mimepart_58d07241bf717_2d0d3f926dea3c308411b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Dup of #291.

—
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_58d07241bf717_2d0d3f926dea3c308411b-- From nobody Mon Mar 20 17:22:38 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=EWeo7b2J/JIhOSl5NbwqkgpvZMg=; b=a5EjwwuOMCvR6xoF Yhlarv4O0y3fIF54gzuuYjQ9T7gYJ0TNj7HJ5DsVQ4BWrJlvOsLN3Ti4gwYXQxfM G7jNvSeL6hP4OSeIpbFGSy6XCD5j9SxsFwERsXhUWdANn+WQCrLEqJ35pRWV8Dqe 1hspiKpizBAO/RpV2tci614YsEc= Date: Mon, 20 Mar 2017 17:22:25 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] origin frames and 0-RTT (#315) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d07241f325d_2d673fbeb85c9c3c21372a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 00:22:32 -0000 ----==_mimepart_58d07241f325d_2d673fbeb85c9c3c21372a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #315. -- 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/315#event-1007734860 ----==_mimepart_58d07241f325d_2d673fbeb85c9c3c21372a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #315.

—
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_58d07241f325d_2d673fbeb85c9c3c21372a-- From nobody Mon Mar 20 17:26:01 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=STQJH7/Qd2u4G3V5S2uD2YaRqU4=; b=iR/NA5w9M23KHYAu eEjdoHKyK5S+0nU5aQ6lIQyStwLrt4hmghmOmxWfQKpo0yhxkDfBKbW7/8YZ6qwH bgS+9NwiLm7JjsSpNpkLJt0Ea6K/xVWxVnPvgXKWxf7tW49ltMkooDFGsmG9wrOD quKe6RD/AKZ7qqm3laADz2LU0BY= Date: Mon, 20 Mar 2017 17:25:42 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Persistence (#291) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d0730670830_4d543f8dc140fc3414152"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 00:25:59 -0000 ----==_mimepart_58d0730670830_4d543f8dc140fc3414152 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit origin set is defined per connection not (ironically) per origin.. so I'm not sure how this would work. -- 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/291#issuecomment-287939402 ----==_mimepart_58d0730670830_4d543f8dc140fc3414152 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

origin set is defined per connection not (ironically) per origin.. so I'm not sure how this would work.

—
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_58d0730670830_4d543f8dc140fc3414152-- From nobody Mon Mar 20 17:28:42 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=DIavqSiHMWZt3JdsO15ekTyxq88=; b=vwwByI9MaeiJeAAs 1dEWI2F/JPq4RAwF3azvhp+IzQMGKhBO3CTEBZkxaix+1AnIg+YnseL/lgVIOG5x /mVG/aZhNz/PCo5I2uf7812h6Qw4Lpm5ROJY6H2inrcK9lhNkyev6gSD7K52ImXh xBCbTvBTmlGQLMgcg0ACIfg6VDE= Date: Mon, 20 Mar 2017 17:28:37 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Persistence (#291) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d073b5436ec_76863f98d35c5c3c1108e1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 00:28:40 -0000 ----==_mimepart_58d073b5436ec_76863f98d35c5c3c1108e1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 2 loadbalanced hosts could have different sets of certs even if they answered to the same SNI on the same (public) IP.. I don't know how you could persist 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/291#issuecomment-287939805 ----==_mimepart_58d073b5436ec_76863f98d35c5c3c1108e1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

2 loadbalanced hosts could have different sets of certs even if they answered to the same SNI on the same (public) IP.. I don't know how you could persist that.

—
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_58d073b5436ec_76863f98d35c5c3c1108e1-- From nobody Mon Mar 20 17:34:39 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.392 X-Spam-Level: X-Spam-Status: No, score=-3.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=EbUWJ8eYp9GB30TBNHHgqWz9qL0=; b=thsV7bIuVR7zMNYV Vi0BKhG56/vmSaYmb0+cTPfJdIN9TLhSTQzOEbZT0tmGkyVd+ybVAjThQA2iZR6T 4yesCTik7nHbWVlb05COjHuP0kQE4S2Ij+ZLgUHrfi0Tf8/BoSPM1l1N9qE8Cx7C 2oHLUNOuHPJzgwpxCieV7ZBolK8= Date: Mon, 20 Mar 2017 17:33:40 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Persistence (#291) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d074e4ee993_193e3f83bbf3fc2c44626"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 00:34:38 -0000 ----==_mimepart_58d074e4ee993_193e3f83bbf3fc2c44626 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yeah. I think there are a lot of ways we could mess up here. If you think of the binding as between a set of origins and a connection, AIUI what's being posited here is that it might be interesting to re-attach that binding to a new connection. It might be interesting if the server could associate a token with a particular set, and then have a dance where its use can be explicitly negotiated. Question is whether it's worth the effort (we've already tried to over-engineer this thing a few times). -- 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/291#issuecomment-287940593 ----==_mimepart_58d074e4ee993_193e3f83bbf3fc2c44626 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yeah. I think there are a lot of ways we could mess up here.

If you think of the binding as between a set of origins and a connection= , AIUI what's being posited here is that it might be interesting to re-atta= ch that binding to a new connection.

It might be interesting if the server could associate a token with a par= ticular set, and then have a dance where its use can be explicitly negotiat= ed. Question is whether it's worth the effort (we've already tried to over-= engineer this thing a few times).

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

= ----==_mimepart_58d074e4ee993_193e3f83bbf3fc2c44626-- From nobody Mon Mar 20 17:35:24 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=iYErq18Y0bY7pOQqokMxUH+V+1A=; b=Yl2p/2KFzYkhScSr 2yIuh8uwHODNqvyeVH6nuicLCPYHjxFNTE5Yun1id83VnSKow6d3ls47lwPxmbw9 4UPbjiITjXQ9M/+LpX0Ohnzz4BMZ8Smo4AsIWVXt8kqBLSXzejMUydrB0J8BeSve wbffwaO5U1T+4F6fevNmjYoD3p4= Date: Mon, 20 Mar 2017 17:35:20 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] origin frame race condition (not the obvious one) (#314) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d07548129cd_6af03f926dea3c30150124"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 00:35:23 -0000 ----==_mimepart_58d07548129cd_6af03f926dea3c30150124 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit multiples definitely help - I forgot to acknowledge that. But the general case is N frames. I think this bothers me more than the base race condition of waiting for the ORIGIN frame to arrive, because it actually undoes 7540 quite accidentally. imagine wanting to coalesce a set and having it setup via the usual DNS rules.. you want to also advertise that same set via origin to get the privacy and no-lookup wins.. halfway through you lose any coalescing for part of the set :( not sure what the big deal with waiting is. That's state you're going to have anyhow - you're just not committing it yet. -- 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/314#issuecomment-287940865 ----==_mimepart_58d07548129cd_6af03f926dea3c30150124 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

multiples definitely help - I forgot to acknowledge that. But the genera= l case is N frames.
I think this bothers me more than the base race condition of waiting for th= e ORIGIN frame to arrive, because it actually undoes 7540 quite accidentall= y.

imagine wanting to coalesce a set and having it setup via the usual DNS = rules.. you want to also advertise that same set via origin to get the priv= acy and no-lookup wins.. halfway through you lose any coalescing for part o= f the set :(

not sure what the big deal with waiting is. That's state you're going to= have anyhow - you're just not committing it yet.

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

= ----==_mimepart_58d07548129cd_6af03f926dea3c30150124-- From nobody Mon Mar 20 17:54:01 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ZmvjrpboEjOFdP7/VJfk9oIth6Y=; b=nKUO9Eu3gp9QV7dQ VXKflv9rUVUZ1XtaoXMkpo+SUyXOt13dZvYWQ6eM73huq1BJag2ixhYuZs9C9v6X Judig5mw67BQ61dYFe17nsXAZCvPo9z2o6qrGA3ERf4Gvuw/AloBronzDsIBJ3Es bN5sXnis1Wf4cuMtsA6GeNoEzXc= Date: Mon, 20 Mar 2017 17:53:56 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] origin frame race condition (not the obvious one) (#314) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d079a46c308_51c53fde0fa37c306576c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 00:54:00 -0000 ----==_mimepart_58d079a46c308_51c53fde0fa37c306576c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I can see that we introduced something new with the DNS rule change -- now there's a point in time where the client has to decide whether or not to resolve DNS for a given origin. -- 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/314#issuecomment-287944120 ----==_mimepart_58d079a46c308_51c53fde0fa37c306576c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I can see that we introduced something new with the DNS rule change -- now there's a point in time where the client has to decide whether or not to resolve DNS for a given origin.

—
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_58d079a46c308_51c53fde0fa37c306576c-- From nobody Tue Mar 21 18:24:47 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.393 X-Spam-Level: X-Spam-Status: No, score=-3.393 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=xCtQ+D7HevkOnxvDrufw9cjSOVc=; b=mzT1kaTiHKPhqXRe uNSBdd6azBwXHysc7xWKB2ylCBjQFNZ3t6It9gZIPiyjYUpjntrbCFiMhsq/yoHa FxGnJg4Dlw3Ta2GlyqbSV6rQLztZlTfkdN2hBSk6dtC2Ghg3x9WmzEScz9xkbOuq KLEf8MK9GPVXFKlUIM5eC8aszDE= Date: Tue, 21 Mar 2017 18:24:42 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] define Accept-CH-Lifetime (#313) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d1d25ab5fba_30da3fe371c7fc38758e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Mar 2017 01:24:46 -0000 ----==_mimepart_58d1d25ab5fba_30da3fe371c7fc38758e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Looks good overall. `Accept-CH-Lifetime` changes the semantics of `Accept-CH`. Not only does it effectively put `Accept-CH` on subsequent responses from the same origin for the given lifetime, it **also** suggests that Client Hints should be added to requests _to_ that origin, no matter where the requesting page has come from. Not a problem, but right now it's conveyed almost as an aside. This needs to be clearly specified so it isn't missed / misunderstood. -- 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/313#issuecomment-288270322 ----==_mimepart_58d1d25ab5fba_30da3fe371c7fc38758e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Looks good overall.

Accept-CH-Lifetime changes the semantics of Accept-CH= . Not only does it effectively put Accept-CH on subsequ= ent responses from the same origin for the given lifetime, it also<= /strong> suggests that Client Hints should be added to requests to= that origin, no matter where the requesting page has come from.

Not a problem, but right now it's conveyed almost as an aside. This need= s to be clearly specified so it isn't missed / misunderstood.

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

= ----==_mimepart_58d1d25ab5fba_30da3fe371c7fc38758e-- From nobody Thu Mar 23 11:42:45 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Cy4TIs5DeVNXnPu476jS65LAcb0=; b=e4NtPi6ph6VvHXOl 2Za9yVlz6sOsdKl3YZBLzQj7FUwEnFQDvYKvGsphBkdYR4Fnm+h89fIk9t1ZxDjH DKymROiMIRtyNXTQVuLWqQRzDxP4UjscTprprS/1iRWcW4spluqqeoZzsMfY/6Bu yjFCao7ziGpnzK0wvzZMihVFOK4= Date: Thu, 23 Mar 2017 11:42:22 -0700 To: httpwg/http-extensions Cc: Push In-Reply-To: References: Subject: Re: [httpwg/http-extensions] define Accept-CH-Lifetime (#313) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d4170e38a86_62983fae6373dc2c18307c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Mar 2017 18:42:44 -0000 ----==_mimepart_58d4170e38a86_62983fae6373dc2c18307c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @igrigorik pushed 1 commit. 937227c clarify accept-ch-lifetime scope -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/httpwg/http-extensions/pull/313/files/22fb1ddb9c8d41f29f5219a252683fde953ae859..937227cca3bccdece4cccc05f330b261c91be2ea ----==_mimepart_58d4170e38a86_62983fae6373dc2c18307c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igrigorik pushed 1 commit.

  • 937227c clarify accept-ch-lifetime scope

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

----==_mimepart_58d4170e38a86_62983fae6373dc2c18307c-- From nobody Thu Mar 23 11:43:04 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=+2oJchoRrRb7B4qgpwaTNyf8cqw=; b=iWL0DA+ixvIK4iIU 70QAShf3zpwHasyggwiZCgjUigOqrXzlhvFScThUrfJV6oms1xLx+8kDD6U89GfZ HQxRR/sSjFPk7xz86juvF3EVjZQqhA8HwLrMCGKh6E/KeBwwG53Ho1cMiObDH4Q2 1AC2t6aMJvVp897CbeIg+2npoPc= Date: Thu, 23 Mar 2017 11:43:00 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] define Accept-CH-Lifetime (#313) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d4173470e6b_4ae63fc810e07c30142950"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Mar 2017 18:43:03 -0000 ----==_mimepart_58d4173470e6b_4ae63fc810e07c30142950 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mnot updated, PTAL. -- 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/313#issuecomment-288822022 ----==_mimepart_58d4173470e6b_4ae63fc810e07c30142950 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mnot updated, PTAL.

—
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_58d4173470e6b_4ae63fc810e07c30142950-- From nobody Sun Mar 26 10:11:21 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.251 X-Spam-Level: X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=LgZ2g6DUA92mxOObM6sYh7pBUCA=; b=CmTINx0STC0k39yu kYtpjtxCA6+QtFpbTelIsqKR3zokb9RaJVrAZIUKKBNRLVURrBBwF7v4zUiwoUam Ch0+7SorrMT9WPTiLGrHkkr66te9fUWN6eV7YRG7I3zUj/rJZy77qKWwUsgVEtfb wSSIpEm9NO6yK2AQygd3QlqUGXM= Date: Sun, 26 Mar 2017 10:11:13 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] define Accept-CH-Lifetime (#313) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d7f6318cd04_40263feec14ebc3c1767e3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 17:11:18 -0000 ----==_mimepart_58d7f6318cd04_40263feec14ebc3c1767e3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mnot approved this pull request. This is better. -- 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/313#pullrequestreview-29074485 ----==_mimepart_58d7f6318cd04_40263feec14ebc3c1767e3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mnot approved this pull request.

This is better.

—
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_58d7f6318cd04_40263feec14ebc3c1767e3-- From nobody Sun Mar 26 10:30:52 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.251 X-Spam-Level: X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=/EOirOgfAOe46RqVF+wLkZTSkJ8=; b=toOMvgL5nIv8UB9H 6g0SZO2X1yuS6ZGvIrN209UR645F0DhbQgwF1mLrC63ljzbAXFwTTpRcR/EkyGoA vztVp8UFeyepBwS9cHf5kRaxIqtWZrddyI2+RG+qsjcYuwMcvFgvABccExiXREGI Zjj2IParhMrupiNVP6BOis7Pnbw= Date: Sun, 26 Mar 2017 10:30:48 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] define Accept-CH-Lifetime (#313) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d7fac822456_10e83ff68032dc30352a0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 17:30:51 -0000 ----==_mimepart_58d7fac822456_10e83ff68032dc30352a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks Mark! -- 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/313#issuecomment-289300643 ----==_mimepart_58d7fac822456_10e83ff68032dc30352a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Thanks Mark!

—
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_58d7fac822456_10e83ff68032dc30352a0-- From nobody Sun Mar 26 10:31:07 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.403 X-Spam-Level: X-Spam-Status: No, score=-0.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Kyl+ZzfvkihYioeN0Qiv3s8SRPQ=; b=XGIOWzs1+vEXafA3 hvrfXlbyi+eZZInl8Q7niHiVV+efq7pIkSVXIpvhzlOwHBUxBy5rm31OYkj8s2IZ rOZDARPYjHh/pLKSl7L3eszcBwGaJbL/5Lhw8lAxhKiBP6KuZajkBxZtCdtVNm+F lRQb2X2j4ezMpu4WMs7gT+FvhYA= Date: Sun, 26 Mar 2017 10:31:01 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] define Accept-CH-Lifetime (#313) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d7fad57d789_7cdd3fc7d8cbfc34606c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 17:31:05 -0000 ----==_mimepart_58d7fad57d789_7cdd3fc7d8cbfc34606c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #313. -- 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/313#event-1015747971 ----==_mimepart_58d7fad57d789_7cdd3fc7d8cbfc34606c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #313.

—
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_58d7fad57d789_7cdd3fc7d8cbfc34606c8-- From nobody Sun Mar 26 10:31:29 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.179 X-Spam-Level: X-Spam-Status: No, score=-3.179 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=evA60hPZjQ/0H83/2GQE2srFlT8=; b=gT8YbjeXgUK41r6V 3swDQo6uaxU7dDbwD5F5YXU4iIVaPvd7WJ1DTr00RMdnPl19SVur03SSAbr5BM4j fzc3yNvziUdfipWLQuiil+nZemt4TYBi+Bt2/hYY7G//bBN8KqeHpt0VP7kNc/h5 dbRw1QTX+nH4bKCwrZbWGqSATJE= Date: Sun, 26 Mar 2017 10:31:01 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Scoping of Accept-CH (#307) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d7fad57c926_53ca3fc66fb65c2c8941e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 17:31:28 -0000 ----==_mimepart_58d7fad57c926_53ca3fc66fb65c2c8941e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #307 via #313. -- 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/307#event-1015747970 ----==_mimepart_58d7fad57c926_53ca3fc66fb65c2c8941e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #307 via #313.

—
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_58d7fad57c926_53ca3fc66fb65c2c8941e-- From nobody Sun Mar 26 10:31:45 2017 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, 26 Mar 2017 10:31:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490549501; bh=DXi1SvnjIfhkCZzr4DFJOdFN1li4dNoqiGdavteqTgw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zCPZSV/RWI1E0V/CSLLnO+vylgtd3tmCCL7hAAtKLlhHCj/wNe0uNd6hRFh3Htd6R i9jfGGUDHJ10D3W/nnNBHP10FXbjCkkYBKYNwoMpRTNKkJ/Ax1+bSA75gBWdSbWTgN oYriWJ39DoGhbk/NiALWLB4CFyNv1Xcyf505sXXw= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Allow servers to specify max-age in the client hints header (#306) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d7fafd1e637_74533fc66fb65c2c1551de"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 17:31:44 -0000 ----==_mimepart_58d7fafd1e637_74533fc66fb65c2c1551de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #306. -- 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/306#event-1015748257 ----==_mimepart_58d7fafd1e637_74533fc66fb65c2c1551de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #306.

—
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_58d7fafd1e637_74533fc66fb65c2c1551de-- From nobody Sun Mar 26 10:31:49 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.179 X-Spam-Level: X-Spam-Status: No, score=-3.179 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-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 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=X5fIfGI6aCZoJohVuzsvDHpZ4rQ=; b=EjaHLZkWW3P4heC0 bGbstQc48Qd6bsa+3TJNbLBW5N4dz4fbLOOV6Ok3mYjHzw02TIQE/94OP3vV3saO zhyrUf9l3fEpp8Irh5O3iIAE+Iy5gv1G81vmSiUutDTD+8W3z/Wm79eq+dXVBlC2 aRMlS9r8DOHn5KlZAeOVoSd3zNM= Date: Sun, 26 Mar 2017 10:31:41 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Allow servers to specify max-age in the client hints header (#306) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58d7fafd9b58_24673feec14ebc3c9877"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 17:31:44 -0000 ----==_mimepart_58d7fafd9b58_24673feec14ebc3c9877 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Resolved via https://github.com/httpwg/http-extensions/pull/313. -- 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/306#issuecomment-289300715 ----==_mimepart_58d7fafd9b58_24673feec14ebc3c9877 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Resolved via #313.

—
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_58d7fafd9b58_24673feec14ebc3c9877-- From nobody Thu Mar 30 13:57:01 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.02 X-Spam-Level: X-Spam-Status: No, score=-7.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_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: Thu, 30 Mar 2017 13:56:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490907396; bh=OWCQkOXdLWvp4JbkJdXlpyLWN5s2bt2vDm6kIUA2Lf4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hG9GPQamKFpw1jS9nHJzgDwWnGaM4f1uilagLoCiSKupKGw0jS1/XMNVVLkEs2752 rogqbO+hkIMh+2UJxbzIhFPQEc+42zca0VFOhZ1Fxho61zDxvoiq/4tXGWhptzhQcG MbnRmcV5cvTLXwsVzbwoz2kYk+hRSRfxsDQov13w= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Cache digest and scoping (#216) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58dd71043347c_65603f97bba69c34154488"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 20:56:49 -0000 ----==_mimepart_58dd71043347c_65603f97bba69c34154488 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @tombergan > Cache digests should not worsen the privacy problem compared to current H2. If cache digests are reducible to cookies, and managed as cookies, then we can argue that the privacy problem hasn't worsened. I agree that cache digests should not worsen the privacy problem. However, I will also argue that cache digests _in current form_ does not worsen the privacy problem since it is something that can be and is implemented using existing technology (stated below), and that there is no need to try to adopt the cookie model which would have issues as @mnot points out. Cache digest can be (and already is) implemented using Service Worker. The only differences between a Service Worker-based implementation and the HTTP/2 frame-based implementation is that the frame-based implementation is more efficient (in HTTP/2 frame-based approach, the digest needs to be sent only once per connection, whereas for Service Worker-based or cookie-based implementation, a client needs to send a digest per every request), and that the digest more accurately reflects the state of the cache (Service Worker cache is located in front of the web browser cache, so a digest of Service Worker cache does not reflect what exists in the browser's cache). -- 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/216#issuecomment-290542538 ----==_mimepart_58dd71043347c_65603f97bba69c34154488 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@tombe= rgan

Cache digests should not worsen the privacy problem compared to curren= t H2. If cache digests are reducible to cookies, and managed as cookies, = then we can argue that the privacy problem hasn't worsened.

I agree that cache digests should not worsen the privacy problem.

However, I will also argue that cache digests in current form= does not worsen the privacy problem since it is something that can be an= d is implemented using existing technology (stated below), and that there= is no need to try to adopt the cookie model which would have issues as <= a href=3D"https://github.com/mnot" class=3D"user-mention">@mnot point= s out.

Cache digest can be (and already is) implemented using Service Worker.= The only differences between a Service Worker-based implementation and t= he HTTP/2 frame-based implementation is that the frame-based implementati= on is more efficient (in HTTP/2 frame-based approach, the digest needs to= be sent only once per connection, whereas for Service Worker-based or co= okie-based implementation, a client needs to send a digest per every requ= est), and that the digest more accurately reflects the state of the cache= (Service Worker cache is located in front of the web browser cache, so a= digest of Service Worker cache does not reflect what exists in the brows= er's cache).

&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_58dd71043347c_65603f97bba69c34154488-- From nobody Thu Mar 30 17:26:42 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=5gUKdJnGbb9F9WWM/VSBrs4QqEA=; b=JrA1mrX30MNziEmp rCNLCSHHSIqU9lV8dtxSIff4Nmnd9G67UVLxGCbzapQxcwXG5WVepH1RbyiYtKP3 Tv7anAnc/KDmDXZmqBpxZQ9l4ExwUYUmczE0RYHUlbAtkFzZnSxaBPGPuOJfsj60 YBqg8qE5DAAg3VNFWL3SoLu6e8Y= Date: Thu, 30 Mar 2017 17:26:36 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Cache digest and scoping (#216) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58dda23c81207_1c9a3fa28c6a9c302383f6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 00:26:40 -0000 ----==_mimepart_58dda23c81207_1c9a3fa28c6a9c302383f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We completely agree. I was making a writing suggestion: if you can write the RFC in such a way that it's obvious that the proposed cache digest frame is equivalent to cookies, then you can more easily argue that you're not introducing any privacy concerns. [1] My specific suggestion is for the browser to create a "cookie" each time it caches a response, where that cookie is treated like any other cookie with a few small changes (see the list of six items in my prior comment). Rephrasing the explanation in terms of cookies also makes it obvious where privacy holes may arise. For example, if a browser supports "normal" and "incognito" modes that use different cookie jars but the same cache, the browser needs to attach the "cache cookies" to the appropriate cookie jar rather than to the cache, otherwise there may be information leakage across browser modes. Does that sound reasonable? Contrast this to [Section 4](https://tools.ietf.org/html/draft-ietf-httpbis-cache-digest-01#section-4), which is currently kind of hand-wavy. [1] Even if you rephrase the explanation in terms of cookies, privacy concerns are still likely to arise since the cookies are created automatically by the browser rather than manually by the server, but that is a separate issue. -- 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/216#issuecomment-290582254 ----==_mimepart_58dda23c81207_1c9a3fa28c6a9c302383f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

We completely agree. I was making a writing suggestion: if you can write= the RFC in such a way that it's obvious that the proposed cache digest fra= me is equivalent to cookies, then you can more easily argue that you're not= introducing any privacy concerns. [1] My specific suggestion is for the br= owser to create a "cookie" each time it caches a response, where that cooki= e is treated like any other cookie with a few small changes (see the list o= f six items in my prior comment).

Rephrasing the explanation in terms of cookies also makes it obvious whe= re privacy holes may arise. For example, if a browser supports "normal" and= "incognito" modes that use different cookie jars but the same cache, the b= rowser needs to attach the "cache cookies" to the appropriate cookie jar ra= ther than to the cache, otherwise there may be information leakage across b= rowser modes.

Does that sound reasonable? Contrast this to Section 4, wh= ich is currently kind of hand-wavy.

[1] Even if you rephrase the explanation in terms of cookies, privacy co= ncerns are still likely to arise since the cookies are created automaticall= y by the browser rather than manually by the server, but that is a separate= issue.

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

= ----==_mimepart_58dda23c81207_1c9a3fa28c6a9c302383f6-- From nobody Fri Mar 31 04:58:01 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.796 X-Spam-Level: X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=iyg7lDX2NgbNsYfO9mwmdCoSNIc=; b=biEQOEkssPLCJJMa HGZtjNifVp5oK5fjnilKH5QebUmt5arPwbdT5zVGUuvRZevBiGiKwTjUuzec0Wwy c/OMG3fGDz79zmKG9CBznZyu5b2UhmeStK+dG3kaGxQrJHHAGzoIzRH6DQ+oV9SR ZjHB3mxAExNK+HeclW1DGmBXsMU= Date: Fri, 31 Mar 2017 04:57:43 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Cache digest and scoping (#216) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de4437228c7_44183fd04aa09c2c1986a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 11:58:00 -0000 ----==_mimepart_58de4437228c7_44183fd04aa09c2c1986a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @tombergan > I realize cookies are kind of weird because they don't exactly follow the same-origin policy. Maybe a better analogy would be local storage? Thank you for the suggestion. I agree that it would be worthwhile to suggest similarity to existing mechanism in Security Considerations. Having that would help the readers understand the issues. I assume that the existing mechanism we would refer to to be Service Worker (and its cache). That is natural since we are likely to have an appendix explaining how to implement Cache Digests using Service Workers (see #256). -- 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/216#issuecomment-290693285 ----==_mimepart_58de4437228c7_44183fd04aa09c2c1986a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@tomberg= an

I realize cookies are kind of weird because they don't exactly follow th= e same-origin policy. Maybe a better analogy would be local storage?

Thank you for the suggestion.

I agree that it would be worthwhile to suggest similarity to existing me= chanism in Security Considerations. Having that would help the readers unde= rstand the issues.

I assume that the existing mechanism we would refer to to be Service Wor= ker (and its cache). That is natural since we are likely to have an appendi= x explaining how to implement Cache Digests using Service Workers (see #256).

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

= ----==_mimepart_58de4437228c7_44183fd04aa09c2c1986a-- From nobody Fri Mar 31 07:33:19 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -8.177 X-Spam-Level: X-Spam-Status: No, score=-8.177 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=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 07:33:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490970795; bh=vIky31+2lah7vTpFTTfeS8vapRTk4qcQB3oV8LdGsXY=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=tEFgtioDR4vbkUHDb+qe3dxIqSgTocv49/seBHcabWOUr8j24Snboq/qAlyYFf89Q 9HnQ1UslVGgnzrXK4ZADhDuhYTUnmX/Ddyfo2Ypf1+pJTrGvfnr52PACSVBJyQ2/Qk fMKtYTM2BIh3g1mkPh7uI0HPEcBeh3bcAzBwgTx0= To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de68ab82a8d_6aad3f939c6dfc301278d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:33:18 -0000 ----==_mimepart_58de68ab82a8d_6aad3f939c6dfc301278d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Roy noted that the header syntax is copied from Cookies, which is an abomination. We have the header-structure draft, which this could follow. Many of the other recent header fields that use comma-separated lists with semi-colon-separated parameter maps could serve as an example. -- 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/316 ----==_mimepart_58de68ab82a8d_6aad3f939c6dfc301278d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Roy noted that the header syntax is copied from Cookies, which is an abomination.

We have the header-structure draft, which this could follow. Many of the other recent header fields that use comma-separated lists with semi-colon-separated parameter maps could serve as an example.

—
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_58de68ab82a8d_6aad3f939c6dfc301278d-- From nobody Fri Mar 31 07:35:50 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=1wXngTqLUxC0Mzf5OlBA6UhAEnc=; b=laYFB3LWOYlYBcS7 M+v2mP7XICWy8Rl5YfRbZrcMFwDF9Y15AX3fcduK02W/ouyM7rtJSmc1bM0+dgGn cAH2SsOVBTBGSqbzttAK3UaNMvJnimnpKm5u1Y3kM3bOv4XCmumVoF5mYE6DP7tH VFgHHOlG7eyimypP0E24R4VSKKk= Date: Fri, 31 Mar 2017 07:35:13 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6921927f_4b303fb891771c381907b7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:35:46 -0000 ----==_mimepart_58de6921927f_4b303fb891771c381907b7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Does it? I don't think so: > Expect-CT-Directives = directive *( OWS ";" OWS directive ) > directive = directive-name [ "=" directive-value ] > directive-name = token > directive-value = token / quoted-string -- 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/316#issuecomment-290729250 ----==_mimepart_58de6921927f_4b303fb891771c381907b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Does it? I don't think so:

Expect-CT-Directives =3D directive *( OWS ";" OWS directive )
directive =3D directive-name [ "=3D" directive-value ]
directive-name =3D token
directive-value =3D token / quoted-string

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

= ----==_mimepart_58de6921927f_4b303fb891771c381907b7-- From nobody Fri Mar 31 07:36:50 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.25 X-Spam-Level: X-Spam-Status: No, score=-3.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=qv5BOcrDM9hg4FRhQJieAs9HvEI=; b=hrO5hfDtcRWDk7wJ 6yie2wM56GTCZOgg9bGXLiNUQhBFe0h1LqvDjT4GbIWQUgap4ZlWNkRZzuL1CLLO fC7ANKSklRaFXEniSraEfyB/DDE7eHtTu5x3xO9i/G+q6YFCVAqsIzjMT/crqXkU +o3jqvQHn3f17qEdIE39kJrOMO4= Date: Fri, 31 Mar 2017 07:36:36 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6974a608c_c6c3f8c96163c3c18924e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:36:49 -0000 ----==_mimepart_58de6974a608c_c6c3f8c96163c3c18924e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit What is the definition for `Expect-CT` itself? Because you are right, this looks fine. -- 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/316#issuecomment-290729633 ----==_mimepart_58de6974a608c_c6c3f8c96163c3c18924e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

What is the definition for Expect-CT itself? Because you are right, this looks fine.

—
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_58de6974a608c_c6c3f8c96163c3c18924e-- From nobody Fri Mar 31 07:37:35 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -8.249 X-Spam-Level: X-Spam-Status: No, score=-8.249 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=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 07:37:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490971047; bh=X60bmsTZvVOGOoT88xUVXBmv8NfvW3jghr5osw9qTpY=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=TlRpg4HQBWNJqZk0mhCyMHYLdV3nEplufDbFJZSEIOypy2dR4xgLxRkq6vt75Lb3r pXCfcB4HvtM8ZgMpMP6jZMrE2o5t64donyeMN372gZI3SQIgMrej24sR+kRWdP3Bkq oZgEEq8cljGzm4QXiNFCOyX29CJx6RzMO0GTzlCY= To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Request header for Expect-CT (#317) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de699ed8bb7_55fa3fce8fc55c2c1692dc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:37:34 -0000 ----==_mimepart_58de699ed8bb7_55fa3fce8fc55c2c1692dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A request header for Expect-CT would allow servers to know how many clients actually support Expect-CT and might allow us to deprecate this header in the future. -- 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/317 ----==_mimepart_58de699ed8bb7_55fa3fce8fc55c2c1692dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

A request header for Expect-CT would allow servers to know how many clients actually support Expect-CT and might allow us to deprecate this header in the future.

—
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_58de699ed8bb7_55fa3fce8fc55c2c1692dc-- From nobody Fri Mar 31 07:38:01 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -8.177 X-Spam-Level: X-Spam-Status: No, score=-8.177 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=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 07:37:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490971076; bh=zp/7TqofHHRx24i1i5Kj4EYPfcan52mTDQQc4EyabZc=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NqehWyC64T+iQ8sua1EUaIWNkEy1oExXtoivUkN/j9VvnjU7cHWsalKn8LHLUH+5D kAHyctPZDy+tJMGowJhZBX6OgUiH4HijJDrO0A1fTFwSSMX+zF1hNmBhRnYewSru8S ogmS7oISl4XpNrhTRPRL6iKzgAuhMAqiyBa4xsCY= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Persistence (#291) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de69bb81204_55493fce8fc55c2c27819f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:38:00 -0000 ----==_mimepart_58de69bb81204_55493fce8fc55c2c27819f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agreed that persisting across connections seems like it may add too much risk and complexity and further additional interactions, especially if we include hosts not found through the DNS. (And doesn't even make sense with some of the changes made to not always rely on DNS.) -- 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/291#issuecomment-290729979 ----==_mimepart_58de69bb81204_55493fce8fc55c2c27819f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Agreed that persisting across connections seems like it may add too mu= ch risk and complexity and further additional interactions, especially if= we include hosts not found through the DNS. (And doesn't even make sens= e with some of the changes made to not always rely on DNS.)

&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_58de69bb81204_55493fce8fc55c2c27819f-- From nobody Fri Mar 31 07:42:59 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.25 X-Spam-Level: X-Spam-Status: No, score=-3.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=3lP384BS62qyDfssXJv5AEAFwbA=; b=Mt0w6whKEl+wk2Ie 17bmI8nTiWqFkwPZHmi+1Cau+jXQBN0ZRxu4f+zX6XQzT//OkhN35vwQue320rLF FrOGWoOLR5xlgWlK4sGX+XiJ8elOeexzVkGIn3Mxuq/h0YNvLehrctkhLW3QFHK/ RQdzeT4dKwQ9HvBAshmeomr2DdI= Date: Fri, 31 Mar 2017 07:42:42 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6ae2be08f_703b3fec49b87c3c1019b9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:42:58 -0000 ----==_mimepart_58de6ae2be08f_703b3fec49b87c3c1019b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This seems to be the ABNF for the field value (good), but the prose could be a bit more clear about 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/316#issuecomment-290731333 ----==_mimepart_58de6ae2be08f_703b3fec49b87c3c1019b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This seems to be the ABNF for the field value (good), but the prose could be a bit more clear about that.

—
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_58de6ae2be08f_703b3fec49b87c3c1019b9-- From nobody Fri Mar 31 07:43:18 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=EygDEZyHtfpuywYEOW+zuYP3Y7U=; b=uZLChEqKZJueL2VS gsm2OT6Tx9yLWtAm0COV5JSN7JNzLGU4tpHHFsKtB72qxUzar5xK3EzZW/w0f+kv TEi8iff7FvTFYwMKxCQ1f+jTUjDEVzPuQEts813e5w+Ub42x/Zj7bNQUuRmeQH6K S5ocfssCTkc6iDYY1NLtZsI2hk8= Date: Fri, 31 Mar 2017 07:43:03 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6af7737b6_182a3fd7e8f4fc2c215751"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:43:13 -0000 ----==_mimepart_58de6af7737b6_182a3fd7e8f4fc2c215751 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We can close this (invalid) and I will open a smaller issue about the definition of `Expect-CT` itself. That can be just editorial. -- 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/316#issuecomment-290731435 ----==_mimepart_58de6af7737b6_182a3fd7e8f4fc2c215751 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We can close this (invalid) and I will open a smaller issue about the definition of Expect-CT itself. That can be just editorial.

—
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_58de6af7737b6_182a3fd7e8f4fc2c215751-- From nobody Fri Mar 31 07:43:26 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=aw9VwFBEboBNTxR9UV4vhkmmeq8=; b=Qkm5kd2fj6lFyhSf ku753qe6HPw8wXHEAPZecC8TqPiYHVrxLC7+1A/w3Hmz77cFNcFCrG6mCSoFZjis hph6Vc6/8laDyb7WLndgDsPOKuIYpKSqUKkDVZ5uvb70x3eP0Z1gb4Qebpz5ovg2 ++ZJIOpAOJuNqB3oMph9sr/qP+I= Date: Fri, 31 Mar 2017 07:43:03 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6af7ce54f_cdc3faad9673c34150566"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:43:21 -0000 ----==_mimepart_58de6af7ce54f_cdc3faad9673c34150566 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #316. -- 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/316#event-1024206993 ----==_mimepart_58de6af7ce54f_cdc3faad9673c34150566 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #316.

—
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_58de6af7ce54f_cdc3faad9673c34150566-- From nobody Fri Mar 31 07:43:36 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=5T5MNfWaEtstrK/u/5w2GOq/JHM=; b=NwPjxjC0Eeppuuo4 NiVaz17a8T8vHRz14WwJjeLygHwpnjzbSXVyjifQ82eEiydYvTjUiqDF8W2tExW+ iNlafJ9qv8JFah0wvAjRaQi2KbHGEvizvGyHSy6q0DUEjB3AdYJvzFE+DEgJCEnU zEXHI/KEbQttRvy3eqPF0nGDA/0= Date: Fri, 31 Mar 2017 07:43:21 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Can dictionary keys repeat? (#281) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6b09782_44003fb891771c383027eb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:43:35 -0000 ----==_mimepart_58de6b09782_44003fb891771c383027eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Either keys need to repeat, or there needs to be a list syntax as a value. Either would satisfy the use case, but "neither" is a painful option. -- 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/281#issuecomment-290731512 ----==_mimepart_58de6b09782_44003fb891771c383027eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Either keys need to repeat, or there needs to be a list syntax as a value. Either would satisfy the use case, but "neither" is a painful option.

—
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_58de6b09782_44003fb891771c383027eb-- From nobody Fri Mar 31 07:52:43 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=fiA6bYzUyKXcomazr6oIcAKPFhg=; b=MU2tGT5FdcZc0MgH 4Mo+5VpfjGI3uENU97vaav02HlNfEx/Ff+EaPpv8MOdMHfVVS8xVbNIkicoAIcR1 lnEaOUcT2O++jflHsz+vNXbEfc0tGe0WhkJSqRKT8Smvt1C+fJj5wwfhTGIjrKnH EtdWoRhIlWMJgcdscDwVILh9LNk= Date: Fri, 31 Mar 2017 07:52:32 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6d30ca302_75463fec49b87c3c360c4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:52:42 -0000 ----==_mimepart_58de6d30ca302_75463fec49b87c3c360c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit No, it is supposed to be a list. It is defined as a semicolon-separated list. That's the cookie syntax. It should be ``` Expect-CT = #directive directive = directive-name [ "=" directive-value ] directive-name = token directive-value = token / quoted-string ``` -- 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/316#issuecomment-290734075 ----==_mimepart_58de6d30ca302_75463fec49b87c3c360c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

No, it is supposed to be a list. It is defined as a semicolon-separated= list. That's the cookie syntax.

It should be

   Expect-CT       =3D #directive
   directive       =3D directive-name [ "=3D" directive-value ]
   directive-name  =3D token
   directive-value =3D token / quoted-string

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

= ----==_mimepart_58de6d30ca302_75463fec49b87c3c360c4-- From nobody Fri Mar 31 07:53:54 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -9.295 X-Spam-Level: X-Spam-Status: No, score=-9.295 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=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 07:53:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490972029; bh=Kry09eHc1QVr/98Zvgg3pse07Bf9ajdzhXRsIIkDB+A=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Iphidja6sqQa1q1lJfCrpTcc2Jv20TEaRsyhaz3zooQf+8T8vM230x03Q74X3a7Sn M1zxt7yBdOxfVTzp3K2kjZjnmXAOV6tXPrXnCbh3LvMknZzGmRdEC74o7XvU/Z8b46 RgDiHJBhTGntIoyBbsgRXP+2Yoi+iQznCW2wr9Ms= To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] Definition of Expect-CT is a little unclear (#318) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6d7db6731_69d03fec49b87c3c2613b0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:53:52 -0000 ----==_mimepart_58de6d7db6731_69d03fec49b87c3c2613b0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The convention for HTTP is to define header fields as follows: ``` = #-fields ``` Which leads to me suggesting: ```abnf Expect-CT = #Expect-CT-Directives Expect-CT-Directives = [ parameter *( OWS ";" OWS parameter ) ] ``` Note that this doesn't follow the common structure, which uses: ```abnf common-structure = 1* ( identifier dictionary ) ``` Ignore the obvious errors in the common structure syntax, the intent is to have a list of identifiers followed by dictionaries. I've marked this as editorial, I think that the outcome will not affect the wire syntax at all. -- 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/318 ----==_mimepart_58de6d7db6731_69d03fec49b87c3c2613b0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The convention for HTTP is to define header fields as follows:

<header-field-name> = #<header-field-name>-fields

Which leads to me suggesting:

Expect-CT = #Expect-CT-Directives
Expect-CT-Directives = [ parameter *( OWS ";" OWS parameter ) ]

Note that this doesn't follow the common structure, which uses:

common-structure = 1* ( identifier dictionary )

Ignore the obvious errors in the common structure syntax, the intent is to have a list of identifiers followed by dictionaries.

I've marked this as editorial, I think that the outcome will not affect the wire syntax at all.

—
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_58de6d7db6731_69d03fec49b87c3c2613b0-- From nobody Fri Mar 31 07:58:12 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -3.178 X-Spam-Level: X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=QZ1vxucPhwctLVSY5VYnVTkCjsY=; b=EHb90kNM9ydkrNTI AiyJY5Wd/dGUsqfI2LkkxBwrrW4WGC48bVeNWleK2efk2RIvbT1EYGcEBjKjtVeB Kwki5USwbJAsPENKbaoE1aNIeearaEZrC/gyj4+SquYgud+BwaBeQMIuYHMFZeGY ppjxRdELt0aIxfYoAJzuhaRUzBM= Date: Fri, 31 Mar 2017 07:58:04 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6e7c5d5a_2b763fec49b87c3c2999a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:58:11 -0000 ----==_mimepart_58de6e7c5d5a_2b763fec49b87c3c2999a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit :-) just because it doesn't use list syntax doesn't make it like cookies. For instance, that would make Content-Type "cookie-like" as well. That said: yes, this might be a candidate for list syntax. -- 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/316#issuecomment-290735612 ----==_mimepart_58de6e7c5d5a_2b763fec49b87c3c2999a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

:-) just because it doesn't use list syntax doesn't make it like cookies= . For instance, that would make Content-Type "cookie-like" as well.

That said: yes, this might be a candidate for list syntax.

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

= ----==_mimepart_58de6e7c5d5a_2b763fec49b87c3c2999a-- From nobody Fri Mar 31 07:58:50 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -7.677 X-Spam-Level: X-Spam-Status: No, score=-7.677 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=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 07:58:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490972325; bh=ad6V3rzmsSG4kVkUtD1sHZzqqdy+fonweIf+2QfEXM4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GSl0ySPaA1VI9FGZVPmfDJMTR6pnnLYWM6l/DiuRlfcFpfSiKnLw4/g/OIUVEd3Sd KljlWVq3Ab0tMM5ASKUGy4n+LIpv78+1SqEHIcvl3LxdJMYSWV9MSjF+Gc0yT7Hv51 HHPesNmHqjMsTXT0qIxwTh+43oXuxSilwy4dDhJU= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Expect-CT uses cookie syntax (#316) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de6ea5a0b72_2ec63fd7e8f4fc2c1930ee"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 14:58:48 -0000 ----==_mimepart_58de6ea5a0b72_2ec63fd7e8f4fc2c1930ee Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I agree that the current text is incredibly opaque. I think that #318 is OK to replace this. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/316#issuecomment-290735816 ----==_mimepart_58de6ea5a0b72_2ec63fd7e8f4fc2c1930ee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I agree that the current text is incredibly opaque. I think that #318 is OK to replace this.

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

----==_mimepart_58de6ea5a0b72_2ec63fd7e8f4fc2c1930ee-- From nobody Fri Mar 31 08:07:41 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -9.794 X-Spam-Level: X-Spam-Status: No, score=-9.794 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=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 08:07:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490972857; bh=CACXZEZ/l/IpzCVESn1bRo0mmPtlUJW5VF5I+F749OE=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OivWOUb04kPkzTwXBTu6QY+nynrYIlHKEqyX0iOR1kFbg1b68Og2pcQNriXhZqGsY 6LP04X/Xdnyvan6TLyJ1ZMjjUjqk4T3GjrVYGNeRLLk2NugYudW9n2qerZCtJ1Dyub 9S3tO44/O8LIB11HGWQTuzB2AyxBSbeweJ8NL1D8= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Definition of Expect-CT is a little unclear (#318) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de70b954b7d_7b833fb891771c3877987"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 15:07:40 -0000 ----==_mimepart_58de70b954b7d_7b833fb891771c3877987 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If it is supposed to be a list of directives (some of which may be name=value), then it should be ``` Expect-CT = #directive directive = directive-name [ "=" directive-value ] directive-name = token directive-value = token / quoted-string ``` If it is supposed to be a list of directives with optional name=value parameters to each directive, then ``` Expect-CT = #directive directive = directive-name *( OWS ";" OWS parameter ) directive-name = token parameter = token / ( token "=" quoted-string ) ``` I guess we could also use some examples in the specification. -- 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/318#issuecomment-290738269 ----==_mimepart_58de70b954b7d_7b833fb891771c3877987 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If it is supposed to be a list of directives (some of which may be nam= e=3Dvalue), then it should be

   Expect-CT       =3D #directive
   directive       =3D directive-name [ "=3D" directive-value ]
   directive-name  =3D token
   directive-value =3D token / quoted-string

If it is supposed to be a list of directives with optional name=3Dvalu= e parameters to each directive, then

   Expect-CT       =3D #directive
   directive       =3D directive-name *( OWS ";" OWS parameter ) =

   directive-name  =3D token
   parameter       =3D token / ( token "=3D" quoted-string )

I guess we could also use some examples in the specification.

&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_58de70b954b7d_7b833fb891771c3877987-- From nobody Fri Mar 31 08:08:45 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -8.249 X-Spam-Level: X-Spam-Status: No, score=-8.249 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=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 08:08:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490972915; bh=zqSSBQeSb2pkZJHe9U9UrKocY2qytP0tb0b3vI4yBNw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=elxVs4OHGBsmXWgaMjW6ERMOwibHHMLGJzGwZSOZFRxCnaczpQfRcj8mOwJ7ot1UV OYwQXTg2gDj0FZZXBsZovyw8Uj2JI8DehFEPYsg03XJh2eRZ3aQAddLkMwiVKQ9F4s jumnDw6flimxPejCrYo1+oMuSwoZkS8BJrhDs9E8= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Definition of Expect-CT is a little unclear (#318) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de70f3d8e1_50df3fce8fc55c2c979bb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 15:08:44 -0000 ----==_mimepart_58de70f3d8e1_50df3fce8fc55c2c979bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson what you suggested *does* change the wire syntax... -- 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/318#issuecomment-290738568 ----==_mimepart_58de70f3d8e1_50df3fce8fc55c2c979bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson what you suggested does change the wire syntax...

—
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_58de70f3d8e1_50df3fce8fc55c2c979bb-- From nobody Fri Mar 31 08:10:50 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -8.177 X-Spam-Level: X-Spam-Status: No, score=-8.177 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=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 08:10:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490973035; bh=bV5Cshv5fX5FKSk6Pd9SGOqqQkCEgL4bfHfo9Hla6Q0=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dZ5clTcuN4xBFp4Hk0iryyOm/TgIq9WU1EVkrNdFXYXHcumEjmGzWpqeV9Qczkdsj ioU9rcBmFI8HAzYbfLs5ID7SZphOZeM4MFiIhz9vrO9yUnS4xahW/arUGyIVAQAkpQ UFRQ97uzVkcLVET9gRzZ2mMQ3y0ujjWq83Y/J/eM= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Definition of Expect-CT is a little unclear (#318) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de716b607a_5e433f8c96163c3c2190eb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 15:10:49 -0000 ----==_mimepart_58de716b607a_5e433f8c96163c3c2190eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I also disgree with the statement: > The convention for HTTP is to define header fields as follows: That depends on the type of the field. It's definitively not true universally right now. -- 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/318#issuecomment-290739149 ----==_mimepart_58de716b607a_5e433f8c96163c3c2190eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I also disgree with the statement:

The convention for HTTP is to define header fields as follows:

That depends on the type of the field. It's definitively not true univ= ersally right now.

&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_58de716b607a_5e433f8c96163c3c2190eb-- From nobody Fri Mar 31 08:10:58 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=y5SlMUJtMMVUW8duUPf6JZoMI0c=; b=NS6Mpt7725e5TYbg SBwROh81N9rRAzff9++5om7WgQrEL5hgTlY3JnRQLo6f1Fr02c6B10UzIoAfdJcW VkNqqtHatB7D/luAudr2Nesc5jd+l1gXxEVpp6B0bEvw2K+lOg2+FCKi7SVDHkaN K8Va/WF8Gf+UBxiwOkKxLAYAn6A= Date: Fri, 31 Mar 2017 08:10:38 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Definition of Expect-CT is a little unclear (#318) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de716ee290a_32f93f8c96163c3c2240c6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 15:10:52 -0000 ----==_mimepart_58de716ee290a_32f93f8c96163c3c2240c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit BTW, that would be to match the standard HTTP/1.x syntax for most header fields. I don't think it is appropriate to use the experimental common structure, which is still just a proposal, unless folks want to make this header field a guinea pig. -- 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/318#issuecomment-290739172 ----==_mimepart_58de716ee290a_32f93f8c96163c3c2240c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

BTW, that would be to match the standard HTTP/1.x syntax for most header= fields. I don't think it is appropriate to use the experimental common str= ucture, which is still just a proposal, unless folks want to make this head= er field a guinea pig.

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

= ----==_mimepart_58de716ee290a_32f93f8c96163c3c2240c6-- From nobody Fri Mar 31 08:13:04 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -5.401 X-Spam-Level: X-Spam-Status: No, score=-5.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 08:12:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490973176; bh=aeFlExcJzuOGBkbTaIXGWRB9IhdewgjFgyxR9YGs3vk=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GwGVXm+qHO+p/5VTERlQfAq4M4YvLy/2xjGMmijHfl/3/zSLhaGKwYgDSq6bm+Hlu AKVg6kGdrD09JAWART/wDpbVX2jqwqL0i94d0uqcT6BMdW4YN6yoeOgcNvZyIcIozk +3DljJ4kFA/+qCXiUC0shXXW+vKx3OE6mfZ6zGnE= To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] Definition of Expect-CT is a little unclear (#318) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de71f87f586_70273fc17900bc3c1445b9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 15:12:59 -0000 ----==_mimepart_58de71f87f586_70273fc17900bc3c1445b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit https://greenbytes.de/tech/webdav/rfc7838.html#rfc.section.3 might be a good template. -- 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/318#issuecomment-290739878 ----==_mimepart_58de71f87f586_70273fc17900bc3c1445b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

https://greenbytes.de/tech/webdav/rfc7838.html#rfc.section.3 might be a good template.

—
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_58de71f87f586_70273fc17900bc3c1445b9-- From nobody Fri Mar 31 08:29:53 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -8.391 X-Spam-Level: X-Spam-Status: No, score=-8.391 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=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Date: Fri, 31 Mar 2017 08:29:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490974188; bh=yFtvFMdCt8agLBGMqO5VfWCkfwFQ58z6pwYqyoumXSM=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=gQn0DhVqQFW02kr4W85lT39n2WpFjVL7w0zrqXvFopY1kXl3/3qIyzG7KuudWtotl Lpl/p2EpWcCOmor0ZZ6wM7gUzlB328t5XRSGIrmUI+7NUd8oWV15EiO/x9fzDGsnPO 4v1y0LZKMaGnOMLz4zk0kb2Ww+fwlQb5UpaXESH0= To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] client-hints requirement on "client MUST NOT process" headers needs better wording (#319) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de75eceb825_30263fe756af3c3c57029"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 15:29:51 -0000 ----==_mimepart_58de75eceb825_30263fe756af3c3c57029 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Regarding ``` A client MAY speculatively evaluate the headers included in the informational response while waiting for the final response. For example, a client may recognize the link header of type preload and start fetching the resource. However, the evaluation MUST NOT affect how the final response is processed; the client must behave as if it had not seen the informational response. A client MUST NOT process the headers included in the response as if they belonged to the informational response. ``` The requirement in the last sentence needs to be re-worded, since `process` includes parsing and the client is clearly parsing those header fields and using them. -- 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/319 ----==_mimepart_58de75eceb825_30263fe756af3c3c57029 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Regarding

   A client MAY speculatively evaluate the headers included in the
   informational response while waiting for the final response.  For
   example, a client may recognize the link header of type preload and
   start fetching the resource.  However, the evaluation MUST NOT affect
   how the final response is processed; the client must behave as if it
   had not seen the informational response.  A client MUST NOT process
   the headers included in the response as if they belonged to the
   informational response.

The requirement in the last sentence needs to be re-worded, since process includes parsing and the client is clearly parsing those header fields and using them.

—
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_58de75eceb825_30263fe756af3c3c57029-- From nobody Fri Mar 31 08:48:04 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -4.796 X-Spam-Level: X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=meY0lcsKQdjkBo4dT0SFx9SShBo=; b=sDPeBs9GX4D8oB6/ uhYAmLpZEYcIQX9IbjzXkgmfDMm6kpQrOvj+rewlEwBLV6aHQq4qgwVKSArQ9X9J SKZDv1n7eI3b/iL7doLm9AkpUFOGUeVwm7hjG6TMc2hhyXEdaKJ25wG937wMCQTG 9Q3s2+2x2jnL6nAnkAWbh/SZJK0= Date: Fri, 31 Mar 2017 08:47:58 -0700 To: httpwg/http-extensions Cc: Subscribed In-Reply-To: References: Subject: Re: [httpwg/http-extensions] client-hints requirement on "client MUST NOT process" headers needs better wording (#319) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de7a2e7cd62_5a9b3fc1ba7d5c381352f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 15:48:03 -0000 ----==_mimepart_58de7a2e7cd62_5a9b3fc1ba7d5c381352f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I would rewrite the paragraph as ``` A client MAY speculatively evaluate the header fields included in the informational response while waiting for the final response. For example, a client might recognize a link header field of type preload and start fetching the indicated resource. However, these fields only provide hints to the client; they do not replace the header fields on the final response. Aside from performance optimizations, such evaluation of the 103 response's header fields MUST NOT affect how the final response is processed. A client MUST NOT interpret the 103 response header fields as if they applied to the 103 response itself (e.g., as metadata about the 103 response). ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/319#issuecomment-290750144 ----==_mimepart_58de7a2e7cd62_5a9b3fc1ba7d5c381352f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I would rewrite the paragraph as

   A client MAY speculatively evaluate the header fields include=
d in
   the informational response while waiting for the final response.
   For example, a client might recognize a link header field of type
   preload and start fetching the indicated resource.  However, these
   fields only provide hints to the client; they do not replace the header
   fields on the final response. Aside from performance optimizations,
   such evaluation of the 103 response's header fields MUST NOT
   affect how the final response is processed. A client MUST NOT
   interpret the 103 response header fields as if they applied to the
   103 response itself (e.g., as metadata about the 103 response).

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

= ----==_mimepart_58de7a2e7cd62_5a9b3fc1ba7d5c381352f3-- From nobody Fri Mar 31 08:52:21 2017 Delivered-To: http-issues@ietfa.amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Toi3w3Pkky8y2nyF0uHKYQF7jtc=; b=xZS7LjsH1xaMcG51 Ia2Jr4M43G6FBJ3kW460KboL4s4cVsRHigfbbzbpImaAgBrGLKahaXJl/D9vg+v8 0HRdedr7hPTUYQael7zgHxnBKZXDiompnGxjiLCOIw5a7yT4G5UAZcfSpj4sKNAK kckcy2fh4h0PXLyb4YfJXA3qcLc= Date: Fri, 31 Mar 2017 08:51:48 -0700 To: httpwg/http-extensions Cc: Subscribed Subject: [httpwg/http-extensions] client hints generally uses "headers" to refer to "header fields" (#320) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_58de7b1475b1d_7a73fc1ba7d5c381008cb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list Archived-At: Message-ID: From: HTTP issue updates Reply-To: http-issues@ietf.org X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.22 List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 15:52:20 -0000 ----==_mimepart_58de7b1475b1d_7a73fc1ba7d5c381008cb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The WG drafts that extend HTTP/1 should be consistent with the terminology of RFC7230 and RFC7231. That means `s/headers/header fields/g;`. -- 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/320 ----==_mimepart_58de7b1475b1d_7a73fc1ba7d5c381008cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The WG drafts that extend HTTP/1 should be consistent with the terminology of RFC7230 and RFC7231. That means s/headers/header fields/g;.

—
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_58de7b1475b1d_7a73fc1ba7d5c381008cb--