ietf-clear
[Top] [All Lists]

[ietf-clear] Re: Make CSV backwards compatible with legacy SPF records?

2004-11-18 19:11:56
In <419D596D(_dot_)8090002(_at_)yahoo-inc(_dot_)com> Miles Libbey 
<miles(_at_)yahoo-inc(_dot_)com> writes:

Douglas Otis wrote:

Providing an identifier for a machine is a different function than an
identifier for a mailbox-domain.  Even mapping these identifiers from
the machine to the mailbox-domain is a challenge.  AOL adds two
sub-domains to the root domain, as example.  Finding the zone-cut
becomes a factor when even attempting to trace accountable
entities. One can not rely upon a wild-card SPF record, as these are
intended to
provide a denial that the label is valid for a mailbox-domain. : (

so the problem is that in HELO web101.mail.yahoo.com, its
hard/impossible to determine that we should look up yahoo.com?

Use the zone cut as defined in [RFC2181] section 6.  There is already
code written in bind to do this hand handle all the corner cases.
Zone cuts are used for other things, it is well defined and well
tested. 


-wayne