Re: [tsvwg] New Version Notification for draft-daiya-tsvwg-udp-options-protocol-number-00.txt

Daiya Yuyama <daiya@sfc.wide.ad.jp> Sat, 22 July 2023 19:13 UTC

Return-Path: <daiya@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13E03C15155B for <tsvwg@ietfa.amsl.com>; Sat, 22 Jul 2023 12:13:11 -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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sfc.wide.ad.jp
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 NFEQ1OrTa1IH for <tsvwg@ietfa.amsl.com>; Sat, 22 Jul 2023 12:13:06 -0700 (PDT)
Received: from mail1.sfc.wide.ad.jp (mail1.sfc.wide.ad.jp [203.178.142.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 377A1C151549 for <tsvwg@ietf.org>; Sat, 22 Jul 2023 12:13:04 -0700 (PDT)
Received: from [IPV6:2001:67c:370:128:a:1615:9c4:d730] (unknown [IPv6:2001:67c:370:128:a:1615:9c4:d730]) (Authenticated sender: daiya) by mail1.sfc.wide.ad.jp (Postfix) with ESMTPSA id 68294222134; Sun, 23 Jul 2023 04:13:00 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sfc.wide.ad.jp; s=mail1; t=1690053181; bh=2lbUVuHG9CWBY4A9G89uUJi3ovG4GKK6pcWgs23n1WQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=R8VAS9jaK/WHBTyP0YBOlRRdi/sA0OwQt1zq8Jp3HHB7EkvBhbpfY16Xdq620xzxQ MIQ53b0cRrf3U77e4Yl9qRG2bIkkP5UQwDlDLzdblX69RXIEJlfantXRRcqoUaEa/P kBdD9GrFU8GT6V8Wml1aoT0mOkPFntYC73MDDSVGX7940mGxoMWeGHZBshZD65Rpgl TknUje/eufzLzlXcrhWQakiTULHI6Vv8Kx4Xka5XA6qOJPNZER2z0qiRicdYpdxg58 DlGLUpWyjpoCknBVtgJMpNjoAz+1oGWf6GlSiekyw3Y24ha7utKfu0ZOLXWEJn/T5t jjnlY1Wk5fDIg==
Message-ID: <b18f8bb2-b880-b1e8-0b6a-0e2bfe0fb3ae@sfc.wide.ad.jp>
Date: Sat, 22 Jul 2023 12:12:55 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0
Content-Language: en-US
To: Tom Herbert <tom@herbertland.com>, Yoshifumi Nishida <nsd.ietf@gmail.com>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Daiya Yuyama <daiya=40sfc.wide.ad.jp@dmarc.ietf.org>, tsvwg@ietf.org
References: <168903260541.49852.5537122429979483346@ietfa.amsl.com> <591bfafb-ff0a-427d-5e14-0de776437fd6@sfc.wide.ad.jp> <2b1306db-6b12-dcce-0018-eb1a10f22056@erg.abdn.ac.uk> <CAAK044Q6BDW+_DoHsDMMHPW1jT6SuBy5DLbV_L_MYniRj3J9dA@mail.gmail.com> <86F95E0E-824B-4E19-82EC-4B5ED9E6F962@sfc.wide.ad.jp> <CAAK044QeySM_H3TXPdbrXXEMSegZOaemMyr9tYQcVZb8c37WMQ@mail.gmail.com> <CALx6S35RiOBV80ELvpg6oN09wX8G7emuk2EG3xfHJs3ep1kezw@mail.gmail.com>
From: Daiya Yuyama <daiya@sfc.wide.ad.jp>
In-Reply-To: <CALx6S35RiOBV80ELvpg6oN09wX8G7emuk2EG3xfHJs3ep1kezw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/flpwtVk2vTLRnlykB35hyU36LyU>
Subject: Re: [tsvwg] New Version Notification for draft-daiya-tsvwg-udp-options-protocol-number-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2023 19:13:11 -0000

Dear Nishida-san and Tom-san,

Thank you for your comment.

I understand that it is difficult for middleboxes to distinguish QUIC 
packets. I believe that with this proposal, the fact that the QUIC is 
encrypted will not be an issue.

The current proposal had some confusing parts where it was difficult to 
recognize whether the option was for the middlebox or the end host. This 
proposal is for end hosts, not for middleboxes; UDP options are 
described in Section 14 as intended to be used only by transport 
endpoints, and this proposal is also not intended to be used by 
middleboxes. This will be clearly stated in the next revision.

Thank you.

Daiya

On 2023/07/20 23:35, Tom Herbert wrote:
> Hi Daiya-san,
> 
> Many people don't want middleboxes meddling with*anything*  beyond the
> network layer!
> 
> Besides that I'm not sure this is feasible, it would require
> middleboxes to process trailers which is not amenable to efficient
> implementation for a high performance implementation. Also, this type
> of marking could only be used with UDP and doesn't help with other
> protocols. You might want to look at
> draft-cc-v6ops-wlcg-flow-label-marking, it's a more generic solution
> that would work with any transport protocol.
> 
> Tom
>