Fwd: New Version Notification for draft-zmlk-quic-te-00.txt
Zhilong Zheng <zhengzl0715@gmail.com> Fri, 05 May 2023 14:22 UTC
Return-Path: <zhengzl0715@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 4F53CC15153E for <quic@ietfa.amsl.com>; Fri, 5 May 2023 07:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.845
X-Spam-Level:
X-Spam-Status: No, score=-1.845 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hNW32x9oKVrn for <quic@ietfa.amsl.com>; Fri, 5 May 2023 07:22:12 -0700 (PDT)
Received: from mail-ej1-x644.google.com (mail-ej1-x644.google.com [IPv6:2a00:1450:4864:20::644]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7008CC14CE4F for <quic@ietf.org>; Fri, 5 May 2023 07:22:12 -0700 (PDT)
Received: by mail-ej1-x644.google.com with SMTP id a640c23a62f3a-965fc25f009so28170266b.3 for <quic@ietf.org>; Fri, 05 May 2023 07:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683296530; x=1685888530; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=+kJXLw3NTM0xN1vnpm01brAzswWcKXg+293L+99T/bQ=; b=CgRpp/nlpCuHivswUhTQLI8Ezqt5rIj0AVeIPgQhrNYjWdnIfn3A6HCKCcPCoak98I Uhvr5RvqiiHK8MAMl5TMS5uhw+2XWK/xOV65NygzO2a+yGDRWZYcqYCqZwYatedV2Ved lW1GOemIhug0sPsqAEqQ6SOtXRCBoKW5kM+TMyssns1FWPGvnAvmbypfoCu531sQwIeK rsDxfgIz2Ns1k82IqligDjW0Q7dmq599BW8vrN8G3Tn1eZou2cRv3C+1SyV/iIFxXh30 EOciCkdAdfkJbcGiNr9Ax3XUBAgUCAr7LUfjDcK+Ef8KAGS8FrYLSITDzC5W7pJBU+aE GXYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683296530; x=1685888530; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=+kJXLw3NTM0xN1vnpm01brAzswWcKXg+293L+99T/bQ=; b=dXSQ7pakBLwLEn0a+uwGbkDg07z2p1+4RayNOpianVt8ObYLvhAC8LqH6p86bNRlpS CpdBHaDqoPAkSAiu5ceJQ7kKj9+tPQK0+eO1vW1kGfzmYMX4ATVh0O0I2Ayeq/MEHr+s useywdC9hp3hRWATCt1YVXUR65tKoM/+6fer3skgu/w9krUyOe/fsPh9gRSQElhBPU8g mvTmi8d6hqzRtARR4K+aJYzgo5DNhaU/sGP/60ASqr0yCF6GYREiwY/KKsNPcgdrCxmL Ue6eEuoVOTXuo9KvTSnA8Hi6xPIrLiJF3wDFCoLivON4YIYZADz0r3BNOcogVYvtAaL5 aX2A==
X-Gm-Message-State: AC+VfDybATAcGh5CxogExHivg22Dekd76NNe+N4y+Hz7ffWt+GZ+bugS NZXVXc8lwYX4MtXgrZcg5vMp5YwgWpjFK7PymCY4zksgjX2Yg9Z96NHplqce
X-Google-Smtp-Source: ACHHUZ5W9991BqisC1pF4UcN2svSp93tq7n9gNx0w9FfZby9c0sbifviuVzGTBXRbaWesImtY4hT5BhSvqb+7YMujKs=
X-Received: by 2002:a17:906:dc92:b0:955:34a5:ae46 with SMTP id cs18-20020a170906dc9200b0095534a5ae46mr1385505ejc.77.1683296529912; Fri, 05 May 2023 07:22:09 -0700 (PDT)
MIME-Version: 1.0
From: Zhilong Zheng <zhengzl0715@gmail.com>
Date: Fri, 05 May 2023 22:21:58 +0800
Message-ID: <CAP=5hd4MpNZq1_kCyp7oJaaukJa=9puLaW2Djs3s6U8S7ft1vA@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-zmlk-quic-te-00.txt
To: quic@ietf.org, yunfei.ma@alibaba-inc.com, mirja.kuehlewind@ericsson.com, miaoji.lym@alibaba-inc.com
Content-Type: multipart/alternative; boundary="000000000000b7979c05faf30383"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-vAxs9AGoyc98PSN4XR881raGiA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 05 May 2023 14:22:16 -0000
Hi all, We just submitted a new draft called "QUIC-enabled Service Differentiation for Traffic Engineering" ( https://datatracker.ietf.org/doc/draft-zmlk-quic-te/). This draft proposes using QUIC CID encoding to support packet prioritization when routing through the wide area network. This approach enables end-host networking stacks and applications to self-select packet routing paths in the WAN, which potentially improves end-to-end performance, cost, and reliability. It has the following major advantages: - Compared with traditional packet prioritization solutions (e.g., DSCP marking), its priority information cannot be modified by the ISP or any network service provider, and does not require any kernel changes (thanks to QUIC's user-space nature). - By combining with Multipath QUIC, it is easy to support packet-level priority (more flexible than flow-level priority). This feature could improve the end-to-end performance. For example, an end-host schedules first-time transmitted packets on a default-priority, low-cost WAN path, and (2) schedules retransmitted packets and handshake packets on a high-priority (low-latency) but more expensive WAN path. - It does not introduce significant overhead on deployment. Because CID is not encrypted, when the edge device (or router) receives such packets, it parses the CID just like parsing the IP header normally, then adds a TE label (e.g., SRv6 SID) that will direct these packets to different routing paths. We performed experiments in our testbed, and a preliminary performance report can be found at: https://github.com/yfmascgy/draft-quic-diffServ/blob/main/docs/performance_report_v0.1.pdf . The result shows that this proposal could improve end-to-end performance by prioritizing some QUIC packets. We would really appreciate any comments and questions! Best regards, Zhilong ------------------Original Mail ------------------ Sender: <internet-drafts@ietf.org> Send Date:Fri May 5 16:33:05 2023 Recipients:Mirja Kühlewind <mirja.kuehlewind@ericsson.com>, Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>, Yanmei Liu < miaoji.lym@alibaba-inc.com>, Ma, Yunfei <yunfei.ma@alibaba-inc.com>, 郑智隆(之有) <zhiyou.zzl@alibaba-inc.com> Subject:New Version Notification for draft-zmlk-quic-te-00.txt A new version of I-D, draft-zmlk-quic-te-00.txt has been successfully submitted by Yunfei Ma and posted to the IETF repository. Name:draft-zmlk-quic-te Revision:00 Title:QUIC-enabled Service Differentiation for Traffic Engineering Document date:2023-05-05 Group:Individual Submission Pages:11 URL: https://www.ietf.org/archive/id/draft-zmlk-quic-te-00.txt Status: https://datatracker.ietf.org/doc/draft-zmlk-quic-te/ Html: https://www.ietf.org/archive/id/draft-zmlk-quic-te-00.html Htmlized: https://datatracker.ietf.org/doc/html/draft-zmlk-quic-te Abstract: This document defines a method for supporting QUIC-enabled service differentiation for traffic engineering through multipath and QUIC connection identifier (CID) encoding. This approach enables end-host networking stacks and applications to select packet routing paths in a wide area network (WAN), potentially improving the end-to-end performance, cost, and reliability. The proposed method can be used in conjunction with segment routing traffic engineering technologies, such as SRv6 TE. The IETF Secretariat
- Fwd: New Version Notification for draft-zmlk-quic… Zhilong Zheng