Sure there is. There is an unwritten if condition for it to be
incorrect or correct. Add the condition and then there is "nothing to
fix" further. It could be as simply as adding:
The following assumes you already have a zone file for
_domainkey.
The thing is WINDOWS DNS admins are goin
On 4/15/2011 8:51 AM, Murray S. Kucherawy wrote:
> Also, there's precedent in the RFC series for referring to the BIND zone file
> format (RFC1034), so including an example of that seems appropriate.
Meta-point:
We should not be trying to fix hypothetical weaknesses in the document. We
shou
> -Original Message-
> From: John R. Levine [mailto:jo...@iecc.com]
> Sent: Friday, April 15, 2011 8:26 AM
> To: Murray S. Kucherawy
> Cc: ietf-dkim@mipassoc.org
> Subject: Re: [ietf-dkim] [dkim] #10: Error in Appendix C. Creating a Public
> Key
>
> Agree with
Agree with Murray, there's nothing to fix here.
On Thu, 14 Apr 2011, Murray S. Kucherawy wrote:
>> -Original Message-
>> From: dkim issue tracker [mailto:trac+d...@zinfandel.tools.ietf.org]
>> Sent: Thursday, April 14, 2011 7:04 AM
>> To: Murray S. Kucherawy
>> Cc: ietf-dkim@mipassoc.org
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 - "Crea
> -Original Message-
> From: dkim issue tracker [mailto:trac+d...@zinfandel.tools.ietf.org]
> Sent: Thursday, April 14, 2011 7:04 AM
> To: Murray S. Kucherawy
> Cc: ietf-dkim@mipassoc.org
> Subject: [dkim] #10: Error in Appendix C. Creating a Public Key
>
> #10: Error in Appendix C. Creati
