[getdns-api] EDNS extended rcode {Sender Address Possibly Forged}

Mankin, Allison amankin at verisign.com
Tue Nov 26 08:10:22 MST 2013

The IANA DNS parameters  for this appear to have an error then too:

65001-65534     Reserved for Local/Experimental Use             [RFC6891<http://www.iana.org/go/rfc6891>]
65535   Reserved for future expansion           [RFC6891<http://www.iana.org/go/rfc6891>]

On Nov 26, 2013, at 10:00 AM, Ray Bellis <Ray.Bellis at nominet.org.uk<mailto:Ray.Bellis at nominet.org.uk>> wrote:

On 26 Nov 2013, at 14:52, I wrote:

12-bit, surely?

§6.1.3, RFC 6891:

      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

[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.


getdns-api mailing list
getdns-api at vpnc.org<mailto:getdns-api at vpnc.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vpnc.org/pipermail/getdns-api/attachments/20131126/3b77a7e3/attachment-0001.html>

More information about the getdns-api mailing list