Re: Last Call: <draft-ietf-httpbis-http2-16.txt> (Hypertext Transfer Protocol version 2) to Proposed Standard

Patrik Fältström <paf@frobbit.se> Sun, 04 January 2015 04:46 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C111A1EF4 for <ietf@ietfa.amsl.com>; Sat, 3 Jan 2015 20:46:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level:
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 BjMqI_66UG28 for <ietf@ietfa.amsl.com>; Sat, 3 Jan 2015 20:46:08 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FD591A1B1E for <ietf@ietf.org>; Sat, 3 Jan 2015 20:46:07 -0800 (PST)
Received: from [192.168.1.84] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id BEDE7202E3; Sun, 4 Jan 2015 05:46:05 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-httpbis-http2-16.txt> (Hypertext Transfer Protocol version 2) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: multipart/signed; boundary="Apple-Mail=_767B6FC7-6763-49F9-AF6E-E84FD78FD808"; protocol="application/pgp-signature"; micalg=pgp-sha1
X-Pgp-Agent: GPGMail 2.5b4
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
In-Reply-To: <20150103215310.D533D26FFFCD@rock.dv.isc.org>
Date: Sun, 4 Jan 2015 05:46:05 +0100
Message-Id: <E9D40359-CB77-4345-8859-FB61CABB7440@frobbit.se>
References: <CAK3LatFh3ZU8ACk8grzLA9oCv2qqUHttz2z83b66xKnfs78mRA@mail.gmail.com> <54A7DBFC.8010800@cisco.com> <20150103143226.GC13599@besserwisser.org> <89DB2965-68B1-43D0-BBEB-FF49DB666A6D@frobbit.se> <54A81E9A.1020700@cisco.com> <20150103215310.D533D26FFFCD@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Yfh_Ej6vzT9TKF-SZben-h5D-u4
Cc: Delan Azabani <delan@azabani.com>, =?utf-8?Q?M=C3=A5ns_Nilsson?= <mansaxel@besserwisser.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jan 2015 04:46:10 -0000

> On 3 jan 2015, at 22:53, Mark Andrews <marka@isc.org> wrote:
> 
> I suspect in
> most cases there would be a single SRV record pointing to the hosting
> service.  There is only a single CNAME record pointing to the hosting
> service today.

Yes, except in the case for the bare domain name which there can not be any CNAME records for. For that you might have a "lame" A/AAAA record pair, which references an HTTP server that only gives back 301 to whatever URL you are to use -- where the CNAME exists.

I.e. I want to replace:

1 A lookup for domain
2 AAAA lookup for domain
3 Open HTTP connection to whatever target there was for A or AAAA lookup for domain
4 Get 301 back
5 A lookup for domain in the result of the 301
6 AAAA lookup for domain in the result of the 301
7 Get back CNAME from either 5 or 6
8 A lookup for domain in the result of the CNAME lookup
9 AAAA lookup for domain in the result of the CNAME lookup
10 Open HTTP connection to whatever target there was for A or AAAA lookup for domain

With:

1 URI lookup for domain
2 A lookup for domain in target for URI
3 AAAA lookup for domain in target for URI
4 Open HTTP connection to whatever target there was for A or AAAA lookup for domain

I.e. with the URI lookup you can resolve both the issue with lack of CNAME as zone apex and the initial 301 to whatever the apex of the web site is.

Or similar shortening of the number of roundtrips in DNS or HTTP with SRV (one can argue whether you get rid of the 301 with SRV, or the CNAME or both).

Today I see both 301 redirect and CNAME chain(s) when opening HTTP connections. Lots of them.

   Patrik