MTA mark draft

I have a question for the members of this subgroup. What are your thoughts
on this draft? http://www.space.net/~maex/draft-irtf-asrg-mtamark-00.txt

Its goal is to provide a mechanism to mark a host as a MTA. This seems to be
a subset of the goal of the RMX-type proposals. Should this work be
considered as part of our reconcilation process here? The reason that I ask
is if you assume that we move forward with a RMX-type proposal then will
such a MTA marking scheme be necessary? Would it be used on top of RMX-type
system, in places where RMX-type system is not usable, or would it simply
not provide any additional benefit?


> -----Original Message-----
> From: Paul Judge [mailto:[email protected]] 
> Sent: Thursday, October 23, 2003 11:02 AM
> To: 'Alan DeKok'; 'Yakov Shafranovich'
> Cc: '[email protected]'
> Subject: RE: [asrg-rmx] Re: [Fwd: [Asrg-Chair] a new draft] 
> 
> 
> The purpose of said draft is a subset of the purpose of the 
> RMX drafts. I feel that if it is going to considered within 
> the ASRG, then it needs to be part of this discussion.
> 
> > -----Original Message-----
> > From: Alan DeKok [mailto:[email protected]]
> > Sent: Wednesday, October 22, 2003 11:27 AM
> > To: Yakov Shafranovich
> > Cc: [email protected]
> > Subject: [asrg-rmx] Re: [Fwd: [Asrg-Chair] a new draft] 
> > 
> > 
> > > Let me know whether you want to use this draft in any 
> way, or if you 
> > > want to leave this outside the RMX subgroup.
> > 
> >   I think it's outside of the scope of ASRG-RMX, as ASRG-RMX
> > is trying to key off of domain names, to discover such 
> > information.  There is overlap with the content of the TXT 
> > records, which describe the information about MTA's for the domain.
> > 
> > ...
> > > >      http://www.space.net/~maex/draft-irtf-asrg-mtamark-00.txt
> > > > Please note that it is not related to RMX propsalsas it doesn't
> > > > implement any domainname or sender checks. It's sole 
> > purpose is to
> > > > mark a MTA in DNS as "is a MTA" or "is not a MTA".
> > 
> > 
> >   It's a small step from this draft to a fully-fledged
> > ASRG-RMX implementation.  The biggest issues are that some 
> > domains may not have control over reverse DNS, which makes it 
> > difficult for them to implement this proposal.  In contrast, 
> > we know that domains control MX records in their own domain, 
> > so adding one more field for ASRG-RMX isn't much of a problem.
> > 
> >   Alan DeKok.
> > _______________________________________________
> > asrg-rmx mailing list
> > [email protected] http://mailman.ntp.org/mailman/listinfo/asrg-rmx
> > 
> _______________________________________________
> asrg-rmx mailing list
> [email protected] http://mailman.ntp.org/mailman/listinfo/asrg-rmx
>