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

Tom Herbert <tom@quantonium.net> Wed, 10 July 2019 18:37 UTC

Return-Path: <tom@quantonium.net>
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 2DC801206CB for <tsvwg@ietfa.amsl.com>; Wed, 10 Jul 2019 11:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.601
X-Spam-Level:
X-Spam-Status: No, score=-0.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.20150623.gappssmtp.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 wXvKYxWQytMx for <tsvwg@ietfa.amsl.com>; Wed, 10 Jul 2019 11:37:08 -0700 (PDT)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36FCE1206C3 for <tsvwg@ietf.org>; Wed, 10 Jul 2019 11:37:08 -0700 (PDT)
Received: by mail-wr1-x42b.google.com with SMTP id r1so3515093wrl.7 for <tsvwg@ietf.org>; Wed, 10 Jul 2019 11:37:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UF6nhgdggQbjVJcTkiAmrcXEYYVTc5xdiCbrVsFtFjw=; b=gxElDyC/Ucu/3SJ2/cKOY15tC5Edc54q2XQHZYYDRcYimL2gJ7RVB1NQkaTJgaJKM9 +6wFzwqVYkbLholmJ36V+mJ6fZ2Rn/NQ/RkfLdrzjNeDv2hBwwmvAZadlXoOaUrhBoZp wZUF3vq5S5blJGpO5yDUsMrD/3XvI23ddQwjmyye5DaiJ/RCNRm5aIaH5cpYrYppfrTs 2tFQZ/Z3D1+E5hf4CuVQZi4SbaRGjY27oEayl5izfH8oC9p83lzg6uodL/lPf63XeXLY qd0V7mvqs9u3Fv7O3C8p0UMdQHajJXqWJFh050TSXm3rhGgLjA9zHgCNAwgwZ9KuT0z/ L67w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UF6nhgdggQbjVJcTkiAmrcXEYYVTc5xdiCbrVsFtFjw=; b=i3rGj8/8vHiI3yQqTROvKutYJH7yQu+jaV2REyTtqQ4+h/QB7pg8GnpN5nyHRn/DQu PI/gN1P6YlxFjpygm7dJWPODTVgwqyBazWuy6bf6vFWk8SI5ABcya28xj+drQxPpiraX 6fUdDX02NndISoG9r87qoRbkx13QWnnNWvzwt/1C542k4OqoEzJjTXzKdmoxAKBmvzwh 00fsAeQKiLMXTSZtGPouKwvOnOu13bDow43NG3RyLVUEm7qgPkb/ve0GvmpVOd+/NOwu KoZjnFVIGSGpslhKUVSNQTNZxyYazE47WbEUQZve/K46RljNVgWBnIYeQtDeXoAMaem+ vmNQ==
X-Gm-Message-State: APjAAAVt1AEF4Hih3lWKXIi64PaQcB8S73/8RSbyTwE4p0x7xckMzZvj +gjsFp8akDHjpzzRpLoCmvmGB+Td6aAMnG6zRhJ1tjpJ
X-Google-Smtp-Source: APXvYqwbrsz7dEQExar97oodcwgugWkETkEROPgWL6PXX3aon1wKivnVKJjog8FvoS8ii84g3MbOlzs8IU4YRYSLjRc=
X-Received: by 2002:a5d:548f:: with SMTP id h15mr32367299wrv.254.1562783826505; Wed, 10 Jul 2019 11:37:06 -0700 (PDT)
MIME-Version: 1.0
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> <e73919f08202937bf45418cbf8bcc38c@strayalpha.com>
In-Reply-To: <e73919f08202937bf45418cbf8bcc38c@strayalpha.com>
From: Tom Herbert <tom@quantonium.net>
Date: Wed, 10 Jul 2019 11:36:54 -0700
Message-ID: <CAPDqMeoh3n5fL1k6Fw9D8rCpy4a9eWyUZvgStyzYfFuJbuWudw@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
Cc: tsvwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d703e9058d57f699"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/EcqHfzqO6Bmc-s6CwGYWiF1jNl0>
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 18:37:11 -0000

On Wed, Jul 10, 2019, 9:49 AM Joe Touch <touch@strayalpha.com> wrote:

> 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.
>

The UDP surplus header provides alignment, integrity check, disambiguation
for other uses of surplus space, a means to extend the UDP header,
friendliness with HW and SW implentations, extensibility, uniformity with
the other notable transport protocol that contains options, addresses the
requirements for UDPv6 checksum without having to invoke RFC6939. Overhead
is four bytes (seven with worse case padding) which is insignificant
compared to the benefits.

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
>> <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
>> <http://tools.ietf.org>.
>> >
>> > The IETF Secretariat
>> >
>>
>>