Re: [ietf-dkim] Modified Introduction text forrfc4871-errata (resend)

2009-06-18 Thread hector
Douglas Otis wrote: 1) Why? There is use in specifying an API here. Every other protocol we've named so far as examples have an API, whether de facto from lots of experience, or implicit from the spec that defines it the protocol, or something actually explicit defining the API.

Re: [ietf-dkim] Modified Introduction text forrfc4871-errata (resend)

2009-06-18 Thread Douglas Otis
On Jun 18, 2009, at 11:18 AM, hector wrote: Douglas Otis wrote: 1) Why? There is use in specifying an API here. Every other protocol we've named so far as examples have an API, whether de facto from lots of experience, or implicit from the spec that defines it the protocol, or

Re: [ietf-dkim] Modified Introduction text forrfc4871-errata (resend)

2009-06-18 Thread hector
Douglas Otis wrote: On Jun 18, 2009, at 11:18 AM, hector wrote: Douglas Otis wrote: 1) Why? There is use in specifying an API here. Every other protocol we've named so far as examples have an API, whether de facto from lots of experience, or implicit from the spec that defines it

Re: [ietf-dkim] Modified Introduction text forrfc4871-errata (resend)

2009-06-18 Thread hector
Douglas Otis wrote: On Jun 18, 2009, at 11:18 AM, hector wrote: This is why I as seeking an answer to why just d= and not anything else. What it for a reputation system? The response from a closed group of large email providers regarding how they would like to have their reputation