Re: Future of IANA (and IETF)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Future of IANA (and IETF)



At 6:42 PM -0800 2/3/98, Dave Crocker wrote:

> >Hold on just one minute, please. Sir, what you say above it just
> >patently untrue, and I must point it out.
> >
> >In July of 1996, Image Online Design formulated a proposal and
> >pursued it with IANA. IANA told Image Online Design to put our
> >proposed registry (.WEB) online for operational testing. Image
>
> Sorry.  I don't recall seeing the IODesign proposal on the net or the
> attendant public discussion about it or the development of public support
> for it or...  well, you get the idea I hope.

Read the 3 newdom archives (maybe you should have done this a year and
a half ago). There was even a proposal from Jon Postel. There were even
requirements posted by IANA staff which mandated online & operational
registries (that were actually taking registrations) in order to
qualify under Jon's draft. The rough consensus and working code which
was then established through organizations such as AlterNIC and eDNS
fullfilled the IANA requirements without breaking the IANA root in any
way, shape, or form.

> It is also important to keep in mind the evolution of this topic.  Way back
> in the dark ages, like the at the start of the IAHC work the belief was
> that it was appropriate to have one, public interest registry.  As I've
> said before, my own thinking starting changing only this Spring.  I don't
> recall when my own postings started suggesting the option of multiple
> registries, but I'd guess at least 6 months.

Could you show me one? I've searched all the archives for the last
year, and can't find one single post from you discussing multiple
registries, except in the last um... few hours.

Thanks!



Best Regards,

Simon

--
The future is still out there...




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.