W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2016

Re: #148: Reasonable Assurances and H2C

From: Mark Nottingham <mnot@mnot.net>
Date: Fri, 26 Feb 2016 11:56:03 +1100
Cc: HTTP WG <ietf-http-wg@w3.org>
Message-Id: <2DDC5527-43AC-4BD2-8ED9-F68D747A7E0C@mnot.net>
To: Martin Thomson <martin.thomson@gmail.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
I've taken a stab at this:

Please review.


> On 20 Feb 2016, at 1:44 PM, Martin Thomson <martin.thomson@gmail.com> wrote:
> On 19 February 2016 at 18:40, Mark Nottingham <mnot@mnot.net> wrote:
>> "For the purposes of this document, "reasonable assurances" can be established through use of a TLS-based protocol with the certificate checks defined in RFC2818. Other means of establishing them MUST be documented in an RFC that updates this specification. Clients MAY impose additional criteria for establishing reasonable assurances."
> That looks good.  I don't think that it helps to note that in practice
> "MAY" becomes "will".

Mark Nottingham   https://www.mnot.net/
Received on Friday, 26 February 2016 00:56:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:11 UTC