We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I recommend the following change: [...] However, using literal IPv4 addresses instead of DNS names will fail (unless 464XLAT [RFC8683] is used). --> [...] However, using literal IPv4 addresses instead of DNS names will fail (unless 464XLAT [RFC6877] is used [RFC8683]). Rationale: 464XLAT is defined in RFC6877, and the use case is described in RFC8683.
I recommend the following change:
[...] However, using literal IPv4 addresses instead of DNS names will fail (unless 464XLAT [RFC8683] is used).
--> [...] However, using literal IPv4 addresses instead of DNS names will fail (unless 464XLAT [RFC6877] is used [RFC8683]).
Rationale: 464XLAT is defined in RFC6877, and the use case is described in RFC8683.
from Gabor LENCSE https://mailarchive.ietf.org/arch/msg/v6ops/LXXuGxJrBa61aH_rJ-UsG2xlyIY/
The text was updated successfully, but these errors were encountered:
464XLAT should cite RFC6877. #4
cb1eaa6
No branches or pull requests
from Gabor LENCSE
https://mailarchive.ietf.org/arch/msg/v6ops/LXXuGxJrBa61aH_rJ-UsG2xlyIY/
The text was updated successfully, but these errors were encountered: