For the sake of consideration of all DNS proposals, we need to know if we
can rely on the DNS-SEC protocol being implemented. Otherwise, if it will
never be implemented there is not point in having DNS-based anti-spam
systems. That's why I suggested in a different thread that we should not
have this discussion here, but rather solicit an official comment from the
IESG or IAB on DNS-SEC status in relation to our group.
Yakov
At 05:44 AM 7/4/2003 -0700, william(_at_)elan(_dot_)net wrote:
The problem is not DNSSEC itself its that some people and organisations
are actively blocking its deployment - and that includes both sides of
as far issues at dnsop and namedroppers. And the term "rough concensus"
or "most agree" does not even closely apply there, so that is why some
are unhappy that WG Chairs are making decisions which may not have
everybody's support.
P.S. That above just my opinion as outsider not having participated and just
based on archives and other docs I've read. I'll not go into this again
and I think ASRG should avoid futher discussions about issues with
current or proposed DNS standards - these are for other WGs and we have
enough countroveries to worry about at ASRG.
> Thank you for pointing this out. Based on this information, does that mean
> that any type of anti-spam scheme that relies on the DNS system
> (RMX/rDNS/etc.) would be inherently insecure? Also, What exactly is the
> nature of the problem with the current DNS-SEC standard?
>
> Yakov
>
>
> _______________________________________________
> Asrg mailing list
> Asrg(_at_)ietf(_dot_)org
> https://www1.ietf.org/mailman/listinfo/asrg
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg