>> 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.
In -32 Section 11.7 said:
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:
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.