[ietf-dkim] Re: I-D ACTION:draft-ietf-dkim-overview-04.txt

[Hallam-Baker, Phillip]

Absolutely. 

And the question that I raized was rather different. The question is whether we should publish a version of the overview with references to policy taken out.

I do not accept that we have to wait till completion of the policy specification to publish a version of overview. It is sufficient to have last call on the policy requirements. The overview document does not go into the details of how policy works, requirements are sufficient. 

> -----Original Message-----
> From: ietf-dkim-bounces at mipassoc.org 
> [mailto:ietf-dkim-bounces at mipassoc.org] On Behalf Of Dave Crocker
> Sent: Wednesday, March 14, 2007 11:11 AM
> To: Eliot Lear
> Cc: Untitled; Powers, Jot
> Subject: Re: [ietf-dkim] Re: I-D 
> ACTION:draft-ietf-dkim-overview-04.txt
> 
> 
> 
> Eliot Lear wrote:
> > Jot,
> > 
> > The overview isn't keeping DKIM from the world.  In fact 
> you guys can 
> > sign today, if you don't already (haven't checked).
> 
> Eliot, you are, of course, correct.  But that rather misses the point.
> 
> The point is what will facilitate adoption.  (Why is it that 
> the IETF works so hard to ignore adoption issues, as we think 
> merely publishing a document is the end of the task?)
> 
> The Overview document, approximately in its current form 
> (IMO), can be extremely helpful for the rest of the 
> community, to understand DKIM and make deployment and use 
> decisions about it.
> 
> 
>  > The real question
> > for me now is simply this: will those people who are writing the 
> > overview now commit to updating it after SSP is complete?  
> And I for 
> > one want to see SSP complete quickly.
> 
> Whether the current document is "updated", or a new document 
> is written, or an overview section in the SSP specification 
> itself is added strikes me as a decision to make at the time 
> we need the additional writing.
> 
> I'm certainly happy to commit to putting in the effort to 
> make sure there is text of an overview style for SSP.
> 
> d/
> -- 
> 
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> NOTE WELL: This list operates according to 
> http://mipassoc.org/dkim/ietf-list-rules.html
>