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

Joe Touch <touch@strayalpha.com> Wed, 10 July 2019 14:51 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 61F2E12029A for <tsvwg@ietfa.amsl.com>; Wed, 10 Jul 2019 07:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 VRMYDjSkfAJD for <tsvwg@ietfa.amsl.com>; Wed, 10 Jul 2019 07:51:28 -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 3A0A912016D for <tsvwg@ietf.org>; Wed, 10 Jul 2019 07:51:28 -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: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To: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=vsqYamt+Ru0XWqracqmWeR1eKd1/bD4V/2/TexH0K/k=; b=evq1Vn7KhWgDAbKiv40sbhA5/ +YcfZbXJfGp9Bt2fpzJk9qfdKrIeQXde9+AjbwEVbks4XolZkv4mvKHDo3/kY3oWgf0Xcq1+785rN VaviQpLlLPeV/XHwB7KI6YqxYuqjJgqtIsyuc20/XAkXKRZ1ruARqQr1Pojd1lqPTWEKGFGABFQNF CH6pSD6XaDCfhxjdfaHjiFQtSF1YMRnth78fDCPP5CfxOwpRRzGlUyPMYIN1ABl9rlSzpwqOuEEkK AvKLYW1cWtYpnLrJfLaXDUFbEgyGt0PQbcSXPHOXgrq/L81K+52ZWfDhmN1Ae050UCoMPrDxeM6KB zDMMp+vDA==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:54093 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hlDwI-004N0m-2G; Wed, 10 Jul 2019 10:51:27 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <CAPDqMeoMqsB8=tH5TBaq5Tw-sLW3HNc8tpfUU3htV=sWo7pJcA@mail.gmail.com>
Date: Wed, 10 Jul 2019 07:51:21 -0700
Cc: tsvwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7E52D2B-3912-4897-80C6-0150CDE10218@strayalpha.com>
References: <156262970360.865.13042807682366763561.idtracker@ietfa.amsl.com> <CAPDqMeoMqsB8=tH5TBaq5Tw-sLW3HNc8tpfUU3htV=sWo7pJcA@mail.gmail.com>
To: Tom Herbert <tom@quantonium.net>
X-Mailer: Apple Mail (2.3445.9.1)
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/ncrqm73FhPNrEdR12tuOZ-mndRg>
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 14:51:31 -0000

This approach serves absolutely no useful purpose. 

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.

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
> 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.
> 
> The IETF Secretariat
>