Re: [tsvwg] Alternative version of the UDP FRAG option

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 18 March 2019 15:40 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 13CEB130F25 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2019 08:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 OJ6uw-J_wtna for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2019 08:40:36 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id DB424127A73 for <tsvwg@ietf.org>; Mon, 18 Mar 2019 08:40:35 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id C670E1B000DF; Mon, 18 Mar 2019 15:40:29 +0000 (GMT)
Message-ID: <5C8FBBED.7000805@erg.abdn.ac.uk>
Date: Mon, 18 Mar 2019 15:40:29 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Tom Herbert <tom@herbertland.com>
CC: "C. M. Heard" <heard@pobox.com>, Joe Touch <touch@strayalpha.com>, tsvwg <tsvwg@ietf.org>
References: <CACL_3VE1=0OORUuOKg9GjcdVuhBNTkWhymE7PAs5WYO0ZR0DWQ@mail.gmail.com> <CALx6S37y_AbESyX5PcCSu7NEr-uPVrPXksEeAx5aSNAyqshL6Q@mail.gmail.com> <CACL_3VFJTxM3s-GLOTz9xmkNk1uOQoCmAGApbAf1ZgbH3Opptw@mail.gmail.com> <CALx6S36aWKHFXO=Zx8W-wFqqC5-Oueb3j-b9evm-yKpfguVQuw@mail.gmail.com>
In-Reply-To: <CALx6S36aWKHFXO=Zx8W-wFqqC5-Oueb3j-b9evm-yKpfguVQuw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/MVT9w2m5YcgXgSYWM3HyeldcB74>
Subject: Re: [tsvwg] Alternative version of the UDP FRAG option
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: Mon, 18 Mar 2019 15:40:39 -0000

I think I missed something between these emails....

On 18/03/2019, 15:13, Tom Herbert wrote:
> On Mon, Mar 18, 2019 at 7:43 AM C. M. Heard<heard@pobox.com>  wrote:
>> On Sat, Mar 16, 2019 at 9:06 AM Tom Herbert wrote:
>>> Thinking about this, it occurs to me be that the LITE option isn't
>>> needed. The assumption in the UDP options draft is that a receiver
>>> needs the UDP payload to immediately follow the UDP header, but the
>>> UDP payload can be anywhere in the surplus area as long as it's
>>> aligned to four bytes. A receiver will know how to handle it and
>>> deliver the UDP data to the application (e.g. by maintaining a pointer
>>> to the data).
>>>
>>> So that allows a format like:
>>>
>>> UDP header (Length=8) | Surplus area header | Options | Payload
>>>
>>> The surplus area header contains the header length and a checksum
>>> covering the surplus space (four bytes altogether). The three headers
>>> can thought of as an extended UDP header, so the format becomes:
>>>
>>> Extended UDP header | Payload
>>>
>>> Which looks a whole lot like any other protocol format with a variable
>>> length header such as TCP or IPv4.
>> A major downside to this approach is that is does not let you add
>> "optional to process" options such as MSS, Echo Request, and Echo
>> Response to UDP datagrams that are intended to be processed normally
>> by legacy receivers that do not understand UDP options or the extended
>> UDP header format. You can do that with the option trailer as
>> currently proposed.
Right, so this really re-designs UDP as a sublayer to another transport. 
To me, this looks very like an encaps like DCCP-in-UDP or GRE-in-UDP, 
etc. So this isn't an "option" it's an encapsulation.
> Mike,
>
> The converse is also true. We can't put options in a trailer that
> *must* be processed by the receiver (fragmentation, compression,
> security, etc.).
>
> Tom
Why this? I thought that if you make a request to negotiate to use say 
enhanced integrity checking or some security option, then you can 
require the option to be present at the receiver?
Am I misunderstanding something?

Gorry
>> Mike Heard