IETF Logo Mail Archive

Re: #148: Reasonable Assurances and H2C

Martin Thomson <martin.thomson@gmail.com> Sat, 20 February 2016 02:47 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 778071B3804 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 19 Feb 2016 18:47:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.008
X-Spam-Level:
X-Spam-Status: No, score=-7.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EyaTnmUg0Feb for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 19 Feb 2016 18:47:26 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 291891B3809 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 19 Feb 2016 18:47:26 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1aWxXc-0003KG-BY for ietf-http-wg-dist@listhub.w3.org; Sat, 20 Feb 2016 02:45:04 +0000
Resent-Date: Sat, 20 Feb 2016 02:45:04 +0000
Resent-Message-Id: <E1aWxXc-0003KG-BY@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1aWxXY-0000mI-BB for ietf-http-wg@listhub.w3.org; Sat, 20 Feb 2016 02:45:00 +0000
Received: from mail-io0-f170.google.com ([209.85.223.170]) by maggie.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1aWxXW-0004un-IM for ietf-http-wg@w3.org; Sat, 20 Feb 2016 02:44:59 +0000
Received: by mail-io0-f170.google.com with SMTP id z135so128853171iof.0 for <ietf-http-wg@w3.org>; Fri, 19 Feb 2016 18:44:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=uqcFmYuuOV+4ELZIA5mq8jUsqe83xYg8IVIgoz9XkJo=; b=AqLxh2gwXrrDHA690f5DFj6u0V8JbjFK/DcrZTMZRKs6HENm5qCdbQBxF2/myAwaMR Are9A2sn6DW0OizJavEq5BbPzw14RRsWCXVjSBPAXeEBT55zvp7YvsbgpaVwbFFuM+T8 O/ASDbr7ueBJ9/dmZqvpB3NOUPliRWGr62HdJ12/Cu3BXResLprUEegxxYFZpslSt/3p rOgBIT3xPK5KNjGHN8+gDHUCcu+Vb4r67F25xCvObo3R1rcT/3xNBB5xqCrX2IlspFMv 8lypivCKM1SG1H1Hi1lkbfbo7PXIzpjVTIUHnj43EIN+VR55WRSRHmzpSjCLhQuXV5+h 6HUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uqcFmYuuOV+4ELZIA5mq8jUsqe83xYg8IVIgoz9XkJo=; b=l4tb82GzjEqxSZa/LtgithCfC4fAG6SV0FnK+3nHc1QuutwZV0yBfVOdLQ/1/+xwvD vSwSrCWoOl5/e60ikSjie8rqJ9zpbDBtx3+CyGXzk8/rWqf79WhQHoDapc8QPttFd5Ee JIx+zX+mGJi46w8OOQ/Mm5H85F9ai3xim0eqrZK1cLbXdkRXR+o56d7YwLp6t5LmDxLp CXvfa/ByYEpSb4FtaoZ3eVqo7gqECg+JydZjHm2czBUc19JU6gL7VnUfJQOglLcAy8lL fF4YS2XgPYDQ//gJDqrSh5EpYxpna0RMS9dOzyrowteHZlx8oRdPKM86lGk7b2oNvP0M dWgA==
X-Gm-Message-State: AG10YORwdzNWm66AVliq/x2fBf6tYK78AOk46mGfKKY1fysdCfIvb8FfQaGA/DoXRu4L7nQVN4u0Bfm4D6yaIA==
MIME-Version: 1.0
X-Received: by 10.107.34.139 with SMTP id i133mr16241067ioi.108.1455936272345; Fri, 19 Feb 2016 18:44:32 -0800 (PST)
Received: by 10.36.53.79 with HTTP; Fri, 19 Feb 2016 18:44:32 -0800 (PST)
In-Reply-To: <072D900D-422E-4168-8DCF-51A739BC9E5A@mnot.net>
References: <20160209074851.32332.24065.idtracker@ietfa.amsl.com> <20160209182822.C37A959F@welho-filter2.welho.com> <B7164F24-DDA1-4753-8A8B-04809B1965FF@mnot.net> <CAC4RtVCCExJNE0y8480vC1W56NP4XhzfvLs+ASh1Qy-UcDPBNw@mail.gmail.com> <C2145C5A-0255-43F9-A44A-F6C7974CDD4C@mnot.net> <CABkgnnW3-c1qaC_N2UP5TLnPS0rrOYjOYFb4nhUzfQ_8AFsTJA@mail.gmail.com> <072D900D-422E-4168-8DCF-51A739BC9E5A@mnot.net>
Date: Fri, 19 Feb 2016 18:44:32 -0800
Message-ID: <CABkgnnWAbKY8RZ5gvjPan3M_-XpjFSau0yDN97H=CfLb0DNL2g@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP WG <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=209.85.223.170; envelope-from=martin.thomson@gmail.com; helo=mail-io0-f170.google.com
X-W3C-Hub-Spam-Status: No, score=-7.9
X-W3C-Hub-Spam-Report: AWL=1.830, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1aWxXW-0004un-IM ce12d5ff334d1fceacdb0244339cbd0e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: #148: Reasonable Assurances and H2C
Archived-At: <http://www.w3.org/mid/CABkgnnWAbKY8RZ5gvjPan3M_-XpjFSau0yDN97H=CfLb0DNL2g@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31082
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

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".

v2.30.2 | Report a Bug | By Email | System Status