agenda for newtrk BOF

sob@harvard.edu (Scott Bradner) Wed, 12 November 2003 15:49 UTC

Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23305 for <ietf-web-archive@odin.ietf.org>; Wed, 12 Nov 2003 10:49:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AJx33-0005vt-Lq for ietf-list@asgard.ietf.org; Wed, 12 Nov 2003 10:36:49 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AJwv7-0005pS-Qf for ietf@asgard.ietf.org; Wed, 12 Nov 2003 10:28:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22035 for <ietf@ietf.org>; Wed, 12 Nov 2003 10:28:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJwv6-0000KT-00 for ietf@ietf.org; Wed, 12 Nov 2003 10:28:36 -0500
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev) by ietf-mx with esmtp (Exim 4.12) id 1AJwv6-0000Jt-00 for ietf@ietf.org; Wed, 12 Nov 2003 10:28:36 -0500
Received: by newdev (Postfix, from userid 501) id 7B8F77539D; Wed, 12 Nov 2003 10:28:00 -0500 (EST)
To: ietf@ietf.org, problem-statement.alvestrand.no@harvard.edu, solutions.alvestrand.no@harvard.edu
Subject: agenda for newtrk BOF
Message-Id: <20031112152800.7B8F77539D@newdev>
Date: Wed, 12 Nov 2003 10:28:00 -0500
From: sob@harvard.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

THURSDAY, November 13, 2003
1530-1730 Afternoon Sessions II
Salon C
GEN	newtrk	New IETF Standards Track Discussion BOF *


------
CHAIRS: Scott Bradner <sob@harvard.edu>	

DESCRIPTION:
The consensus in the problem working group is that the current IETF 3-
stage standards track described in RFC 2026 [RFC2026] is not working as
originally intended.  The draft problem statement document says:

     "The current hierarchy of Proposed, Draft and Full Standard
     maturity levels for specifications is no longer being used in the
     way that was envisioned when the stratification was originally
     proposed.  In practice, the IETF currently has a one-step
     standards process that subverts the IETF's preference for
     demonstrating effectiveness through running code in multiple
     interoperable implementations and compresses the process that
     previously allowed specifications to mature as experience was
     gained with actual implementations:"

The draft document then goes on to list 4 observations:

  1/ few documents actually progress after being published as PS
  2/ there is a perception that the IESG raised the quality requirement
  3/ in spite of the raised quality requirement, running code is not
     required
  4/ there seems to be a reinforcing feedback loop involved: vendors
     implement and deploy PS documents so the IESG tries to make the PS
     documents better

The draft problem document concludes that the 3-stage process is
excessive.

This BOF will discuss the observation that the current IETF 3-stage
standards track is not working and discuss options for different standards
track processes.

Expected output of BOF:
        1/ criteria for declaring "success" for a new IETF standards track
        2/ next steps

AGENDA:

  1/ description of current IETF Standards Track
  2/ observations from problem working group
  3/ what other SDOs do
  4/ proposals for alternate standards track processes
  5/ what would define success in a revised IETF Standards track
  6/ open discussion

Reading List:
        draft-ietf-problem-issue-statement-04.txt
        draft-dawkins-pstmt-twostage-01.txt
        draft-bradner-ietf-stds-trk-00.txt
        draft-iesg-hardie-outline-00.txt
        draft-loughney-what-standards-00.txt