RE: Interests of Using QUIC for 3GPP 5G Core Control Plane

Mike Bishop <Michael.Bishop@microsoft.com> Tue, 22 August 2017 23:51 UTC

Return-Path: <Michael.Bishop@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48915132B93 for <quic@ietfa.amsl.com>; Tue, 22 Aug 2017 16:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.799
X-Spam-Level:
X-Spam-Status: No, score=-4.799 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, RCVD_IN_MSPIKE_H2=-2.8, 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=microsoft.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 TL9qghlHI4t7 for <quic@ietfa.amsl.com>; Tue, 22 Aug 2017 16:51:56 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0101.outbound.protection.outlook.com [104.47.41.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F39C1132B9E for <quic@ietf.org>; Tue, 22 Aug 2017 16:51:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=VxnFCjw25DTyDXzigiynEr1m0H0U0gueA8WrDsFa9NQ=; b=ON1DFMap3id+2n3bh2AobDwW1k+GPA5XBgM+Qfj23f3RUSrxwJlIkq0AHHTXeOi7jqRrRXgo1SXqxBjDMamf3eeeXXc4fq0oGUInQZzE9KIK7pMpG0RurqGXQ26zOhz3hZfU+C0LA9bwdKYjaiqMOoE8o6RIP8EYx9arafgEjDM=
Received: from MWHPR21MB0141.namprd21.prod.outlook.com (10.173.52.11) by MWHPR21MB0144.namprd21.prod.outlook.com (10.173.52.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.13.0; Tue, 22 Aug 2017 23:51:50 +0000
Received: from MWHPR21MB0141.namprd21.prod.outlook.com ([10.173.52.11]) by MWHPR21MB0141.namprd21.prod.outlook.com ([10.173.52.11]) with mapi id 15.20.0013.000; Tue, 22 Aug 2017 23:51:50 +0000
From: Mike Bishop <Michael.Bishop@microsoft.com>
To: GENG Liang <liang.geng@hotmail.com>
CC: quic <quic@ietf.org>
Subject: RE: Interests of Using QUIC for 3GPP 5G Core Control Plane
Thread-Topic: Interests of Using QUIC for 3GPP 5G Core Control Plane
Thread-Index: AQHS+qXfG9GSk92hqE2tSD/y2hc5gKKRSk2Q
Date: Tue, 22 Aug 2017 23:51:50 +0000
Message-ID: <MWHPR21MB01412B8BF6A36DC140AA7EF187840@MWHPR21MB0141.namprd21.prod.outlook.com>
References: <HK2PR06MB09134BAD122CA79EA6E1CF9987AF0@HK2PR06MB0913.apcprd06.prod.outlook.com>
In-Reply-To: <HK2PR06MB09134BAD122CA79EA6E1CF9987AF0@HK2PR06MB0913.apcprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e8:7::664]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR21MB0144; 6:Si92z3ClSbcsOkOYb551X9eTPrSSzIZ3rRE0653ftqm+f/eS5pGMuG5iCrCS2HrltTNaXZ84H/MWsF+ltSF9UPgwcCsLdLOD8k7PIiiYjTSC+0nv97lR2w0Sf9osNHUtzvKMGVxV2kVaPsm/o7YOCgdoc6CRSeOjhz9lFHx3AXUBe0xOiQaYawfxIrVSG7mW+EO5AfIBL4TeFPDmx4VkOyVOJ2rRMJ/dhNF/vQS3MtXRVlSa2z/hFciI0GyYqsaiirO1tGfX2dCKQZ6TwW7nzNMse/riqM2r5gcfgJXtkR2JNhzBf9XSvKaQeMH1n/3GPGfWItXQemu2tDhznNUF/w==; 5:v//plWE2ZeWFumDXQHV6IxnHe4a62ZguZ6+61M+R49ttG0doFVd5L4C4bjTjqoDxygYN6Mg4TRyPmH7ObFh8pRixJFKX+tPJixxIzVFFkVpi7z5GYyMm7epnw2fogz3DLsH9okqaYPsncEYyP1TIOw==; 24:cBG4KMJXrD+upXSMsu4yM7Xp30oO4y4d1shvgPV7dtnRcbXhCqc5Ok2uDvi9PTNHUqpKdq7N73UoWYOhiL3UI8x/1P5PwdKHKEk5ZVWUmHA=; 7:GBoIPjxfXHSM30MsfHrAO8pGuriVDM5m8g0Y2FrPrgDmfCsM19viTI5FmdTsun0j0VEKB6rOE+wu/qaOCdz6bQU47EsEjirVordpr0zcwGtIHmdG8gw95QNGONRfFX283ObykJNhBpSF4RYzb+Ai7tI1kcP1OKKow0xWFQfHS1f8b/ntV66h6kEw0J02l3yv1Ag/eDO1QBmLIQsm93tD8Sy7q2aNZ11NFFPRzyRCTnY=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 0722b322-67b7-4bef-1651-08d4e9b8c1fc
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(300000502095)(300135100095)(22001)(2017030254152)(48565401081)(300000503095)(300135400095)(2017052603175)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:MWHPR21MB0144;
x-ms-traffictypediagnostic: MWHPR21MB0144:
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-microsoft-antispam-prvs: <MWHPR21MB0144832F1C3EBE2EFDF3D4F687840@MWHPR21MB0144.namprd21.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(61425038)(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(100000703101)(100105400095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123555025)(20161123558100)(20161123560025)(201703131423075)(201703031522075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:MWHPR21MB0144; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:MWHPR21MB0144;
x-forefront-prvs: 04073E895A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(47760400005)(189002)(501624003)(377454003)(199003)(53936002)(86362001)(86612001)(10290500003)(478600001)(99286003)(55016002)(9686003)(6306002)(3660700001)(3280700002)(50986999)(54356999)(76176999)(561944003)(2900100001)(6246003)(110136004)(39060400002)(101416001)(106356001)(2906002)(54896002)(105586002)(33656002)(6436002)(4326008)(6916009)(229853002)(25786009)(2950100002)(77096006)(6506006)(6116002)(74316002)(10090500001)(97736004)(7736002)(102836003)(7696004)(790700001)(72206003)(5660300001)(53546010)(8990500004)(5005710100001)(68736007)(81156014)(14454004)(8676002)(189998001)(8936002)(81166006); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0144; H:MWHPR21MB0141.namprd21.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Bishop@microsoft.com;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR21MB01412B8BF6A36DC140AA7EF187840MWHPR21MB0141namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Aug 2017 23:51:50.2454 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0144
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YxnoknK-7KytCVXPzMrnpB4ki_w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Aug 2017 23:51:59 -0000

Hi, Liang -

I wanted to make sure we got back to you on this, since this didn't make it onto the IETF 99 agenda and I didn't see any subsequent list discussion.

The answer to the question you ask in your slides is definitely "no":  the QUIC transport will not be sent to the IESG by Q4 of 2017.  The QUIC WG was chartered in October 2016 and our chartered milestones say that we hope to finish the transport, TLS, and congestion control docs by March of 2018.  That already seems somewhat improbable to me.  (Chairs and fellow editors, speak up if you disagree.)

This is a really interesting proposal and I'd love to see it move forward.  You say that it would need to be "a stable WG document," which seems slightly contradictory - a WG document is inherently still changing.  If what you need is the fact that those features are present and not going to be removed, we're already there.  If what you need is that the wire format is locked, I don't think that's likely.

But if 5G slips, or just has feature requirements to relay to us so that it could leverage QUIC in future work, I'm interested in seeing what those requirements would be.

From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of GENG Liang
Sent: Tuesday, July 11, 2017 5:29 PM
To: quic <quic@ietf.org>
Subject: Interests of Using QUIC for 3GPP 5G Core Control Plane

Dear all,

We are proposing and promoting the use of QUIC for 3GPP SBA control plane. This results from various advantages of QUIC protocol, which align with the 3GPP requirements:

-Performance advantages including 0-RTT and Multiplexing
-Reliability advantages including ACK mechanism over UDP and etc.

We put together a set of sides to introduce the timeline of 3GPP work and what we think are important to be considered if QUIC could be potentially adopted.

Although I fully understand that the WG session may be packed in IETF99, we would really appreciate if a 5-10 mins could be allocated to us to present this interest to all QUIC colleagues.

Any comments will be extremely welcome.

Best wishes
Liang

________________________________
Liang GENG
China Mobile Research Institute