Changes to the Internet Standards Process defined by RFC 2026
draft-carpenter-rfc2026-changes-02

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'Changes to the Internet Standards 
         Process defined by RFC 2026' to BCP 

The IESG has approved the following document:

- 'Changes to the Internet Standards Process defined by RFC 2026 '
   <draft-carpenter-rfc2026-changes-02.txt> as a BCP

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Russ Housley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-carpenter-rfc2026-changes-02.txt

Ballot Text

Technical Summary

  This document defines a number of changes to RFC 2026, which defines
  the IETF standards process.  While some rule changes are included, the
  intention is to preserve the intent of the original rules, while
  adapting them to experience and current practice.  RFC 2026 has been
  in force since 1996, and has proved robust and adequately flexible.
  However, some provisions have led to practical difficulties or deserve
  clarification.  The changes defined here are intended to tackle those
  issues.

Working Group Summary

  This document is not the product of an IETF Working Group.

  There was a major attempt at updating the standards process by the
  NEWTRK WG several years ago, and by other non-WG efforts.  These
  efforts have failed to reach any kind of consensus.  This document
  aims at clearing up relatively minor aspects of the process rules
  without any fundamental change to current practice.  It has been
  discussed on the ietf@ietf.org mail list.

Protocol Quality

  This document was reviewed by Russ Housley for the IESG.

  This document is structured as a set of changes to RFC 2026.  It
  attempts to clarify the IETF rules applied in practice, so in that
  sense it documents running code.

RFC Editor Note