Re: design teams (was Re: v 1.2, IETF material)
Dave Crocker <dcrocker@mordor.stanford.edu> Wed, 02 December 1992 15:14 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05051; 2 Dec 92 10:14 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05042; 2 Dec 92 10:14 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa11015; 2 Dec 92 10:15 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05023; 2 Dec 92 10:13 EST
Received: from Mordor.Stanford.EDU by CNRI.Reston.VA.US id aa10986; 2 Dec 92 10:14 EST
Received: from localhost by Mordor.Stanford.EDU (5.65/inc-1.0) id AA25602; Wed, 2 Dec 92 07:14:53 -0800
Message-Id: <9212021514.AA25602@Mordor.Stanford.EDU>
To: kasten@ftp.com
Cc: poised@CNRI.Reston.VA.US
Subject: Re: design teams (was Re: v 1.2, IETF material)
Org: The Branch Office, Sunnyvale CA
Phone: +1 408 246 8253; fax: +1 408 249 6205
In-Reply-To: Your message of Tue, 01 Dec 92 17:34:01 -0500. <9212012234.AA14207@ftp.com>
Date: Wed, 02 Dec 1992 07:14:53 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dave Crocker <dcrocker@mordor.stanford.edu>
X-Mts: smtp
Frank, let's get the main ietf/iesg/iab re-org done. then we can tackle design teams. there are only 24 hours in each day and some of us would like to When I read your note, last night, I felt it to be a reasonable request. In the cold (by local standards) light of morning, I think otherwise. Here's why: Public debate leading into the IAB/IESG/IETF organizational changes proposed at the IETF focussed quite heavily on frustrations with the IAB. But there are, I believe, other frustrations that are serious, frequent, and likely to surface with a vengence. The IESG spends much of its time managing the "process" of IETF working groups. It simply doesn't have enough time to do as much of this as is occurring already. With its new responsbililities, I believe it essential to help working groups do their stuff _much_ more crisply than often occurs, now. (Many, and maybe most, working groups do just fine and don't need any of this wonderful help I'm suggesting.) But having just spend several month participating in one working group that found the contributions of a design team to cause difficulty rather than assistance, and having watched the rather public discomfort about the SMP/SNMPv2 process, I think we need to come to grips with this issue sooner, not later, so that working groups and design teams can know their bounds, rights, and responsibilities. Dave
- design teams (was Re: v 1.2, IETF material) Frank Kastenholz
- Re: design teams (was Re: v 1.2, IETF material) Einar Stefferud
- Re: design teams (was Re: v 1.2, IETF material) Dave Crocker
- Re: design teams (was Re: v 1.2, IETF material) Frank Kastenholz
- Re: design teams (was Re: v 1.2, IETF material) Dave Crocker