suggestions
Marc Blanchet
Marc.Blanchet@viagenie.qc.ca
Thu, 21 Nov 2002 22:26:55 -0500
--==========1378965387==========
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
I think:
- that presentations tonight gave a pretty good overview of the problem.
- we all know the symptoms.
Here is some humble simple and practical suggestions to help streamline the
IETF process.
I deliberatly avoid to write statements on how to be a good ietf
participant, a good wg chair, a good author, a good AD.
Just sent to drafts directory.
All ideas are my own responsibility and I'm prepared to be shooted.
Marc.
--==========1378965387==========
Content-Type: text/plain; charset=us-ascii;
name="draft-blanchet-ietf-evolutionize-suggestions-00.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="draft-blanchet-ietf-evolutionize-suggestions-00.txt"; size=6784
Internet M. Blanchet
Internet-Draft Viagenie inc.
Expires: May 22, 2003 November 21, 2002
Suggestions to Streamline the IETF Process
draft-blanchet-ietf-evolutionize-suggestions-00
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 22, 2003.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract
This document was made during the presentations of the Atlanta ietf
plenary on the subject of evolutionizing the IETF. The intent is to
suggest solutions based on my own personal view of this situation.
Problems were well described in that plenary IMHO. These are
personal suggestions based on my experience as participant and co-
chair of one wg in IETF. All these considerations and practical
suggestions are mine and feel free to shoot me if I'm wrong. Only
one generic idea in this document: Make better wg preparation before
wg is started will help a lot.
Blanchet Expires May 22, 2003 [Page 1]
Internet-Draft Suggestions to Streamline the IETF Process November 2002
1. Use of keyword
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
2. Considerations and Suggestions
Proposals are numbered in order to pin-point them.
o WG chairs MUST be formed and know the details of the process.
P1: new wg chairs MUST attend to wg chair "course" on their
first IETF as chairs
o WG chairs are sometimes busy with their own life/work.
P2: a wg SHOULD have 2 wg chairs
o WG charters and requirements are not clear at the beginning
P3: before wg is started, the charter AND the requirement
document SHOULD HAVE reached concensus.
o Find concensus transparently and efficiently.
P4: have an online voting tool to help sense concensus on the
wg between ietf. I can commit to help set this up if
concensus.
o Pro-active to see in advance issues related to not your area of
expertise
P5: have area experts (i.e. for each area) pre-assigned to
each wg. They report to the chairs and AD of the wg, not
theirs
o Cultivate transparency.
P6: design teams MUST be avoided.
P7: interim meeting should not happen unless a significant
portion of the wg confirmed presence.
P8: have a formal tracking system to track document comments.
P9: any room concensus MUST use hands not humms. Questions
MUST be written on the screen
Blanchet Expires May 22, 2003 [Page 2]
Internet-Draft Suggestions to Streamline the IETF Process November 2002
o We are a world organization which bridges languages and cultures
and egos
P10: Chairs and proposers MUST write questions/proposals/...
on the screen before any discussion
P11: If a wg chair or AD is an author of a wg doc, he should
find a co-author and have his co-author make presentations.
3. Security Considerations
If we don't streamline the IETF process, we might end up either:
doing too late standards to secure the Internet or pushing bad
unsecure protocols.
4. Acknowledgements
All people that have been involved in the idn working group and
helped me to learn to try to be a wg co-chair. Again, this document
is a humble contribution to help resolve the raised problem.
References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
Author's Address
Marc Blanchet
Viagenie inc.
2875 boul. Laurier, bureau 300
Sainte-Foy, QC G1V 2M2
Canada
Phone: +1 418 656 9254
EMail: Marc.Blanchet@viagenie.qc.ca
URI: http://www.viagenie.qc.ca/
Blanchet Expires May 22, 2003 [Page 3]
Internet-Draft Suggestions to Streamline the IETF Process November 2002
Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Blanchet Expires May 22, 2003 [Page 4]
--==========1378965387==========--