I not against the use of wildcards; wildcards per se are wonderful so
far as I am concerned. I've never met a wildcard I didn't like; got
nothing against 'em.
It's just that, as I understand things, if we are to accommodate them,
then we need to put our MARID data in the domain's entries itself, not
in a subdomain. If I'm wrong about that, please let me know.
And it's that that I have a problem with. Using TXT records in the raw
domain level
a. conflicts with any existing TXT information that is there, and
b. will interact very poorly or not at all with the next batch of
information that some future standard might wish to publish about a
domain, building on the precedent and education that we will set about
how to go about doing that.
So I understand there to be a cost in choosing to support wildcards.
I thus am lead to try to understand the actual relative costs and
benefits of doing things one way vs doing things the other. All I'm
trying to do is get real data about this, from actual real world
experience as much as possible.
Bob
PS: You can keep MSFT-bashing if you wish; I'm used to it. But I truly
am trying to be constructive here.
-----Original Message-----
From: owner-ietf-mxcomp(_at_)mail(_dot_)imc(_dot_)org [mailto:owner-ietf-
mxcomp(_at_)mail(_dot_)imc(_dot_)org] On Behalf Of william(at)elan.net
Sent: Friday, May 28, 2004 1:39 AM
To: ietf-mxcomp(_at_)imc(_dot_)org
Subject: RE: Wild card MXes
Am I correct in understanding that right now nobody else on this list
is against use of wildcards except Bob from Microsoft (and I suppose
everyone else from same company) and that everybody else on this list
feels that they are important part of dns->email functionality.
If above is not true, please speak out and tell that you're also
against
wildcards and why.
--
William Leibzon
Elan Networks
william(_at_)elan(_dot_)net