| At Large Membership and Civil Society Participation in ICANN |
|
|
|
|
|
|
|
|
[ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]
|
|
| |
|
This discussion has been archived.
No new comments can be posted.
|
IDN: Verisign Responds to IAB
|
Log in/Create an Account
| Top
| 5 comments
|
Search Discussion
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
In June 2002, recognizing that application providers needed time to deploy IDN applications and Internet users demanded a solution, VGRS launched the i-Nav plug-in for the Internet Explorer browser. The i-Nav plug-in today implements the earlier RACE encoding of IDNA for Microsoft's Internet Explorer browser and Outlook email client applications. The Punycode version of the i-Nav plug-in will be delivered when the IDN RFCs have been published. While the Internet community positively received the i-Nav solution, VGRS received consistent feedback that the i-Nav plug-in solution did not go far enough to provide a ubiquitous solution to every Internet user around the world. Internet users, registrars, and registrants told us that IDNs should not only be supported through an IDNA-based plug-in solution, but also that the IDN's should be resolvable from any Internet browser address bar where the end user could also have the opportunity to download the plug-in. VGRS takes the obligation very seriously to provide a working IDN service to our registrars, their IDN registrants, and the 665 million Internet users around the world.
[unbelievable...]
|
|
|
[ Reply to This | Parent
]
|
| - I believe it!
by isquat
Sunday February 09 2003, @02:22PM
- Re:ugh.
by CapnB
Sunday February 09 2003, @10:35PM
- 1 reply beneath your current threshold.
|
|
 |
"VGRS: The deployed system returns Name Error/NXDOMAIN responses instead of "no data" responses under some circumstances. The modifications to the DNS portion of the system described above address this issue. We also point out that nothing in RFC 2308 prohibits the synthesis of records. The set of synthesized records is finite, but these records are synthesized rather than represented statically for the sake of efficiency. It is important to note that responses from the .com and .net name servers are and will continue to be deterministic and consistent across all authoritative servers."
Can someone translate this functionality (change?) in true "DNS for Dummies" terminology that even someone like me can understand and appreciate?
thanks,
Ray
|
|
|
[ Reply to This | Parent
]
|
|

Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their
respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com
|