search

tsvwg / draft-ietf-tsvwg-udp-options

0 stars 0 forks source link

ZS/CMH: Backwards compatibility with UDP #43

Open gorryfair opened 2 months ago

gorryfair commented 2 months ago 
         The backwards compatibility with UDP was considered important in the development of this Spec.

    This point is absent, AFAIK in Section 16 of the draft now.

Adding such a discussion is a reasonable request; IMO the best place would be Section 6 (Design Principles).
Mike-Heard commented 2 months ago

After further review, it seems to me that the following text now in Section 6 adequately addresses this issue:

  1. The UDP option mechanism and UDP options themselves should default to the same behavior experienced by a legacy receiver.

    By default, even when option checksums (OCS, APC), authentication, or encryption fail, every received packet is passed (possibly with an empty data payload) to the user application. Options that do not modify user data should (by default) result in the user data also being passed, even if, e.g., option checksums or authentication fails. It is always the user's obligation to override this default behavior explicitly.

Does this address the request in https://mailarchive.ietf.org/arch/msg/tsvwg/xC4M6R0nAmSLgjC-2yGgffk37YI/?

gorryfair commented 2 months ago

I wonder if section 16 might just benefit from a cross-reference to section 6, relating to the interaction with legacy receivers?

zaheduzzaman commented 2 months ago

Yes, ref to section 6 would be helpful here.