![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Some notes on a couple of your points.....
--On 25. oktober 2005 08:48 -0400 John C Klensin <john-ietf at jck.com> wrote:
----------------------- Addendum: Examples of why this team needs to be considered as an extraordinary procedure, created by extraordinary procedures and without clear community consent, and cannot be considered as an "ordinary design team"....
In no particular order...
(1) Design teams tend to self-constitute although they can be selected. When they are selected by a WG Chair or AD, the membership criteria are usually clear and then followed. In this case, membership selection was filtered based, in part, on the participants not being an activist and, specifically, not having current drafts for reform. Yet the organizer has a reform draft, and is generating new versions of it, and is an exception. (20050923)
(3) The "team" is expected to report at the Plenary, partially on the basis of its BOF meeting, but the BOF ends only one 50-minute break before the plenary. Not exactly time for the team to meet, carefully consider the discussion at the BOF, and prepare a report. Indeed, while it is reasonable to hope for something else, this would appear to be a setup for the "well, we just got a lot of input and are thinking about it, stay tuned" reports that characterized the admin restructuring process.
Speaking only as a PESCI member.
Attachment:
pgpDi3SR2xCJg.pgp
Description: PGP signature
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.