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.

Sign up for GitHub

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

Jump to bottom

Do not allow duplicate ipv4hint and ipv6hint parameters #94

Closed
wants to merge 1 commit into from
Closed

Do not allow duplicate ipv4hint and ipv6hint parameters #94

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions draft-ietf-dnsop-svcb-httpssvc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -750,9 +750,6 @@ The wire format for each parameter is a sequence of IP addresses in network
byte order. Like an A or AAAA RRSet, the list of addresses represents an
unordered collection, and clients SHOULD pick addresses to use in a random order.

These parameters MAY be repeated multiple times within a record.
When receiving such a record, clients SHOULD combine the sets of addresses.

When selecting between IPv4 and IPv6 addresses to use, clients may use an
approach such as {{!HappyEyeballsV2=RFC8305}}.
When only "ipv4hint" parameters are present, IPv6-only clients may synthesize
Expand Down