You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add text about the sorting algorithm incorporating SVCB/HTTPS RR.
One option (that an existing implementation has already been using) is to prefer addresses received in hints or resolved via service names on SVCB/HTTPS records over direct A and AAAA responses, and sort the SVCB/HTTPS derived addresses based on their priority.
The text was updated successfully, but these errors were encountered:
Right. I think the hints in SVCB should be the same as the A/AAAA derived from SVCB, but our implementation does prefer any SVCB-based (hint or query) address over the "plain" A/AAAA answers.
We should add text about the sorting algorithm incorporating SVCB/HTTPS RR.
One option (that an existing implementation has already been using) is to prefer addresses received in hints or resolved via service names on SVCB/HTTPS records over direct A and AAAA responses, and sort the SVCB/HTTPS derived addresses based on their priority.
The text was updated successfully, but these errors were encountered: