Re: Process for Process Change

To: "Ash, Gerald R (Jerry), ALABS" <gash at att.com>
Subject: Re: Process for Process Change
From: Sam Hartman <hartmans-ietf at mit.edu>
Date: Thu, 17 Nov 2005 13:35:26 -0500
Cc: ietf at ietf.org
In-reply-to: <9473683187ADC049A855ED2DA739ABCA09FA969B@KCCLUST06EVS1.ugd.att.com> (Gerald R. ALABS Ash's message of "Thu, 17 Nov 2005 07:34:21 -0600")
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF-Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
References: <9473683187ADC049A855ED2DA739ABCA09FA969B@KCCLUST06EVS1.ugd.att.com>
Sender: ietf-bounces at ietf.org
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

We do have a process for process change.  We can approve a BCP using
the procedure outlined in RFC 2026.

When we can get a strong consensus behind a process change, that
procedure works reasonably well.

There are other cases where it doesn't work well.  Some of us think
that's OK; some of us don't.

--Sam


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Follow-Ups:
- Re: Process for Process Change
  - From: Spencer Dawkins

References:
- Process for Process Change (Was Diagrams ((Was RFCs should be distributed in XML))
  - From: Ash, Gerald R \(Jerry\), ALABS

Prev by Date: Re: Diagrams
Next by Date: RE: Diagrams
Previous by thread: Process for Process Change (Was Diagrams ((Was RFCs should be distributed in XML))
Next by thread: Re: Process for Process Change
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Process for Process Change

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.