[tsvwg] Fwd: [tsvwg/draft-ietf-tsvwg-udp-options] Refine the text in Section 11.7 regarding disabling REQ/RES (Issue #64)

["C. M. Heard" <[e-mail]>]

This concerns a post-WGLC issue. Please comment on GitHub
<https://github.com/tsvwg/draft-ietf-tsvwg-udp-options/issues/64> if you
have concerns.

---------- Forwarded message ---------
From: Mike-Heard <[e-mail]>
Date: Sat, Aug 10, 2024 at 6:54 PM
Subject: [tsvwg/draft-ietf-tsvwg-udp-options] Refine the text in Section
11.7 regarding disabling REQ/RES (Issue #64)
To: tsvwg/draft-ietf-tsvwg-udp-options <
[e-mail]>
Cc: Mike-Heard <[e-mail]>, Your activity <
[e-mail]>


In -32 Section 11.7 said:

>> REQ/RES MUST be disabled by default, i.e., arriving REQs are silently
ignored and RES cannot be issued unless REQ/RES is actively enabled, e.g.,
for DPLPMTUD or other known use by an upper layer mechanism.

This default seems more restrictive than necessary or intended, in that it
prevents the user/application from sending REQ and replying to REQ with RES
without additional action other than a request to the API. It has been
replaced in the editor's copy of -33 with the following:

>> If the implementation includes a layer/library that produces and
consumes REQ/RES on behalf of the user/application, then that layer MUST be
disabled by default, in which case and REQ/RES are simply sent upon request
by the user/application and passed to it when received, as with most other
UDP options.

That achieves the goal of not having an automatic response to anything by
the UDP layer unless explicitly authorized by the user/application, and
also allows REQ/RES to be used for other purposes than DPLPMTUD if an
application that has not enabled it.

Please speak up if you find this change objectionable.

—
Reply to this email directly, view it on GitHub
<https://github.com/tsvwg/draft-ietf-tsvwg-udp-options/issues/64>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBA6FAVBZEFNA7ICS6NTTKDZQ2755AVCNFSM6AAAAABMKJZIHKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TSMZXGQYDKNY>
.
You are receiving this because you are subscribed to this thread.Message
ID: <tsvwg/draft-ietf-tsvwg-udp-options/issues/[e-mail]>