IETF Logo Mail Archive

Re: [Http-srv] Alternative to SRV?

Daniel Stenberg <daniel@haxx.se> Wed, 22 August 2018 05:55 UTC

Return-Path: <daniel@haxx.se>
X-Original-To: http-srv@ietfa.amsl.com
Delivered-To: http-srv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF8C130DF6 for <http-srv@ietfa.amsl.com>; Tue, 21 Aug 2018 22:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 cV0y6gEPGLdk for <http-srv@ietfa.amsl.com>; Tue, 21 Aug 2018 22:55:27 -0700 (PDT)
Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) by ietfa.amsl.com (Postfix) with ESMTP id 26CC6130E8F for <Http-srv@ietf.org>; Tue, 21 Aug 2018 22:55:26 -0700 (PDT)
Received: from giant.haxx.se (mail [127.0.0.1]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id w7M5tJ6D025560 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 22 Aug 2018 07:55:19 +0200
Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id w7M5tIVM025552; Wed, 22 Aug 2018 07:55:19 +0200
X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs
Date: Wed, 22 Aug 2018 07:55:18 +0200
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Mark Andrews <marka@isc.org>
cc: Tony Finch <dot@dotat.at>, Http-srv@ietf.org, Ray Bellis <ray@bellis.me.uk>
In-Reply-To: <9BDFA596-FBD5-4ECF-9361-FEBBDDDCDCA5@isc.org>
Message-ID: <alpine.DEB.2.20.1808220752240.22009@tvnag.unkk.fr>
References: <6aceab29-cf81-8644-20cd-e02281e6394c@bellis.me.uk> <alpine.DEB.2.20.1808212037370.3596@grey.csi.cam.ac.uk> <9BDFA596-FBD5-4ECF-9361-FEBBDDDCDCA5@isc.org>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-srv/QZsYs_zs2GMrS148s2fUHzLN8Fk>
Subject: Re: [Http-srv] Alternative to SRV?
X-BeenThere: http-srv@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Using DNS SRV Records with HTTP <http-srv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-srv>, <mailto:http-srv-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-srv/>
List-Post: <mailto:http-srv@ietf.org>
List-Help: <mailto:http-srv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-srv>, <mailto:http-srv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2018 05:55:31 -0000

On Wed, 22 Aug 2018, Mark Andrews wrote:

> For MX this took 10 to 15 years as it took a long time to replace MTAs. 
> Browser vendors have shown that they can replace the client side in less 
> that 3 years.

HTTP(S) is used way more widely than just the major browsers, and 
unfortuantely most of the non-browser usage is not as agile when it comes to 
upgrades...

-- 

  / daniel.haxx.se

v2.23.0 | Report a Bug | By Email