Re: Alt-SvcB

Tommy Pauly <tpauly@apple.com> Tue, 25 October 2022 20:32 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 57BE0C14CF1C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 25 Oct 2022 13:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.329
X-Spam-Level:
X-Spam-Status: No, score=-8.329 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1-BjKkzdtYO for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 25 Oct 2022 13:32:27 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F09DDC14CF05 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 25 Oct 2022 13:32:26 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1onQYa-004Jm1-Lg for ietf-http-wg-dist@listhub.w3.org; Tue, 25 Oct 2022 20:29:52 +0000
Resent-Date: Tue, 25 Oct 2022 20:29:52 +0000
Resent-Message-Id: <E1onQYa-004Jm1-Lg@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <tpauly@apple.com>) id 1onQYY-004Jkt-R7 for ietf-http-wg@listhub.w3.org; Tue, 25 Oct 2022 20:29:50 +0000
Received: from rn-mailsvcp-ppex-lapp35.rno.apple.com ([17.179.253.44] helo=rn-mailsvcp-ppex-lapp35.apple.com) by titan.w3.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <tpauly@apple.com>) id 1onQYX-001Mso-1e for ietf-http-wg@w3.org; Tue, 25 Oct 2022 20:29:50 +0000
Received: from pps.filterd (rn-mailsvcp-ppex-lapp35.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp35.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 29PKIjGh010196; Tue, 25 Oct 2022 13:29:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=mwyAMjGfkjM0jUYf0enySJNLe82JxfBWHaxfSCQk/nY=; b=Akp5GrdL/PTDEcMNrfEr+rowePMSPt2Nu3UCFuJHx4Oru5jnzlU/BTmsg2cfhxDRZuLS gH5CGJGdmyo4ZkNbnA0hqqYBGTx5B9/Ob0DJMHctj93vjm/EZFSQd9G5168d0KP2NOlK nDrudy9GIQ8MO0Oz6NTsW5DeU8G3fZDCzm+wpFEoV7KwsMhaeVIriYpl1xZuunPsjyki xGWFu9T+9kBg6EII5wsc3Mi/N5R8czP+1/r+fuvW+gPTPF8Du+qs9gyNDUawnqkXlS2C /nl77X9jW+7u+XWQsZav9UZILBGwFIBePzXZiaPE9/GmdXYvbcUXJn6Kns2muUA5o5lu VQ==
Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com [10.225.203.151]) by rn-mailsvcp-ppex-lapp35.rno.apple.com with ESMTP id 3kcc25dphj-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 25 Oct 2022 13:29:29 -0700
Received: from rn-mailsvcp-policy-lapp01.rno.apple.com (rn-mailsvcp-policy-lapp01.rno.apple.com [17.179.253.18]) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.19.20220711 64bit (built Jul 11 2022)) with ESMTPS id <0RKB005SXSX5YG90@rn-mailsvcp-mta-lapp03.rno.apple.com>; Tue, 25 Oct 2022 13:29:29 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-policy-lapp01.rno.apple.com by rn-mailsvcp-policy-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.19.20220711 64bit (built Jul 11 2022)) id <0RKB00V00SPV9Y00@rn-mailsvcp-policy-lapp01.rno.apple.com>; Tue, 25 Oct 2022 13:29:29 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 08b9881e6a3d9181aad7a817dd98f2d4
X-Va-E-CD: 8c8215fd9f03e60e18246037ecdb1d49
X-Va-R-CD: a0fde10e5b571921d84e20def2fe57ff
X-Va-CD: 0
X-Va-ID: d214444c-756c-4682-93d2-d05e9be68de6
X-V-A:
X-V-T-CD: 08b9881e6a3d9181aad7a817dd98f2d4
X-V-E-CD: 8c8215fd9f03e60e18246037ecdb1d49
X-V-R-CD: a0fde10e5b571921d84e20def2fe57ff
X-V-CD: 0
X-V-ID: 38ebdc07-352b-4ada-8959-cabd7dae6f8a
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.545,18.0.895 definitions=2022-10-25_12:2022-10-25,2022-10-25 signatures=0
Received: from smtpclient.apple ([17.11.33.235]) by rn-mailsvcp-policy-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.19.20220711 64bit (built Jul 11 2022)) with ESMTPSA id <0RKB00X7TSX1E900@rn-mailsvcp-policy-lapp01.rno.apple.com>; Tue, 25 Oct 2022 13:29:29 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <0BE7FC0E-D294-453B-A9EB-01825447168F@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_2834ED40-2BCC-4577-831D-7A316CDD7F0D"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3730.0.21\))
Date: Tue, 25 Oct 2022 13:29:14 -0700
In-reply-to: <CAKcm_gNNxCaaG65Cfg9VqS9nwH-gWm3sA42hYfYYvxdgQqoxOg@mail.gmail.com>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, Martin Thomson <mt@lowentropy.net>, ietf-http-wg@w3.org
To: Ian Swett <ianswett@google.com>
References: <bfc198a9-25da-4a96-aca9-5e4451c19105@betaapp.fastmail.com> <CAPDSy+5d7h63_bpBQBMJMbXA0O6rNe7HdstePW3ggF6zmSBnrA@mail.gmail.com> <CAKcm_gNNxCaaG65Cfg9VqS9nwH-gWm3sA42hYfYYvxdgQqoxOg@mail.gmail.com>
X-Mailer: Apple Mail (2.3730.0.21)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.545,18.0.895 definitions=2022-10-25_12:2022-10-25,2022-10-25 signatures=0
Received-SPF: pass client-ip=17.179.253.44; envelope-from=tpauly@apple.com; helo=rn-mailsvcp-ppex-lapp35.apple.com
X-W3C-Hub-DKIM-Status: validation passed: (address=tpauly@apple.com domain=apple.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-11.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.517, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1onQYX-001Mso-1e 0ab901923f0a6281dffc3a2d6d956a1d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Alt-SvcB
Archived-At: <https://www.w3.org/mid/0BE7FC0E-D294-453B-A9EB-01825447168F@apple.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40485
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>

The way I’d look at this is that we should be fine keeping the use of Alt-Svc for existing (and what will become legacy) clients to upgrade to h3, but we should not use it for any new protocol discovery. I.e., when we have an HTTP version that needs some transport other than TCP and QUIC, we shouldn’t plan on using Alt-Svc for that. So, our timeline should be to make sure clients can do HTTPS RRs by the time we replace QUIC, which should give us time.

Tommy

> On Oct 25, 2022, at 1:21 PM, Ian Swett <ianswett@google.com> wrote:
> 
> I would second David's statement.  In the world we live in today, we still need to use the Alt-Svc header for a substantial number of users.
> 
> On Tue, Oct 25, 2022 at 2:31 PM David Schinazi <dschinazi.ietf@gmail.com <mailto:dschinazi.ietf@gmail.com>> wrote:
>> Hi Martin,
>> 
>> Thanks for writing this up. Overall I think the long-term strategy makes sense, but I think it's too early to obsolete/deprecate 7838. It's fairly common for browsers to use getaddrinfo() on some platforms and that does not provide access to HTTPS RRs. In those cases, 7838 is the only path to using HTTP/3, so I expect browsers to keep using it for quite some time. Marking 7838 as obsolete doesn't reflect that reality.
>> 
>> David
>> 
>> On Mon, Oct 24, 2022 at 5:10 PM Martin Thomson <mt@lowentropy.net <mailto:mt@lowentropy.net>> wrote:
>>> Hey everyone,
>>> 
>>> The Alt-Svc design team has been very busy recently and making some progress on working out an alternative alternative services design.
>>> 
>>> I just posted https://martinthomson.github.io/alt-svcb/draft-thomson-httpbis-alt-svcb.html as a -00 draft.  This outlines the alternative design that we've been exploring in the design team.
>>> 
>>> The basic idea is split into two procedures:
>>> 
>>> 1. Use: When an Alt-SvcB field or ALTSVCB frame is encountered, the client looks for HTTPS records for the provided name in the DNS and creates a connection using what it learns.
>>> 2. Reuse: When a client that has previously used an alternative service connects again, it remembers the HTTPS record that worked.  It performs a regular HTTPS record lookup for the server - not using the alternative that it learned, but the name from the URI - but it prefers the alternative it previously used if that alternative appears in the results.
>>> 
>>> The draft explains in more detail and goes into some of the implications of the design.
>>> 
>>> This is not done by any imagining.  We have a bunch of open issues at https://github.com/martinthomson/alt-svcb/issues that do require some amount of input.  But we think that this is a promising approach and would appreciate more input.
>>> 
>>> Cheers,
>>> Martin
>>>