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

Tom Herbert <tom@herbertland.com> Sun, 23 July 2023 17:10 UTC

Return-Path: <tom@herbertland.com>
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 71902C14CEFE for <tsvwg@ietfa.amsl.com>; Sun, 23 Jul 2023 10:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, 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=herbertland.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 0bsw6L5UzyPq for <tsvwg@ietfa.amsl.com>; Sun, 23 Jul 2023 10:10:04 -0700 (PDT)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 655CCC14F75F for <tsvwg@ietf.org>; Sun, 23 Jul 2023 10:10:04 -0700 (PDT)
Received: by mail-pg1-x52a.google.com with SMTP id 41be03b00d2f7-55b0e7efb1cso1874306a12.1 for <tsvwg@ietf.org>; Sun, 23 Jul 2023 10:10:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland.com; s=google; t=1690132204; x=1690737004; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=m2+B6ME2NfdAdnuMA/XP2NecaX8pqe+lazERVHwE9gE=; b=bP5yXcgVDU2FkDA/mgTZiDkxFubvbdxonySB1hJieOh8HAWTy0IsgKrtqRl3666irS Qw1+MpNyuvzMBCgvGyGHggBmV72FOZ+fdIU6u5ct8ucKtleMmTcjAalddo8xhoL40kVZ Ji7cIoXJL378d2vt0E2HAIHHPaKdALWlcRvXIX2rnITiJ526PNKSJvkeTxShmet1+I0d 8/bj/ZuDNuN3LeFAI6k0i2YF6JwjtxvHc761ULZ1HYLoxJ8PmagkNuudzlgLeS0c3LYu bXBjetU4zcI+TipxiNLKBXr4ajs4EEmSOTMxLMIkBWGQhgmcm9oBUrIWKBU95SAJx/4Y 3LNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690132204; x=1690737004; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=m2+B6ME2NfdAdnuMA/XP2NecaX8pqe+lazERVHwE9gE=; b=AbicNAqXoVb+YOuI9FDr9wYLdV/52v/NQZY9Bi5xgbb9PhPx+gXUD73ZEDYuVdPSkf c0BSIi4H418fRX6CsDChhBrmx7qjjPPIoNGhMnl/SZ8fV1j/6K0qil252qiW6QOaFWlL xCR4AGEKLhbuLL/Fvdqaqtb1AKTXA3Ajzgp+NIYHewpAqI+So42U1dskC4g8kfKqwF6u QD0geCoQtanSg0mnydtmu7nWuB4gP6DxywoHSck/H9dW0sr8nUrhINxOYjeHJZhXAfY/ bqoAWii2sowGkZNC+uUSovJiYM2SqESEKl7CniyQoKUddI4Q19qaqI4tumwpf92jQvAY excA==
X-Gm-Message-State: ABy/qLYdv3MKamqAlgmCJaP/FWEeDYLsxrZDAFEvq6F+3SvHTUcgbZHp KryOpX4rkg7grE/+kOzWMYL5PznrxPcJOxVNYC5+sdlI7YD3/MtWS5k=
X-Google-Smtp-Source: APBJJlHbYrmeUXAEYMa2E7mB7cbTCn7knZJkFX9Ar6Mb5BDXqt4GwycYAYbA8M623/VAXI2xD7becTAls7E1sOQ5Kv8=
X-Received: by 2002:a17:90a:a50c:b0:263:1526:2fb9 with SMTP id a12-20020a17090aa50c00b0026315262fb9mr6496324pjq.36.1690132203599; Sun, 23 Jul 2023 10:10:03 -0700 (PDT)
MIME-Version: 1.0
References: <168903260541.49852.5537122429979483346@ietfa.amsl.com> <591bfafb-ff0a-427d-5e14-0de776437fd6@sfc.wide.ad.jp>
In-Reply-To: <591bfafb-ff0a-427d-5e14-0de776437fd6@sfc.wide.ad.jp>
From: Tom Herbert <tom@herbertland.com>
Date: Sun, 23 Jul 2023 10:09:52 -0700
Message-ID: <CALx6S359UD3DJF=WbviOjxNw=1eK5pm3JPehQaj=z2vzmR8iHg@mail.gmail.com>
To: Daiya Yuyama <daiya=40sfc.wide.ad.jp@dmarc.ietf.org>
Cc: tsvwg@ietf.org, Hirochika Asai <panda@wide.ad.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/4_lOVF5KWvhELhKMJFB-dcrmFpA>
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: Sun, 23 Jul 2023 17:10:08 -0000

Hi Daiya,

One comment on the draft:

 "Also, request IANA to assign one number from the Safe Options range
of the UDP Option Kind Number as Protocol Number (PROTONUM)."

If correct host processing of the UDP payload depends on interpreting
the Protocol Number Option then it will need to be an Unsafe option.
The requirement of Safe options is that they can be ignored and that
the UDP payload is treated the same regardless of whether the options
were processed or not, Unsafe options must be successfully processed
before the UDP payload is processed.

Tom


Tom

On Tue, Jul 11, 2023 at 10:48 AM Daiya Yuyama
<daiya=40sfc.wide.ad.jp@dmarc.ietf.org> wrote:
>
> 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
> >
> >
>