Jump to content

Joint Project Agreement: Difference between revisions

From ICANNWiki
Saassoln (talk | contribs)
Created page with "Image:UnderConstruction.png '''JPA''' is the abbreviation for '''Joint Project Agreement'''. A JPA was signed to reach a Memorandum of Understanding (MoU) between the Unite..."
 
Christiane (talk | contribs)
m Christiane moved page JPA to Joint Project Agreement over redirect: Standardize
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
[[Image:UnderConstruction.png]]
'''JPA''' is the abbreviation for '''Joint Project Agreement'''. A JPA was signed to reach a Memorandum of Understanding (MoU) between [[ICANN]] and the United States Department of Commerce ([[DOC]]), on the behalf of United States Government (USG). The two parties signed the agreement in September, 2006. The main objective of the JPA was to effect the transition of Domain Name System ([[DNS]]) management to the private sector. Under the Joint Project Agreement, ICANN agreed to carry out 10 responsibilities and committed itself to promote the security and stability of the Internet.<ref>[http://www.icann.org/en/jpa icann.org]JPA</ref>
 
 
'''JPA''' is the abbreviation for '''Joint Project Agreement'''. A JPA was signed to reach a Memorandum of Understanding (MoU) between the United States Department of Commerce ([[DOC]]), on the behalf of United States Government (USG) and the Internet Corporation for Assigned Names and Numbers (ICANN), a not-for-profit private sector organization. The two parties signed the agreement in September, 2006.
 
The main objective of the JPA was to effect the transition of Domain Name System (DNS) management to the private sector. Under the Joint Project Agreement, ICANN had agreed to carry out 10 responsibilities and had committed itself to promote the security and stability of the Internet. ICANN and US Department of Commerce are assessing these 10 responsibilities of ICANN for more than nine years now. <ref>[http://www.icann.org/en/jpa icann.org]JPA</ref>


== Responsibilities of ICANN under JPA ==
== Responsibilities of ICANN under JPA ==


In the Joint Project Agreement (JPA) signed between the US Department of Commerce, on behalf of the US government and ICANN, ICANN was mostly assigned with the following 10 responsibilities.
The following 10 responsibilities were assigned to ICANN upon the signing of the JPA:
Stability and Security: To ensure stability and security in the Internet’s unique identifier systems.
 
'''Transparency:''' To continue developing, testing and enhancing procedures to increase transparency in the adoption of policies pertaining to technical coordination of Internet Domain Name System (DNS).
 
'''Accountability:''' To develop, test, maintain and enhance the accountability mechanisms to be responsive to global Internet stakeholders.
Root server Security and relationships: To coordinate with the operators with root name servers and other relevant experts in relation to the operational and security issues, this can be both network as well as physical.
 
'''TLD management:''' To build and maintain processes so that there is competition, Internet DNS stability and consumer interests.
 
'''Multi-stakeholder Model:''' To improve and maintain multi-stakeholder model and to ensure that all the global stakeholders participate equally and conduct reviews of its existing advisory committees.
 
'''Role of Governments:''' To work with the Government Advisory Committee (GAC) members to review the GAC’s role so that there is effective consideration of the advice of GAC on the public policy aspects dealing with the technical coordination of the Internet.
 
'''IP Addressing:''' To work in a collaborative manner at both the global as well as regional level so that there is sufficient incorporation of the Regional Internet Registries policy making activities into ICANN.
 
'''Corporate Responsibility:''' To maintain efficiency and excellence in operations, which will include organizational measures, good governance , International private sector organization and to maintain relevant business and technical experience for members of the Board of Directors, staff and executive management.


'''Corporate Administrative Structure:''' To conduct a timely review of corporate administrative structure so that there is adequate stability and distribution of adequate resources. <ref>[http://www.icann.org/en/general/JPA-29sep06.pdf icann.org]JPA 29 sep 2006</ref>
# '''Stability and Security''': To ensure stability and security for the Internet’s unique identifier systems.
# '''Transparency:''' To continue developing, testing, and enhancing procedures to increase transparency in the adoption of policies pertaining to technical coordination of the Internet Domain Name System (DNS).
# '''Accountability:''' To develop, test, maintain, and enhance accountability mechanisms to be responsive to global Internet stakeholders.
# '''Root Server Security and Relationships''': To coordinate with the operators of root name servers and other relevant experts in relation to operational and security issues.
# '''TLD management:''' To build and maintain processes so that there is no monopoly on [[TLD]]s, so that the Internet DNS remains stable, and so that consumer interests are kept in mind.
# '''Multi-stakeholder Model:''' To improve and maintain the multi-stakeholder model and to ensure that all global stakeholders participate equally and conduct reviews of ICANN's existing advisory committees.
# '''Role of Governments:''' To work with the Government Advisory Committee (GAC) members to review the GAC’s role so that there is effective consideration of the advice of GAC on the public policy aspects dealing with the technical coordination of the Internet.
# '''IP Addressing:''' To work in a collaborative manner at both the global and regional levels so that there is sufficient incorporation of the Regional Internet Registries policy in the action of ICANN.
# '''Corporate Responsibility:''' To maintain efficiency and excellence in all operations, including organizational measures, good governance, and international private sector organization, and to maintain the Board of Directors, staff, and executive management so that they consist of people with relevant business and technical experience.
# '''Corporate Administrative Structure:''' To conduct a timely review of the corporate administrative structure so that there is adequate stability and adequate distribution of resources.<ref>[http://www.icann.org/en/general/JPA-29sep06.pdf icann.org]JPA 29 Sep 2006</ref>


== Midterm review of JPA ==
== Midterm review of JPA ==


'''NTIA:''' The National Telecommunications and Information Administration (NTIA) released a statement on the mid-term review of the JPA. The NTIA observed that there was a consensus on the need to preserve the stability and security of the Domain Name System (DNS) and recognition that the ICANN is a suitable technical coordinator of the Internet DNS. <ref>[http://www.techlawjournal.com/home/newsbriefs/2008/04a.asp techlawjournal.com]</ref>
'''NTIA:''' The National Telecommunications and Information Administration (NTIA) released a statement on the mid-term review of the JPA. The NTIA observed that there was a consensus on the need to preserve the stability and security of the Domain Name System (DNS) and recognized that ICANN is a suitable technical coordinator of the Internet DNS.<ref>[http://www.techlawjournal.com/home/newsbriefs/2008/04a.asp techlawjournal.com]</ref>


'''ICANN:''' During the midterm review of the JPA in the year 2008, ICANN specified that though the JPA was instrumental in the initial years of ICANN it viewed it as an agency, in which the US government was overseeing the part of DNS on a daily basis. It was also of the view that ending the JPA would help in providing a long-term stability and security for a model which will work and would also build confidence among all the participants that invested energy, time and thought for more than nine years and has led to a secured Internet coordination, which would always be managed by the stakeholders and not managed or looked after by any one entity. <ref>[http://www.icann.org/en/announcements/announcement-09jan08.htm icann.org]</ref>
'''ICANN:''' During the midterm review of the JPA in 2008, ICANN specified that though the JPA was instrumental in the initial years of ICANN, it viewed that the JPA allowed the US government too much power over DNS management. It was also of the opinion that ending the JPA would help to provide long-term stability and security for ICANN's DNS management, and would also build confidence among all participants who invested the energy, time and thought that led to secured Internet coordination that would always be managed by the stakeholders and not any one entity.<ref>[http://www.icann.org/en/announcements/announcement-09jan08.htm icann.org]</ref>


== References ==
== References ==

Latest revision as of 21:00, 19 June 2024

JPA is the abbreviation for Joint Project Agreement. A JPA was signed to reach a Memorandum of Understanding (MoU) between ICANN and the United States Department of Commerce (DOC), on the behalf of United States Government (USG). The two parties signed the agreement in September, 2006. The main objective of the JPA was to effect the transition of Domain Name System (DNS) management to the private sector. Under the Joint Project Agreement, ICANN agreed to carry out 10 responsibilities and committed itself to promote the security and stability of the Internet.[1]

Responsibilities of ICANN under JPA[edit | edit source]

The following 10 responsibilities were assigned to ICANN upon the signing of the JPA:

  1. Stability and Security: To ensure stability and security for the Internet’s unique identifier systems.
  2. Transparency: To continue developing, testing, and enhancing procedures to increase transparency in the adoption of policies pertaining to technical coordination of the Internet Domain Name System (DNS).
  3. Accountability: To develop, test, maintain, and enhance accountability mechanisms to be responsive to global Internet stakeholders.
  4. Root Server Security and Relationships: To coordinate with the operators of root name servers and other relevant experts in relation to operational and security issues.
  5. TLD management: To build and maintain processes so that there is no monopoly on TLDs, so that the Internet DNS remains stable, and so that consumer interests are kept in mind.
  6. Multi-stakeholder Model: To improve and maintain the multi-stakeholder model and to ensure that all global stakeholders participate equally and conduct reviews of ICANN's existing advisory committees.
  7. Role of Governments: To work with the Government Advisory Committee (GAC) members to review the GAC’s role so that there is effective consideration of the advice of GAC on the public policy aspects dealing with the technical coordination of the Internet.
  8. IP Addressing: To work in a collaborative manner at both the global and regional levels so that there is sufficient incorporation of the Regional Internet Registries policy in the action of ICANN.
  9. Corporate Responsibility: To maintain efficiency and excellence in all operations, including organizational measures, good governance, and international private sector organization, and to maintain the Board of Directors, staff, and executive management so that they consist of people with relevant business and technical experience.
  10. Corporate Administrative Structure: To conduct a timely review of the corporate administrative structure so that there is adequate stability and adequate distribution of resources.[2]

Midterm review of JPA[edit | edit source]

NTIA: The National Telecommunications and Information Administration (NTIA) released a statement on the mid-term review of the JPA. The NTIA observed that there was a consensus on the need to preserve the stability and security of the Domain Name System (DNS) and recognized that ICANN is a suitable technical coordinator of the Internet DNS.[3]

ICANN: During the midterm review of the JPA in 2008, ICANN specified that though the JPA was instrumental in the initial years of ICANN, it viewed that the JPA allowed the US government too much power over DNS management. It was also of the opinion that ending the JPA would help to provide long-term stability and security for ICANN's DNS management, and would also build confidence among all participants who invested the energy, time and thought that led to secured Internet coordination that would always be managed by the stakeholders and not any one entity.[4]

References[edit | edit source]