<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<br>
<div>
<div>On 26 Nov 2013, at 14:48, Wiley, Glen <<a href="mailto:gwiley@verisign.com">gwiley@verisign.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>I should elaborate: As Allison pointed out, rfc6891 provides a 32-bit value so if we want to support values above 256 we will need to change the data type to something beyond uint8_t.</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
<div>12-bit, surely?</div>
<div><br>
</div>
<div>§6.1.3, RFC 6891:</div>
<div><br>
</div>
<div>
<pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;">EXTENDED-RCODE
Forms the upper 8 bits of extended 12-bit RCODE (together with the
4 bits defined in [<a href="http://tools.ietf.org/html/rfc1035" title=""Domain names - implementation and specification"">RFC1035</a>]. Note that EXTENDED-RCODE value 0
indicates that an unextended RCODE is in use (values 0 through
15).</pre>
<div><br>
</div>
<div>[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].</div>
<div><br>
</div>
<div>Ray</div>
<div><br>
</div>
</div>
<br>
</body>
</html>