Protocol Action: IETF Standards Process Documents to BCP

The IESG <iesg-secretary@CNRI.Reston.VA.US> Tue, 09 July 1996 18:03 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19471; 9 Jul 96 14:03 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19456; 9 Jul 96 14:03 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa17590; 9 Jul 96 14:03 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19423; 9 Jul 96 14:03 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19222; 9 Jul 96 13:58 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa17385; 9 Jul 96 13:58 EDT
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa19210; 9 Jul 96 13:58 EDT
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: poised@tis.com
X-Orig-Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: The IESG <iesg-secretary@CNRI.Reston.VA.US>
Subject: Protocol Action: IETF Standards Process Documents to BCP
Date: Tue, 09 Jul 1996 13:58:22 -0400
X-Orig-Sender: scoya@CNRI.Reston.VA.US
Message-ID: <9607091358.aa19210@IETF.CNRI.Reston.VA.US>

This action was reported by Fred Baker during the opening session of the IETF
Meeting in Montreal.


  The IESG has approved the the following Internet-Drafts for
  publication as Best Current Practices RFCs:

  1. The Internet Standards Process -- Revision 3: a proposed revision
     of part of RFC 1602
	<draft-ietf-poised95-std-proc-3-06.txt>

  2. IAB and IESG Selection, Confirmation, and Recall Process:
     Operation of the Nominating and Recall Committees
	<draft-ietf-poised95-nomcom-05.txt>

  3. The Organizations Involved in the IETF Standards Process
	<draft-ietf-poised95-ietf-orgs-03.txt>


  The IESG also approved the Internet-Draft IETF-ISOC Relationship
  <draft-ietf-poised95-isoc-03.txt> for publication as an Informational
  RFC.


  These documents are the product of the Process for Organization of
  Internet Standards '95 (Poised95) Working Group. The IESG contact
  person is Fred Baker.

=========================================================================
  1. The Internet Standards Process -- Revision 3: a proposed revision
     of part of RFC 1602
	<draft-ietf-poised95-std-proc-3-06.txt>

Technical Summary

 In the words of the document:

   The Internet Standards Process described in this document is
   concerned with all protocols, procedures, and conventions that are
   used in or by the Internet, whether or not they are part of the
   TCP/IP protocol suite.  In the case of protocols developed and/or
   standardized by non-Internet organizations, however, the Internet
   Standards Process normally applies to the application of the protocol
   or procedure in the Internet context, not to the specification of the
   protocol itself.

   ...

   The goals of the Internet Standards Process are:

   o  technical excellence;
   o  prior implementation and testing;
   o  clear, concise, and easily understood documentation;
   o  openness and fairness;  and
   o  timeliness.

   The procedures described in this document are designed to be fair,
   open, and objective;  to reflect existing (proven) practice;  and to
   be flexible.

  The community needs this document because it spells out the way we
  develop standards, the steps along the way, and the ways disagreements
  and intellectual property rights are handled.

Working Group Summary

  To say that the POISED process was without significant debate would
  be ludicrous. However, there are no outstanding issues (to this
  reviewer's knowledge) that remain under debate - the text seems to
  satisfy the concerns of those who have taken part in the discussion.

  This represents a major revision from its predecessor. Changes in
  content are primarily in the appeals process and the handling of
  intellectual property rights. Unlike the first document, which was
  published without testing, the current document's procedures have
  been tested in that we have been operating on them for some period of
  time, and have achieved better results with these procedures than
  with the predecessor document.

  There were no last call comments.

Protocol Quality

  The specification was reviewed by Fred Baker, in his role as IETF
  Chair. Several IAB and IESG members contributed significantly to the
  discussion in the working group, and Scott Bradner authored it. To
  the reviewer's knowledge, there is but one implementation, and it is
  not clear that the implementation always interoperates with itself.
  However, at the present time, the community consensus is that this is
  the best we can do.

=========================================================================
  2. IAB and IESG Selection, Confirmation, and Recall Process:
     Operation of the Nominating and Recall Committees
	<draft-ietf-poised95-nomcom-05.txt>

Technical Summary

  In the words of the document:

   The process by which the members of the IAB and IESG are selected,
   confirmed, and recalled has been exercised four times since its formal
   creation.  The evolution of the process has relied principally on oral
   tradition as a means by which the lessons learned could be passed on to
   successive committees.  This document is a self-consistent, organized
   compilation of the process as it is known today.

Working Group Summary

  There was quite a bit of debate on the POISED list and in meetings
  about this document. However, the specifics that it imposes were
  agreed among the working group, and there are no outstanding issues
  to my knowledge that would require documentary changes.

  There were no last call comments.

Protocol Quality

  The specification was reviewed by Fred Baker, in his role as IETF
  Chair. Several IAB and IESG members contributed significantly to the
  discussion in the working group. As noted in the document, the
  Nominating Committee process has now operated four times, each time
  with a different internal mechanism. This document distills those
  truths learned in the process and passed along by the chairs of those
  committees.

=========================================================================
  3. The Organizations Involved in the IETF Standards Process
	<draft-ietf-poised95-ietf-orgs-03.txt>


Technical Summary

  This document lists the organizations involved in the standards
  process and the roles of certain key contributors (such as the IETF
  Executive Director, the Working Group Chair and Document Editor).

Working Group Summary

  I believe that this document was not heavily contested.

  There was a grand total of one last call comment, that being from
  this reviewer. It asked for a minor reorganization of the material to
  improve document utility.

Protocol Quality

  The specification was reviewed by Fred Baker, in his role as IETF
  Chair. Several IAB and IESG members contributed significantly to the
  discussion in the working group, and Scott Bradner do-authored this
  document. To the reviewer's knowledge, there is but one