IETF Logo Mail Archive

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

"touch@strayalpha.com" <touch@strayalpha.com> Fri, 27 October 2023 22:44 UTC

Return-Path: <touch@strayalpha.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 537FAC14CE42 for <tsvwg@ietfa.amsl.com>; Fri, 27 Oct 2023 15:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.627
X-Spam-Level:
X-Spam-Status: No, score=-3.627 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_PSBL=2.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, 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=strayalpha.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 AoX6OZJ4UKar for <tsvwg@ietfa.amsl.com>; Fri, 27 Oct 2023 15:44:12 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 0E91CC14CF05 for <tsvwg@ietf.org>; Fri, 27 Oct 2023 15:44:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=mKHbbSDkSE/h6NnzRgHIOjEj97eFtTTAP2Dff2tb/Jw=; b=wpcTZi1T3LingW0nyfgIhuhSEt a52phhfmAt+pseJQJhuU6mZILaFaI3aChv4pvzRGo8guqf79ouIyg8+r/y9L2XPhHAiknM9Y2AEyd 6tLM1q+67PFucGrKb5dItc5f5IPvG5dLtpYyINAsE8v/my3pEvZAPu6uWYfjhV2DXfSq7DpcDP2Mm uw8ppZy9A3LzVZQWmPOzs354Bcb88K8tCwj8uNoCFQKl/aZu2iyYoP7c1Es8X2IhyIAC+8mjLF3wT 3LEbHj4/aX8eQzyj5kGpBzJaj1gKdSYsfjMOpbvhXQsOoDpdJ27s3cZFNthE0o78MVhvDfMhwOyED T0ok9M9Q==;
Received: from 096-040-160-173.res.spectrum.com ([96.40.160.173]:64689 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.1) (envelope-from <touch@strayalpha.com>) id 1qwVYj-003x42-1U; Fri, 27 Oct 2023 18:44:10 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_52F02755-7D4D-45AE-A2C5-F3D27BA3FA08"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.100.2.1.4\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <CALx6S34__pK8tTM08fzTAxx=_dAM4MsEwH1-RL7eXGrCdtnR1Q@mail.gmail.com>
Date: Fri, 27 Oct 2023 15:43:54 -0700
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, tsvwg <tsvwg@ietf.org>
Message-Id: <7E9754EA-9A11-49F6-A3F2-3F5E630CEBA6@strayalpha.com>
References: <CAKKJt-cr7e5pUR=zxaO35Tjn2d=oM-xBvpdyGop+xaLOG-_U9g@mail.gmail.com> <CALx6S34__pK8tTM08fzTAxx=_dAM4MsEwH1-RL7eXGrCdtnR1Q@mail.gmail.com>
To: Tom Herbert <tom=40herbertland.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.100.2.1.4)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/drE_LnQ7MyLwy2-LSoD6zBvLohg>
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: Fri, 27 Oct 2023 22:44:16 -0000

+1 ;-)
—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com

> On Oct 27, 2023, at 2:55 PM, Tom Herbert <tom=40herbertland.com@dmarc.ietf.org> wrote:
> 
> On Fri, Oct 27, 2023 at 2:26 PM Spencer Dawkins at IETF
> <spencerdawkins.ietf@gmail.com> wrote:
>> 
>> Dear TSVWG,
>> 
>> We have requested a slot during the IETF 118 meeting to propose that the co-chairs poll the working group for adoption of https://datatracker.ietf.org/doc/draft-kaippallimalil-tsvwg-media-hdr-wireless/, as a basis for further work.
>> 
>> The chairs have given us a 15-minute slot during the Thursday TSVWG session.
>> 
>> Face-to-face meeting time is precious, so we thought it would be helpful if we invited people to look over the draft, and let us know if you see significant impediments to adopting this draft. That would reduce the time we need in the meeting itself.
> 
> Hi Spencer,
> 
> I believe that the use of UDP Options to carry information that is
> processed by intermediate nodes is a significant impediment to
> adoption.
> 
>> From the draft: "The Wireless Node is responsible for forwarding
> packets to the Client over the Wireless Network.  The Wireless Node
> inspects metadata but does not alter the UDP option."
> 
> There was discussion on the list and I believe that there is general
> consensus that UDP Options are neither designed nor intended to carry
> network layer information like this. They are for carrying End-to-End
> transport layer information.
> 
> IMO the proper alternative for carrying network layer information is
> Hop-by-Hop Options like in FAST
> (https://www.ietf.org/archive/id/draft-herbert-fast-04.txt).
> 
> Tom
> 
> 
> 
> 
> 
>> 
>> As a reminder,
>> 
>> This draft has been presented at IETF 116, 117 and now 118
>> We had considerable discussion at previous IETF meetings and on the TSVWG mailing list
>> That feedback has been uniformly helpful, and we've taken it into consideration in the -03 update.
>> Adoption has been discussed previously at IETF 117
>> 
>> The updated draft (-03) is described in slides that are uploaded at https://datatracker.ietf.org/doc/draft-kaippallimalil-tsvwg-media-hdr-wireless/
>> 
>> A diff from version -02, discussed at IETF 117, is here: https://datatracker.ietf.org/doc/draft-kaippallimalil-tsvwg-media-hdr-wireless/
>> 
>> Please feel free to follow up on this mailing list, or privately with the document authors.
>> 
>> Best,
>> 
>> Spencer
>

v2.23.0 | Report a Bug | By Email