Mark Martinec wrote:
I came across a real life example where a public key as returned
by a DNS record contained embedded CR LF, probably due to a
misconfiguration or a broken DNS server implementation.
I think the key phrase here is "probably due to a misconfiguration or a
broken DNS server implementation." While it doesn't seem that there's a
good reason to require SP after CRLF in the key record, I also can't
think of a good reason why the DNS server needs to split it in the first
place. If this behavior had been a characteristic of a common DNS
server implementation, I think we would have seen it before now.
I don't think a change to the spec is required just because there's a
name server that 's broken, misconfigured, or otherwise did something
unexpected.
-Jim
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html