Slashdot Mirror


User: snorked

snorked's activity in the archive.

Stories
0
Comments
2
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 2

  1. Re:RFC on Registrations Now Accepted For Asian Domain Names · · Score: 1
    To all the folks out there who are saying "but UTF-8 doesn't directly translate to ascii!", I wonder why NSI ("for as little as $49!") will "translate" a name for me.

    So, this says that if I have foo.com, I can translate that into any of the four alternate character sets.

    Someone remind me how this isn't sanctioned and assisted domain hijacking again?

    ref: http://www.networksolutions.com/promotions/offers/ multilingual/trans-req.html

  2. Re:RFC on Registrations Now Accepted For Asian Domain Names · · Score: 1
    The current memo (pre RFC) from the Network Working Group can be found at: ftp://ftp.isi.edu/in-notes/rfc2825.txt where it clearly states that the matter of UTF-8 names are solely up to the IETF. (second paragraph of the Abstract section)

    The IETF draft (clearly not an RFC) on the matter, dated 28 June 2000 can be found at: http://www.i-d-n.net/draft/draft-ietf-idn-requirem ents-03.txt

    The remaining questions are a) NSI has no control over the TLD for each respective character set, so why are they offering these? b) why are they polluting the .com, .net, and .org TLDs? c) if you already own "wine.com", does this mean they're willing to give the UTF-8 translation to Joe Blow so he can hijack all your asian client and ruin your otherwise good name?

    Clearly this is not well thought out at all.

    Please peruse this: http://www.emarketer.com/enews/reuters/11_09_2000. rwntz-story-bcnetinterlanguagedc.html?re f=dn and come up with your own conclusing as to the real reason why. (hint: third paragraph)