[CRISP-TEAM] Glossary of Definitions for RFP response

[Bill Woodcock]

Paul, thanks for taking the lead on the glossary.

I’d originally had in mind something more like the paragraph near the top of many legal documents, that defines all neologistic terms and keywords, but this has grown to something quite substantial, more than two pages already, and not all terms have been defined yet…  That’s seeming to me more like an appendix than something we cram in right at the top.  Thoughts?  Current version is appended, and I’d very much appreciate it if people would contribute definitions for the as-yet-undefined terms that people have asked be included.

                                -Bill



Accountability and Transparency Review Team (ATRT):

Address Supporting Organization (ASO):  a Supporting Organization in the ICANN structure, as defined in the ICANN Bylaws, and was formed in 2004 by the ICANN ASO MoU. The ASO's role is to review and develop recommendations on Internet Protocol (IP) address policy and to advise the ICANN Board.  The functions of the ASO are carried out by the Address Supporting Organization Address Council (ASO AC). https://aso.icann.org/about-the-aso/ <https://aso.icann.org/about-the-aso/>
Address Supporting Organization Address Council (ASO AC): has the following responsibilities in the ICANN structure and processes: undertaking a role in the global policy development process; defining procedures for the selection of individuals to serve on other ICANN bodies, in particular seats 9 and 10 on the ICANN Board, and implementing any roles assigned to the AC in such procedures; and providing advice to the ICANN Board on number resource allocation policy, in conjunction with the RIRs. The ASO AC function is carried out by the members of the NRO NC.

AFRINIC:

APNIC:

ARIN:

CRISP Team: The Consolidated RIR IANA Stewardship Proposal (CRISP) team was established by the five RIRs specifically for the purpose of producing this document.

Global Policies: Internet number resource policies that have the agreement of all RIRs according to their policy development processes and ICANN, and require specific actions or outcomes on the part of IANA or any other external ICANN-related body in order to be implemented.

Global Policy Development Process (gPDP): The RIR communities’ process for the development of policy relating to management of the global Internet number registries. The gPDP is employed in the development of policies relating to all of the number-related IANA activities described in Section I, except those relating to maintenance of the “IN-ADDR.ARPA” and “IP6.ARPA” domains. The gPDP is formally defined in Attachment A of the ASO MoU and posted on the NRO website: https://www.nro.net/documents/global-policy-development-process <https://www.nro.net/documents/global-policy-development-process>
IANA Functions Contract:

IANA Number Registries: This term refers collectively to the IPv4, IPv6, and ASN registries, as well as the associated IN-ADDR.ARPA and IP6.ARPA DNS zones. The registries can be found here: http://www.iana.org/numbers

IANA Numbering Services Operator: The party contractually engaged to perform the IANA Numbering Services.

IANA Numbering Services: The IANA activities relevant to the Internet Number Community, which are the allocation of blocks of Internet Number Resources (namely IPv4 addresses, IPv6 addresses, and Autonomous System Numbers or ASNs) to the Regional Internet Registries (RIRs); the registration of such allocations in the corresponding IANA Internet Number Registries; other related registry management tasks including the management of returned IP address space, and general registry maintenance; and the administration of the special-purpose “IN-ADDR.ARPA” and “IP6.ARPA” DNS zones, in accordance with IPv4 and IPv6 allocations, respectively.

ICANN Address Supporting Organization Memorandum of Understanding (ICANN ASO MoU): A Memorandum of Understanding signed by ICANN and the NRO in 2004, under which the NRO shall fulfill the role, responsibilities and functions of the ASO (including that the NRO NC shall carry out the functions of the ASO AC).

Internet Assigned Number Authority (IANA):

Internet Corporation for Assigned Names and Numbers (ICANN):

Internet Engineering Task Force Trust (IETF Trust):

Internet Number Community or RIR Community: Collaborative forum operating through decision-making processes that are bottom-up, inclusive and open to all parties interested in the IANA numbering services as well as in the services of the five RIRs.

Internet Number Community:

Internet Number Registry System:

Internet Number Registry System: The system for administering Internet Number Resources, whereby the IANA maintains the Number Registries from which the RIRs receive allocations to distribute to the community and the RIRs coordinate with the IANA to correctly register any resources that are returned to the Number Registries. This system is described in detail in RFC 7020.

Internet Number Resources: IP addresses (IPv4, IPv6) and Autonomous System (AS) Numbers.

LACNIC:

National Telecommunications and Information Administration (NTIA):

Number Resource Organization (NRO): a coordinating mechanism of the RIRs to act collectively on matters relating to the interests of the RIRs, established by an MoU between the RIRs.

Number Resource Organization (NRO): The Number Resource Organization (NRO) is a coordinating mechanism of the RIRs to act collectively on matters relating to the interests of the RIRs. It was established in 2003 by a Memorandum of Understanding between the four RIRs in operation at that time (and signed by AFRINIC upon its establishment in 2005). https://nro.net/ <https://nro.net/>

Number Resource Organization Executive Council (NRO EC): a group of appointed representatives of each RIR, normally the CEOs.

Number Resource Organization Executive Council (NRO EC): represents the NRO and its suborganizations in all matters. It is made up of one representative from each RIR, generally the CEO or Director of the RIR. Chairmanship of the NRO EC rotates through each of the RIRs on an annual basis.

Number Resource Organization Memorandum of Understanding (NRO MoU): A Memorandum of Understanding signed in 2003 by the four RIRs in operation at the time, and subsequently signed by AFRINIC in 2005. The MoU established the Number Resource Organization and defines its activities and sub-organizations.

Number Resource Organization Number Council (NRO NC): a body made up of three community members from each RIR community. It acts in an advisory capacity to the NRO Executive Council and to review of any global policy proposal to confirm that the documented RIR PDPs and relevant procedures were followed in its development and approval. In the ICANN structure, the members of the NRO NC serve the functions of the Address Supporting Organization Address Council (ASO AC).

Policy Development Process (PDP): The process within each RIR by which the community makes policies relating to the distribution and registration of Internet number resources within its service region. While these PDPs differ in some specifics, the share common characteristics: all RIR PDPs are open to all and follow an established, bottom-up process of collaboration; all RIR PDPs are transparent in their working methods, utilizing public mailing lists and open community forums; all RIR PDPs reach conclusions by community consensus; and the policies produced by an RIR PDP are made freely and publicly available.

Regional Internet Registry (RIR): The not-for-profit membership-based organizations responsible for the distribution and registration of Internet Number Resources in continent-sized geopolitical regions, as first proposed by the IETF in RFC 1366. The RIRs are an important element in the Internet Number Registry System as defined in RFC 7020. The RIRs were established in a bottom-up fashion and serve a secretariat role for their communities, facilitating the open, inclusive, bottom-up development of number resource policy. There are currently five RIRs in operation, as described in Section 1.B. of this document.

RIPE NCC:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.nro.net/pipermail/crisp/attachments/20150115/6c0268e4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://www.nro.net/pipermail/crisp/attachments/20150115/6c0268e4/signature.asc>