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

Clarify Alias wire format and motivation for binary SvcFieldValue encoding #99

bemasc opened this issue Jan 8, 2020 · 1 comment


Copy link

@bemasc bemasc commented Jan 8, 2020

@miekg has asked for two related clarifications:

  1. How is it that the AliasForm and ServiceForm encodings are compatible?
  2. Why not reuse the TXT/SPF format?

This comment has been minimized.

Copy link

@miekg miekg commented Jan 12, 2020

If this is previously discussed I am happy to read those emails.

Re 1.: the text in the 01 draft is unclear to me that these two encoding (as proposed) are in fact identical.

Re 2.: Easiest for us is to just re-use the TXT encoding, the draft talks about limit length (255 octets) per txt segment, which is true, but the total size can still be more than that. Downside is that parsing of the key, values must be done by the client, instead of the DNS client. But things like \DDD are supported within TXT as well.

See miekg/dns#1064 for our bug to add this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.