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

add SVCB record #1064

Closed
miekg opened this issue Dec 27, 2019 · 1 comment · Fixed by #1067
Closed

add SVCB record #1064

miekg opened this issue Dec 27, 2019 · 1 comment · Fixed by #1067

Comments

@miekg
Copy link
Owner

miekg commented Dec 27, 2019

See https://tools.ietf.org/html/draft-ietf-dnsop-svcb-httpssvc-01. We should add this record as a private RR type for the time being. Wireformat is fairly straight forward, except for the value field, which resembles TXT but not entirely and it can be switched to something else by a previous value in the RR.

I was thinking off:

// SVCB RR. See RFC xxxx (https://tools.ietf.org/html/draft-ietf-dnsop-svcb-httpssvc-01)
type SVCB struct {
	Hdr      RR_Header
	Priority uint16
	Target   string   `dns:"domain-name"`
	Value    []string `dns:"txt"` // this is wrong, if priority == 0 this must be something else entirely
} 

The draft talks about SvcFieldPriority instead of Priority, which I really dislike, hence Priority in the above example. Target is a better name than "SvcDomainName" which is used in the draft - this also mimics the SRV record a bit.

@miekg
Copy link
Owner Author

miekg commented Dec 30, 2019

The wiredata is kinda crazy, so I wonder what's up with that.

question asked: https://mailarchive.ietf.org/arch/msg/dnsop/KxThjOYEKbzaUZXtoZ_Hl0yRVyY

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant