As per Relevance of the word organization, we have this rfc below:
Network Working Group S.
Request for Comments: 2691 Harvard
Category: Informational September 1999
A Memorandum of Understanding for an
Protocol Support
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This is the text of the Memorandum of Understanding (MoU) that
signed by ICANN, the IETF, the ITU-T, W3C and ETSI on July 14, 1999
in Oslo. This MoU creates the Protocol Support Organization (PSO
within the Internet Corporation for Assigned Names and
(ICANN). This MoU was developed by representatives of the IETF, ITU
W3C, ETSI, and ICANN with the help of Jorge Contreras of Hale
Dorr
MEMORANDUM OF
July 14, 1999
ICANN Protocol Supporting
(1) Purpose and
(a) The Protocol Support Organization (PSO) will be a consensus
based advisory body within the ICANN framework
(b) The PSO will establish a "Protocol Council" and host
annual open meeting (the "General Assembly").
(c) The purpose of this Memorandum of Understanding (MOU) is
establish a set of principles that ICANN and the
Development Organizations who have signed below (the
SDOs) will use in forming and operating the
Bradner Informational [Page 1]
RFC 2691 MoU for an ICANN PSO September 1999
(2) Composition and Action of Protocol
(a) Size. Each Signing SDO will appoint two (2) members to
Protocol Council, each such member to serve for a time
determined by such Signing SDO
(b) Each Signing SDO shall be responsible for choosing
members of the Protocol Council in a manner of its
choosing, and in accordance with its own open procedures
Each Signing SDO may remove or replace one or both of
members on the Protocol Council in its discretion.
Signing SDO must notify the Protocol Council Secretary
ICANN when it changes its members and, in addition,
ratify its choices at least annually
(c) Selection and Appointment. Concurrently with the posting
notice of the date of the annual meeting of the PSO
Assembly on the PSO Web Site, ICANN and the Protocol
shall make an open call for nominations to any
vacancies on the Protocol Council. Any nominations
will be forwarded to the Signing SDOs eligible to
members (i.e., they do not already have two members on
Protocol Council) for their consideration
(d) Action by Protocol Council. Unless otherwise specified
this MOU, all actions of the Protocol Council shall be
by majority vote of the total number of members. Action
be taken at any meeting of the Protocol Council, which may
by telephone conference in which all participants can
the others. Meetings of the Protocol Council may be
by request of any three members of the Protocol Council,
at least 45 days for physical meetings or fifteen (15)
for telephonic or other electronic meetings prior
notice to each of the other members. In order to
business at any meeting of the Protocol Council, at least
quorum of members must be present; a quorum shall be
when at least majority of the members of the Protocol
are present, and when such members represent at least 3/4
of the Signing SDOs
(e) Web Site. The Protocol Council will arrange for
establishment and maintenance of a Web site devoted to
activities and news
(f) Secretary. The Protocol Council will have a Secretary
coordinate administrative matters relating to the PSO
Protocol Council. The Secretary's term of office shall
one year. The position of Secretary will rotate among
Bradner Informational [Page 2]
RFC 2691 MoU for an ICANN PSO September 1999
Signing SDOs, with the initial Secretary to be selected
the IETF, and subsequent Secretaries to be appointed by
randomly selected Signing SDO that has not appointed
Secretary in the current rotation
(g) No Compensation. Neither the Secretary, nor any
Council member or designated ICANN Board member shall
entitled to any compensation or reimbursement of
from the PSO. The PSO shall not be required to
insurance coverage for, or to indemnify, the members of
Protocol Council or persons acting in any other capacity
or for the PSO
(3) ICANN
(a) The Protocol Council will appoint Directors to the
Board of Directors in accordance with the By-laws of ICANN
for such terms as are specified by such By-laws. ICANN
notify the Protocol Council of any vacancies on the
Board which may be filled by the Protocol Council
(b) The Protocol Council will conduct an open call
nominations for any open PSO seats on the ICANN Board.
Signing SDO is entitled to nominate candidates by
of its own choosing. Additionally, nominations from
public at large will be allowed under conditions to
defined by the Protocol Council. The Protocol Council
select the PSO nominees to the ICANN Board from among
nominees. ICANN Directors selected by the Protocol
may, but need not, be members of the Protocol Council or
SDO
(c) No more than 2 PSO-nominated Directors may be residents
the same Geographic Region (as defined in the ICANN By-laws).
(d) The ICANN Directors appointed by the Protocol Council
not represent the PSO on the ICANN Board, but will
as full Directors of ICANN
(4) Duties of Protocol
(a) Advisory Role. The Protocol Council will advise the
Board on matters referred to the Protocol Council by
ICANN Board relating to the assignment of parameters
Internet protocols
Bradner Informational [Page 3]
RFC 2691 MoU for an ICANN PSO September 1999
(b) Policy
(i) In the tradition of the Internet, standards
policies and conflict resolution mechanisms should
created and utilized by those institutions
directly involved, without undue interference
centralized bodies
(ii) The ICANN By-laws vest in the PSO the
responsibility for developing and
substantive policies in the area of protocol
assignment
(iii) The PSO is committed to the proposition that
for parameter assignments for particular protocols
the responsibility of the individual Signing SDO
developed the protocol
(iv) The Protocol Council, and, when requested, ICANN,
be available as needed by the Signing SDOs to
policies and procedures for conflict resolution
Signing SDOs
(v) Any such policies and procedures will be adopted
with the agreement of all SDOs
(5) Annual Open
(a) The Protocol Council will periodically convene an
meeting ("General Assembly") for promoting discussion
receiving input regarding the work of the PSO
(b) A General Assembly will be held at least once per year,
will permit open participation by all interested individuals
(c) Each annual General Assembly will be hosted by a Signing
in conjunction with one of its major meetings, as
by the Protocol Council (with an effort to hold no 2
consecutive General Assemblies in the same
Region.)
(d) It is expected that the major organizations within
Internet protocol standards development community
provide the constituency of the General Assembly
(6) Open Proceedings and
(a) Communications between ICANN and the Protocol Council.
official communications between ICANN and the
Council will be made public on the PSO web site. In
event that ICANN requests that a communication be
Bradner Informational [Page 4]
RFC 2691 MoU for an ICANN PSO September 1999
confidential, the Protocol Council will honor this
for a fixed period of time not to exceed one year, and
make the communication public
(b) Protocol Council Proceedings. All meetings of the
Council and official discussions of Protocol Council
will be conducted or reported on a publicly-archived
list accessible through the PSO web site
(c) Meeting Announcements. The schedule and agenda for the
General Assembly will be posted on the PSO Web Site at
90 days in advance of the meeting date. Notice of
Council meetings will be posted on the PSO Web at least 45
days before each physical meeting or fifteen (15) days
any telephonic or other electronic meeting, or such
time period agreed upon by each of the Signing SDOs.
minutes from all PSO meetings will be publicly posted on
PSO web site within 30 days of the meeting
(7) Review and Modification of MOU. ICANN and the Signing SDOs
periodically review the results and consequences of
cooperation under this MOU. When appropriate, the
will consider the need for improvements in the MOU and
suitable proposals for modifying and updating the
and scope of the MOU. Any modification to the MOU must
approved by all signatories
(8) Standards Development
(a) The initial signatories to this MOU shall include ICANN
the Signing SDOs who have signed below. Each Signing
must be an international, Internet-related
development organization that establishes that it meets
criteria for SDOs set forth below
(i) SDOs must be open, international, voluntary
standard and technical specification
organizations which
(A) Develop standards and/or specifications for
over the public Internet
(B) Can demonstrate active membership in the IP-
standards and/or specification development
of more than 800 individuals, if
memberships are used by the organization, or 80
companies, if corporate memberships are used by
organization
Bradner Informational [Page 5]
RFC 2691 MoU for an ICANN PSO September 1999
(C) Has been in operation for 3 or more years at
time of their application
(D) Can demonstrate that there is
deployment of its standards on the Internet
(E) The significant protocols controlled by
organization can be implemented without paying
licensing fee to the organization
(ii) Open, international, voluntary standards
are defined as international organizations that plan
develop or establish voluntary standards.
organization shall be considered open and
if its standards and/or specifications
process is open to any person or organization of
nationality on equitable terms. An organization
be considered voluntary if it makes no claim to
use of its standards and specifications. Additionally
to be considered 'international', an organization'
voting (or other "full") membership must
individuals or companies primarily located in at
three different Geographic Regions and at least
different countries within each of those
Regions
(b) New
(i) Any organization that believes it satisfies the
qualifications set forth above may apply in writing
the Protocol Council to become a party to this MOU
In order for an organization to become a party to
MOU, all then-existing MOU signatories must agree
such organization qualifies as an SDO
(ii) Rejected applicants can appeal to the ICANN Board
which may override such a rejection if the ICANN
finds, by at least a two-thirds vote, that
organization meets the SDO criteria set forth above
(iii) Any organization that is accepted as an SDO under
MOU must execute a copy of this MOU, and agree to
bound by all of its terms and conditions, upon which
shall be considered a Signing SDO for all
under this MOU
Bradner Informational [Page 6]
RFC 2691 MoU for an ICANN PSO September 1999
(9) General. This MOU does not constitute any of the parties
a partner, joint venture, agent, principal or franchisee
any other party. The waiver of any provision of this MOU
any occasion shall not constitute a waiver for purposes
any other occasion. No party may transfer or assign
interest, right or obligation arising under this MOU
the prior written consent of each other party to this MOU
IN WITNESS WHEREOF, this Memorandum of Understanding is
this 14 day of July 1999 by the undersigned, acting through
duly authorized representatives
INTERNET CORPORATION FOR ASSIGNED NAMES AND
By: (signature
Name: Michael W.
Title: Interim President /
INTERNET ENGINEERING TASK
By: (signature
Name: Fredrick J.
Title: Chair,
INTERNATIONAL TELECOMMUNATIONS
By: (signature
Name: Houlin Zhao, on behalf of Secretary-General of
Title: Director,
WORLD WIDE WEB
By: (signature
Name: Henrik Frystyk
Title: HTTP Activity
EUROPEAN TELECOMMUNICATIONS STANDARDS
By: (signature
Name: Bridget
Title: Deputy Director
Bradner Informational [Page 7]
RFC 2691 MoU for an ICANN PSO September 1999
Security
This type of non-protocol document does not directly effect
security of the Internet
Editor's
Scott
Harvard
1350 Mass Ave, rm 876
Cambridge,
02138
Phone: +1 617 495 3864
EMail: sob@harvard.
Bradner Informational [Page 8]
RFC 2691 MoU for an ICANN PSO September 1999
Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Bradner Informational [Page 9]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
