Re: [tsvwg] New Version Notification for draft-herbert-udp-space-hdr-01.txt

Joe Touch <touch@strayalpha.com> Wed, 10 July 2019 16:49 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 8F695120148 for <tsvwg@ietfa.amsl.com>; Wed, 10 Jul 2019 09:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level:
X-Spam-Status: No, score=-1.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSSOnBDX-HyZ for <tsvwg@ietfa.amsl.com>; Wed, 10 Jul 2019 09:49:11 -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 5D8BE120047 for <tsvwg@ietf.org>; Wed, 10 Jul 2019 09:49:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Message-ID:References:In-Reply-To:Subject:Cc: To:From:Date:Content-Type:MIME-Version: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=9J44bOhGqlbwRYfTkYiPeKnDyVOkgOB0IdE9i9DMVgA=; b=vZw5Sv0+6JLXKb6BPyr3gjLLJ 5K018cZW36xFHKEwalZgg6Is5T09MG6HU3Wgd//CwGNjuUTlv+pzatIAhsHyaUSKyKLDvK5h1hd5s qid+DvotAWZ8xsy8jenZUes/lG4TzBO5/7/Kb/P2J7q1BLpNIDZ+MGxPRuamIHLB/6Dga+mtFeO1v erNWKTNR9aIe9wRg3k3LWV/7lmNYmCdiklHlYa3Dg5WyHli+tayP+I6UWAxJWjdTsyo7Ao45062mt f0MeLIzFlGx4OyOjElBue1G+3YMCykT0nWkLwxM7R2KjxVl3iytcktBBy79Q6Lq0zX/n4JCIOStyK i+v6Nm1hg==;
Received: from [::1] (port=49948 helo=server217.web-hosting.com) by server217.web-hosting.com with esmtpa (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hlFmD-001Uve-AL; Wed, 10 Jul 2019 12:49:10 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_4e4f6460866f2afc340c3e26a7668ffb"
Date: Wed, 10 Jul 2019 09:49:05 -0700
From: Joe Touch <touch@strayalpha.com>
To: Tom Herbert <tom@quantonium.net>
Cc: tsvwg@ietf.org
In-Reply-To: <CAPDqMep9MYqjFvvJSVbqYwo-xJ1pUocYszNukveaZODhf9+75A@mail.gmail.com>
References: <156262970360.865.13042807682366763561.idtracker@ietfa.amsl.com> <CAPDqMeoMqsB8=tH5TBaq5Tw-sLW3HNc8tpfUU3htV=sWo7pJcA@mail.gmail.com> <D7E52D2B-3912-4897-80C6-0150CDE10218@strayalpha.com> <CAPDqMep9MYqjFvvJSVbqYwo-xJ1pUocYszNukveaZODhf9+75A@mail.gmail.com>
Message-ID: <e73919f08202937bf45418cbf8bcc38c@strayalpha.com>
X-Sender: touch@strayalpha.com
User-Agent: Roundcube Webmail/1.3.7
X-OutGoing-Spam-Status: No, score=-1.0
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/f4Xio_D9EDgPbPAbNsbo_62uXR0>
Subject: Re: [tsvwg] New Version Notification for draft-herbert-udp-space-hdr-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Jul 2019 16:49:15 -0000

a) I gave a very specific pair of reasons. To repeat, in detail: 

- UDP options already provides the same vehicle (type flags) for others
to use the space 

- UDP options are not limited in length and (now) already consume the
entirety of that space when used 

b) it is a waste of time to even provide further reasons. 

It would be much more useful IMO for others to comment on the other
pending suggestions. 

(so others can feel free to skip the rest of this post) 

But since you asked: 

- the length field unnecessarily limits use of the space to chunks of
1020 bytes 

- the front padding isn't helpful (the checksum can be adjusted with a
byte-swap if not half-word aligned) 

- the length field assumes (incorrectly) that all use of the space is in
chunks that end at word boundaries 

- the excessive space for experiments is not needed, given RFC6994
techniques 

- it wastes space and provides no additional capability for the current
UDP option approach 

But most importantly: 

- there are no currently known uses of the surplus space 

- but even if there were, they would need to be adapted to this scheme
(and could instead be adapted to the existing UDP options) 

Again, this serves no useful purpose and is actually wasteful. 

Joe 

On 2019-07-10 09:18, Tom Herbert wrote:

> On Wed, Jul 10, 2019, 7:51 AM Joe Touch <touch@strayalpha.com> wrote: 
> 
>> This approach serves absolutely no useful purpose.
> 
> Obviously, I disagree with that assessment. See the motivations section in the draft. 
> 
>> The UDP options already provide a vehicle for others to use the surplus space and it already consumes the entirety of that space.
>> 
>> I hope those in the WG interested in improving UDP options will comment on the other posted issues instead.
> 
> Well, I've already posted many comments on that UDP options proposal, I would hope my proposal gets equally constructive feedback from the WG (more than just an arbitrary statement that it has no useful purpose). 
> 
> Tom 
> 
>> Joe
>> 
>>> On Jul 8, 2019, at 4:52 PM, Tom Herbert <tom@quantonium.net> wrote:
>>> 
>>> Hello,
>>> 
>>> I've posted a new draft version for the UDP surplus space header. The
>>> version provides detail on the use cases of the UDP Surplus Header as
>>> a protocol trailer and protocol header. Also, I added a motivations
>>> section and added appendices for implementation considerations.
>>> 
>>> Thanks,
>>> Tom
>>> 
>>> ---------- Forwarded message ---------
>>> From: <internet-drafts@ietf.org>
>>> Date: Mon, Jul 8, 2019 at 4:48 PM
>>> Subject: New Version Notification for draft-herbert-udp-space-hdr-01.txt
>>> To: Tom Herbert <tom@quantonium.net>
>>> 
>>> 
>>> 
>>> A new version of I-D, draft-herbert-udp-space-hdr-01.txt
>>> has been successfully submitted by Tom Herbert and posted to the
>>> IETF repository.
>>> 
>>> Name:           draft-herbert-udp-space-hdr
>>> Revision:       01
>>> Title:          UDP Surplus Header
>>> Document date:  2019-07-08
>>> Group:          Individual Submission
>>> Pages:          16
>>> URL:
>>> https://www.ietf.org/internet-drafts/draft-herbert-udp-space-hdr-01.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-herbert-udp-space-hdr/
>>> Htmlized:       https://tools.ietf.org/html/draft-herbert-udp-space-hdr-01
>>> Htmlized:
>>> https://datatracker..ietf.org/doc/html/draft-herbert-udp-space-hdr [1]
>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-herbert-udp-space-hdr-01
>>> 
>>> Abstract:
>>> This specification defines the UDP Surplus Header that is an
>>> extensible and generic format applied to the UDP surplus space. The
>>> UDP surplus space comprises the bytes between the end of the UDP
>>> datagram, as indicated by the UDP Length field, and the end of the IP
>>> packet, as indicated by IP packet or payload length. The UDP Surplus
>>> Header can be either a protocol trailer of the UDP datagram, or a
>>> protocol header which effectively serves as an extended UDP header.
>>> 
>>> 
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at tools.ietf..org [2].
>>> 
>>> The IETF Secretariat
>>> 
 

Links:
------
[1] https://datatracker.ietf.org/doc/html/draft-herbert-udp-space-hdr
[2] http://tools.ietf.org