![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
>Is generic "buyer beware" disclaimer really sufficient here? The cost to get a domain from ICANN under the new rules is estimated to be about $100,000. Don't you think we can assume that people who are laying out that kind of money are big boys and girls who will do adequate due diligence? >The problem isn't just "inability to use" -- it's that other parties >exist who may claim the usage right, and provide citations to RFCs to >back up their claim. There are several ICANN documents describing the new process that include a set of recommendations to guide the process. You must have read them, since you are concerned about this proposal. Do you think that recommendations 3, 4, and 20 are adequate to address this problem? If not, why not? Regards, John Levine, johnl at iecc.com, Primary Perpetrator of "The Internet for Dummies", Information Superhighwayman wanna-be, http://www.johnlevine.com, ex-Mayor "More Wiener schnitzel, please", said Tom, revealingly. _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.