Re: [tsvwg] Advance notice on request to poll TSVWG for adoption of draft-kaippallimalil-tsvwg-media-hdr-wireless-03

Tom Herbert <tom@herbertland.com> Sat, 28 October 2023 18:54 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 1441CC151061 for <tsvwg@ietfa.amsl.com>; Sat, 28 Oct 2023 11:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=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 Lm67sb5xbS8O for <tsvwg@ietfa.amsl.com>; Sat, 28 Oct 2023 11:54:15 -0700 (PDT)
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (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 378FEC14CE25 for <tsvwg@ietf.org>; Sat, 28 Oct 2023 11:54:15 -0700 (PDT)
Received: by mail-ot1-x332.google.com with SMTP id 46e09a7af769-6d2de704f53so1017388a34.2 for <tsvwg@ietf.org>; Sat, 28 Oct 2023 11:54:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland.com; s=google; t=1698519254; x=1699124054; darn=ietf.org; 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=q/Tdgbb/K5jdO5Wk6nXRDPevCbJZJjvrb1dgafkIFGw=; b=JuStsuhrWNKVQqdJ5f5pArhjG7saIx2OhUdmGFEninJ9G4ZJ4Fodv3qcV8P2FOYmKc oddZDrPMyNMKEWk38eHF2IIePBDlykxIW+HhZHU8uHXTmYBperUqdd0LRA8Kv036rdZW VkX3rNW0w+KCsbXwn1HOIHDDXMRM9mgbgt4Gzqlq3lcIqEkSE1/1paGuH6Jg8jSC5zD3 FYSzUgvA84bIvew2EQ4uw1Zr9fr3U2RjUDMWTdV9vec3Dv71ssxgjWAe5WvYm0vMMlSf K6cIrBZEC9WjLvEmc9GLwDGII7jYrqyWnT9I0Wys8gbq1QYpQqs5IZf9hG/DoYwv3xkU eJWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698519254; x=1699124054; 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=q/Tdgbb/K5jdO5Wk6nXRDPevCbJZJjvrb1dgafkIFGw=; b=Z3WpD2121heituv5uD0zXp7lCdDmz6QidUMl2qg9BaeoAyfk+jftr0ZOBmB6M6IG+w 4vixcbH7OE+BgsSjH7sBgoKWQng7pdAZuvAMRKpF4XB30+avcF1qAuMOym5k0DlcmyQe kxLRawTpxl2N+BJZ+CpCwnHYSHFszSVz6RqHyIJkIJ3W8EXaioKjOGrKXn/H3HPbZK03 L4ZUVCfEfYNy/qISewwwUdyAJXyxXaXkPajG1gVMOVzK5oLFop3DOKaugojI/bKowQw4 FbCPS9VTcbLrM88sR6G3ETUDhLZDwPUfd1ln8DqZBSW5Iuv/wX6Hs7vQqvS8ASc2tjw4 PT+A==
X-Gm-Message-State: AOJu0YzUPFrnZH88oZvmT0ufPRisckBcDtXO42VNq/VWgAmNyMLkgY1q mpH07Xq/c+ETTT1iA/0M4W+VLIiWs9nMQwjVF8HsgQ==
X-Google-Smtp-Source: AGHT+IG5Iv8tZMeQPr3v2BmmUwvGuObh/kKEYa8JAh+KrIvgaLi4DAsBniBqXdsbz9jZ5KpKSJQB99o6cS9aqCDtE3Q=
X-Received: by 2002:a05:6830:1212:b0:6b7:518a:1672 with SMTP id r18-20020a056830121200b006b7518a1672mr6179270otp.34.1698519254246; Sat, 28 Oct 2023 11:54:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-cr7e5pUR=zxaO35Tjn2d=oM-xBvpdyGop+xaLOG-_U9g@mail.gmail.com> <CALx6S34__pK8tTM08fzTAxx=_dAM4MsEwH1-RL7eXGrCdtnR1Q@mail.gmail.com> <7E9754EA-9A11-49F6-A3F2-3F5E630CEBA6@strayalpha.com> <SN4PR13MB5311CF46AF56025360252C3AE8DCA@SN4PR13MB5311.namprd13.prod.outlook.com> <CALx6S378sTLPzis3=qB07OvojjbCTV8St21-31_oZzsUNZ-5vA@mail.gmail.com> <3D728108-E440-4625-BC4F-F1D134C1BD63@gmx.de> <CALx6S36G3s6UjfLXoxdotGoJaaQgXDhBCTVJi=j8=NhQQDUMWw@mail.gmail.com> <CACL_3VFvjNXGWh3jUg7b21z6f8uWQr8aKe_Lok+gqt-_jy1XKg@mail.gmail.com>
In-Reply-To: <CACL_3VFvjNXGWh3jUg7b21z6f8uWQr8aKe_Lok+gqt-_jy1XKg@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Sat, 28 Oct 2023 11:54:02 -0700
Message-ID: <CALx6S354yf9x5_vm65CU3van6s2XY2fGT3fTnrTGXh9TPO=q4w@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
Cc: Kaippallimalil John <john.kaippallimalil@futurewei.com>, Sri Gundavelli <sgundave@cisco.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Sebastian Moeller <moeller0@gmx.de>, Joe Touch <touch@strayalpha.com>, TSVWG <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/YZenyyhFY04ovNcc62-Zg0WNul4>
Subject: Re: [tsvwg] Advance notice on request to poll TSVWG for adoption of draft-kaippallimalil-tsvwg-media-hdr-wireless-03
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, 28 Oct 2023 18:54:19 -0000

On Sat, Oct 28, 2023 at 10:53 AM C. M. Heard <heard@pobox.com> wrote:
>
> On Sat, Oct 28, 2023 at 9:50 AM Tom Herbert wrote:
> > On Sat, Oct 28, 2023 at 9:18 AM Sebastian Moeller wrote:
> > > Unless the respective layer's data is encrypted, intermediate nodes
> > > obviously can look into packets at every level they desire, and
> > > since they do not need to ask for permission there is really nothing
> > > stopping them... Given that fact, it seems academic to claim there
> > > is a practical difference in usability of UDP options and IPv6 HBH.
> >
> > I think there are material differences. UDP Options only work with
> > UDP, UDP options are in protocol trailers which would be problematic
> > to support in router hardware data path, and there's no distinction
> > between transport layer options and network layer options (i.e. last
> > thing we want is for some router to burn cycles parsing and skip over
> > a bunch of transport layer options to find the network layer options
> > they're interested in).
>
> I'd like to answer these points.
>
> 1. UDP Options only work with UDP.
>
> Correct.
>
> On the other hand, IPv6 HbH options work only with IPv6 and by all
> accounts suffer from an egregious drop rate in today's open Internet.
> There is some empirical evidence that the Internet is much more
> tolerant of UDP options; however, the measurements didn't test what
> happens when UDP Length == 8 (which would be required by the potential
> fixes in 2 and 3 below).
>
> 2. UDP options are in protocol trailers which would be problematic to
> support in a router's [or any middlebox's] hardware data path.
>
> Correct but potentially fixable: draft-ietf-tsvwg-udp-options defines
> per-fragment options, which do not have that disadvantage. Moreover,
> any host to network signalling in a packet that uses UDP fragmentation
> would necessarily have to put such signals in the per-fragment options
> area, not in the trailer (which cannot in principle be located until
> the packet is reassembled). There is some waste of space by using an
> atomic FRAG option, but that could in principle be mitigated by
> introducing a third format that omits the Identification, Frag.
> Offset, and Reass DgOpt Start fields (this would be useful in any
> situation where an endpoint wants to hide one or more UNSAFE options).
>
> 3. There's no distinction between transport layer options and network
> layer options.
>
> Again, correct but potentially fixable: add a proviso to the spec that
> any option intended for the endpoint use  only SHOULD be in the trailer.
>
> My intent here is not to advocate for the changes, but rather to point
> out that they are likely to be NECESSARY to turn UDP options into a
> suitable carrier for host-to-network signalling. I brought these
> points up before, but I didn't see them addressed in
> draft-kaippallimalil-tsvwg-media-hdr-wireless-03.
>
> But the big elephant in the room is that draft-ietf-tsvwg-udp-options
> exclusively defines TRANSPORT options designed to be consumed by
> endpoints, not NETWORK options designed to be inspected by routers or
> other middleboxes. If draft-kaippallimalil-tsvwg-media-hdr-wireless-03
> is to be adopted as a basis for future work, then in my opinion one of
> the adoption questions should be whether the WG would be willing to
> make this change of direction to draft-ietf-tsvwg-udp-options.
>
> The rather lengthy previous discussion pretty much left this last point
> up in the air, but I came away with the conclusion that trying to fix
> IPv6 HbH options is probably the better alternative in the long run.

Hi Mike,

That has been my conclusion as well. But even so, I believe it was
important to give the idea of conveying network layer options in UDP
Options a fair hearing. I believe those discussions have occured on
the list. It would be good if we can establish consensus that UDP
Options aren't the right solution to carry network layer options.

Tom

>
> Mike Heard