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

Daiya Yuyama <daiya@sfc.wide.ad.jp> Tue, 11 July 2023 17:48 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 5D959C14F749 for <tsvwg@ietfa.amsl.com>; Tue, 11 Jul 2023 10:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 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_DNSWL_HI=-5, 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=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 aFSxNcl7VvNi for <tsvwg@ietfa.amsl.com>; Tue, 11 Jul 2023 10:48:00 -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 24B50C14F747 for <tsvwg@ietf.org>; Tue, 11 Jul 2023 10:47:58 -0700 (PDT)
Received: from [IPV6:2409:11:3e00:0:a448:5758:d319:d5ad] (unknown [IPv6:2409:11:3e00:0:a448:5758:d319:d5ad]) (Authenticated sender: daiya) by mail1.sfc.wide.ad.jp (Postfix) with ESMTPSA id 967695089; Wed, 12 Jul 2023 02:47:55 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sfc.wide.ad.jp; s=mail1; t=1689097675; bh=lL3CQeFy+vTjlZVKUcRB+QPRQMHubpyxuxzF76ROj3k=; h=Date:Subject:To:References:From:In-Reply-To:From; b=THgJleNSyrzVePOWGGC+XWoUAYArApdd/ntCzYXexGeIGRwduov+qXuygy5bUO6AY aw/Fs0VMOJA2goPaYLW+pNOY2PPGwLvKXWXr1023b+K+pbwsygWxpymh3xekjRzRhU 9EK6I4Y0a8hI0pB1dUsvCwHO/A1LtFJkpgmqzShDOAUJgDg4DioM1Gnwt1BLEUXk0m a9FUiF6/cH7XE1oOwiVKAtcXFrUkfqQVnADVxBK6mg3rv3ExnrPzZ1fl8ercLZ2rnE SOzORWHxE9F4QPKeRfPJd9TKHDiOiyRiCj6XMkhMU+2VZWs3p2tmTVphU80PBvfE18 EImppz/Q/auQQ==
Message-ID: <591bfafb-ff0a-427d-5e14-0de776437fd6@sfc.wide.ad.jp>
Date: Wed, 12 Jul 2023 02:47:56 +0900
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: tsvwg@ietf.org, Hirochika Asai <panda@wide.ad.jp>
References: <168903260541.49852.5537122429979483346@ietfa.amsl.com>
From: Daiya Yuyama <daiya@sfc.wide.ad.jp>
In-Reply-To: <168903260541.49852.5537122429979483346@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/G1c2sfvoUlKhrWSYhZU3ufuKW94>
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: Tue, 11 Jul 2023 17:48:04 -0000

Dear all

We have submitted a draft that defines the protocol number option in UDP 
options. The protocol number option specifies the protocol immediately 
following the UDP header.

https://datatracker.ietf.org/doc/draft-daiya-tsvwg-udp-options-protocol-number/

Currently, the only information about the packet encapsulated in UDP is 
the port number corresponding to the service. In addition, UDP-based 
protocols such as QUIC are increasingly used as transport for applications.
When using such protocols, it is not possible to provide the UDP layer 
with information about the transport layer protocol that follows the UDP 
header. The protocol number option provides this information.

We believe this option would be beneficial for extending the transport 
protocol with UDP.

If you are interested in it or have any comments, I really appreciate 
your feedback or comments.

Thank you.

Daiya

On 2023/07/11 8:43, internet-drafts@ietf.org wrote:
> 
> A new version of I-D, draft-daiya-tsvwg-udp-options-protocol-number-00.txt
> has been successfully submitted by Daiya Yuyama and posted to the
> IETF repository.
> 
> Name:		draft-daiya-tsvwg-udp-options-protocol-number
> Revision:	00
> Title:		Protocol Number Option in UDP Options
> Document date:	2023-07-10
> Group:		Individual Submission
> Pages:		6
> URL:            https://www.ietf.org/archive/id/draft-daiya-tsvwg-udp-options-protocol-number-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-daiya-tsvwg-udp-options-protocol-number/
> Html:           https://www.ietf.org/archive/id/draft-daiya-tsvwg-udp-options-protocol-number-00.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-daiya-tsvwg-udp-options-protocol-number
> 
> 
> Abstract:
>     This document defines the protocol number option in UDP options.  The
>     protocol number option specifies the protocol immediately following
>     the UDP header.
> 
>                                                                                    
> 
> 
> The IETF Secretariat
> 
>