Escape Clause

[[e-mail]]

Hi.

At the Danvers IETF meeting i promised to draft an "escape clause" to
allow a way out of deadlocks or other problems we may get into by following
our written rules.  Here is a rough draft.  Suggestions please.

--jon.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


INTERNET DRAFT
                                                               J. Postel
                                                                     ISI
                                                               June 1995

                             Escape Clause

Status of this Memo

   This document describes a modification to the IETF procedures to
   allow an escape from a situation where the existing procedures are
   not working or do not seem to apply.  This is a modification to the
   procedures of RFC 1602 and 1603.

   This document is an Internet Draft. 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. Internet Drafts may be updated, replaced, or obsoleted by
   other documents at any time. It is not appropriate to use Internet
   Drafts as reference material or to cite them other than as a "working
   draft" or "work in progress".

Introduction

   The current IETF procedures are documented in "The Internet Standards
   Process -- Revision 2" [1], and "IETF Working Group Guidelines and
   Procedures" [2].

   There may be situations where following the procedures leads to a
   deadlock, or there may be situations where the procedures provide no
   guidance.  This these cases it may be appropriate to invoke the
   escape procedure described below.

Discussion

   Any escape from following the written rules must be a public process
   with opportunity for all concerned parties to comment.

   The escape procedure should be similar to existing mechanisms and
   involve existing bodies.








Expiration Date: December 1995                                  [Page 1]

INTERNET DRAFT               Escape Clause                     June 1995


The Escape Procedure

   When the IESG has determined that there is in a situation where the
   existing written rules do not apply or lead to a deadlock, the IESG
   may ask the IAB to conduct a Review of the matter and to either (1)
   decide the matter, or (2) define a procedure for resolving the
   matter.

   Any such IAB Review must include a public meeting where any
   interested individual can make a brief statement to the IAB regarding
   his concerns in the matter.  Such a public meeting must be announced
   with at least thirty (30) days notice on the IETF announcements
   mailing list.  Such a public meeting may be conducted as part of an
   IETF meeting.

   The IAB shall announce its findings and decision on the matter within
   thirty (30) days of the public meeting.  The decision will be
   reported on the IETF announcements mailing list, and should also
   appear in the IAB minutes, and the Internet Monthly Report.

References

   [1] IAB, and IESG, "Internet Standards Process -- Revision 2", RFC
       1602, IAB and IESG, March 1994.

   [2] Huizer, E., and D. Crocker, "IETF Working Group Guidelines and
       Procedures", RFC 1603, SURFnet and Silicon Graphics, Inc., March
       1994.

Security Considerations

   Security issues are not discussed in this memo.

Author's Addresses

      Jon Postel
      USC - ISI, Suite 1001
      4676 Admiralty Way
      Marina del Rey, CA  90292-6695
      Phone: [phone]
      email: [e-mail]










Expiration Date: December 1995                                  [Page 2]


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~