IETF Logo Mail Archive

Re: [Masque] QUIC non-encapsulation and CIDs

Tommy Pauly <tpauly@apple.com> Wed, 09 November 2022 20:51 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: masque@ietfa.amsl.com
Delivered-To: masque@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38AE8C14CE47; Wed, 9 Nov 2022 12:51:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.977
X-Spam-Level:
X-Spam-Status: No, score=-4.977 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 oPDweaLwHSwj; Wed, 9 Nov 2022 12:51:14 -0800 (PST)
Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) (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 1FF5EC14CF03; Wed, 9 Nov 2022 12:50:51 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.42/8.16.0.42) with SMTP id 2A9KoejZ055770; Wed, 9 Nov 2022 12:50:49 -0800
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=iqH1LhlWKW+uiJAHUcBCu4PjkGF6ZP+IBqQGo3A64/4=; b=Yw/TFZDHU3mZLwKpm9ZFFz7Pg9r7z/ElyklARHJCXvLnX8Vc4OvxoGURUhePUVSL65RK pieolJousKkrIrPOCZxnO0NDymL3ZRfcpNOxhOD6EiiVLhyEtXVjh5/eC2+gWx3CYtEf wQLRiwdiyNmYYDt9d4ITDQlsRc5srHjvNXvCdCuAK/VEjqZocvUhkBvEI/rPQ0FJVd+J hf1tiIOmyNZ5G8EHqaLEcf7+SJfqi3YKpcoBWtu3EsPnrbk4n59URGoEEjo0XqVWF2o7 bA3PUg+j2Z2pAT81elTKCCt/G1A6SiU0FcsFXASW9evGORTSrdNnUz1yxiahDc1MUzJt YA==
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 3knpg37t0e-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 09 Nov 2022 12:50:49 -0800
Received: from rn-mailsvcp-policy-lapp01.rno.apple.com (rn-mailsvcp-policy-lapp01.rno.apple.com [17.179.253.18]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.20.20220923 64bit (built Sep 23 2022)) with ESMTPS id <0RL300X5ILWPE740@rn-mailsvcp-mta-lapp02.rno.apple.com>; Wed, 09 Nov 2022 12:50:49 -0800 (PST)
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.20.20220923 64bit (built Sep 23 2022)) id <0RL300100LUOHC00@rn-mailsvcp-policy-lapp01.rno.apple.com>; Wed, 09 Nov 2022 12:50:49 -0800 (PST)
X-Va-A:
X-Va-T-CD: e72da815dcb01dab2f988f94f1719970
X-Va-E-CD: aad0465d6483c60260ff8d99c239fcb8
X-Va-R-CD: 9508b404f283f72fddb3b4921b7b876b
X-Va-CD: 0
X-Va-ID: 18a8f70f-b244-473c-8e22-40f2d57bc7b7
X-V-A:
X-V-T-CD: e72da815dcb01dab2f988f94f1719970
X-V-E-CD: aad0465d6483c60260ff8d99c239fcb8
X-V-R-CD: 9508b404f283f72fddb3b4921b7b876b
X-V-CD: 0
X-V-ID: 319cccf2-80af-4888-8c81-1a8be72bfe51
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.545, 18.0.895 definitions=2022-11-09_06:2022-11-09, 2022-11-09 signatures=0
Received: from smtpclient.apple ([17.11.143.135]) by rn-mailsvcp-policy-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.20.20220923 64bit (built Sep 23 2022)) with ESMTPSA id <0RL30102PLWO8B00@rn-mailsvcp-policy-lapp01.rno.apple.com>; Wed, 09 Nov 2022 12:50:48 -0800 (PST)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <7364ECF1-E0D5-40B7-A923-B4DA6CB4C1C0@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_55A800F1-4D20-4D57-86E8-3935A3F22E84"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3731.300.63.1.1\))
Date: Wed, 09 Nov 2022 12:50:38 -0800
In-reply-to: <CAHbrMsCfuirvL4pWG6ULyorfEfSEO9GWLNFSQAYjaSBDmbpS8A@mail.gmail.com>
Cc: Martin Thomson <mt@lowentropy.net>, MASQUE <masque@ietf.org>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
References: <976e7806-0e83-4090-95c5-7905f89fe02f@app.fastmail.com> <CAHbrMsCfuirvL4pWG6ULyorfEfSEO9GWLNFSQAYjaSBDmbpS8A@mail.gmail.com>
X-Mailer: Apple Mail (2.3731.300.63.1.1)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.545, 18.0.895 definitions=2022-11-09_06:2022-11-09, 2022-11-09 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/edpV69skjQ_9KbWNeB4wXQCpkA4>
Subject: Re: [Masque] QUIC non-encapsulation and CIDs
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multiplexed Application Substrate over QUIC Encryption <masque.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/masque>, <mailto:masque-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/masque/>
List-Post: <mailto:masque@ietf.org>
List-Help: <mailto:masque-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/masque>, <mailto:masque-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2022 20:51:19 -0000


> On Nov 9, 2022, at 12:05 PM, Ben Schwartz <bemasc=40google.com@dmarc.ietf.org> wrote:
> 
> On Wed, Nov 9, 2022 at 2:48 PM Martin Thomson <mt@lowentropy.net <mailto:mt@lowentropy.net>> wrote:
>> All of these are request-response exchanges
> 
> Nice.  I think this gets us pretty close to a system where we have a "forwarder" (essentially a load balancer running upside-down) that is created and managed via a REST API.
> 
> For example, the client could POST the Client Initial and target endpoint to the proxy to instantiate a session, and get the Server Initial in the response body, along with a forwarder endpoint.  Then the client can send short-header packets to the forwarder endpoint, using connection IDs that are mapped by another REST API call.

I’m not sure the request-response suggestion was to have these be separate HTTP requests. The old version of the draft did have separate requests, but request-response capsules are far cleaner.

Tommy
> -- 
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque

v2.23.0 | Report a Bug | By Email