QUIC and router Nat support and
Gyan Mishra <hayabusagsm@gmail.com> Sat, 04 January 2020 16:38 UTC
Return-Path: <hayabusagsm@gmail.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 C16A4120046 for <quic@ietfa.amsl.com>; Sat, 4 Jan 2020 08:38:32 -0800 (PST)
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 TqlG0WDCe4Ar for <quic@ietfa.amsl.com>; Sat, 4 Jan 2020 08:38:30 -0800 (PST)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 9DC5F120241 for <quic@ietf.org>; Sat, 4 Jan 2020 08:38:30 -0800 (PST)
Received: by mail-il1-x135.google.com with SMTP id v15so39102133iln.0 for <quic@ietf.org>; Sat, 04 Jan 2020 08:38:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=oY4BD0MVUPvMG/jf8eJx/yjSl9bcta+1TkfSphmOhn4=; b=SD6e1Y3kATtrJqVqLeRFKqJZqelIXbfvxvVguxsPZZ3bw4eId49JcfoyN1R13daeqr TUbyhNz5KVE+aBiVC8wk9VEpmLoehjRLb+11Z6+zqOowruPUDsqovqT+H/Q15oKIwYZp r+RPK0pZ+CDP8F/meRdNBT1OLmqSmvpbXBaah31ZXXMen8fh9eqp0sTmukfTFNnNtnep S3rJvvZCC/VrdPPHGqkcFmTcYj3btMADeuxNzOH8Sl+LQU7kQ31xTy/w6HqlpzXzTKu2 MifeTBII64fVukVDVjPCB78PtJdcPGL7p3TxQ3a4kvmRpLkhFrHK65HMnrml/VJnRn7A UL1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oY4BD0MVUPvMG/jf8eJx/yjSl9bcta+1TkfSphmOhn4=; b=djuv0ZGVIMvDe1dCDejlTz9tRxBhhIR9or/WC4DC1PS9ae+Xyv7T0LJd9PbOsFRmAw MSulYwtCoIR9DW/i6rMgCd/fTnMX9CblAWKYSZYwJqo7FUkWEAcUwPs/Ohx8zFZLK5S7 bIMoefFalso4wB/ujGSZxYcbsZY4u87bEshF3KsMKXDY2t0LjCEnyaWnB7COqCoiEuki OR2jn2ldMZdbrc+325kke9d9z+tAzua50N8C+8bTbbtJCpuJPePF1aadnn69PP7iWbTD WhN78G+CuR/vVUkFCAK+UWF391cVvCVVLooqwVEDMo8ZenyrH0d1bBdokIk1OWSpbtQg x+6g==
X-Gm-Message-State: APjAAAXtGdD+GKD3Pj8g5Fw0a30BMR/7DNu3EdHhbsVxUSlE3O07YGvt 5GJzuoYeaIgLOp8Lt2xuz21tvfAH0kn6qKt1yh69fwQj
X-Google-Smtp-Source: APXvYqyPMgoYtoOwPA7F0hMarw9n9pVhQgMWWGWiWTFWsdDok2QQ9MRN4Ddcmm6wJ9x7W4R7nZT58Uz6ZE4+hUffCUA=
X-Received: by 2002:a92:dc91:: with SMTP id c17mr84024368iln.78.1578155909681; Sat, 04 Jan 2020 08:38:29 -0800 (PST)
MIME-Version: 1.0
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 04 Jan 2020 11:38:03 -0500
Message-ID: <CABNhwV0qPxqRz4H_9FDdMDCT-1pGi+BONqhxdWkFy8BgBf3Lyg@mail.gmail.com>
Subject: QUIC and router Nat support and
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000659548059b530e7e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9QJip--0VLjvrXxcBNSWJGuemUk>
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: Sat, 04 Jan 2020 16:38:33 -0000
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
- Re: QUIC and router Nat support and Gyan Mishra
- QUIC and router Nat support and Gyan Mishra
- Re: QUIC and router Nat support and Mirja Kuehlewind