On Fri, 6 Jan 2017 13:01:10 -0500, Robert Edmonds <[email protected]> wrote:
> It can be rev'd in the same document that introduces a DNS address RR > for that address family :-) > Why not use Address Family <http://www.iana.org/assignments/address-family-numbers/address-family-numbers.xhtml> like EDNS Client Subnet <https://tools.ietf.org/html/rfc7871#section-6>? But for that matter... On Fri, 6 Jan 2017 18:43:30 +0000, "Wessels, Duane" <[email protected] > wrote: > It is of course quite similar to EDNS client subnet, except that there is > no masking and the client cannot opt-out. Might be worth saying in your > document why EDNS client subnet wouldn't work for this purpose. > Why *wouldn't* ECS work for this? If the idea is to expose everything obscured by a proxy (e.g., for backend logging), then the option data should include quite a bit more than an address—at minimum, a protocol number <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml> for differentiating UDP/TCP, the original OPT CLASS (UDP payload size) and flags (including DO), and a flag indicating presence or absence of an OPT record in the original query. You might also want to include the port and id from the original query (for direct response) and/or allow arbitrary data after the address (for communicating installation-specific metadata).
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
