[getdns-api] EDNS extended rcode {Sender Address Possibly Forged}
Ray Bellis
Ray.Bellis at nominet.org.uk
Tue Nov 26 16:00:33 CET 2013
On 26 Nov 2013, at 14:52, I wrote:
12-bit, surely?
§6.1.3, RFC 6891:
EXTENDED-RCODE
Forms the upper 8 bits of extended 12-bit RCODE (together with the
4 bits defined in [RFC1035<http://tools.ietf.org/html/rfc1035>]. Note that EXTENDED-RCODE value 0
indicates that an unextended RCODE is in use (values 0 through
15).
[I think the 32-bits you're referring to relate to the fact that this field is packed into what's usually the 32-bit TTL field].
But following up to myself, there's no need to support 12 bits here if the other four bits are provided by the "non-EDNS" API.
Ray
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://getdnsapi.net/pipermail/spec/attachments/20131126/f2f22b1e/attachment.html>
-------------- next part --------------
_______________________________________________
getdns-api mailing list
getdns-api at vpnc.org
More information about the spec
mailing list