RE: Draft Charter

["Hallam-Baker, Phillip" <pbaker@xxxxxxxxxxxx>]

> At 12:21 PM -0800 03/16/2004, Hallam-Baker, Phillip wrote:
> >Given that this is the charter lets try to avoid all use of terms
> >that are considered contentious by anyone, in particular 'policy',
> >'authorization' etc.
> 
> Sadly, I think this would leave us with no terms at all.  I 
> think we must use some of the technical terms of the trade here.

Tempting though it is to try to reduce the charter to carte blanche
to fix everything that needs fixing on the Internet in the next three 
months I'll accept that.

> >It would be useful for Mail Transfer Agents (MTAs) implementing
> >message acceptance restrictions to be able to confirm that
> >information provided by peer MTAs' is consistent with a description
> >of the configuration of the purported origin.

> In everyday English, "does this domain
> list this host as able to act as an outbound mail server?" 

I prefer the everyday English, "does this domain list this host
as being configured to act as an outgoing mail server?"

But the revision looks close enough here. If it will get through
the IESG it has done its work.


> Here's another shot, striking the "implementing message acceptance"
> and describing things slightly more from the "what gets stored" side
> than the "how it gets used side.
> ++++++++++++new++++text+++++++++++++++
> It would be useful for those maintaining domains and networks
> to be able to specify that individual hosts or nodes are authorized
> to act as MTAs for messages sent from those domains or networks.
> This working group will develop a DNS-based mechanism for
> storing and distributing information associated with that 
> authorization.
> The primary current use case for this facility is to allow recipient
> MTAs to confirm that peer MTAs' actions are authorized by
> specific domains or networks.  This will help combat a certain
> class of domain forgery common in spam.  The solution chosen,
> however, should be generally useful for others which might
> check this authorization data.
> 
> +++++++++end++++++++++++++++++++++++++
>