To reach another person on the Internet you have to type an address into your computer – a name or a number. That address has to be unique so computers know where to find each other.
ICANN coordinates these unique identifiers ( Names and Numbers) across the world.
When typing a name, that name must be first translated into a number by a system before the connection can be established. That system is called the Domain Name System (DNS) and it translates names like https://wikipedia.org into the numbers. These numbers are called Internet Protocol (IP) addresses.
ICANN coordinates the addressing system to ensure all the addresses are unique. Without that coordination we wouldn’t have one global Internet.
Recently vulnerabilities in the DNS were discovered that allow an attacker to hijack this process of looking some one up or looking a site up on the Internet using their name. The purpose of the attack is to take control of the session to, for example, send the user to the hijacker’s own deceptive web site for account and password collection.
A technology called DNS Security Extensions (DNSSEC) secures this part of the Internet’s infrastructure. You can read more about DNSSEC here:
ICANN organises DNSSEC Training and Events worldwide. The Internet Society India Chennai Chapter would co-organize a DNSSEC event at Chennai on July 9, 2017. ICANN would host this event.
This would be a half-day session on DNSSEC with particular attention to the KSK rollover for the technical community in Chennai. The event is open for ISPs, Network Operators, DNS Administrators and other Interested parties, preferably for those whose line of work relates to DNSSEC. Please reach out to the companies / organizations including educational institutions, Law and Order Agencies, Banks, ISPs, IT Companies and independent professionals you may know to be likely to have an interest in this topic.
The session would cover the following topics during 9 30 am – 1 pm, followed by Lunch
DNS and DNS Security Overview
Root Zone DNSSEC KSK Rollover
After Lunch we will have an hour of discussions on the policy aspects of DNS. This session would be for Business and Community Leaders who have an interest in Internet Policy, who would join us on invitation. If wish to recommend names of Business / Community Leaders whom you might have expertise and interest in the security aspects of DNS, please pass on the names by email to isocindiachennai AT gmail DOT com The invitees would join other participants for Lunch at 1 pm which would be followed by about 60 minutes or round table discussions on the policy aspects of DNS.
Do you want your voice to be heard in YOUR region and by the global Internet community?
ICANN is looking for the ‘next generation’ of individuals who are interested in becoming more actively engaged in their own regional communities as well as taking part in the future growth of global Internet policy. Important work is happening every day at ICANN; if you are ready to start your journey, read the information below to see if you are eligible for THIS ICANN Meeting.
Prospective members of the NextGen@ICANN initiative must be:
Living or studying in the region of the respective ICANN meeting and between the ages of 18 and 30. Since applicants must be from the region in which the meeting is being held in, it’s important to understand what ‘regions’ mean. ICANN has established five geographic regions: Africa, Europe, North America, Latin America and Asia. ICANN‘s meetings rotate through these geographic locations using the new ICANNMeeting Strategy. For those over the age of 30, be sure to apply for the ICANN Fellowship program if you meet the Fellowship criteria (Learn More).
Able to spend the time allotted for the ICANN meeting, actively participating and in attendance at all required events, as noted by the organizers of NextGen.
Interested in Internet Governance, the future of the Internet, and other topics covered at the ICANNmeeting.
Willing to present a 5-10 minute project at the meeting. This could be a presentation of research you are working on or have completed, an activity you are doing related to ICANN‘s work, a website you are affiliated with that is related to ICANN‘s work, a thesis project you are working on, etc. All NextGen presentations may be attended by members of the ICANN Multistakeholder community who are in attendance at the ICANN Meeting, as well as NextGen Ambassadors and other NextGen participants.
By applying, applicants are stating they are willing and able to spend the period of the ICANN meeting with the NextGen@ICANN group and will attend all required events. Each individual is provided a grant of support that covers the cost of economy class airfare, hotel and a stipend. NextGen participants are required to secure their own visas for travel at their own expense, as well as obtain any travel or health insurance, if desired, at their own expense. If you wish to apply for NextGen@ICANN, you must provide your personal information, however it is voluntary to choose to apply.
Upcoming Launch Dates:
ICANN57 (Meeting C) in Hyderabad, India to be held 3 – 9 November 2016
Application Round open: 13 June 2016 at 23:59 UTC
Application Round close: 22 July 2016 at 23:59 UTC
It was not uncommon to find the earliest of the Web Application Developers to assume that all domain names would end in .com, all email addresses would follow the format @xyz.com. While developers took into account newer domain names such as .info in due course, most continued to design applications to accept Domain names and email addresses in ASCII just as software developers in the 80s assumed that it would be unnecessary to have any more than two digits to denote the year, which led to the famous Y2K issue towards the year 2000.
Now there are new Top Level Domain Names (such as .family and .game) and Internationalized Domain Names (in various native non-ascii scripts of India and the world, such as .??????? and .???? (I typed India in Tamil and Devanagiri, displays here as ???) as well as Internationalized email Internet Domain Names that would allow users to have addresses in their native scripts.
If a browser or a form in a webpage limits acceptance of domain names or email addresses with a rule such as “a domain name must be in English and end with .com, or .net or .org” or “an email address must be in English or numerals” then it is archaic.
It is a problem far larger in its dimensions than the Y2K problem of year 2000 which kept the IT community of the entire world talking. On this problem of “Universal Acceptance” there appears to be inadequate attention to the problem in global public interest as well as to the commercial opportunities it presents for enterprising Developers and Corporations. This might emerge to be a huge commercial vertical in itself in view of the Design changes to be brought about and in terms of the testing requirements. #Deity #NASSCOM #WIPRO #TiE #TCS #Cognizant (If you are from a different country, please feel free to rewrite this post to suit your country and publish it. This post is not copyrighted.)
For more information, follow the publicly archived, transparent discussions in the IETF forum, at ICANN and at the Internet Society on this issue. You could also write to isocindiachennai (At) gmail (dot) com for additional pointers or any clarification. Or ask your Executives at a higher level to take part in ICANN meetings that are open and held as multi-stakeholder global meetings. And also join the Internet Society India Chennai Chapter. Such participation would lead you to positive involvement in the global Internet and also connect you to business opportunities not only in the y2k20 (there is no such term, the term is coined to describe the issue and the opportunity) but also in DNSSEC, IPv6 transition, Internet of Things (IoT) and new gTLDs.
What does the phrase “Universal Acceptance” mean?
“Universal Acceptance of domain names and email addresses” (or just “Universal Acceptance”, or even “UA”, for short) means that all apps and online services should accept all Internet domain names and email addresses equally.
Universal Acceptance is an important concept these days because the Internet is changing. One way that it is changing is that addresses no longer need to be composed of ASCII characters. (ASCII characters are the 127 Latin-script letters, numerals and punctuation marks that are dominant on the Internet today. All the characters in this document so far have been ASCII characters.)
Most people on earth are not native speakers of languages which use the ASCII characters, so moving from a character set limited to 127 characters to an alternate which can support more than one million characters is essential for those people to fully use and benefit from the Internet. This alternate is called Unicode.
Another way that the Internet is changing is by allowing lots of new domain names. Not only are there simply more of them, but some are longer than any of the older domain names and many of them use the same Unicode system mentioned above.
Note: “Universal Acceptance” is sometimes confused with “Universal Access” or “Universal Accessibility”; those phrases refer to connecting everyone on earth to the Internet, and to building Internet-connected systems for all differently-abled people on earth, respectively. Universal acceptance is limited to domain names and email addresses.
A special group called “Universal Acceptance Steering group (UASG) has been created to work on issues related to Universal Acceptance. UASG doesn’t work on anything else (e.g. Universal Access or Universal Accessibility).
How does an app or an online service support Universal Acceptance?
Software and online services support Universal Acceptance when they offer the following capabilities:
A. Can accept any domain name or email name as an input from a user interface, from a document, or from another app or service
B. Can validate and process any domain name or email name
C. Can store any domain name or email name
D. Can output any domain name or email name to a user interface, to a document, or to another app or service
Unfortunately, older apps and online services don’t always offer those capabilities. Sometimes they lack support for Unicode; sometimes they make wrong assumptions about new domain names, or even assume they don’t exist. Sometimes they support Universal Acceptance in some features but not in all.
How can Universal Acceptance be measured?
Universal Acceptance can be measured in a few ways.
1. Source code reviews and unit testing
2. Manual testing
3. Automated testing
#1 means inspecting the source code and verifying that only the correct programming techniques, software libraries and interfaces (AKA “APIs”) have been used, then verifying that the app or service works by testing against specific test cases for the capabilities A-D listed above. #1 is only practical for app developers and online service providers.
UASG is reaching out directly to the community of app developers and the largest online service providers to encourage them to perform source code reviews and testing to determine the level of Universal Acceptance in their offerings. UASG is also providing a list of criteria which can be used to develop test cases for the capabilities A-D listed above.
#2 can be done by anyone, but it’s labor-intensive. Examples of #2 would include submitting an email address when registering for an online service and verifying that it has been accepted. Since there are lots of potential online services to sign up for, and lots of potential new email address combinations, one must pick and choose which combinations of app, services, email address and/or domain name to test.
UASG is developing a list of top web sites, apps, email addresses and domain names suitable for testing.
#3 requires up-front technical work, but is more scalable to large measuring and monitoring efforts. An example of #3 is the recent gTLD investigation performed by APNIC on behalf of ICANN. <http://www.potaroo.net/reports/Universal-Acceptance/UA-Report.pdf >
UASG is investigating methods of automated testing for Universal Acceptance and will share these as they are developed.