IETF Logo Mail Archive

Re: QUIC and router Nat support and

Mirja Kuehlewind <mirja.kuehlewind@ericsson.com> Mon, 06 January 2020 11:29 UTC

Return-Path: <mirja.kuehlewind@ericsson.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 599551201EF for <quic@ietfa.amsl.com>; Mon, 6 Jan 2020 03:29:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 A5YRnIA2oOEC for <quic@ietfa.amsl.com>; Mon, 6 Jan 2020 03:29:49 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60064.outbound.protection.outlook.com [40.107.6.64]) (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 A88371201EA for <quic@ietf.org>; Mon, 6 Jan 2020 03:29:48 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jtHvP5IgxxedV+TmnP++/QyXRdElayHQiFvEoJI8bIlk7Iv2+YtxqaDHNzTPOgQi9J8ccPr1hOtHsWLXVWmCVX/SATLuqPVdNKZq+2naWpcHQ0nbtYDdyxYiHBFsTiK5vxiEZ3tiEpz5aHDI2xqiIvE34lT1ZoAEMG6+iPJ/P7QnOaBhPYfLBuFmTkuy4O1CxTeI+JyVjW4TAiVjiqJE8rBU4zwCxutXsLPFpOKoIsy0LkOx9NTFLwTUwtK5USVJwRnftXP+s/+nBBBUt5a6OG3hmEuBH9stc/22/6q54uL82CkTRJJAUoRm9mN7txNytlAGfAqNLjFSaUVe0CqoZw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=F8FJdWjLkWBnL2UCIL4Bg5UY+Ia/lOqHjgZtPKsacOo=; b=dCyfWRYD0B6WW/uHgGXuwwJA/C3beUczOS2BQQEuMX5mHdFjs+I+JO8OZ6+3hoEQFrZKOTxbKzI12hgsBlhmzWnzDAXM4lrCkMT2ZkTJD6BKDFIGEwGiJx8IFlN/VUMufPfrlFltZl3j2lmhzanswzJNQyiPMlHmNIOX7w80o6kP+qsUoTd3es2uaZkLYtznVw5rO3mtahYX6+vdMkTmUntd6lKtLsi75X0VOJWgZ/yjMiBKJq8og/TzQ0buBbLmnhuKYA50R6HXfFOBigQ0GwtAhMbWDS0f5T9LoXNULbeOHtQeZhNnBv6GNO9kRKl7biCMbTAtaCblMwOvDoimOA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=F8FJdWjLkWBnL2UCIL4Bg5UY+Ia/lOqHjgZtPKsacOo=; b=ushkHCrNI28gFnHJe5k5OuWd33jbrqi+XbiXmdjH5PfmawUWITkLKEHXPIwCkImjYV4bt/N5FnFBO4OziAvV1ngluivzcdwT+bCPEjXRbmYv+nYe94YpDn+WvtXCvYAph9ZfzmBxcFScKM6/4/m0S6GMzGsliZZJ3QZ0vErNpPQ=
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com (52.135.149.158) by AM0PR07MB5569.eurprd07.prod.outlook.com (20.178.23.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2623.6; Mon, 6 Jan 2020 11:29:45 +0000
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::4879:46ae:16e:f5b7]) by AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::4879:46ae:16e:f5b7%7]) with mapi id 15.20.2623.008; Mon, 6 Jan 2020 11:29:45 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
CC: IETF QUIC WG <quic@ietf.org>
Subject: Re: QUIC and router Nat support and
Thread-Topic: QUIC and router Nat support and
Thread-Index: AQHVwx1x2D3arDR8G0qFMpGB48xJvqfdgvQA
Date: Mon, 06 Jan 2020 11:29:45 +0000
Message-ID: <DA030E02-7041-4BB3-B7AC-AB489F10D52A@ericsson.com>
References: <CABNhwV0qPxqRz4H_9FDdMDCT-1pGi+BONqhxdWkFy8BgBf3Lyg@mail.gmail.com>
In-Reply-To: <CABNhwV0qPxqRz4H_9FDdMDCT-1pGi+BONqhxdWkFy8BgBf3Lyg@mail.gmail.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mirja.kuehlewind@ericsson.com;
x-originating-ip: [2001:16b8:2435:5000:650d:9c93:310a:8883]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c4de73c8-7cac-4c5c-a98f-08d7929bbb72
x-ms-traffictypediagnostic: AM0PR07MB5569:
x-microsoft-antispam-prvs: <AM0PR07MB55696EEBB10A0EDEEB551939F43C0@AM0PR07MB5569.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0274272F87
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(366004)(346002)(396003)(376002)(136003)(189003)(199004)(5660300002)(45080400002)(66556008)(64756008)(66616009)(76116006)(44832011)(8936002)(316002)(2906002)(186003)(4326008)(66476007)(71200400001)(86362001)(8676002)(66446008)(66946007)(66574012)(6506007)(966005)(6486002)(33656002)(478600001)(36756003)(81156014)(2616005)(81166006)(6512007)(6916009); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB5569; H:AM0PR07MB4691.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: BCL:0;
x-microsoft-antispam-message-info: 4m6P5YvPgJ6zJh2VNJ9K3Vpjk5Efi4lQcSMFMW/5Q4hLe0E+GAktaLXKOGs/Nff1yPKJRhDdLt3oIgppePz1ILv4wEzM2d4Q3P/NV4Zv0tYXk7r3LdQMgWS94jaKKRwrR4IeqL1w3P8xtqU3nZ4HVMgGC/R7KeEpki870QU0P646BV+8eSkgA3ap9MK5NnDlWmZt3DpMxV4mHoSBKEKXq6zV0JCRnghOXytJnrjZWSzayUSHIZ7XnPR2p47PVx9h7IRYSWIIUlbt7vb9ViWli0S90FsGTnwd8KjIgqwFEtaRBQa5Sb8Pyp/uE1DQ/R4aG7XUawZ+Af7mRqIIKqvt8NBYWfp79dMoFSF+Y4+SQD/qo8H5IqHkQ3QVqbLR0ozOyQTHaidUoSuRdSMhO2/0n+R+e3+LmyEKJlLuoJ+/nX4khvUA+4ezuGvfNT0/WaYovkAEsUevTaGrd/b58PSsZevFvi81l6HuCPA9aM8cw0E=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; boundary="Apple-Mail-550E161D-C12A-4F23-934C-0C14E8338494"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c4de73c8-7cac-4c5c-a98f-08d7929bbb72
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jan 2020 11:29:45.6985 (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: jskHzy98e6MzE2XBqjdYF6+e8JXohM6BWOfgL6iCget/EB/pV+60XTWkfW7tRY7DUw9ALjo6SPvVLLgeafWEGVzvaeZXti80ptj6OIO11kM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB5569
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/yIZY94MgelvgXRBBCsyjPZePO4A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 06 Jan 2020 11:29:51 -0000

Hi Gyan,

We have a document on manageability that should cover most of the points you raised below:

https://datatracker.ietf.org/doc/draft-ietf-quic-manageability/

There is also an open issue on GitHub regarding NAT support which explicitly say that CID should not be used for NAT. Short time-outs are actually not a problem if a CID is used from the endpoint that is NATed as address migration is supported by Quic. 

https://github.com/quicwg/ops-drafts/issues/87

If you have further points that should be covered by this document but are currently not, please feel free to raise another issue on GitHub!

Mirja


> Am 04.01.2020 um 17:38 schrieb Gyan Mishra <hayabusagsm@gmail.com>:
> 
> 
> QUIC WG,
> 
> I have a few questions related to QUIC and network support for NAT and also with out of order packets as well as other network related issues in supporting QUIC over UDP.
> 
> Routers today do not support QUIC for Nat and treat the connections as traditional udp and may not have the proper long lived timers as tcp. 
> 
> Most router vendors have global timeouts for Nat but and the setting are global for all tcp and udp.
> 
> Since QUIC used udp and is long lived connections how do you break that out of the generic udp timer..
> 
> It sounds like routers need special treatment like a NAT ALG to support QUIC.
> 
> As far as routing with ECMP paths since QUIC is udp based has that could cause issues with out of sequence packets.
> 
> I believe load balancing may also be an issue and how is that addressed since QUIC used udp and really the LB appliances now need to support the QUIC protocol to monitor state of the connections.
> 
> From a routing and QOS perspective there also could be issue with WRED which is used to prevent saw tooth effect ramp up and down tcp globalization ; since QUIC uses udp wred will not work.
> 
> 
> Is their any development in the routing or internet WGs related to support of QUIC from a routing and switching perspective?
> 
> Kind regards,
> 
> Gyan
> Verizon Communications 
> Cell 301 502-1347
> -- 
> Gyan S. Mishra
> 
> IT Network Engineering & Technology 
> 
> Verizon Communications Inc. (VZ)
> 
> 13101 Columbia Pike FDC1 3rd Floor
> 
> Silver Spring, MD 20904
> 
> United States
> 
> Phone: 301 502-1347
> 
> Email: gyan.s.mishra@verizon.com
> 
> www.linkedin.com/in/networking-technologies-consultant
> 
>

v2.23.0 | Report a Bug | By Email