Re: Question regarding HTTP/2, SNI, and IP addresses
Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 23 June 2021 08:35 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0CB3A2F8A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Jun 2021 01:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 BRmcnz9NBAsS for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Jun 2021 01:35:12 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3A3D3A2F88 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 23 Jun 2021 01:35:11 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1lvyIi-0008W8-2M for ietf-http-wg-dist@listhub.w3.org; Wed, 23 Jun 2021 08:32:02 +0000
Resent-Date: Wed, 23 Jun 2021 08:32:00 +0000
Resent-Message-Id: <E1lvyIi-0008W8-2M@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <bortzmeyer@nic.fr>) id 1lvyID-0008Tn-KR for ietf-http-wg@listhub.w3.org; Wed, 23 Jun 2021 08:31:36 +0000
Received: from mx4.nic.fr ([2001:67c:2218:2::4:12]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <bortzmeyer@nic.fr>) id 1lvyI8-00072U-Cx for ietf-http-wg@w3.org; Wed, 23 Jun 2021 08:31:26 +0000
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D5D0B28176D; Wed, 23 Jun 2021 10:31:11 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id D005B281772; Wed, 23 Jun 2021 10:31:11 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id C87BA28176D; Wed, 23 Jun 2021 10:31:11 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id C4FF76071EA6; Wed, 23 Jun 2021 10:31:11 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id B3AAA3FF0D; Wed, 23 Jun 2021 10:30:46 +0200 (CEST)
Date: Wed, 23 Jun 2021 10:30:46 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Martin Thomson <mt@lowentropy.net>
Cc: ietf-http-wg@w3.org
Message-ID: <20210623083046.GA558@nic.fr>
References: <HE1PR0701MB30500174B18EDB6C2704D15B890D9@HE1PR0701MB3050.eurprd07.prod.outlook.com> <bc78d96e-d4dd-4a89-8937-165a2c9f86fa@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <bc78d96e-d4dd-4a89-8937-165a2c9f86fa@www.fastmail.com>
X-Operating-System: Debian GNU/Linux 10.10
X-Kernel: Linux 4.19.0-17-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.4.9.2830568, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2021.6.23.80916, AntiVirus-Engine: 5.83.0, AntiVirus-Data: 2021.6.23.5830000
Received-SPF: pass client-ip=2001:67c:2218:2::4:12; envelope-from=bortzmeyer@nic.fr; helo=mx4.nic.fr
X-W3C-Hub-Spam-Status: No, score=-9.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1lvyI8-00072U-Cx 31a69ad69ff7b4f4087d67bc77505c52
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Question regarding HTTP/2, SNI, and IP addresses
Archived-At: <https://www.w3.org/mid/20210623083046.GA558@nic.fr>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38934
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On Tue, Jun 22, 2021 at 10:55:08AM +1000, Martin Thomson <mt@lowentropy.net> wrote a message of 20 lines which said: > > The TLS implementation MUST support the Server Name Indication (SNI) [TLS-EXT] extension to TLS. If the server is identified by a domain name [DNS-TERMS], clients MUST send the server_name TLS extension unless an alternative mechanism to indicate the target host is used. > > -- https://httpwg.org/http2-spec/draft-ietf-httpbis-http2bis.html#section-9.2-2 > > Is that clearer? There is also similar updates to the HTTP core documents. > > The intent was never to prohibit the use of IP addresses as > authority. What are the possible "alternative mechanisms"?
- Question regarding HTTP/2, SNI, and IP addresses John Mattsson
- Re: Question regarding HTTP/2, SNI, and IP addres… Stephane Bortzmeyer
- Re: Question regarding HTTP/2, SNI, and IP addres… Martin Thomson
- Re: Question regarding HTTP/2, SNI, and IP addres… John Mattsson
- Re: Question regarding HTTP/2, SNI, and IP addres… Stephane Bortzmeyer
- Re: Question regarding HTTP/2, SNI, and IP addres… Martin Thomson
- Re: Question regarding HTTP/2, SNI, and IP addres… Ilari Liusvaara