
From nobody Sat Jun  8 13:14:20 2019
Return-Path: <mirja.kuehlewind@ericsson.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 25DA1120025; Sat,  8 Jun 2019 13:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 3H7B1wj2uHNg; Sat,  8 Jun 2019 13:14:16 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140047.outbound.protection.outlook.com [40.107.14.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28C41120074; Sat,  8 Jun 2019 13:14:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=nUMpcPr18ajIFsddXXQ1SEPGrRalST1j9SZkgqPOVU8=; b=pifMoYW41Z0zoD4Uo35VCrRj7MVqGjGYofa7EEiKSFPyppZYdTUG+Ot5hr/n9lydrusi9O9R+PxG6K0U0Uj057Iw+qr0SwNCBn9whv3+eNrb5Xt1S1Ajlj/0AUWqwXYOHuQYuOnkTKeuwqzQhiDPzVlIuhhHMInPKFdQbuC3fg8=
Received: from HE1PR07MB3148.eurprd07.prod.outlook.com (10.170.245.22) by HE1PR07MB3177.eurprd07.prod.outlook.com (10.170.245.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.5; Sat, 8 Jun 2019 20:14:11 +0000
Received: from HE1PR07MB3148.eurprd07.prod.outlook.com ([fe80::d44a:12cc:c916:92ca]) by HE1PR07MB3148.eurprd07.prod.outlook.com ([fe80::d44a:12cc:c916:92ca%7]) with mapi id 15.20.1987.008; Sat, 8 Jun 2019 20:14:11 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: "masque@ietf.org" <masque@ietf.org>
CC: "quic@ietf.org" <quic@ietf.org>
Thread-Topic: New Version Notification for draft-kuehlewind-quic-substrate-00.txt
Thread-Index: AQHVHUIiezeDbeUyN0i3J5nDupG4/qaSVHkA
Date: Sat, 8 Jun 2019 20:14:11 +0000
Message-ID: <A157660A-7087-4565-B1C6-23E35DE4D3FE@ericsson.com>
References: <155991978677.19940.1367137731581920871.idtracker@ietfa.amsl.com>
In-Reply-To: <155991978677.19940.1367137731581920871.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mirja.kuehlewind@ericsson.com; 
x-originating-ip: [2001:16b8:241b:1f00:8488:afdd:718e:6d11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 601bdcab-0060-48f6-db1a-08d6ec4ddefd
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:HE1PR07MB3177; 
x-ms-traffictypediagnostic: HE1PR07MB3177:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <HE1PR07MB317741F1A9D7385DD5D01609F4110@HE1PR07MB3177.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0062BDD52C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(136003)(376002)(396003)(366004)(346002)(189003)(199004)(53754006)(186003)(5660300002)(2501003)(66574012)(66946007)(66446008)(66556008)(478600001)(5640700003)(71190400001)(446003)(450100002)(83716004)(6916009)(8936002)(44832011)(2616005)(91956017)(73956011)(64756008)(476003)(46003)(6436002)(6506007)(4326008)(486006)(2351001)(11346002)(76176011)(82746002)(14454004)(316002)(305945005)(229853002)(36756003)(2473003)(71200400001)(99286004)(66476007)(6116002)(76116006)(2906002)(6306002)(1730700003)(14444005)(966005)(53936002)(256004)(15650500001)(6512007)(6486002)(25786009)(102836004)(33656002)(81166006)(81156014)(86362001)(7736002)(68736007)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3177; H:HE1PR07MB3148.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: B+sVhO2IstyQJfxGZGzY/RnHeABe/ALJ88zzhLduC3kbCUb8pMFobR/0GAo71QLwu5+aiX/dqChRzjF+hOGVyb1ybTo+EvuMcfTtcYHNNZKCUlj3+5aHmbfzLCCa9bmNQcCPEzLFRYJitAv6x1OUdyN5ZDxB3EWVhPqPNTtRlQH4/hKkNEOrgbp+wFVsL4mk5NJkFJS6tshp1CKLYHJm7MqGXfLfpVad3o6PsIkz7P2DTjqYrt6Fo/RMYStTpw3eDAa8jOBVIQyL/nv+JBCLVznfSk1rrq5CXuN6AinSYXtc5C5r4pqTH5r2B3bTSM7DVwzT9C7+EDLNZQuc6YHuTMeFPoz9yyE/tbJ9l0mvpPNLy5ux4quh6TMha/D3BdkeDt8DHe6B3iXTJRFMMCYgZ4fTSUFY1XqOlzFwqjAO1vo=
Content-Type: text/plain; charset="utf-8"
Content-ID: <E764A96447A94C43A6E19DD151670B05@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 601bdcab-0060-48f6-db1a-08d6ec4ddefd
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jun 2019 20:14:11.5240 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: mirja.kuehlewind@ericsson.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3177
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/tlf-yCPHeE3c8uQ_gBSnhGoyZh4>
Subject: [Masque] FW: New Version Notification for draft-kuehlewind-quic-substrate-00.txt
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 08 Jun 2019 20:14:19 -0000

SGkgZXZlcnlib2R5LA0KDQp3ZSd2ZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQgb24gdXNhZ2Ugc2Nl
bmFyaW9zIGZvciBRVUlDIGFzIHN1YnRyYWN0IGFuZCB0dW5uZWxpbmcuIFBsZWFzZSBzZWUgYmVs
b3cuIExldCB1cyBrbm93IGlmIHlvdSBoYXZlIGFueSBjb21tZW50cyBvciBvdGhlciB1c2UgY2Fz
ZXMuIEkgYWxzbyBoYXZlIHRoZSBkcmFmdCBvbiBteSBnaXRodWIuIFNvIHlvdSBjYW4gYWxzbyBv
cGVuIGlzc3VlcyBvciBzZW5kIFBScyB0aGVyZToNCg0KaHR0cHM6Ly9naXRodWIuY29tL21pcmph
ay9kcmFmdC1rdWVobGV3aW5kLXF1aWMtc3Vic3RyYXRlDQoNCkknbSBzZW5kaW5nIHRoaXMgbWFp
bCB0byB0aGUgbWFzcXVlIGxpc3QgYXMgd2VsbCBhcyBxdWljIGxpc3QgaW4gb3JkZXIgdG8gaW5m
b3JtIHBlb3BsZSB3aG8gbWF5IGJlIGludGVyZXN0ZWQuIEdpdmVuIHRoZSBxdWljIGxpc3QgaXMg
dXN1YWxseSBidXN5LCBJIHdvdWxkIHByb3Bvc2UgdG8gZGlyZWN0IGFsbCBkaXNjdXNzaW9uIHRv
IHRoZSBtYXNxdWUgbGlzdCAob25seSkuDQoNClRoYW5rcyENCk1pcmphDQoNCg0K77u/T24gMDcu
MDYuMTksIDE3OjAzLCAiaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIiA8aW50ZXJuZXQtZHJhZnRz
QGlldGYub3JnPiB3cm90ZToNCg0KICAgIA0KICAgIEEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFm
dC1rdWVobGV3aW5kLXF1aWMtc3Vic3RyYXRlLTAwLnR4dA0KICAgIGhhcyBiZWVuIHN1Y2Nlc3Nm
dWxseSBzdWJtaXR0ZWQgYnkgTWlyamEgS3VlaGxld2luZCBhbmQgcG9zdGVkIHRvIHRoZQ0KICAg
IElFVEYgcmVwb3NpdG9yeS4NCiAgICANCiAgICBOYW1lOgkJZHJhZnQta3VlaGxld2luZC1xdWlj
LXN1YnN0cmF0ZQ0KICAgIFJldmlzaW9uOgkwMA0KICAgIFRpdGxlOgkJVXNlIENhc2VzIGFuZCBS
ZXF1aXJlbWVudHMgZm9yIFFVSUMgYXMgYSBTdWJzdHJhdGUNCiAgICBEb2N1bWVudCBkYXRlOgky
MDE5LTA2LTA3DQogICAgR3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCiAgICBQYWdlczoJ
CTkNCiAgICBVUkw6ICAgICAgICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJh
ZnRzL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1zdWJzdHJhdGUtMDAudHh0DQogICAgU3RhdHVzOiAg
ICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWt1ZWhsZXdpbmQt
cXVpYy1zdWJzdHJhdGUvDQogICAgSHRtbGl6ZWQ6ICAgICAgIGh0dHBzOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9kcmFmdC1rdWVobGV3aW5kLXF1aWMtc3Vic3RyYXRlLTAwDQogICAgSHRtbGl6ZWQ6
ICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQta3VlaGxl
d2luZC1xdWljLXN1YnN0cmF0ZQ0KICAgIA0KICAgIA0KICAgIEFic3RyYWN0Og0KICAgICAgIFRD
UCBpcyBvZnRlbiB1c2VkIGFzIGEgcHJveHlpbmcgb3IgdHVubmVsaW5nIHByb3RvY29sLiAgUVVJ
QyBpcyBhDQogICAgICAgbmV3LCBlbWVyZ2luZyB0cmFuc3BvcnQgcHJvdG9jb2wgYW5kIHRoZXJl
IGlzIGEgc2ltaWxhciBleHBlY3RhdGlvbg0KICAgICAgIHRoYXQgaXQgdG9vIHdpbGwgYmUgdXNl
ZCBhcyBhIHN1YnN0cmF0ZSBvbmNlIGl0IGlzIHdpZGVseSBkZXBsb3llZC4NCiAgICAgICBVc2lu
ZyBRVUlDIGluc3RlYWQgb2YgVENQIGluIGV4aXN0aW5nIHNjZW5hcmlvcyB3aWxsIGFsbG93IHBy
b3h5aW5nDQogICAgICAgYW5kIHR1bm5lbGluZyBzZXJ2aWNlcyB0byBtYWludGFpbiB0aGUgYmVu
ZWZpdHMgb2YgUVVJQyBuYXRpdmVseSwNCiAgICAgICB3aXRob3V0IGRlZ3JhZGluZyB0aGUgcGVy
Zm9ybWFuY2UgYW5kIHNlY3VyaXR5IGNoYXJhY3RlcmlzdGljcy4gIFFVSUMNCiAgICAgICBhbHNv
IG9wZW5zIHVwIG5ldyBvcHBvcnR1bml0aWVzIGZvciB0aGVzZSBzZXJ2aWNlcyB0byBoYXZlIGxv
d2VyDQogICAgICAgbGF0ZW5jeSBhbmQgYmV0dGVyIG11bHRpc3RyZWFtaW5nIHN1cHBvcnQuICBU
aGlzIGRvY3VtZW50IHN1bW1hcml6ZXMNCiAgICAgICBjdXJyZW50IGFuZCBmdXR1cmUgdXNhZ2Ug
c2NlbmFyaW9zIHRvIGRlcml2ZSByZXF1aXJlbWVudHMgZm9yIFFVSUMNCiAgICAgICBhbmQgdG8g
cHJvdmlkZSBhZGRpdGlvbmFsIHByb3RvY29sIGNvbnNpZGVyYXRpb25zLg0KICAgIA0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICANCiAgICANCiAgICANCiAgICBQbGVhc2Ugbm90ZSB0aGF0
IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNz
aW9uDQogICAgdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJs
ZSBhdCB0b29scy5pZXRmLm9yZy4NCiAgICANCiAgICBUaGUgSUVURiBTZWNyZXRhcmlhdA0KICAg
IA0KICAgIA0KDQo=


From nobody Wed Jun 12 19:39:38 2019
Return-Path: <dschinazi.ietf@gmail.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 8831112016B for <masque@ietfa.amsl.com>; Wed, 12 Jun 2019 19:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XCggyi4i8Bev for <masque@ietfa.amsl.com>; Wed, 12 Jun 2019 19:39:35 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 072DF12008B for <masque@ietf.org>; Wed, 12 Jun 2019 19:39:35 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id 16so16927401ljv.10 for <masque@ietf.org>; Wed, 12 Jun 2019 19:39:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ywqxqUN3yYEzvsKyqIiLxXa5tkzUs5wZFPRnucb4BeY=; b=YZwXZl2CT14DU7lrgQ1i4/yuoQCLvDzrfP3mbdnVJEagJhCoNgT0hWw9fFcxFs0dx2 mXbH2AbRVXuenW1vNnlcLZUMglcweoWL4HSGQyRwSXbjcmaAchhR0hfLlh9dhOYyLRXd YVbtjttw0om2oe+8ZxuRG5HKPyGmWvKE7ckiYmWLX4hZB1cqXDZXloOn5yPebor4LRew iqU8Sf3AKW8gHBnD3VM23Mw3wFea0rbGNo4pJrvy3ZftcJRQ/AZD4mkeaUXU00uXAG1j 2sEy/Du9wKxt7NNw7IL59QSSBmxiXDPMgta4OTzKHsEvCAXi6CnKGTPFhETt51v3Beum 0EOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ywqxqUN3yYEzvsKyqIiLxXa5tkzUs5wZFPRnucb4BeY=; b=eil046gWpRZT19/HbQ9DIlVTMYoOtK937Mj5NI7P/iGEaYnKsGyRVcrC2IaLlzQlZi nrublMxDC5nTQHuZKrcapis/cCPU4i4YwFY9g87mn27zBW917R8nBY+fY3None4KarSt VwmYUdARYh5SWvHQdF4wiyDkUfOswObHRcvnR1fn4FlrYqwEEPKnwHIN3QZT1E5+RerA 7UjUWLwa9S7TbjPvIZy+czbPWy2dVI+fqGm1COzlVXW7En8m06XHLtekMfn7rRG+9Es8 8buHwQSnZ7k/AuDlt8Xv/mOWfkwlNbOMOjLYD+jRuqDnjOZzs3OARkMeJkVdQE9tqGHZ zIyA==
X-Gm-Message-State: APjAAAW+6C1PqIjF2uusKD474FEvA11r43D06qPJ40UgDsth02EZcgaU 30GbuifGtne7mLh2Z9it+R3CwwH77+0nMuY8zzJA0g==
X-Google-Smtp-Source: APXvYqxXZx6IcfSj96QGtugLNXPqn1DIShn18+RiLbTW1oA9RXiPZF3ghJSQ4oM+1IIVXCJNDn3Q65/OEmvyQYBqbds=
X-Received: by 2002:a05:651c:150:: with SMTP id c16mr3938278ljd.193.1560393573193;  Wed, 12 Jun 2019 19:39:33 -0700 (PDT)
MIME-Version: 1.0
References: <273b9eaf-5d9d-949f-7d43-95293248f43f@huitema.net> <CAPDSy+5neR6j7VCeXs=uqTWDP8EwmFGjW4DCw3t3b8tFMp7AdA@mail.gmail.com>
In-Reply-To: <CAPDSy+5neR6j7VCeXs=uqTWDP8EwmFGjW4DCw3t3b8tFMp7AdA@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 12 Jun 2019 19:39:21 -0700
Message-ID: <CAPDSy+4Dj5-nnKDCRAdch=MgwgZ=73EjFvWxwwgLrqCOB7NHLg@mail.gmail.com>
To: Christian Huitema <huitema@huitema.net>
Cc: masque@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a3ddb8058b2b70d3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/oL1gE2pzl4B1Q5gCteqWP_Ym1d4>
Subject: Re: [Masque] QUIC proxy scenarios
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Jun 2019 02:39:38 -0000

--000000000000a3ddb8058b2b70d3
Content-Type: text/plain; charset="UTF-8"

Hi Christian,

Apologies for the delayed response, it's been a busy few weeks.

I've taken a lot of text from your PR
<https://github.com/DavidSchinazi/masque-drafts/pull/2/files> and added it
to the document.
I think we can have MASQUE be a framework where both proxy and VPN can be
negotiated and co-exist.

Please let me know what you think of the latest text
<https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.html>.

I'm thinking as a next step we may want to flesh out the details of the QUIC
proxy
<https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.html#rfc.section.5.4>?
(e.g., how to negotiate its use and to compress QUIC connection IDs)

Thanks,
David


On Tue, May 21, 2019 at 3:59 AM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

> Hi Christian,
>
> These are definitely interesting use-cases, and I think the draft could
> use more text to that extent.
>
> A pull request would be most welcome!
> https://github.com/DavidSchinazi/masque-drafts
>
> In the Home Server Scenario, can you elaborate on who the
> client/server/proxy is? Is the goal to access home services from anywhere
> in the Internet?
>
> David
>
> On Tue, May 21, 2019 at 10:04 AM Christian Huitema <huitema@huitema.net>
> wrote:
>
>> During the first day of the QUIC interop in London, we discussed the
>> scenarios for a QUIC proxy. This is what I am looking at:
>>
>>
>> # Scenarios
>>
>> ## Home Server Scenario
>>
>> Home server establishes QUIC connection with proxy server "in the
>> cloud", publishes name in DNS with address of cloud server.
>> Client sends QUIC messages to proxy.
>> Proxy recognizes the SNI in Initial packets, or the Destination CID in
>> handhsake and short packets.
>> Proxy forwards packets to QUIC server as "datagram".
>> Home server treat packets as if received on UDP socket.
>> Home server forwards packets to proxy as datagram.
>> Proxy relays QUIC packets to the client.
>>
>> Optional: QUIC server may use the "preferred address" mechanism to
>> suggest migration to a direct connection, bypassing the proxy.
>> Optional: local clients may discover the local server, without using the
>> proxy.
>>
>> ## Hidden client scenario
>>
>> Client establishes connection with proxy. Sends QUIC messages to proxy
>> as datagrams.
>> Proxy decapsulates the messages, sends them to destination server.
>> Destination server replies to proxy.
>> Proxy examines CID, determines which client it belongs to, forwards QUIC
>> messages as Datagrams to appropriate destination.
>>
>> ## Onion scenario
>>
>> Client establishes connection to proxy, then through that to another,
>> etc. This creates a tree of proxies rooted at the client.
>> QUIC connections are mapped to a specific branch of the tree.
>>
>> Hidden server can similarly hide between several layers of proxy. Hidden
>> servers should not publish their address in the DNS.
>> May use an Onion DHT service instead (see Tor ".onion"), or in fact any
>> other mechanism. This is out of scope in this spec.
>>
>> -- Christian Huitema
>>
>> --
>> Masque mailing list
>> Masque@ietf.org
>> https://www.ietf.org/mailman/listinfo/masque
>>
>

--000000000000a3ddb8058b2b70d3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Christian,<div><br></div><div>Apologies for the delayed=
 response, it&#39;s been a busy few weeks.</div><div><br></div><div>I&#39;v=
e taken a lot of text from <a href=3D"https://github.com/DavidSchinazi/masq=
ue-drafts/pull/2/files">your PR</a> and added it to the document.</div><div=
>I think we can have MASQUE be a framework where both proxy and VPN can be =
negotiated and co-exist.</div><div><br></div><div>Please let me know what y=
ou think of <a href=3D"https://davidschinazi.github.io/masque-drafts/draft-=
schinazi-masque.html">the latest text</a>.</div><div><br></div><div>I&#39;m=
 thinking as a next step we may want to flesh out the details of the <a hre=
f=3D"https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.ht=
ml#rfc.section.5.4">QUIC proxy</a>? (e.g., how to negotiate its use and to =
compress QUIC connection IDs)</div><div><br></div><div>Thanks,</div><div>Da=
vid</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Tue, May 21, 2019 at 3:59 AM David Schinazi &lt;=
<a href=3D"mailto:dschinazi.ietf@gmail.com" target=3D"_blank">dschinazi.iet=
f@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">Hi Christian,<div><br></div><d=
iv>These are definitely interesting use-cases, and I think the draft could =
use more text to that extent.</div><div><br></div><div>A pull request would=
 be most welcome!</div><div><a href=3D"https://github.com/DavidSchinazi/mas=
que-drafts" target=3D"_blank">https://github.com/DavidSchinazi/masque-draft=
s</a><br></div><div><br></div><div>In the=C2=A0Home Server Scenario, can yo=
u elaborate on who the client/server/proxy is? Is the goal to access home s=
ervices from anywhere in the Internet?</div><div><br></div><div>David</div>=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Tue, May 21, 2019 at 10:04 AM Christian Huitema &lt;<a href=3D"mai=
lto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">During the fi=
rst day of the QUIC interop in London, we discussed the<br>
scenarios for a QUIC proxy. This is what I am looking at:<br>
<br>
<br>
# Scenarios<br>
<br>
## Home Server Scenario<br>
<br>
Home server establishes QUIC connection with proxy server &quot;in the<br>
cloud&quot;, publishes name in DNS with address of cloud server.<br>
Client sends QUIC messages to proxy.<br>
Proxy recognizes the SNI in Initial packets, or the Destination CID in<br>
handhsake and short packets.<br>
Proxy forwards packets to QUIC server as &quot;datagram&quot;.<br>
Home server treat packets as if received on UDP socket.<br>
Home server forwards packets to proxy as datagram.<br>
Proxy relays QUIC packets to the client.<br>
<br>
Optional: QUIC server may use the &quot;preferred address&quot; mechanism t=
o<br>
suggest migration to a direct connection, bypassing the proxy.<br>
Optional: local clients may discover the local server, without using the<br=
>
proxy.<br>
<br>
## Hidden client scenario<br>
<br>
Client establishes connection with proxy. Sends QUIC messages to proxy<br>
as datagrams.<br>
Proxy decapsulates the messages, sends them to destination server.<br>
Destination server replies to proxy.<br>
Proxy examines CID, determines which client it belongs to, forwards QUIC<br=
>
messages as Datagrams to appropriate destination.<br>
<br>
## Onion scenario<br>
<br>
Client establishes connection to proxy, then through that to another,<br>
etc. This creates a tree of proxies rooted at the client.<br>
QUIC connections are mapped to a specific branch of the tree.<br>
<br>
Hidden server can similarly hide between several layers of proxy. Hidden<br=
>
servers should not publish their address in the DNS.<br>
May use an Onion DHT service instead (see Tor &quot;.onion&quot;), or in fa=
ct any<br>
other mechanism. This is out of scope in this spec.<br>
<br>
-- Christian Huitema<br>
<br>
-- <br>
Masque mailing list<br>
<a href=3D"mailto:Masque@ietf.org" target=3D"_blank">Masque@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/masque" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/masque</a><br>
</blockquote></div>
</blockquote></div>

--000000000000a3ddb8058b2b70d3--


From nobody Wed Jun 12 20:16:37 2019
Return-Path: <huitema@huitema.net>
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 7641E120177 for <masque@ietfa.amsl.com>; Wed, 12 Jun 2019 20:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.013
X-Spam-Level: 
X-Spam-Status: No, score=-3.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.415, SPF_HELO_NONE=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 tXyojo0BOMxV for <masque@ietfa.amsl.com>; Wed, 12 Jun 2019 20:16:34 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 29213120169 for <masque@ietf.org>; Wed, 12 Jun 2019 20:16:33 -0700 (PDT)
Received: from [66.113.192.14] (helo=xsmtp06.mail2web.com) by mx66.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1hbGE2-000ADK-Ox for masque@ietf.org; Thu, 13 Jun 2019 05:16:32 +0200
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp06.mail2web.com with esmtp (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1hbGDy-0003iO-0i for masque@ietf.org; Wed, 12 Jun 2019 23:16:27 -0400
Received: (qmail 20400 invoked from network); 13 Jun 2019 03:16:23 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.223]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <masque@ietf.org>; 13 Jun 2019 03:16:23 -0000
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: masque@ietf.org
References: <273b9eaf-5d9d-949f-7d43-95293248f43f@huitema.net> <CAPDSy+5neR6j7VCeXs=uqTWDP8EwmFGjW4DCw3t3b8tFMp7AdA@mail.gmail.com> <CAPDSy+4Dj5-nnKDCRAdch=MgwgZ=73EjFvWxwwgLrqCOB7NHLg@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <05fc564e-6eef-9663-4991-7de735434659@huitema.net>
Date: Wed, 12 Jun 2019 20:16:23 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <CAPDSy+4Dj5-nnKDCRAdch=MgwgZ=73EjFvWxwwgLrqCOB7NHLg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------F67C0BC9BCDA2782616C9577"
Content-Language: en-US
X-Originating-IP: 66.113.192.14
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.192.14
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.192.14@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: ham
X-Spampanel-Outgoing-Evidence: Combined (0.05)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0Q9DGisTdy29Heef28Cu3sipSDasLI4SayDByyq9LIhVI9tibm/OsjBn A3ikzdCcCETNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDLFrcqaxDIU8vFldGbCR/osRX qYbtEQV1z/L435ZRxFRcyUiLYXi9Oqr0cPRcN/iU5EYKk9ePgXGbt5xuMhAKm1ZiUSAofzQZyw1N o2+95uScbEFMQEHcY1gOuErbvRTKK5uN4Nhp7uOkWlmbQCkb20TPhU3goSfeZ3FRZeTXp/1uwfTD UUz/IMrauEP0IARAT9bZnTCIQ4C96g4mKe6NiGYbkIWSKodQEiewuMhOtmK5/BpNYAQEvig3GMx7 MpXZ3WOGcz8xu9rZctX8sgTNoiY/SOc5OwzuESxfsyWF3826CT9M1stWoUTybRqU5J7031/E3ahF 5MMcDI7KdpjQKU5lRZ094UyTENZdfY1zhq4hEWyJzIkwSFAW0Pw8uiKe79Ir/Me7RAJ5cVVkcq6a It2zYvPTd+DTpPBZoZwGv5Fn6p9MIdoVmwQd+5hcJZ3T6J1fhOzjF0b4LXcjJZ5louZdkd+OFbW3 tZOhTHnfaNaUwbkUC3efQxX081Uu4CHRXS97PvK9t7qTKwm0TQlPrYe5ALa+6loncFiHKXZysSaD LT4PBIvkxZFg1HsGn09MNQSIKMznUZcFqGs41thPHj3KyNX+kDcmnP+9Ez78VNaLBDMrD7q/cJog wbqzsuokhGmaOYL/X8rhoXFOgTB1ujSxnqQ5eTkkXXEhnQlrl1oKbAAMMhWe/rIDnPorDxie/ymH KVf3AgfEiVP9XNrw1B7Oiwo2XvIlW0xK+GaMnDxO8iSbXbehPAyorygrFjnWuVGBtJ1DsK23UcLY dhI56G6gIHbmXm17lUweLCEIWKlP9DbK43kvDm9XK01IC3BpIRFsicyJMEhQFtD8PLoink2oV0uz 1ws450298AxBBxbzOWlxaUzOk1oSeJNWp1+1XkgMLOZvYCakZp5atAhVig==
X-Report-Abuse-To: spam@quarantine9.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/C_fA1z__6Cnw74I3fQE7P5K9fok>
Subject: Re: [Masque] QUIC proxy scenarios
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Jun 2019 03:16:37 -0000

This is a multi-part message in MIME format.
--------------F67C0BC9BCDA2782616C9577
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 6/12/2019 7:39 PM, David Schinazi wrote:
> Hi Christian,
>
> Apologies for the delayed response, it's been a busy few weeks.
>
> I've taken a lot of text from your PR
> <https://github.com/DavidSchinazi/masque-drafts/pull/2/files> and
> added it to the document.
> I think we can have MASQUE be a framework where both proxy and VPN can
> be negotiated and co-exist.
>
> Please let me know what you think of the latest text
> <https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.ht=
ml>.

Looks good.


>
> I'm thinking as a next step we may want to flesh out the details of
> the QUIC proxy
> <https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.ht=
ml#rfc.section.5.4>?
> (e.g., how to negotiate its use and to compress QUIC connection IDs)

Yes. This is something that I want to start implementing soon, but first
I need to implement ESNI in picoquic, which will probably take a week.
Then I will need to align to draft 21 when it comes out...

There are a couple drafts that we may want to also consider, notably
Mirja's requirement draft, and the load balancer draft -- many common
points between a proxy and a load balancer.

I have been thinking about the management of connection ID. The big
question is whether we want to have a proxy serve multiple home servers
or home clients (I believe the answer is yes), and also whether the home
server wants to be able to use multiple proxies. The latter requirement
drives some additional complexity.

The basic scenario will be:

1) Client and proxy negotiate usage by the client of a set of CID

2) Client announces one of those CID during handshake

3) Peer sends packet to proxy with CID, proxy relays to client

4) Client sends the other CID to the peer in NCID frame

5) Peer picks one of those when migrating to new address

6) Proxy recognizes CID and routes to client.

7) Peer sends RETIRE CID frame to client

8) Client tells the server that retired CID are not useful anymore

9) Client cleans the connection, and tell the peer to retire all CID

The client (in some cases) may want to use migration to establish a
direct connection and bypass the proxy. That migration will consume some
of the negotiated CID.

If we want client (home servers) to support several proxies, then the
same set of CID must be negotiated with multiple proxies. This implies
something like:

a) Client proposes a set of new CID to proxy1

b) Proxy1 checks whether the CID collides with something used by another
client, marks the colliding ones as rejected

c) Proxy1 replies with the accepted subset

d) Client proposes accepted subset to proxy2

e) Proxy2 does its own checks, reply with a subset of confirmed CID

f) Client is polite and retires the CID rejected by proxy2 from the set
managed by proxy1

Proxies may want to impose some minimal CID length.

-- Christian Huitema







--------------F67C0BC9BCDA2782616C9577
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 6/12/2019 7:39 PM, David Schinazi
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAPDSy+4Dj5-nnKDCRAdch=MgwgZ=73EjFvWxwwgLrqCOB7NHLg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Hi Christian,
        <div><br>
        </div>
        <div>Apologies for the delayed response, it's been a busy few
          weeks.</div>
        <div><br>
        </div>
        <div>I've taken a lot of text from <a
            href="https://github.com/DavidSchinazi/masque-drafts/pull/2/files"
            moz-do-not-send="true">your PR</a> and added it to the
          document.</div>
        <div>I think we can have MASQUE be a framework where both proxy
          and VPN can be negotiated and co-exist.</div>
        <div><br>
        </div>
        <div>Please let me know what you think of <a
href="https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.html"
            moz-do-not-send="true">the latest text</a>.</div>
      </div>
    </blockquote>
    <p>Looks good.<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
cite="mid:CAPDSy+4Dj5-nnKDCRAdch=MgwgZ=73EjFvWxwwgLrqCOB7NHLg@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>I'm thinking as a next step we may want to flesh out the
          details of the <a
href="https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.html#rfc.section.5.4"
            moz-do-not-send="true">QUIC proxy</a>? (e.g., how to
          negotiate its use and to compress QUIC connection IDs)</div>
      </div>
    </blockquote>
    <p>Yes. This is something that I want to start implementing soon,
      but first I need to implement ESNI in picoquic, which will
      probably take a week. Then I will need to align to draft 21 when
      it comes out...</p>
    <p>There are a couple drafts that we may want to also consider,
      notably Mirja's requirement draft, and the load balancer draft --
      many common points between a proxy and a load balancer.</p>
    <p>I have been thinking about the management of connection ID. The
      big question is whether we want to have a proxy serve multiple
      home servers or home clients (I believe the answer is yes), and
      also whether the home server wants to be able to use multiple
      proxies. The latter requirement drives some additional complexity.</p>
    <p>The basic scenario will be:</p>
    <p>1) Client and proxy negotiate usage by the client of a set of CID</p>
    <p>2) Client announces one of those CID during handshake</p>
    <p>3) Peer sends packet to proxy with CID, proxy relays to client<br>
    </p>
    <p>4) Client sends the other CID to the peer in NCID frame</p>
    <p>5) Peer picks one of those when migrating to new address</p>
    <p>6) Proxy recognizes CID and routes to client.</p>
    <p>7) Peer sends RETIRE CID frame to client</p>
    <p>8) Client tells the server that retired CID are not useful
      anymore</p>
    <p>9) Client cleans the connection, and tell the peer to retire all
      CID</p>
    <p>The client (in some cases) may want to use migration to establish
      a direct connection and bypass the proxy. That migration will
      consume some of the negotiated CID.<br>
    </p>
    <p>If we want client (home servers) to support several proxies, then
      the same set of CID must be negotiated with multiple proxies. This
      implies something like:</p>
    <p>a) Client proposes a set of new CID to proxy1</p>
    <p>b) Proxy1 checks whether the CID collides with something used by
      another client, marks the colliding ones as rejected<br>
    </p>
    <p>c) Proxy1 replies with the accepted subset</p>
    <p>d) Client proposes accepted subset to proxy2</p>
    <p>e) Proxy2 does its own checks, reply with a subset of confirmed
      CID</p>
    <p>f) Client is polite and retires the CID rejected by proxy2 from
      the set managed by proxy1</p>
    <p>Proxies may want to impose some minimal CID length.</p>
    <p>-- Christian Huitema<br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------F67C0BC9BCDA2782616C9577--


From nobody Thu Jun 13 09:48:57 2019
Return-Path: <dschinazi.ietf@gmail.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 01C9A120164 for <masque@ietfa.amsl.com>; Thu, 13 Jun 2019 09:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mcDYgh06MEWW for <masque@ietfa.amsl.com>; Thu, 13 Jun 2019 09:48:44 -0700 (PDT)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B84D12044D for <masque@ietf.org>; Thu, 13 Jun 2019 09:48:44 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id t28so19203126lje.9 for <masque@ietf.org>; Thu, 13 Jun 2019 09:48:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=h2/d3cWiccNI+m+972lGQ2mdZSsYi2y/5eiPhtg5GY0=; b=VY3uCPy36tq9O77q0iwDWBVGF9zCEJ5cRjqkOuU0Zn55k59/uwIMcoZhT9T0nFr07r PxJAXQlKcMveEWt4LHen6dCo4C3AYJ6LRB+WiJK4h0jetO9TXKHRKM9NMZHx3VNYtk3B Bm6NAHw4+FUpE2vtWruzY17NAGh2U1LF403gpVSY+4ol4dR6XsO7Zdnkwbbd/LnVNXPb a8+WUpJ+RF1kX2sFFurQBdOuWXbGs+vbst16ed0EcPDlCTEl0u0hPyDzTV6UbNSAHewf ZETOA3o/gQkmD87wxjCNO2Q+rzcYykwxYuf5InQrDidDiOkpomDfW1vsvRuY78ejbxg1 3BqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=h2/d3cWiccNI+m+972lGQ2mdZSsYi2y/5eiPhtg5GY0=; b=q4AhztQQMGc9hbJek7TDa81T4Y9fn23UuO9fpyFvu/jQZwnMiZl2Rx5UgDOJZYtDWq as5sIrRDfce6VpBk7gM6v2RvPl5u9ZRCCJUPSS3GbR1iepFNSniHB5VK6ZOHP/Q735bV fIm0IjkCnPMOuYy47d2D+nbwYiVznA4OQ9HG/1UuowkStigSACYmjqS2z+o3cNG/iGV9 FtygoVswuj+zHVgR3U+xMWqIqJ+a6bLdVl4dCyJVB0TOuv2ddx57YLpRyqcoPbv2ErkQ xkhZfIYhuGjX1/QXHYcQ1PA1vYWNAVkIlpKw5h4wR0xOnmlJyEacsU9ejCpu/RCuQOR7 Cp+A==
X-Gm-Message-State: APjAAAX2e6gfUvx5Ke3bpDfpmhDuO3V0Nd9ha1hWK2k3KKQMEStRbvOv 5FgxII6VNImQcxofKerupFLra5WzSf2dcSTbzsaZvg==
X-Google-Smtp-Source: APXvYqxfir7SXynfErdWfkqOa9G7hGRw1XKYPwo94hKSqbQpMYuqajbvdy0gabAEozfDFu/IN/hmOW0rQ+exWpSR4es=
X-Received: by 2002:a2e:82c5:: with SMTP id n5mr8406556ljh.175.1560444522306;  Thu, 13 Jun 2019 09:48:42 -0700 (PDT)
MIME-Version: 1.0
References: <273b9eaf-5d9d-949f-7d43-95293248f43f@huitema.net> <CAPDSy+5neR6j7VCeXs=uqTWDP8EwmFGjW4DCw3t3b8tFMp7AdA@mail.gmail.com> <CAPDSy+4Dj5-nnKDCRAdch=MgwgZ=73EjFvWxwwgLrqCOB7NHLg@mail.gmail.com> <05fc564e-6eef-9663-4991-7de735434659@huitema.net>
In-Reply-To: <05fc564e-6eef-9663-4991-7de735434659@huitema.net>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 13 Jun 2019 09:48:31 -0700
Message-ID: <CAPDSy+6QEzv6BKhjQhADXW3V=2nsV9zZkVz6Uy2XH7vX0C7ZVg@mail.gmail.com>
To: Christian Huitema <huitema@huitema.net>
Cc: masque@ietf.org
Content-Type: multipart/alternative; boundary="00000000000071a1ff058b374d6c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/U0fXPpU4nJAjeUYISZTvVpQyIUU>
Subject: Re: [Masque] QUIC proxy scenarios
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Jun 2019 16:48:55 -0000

--00000000000071a1ff058b374d6c
Content-Type: text/plain; charset="UTF-8"

I was thinking among the same lines. I think their are three ways the proxy
can vend CIDs to clients:
(1) server says minimum length is X, clients generate them pseudo-randomly
and we hope to avoid collisions
(2) server vends individual CIDs
(3) server vends a scheme, e.g.: CID is AES_ECB(key, prefix || client
chosen bytes) and server tells client key and prefix and client can
increment the client chosen bytes for each new CID

I think (1) should work well enough in practice. Today Google QUIC CIDs are
64bits randomly chosen by clients and we operate at massive scales without
collisions being an issue yet.
(2) and (3) unfortunately break down when you have multiple servers

But if we want to handle collisions while assuming they're rare, using (1)
with a way for proxies to reject CIDs should work.

On Wed, Jun 12, 2019 at 8:16 PM Christian Huitema <huitema@huitema.net>
wrote:

>
> On 6/12/2019 7:39 PM, David Schinazi wrote:
>
> Hi Christian,
>
> Apologies for the delayed response, it's been a busy few weeks.
>
> I've taken a lot of text from your PR
> <https://github.com/DavidSchinazi/masque-drafts/pull/2/files> and added
> it to the document.
> I think we can have MASQUE be a framework where both proxy and VPN can be
> negotiated and co-exist.
>
> Please let me know what you think of the latest text
> <https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.html>
> .
>
> Looks good.
>
>
>
> I'm thinking as a next step we may want to flesh out the details of the QUIC
> proxy
> <https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.html#rfc.section.5.4>?
> (e.g., how to negotiate its use and to compress QUIC connection IDs)
>
> Yes. This is something that I want to start implementing soon, but first I
> need to implement ESNI in picoquic, which will probably take a week. Then I
> will need to align to draft 21 when it comes out...
>
> There are a couple drafts that we may want to also consider, notably
> Mirja's requirement draft, and the load balancer draft -- many common
> points between a proxy and a load balancer.
>
> I have been thinking about the management of connection ID. The big
> question is whether we want to have a proxy serve multiple home servers or
> home clients (I believe the answer is yes), and also whether the home
> server wants to be able to use multiple proxies. The latter requirement
> drives some additional complexity.
>
> The basic scenario will be:
>
> 1) Client and proxy negotiate usage by the client of a set of CID
>
> 2) Client announces one of those CID during handshake
>
> 3) Peer sends packet to proxy with CID, proxy relays to client
>
> 4) Client sends the other CID to the peer in NCID frame
>
> 5) Peer picks one of those when migrating to new address
>
> 6) Proxy recognizes CID and routes to client.
>
> 7) Peer sends RETIRE CID frame to client
>
> 8) Client tells the server that retired CID are not useful anymore
>
> 9) Client cleans the connection, and tell the peer to retire all CID
>
> The client (in some cases) may want to use migration to establish a direct
> connection and bypass the proxy. That migration will consume some of the
> negotiated CID.
>
> If we want client (home servers) to support several proxies, then the same
> set of CID must be negotiated with multiple proxies. This implies something
> like:
>
> a) Client proposes a set of new CID to proxy1
>
> b) Proxy1 checks whether the CID collides with something used by another
> client, marks the colliding ones as rejected
>
> c) Proxy1 replies with the accepted subset
>
> d) Client proposes accepted subset to proxy2
>
> e) Proxy2 does its own checks, reply with a subset of confirmed CID
>
> f) Client is polite and retires the CID rejected by proxy2 from the set
> managed by proxy1
>
> Proxies may want to impose some minimal CID length.
>
> -- Christian Huitema
>
>
>
>
>
>
> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
>

--00000000000071a1ff058b374d6c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I was thinking among the same lines. I think their are thr=
ee ways the proxy can vend CIDs to clients:<div>(1) server says minimum len=
gth is X, clients generate them pseudo-randomly and we hope to avoid collis=
ions</div><div>(2) server vends individual CIDs</div><div>(3) server vends =
a scheme, e.g.: CID is AES_ECB(key, prefix || client chosen bytes) and serv=
er tells client key and prefix and client can increment the client chosen b=
ytes for each new CID</div><div><br></div><div>I think (1) should work well=
 enough in practice. Today Google QUIC CIDs are 64bits randomly chosen by c=
lients and we operate at massive scales without collisions being an issue y=
et.</div><div>(2) and (3) unfortunately break down when you have multiple s=
ervers</div><div><br></div><div>But if we want to handle collisions while a=
ssuming they&#39;re rare, using (1) with a way for proxies to reject CIDs s=
hould work.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Wed, Jun 12, 2019 at 8:16 PM Christian Huitema &lt;<a h=
ref=3D"mailto:huitema@huitema.net">huitema@huitema.net</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    <p><br>
    </p>
    <div class=3D"gmail-m_3553624377135112625moz-cite-prefix">On 6/12/2019 =
7:39 PM, David Schinazi
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Hi Christian,
        <div><br>
        </div>
        <div>Apologies for the delayed response, it&#39;s been a busy few
          weeks.</div>
        <div><br>
        </div>
        <div>I&#39;ve taken a lot of text from <a href=3D"https://github.co=
m/DavidSchinazi/masque-drafts/pull/2/files" target=3D"_blank">your PR</a> a=
nd added it to the
          document.</div>
        <div>I think we can have MASQUE be a framework where both proxy
          and VPN can be negotiated and co-exist.</div>
        <div><br>
        </div>
        <div>Please let me know what you think of <a href=3D"https://davids=
chinazi.github.io/masque-drafts/draft-schinazi-masque.html" target=3D"_blan=
k">the latest text</a>.</div>
      </div>
    </blockquote>
    <p>Looks good.<br>
    </p>
    <p><br>
    </p>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><br>
        </div>
        <div>I&#39;m thinking as a next step we may want to flesh out the
          details of the <a href=3D"https://davidschinazi.github.io/masque-=
drafts/draft-schinazi-masque.html#rfc.section.5.4" target=3D"_blank">QUIC p=
roxy</a>? (e.g., how to
          negotiate its use and to compress QUIC connection IDs)</div>
      </div>
    </blockquote>
    <p>Yes. This is something that I want to start implementing soon,
      but first I need to implement ESNI in picoquic, which will
      probably take a week. Then I will need to align to draft 21 when
      it comes out...</p>
    <p>There are a couple drafts that we may want to also consider,
      notably Mirja&#39;s requirement draft, and the load balancer draft --
      many common points between a proxy and a load balancer.</p>
    <p>I have been thinking about the management of connection ID. The
      big question is whether we want to have a proxy serve multiple
      home servers or home clients (I believe the answer is yes), and
      also whether the home server wants to be able to use multiple
      proxies. The latter requirement drives some additional complexity.</p=
>
    <p>The basic scenario will be:</p>
    <p>1) Client and proxy negotiate usage by the client of a set of CID</p=
>
    <p>2) Client announces one of those CID during handshake</p>
    <p>3) Peer sends packet to proxy with CID, proxy relays to client<br>
    </p>
    <p>4) Client sends the other CID to the peer in NCID frame</p>
    <p>5) Peer picks one of those when migrating to new address</p>
    <p>6) Proxy recognizes CID and routes to client.</p>
    <p>7) Peer sends RETIRE CID frame to client</p>
    <p>8) Client tells the server that retired CID are not useful
      anymore</p>
    <p>9) Client cleans the connection, and tell the peer to retire all
      CID</p>
    <p>The client (in some cases) may want to use migration to establish
      a direct connection and bypass the proxy. That migration will
      consume some of the negotiated CID.<br>
    </p>
    <p>If we want client (home servers) to support several proxies, then
      the same set of CID must be negotiated with multiple proxies. This
      implies something like:</p>
    <p>a) Client proposes a set of new CID to proxy1</p>
    <p>b) Proxy1 checks whether the CID collides with something used by
      another client, marks the colliding ones as rejected<br>
    </p>
    <p>c) Proxy1 replies with the accepted subset</p>
    <p>d) Client proposes accepted subset to proxy2</p>
    <p>e) Proxy2 does its own checks, reply with a subset of confirmed
      CID</p>
    <p>f) Client is polite and retires the CID rejected by proxy2 from
      the set managed by proxy1</p>
    <p>Proxies may want to impose some minimal CID length.</p>
    <p>-- Christian Huitema<br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
  </div>

-- <br>
Masque mailing list<br>
<a href=3D"mailto:Masque@ietf.org" target=3D"_blank">Masque@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/masque" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/masque</a><br>
</blockquote></div>

--00000000000071a1ff058b374d6c--


From nobody Wed Jun 19 10:00:05 2019
Return-Path: <mcmanus@ducksong.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 50CBC12012B for <masque@ietfa.amsl.com>; Wed, 19 Jun 2019 10:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=gGF1gu09; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=Vb/RiiLx
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 FxZwbokHXQTa for <masque@ietfa.amsl.com>; Wed, 19 Jun 2019 10:00:00 -0700 (PDT)
Received: from outbound2r.ore.mailhop.org (outbound2r.ore.mailhop.org [54.200.129.228]) (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 AF03112030D for <masque@ietf.org>; Wed, 19 Jun 2019 10:00:00 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1560963599; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=SSnFKFDT0g6VM+1HrzMzjzRZiSg4QS7g6wSBbIrhtHrSA+AuYLr/7ZCugnJwDToWOd3a9C3HDSrOS jqRKoIpfbvgw/t9rcpZe4kuFh8bi+izfXOf8b0QDFmTSrjWg/FOXdXcP2R8i85oOBzVDaF7eHGHvZw DmyvxkxmJAkh4QsEX79fMKCPTzLYdVB49bCyt8cGbp6hHIu1m3uhsz1L8HQJ1uVwJak/lZsACWl+W+ Q3FiHmkQsbiG03gdz0xOSmwP+iiFI0gwlA/AR9t4wthzEYHyZK3K/BgF0SSVZEzvcSXFqttSMcqZAF yIzkFMsUsO1UwmFNUZnD/KZ9uiI0zRg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:to:subject:message-id:date:from:mime-version:dkim-signature: dkim-signature:from; bh=515zZPm3N5FY/oi0d9syhQB85SWrjAEmbHMCavf0VBY=; b=V8jT7Odxq2FVKVxeiv9sBkqpfO7VAP6AEZp+dZPOKaXObglANhlqVPAR7ONLbmk2Yv3OKcB9yWkci nZQSNMdql9oZVEuCl9hQ5RyiaBku4MML28d/6wdpm4hGG9CU6jz20dqJQip4zUJ7Ty479ijwZnFKJl JPK9DflEpCo1LN8gb3Sq8pBi2Mh/Goc6dWmpRK6ZnayMVQjHs0EZg3S/hwswA9h5wZKCNKibe2jnR+ EFaMH8MSe1Ob62ZuhrspsANHAh34FjjYgIXUh75S5B4j3+PKX2gFDgucsQ6OiKBirH8fDcviqe71nv 4ZSSMevsYNJvvRdVuRTDnul4TjkHlbg==
ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.210.47; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:to:subject:message-id:date:from:mime-version:from; bh=515zZPm3N5FY/oi0d9syhQB85SWrjAEmbHMCavf0VBY=; b=gGF1gu09dNf54UPpy2z1Gb5KdQXwZ5evnlYRttq6BCMgLwCFjkDuFvirLLV+zpkriGnMgMLxONY3U ThT/ihPxpS/zIUB1SMeGGwv28ppAfip11U2bFjyB0H9Gtkgo01g+F/iKqZC6w75AEEG8RNGWt5AqdJ LyN/tyo1cNj/rKAU=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:to:subject:message-id:date:from:mime-version:from; bh=515zZPm3N5FY/oi0d9syhQB85SWrjAEmbHMCavf0VBY=; b=Vb/RiiLxLKNUKOJemvUDBBd4JxBeYsTedKJEWO/YdKRgICYvkMJ5jwp1v6Wb5zQlCbwa+ea3ETz6s HRdS8KcYPVhgQA4wV7ebZOMsi62UnczMNAW0q0LP9RpNQtbyZj9crG/nxcbhcfQJtLqcoYY0BaEE8o 1bcR/e/4dHSBWXyCJND1hr4oWt8xHSHkbPOlKH/mIZ6Us7tjJ0y2H0QDpj4rIecyB0gg/53rED87/9 Ko0/EaY2infgk7n/1LgMumNTw+Fi72Q98xIxbtek4pExPBQ1esWaAV0qEX8qk4nXBxEh1O45QbGiZD vuV/3gci9KQjUD3s+2cW7QUPXR7OlkA==
X-MHO-RoutePath: bWNtYW51cw==
X-MHO-User: aaced664-92b3-11e9-a46e-ff59a9ad0924
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 209.85.210.47
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from mail-ot1-f47.google.com (unknown [209.85.210.47]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id aaced664-92b3-11e9-a46e-ff59a9ad0924; Wed, 19 Jun 2019 16:59:58 +0000 (UTC)
Received: by mail-ot1-f47.google.com with SMTP id x21so19985345otq.12 for <masque@ietf.org>; Wed, 19 Jun 2019 09:59:57 -0700 (PDT)
X-Gm-Message-State: APjAAAVb/rOtNcNIEjtJEWpOjj1u7rR1B1rBEOO70tKKRvqq9N43wXIw yTIyxXPqMvM7RE6YweV/OxrronyuRYblrjY6svA=
X-Google-Smtp-Source: APXvYqz9hYeT0Nb4nbbvjKNeCKN1RMyG8AFg4qVmNSpswq07z7T85W6sHxcCBV1mSE0c4FnKaz0ulqs01/UxPjrW0hg=
X-Received: by 2002:a9d:6312:: with SMTP id q18mr3507234otk.45.1560963597010;  Wed, 19 Jun 2019 09:59:57 -0700 (PDT)
MIME-Version: 1.0
From: Patrick McManus <mcmanus@ducksong.com>
Date: Wed, 19 Jun 2019 12:59:46 -0400
X-Gmail-Original-Message-ID: <CAOdDvNqoSv94fiGKdnKusqG5AvKbeYZ3LO-kKydVQkRr8hQ5-w@mail.gmail.com>
Message-ID: <CAOdDvNqoSv94fiGKdnKusqG5AvKbeYZ3LO-kKydVQkRr8hQ5-w@mail.gmail.com>
To: masque@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b50fe5058bb02809"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/ZnLn1dpv21fBx65qnj_xl4yhfuw>
Subject: [Masque] (no subject)
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Jun 2019 17:00:04 -0000

--000000000000b50fe5058bb02809
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

David, thanks for writing up https://github.com/DavidSchinazi/masque-drafts
.. it makes things a bit more concrete even at a very early stage.

I have a couple drive by comments - I hope they help, and I'm sure its
possible they've been discussed in another forum.. the general tech here
has been in a number of different places.

1] istm the configuration primative should be a URI rather than an origin
with a .wk.. there is a reason multiple masque instances couldn't co-exist
on different streams? (different auth, different qos, whatever..)

2] I can't quite figure out what the document _is_. Is it an h3 and h2
extension? Is it a version independent http pattern?

3] You switch up a few things about CONNECT in the same way that rfc 8441
does (which obviously warms my heart!).. but note that 8441 had to be a
negotiated extension to get opt in for breaking some of the base rules of
7540 (a totally allowable thing if negotiated)... specifically you can't
send :protocol or implement CONNECT in some way other than opening a TCP
connection to :authority.

3a - but you obviously don't want to announce your extension in the server
SETTINGS. This seems more like a spec lawyer problem than a real problem.
Nonetheless give the matter some thought, maybe CONNECT isn't the right way
to do it (even though it seems in spirit).

4 - speaking of which, what do you set :authority to on this CONNECT
request given CONNECT defines that..

5 - "When the server receives this CONNECT request, it verifies the
signature and if that fails responds with code =E2=80=9C405 Method Not Allo=
wed=E2=80=9D,
making sure its response is the same as what it would return for any
unexpected CONNECT request." .. I'm not totally sure about my comment here,
but my gut says you don't want to require 405 and instead have text about
probing as it seems to me that servers might be inclined to do other things
for existing errors. For instance I just tried two public facing servers
(not proxies) and gave them CONNECT requests.. one gave me a 405 and one
gave me a 500..

6;plkjhghjkl;][poiuyguiop[]\[poiuytyuiop[][poiuyuiop[poip[][poikp[';[lpkjhb=
nm,./09865432

hth!

-P

--000000000000b50fe5058bb02809
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">David, thanks for writing up <a href=3D"https://github.com=
/DavidSchinazi/masque-drafts">https://github.com/DavidSchinazi/masque-draft=
s</a> .. it makes things a bit more concrete even at a very early stage.<br=
><br>I have a couple drive by comments - I hope they help, and I&#39;m sure=
 its possible they&#39;ve been discussed in another forum.. the general tec=
h here has been in a number of different places.<br><br>1] istm the configu=
ration primative should be a URI rather than an origin with a .wk.. there i=
s a reason multiple masque instances couldn&#39;t co-exist on different str=
eams? (different auth, different qos, whatever..)<br><br>2] I can&#39;t qui=
te figure out what the document _is_. Is it an h3 and h2 extension? Is it a=
 version independent http pattern?<br><br>3] You switch up a few things abo=
ut CONNECT in the same way that rfc 8441 does (which obviously warms my hea=
rt!).. but note that 8441 had to be a negotiated extension to get opt in fo=
r breaking some of the base rules of 7540 (a totally allowable thing if neg=
otiated)... specifically you can&#39;t send :protocol or implement CONNECT =
in some way other than opening a TCP connection to :authority.<br><br>3a - =
but you obviously don&#39;t want to announce your extension in the server S=
ETTINGS. This seems more like a spec lawyer problem than a real problem. No=
netheless give the matter some thought, maybe CONNECT isn&#39;t the right w=
ay to do it (even though it seems in spirit).<br><br>4 - speaking of which,=
 what do you set :authority to on this CONNECT request given CONNECT define=
s that..<br><br>5 - &quot;When the server receives this CONNECT request, it=
 verifies the signature and if that fails responds with code =E2=80=9C405 M=
ethod Not Allowed=E2=80=9D, making sure its response is the same as what it=
 would return for any unexpected CONNECT request.&quot; .. I&#39;m not tota=
lly sure about my comment here, but my gut says you don&#39;t want to requi=
re 405 and instead have text about probing as it seems to me that servers m=
ight be inclined to do other things for existing errors. For instance I jus=
t tried two public facing servers (not proxies) and gave them CONNECT reque=
sts.. one gave me a 405 and one gave me a 500..<br><br>6;plkjhghjkl;][poiuy=
guiop[]\[poiuytyuiop[][poiuyuiop[poip[][poikp[&#39;;[lpkjhbnm,./09865432<br=
><br>hth!<br><br>-P<br></div>

--000000000000b50fe5058bb02809--


From nobody Wed Jun 19 10:02:23 2019
Return-Path: <mcmanus@ducksong.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 EDB361202E2 for <masque@ietfa.amsl.com>; Wed, 19 Jun 2019 10:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=dmRYajMz; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=LmAqnI+B
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 ylyuQ3F5proo for <masque@ietfa.amsl.com>; Wed, 19 Jun 2019 10:02:19 -0700 (PDT)
Received: from outbound1f.eu.mailhop.org (outbound1f.eu.mailhop.org [52.28.59.28]) (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 05FB1120273 for <masque@ietf.org>; Wed, 19 Jun 2019 10:02:07 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1560963725; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=STZp8cZK4Pv/eR7Lbo2qJ+skXe1rkLkT6uBbLgh/jcbrsbhkkd8aNbWAK9FHwM2rcSLuny/DDaxZK Vz39yiA1/Bel1bDisIaNsB5M/669WyVZM96va1oqBPlIN5KlAQp8JcPrQGVPAnx3PnPFuJ7V3Cr7G4 5GSMAdGc4EdFn/CmLVBBdDeuCg6c/X0ejpt6d0B50G3dbfwVAVd/YEd0DU6bDOKITBt5ZwbwWcHxrJ hCzNmmTbk3kUHCKcNoWPQF2K6Bp4F7Foh9Curbeh4sIND/mlluPdFk6dMRyjTS9Q9tV1nUSgu0MQlz 0FOS5uaORhalaAaR8SLkmYrftoOQlSw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:dkim-signature:dkim-signature:from; bh=EnmXcwxohAOsQEBczIHheE8tMUZY+9saiEW7rQ9pIBY=; b=IY3cWOIcU/Audx854q81pL26dJfLFp4o5hCqxtZc9hNVonnuR9UzO3ArUFlXteKThAW57PYGbbVjE 7oFh6pyXwXXCjvAX6K0KwR6iWF8PgobbyWitQ1OyVjM1FdG4q/fG40LH45inFgeRxoq/91RiShFM2u tZMlDRGvYPGhZY7awxvLDHbTQQE9DcJeS7B1900eln14H+B83WdznxLHZI5nKsiHXzukRU3lkZWXAG wjgEUbNk2VXCJBesRCGX4Ll69CeSHgOQY3MBngWjKSE/ya/Y0iIc6wlXjssG0q1pSgFupSaiKNAgWg reG+L41tpcMSD4wJZG4UpLwBEE5dfOA==
ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.167.177; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=EnmXcwxohAOsQEBczIHheE8tMUZY+9saiEW7rQ9pIBY=; b=dmRYajMzARO2T2oJzP//PzEgvNCAD1rSWiJmg7MK0N4R9MdJ+hzuu5qxZW8CfzwYPsXsStuNoXR69 I7d1totLBrHgauActvJReD2ggDi0wkf/cxwvdfND9XpUCVZHNr69k65q3ANKd+wvG+V2up179hUncs 2FQB+EbwITHDPaeQ=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=EnmXcwxohAOsQEBczIHheE8tMUZY+9saiEW7rQ9pIBY=; b=LmAqnI+BiSdFQhI8pB9k3wNoQXuJFc2WHRLoa5jsVkTKDTd1jF4+w4Xglz3EtnsPWANRDdd5e9/vC uB0UMo15PxMUTDujg6GpLpQUI5yypcmIWGxIwX0RlsaA5sQEU+lSoy/L7b07uLO5vGAb/RQKRhAtUB QTg7poJVk7p0cO4M2LCKxcqfoqYvBeN9x2ZGMan5z4Sw9E/kdrphA7gHM8/chXkj37COicHnmXd9M5 wYH+RxaJj6PifLG/N5Klh8cZqh0Nrime4mb9h/R5ZW7p/3OdD5kzb7xb/EiwrPsMVaLi1ak+3osZtE bNsd4xcj3JcgP1Hs8mAW6CEGbNVFnJQ==
X-MHO-RoutePath: bWNtYW51cw==
X-MHO-User: f5c6e9fa-92b3-11e9-b103-9d44562f9f30
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 209.85.167.177
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from mail-oi1-f177.google.com (unknown [209.85.167.177]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id f5c6e9fa-92b3-11e9-b103-9d44562f9f30; Wed, 19 Jun 2019 17:02:03 +0000 (UTC)
Received: by mail-oi1-f177.google.com with SMTP id m206so11121032oib.12 for <masque@ietf.org>; Wed, 19 Jun 2019 10:02:03 -0700 (PDT)
X-Gm-Message-State: APjAAAXsTfVEnZ9drc3CUSpMhi+5ATbdWq8kXg8XtmkBTaPQEsEBHsyW yvbLQfBhDuJWBG7hk1sOMCkT6D9m5tc3XDBcaA8=
X-Google-Smtp-Source: APXvYqxU0YwHLTL1YuMqn+Wqmrs1AMHK7mWpBFbXk273RnTxI20UL47UN3KV+h1Li8UnUNHR338uC+RseCjECyZkbSI=
X-Received: by 2002:aca:c3d7:: with SMTP id t206mr3404350oif.138.1560963722919;  Wed, 19 Jun 2019 10:02:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAOdDvNqoSv94fiGKdnKusqG5AvKbeYZ3LO-kKydVQkRr8hQ5-w@mail.gmail.com>
In-Reply-To: <CAOdDvNqoSv94fiGKdnKusqG5AvKbeYZ3LO-kKydVQkRr8hQ5-w@mail.gmail.com>
From: Patrick McManus <mcmanus@ducksong.com>
Date: Wed, 19 Jun 2019 13:01:51 -0400
X-Gmail-Original-Message-ID: <CAOdDvNrAG2-C0+Y+MHjJtF6zGcUdmuifFp4-Th7dqvpz_Mj_+g@mail.gmail.com>
Message-ID: <CAOdDvNrAG2-C0+Y+MHjJtF6zGcUdmuifFp4-Th7dqvpz_Mj_+g@mail.gmail.com>
To: Patrick McManus <mcmanus@ducksong.com>
Cc: masque@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003644cf058bb03053"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/pMPcs2VES1_hi8r8zOFVXx9n8B8>
Subject: Re: [Masque] (no subject)
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Jun 2019 17:02:22 -0000

--0000000000003644cf058bb03053
Content-Type: text/plain; charset="UTF-8"

On Wed, Jun 19, 2019 at 1:00 PM Patrick McManus <mcmanus@ducksong.com>
wrote:

>
>
>
> 6;plkjhghjkl;][poiuyguiop[]\[poiuytyuiop[][poiuyuiop[poip[][poikp[';[lpkjhbnm,./09865432
>
>
oh man. all I can do is laugh. Pretend its a secret coded message (I was
cleaning my keyboard). sry.

-P

--0000000000003644cf058bb03053
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun 19, 2019 at 1:00 PM Patri=
ck McManus &lt;<a href=3D"mailto:mcmanus@ducksong.com">mcmanus@ducksong.com=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div dir=3D"ltr"><br><br>6;plkjhghjkl;][poiuyguiop[]\[poiuytyuiop[][poiuyui=
op[poip[][poikp[&#39;;[lpkjhbnm,./09865432<br><br></div></blockquote><div><=
br></div><div>oh man. all I can do is laugh. Pretend its a secret coded mes=
sage (I was cleaning my keyboard). sry.</div><div><br></div><div>-P</div><d=
iv>=C2=A0</div></div></div>

--0000000000003644cf058bb03053--

