All,

  FYI.

Regards,

--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail [EMAIL PROTECTED]
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208




this is the latest version of the draft -

I've made modifications based on the discussion on the
poised list and based on input from the ITU & W3C

I expect the most significant change is the removal of
the requirement for "free" access to standards - this was a hotly
debated point on the poised list but I'm taking the view that
Paul Hoffman expressed as making the most sense

> When I wrote my piece on the high cost of ITU specs the other day, I did so
> with the attitude of "they shouldn't be allowed in if they charge for
> specs". I have now changed my mind, and think that "they should be allowed
> in <grumble>". I agree with the folks who have pointed out that, as much as
> we would like to force the ITU into our mold, this is not the place to do that

> Just because we're the ones writing this document, doesn't mean that we
> should use that fact to hurt or exclude someone else. We can do things our
> way without forcing our way on others. Heck, we might even show kindness to
> other groups who still don't get it.

there have been a number of formatting changes and some text
on openness added as well as a number of other smaller changes

To meet ICANN's timetable for their next meeting a proposal must
be submitted to them this week.

Scott

-----------
        DRAFT --- DRAFT --- DRAFT --- DRAFT --- DRAFT --- DRAFT

                          April 20 1999

                Protocol Supporting Organization


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 annual
        open meeting (known as the "General Assembly" (described below)).


 c.     Creation through a Memorandum of Understanding
        Arrangements regarding the PSO are to be reflected in a
        Memorandum of Understanding (MOU) among ICANN and a group of
        open international Internet related standards development
        organizations (SDOs). SDOs must satisfy a set of objective
        criteria before they can be considered for membership.
        (see Appendix A)

        The initial signatories of the MOU are expected to be ICANN,
        IETF, the ITU and W3C. All existing signatories must agree to the
        admission of new signatories.

2.      The Protocol Council

 a.     Members.
        The Protocol Council will have up to [12] individual
        members selected by the SDO signatories of the MOU. (see below)

 b.     Term.
        The term of Protocol Council members will be 2 years.
        Removal will be pursuant to procedures established through the
        MOU. (Initial terms will be 1 and 2 years to provide
        initial conditions for staggered terms.)

 c.     Powers/Duties of the Protocol Council.

  i     Appointment of ICANN Directors.
        The Protocol Council will nominate 3 Directors to the ICANN
        Board (By-laws, Art. V, Sec. 4(iii)). The initial directors
        would have terms of 1, 2 and 3 years  (By-laws, Art. V, Sec. 9(d)

        The Protocol Council will conduct an open call for nominations
        for any open PSO seats on the ICANN board. Each SDO signatory
        to the MOU is entitled to nominate candidates by procedures
        of its own choosing. Additionally, nominations from the public
        at large should be allowed under conditions to be defined
        by the Protocol Council.

        The Protocol Council will select the PSO nominees to the ICANN
        board from among these nominees by a means of its own choosing.

  ii    Qualifications of ICANN Directors
        No more than 2 PSO-nominated Directors may come from the same
        geographic region.

  iii   Role of ICANN Directors
        The Directors appointed by the Protocol Council will not
        represent the PSO on the Board, but will function as full
        Directors of ICANN. (By-laws, Art. V, Sec. 8)


  iv    Advisory Role.  The Protocol Council will advise the Board of
        ICANN on matters referred to the Protocol Council by the
        ICANN Board.  As per the ICANN By-laws, only matters relating
        to the assignment of parameters for Internet protocols would be
        so referred.

 d.     Policy Development.  The ICANN By-laws vest in the Protocol
        Council the primary responsibility for developing and
        recommending substantive policies in the area of protocol
        parameter assignment. Since the specific policies for
        parameter assignment for particular protocols are the
        responsibility of the SDO that developed the related
        protocol, the Protocol Council will only have the
        responsibility to develop and recommend related substantive
        policies for the specific case where additional cooperative
        initiatives are required (e.g., in the case of a conflict)
        and resolution cannot be arranged through bilateral discussions
        between SDOs.

        As recognized in the U.S. Departmant of Commerce White Paper,
        "The Internet succeeds in great measure because it is a
        decentralized system that encourages innovation and maximizes
        individual freedom."  Therefore, in the tradition of the
        Internet, conflict resolution mechanisms in which the involved
        parties work things out themselves will be preferred to
        mechanisms requiring third-party intervention

3.      Annual Open Meeting (General Assembly)

 a.     The Protocol Council will periodically host an open meeting
        ("General Assembly") for promoting discussion and receiving
        input regarding the work of the PSO.  A General Assembly
        meeting will be held at least once per year, and will permit
        open participation by all interested individuals.

        The annual open meeting will be held in conjunction with a major
        meeting of one of the SDOs that have signed the MOU. (with an effort
        to hold no 2 consecutive meetings in the same geographic region.

        It is expected that the major SDOs within the Internet protocol
        standards development community will provide the constituency
        of the General Assembly.

  b.    Selection of Protocol Council Members.

        Prior to the annual open meeting, the Protocol Council
        shall make an open call for nominations to the upcoming
        vacancies in the Protocol Council. Each SDO signatory to the
        PSO MOU will be entitled to make nominations for some or all of
        the vacant seats by a procedure of its own choosing. In the
        event that there are more nominees than vacancies, an election
        will be held in which each SDO signatory to the PSO MOU has
        equal votes.

        Protocol Council Members should fairly represent,
        to the extent reasonable, all constituencies within the member
        SDOs, including the major technical areas and geographical
        regions.


4.      Open Proceedings and Documents

  a.    Communications between ICANN and the PSO
        All communications between ICANN and the PSO will be made public
        on the PSO web site.  In the event that ICANN requests that a
        communication be kept confidential, the PSO will honor this
        request for a fixed period of time not to exceed one year,
        and then make the communication public.

  b.    PSO Proceedings
        All discussions of PSO business will be conducted on a
        publicly-archived mailing list accessible through the PSO
        web site.  The schedule for the PSO meetings will be posted
        90 days in advance of the meeting date.  The agenda for the
        Protocol Council and annual open meetings will be posted
        on the PSO web site at least 30 days before the meetings.
        The minutes from all PSO meetings will be publicly posted
        on the PSO web site within 30 days of the meeting.


5.      Review of MOU.

        The MOU signatories will periodically review the results and
        consequences of their cooperation under the MOU.  When
        appropriate, the signatories will consider the need for
        improvements in the MOU and make suitable proposals for
        modifying and updating the arrangements and scope of the MOU

6.      Recognition.

        ICANN will officially recognize the PSO described in this
        memo as the PSO under the ICANN By-laws Art. 6, Sec. 3.


Appendix A - requirements for consideration as a PSO-qualified SDO

  SDOs must be open, international, voluntary technical standard
  and technical specification development organizations which:

        1) Develop standards and/or specifications for use over the
           public Internet.


        2) Can demonstrate active membership in the IP-related
           standards and/or specification development process of
           more than 1000 individuals, if individual memberships are
           used by the organization, or 100 companies, if corporate
           memberships are used by the organization.

        3) Has been in operation for 3 or more years at the time of
           their application.

        4) Can demonstrate that there is significant deployment of
           its standards on the Internet.

        5) The significant protocols controlled by the organization
           can be implemented without paying a licensing fee to the
           organization


        Open international voluntary standards bodies are defined as
        international organizations that plan, develop or establish
        voluntary standards.

        An organization shall be considered open and international
        if its standards and/or specifications development process is
        open to any person or organization of any nationality on
        equitable terms. It shall be considered voluntary if it makes
        no claim to compel use of its standards and specifications. 



Reply via email to