2.2.1 Procedures Update for IETF (pufi)

NOTE: This charter is a snapshot of the 71st IETF Meeting in Philadelphia, PA USA. It may now be out-of-date.

Last Modified: 2008-02-07


Pete Resnick <presnick@qualcomm.com>

General Area Director(s):

Russ Housley <housley@vigilsec.com>

General Area Advisor:

Russ Housley <housley@vigilsec.com>

Mailing Lists:

General Discussion:
To Subscribe:

Description of Working Group:

The recent IETF Last Call for draft-carpenter-rfc2026-changes has
shown that many people active in the IETF community are wary of
changing the IETF procedures without a very thorough discussion. Yet,
the POISED WG and the NEWTRK WG efforts showed that it is indeed
difficult to craft new procedures and then obtain IETF consensus for

While there does not appear to be consensus to adopt all of the
changes in draft-carpenter-rfc2026-changes, there does appear to be
support for some of the changes. The objective of this BOF is to
determine which of the proposed changes have broad community support.
The intent is to generate a document that can be easily approved as
an update to RFC 2026 that contains only the proposed changes with
broad community support.

This BOF is not intended to form an IETF WG.

Goals and Milestones:

No Current Internet-Drafts

No Request For Comments

Meeting Minutes


PUFI - Main slides