ietf-dkim
[Top] [All Lists]

Re: [ietf-dkim] The URL to my paper describing the DKIM policy options

2006-07-25 09:07:42
Patrick Peterson wrote:

----- Original Message -----
From: "Hallam-Baker, Phillip" <pbaker(_at_)verisign(_dot_)com>
To: "IETF-DKIM" <ietf-dkim(_at_)mipassoc(_dot_)org>
Sent: Wednesday, July 12, 2006 2:05 PM
Subject: [ietf-dkim] The URL to my paper describing the DKIM policy options


I submitted the draft in both pdf and txt. Only the txt is shown, the more
readable pdf is attached.

http://www.ietf.org/internet-drafts/draft-hallambaker-pcon-00.txt

I think this is a great idea and am surprised it didn't generate more
traffic on the list. It's not easy to cram needed new functionality into
a backward-compatible solution.
So I'm trying to understand the basic algorithm:

To discover the policy for DKIM at alice.example.com: 1) policy = lookup (TXT, "_dkim.alice.example.com") IF policy <> NULL THEN RETURN policy 2) pointer = lookup (PTR, "alice.example.com") IF pointer == NULL THEN RETURN NULL 3) policy = lookup (TXT, "_dkim." + pointer) return policy
So I set up mtcc.com's bind config to:

$ORIGIN mtcc.com.

*        IN     PTR    mtcc.com.

Where mtcc.com is the top level and contains the policy record. When I choose a label that doesn't have any other labels (say, frogger.mtcc.com) it doesn't
return anything as TXT so I go to step 2, it points back to mtcc.com and 3
succeeds.

However, when I use a label *with* a record:
   fafner        IN    A    216.102.208.11

the host -t PTR fafner.mtcc.com returns a reply with an answer count of zero.
Which is just the same thing that happens with TXT.

So I guess I must be missing something because wildcarded PTR records seem
to be handled the same as any other wildcard which is to say, not the behavior
you'd hope for.

Phill?

      Mike
_______________________________________________
NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html