It doesn't matter -- I don't have the password to log into their registrar
account.
Ok, my point was that a tech contact should have their own log in. It has in
the Frobbit system ;-)
They don't in any of the gTLD registrars I've used. As far as I can tell,
the only actual use of the tech contact is so ISC employees can flame you
if your DNS records are mildly inconsistent.
I just wanted to say that I personally for DNSSEC think we will
not get forward movement faster than software get the features by
default so that one have to turn off things to not use it. For that to
happen, yes, many many things are still to be resolved. For example side
channel for the DS (which we have a suggestion on how to implement, by
publication of the key material in the zone itself).
These issues are certainly soluble, but it's pretty telling that this
obvious problem has been been facing us for ten years and we're just
getting around to it now.
FYI, people at Google have told me that they have no plans to turn on
DNSSEC for their zones any time soon because too much stuff breaks. Since
it's Google, I expect they have precise but non-public numbers for what
too much means. I don't know enough details to guess whether normal
upgrade cycles with newer software will fix the breakage.
Regards,
John Levine, [email protected], Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
_______________________________________________
dane mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dane
