Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-22.txt

["[e-mail]" <[e-mail]>]

Hi, Tom,

Text was there so the result was unambiguous; I agree, it’d be better treating it as malformed and halting option processing (while passing the user data up, if any - same as any other malformed option set).

Do we want to add similar treatment for multiple copies of experimental options with the same ExIDs?

Joe

—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com

> On Jun 13, 2023, at 3:59 PM, Tom Herbert <tom=[e-mail]> wrote:
> 
> Form the draft:
> 
> "If an option other than these occurs more than once, a receiver MUST
> interpret other than these occurs more than once, a receiver MUST
> interpret
> only the first instance of that option and MUST ignore all others."
> 
> I don't think this is a preferred behavior. Since all options after
> the first are ignored, I don't see how any useful work can be done by
> sending the same option to more than once. Furthermore, a sender would
> KNOW that multiple instances of the same option would always be
> ignored, and I don't see any other purpose for doing that than DOS
> attack. Note that ignoring repeated options is not processing cost, in
> this case it's actually fairly involved since we need to have a
> conditional check and probably set a bitmap for every option.
> 
> I think the behavior should either be to process all the copies of the
> option (repeated occurrences of the same option might be deemed useful
> someday), or treat a repeated options as malformed UDP options
> 
> Tom
> 
> 
> On Fri, Jun 9, 2023 at 8:28 PM <[e-mail]> wrote:
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories. This Internet-Draft is a work item of the Transport Area Working
>> Group (TSVWG) WG of the IETF.
>> 
>>   Title           : Transport Options for UDP
>>   Author          : Joe Touch
>>   Filename        : draft-ietf-tsvwg-udp-options-22.txt
>>   Pages           : 44
>>   Date            : 2023-06-09
>> 
>> Abstract:
>>   Transport protocols are extended through the use of transport header
>>   options. This document extends UDP by indicating the location,
>>   syntax, and semantics for UDP transport layer options.
>> 
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-udp-options/
>> 
>> There is also an htmlized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options-22
>> 
>> A diff from the previous version is available at:
>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-tsvwg-udp-options-22
>> 
>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>> 
>> 
>