[cabfpub] CAA records on google.com

Adam Langley agl at google.com
Thu Jun 27 20:43:23 UTC 2013

On Thu, Jun 27, 2013 at 4:41 PM, Gervase Markham <gerv at mozilla.org> wrote:
> I'm sure there's a good reason, but I can't find it in the RFC - why are
> the values encoded in this opaque way? Every other type of record I
> 'dig' for seems human-readable. Is this because 'dig' does special
> processing for common record types which it doesn't do for this type
> (and needs to)?

Yes, dig on my machine has not been updated to serialize and parse the
records in the human-friendly, presentation format. Thus it has to use
hex encoding.



More information about the Public mailing list