Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Martin Duke COMMENT (1) (2) #11

Open
vixie opened this issue Jan 7, 2024 · 1 comment
Open

Martin Duke COMMENT (1) (2) #11

vixie opened this issue Jan 7, 2024 · 1 comment

Comments

@vixie
Copy link
Contributor

vixie commented Jan 7, 2024

(1) I support Rob's DISCUSS (and Paul's comment) about SHOULD/MAY. "do it
unless the OS makes it impossible" is a typical use of SHOULD.

(2) Section 3.1, R1 says that responders SHOULD omit the fragment header. Under
what circumstances would it be reasonable to keep it?

@paulwouters
Copy link

(1) was addressed.
For (2), it was rephrased but the issue still stands. I personally cannot think of a good reason? Maybe if you know TCP seems discfunctional? In general, this draft moves us from MAY to SHOULD NOT. I think an update to MUST NOT could be in the form of a bis document after some more experience with these updated settings? (again, personally I would be ok with a MUST here and for the ipv4 DF bit)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants