I was going to raise the same issues, including maybe suggesting to
thrown in a Microsoft "how to" generate keys to complete the picture.
But I didn't think you wanted to go there or get into the zone
format (Bind vs Microsoft?), or even suggest to take it out and make
it more general - "Create a subdomain using the format described in
section x.y."
If anything, I like the idea to help Windows people how they can
create keys using OS cert tools, which I am not sure off hand if its
part of the OS or comes with installation of SDKs.
I would probably throw in some text about the domains that need to do
this via their ISP - "add this subdomain and TXT line using your ISP
DNS Manager setup"
Murray S. Kucherawy wrote:
-----Original Message-----
From: dkim issue tracker
[mailto:trac+dkim(_at_)zinfandel(_dot_)tools(_dot_)ietf(_dot_)org]
Sent: Thursday, April 14, 2011 7:04 AM
To: Murray S. Kucherawy
Cc: ietf-dkim(_at_)mipassoc(_dot_)org
Subject: [dkim] #10: Error in Appendix C. Creating a Public Key
#10: Error in Appendix C. Creating a Public Key
http://mipassoc.org/pipermail/ietf-dkim/2011q2/015812.html
For appendix C, I believe the example for the public key DNS record is
missing the complete subdomain. It has brisbane where it should be
brisbane._domainkey
Text change to consider:
This public-key data (without the BEGIN and END tags) is placed in
the DNS as a TXT record subdomain using the selector (i.e. brisbane)
plus "._domainkey" like so:
brisbane._domainkey IN TXT ("v=DKIM1; p=".....")
I don't think this clarifies anything in particular. If the zone file is for
a domain itself, this makes sense, but the text as-is is just fine if the
zone file is for _domainkey.<domain>. I've seen it done (and have done it)
using both designs, so both are equally correct.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
--
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html