> This document can certainly provide an initial registration for
> specific authentication mechanisms already published as RFCs and
> deployed. So it can and probably should provide a registration for
> SMTP AUTH. I guess it could/should also define them for mechanisms
> that are in the rfc-editor's queue, so that covers SPF and SenderID.
>
> We could also consider this spec to be the place where the DKIM method
> should be defined, but that's unclear. I don't know at this point
> *where* the DKIM method will be defined otherwise.
>
> All of this would be in the IANA Considerations section.
Got it, thanks! In this case all the methods you suggested are viable
and I can go with any of them. I think option (1) should be preserved
in any case.
--
Arvel
_______________________________________________
NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html