evolut的ion of multilingual domain name.pptVIP

Technology Perspective Human factors People would like to name themselves and their objects in their own language ISO 10646+UNICODE is a necessary answer, but not sufficient DNS has some shortcomings as well Deployment Issues Objectives of Internationalizing Protocols Deploying parallel name spaces Deploying parallel communication spaces Objectives of Internationalizing Protocols Many protocols internationalized: SMTP, HTML, etc Domain Name Service foundational and therefore has earthquake effects if changed without thinking clearly Deploying parallel name spaces Simple to do - Deploy many DNS roots with different name spaces Effect: People using one cannot find people in another Commerce diminished Mail exchange impeded, etc Correctness issues Many servers running Bind Often as old as version 4 Incompatible upgrades cause other systems to fail Software reliability is one of the big issues, and this is a key component IETF Comments Application-based solution will be adequate Directory service Partial, local matching rule is needed ASCII (ACE) or non ASCII MDN The MDN solutions can be very extreme, there is no intermediate solution ACE has short-term benefit but has long-term penalty 8bit clean technique introduces system vulnerability ? Policy Perspective Who Own and Control the Internet? Domain Names(gTLD, ccTLD) IP Address Protocol Parameter Root Server BIND ICANN What ICANN does To Coordinate the unique assignment of Three values that are essential to the Proper functioning of the Internet - Domain Names - IP addresses - Protocol port and parameter numbers What ICANN does not do Content Control Network Security Data Privacy Protection Setting multilingual name standards Multilingual Internet interoperability ICANN’s Responses 2000. 3 Cairo 2000. 6 Yokohama ASCII, Internet Language 2000. 11Marina del Rey To host Internationalized Domain Names Workshop 2001. 3 Melbourne To discuss Internationalized DN in the public forum MINC Coordination of RD on m