As per Relevance of the word standard, we have this rfc below:
Network Working Group S.
Request for Comments: 2690 Harvard
Category: Informational September 1999
A Proposal for an MOU-Based ICANN 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
1.
This is a copy of the proposal for an MOU-based Protocol
Organization that was submitted to ICANN on April 23, 1999.
2. Cover
This is a copy of the cover letter that was used to submit the
to ICANN
Dear Esther
Enclosed please find a description of a proposed
Support Organization (PSO) for ICANN's consideration.
description is purposefully informal as it is meant to be a basis
discussion and not a final formal legal document
This proposal was developed primarily by using the
Internet Engineering Task Force (IETF) poisson working group
list to discuss successive versions of the proposal. In addition
proposal has benefited from extensive discussion within the IETF'
Internet Engineering Steering Group (IESG) and Internet
Board (IAB). The proposal also benefited from extended
with representatives of the International Telecommunication
(ITU) and the World Wide Web Consortium (W3C).
I look forward to ICANN's evaluation of this proposal and
also looking forward to the MOU development meeting noted in
1.c of the proposal
Bradner Informational [Page 1]
RFC 2690 ICANN PSO Proposal September 1999
3. Proposal for a MOU-based
ICANN Protocol Supporting
1. Definition of the PSO
a. Purpose
The Protocol Support Organization (PSO) will be a consensus
based advisory body within the ICANN framework
b. Components
The PSO will establish a "Protocol Council" and host an
open meeting (known as the "General Assembly" (
below)).
c. Creation through a Memorandum of Understanding
Arrangements regarding the PSO are to be reflected in
Memorandum of Understanding (MOU) among ICANN and a group
open international Internet related standards
organizations (SDOs). SDOs must satisfy a set of
criteria before they can be considered for membership. (
Appendix A) After ICANN has accepted a proposal for an
PSO, including the SDO criteria, a meeting, open to all
that believe they meet the criteria, will be held to
the MOU
All existing MOU signatories must agree to the admission of
signatories. Rejected applicants can appeal to the ICANN
where a 2/3rds majority can override such a rejection if
board finds the SDO meets the criteria
2. The Protocol
a.
The Protocol Council will have up to [12] individual
selected by the SDO signatories of the MOU. (see below
Bradner Informational [Page 2]
RFC 2690 ICANN PSO Proposal September 1999
b.
The term of Protocol Council members will be 2 years.
will be pursuant to procedures established through the MOU
(Initial terms will be 1 and 2 years to provide
conditions for staggered terms.)
c. Powers/Duties of the Protocol
i Appointment of ICANN
The Protocol Council will nominate 3 Directors to the
Board (By-laws, Art. V, Sec. 4(iii)). The initial
would have terms of 1, 2 and 3 years (By-laws, Art. V, Sec
9(d
The Protocol Council will conduct an open call
nominations for any open PSO seats on the ICANN board.
SDO signatory to the MOU is entitled to nominate
by procedures of its own choosing. Additionally
nominations from the public at large should be
under conditions to be defined by the Protocol Council
The Protocol Council will select the PSO nominees to
ICANN board from among these nominees by a means of its
choosing
ii Qualifications of ICANN
No more than 2 PSO-nominated Directors may come from
same geographic region
iii Role of ICANN
The Directors appointed by the Protocol Council will
represent the PSO on the Board, but will function as
Directors of ICANN. (By-laws, Art. V, Sec. 8)
iv Advisory
The Protocol Council will advise the Board of ICANN
matters referred to the Protocol Council by the
Board. As per the ICANN By-laws, only matters relating
the assignment of parameters for Internet protocols
be so referred
Bradner Informational [Page 3]
RFC 2690 ICANN PSO Proposal September 1999
d. Policy
In the tradition of the Internet, standards
policies and conflict resolution mechanisms should be
by those institutions most directly involved, without
interference from centralized bodies
The ICANN By-laws vest in the PSO the primary
for developing and recommending substantive policies in
area of protocol parameter assignment. The PSO is committed
the proposition that policies for parameter assignments
particular protocols are the responsibility of the
SDO that developed the protocol. The Protocol Council will
available as needed by the SDOs to develop policies
procedures for conflict resolution between SDOs. (By-laws,
Art. VI, Sec. 2(b)). Any policies must be adopted by
of all SDOs. The ICANN Board of Directors will take
addition action regarding disputes between SDOs related
protocol assignment or registration
3. Annual Open Meeting (General Assembly
a. Hosting an open
The Protocol Council will periodically host an open
("General Assembly") for promoting discussion and
input regarding the work of the PSO. A General Assembly
will be held at least once per year, and will permit
participation by all interested individuals
The annual open meeting will be held in conjunction with
major meeting of one of the SDOs that have signed the MOU
(with an effort to hold no 2 consecutive meetings in the
geographic region
It is expected that the major SDOs within the Internet
standards development community will provide the
of the General Assembly
b. Selection of Protocol Council
Prior to the annual open meeting, the Protocol Council
make an open call for nominations to the upcoming vacancies
the Protocol Council. Each SDO signatory to the PSO MOU will
entitled to make nominations for some or all of the
seats by a procedure of its own choosing. In the event
there are more nominees than vacancies, an election will
held in which each SDO signatory to the PSO MOU has equal votes
Bradner Informational [Page 4]
RFC 2690 ICANN PSO Proposal September 1999
Protocol Council Members should fairly represent, to the
reasonable, all constituencies within the member SDOs
including the major technical areas and geographical regions
4. Open Proceedings and
a. Communications between ICANN and the
All communications between ICANN and the PSO will be
public on the PSO web site. In the event that ICANN
that a communication be kept confidential, the PSO will
this request for a fixed period of time not to exceed one year
and then make the communication public
b. PSO
All discussions of PSO business will be conducted on
publicly-archived mailing list accessible through the PSO
site. The schedule for the PSO meetings will be posted 90
in advance of the meeting date. The agenda for the
Council and annual open meetings will be posted on the PSO
site at least 30 days before the meetings. The minutes
all PSO meetings will be publicly posted on the PSO web
within 30 days of the meeting
5. Review of
The MOU signatories will periodically review the results
consequences of their cooperation under the MOU. When appropriate
the signatories will consider the need for improvements in the
and make suitable proposals for modifying and updating
arrangements and scope of the MOU
6.
ICANN will officially recognize the PSO described in this memo
the PSO under the ICANN By-laws Art. 6, Sec. 3.
Bradner Informational [Page 5]
RFC 2690 ICANN PSO Proposal September 1999
Appendix A - requirements for consideration as a PSO-qualified
SDOs must be open, international, voluntary technical standard
technical specification development organizations which
1) Develop standards and/or specifications for use over the
Internet
2) Can demonstrate active membership in the IP-related
and/or specification development process of more than 1000
individuals, if individual memberships are used by
organization, or 100 companies, if corporate memberships
used by the organization
3) Has been in operation for 3 or more years at the time of
application
4) Can demonstrate that there is significant deployment of
standards on the Internet
5) The significant protocols controlled by the organization can
implemented without paying a licensing fee to the
Open international voluntary standards bodies are defined
international organizations that plan, develop or
voluntary standards
An organization shall be considered open and international if
standards and/or specifications development process is open to
person or organization of any nationality on equitable terms.
shall be considered voluntary if it makes no claim to compel
of its standards and specifications
In either case, to be considered as 'international', the
(or other "full") membership must include individuals or
primarily located in at least three different regions and at
two different countries within each of those regions
Bradner Informational [Page 6]
RFC 2690 ICANN PSO Proposal September 1999
4. Security
This type of non-protocol document does not directly effect
security of the Internet
5. Editor's
Scott
Harvard
1350 Mass Ave, rm 876
Cambridge,
02138
Phone: +1 617 495 3864
EMail: sob@harvard.
Bradner Informational [Page 7]
RFC 2690 ICANN PSO Proposal September 1999
6. 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 8]
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
