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

previously associated with that CID value #46

Closed
boaks opened this issue Jun 24, 2022 · 0 comments · Fixed by #52
Closed

previously associated with that CID value #46

boaks opened this issue Jun 24, 2022 · 0 comments · Fixed by #52

Comments

@boaks
Copy link
Contributor

boaks commented Jun 24, 2022

if a record with CID is received that has the source address of the enclosing UDP datagram different from the one previously associated with that CID value, the receiver SHOULD perform a return routability check as described in {{path-validation}}.

For me the previously is misleading. My understanding was, that RFC9146 recommend to not update the association before passing the address check.

So, for me "currently" may be the better choice.

thomas-fossati added a commit that referenced this issue Jun 24, 2022
Fix #46

Signed-off-by: Thomas Fossati <thomas.fossati@arm.com>
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

Successfully merging a pull request may close this issue.

1 participant