Fast Address Validation - about

"Qing An" <anqing.aq@alibaba-inc.com> Wed, 30 October 2019 13:41 UTC

Return-Path: <anqing.aq@alibaba-inc.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 BC3C51200FF for <quic@ietfa.amsl.com>; Wed, 30 Oct 2019 06:41:17 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=alibaba-inc.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 ENRv5X9u9WXw for <quic@ietfa.amsl.com>; Wed, 30 Oct 2019 06:41:15 -0700 (PDT)
Received: from out0-155.mail.aliyun.com (out0-155.mail.aliyun.com [140.205.0.155]) (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 6719E1200DE for <quic@ietf.org>; Wed, 30 Oct 2019 06:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572442871; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=gTDjGPvTR5DgS3hnxBA3HQwanlvBae+nfdiXupUKUNk=; b=n1MDBGFpYW8wb6n8eROunY347XYm6/uoSpSLvEEbuc9wCvNQdkKoqOjHPyZVqn9YQyTsEDpmw7Ga/43/J9S2E0fCE7D5yz1fAMGbVb+mtBaWRZEJboDm32VzFrSQHzGlgUupGdunU9sd+wHL49M97oAvEOHZrwoPpcEI3I9qjzg=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R141e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03292; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=4; SR=0; TI=W4_5657687_v5ForWebDing_0A9326DB_1572442075839_o7001c3975q;
Received: from WS-web (anqing.aq@alibaba-inc.com[W4_5657687_v5ForWebDing_0A9326DB_1572442075839_o7001c3975q]) by e01l07406.eu6 at Wed, 30 Oct 2019 21:41:10 +0800
Date: Wed, 30 Oct 2019 21:41:10 +0800
From: Qing An <anqing.aq@alibaba-inc.com>
To: quic <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, mt <mt@lowentropy.net>
Cc: "刘大鹏(鹏成)" <max.ldp@alibaba-inc.com>
Reply-To: Qing An <anqing.aq@alibaba-inc.com>
Message-ID: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com>
Subject: Fast Address Validation - about
X-Mailer: [Alimail-Mailagent revision 2765257][W4_5657687][v5ForWebDing][Chrome]
MIME-Version: 1.0
x-aliyun-mail-creator: W4_5657687_v5ForWebDing_NTMTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfMCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzc4LjAuMzkwNC43MCBTYWZhcmkvNTM3LjM2XQ
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_12452_53252940_5db992f6_2fa5a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NGcM-S8vWUCp7AUNUPrfZ6VOYHg>
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: Wed, 30 Oct 2019 13:41:18 -0000


Hi Martin, Jana, 

I read through https://www.ietf.org/id/draft-ietf-quic-transport-23.txt and have a few comments and ideas to discuss.

[QUIC-Trans] defines a token based scheme to facilitate address validation of a client. The token MUST be covered by integrity protection against modification or falsification by clients. The server remembers the value it sends to clients and validates the token sent back from a client. In its design, Retry packet is used to deliver the token to a client which address has not yet been validated. It voids the first transmission of the Initial packet sent by the client, and triggers a second Initial packet to be sent with the token. The exchange of token will cause longer connection establishment delay for a client.
To improve the efficiency of address validation during handshake, one idea is that the same token can be exchanged via a different container i.e. the Handshake packet, that eliminates the use of Retry packet for token delivery. 

I am working on the complete draft and will submit it by Friday. Before that, hope this can be discussed in email first.

BR,
Qing An