[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I-D ACTION:draft-ietf-poisson-appts-01.txt
- To: "A.M. Rutkowski" <amr@chaos.com>
- Subject: Re: I-D ACTION:draft-ietf-poisson-appts-01.txt
- From: jeff Williams <jwkckid1@ix.netcom.com>
- Date: Mon, 08 Mar 1999 10:35:08 +0000
- CC: poised@portal.gw.tislabs.com, IFWP Discussion List <list@ifwp.org>, "domain-open-rsc.org" <domain-policy@open-rsc.org>, ICANN Comments <Comments@icann.org>, "etrigar@teleline.es" <etrigar@teleline.es>, "edyson@edventure.com" <edyson@edventure.com>, "mmr@darwin.ptvy.ca.us" <mmr@darwin.ptvy.ca.us>, "linda_wilson@radcliffe.edu" <linda_wilson@radcliffe.edu>, "junsec@wide.ad.jp" <junsec@wide.ad.jp>, "gregcrew@iaccess.com.au" <gregcrew@iaccess.com.au>, "geraldine.capdeboscq@bull.fr" <geraldine.capdeboscq@bull.fr>, "gconrades@polarisventures.com" <gconrades@polarisventures.com>, "fitzsimmon@dnb.com" <fitzsimmon@dnb.com>, "gconrades@icann.org" <gconrades@icann.org>, "gregcrew@icann.org" <gregcrew@icann.org>, "roberts@icann.org" <roberts@icann.org>, ICANN SO comments <comment-so@icann.org>, "emaxwell@doc.gov" <emaxwell@doc.gov>, "bburr@ntia.doc.gov" <bburr@ntia.doc.gov>
- Organization: INEGroup INC.
- References: <4.2.0.25.19990308090909.00b0e9d0@mail.netmagic.com>
- Sender: owner-comment-so@zephyr.isi.edu
Tony and all,
Good points and questions here Tony. I made some similar queries
as well along this same lines. It appears that the IETF PSO
proposal will be more of a dictatorial type of proposal instead
of complying with the White Paper and the ICANN/NTIA/MoU
requirements.
A.M. Rutkowski wrote:
> > Title : Procedures for IETF appointments to the
> > Protocol Supporting Organization
>
> 1. What currently defines the current attributes of the
> Protocol Supporting Organization as adopted or proffered
> to ICANN? There is no indication that ICANN has done
> anything regarding a PSO.
>
> 2. "This memo describes the procedures by which the IETF appoints
> representatives to the various bodies of the Internet
> Corporation for Assigned Names and Numbers (ICANN) and to
> the Protocol Supporting Organization (PSO) related to ICANN.
>
> What other bodies are involved than the PSO? Isn't the PSO
> *a part of ICANN* rather than "related to?"
>
> 3. Sections 1 and 2 make reference to a "PSO Board." What is
> this? Where is it defined or described? There is nothing in
> the ICANN Bylaws that speaks to the creation of such a body.
>
> 4. Section 4 makes reference to the Protocol Council and its
> responsibilities. It might be useful to quote from the ICANN
> Bylaws:
>
> The Protocol Supporting Organization shall create a
> Protocol Council to make recommendations regarding
> the operation, assignment and management of protocol
> parameters, such as port numbers, enterprise numbers,
> other technical parameters and related subjects.
>
> 5. "The number of persons and their terms will be defined
> by the by laws of ICANN and the PSO. However, in normal..."
> It's repeated again in the subsequent paragraph. Isn't
> "laws" somewhat aggrandized?
>
> 6. "The IETF nominees for the Protocol Council shall be
> the thirteen current voting members of the IAB."
>
> This seems rather autocratic in nature. Why not establish
> a more democratic and more flexible alternative?
>
> 7. I refuse to acknowledge or comply with the copyright assertion
> of the document.
>
> --tony
Regards,
--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208