<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Japan Registry Services Co., Ltd.</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/" />
    <link rel="self" type="application/atom+xml" href="/en/rss.xml" />
    <id>tag:jprs.co.jp,2008-12-17://6</id>
    <updated>2009-10-05T08:19:39Z</updated>
    <subtitle>Contributing to building of the network society and creation of a more fulfilling and enriching world</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Commercial 4.23-ja</generator>
<entry>
    <title>JPRS Position on Conclusion of Joint Project Agreement between ICANN and U.S. Department of Commerce</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2009/091005.html" />
    <published>2009-10-05T07:35:48Z</published>
    <updated>2009-10-05T08:19:39Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(5 October 2009)</div>
<p><br />
On September 30th, 2009, ICANN and the U.S. Department of Commerce concluded the JPA (Joint Project Agreement).  On the same day, the Affirmation of Commitments was signed between them.</p>
<p>The Affirmation is of long standing and is not limited to the three years for which previous agreements operated.<br />
It declares ICANN is independent and is not controlled by any one entity.  It commits ICANN to reviews performed BY THE COMMUNITY -- a further recognition that the multi-stakeholder model is robust enough to review itself.</p>
<blockquote>The Affirmation of Commitments - What it Means<br>
<a href="http://www.icann.org/en/announcements/announcement-30sep09-en.htm">http://www.icann.org/en/announcements/announcement-30sep09-en.htm</a></blockquote>
<p>JPRS has, since its establishment, supported Internet resource management led by private sector.  Being a private organization itself, JPRS has taken responsibility as the registry of .JP top-level domain and built up international framework through signing the Sponsorship Agreement with ICANN, also the private organization.</p>
<p>In addition, JPRS has actively taken part in ICANN's relevant councils, committees, working groups and other policy development discussions.</p>
<p>In the past JPA reviews, JPRS has supported ICANN by publicly stating that ICANN has become capable of taking its responsibility.</p>
<blockquote>JPRS Submitted Comments to U.S. Department of Commerce<br>
(9 June 2009)<br>
<a href="http://jprs.co.jp/en/topics/2009/090609.html">http://jprs.co.jp/en/topics/2009/090609.html</a>
<br>
<p>
JPRS Submitted Comments Responding to Notice of Inquiry by the U.S. Department of Commerce Regarding Joint Project Agreement<br>
(19 February 2008)<br>
<a href="http://jprs.co.jp/en/topics/2008/080219.html">http://jprs.co.jp/en/topics/2008/080219.html</a>
<br>
<p>
JPRS Submitted Comments Responding to Notice of Inquiry by the U.S. Department of Commerce<br>
(7 July 2006)<br>
<a href="http://jprs.co.jp/en/topics/2006/060707.html">http://jprs.co.jp/en/topics/2006/060707.html</a>
</blockquote>
<p>JPRS welcomes the end of JPA and signing of the Affirmation as the milestone of private-sector-led Internet resource management.  And JPRS will contribute more than ever to sound evolution of the Internet.</p>]]>
    </content>
</entry>
<entry>
    <title>JPRS Plans to Implement DNSSEC in JP Domain Name Services</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2009/090709.html" />
    <published>2009-07-09T01:12:19Z</published>
    <updated>2009-07-09T01:33:22Z</updated>
    <summary>9 July 2009...</summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        <![CDATA[<div style="text-align: right;">9 July 2009</div>]]>
        <![CDATA[<p><strong>Introduction</strong></p>
<p>We, JPRS, are developing a plan to implement DNSSEC [*1], the technology that adds improved security to the Domain Name System, in JP domain name services by the end of 2010.  The purpose of this document is to present a background of the implementation and future actions.</p>
<blockquote></blockquote><small>*1 DNSSEC: DNS Security Extensions</small>
<p><br />
<strong>Background</strong></p>
<p>DNS is a vital mechanism which provides the core function of the Internet, and its operational stability is required in line with the growing importance of the Internet as part of the social infrastructure.  In addition, under the circumstance where security threats caused by frauds of DNS responses have turned into reality, a strong demand for worry-free DNS which excludes these threats has grown in late years.</p>
<p>Aiming at improving DNS security, IETF [*2] advanced the consideration to establish the security extension of DNS called DNSSEC.  DNSSEC adds signatures to DNS responses with the public key encryption scheme.  This enables receivers of the DNS response to validate whether or not the response is correct and complete.</p>
<p>JPRS regards DNSSEC as the most effective and feasible current solution against the security threats caused by frauds of DNS responses.  Based on this view, JPRS has researched and developed the method of implementing DNSSEC into large-scale zones, while discussing operational technology and roadmap toward diffusion through collaboration with DNS-related parties from home and abroad.  From now on, we are going to conduct tests and reviews of specifications in order to implement DNSSEC into JP domain name services.</p>
<blockquote></blockquote><small>*2 IETF: Internet Engineering Task Force</small>
<p><br />
<strong>Actions to be taken by related parties</strong></p>
<p>DNSSEC is a mechanism to validate integrity and authenticity of DNS response, which is realized by supporting DNSSEC on both DNS providers' and users' side.  Consequently, various DNS-related parties need to move ahead on their own plan to handle DNSSEC.</p>
<p>JPRS is going to deploy DNSSEC in JP DNS and JP domain name services provided by JPRS itself, while conducting promotional and educational activities and providing information to different DNS-related parties categorized as follows.</p>
<p><u>Operators of authoritative DNS server</u></p>
<p>As DNS forms a hierarchical structure stretched from the root, it is demanded that DNSSEC be introduced into all the layers of DNS from the highest layer of root DNS to DNS at the TLD level and DNS server for each domain name. </p>
<p>- Operators of root DNS</p>
<blockquote>To ensure smooth operation of DNSSEC, it is essential to introduce DNSSEC into root DNS which is the highest layer in the DNS structure.  ICANN [*3]/IANA [*4] is moving ahead the discussion toward adopting DNSSEC.   Taking the discussion into consideration, JPRS continues to support early adoption of DNSSEC at the root level, by cooperating with the other TLD registries.</blockquote>
<blockquote><small>*3 ICANN: Internet Corporation for Assigned Names and Numbers</small><br><small>*4 IANA: Internet Assigned Numbers Authority</small></blockquote>
<p>- Operators of the other TLD registries </p>
<blockquote>Use of DNS does not close within the national borders or respective TLDs.  With a view to contributing to spread of DNSSEC over the whole Internet and enhancing DNS security, JPRS is going to play an active part in information exchange among the TLD registries.</blockquote>
<p>- DNS server operators for each JP domain name </p>
<blockquote>DNSSEC requires specific procedures including signing DNS information and registering signing key information in DNS server for each domain name.　 Targeting the operators of each JP domain names, JPRS will provide information on DNSSEC operation through seminars and media.</blockquote>
<p><u>Operators of cache DNS server</u></p>
<p>Validation of DNS responses in DNSSEC is done by cache DNS servers administered in ISPs, universities and companies.  JPRS will build deeper cooperation with domestic ISPs and will develop activities such as providing information on DNSSEC operation through seminars and media.</p>
<p><u>JP domain name registrars</u></p>
<p>To enable JP domain name registrants to use DNSSEC service provided by JPRS, it is required that the services of JP domain name registrars support DNSSEC. JPRS is going to cooperate with registrars to promote the arrangement of DNSSEC service environment.</p>
<p><u>Internet users</u></p>
<p>Internet users are not required to take any special action, as the necessary validation on the users' side is done in the cache DNS servers of their providers such as ISPs.  However, it is important for the users to be aware of DNSSEC and whether he/she is in the environment supporting DNSSEC or not.  To help ensure this circumstance, JPRS is going to provide explanatory information on DNSSEC for the users.</p>
<p>As mentioned above, we will continue to promote actions by various related parties toward dissemination of DNSSEC, with an eye to implement DNSSEC into JP domain name services by the end of 2010.</p>]]>
    </content>
</entry>
<entry>
    <title>JPRS Submitted Comments to U.S. Department of Commerce </title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2009/090609.html" />
    <published>2009-06-09T08:13:00Z</published>
    <updated>2009-06-08T09:54:21Z</updated>
    <summary> ...</summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
         
        <![CDATA[<h3>
- In Response to Notice of Inquiry on Transition of Technical Coordination and 
Management of Internet's Domain Name and Addressing System -
</h3><div align="right">(9 June 2009)<br /></div><br />
<div class="lead" id="lead"><div>
<div class="right">
<p>
</p>
<br />
</div>
</div></div>
<div class="SOLO" id="p1"><div>
On June 8th, 2009, JPRS submitted its comments in response to the Notice of Inquiry posted
on April 24th, 2009 by the National Telecommunications and Information 
Administration (NTIA), U.S. Department of Commerce.<br />
<br />
In the Notice of Inquiry, NTIA solicits public comments with regards to performance of Internet Corporation for Assigned Names and Numbers (ICANN), prior to expiration of the Joint Project Agreement.<br /><br />As one of the earliest adopters of ccTLD Sponsorship Agreement with ICANN, JPRS has supported technical coordination of the Internet resources led by private sector and has contributed to ICANN process.&nbsp; JPRS's comments submitted to NTIA today are as follows.<br />
<br />
<br />
<br />
<br />
<strong>JPRS Comments</strong>
<table border="1" cellspacing="5" width="70%">
<tbody><tr><td>
8th June 2009<br />
<br />
Ms. Fiona M. Alexander<br />
Office of International Affairs<br />
National Telecommunications and<br />
Information Administration<br />
U.S. Department of Commerce<br />
1401 Constitution Avenue, N.W.<br />
Room 4701, Washington, DC 20230<br />
United States of America<br />
<br />
Re: Docket No. 090420688-9689-01<br />
Assessment of the Transition of the Technical Coordination and Management of the Internet's Domain Name and Addressing System<br />
<br />
Dear Ms. Alexander,<br />
<br />
We, JPRS (Japan Registry Services Co., Ltd.), are one of the ccTLD sponsoring 
organizations that formalized relationship with ICANN at its earliest stage, 
through conclusion of the ccTLD sponsorship agreement.  JPRS has supported 
coordination of Internet resource management led by private sector centering 
on ICANN, thus has actively participated in and contributed to the ICANN 
process.<br />
<br />
We submit the following comments responding to your Notice of Inquiry:<br />
<br />
<ul>
<li>
ICANN has promoted technical coordination of the Internet's resources on the 
basis of multi-stakeholder participation and contributed to realizing security 
and stability of the DNS.  Overall, ICANN has achieved a satisfactory level of 
performance.
</li>
<br />
<li>
For instance, as for the formalization of the relationship between ICANN and 
ccTLD, a new framework based on mutual trust, called Accountability Framework, 
was introduced by ICANN in 2006. Since the introduction, the formalization has 
been steadily advanced.  As of June 1, 2009, as many as 66 ccTLD's, including 
50 who executed the Accountability Framework, have established formal 
relationship with ICANN.
</li>
<br />
<li>
With regard to IDN ccTLD, discussion has been accelerated to a very high level 
in the past two years, accompanied by concrete actions toward implementation.  
We can now expect to see the selection of IDN ccTLD starts within 6 months or 
so at the earliest.  This acceleration is the evidence of the fact that ICANN 
has proactively taken in what community demands, and complex issues have been 
addressed by ICANN's efforts through participation of multiple stakeholders, 
including organizations and individuals worldwide.
</li>
<br />
<li>
In terms of root server administration, ICANN has already carried forward the 
formalization of relationship with 4 out of 12 operators except for ICANN itself,
 and the progress in stabilization of entire root server system has been 
observed.
</li>
<br />
<li>
JPRS continues to support private-sector coordination of Internet resources 
and agree to the transition of DNS management responsibility into private 
hands.  The transition should be carefully carried out, so that the transfer 
does not damage continuity of the DNS stability and IANA function.</li>
<br />
</ul>
<br />
Sincerely yours,<br />
<br />
<br />
Koki Higashida<br />
President<br />
Japan Registry Services Co., Ltd.
</td></tr>
</tbody></table>
<br /><br />
<strong>References:</strong><br />
<br />
Notice of Inquiry<br />
National Telecommunications and Information Administration<br />
[Docket No. 090420688-9689-01]<br />
Assessment of the Transition of the Technical Coordination and Management of the Internet's Domain Name and Addressing System<br />
<a href="http://www.ntia.doc.gov/frnotices/2009/FR_ICANNVol.74_No78_Apr242009.pdf">http://www.ntia.doc.gov/frnotices/2009/FR_ICANNVol.74_No78_Apr242009.pdf</a><br />
<br />
Public Comments: DNS Transition<br />
<a href="http://www.ntia.doc.gov/comments/2009/dnstransition/">http://www.ntia.doc.gov/comments/2009/dnstransition/</a>
<br />
<br />
JPRS Submitted Comments Responding to Notice of Inquiry by the U.S. Department of Commerce Regarding Joint Project Agreement (19 February 2008)<br />
<a href="http://jprs.co.jp/en/topics/2008/080219.html">http://jprs.co.jp/en/topics/2008/080219.html</a>
<br />
<br />
JPRS Submitted Comments Responding to Notice of Inquiry by the U.S. Department of Commerce (7 July 2006)<br />
<a href="http://jprs.co.jp/en/topics/060707.html">http://jprs.co.jp/en/topics/060707.html</a><br />
</div>
</div>
]]>
    </content>
</entry>
<entry>
    <title>Translation of &quot;JP Domain Name Registry Report 2008&quot; Posted</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2009/090525.html" />
    <published>2009-05-25T11:14:13Z</published>
    <updated>2009-05-25T11:16:51Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(25 May 2009)</div>
<p><br />
JPRS posted English translation of "JP Domain Name Registry Report 2008." This is the annual report for 2008, briefing that year's activities performed by JPRS, in relation to its management and administration of .JP top-level domain. </p>
<p>Translation: JP Domain Name Registry Report 2008 (PDF) <br />
<a href="http://jprs.co.jp/doc/report/registry-report-2008-e.pdf">http://jprs.co.jp/doc/report/registry-report-2008-e.pdf</a></p>
<p>Original: JP Domain Name Registry Report 2008 (in Japanese, PDF) <br />
<a href="http://jprs.co.jp/doc/report/registry-report-2008.pdf">http://jprs.co.jp/doc/report/registry-report-2008.pdf</a></p>
<p><br />
Note: This English translation is provided only for reference. <br />
</p>]]>
    </content>
</entry>
<entry>
    <title>JPRS Participates in BIND 10 Development Project</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/press/2009/090422.html" />
    <published>2009-04-22T08:10:46Z</published>
    <updated>2009-05-13T08:36:21Z</updated>
    <summary>Press Release April 22, 2009 Japan Regis...</summary>
    
        <category term="Press Release" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        <![CDATA[<p>Press Release</p>
<p>April 22, 2009<br />
Japan Registry Services Co., Ltd.(JPRS)<br />
</p>]]>
        <![CDATA[<p>- Contributing to Operational Stability of the Internet -</p>
<p>Japan Registry Services Co., Ltd. (JPRS: head office at Chiyoda-ku, Tokyo; President: Koki Higashida), the company responsible for management and administration of .JP top-level domain and overall management and operation of the JP Domain Name System (JP DNS), announced today that it would participate in the BIND 10 development project. BIND 10 is the next version of DNS software to be launched by Internet Systems Consortium, Inc. (ISC: head office at Redwood City, CA; President: Paul Vixie). </p>
<p>DNS is one of the fundamental functions supporting the Internet and is indispensable for its smooth operation. BIND, which is developed by ISC, is the most widely-used DNS server software. The current BIND version 9 was released in September 2000, thus it has been nearly a decade since the start of its distribution. </p>
<p>With the remarkable growth of the Internet during these years, requirements for DNS, such as stronger resistance against DDoS attacks on DNS servers, are building up continuously. In addition, as the new technologies including IP Anycast and DNSSEC spread, demand for the new DNS software to apply these new technologies is increasing. In response to these growing needs, ISC announced a new project to develop the next-generation BIND 10 which offers enhanced security and resilience. </p>
<p>In support of the objectives of the project, and as the registry of .JP domain names, JPRS decided to participate in it from the development stage. JPRS believes that would lead to its contribution towards the operational stability of the Internet. A number of TLD registries in the world, including CIRA (.ca) and DENIC (.de), have also announced that they will join the project. And JPRS plans to take an active part in this joint development initiative not only by offering financial support, but also by assigning its engineers to the project. </p>
<p>According to the current plan, BIND 10 will have the features including the followings:<br />
<ol><li>Secure<br />
- Full support of DNSSEC<br />
- Improved key management and renewal benefiting DNSSEC operators </li><br />
<li>Flexible<br />
- Modular design<br />
- Facile integration with external modules and programs </li><br />
<li>Scalable<br />
- Adaptability to a wide range of systems from a large complex system used by TLDs to small home system </li><br />
<li>Resilient<br />
- System logs to provide data necessary for identifying the causes of failures<br />
- Prompt notification of and response to threats against security, including attacks from outside. </li><br />
</ol></p>
<p>Like its predecessors, BIND 10 will be released by ISC as the open-source software offered for the entire Internet community. </p>
<p>JPRS will continue to cooperate with DNS server operators to meet the needs of the Internet community and society at large, and endeavor to achieve growth and operational stability of the Internet. </p>
<p><br />
<big><strong>List of TLD Registries Announcing Participation in BIND 10 Development Project:</strong></big></p>
<p>- JPRS (.jp/ Japan)<br />
- CIRA (.ca/ Canada)<br />
- Afilias (.info)<br />
- AFNIC (.fr/ France)<br />
- DENIC (.de/ Germany)<br />
- IIS.SE (.se/ Sweden)<br />
- Nominet (.uk/ United Kingdom)<br />
- Registro.br (.br/ Brazil)<br />
- SIDN (.nl/ The Netherlands)<br />
- ZADNA (.za/ South Africa)</p>
<p><br />
<hr></p>
<p><big><strong>Glossary</strong></big></p>
<p><strong>* IP Anycast </strong><br />
Generally, a single IP address is assigned to each specific host on the Internet. With the IP Anycast technology, a single IP address is assigned to a particular function or service so that multiple hosts can handle the transactions assigned to the address. With this approach, load distribution is realized by the routing technology. Servers that use IP Anycast technology share a single IP address, and users' requests are handled by the server closest to the user in terms of routing protocols. </p>
<p><strong>* DNSSEC</strong> <br />
DNSSEC is an extended function of DNS providing DNS services more securely. DNSSEC uses the public key encryption technology for authentication to assure the legitimacy of the source and contents of the data received from servers. </p>
<p>*<strong> DDoS attack </strong><br />
Distributed Denial of Service (DDoS) attack whereby a number of computers are engaged in denial of service attacks simultaneously. </p>
<p><strong>* Japan Registry Services Co., Ltd. (JPRS) </strong><br />
<a href="http://jprs.co.jp/en/" target="_blank">http://jprs.co.jp/en/</a><br />
JPRS was incorporated on December 26, 2000 to carry out responsibility of the management and administration of the .JP top-level domain and to operate the domain name system. As a company dedicated to maintaining the Internet infrastructure, JPRS contributes to the development of the Internet and building of a better future for everyone. </p>
<p><br />
<big><strong>References</strong></big></p>
<p><strong>* "ISC Commences Development of Next Generation Domain Name Server Architecture with Unprecedented Community Sponsorship": Release by ISC</strong> <br />
<a href="https://www.isc.org/about/pr/2009042200" target="_blank">https://www.isc.org/about/pr/2009042200</a> </p>
<p><strong>* ISC BIND 10</strong> <br />
<a href="https://www.isc.org/bind10/" target="_blank">https://www.isc.org/bind10/</a> </p>
<p><strong>* ISC (Internet Systems Consortium, Inc.) </strong><br />
<a href="https://www.isc.org/" target="_blank">https://www.isc.org/</a> </p>
<p><strong>* BIND (Berkeley Internet Name Domain)</strong> <br />
<a href="https://www.isc.org/software/bind/" target="_blank">https://www.isc.org/software/bind/</a> </p>
<p><br />
<big><strong>Press Contacts</strong></big></p>
<p>Japan Registry Services Co., Ltd. (JPRS)<br />
TEL:+81-3-5215-8451<br />
FAX:+81-3-5215-8452<br />
E-mail: press@jprs.co.jp<br />
http://jprs.co.jp/<br />
Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda<br />
Chiyoda-ku, Tokyo 101-0065, Japan</p>]]>
    </content>
</entry>
<entry>
    <title>RFC on EAI Co-Authored by JPRS Engineers Was Published</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2009/090406.html" />
    <published>2009-04-06T02:15:52Z</published>
    <updated>2009-04-13T07:24:54Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<p><strong>- Contributing to the Standardization Activity of the E-mail Address Internationalization -</strong></p>
<div style="text-align: right;">(6 April 2009)</div>
<p><br />
On 31 March 2009, an RFC which specifies a standard for E-mail Address Internationalization (EAI) and was co-authored by two (2) engineers of JPRS was published. This means that EAI is prepared for the field tests toward the actual utilization. </p>
<p></p>
<p>An e-mail address is described in the form of "user-name@domain-name". In terms of standardization of "domain name" which is on the right part to @, a standard is already defined as Internationalized Domain Name (IDN). EAI is the technology which internationalizes the whole e-mail address including the left part to @, i.e., "local part"; also, it is the technology whereby non-ASCII characters of various languages including Japanese can be used in any part of an e-mail address. </p>
<p></p>
<p>Internationalization of e-mail address is one of the significant technical developments to break down barriers to the use of the Internet; thus, it is beneficial for those whose mother tongue is not English. E-mail is one of the fundamental services of the Internet. Therefore, we need to internationalize e-mail through retaining the compatibility with the current system, while making them interface with the future extensions. </p>
<p></p>
<p>With this publication, the fundamental standards to keep the backward compatibility and extend the respective protocols which set up the e-mail system are compiled in four (4) RFCs (RFC 5335, RFC 5336, RFC 5337 and RFC 5504) as experimental standards. RFC 5504 specifically defines a standard for the backword compatibility with the existing e-mail system in case the internationalized e-mail address is used. RFC 5504 is co-authored by Mr. Kazunori Fujiwara and Mr.Yoshiro Yoneya from JPRS. </p>
<p></p>
<p>Now that these RFCs are published, all the fundamental RFCs required to handle the internationalized e-mail address are in place, so the development of experimental implementation and the field test on the Internet toward the actual utilization are now available. From now on, implementation to e-mail softwares and the review toward the preparation of a variety of RFCs which become standard track are going to be proceeded through the field tests and other related activities. </p>
<p></p>
<p><br />
<strong>References:</strong></p>
<p><br />
<ul><li>RFC 5504<br />
(Downgrading mechanism for Email Address Internationalization. K. Fujiwara, Ed., Y. Yoneya Ed.. March 2009.)<br />
<a href="http://www.ietf.org/rfc/rfc5504.txt" target="_blank">http://www.ietf.org/rfc/rfc5504.txt</a></li></p>
<p><li>RFC 5335<br />
(Internationalized Email Headers. Y. Abel, Ed.. September 2008.)<br />
<a href="http://www.ietf.org/rfc/rfc5335.txt" target="_blank">http://www.ietf.org/rfc/rfc5335.txt</a></li></p>
<p><li>RFC 5336<br />
(SMTP Extension for Internationalized Email Addresses. J. Yao, Ed., W. Mao, Ed.. September 2008.)<br />
<a href="http://www.ietf.org/rfc/rfc5336.txt" target="_blank">http://www.ietf.org/rfc/rfc5336.txt</a></li></p>
<p><li>RFC 5337<br />
(Internationalized Delivery Status and Disposition Notifications. C. Newman, A. Melnikov, Ed.. September 2008.)<br />
<a href="http://www.ietf.org/rfc/rfc5337.txt" target="_blank">http://www.ietf.org/rfc/rfc5337.txt</a></li><br />
</ul></p>]]>
    </content>
</entry>
<entry>
    <title>JPRS Comments in Response to Notice of Inquiry by the U.S. DoC on DNSSEC</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2008/081125.html" />
    <published>2008-11-25T02:01:16Z</published>
    <updated>2009-04-10T02:15:32Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(25 November 2008)</div>
<p><br />
On 22 November 2008, JPRS submitted its comments responding to the Notice of Inquiry which had been opened on 9 October by the National Telecommunications and Information Administration (NTIA), U.S. Department of Commerce (DoC).</p>
<p></p>
<p>The Notice of Inquiry invites comments regarding implementation of DNSSEC at the root zone. JPRS submitted its position from the standpoint of supporting early deployment of DNSSEC.</p>
<p></p>
<p><br />
<strong>References:</strong></p>
<ul><li>Notice of Inquiry
Department of Commerce
National Telecommunications and Information Administration
Docket No. 0810021307-81308-01
Enhancing the Security and Stability of the Internet's Domain Name and Addressing System
<li><a href="http://www.ntia.doc.gov/frnotices/2008/FR_DNSSEC_081009.pdf" target="_blank">http://www.ntia.doc.gov/frnotices/2008/FR_DNSSEC_081009.pdf</a></li>
<p><li>NTIA Seeks Public Comments Regarding the Deployment of DNSSEC<br />
<a href="http://www.ntia.doc.gov/DNS/dnssec.html" target="_blank">http://www.ntia.doc.gov/DNS/dnssec.html </a></li><br />
</ul></p>
<p><br />
<strong>JPRS Comments</strong></p>
<table>
<tr><td>
To: Office of International Affairs<br>
National Telecommunications and Information Administration, U.S.<br>
Department of Commerce<br>
<p><br />
To whom it may concern, </p>
<p><br />
Greetings. I am Kentaro Mori of JPRS (TLD registry of .JP), currently in charge of the project for DNSSEC production implementation to .JP zone. </p>
<p><br />
On behalf of JPRS, I would like to provide a feedback to your public comment request about DNS security of docket number: 0810021307-81308-01 in the Federal Register (October 9, 2008 Volume 73, Number 197, Page 59608-59612). </p>
<p><br />
Please find the comments below, which are our thoughts basically related to your questions. </p>
<p>---------------------------------------------------------------------- <br />
<strong>Comments with regards to Questions on DNSSEC Deployment Generally: </strong></p>
<p>DNSSEC is the technology that the Internet community has been cooperatively designing and verifying for a long time, carefully considering backward compatibility with the existing DNS, its performance issues, conformance issues with the current Internet structure and so on. We consider DNSSEC to be the only practical solution we are currently able to take to protect DNS fundamentally from data manipulation attempts. </p>
<p><br />
Therefore, considering the current situation, where the existence of apparent risks for DNS has been widely recognized, we support the immediate preparation of DNSSEC deployment. Without already knowing obvious ability to enforce DNS security, to start verifying other methods which replace DNSSEC or are combined with DNSSEC would be a waste of time and resources. </p>
<p><br />
To facilitate deployment, an effort by the root/TLD community to enlighten stakeholders (end users, software vendors, ISPs, Registrars, etc.) will be required, in addition to signing the root zone. </p>
<p><br />
<strong>Comments with regards to General Questions Concerning Signing of the Root Zone:</strong> </p>
<p>From the standpoint of properly moving the Internet forward with timely response to security demands, those who are involved in root DNS or TLD DNS administration have great responsibility to the community. Proactively deploying DNSSEC into the root/TLD zones would be one of the key elements in answering these demands and is considered to be the right thing to do in line with their roles. </p>
<p><br />
It would become difficult for users to replace their trust anchors with the root key if alternative technologies (such as DLV or ITAR) have been widely spread prior to the launch of the signed root zone. To deploy DNSSEC in accordance with the original design, signing of the root zone in the earlier deployment stage will be very important. </p>
<p><br />
<strong>Comments with regards to Operational Questions Concerning Signing of the Root Zone: </strong></p>
<p>Operation flow should be designed so as to avoid the situation where a human error would lead to catastrophe, such as a whole TLD zone vanishing from DNSSEC-aware resolvers due to mismatching of TLD keys in a delegation point. </p>
<p><br />
Meanwhile, it is highly important that the operation flow has the ability to update the root zone immediately, especially in urgent situation such as the case of TLD key compromise occurring. </p>
<p><br />
The flow model that transfers root keys or zone data between multiple entities may have more difficulties than the other models, in keeping data security throughout the communication channels, operational efficiency for periodical root key rollover and rapid reaction capability in the event of emergent TLD key rollover. </p>
<p><br />
The purpose of DNSSEC deployment is to improve the current situation where DNS response can be malformed by unauthorized entities. Thus, it is desirable to implement a flow which extends naturally from the current one. </p>
<p>---------------------------------------------------------------------- <br />
We hope this helps you move the deployment activities for the root zone signing forward to whatever extent. We also appreciate you giving us this opportunity. </p>
<p><br />
Sincerely, </p>
<p><br />
Kentaro Mori, Service Development department<br />
Japan Registry Services Co.,Ltd. (JPRS)<br />
E-Mail: kentaro@jprs.co.jp<br />
</td></tr><br />
</table></p>]]>
    </content>
</entry>
<entry>
    <title>&quot;Interim Report on DNAME Technical Evaluation&quot; Posted</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2008/080929.html" />
    <published>2008-09-29T08:44:39Z</published>
    <updated>2009-04-13T07:19:46Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(29 September 2008)</div>
<p></p>
<p>JPRS has published on its website "Interim Report on DNAME Technical Evaluation" which was performed by JPRS. </p>
<p></p>
<p>This report explains how DNAME resource record works with some of major recursive DNS servers if it is used to implement IDN ccTLD. </p>
<p></p>
<p>Interim Report on DNAME Technical Evaluation<br />
<a href="http://jprs.co.jp/en/Report-20080929-DNAME.pdf" target="_blank">http://jprs.co.jp/en/Report-20080929-DNAME.pdf </a></p>
<p><br />
<strong>Reference:</strong></p>
<p>DNAME (Non-Terminal DNS Name Redirection)<br />
<a href="http://www.ietf.org/rfc/rfc2672.txt" target="_blank">http://www.ietf.org/rfc/rfc2672.txt </a></p>]]>
    </content>
</entry>
<entry>
    <title>Translation of &quot;JP Domain Name Registry Report 2007&quot; Posted </title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2008/080522.html" />
    <published>2008-05-22T08:43:13Z</published>
    <updated>2009-04-13T07:17:11Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(22 May 2008)</div>
<p><br />
JPRS posted English translation of "JP Domain Name Registry Report 2007." This is an annual report for 2007, briefing that year's activities performed by JPRS, in relation to its management and administration of .JP top-level domain. </p>
<p>Translation: JP Domain Name Registry Report 2007 (PDF) <br />
<a href="http://jprs.co.jp/doc/report/registry-report-2007-e.pdf" target="_blank">http://jprs.co.jp/doc/report/registry-report-2007-e.pdf</a></p>
<p>Original: JP Domain Name Registry Report 2007 (in Japanese, PDF) <br />
<a href="http://jprs.co.jp/doc/report/registry-report-2007.pdf" target="_blank">http://jprs.co.jp/doc/report/registry-report-2007.pdf</a></p>
<p><br />
Note: This translation is made only for reference. The Japanese language version of this report is original.</p>]]>
    </content>
</entry>
<entry>
    <title>&quot;Application Evaluation Report Regarding IDN TLD&quot; Posted</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2008/080402.html" />
    <published>2008-04-02T08:39:57Z</published>
    <updated>2009-04-13T07:15:14Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(2 April 2008)</div>
<p><br />
JPRS has published on its website "Application Evaluation Report Regarding IDN TLD" which was co-authored by CNNIC, NIDA (KRNIC), TWNIC and JPRS. </p>
<p></p>
<p>This report consists of the results of the tests carried out by each of these co-authors on a voluntary basis. The objective of the report is to provide with common criteria for the evaluation of IDN TLDs on applications and to encourage relevant entities to join the evaluation. </p>
<p></p>
<p><strong>Application Evaluation Report Regarding IDN TLD</strong><br />
<a href="http://jprs.co.jp/topics/Report-20080331-v1.0.pdf" target="_blank">http://jprs.co.jp/topics/Report-20080331-v1.0.pdf </a></p>
<p></p>
<p><br />
<strong>References:</strong></p>
<ul><li>CNNIC<br>
<a href="http://www.cnnic.cn/" target="_blank">http://www.cnnic.cn/ </a></li>
<li>NIDA (KRNIC)<br>
<a href="http://www.nic.or.kr/" target="_blank">http://www.nic.or.kr/ </a></li>
<li>TWNIC<br>
<a href="http://www.twnic.net.tw/" target="_blank">http://www.twnic.net.tw/ </a></li>
</ul>]]>
    </content>
</entry>
<entry>
    <title>Cumulative Number of Registered JP Domain Names Exceeds One Million</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2008/080305.html" />
    <published>2008-03-05T08:35:25Z</published>
    <updated>2009-04-13T07:13:02Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<p><strong>- General-use JP Domain Names Quadrupled in 7 Years -</strong></p>
<p><br />
<div style="text-align: right;">(5 March 2008)</div></p>
<p></p>
<p>On 4 March 2008, JPRS announced that the cumulative number of registered JP domain names as of 1 March 2008 exceeded one million for the first time, hitting 1,003,285. </p>
<p></p>
<p>Of 1,003,285 registrations, 622,903 are the General-use JP domain names (e.g., EXAMPLE.JP) (ASCII: 480,890; and Japanese: 142,013). The rest consists of the Organizational Type JP domain names (e.g., EXAMPLE.CO.JP) and Geographic Type JP domain names, recording 380,382. </p>
<p></p>
<p>The General-use JP domain names marked 17% increase by over 90,000 from 532,699 to 622,903, while Organizational and Geographic Type JP domain names grew by steady 4%. </p>
<p></p>
<p>This rapid growth of the General-use JP domain name was propelled by the rise of companies setting up a website for each of their product as well as individuals sending out information to the Internet through various online means including blogs. Also, JPRS regards that a series of its measures to improve its services, including reduction of registration fee in March 2007, has promoted registrations and active utilization of the General-use JP domain names. </p>
<p></p>
<p>Back in May 1992, when JP domain names were managed by a small group of researchers, there were only 795 JP domain names. In 1993, JPNIC (Japan Network Information Center), the predecessor of JPRS, was established and took over the responsibility to manage JP domain names. Since then, registration of JP domain names has taken a leap forward with increased commercial use of the Internet, which resulted in 100,000 registrations in 1999. Then in February 2001, when JPRS launched General-use JP domain names, the number of registration expanded further and marked 240,000. JP domain names has continued to increase along with the Internet growth in Japan, which led to the recent accomplishment of one million registrations for the first time in the history of JP domain names. </p>
<p><br />
<strong>References:</strong></p>
<ul><li>Statistics<br>
<a href="http://jprs.co.jp/en/stat/" target="_blank">http://jprs.co.jp/en/stat/</a></li>
<li>Time-Series Data of JP Domain Name Registration (since 1992)<br>
<a href="http://jprs.co.jp/en/stat/domains.html" target="_blank">http://jprs.co.jp/en/stat/domains.html</a></li>
</ul>]]>
    </content>
</entry>
<entry>
    <title>Hirofumi Hotta of JPRS Re-Appointed as the ccNSO Council Member</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2008/080227.html" />
    <published>2008-02-27T08:31:06Z</published>
    <updated>2009-04-13T07:11:06Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(27 February 2008)</div>
<p></p>
<p>Hirofumi Hotta, Director of JPRS, was re-appointed as the Council Member of ICANN ccNSO (Country Code Names Supporting Organisation). </p>
<p></p>
<p>ccNSO, one of ICANN's Supporting Organisations, was established under the bylaws of ICANN. ccNSO bears important roles in nurturing consensus across the ccTLD community relating various issues concerning ccTLD's, and in making policy recommendations to ICANN Board, by coordinating with the other ICANN Supporting Organisations and Committees. </p>
<p></p>
<p>ccNSO Council Member is to be first nominated by other ccTLD managers and then selected through election. Hotta who has been the Councilor since February 2005, has been vigorously contributing to ICANN activities, such as establishing Accountability Framework (a framework to formalize the relationship between ICANN and ccTLD registries), and reviewing global policies concerning Internationalized Domain Names (IDNs). </p>
<p></p>
<p>Due to termination of his current term as the Council Member, and through the process to select the successor, Hotta has been elected again to represent Asia-Pacific region. He will cotinue to serve until March 2011. </p>
<p></p>
<p>One of the biggest challenges for the ccTLD community today is to develop policies with regards to implementation of IDN ccTLD's. Hotta and JPRS will make full use of their knowledge and expertise in addressing this issue, as well as other relevant issues. </p>
<p><br />
<strong>References:</strong></p>
<ul><li>ccNSO Council Members<br>
<a href="http://ccnso.icann.org/about/council.htm" target="_blank">http://ccnso.icann.org/about/council.htm</a> </li>
<li>ICANN(Internet Corporation for Assigned Names and Numbers)<br>
<a href="http://www.icann.org/" target="_blank">http://www.icann.org/</a>
<li>ccNSO(Country Code Names Supporting Organisation)<br>
<a href="http://ccnso.icann.org/" target="_blank">http://ccnso.icann.org/</a></li>
</ul>]]>
    </content>
</entry>
<entry>
    <title>JPRS Submitted Comments Responding to Notice of Inquiry by the U.S. Department of Commerce Regarding Joint Project Agreement </title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2008/080219.html" />
    <published>2008-02-19T08:22:19Z</published>
    <updated>2009-04-09T08:30:05Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(19 February 2008)</div>
<p></p>
<p>On 15 February 2008, JPRS submitted its comments responding the notice of inquiry opened by the National Telecommunications and Information Administration, U.S. Department of Commerce.</p>
<p>The Joint Project Agreement (JPA) is between the United States government and ICANN for the purpose of transitioning the Internet domain name and addressing system to a private sector multi-stakeholder model. This agreement is in the process of a mid-term review for which the NTIA called for comments.</p>
<p>Since its inception, JPRS has strongly supported private-sector-led Internet governance and so actively participated in the ICANN process. On this account, JPRS submitted its comments appreciating ICANN's achievement. This is in line with the submission which JPRS had made in July 2006, as in reference below.</p>
<p><br />
<strong>JPRS Comments </strong><br />
<table><tr><td><br />
15 February 2008</p>
<p>Office of International Affairs<br />
National Telecommunications and Information Administration<br />
Ms. Suzanne R. Sene<br />
1401 Constitution Avenue / Room 4701<br />
Washington DC 20230<br />
USA</p>
<p>Subject: The Continued Transition of the Technical Coordination and Management of the Internet's Domain Name and Addressing System: Midterm Review of the Joint Project Agreement</p>
<p>Dear Ms Sene,</p>
<p>JPRS appreciates the US Government for offering this opportunity for comments on the transition of the coordination and management of the DNS.</p>
<p>We, JPRS (Japan Registry Services Co., Ltd.), are one of the ccTLD Sponsoring Organizations that formalized the relationship with ICANN in its earliest days. Since its inception, JPRS has supported private-sector-led Internet governance, thus contributed to organize ICANN and participated in discussions of various issues surrounding the management of the DNS. This contribution has been made based on a notion that JPRS, as well as the other community members, forms part of ICANN.</p>
<p>JPRS gives the following comments responding to your Notice of Inquiry:</p>
<p><br />
<ul><li>ICANN has promoted management of the Internet's technical resources on a multi-stakeholder coordination basis and contributed to realizing security and stability of the DNS. All in all, we view ICANN has achieved a satisfactory level of performance.</li><br />
<li>Especially, we value a series of steps taken by ICANN to protect gTLD registrants including Registry Failover Planning, Registrar Data Escrow and RAA amendments; as these measures strengthen consumer protection as well as security and stability of the DNS. We also value ICANN's processes where the inputs made by JPRS and other parties such as ccTLD registries, who have similar experiences, were well taken into consideration in ICANN's developing these solutions. It is crucial that ICANN continues to listen to and incorporate the views and experiences of the relevant parties in addressing any issues. </li><br />
<li>It is likely that ICANN adds new TLD's in near future. In introducing the new TLD's, ICANN needs to develop mechanisms that avoid confusion and satisfy the demand of the community. One of ccTLD manager's responsibilities is to serve the interest of the relevant community. In this regard, we believe ccTLD's can provide valuable input to ICANN throughout the process for the introduction. So we propose ICANN continue to consider such input for the policy development. </li><br />
<li>The initial process to address IDN TLD issue was slow as it took time to gain common understanding of the issues per se by multi-stakeholders, global organizations and individuals. In the past few years, however, the discussion has been accelerated to a very high level, accompanied by concrete action. Accordingly, we can now expect to see the first IDN TLD within a year or so. This acceleration is the evidence of the fact that complex issues have been tackled by ICANN's activities through participation of multiple stakeholders, including global organizations and individuals. </li><br />
<li>In the early days, not many ccTLD's formalized their relationships with ICANN due to excess formality of the responsibility in the proposed contract. Later, however, ICANN poured efforts in perceiving the situation of ccTLD's, and a new framework based on mutual trust called Accountability Framework was introduced. It is noteworthy that as of January 22, 2008, as many as 53 ccTLD's, including 37 ccTLD's who signed Accountability Frameworks, have formalized their relationships with ICANN. </li><br />
<li>In respect to more participation of ccTLD's in the ICANN process, a working group has been established in ccNSO; and we expect to see further development. We believe relationship between ccTLD's and ICANN will continue to be stabilized. JPRS, as a ccTLD manager, is certainly ready to contribute in achieving this. </li><br />
<li>The plans for transition of the DNS responsibility should be carefully developed so that the transition does not damage continuity of the IANA function. We understand the IANA is the scope of the agreement that is separate from JPA, but we should take into consideration of the continuity of IANA function when developing the plan. </li><br />
</ul></p>
<p>Finally, please let us emphasize that JPRS continues to support the private-sector management of the DNS. We strongly believe that now is the time to start developing the plan for transition in preparation for the upcoming termination of JPA.</p>
<p>Sincerely yours,</p>
<p>Koki Higashida<br />
President<br />
Japan Registry Services Co., Ltd. <br />
</td></tr><br />
</table></p>
<p><strong>References:</strong></p>
<p>Notice of Inquiry<br />
Department of Commerce<br />
National Telecommunications and Information Administration<br />
The Continued Transition of the Technical Coordination and Management of the Internet's Domain Name and Addressing System:<br />
Midterm Review of the Joint Project Agreement<br />
Docket No. 071023616-7617-01<br />
<a href="http://www.ntia.doc.gov/ntiahome/frnotices/2007/ICANN_JPA_110207.html" target="_blank">http://www.ntia.doc.gov/ntiahome/frnotices/2007/ICANN_JPA_110207.html</a></p>
<p>NTIA Seeks Public Comments Regarding Joint Project Agreement with ICANN<br />
<a href="http://www.ntia.doc.gov/ntiahome/domainname/jpamidtermreview.html" target="_blank">http://www.ntia.doc.gov/ntiahome/domainname/jpamidtermreview.html </a></p>
<p>JPRS Submitted Comments Responding to Notice of Inquiry by the U.S. Department of Commerce (7 July 2006)<br />
<a href="http://jprs.co.jp/en/topics/060707.html" target="_blank">http://jprs.co.jp/en/topics/060707.html</a></p>]]>
    </content>
</entry>
<entry>
    <title>The M-Root DNS server has its IPv6 address registered in the root zone, making DNS queries in IPv6 possible, and further accelerating transition to IPv6.</title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/press/2008/080205.html" />
    <published>2008-02-05T09:02:11Z</published>
    <updated>2009-03-23T09:14:31Z</updated>
    <summary>Press Release February 5, 2008 Japan Reg...</summary>
    
        <category term="Press Release" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        <![CDATA[<p>Press Release</p>
<p>February 5, 2008<br />
Japan Registry Services Co., Ltd.(JPRS)<br />
WIDE Project<br />
</p>]]>
        <![CDATA[<p>The WIDE Project (Representative: Jun Murai, Vice President, Keio University and Prof., Faculty of Environmental Information, Keio University) and Japan Registry Services Co., Ltd. (JPRS; Chiyoda-ku Tokyo; President: Koki Higashida) announced that the IPv6 address of M-Root DNS server, a jointly operated Root DNS server under responsibility of WIDE Project, has been registered with the Root zone by IANA. This registration enables DNS queries in IPv6 to Root DNS servers, and it is expected that it triggers the deployment of the IPv6. </p>
<p>The M-Root DNS server is one of the thirteen root servers currently operating in the world. The WIDE Project first started its operation in August 1997 as the only root server in the Asia-Pacific region. With an expansion of added servers enhanced with the IP Anycast technology, the servers are now based in such countries as Japan (three servers in Tokyo), Korea (Seoul), France (Paris) and U.S. (San Francisco). They have been jointly operated by WIDE and JPRS through assistance and cooperation from IXs and ISPs. </p>
<p>The M-Root DNS server acquired the IPv6 address in 2003 ahead of any other Root DNS servers in the world.Through various experiments, the IPv6 address of the M-Root DNS server, 2001:dc3::35, is finally registered as an AAAA record in the root zone, offering a DNS query to the root zone solely operating in IPv6. While IPv4 is facing its address exhaustion that is likely to surface in about two years, the IPv6 address registration of the M-Root DNS server is expected to promote further deployment of IPv6. </p>
<p>The WIDE Project and JPRS will continuously and jointly work in cooperation with other domestic and international DNS server operators to achieve further development and to provide greater operational stability for the Internet in accordance with the demands of the Internet community and society. </p>
<p><br />
<hr></p>
<p><br />
Terminology</p>
<p><br />
<strong>* Root DNS server: </strong><br />
A group of name servers that maintain the information stored at the top most level in the hierarchy of the Domain Name System (DNS). The Root DNS servers have 13 host names ranging from A.ROOT-SERVERS.NET to M.ROOT-SERVERS.NET. Their task is to provide the core information that makes all kinds of domain naming available on the Internet.<br />
List of the Root DNS server operators: <a href="http://www.root-servers.org/" target="_blank">http://www.root-servers.org/</a></p>
<p><strong>* IANA (Internet Assigned Numbers Authority) </strong><br />
IANA is currently operated by ICANN. The tasks of IANA include allocation and management of the Internet addresses and numbers used in various Internet protocols in addition to DNS root zone management. It is also responsible for IPv4/IPv6 address allocation to the regional registries such as APNIC.<br />
<a href="http://www.iana.org/" target="_blank">http://www.iana.org/</a></p>
<p><strong>* ICANN (The Internet Corporation for Assigned Names and Numbers) </strong><br />
ICANN is a non-profit corporation established in October 1998, with the goal of coordinating and managing the Internet resources globally. The tasks of ICANN include allocation of IP (Internet Protocol) address space, assignment of protocol identifiers, name system management for gTLD (generic Top-Level Domain) and ccTLD(country code Top-Level Domain) and system administration of root servers.<br />
<a href="http://www.icann.org/" target="_blank">http://www.icann.org/</a></p>
<p><strong>* AAAA record (a quad-A record)</strong><br />
An AAAA record is a DNS record used to specify an IPv6 address associated with the domain name (See RFC3596). A DNS cache server may also look up AAAA records of other DNS servers to submit DNS queries in IPv6.</p>
<p><strong>* Japan Registry Services Co., Ltd.(JPRS) </strong><br />
JPRS was incorporated on December 26, 2000 to carry out responsibility of the management and administration of the .JP top-level domain and to operate the domain name system. As a company dedicated to maintaining the Internet infrastructure, JPRS contributes to the development of the Internet and building of a better future for everyone.<br />
<a href="http://jprs.co.jp/">http://jprs.co.jp/</a></p>
<p><strong>* WIDE Project </strong><br />
WIDE (Widely Integrated Distributed Environment), established in 1988, is a research consortium that promotes the research and development of Internet technologies. Over 100 corporations and 40 universities are currently involved in the WIDE Project, partaking in a wide array of research and development activities.<br />
<a href="http://www.wide.ad.jp/" target="_blank">http://www.wide.ad.jp/</a> </p>
<p><br />
<big><strong>Press Contacts</strong></big></p>
<p>Japan Registry Services Co., Ltd. (JPRS)<br />
TEL:+81-3-5215-8451<br />
FAX:+81-3-5215-8452<br />
E-mail: press@jprs.co.jp<br />
http://jprs.co.jp/<br />
Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda<br />
Chiyoda-ku, Tokyo 101-0065, Japan</p>
<p><br />
WIDE Project<br />
TEL: +81-466-49-3618<br />
FAX: +81-466-49-3622<br />
E-mail: press@wide.ad.jp<br />
Delta 109, Keio Research Institute at SFC<br />
5322 Endo, Fujisawa-shi, Kanagawa 252-8520, Japan</p>]]>
    </content>
</entry>
<entry>
    <title>Shinta Sato of JPRS Appointed as the ICANN SSAC Member </title>
    <link rel="alternate" type="text/html" href="http://jprs.co.jp/en/topics/2007/071116.html" />
    <published>2007-11-16T08:15:30Z</published>
    <updated>2009-04-13T07:01:46Z</updated>
    <summary></summary>
    
        <category term="Topics" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://jprs.co.jp/">
        
        <![CDATA[<div style="text-align: right;">(16 November 2007)</div>
<p><br />
At the ICANN Board Meeting held on November 2, 2007 in Los Angeles, Mr.Shinta Sato of JPRS was formally appointed by ICANN Board as a member of SSAC (Security and Stability Advisory Committee), one of ICANN's Advisory Committees.</p>
<p>SSAC advises the ICANN community and the Board on matters relating to the security and integrity in the areas of Internet's naming and addressing systems.</p>
<p>The committee is made up of the experts for the operation of root servers, gTLD's/ccTLD's, domain name registrars, and Regional Internet Registries for IP address allocation.</p>
<p>In SSAC, Mr.Sato will build on his experience and expertise gained with JPRS, a leading ccTLD registry, and contribute to stable operation of the global Internet.</p>
<p>His participation to SSAC is in line with JPRS's notion that it consistently devotes itself to the interest of the global Internet community.</p>
<p><br />
<strong>References:</strong></p>
<p>ICANN (The Internet Corporation for Assigned Names and Numbers)<br />
<a href="http://www.icann.org/" target="_blank">http://www.icann.org/</a></p>
<p>SSAC (Security and Stability Advisory Committee)<br />
<a href="http://www.icann.org/committees/security/" target="_blank">http://www.icann.org/committees/security/</a></p>]]>
    </content>
</entry>
</feed>
