Re: possible changes to the SPF I-D during AUTH48

In 
<Pine(_dot_)LNX(_dot_)4(_dot_)44(_dot_)0508111313570(_dot_)12921-100000(_at_)bmsred(_dot_)bmsi(_dot_)com>
 "Stuart D. Gathman" <stuart(_at_)bmsi(_dot_)com> writes:

>     * CNAME chains should be limited to 10 hops.  More than 10 hops
>       should be treated as NX_DOMAIN or PermError to match whether
>       more than 10 PTR, MX, or A RRs should be ignored or cause PermError.
As I've said in the past, I'm not so sure about this.

Don't most resolvers deal with this automatically and leave the
application no control over this?

Are you saying that SPF implementations need to bypass standard
resolvers and do special checking?


-wayne