> >It can be quite reasonable to make wildcard assertions about RRs that
> >are all within the same administrative domain, but arguably this
> >condition is not met for the COM or NET zones.
>
> Agreed - but again, unless it breaks the protocol or has an adverse impact
> on robustness, (and not j
Hi Keith -
At 12:56 9/16/2003, Keith Moore wrote:
> An interesting point, but
probably one better made to ICANN. Try
> [EMAIL PROTECTED] Since its not a standards or protocol issue
its
> probably not an IETF issue.
I disagree that this is not a protocol issue, as it certainly
affects
operati
> An interesting point, but probably one better made to ICANN. Try
> [EMAIL PROTECTED] Since its not a standards or protocol issue its
> probably not an IETF issue.
I disagree that this is not a protocol issue, as it certainly affects
operation of protocols. There are probably issues for the D
Hi David -
An interesting point, but probably one better made to ICANN. Try
[EMAIL PROTECTED] Since its not a standards or protocol issue its probably
not an IETF issue.
Thanks - Mike
At 11:59 9/16/2003, [EMAIL PROTECTED] wrote:
Verisign's recent inclusion of wildcard RR's for the .net an
Verisign's recent inclusion of wildcard RR's for the .net and .com TLD's
does not violate any standards in the DNS that I can find, although it has
raised some interesting questions with regard to the ethical behavior or
TLD managers.
I think that managers of the TLD's should not be allow to use
