Re: WG guidelines DRAFT!
Fred Baker <fbaker@acc.com> Thu, 14 January 1993 16:51 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15273; 14 Jan 93 11:51 EST
Received: from SAFFRON.ACC.COM by IETF.CNRI.Reston.VA.US id aa15264; 14 Jan 93 11:51 EST
Received: by saffron.acc.com (4.1/SMI-4.1) id AA00321; Thu, 14 Jan 93 08:51:49 PST
Date: Thu, 14 Jan 1993 08:51:49 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Fred Baker <fbaker@acc.com>
Message-Id: <9301141651.AA00321@saffron.acc.com>
To: Erik.Huizer@surfnet.nl, kasten@ftp.com
Subject: Re: WG guidelines DRAFT!
Cc: poised@IETF.CNRI.Reston.VA.US
>> > Termination of a WG >> > ------------------- >> > After that task is complete, the group will be disbanded. >> Sometimes working groups might also go "dormant". They remain in >> existance, but there is little activity. For example, as a document >> goes through the progression from Proposed Standard to Draft >> Standard to Full Standard the working group might periodically "wake >> up" to monitor the implementations to ensure that the "right things" >> are being done, to fix problems in the standard that show up with >> implmentation, and to make the necessary reports to the IESG. I'm very much in favor of this "dormancy" concept. Current practice in the network manageemnt area seems to be to terminate the working group after IESG acceptance of a document, whether at Proposed, Draft, or Standard status has been reached. The idea is that "if it needs to be fixed we'll revive the working group." I think the normal expectation should be that the WG is shepherding the document from inception to Full Standard status. Fred
- WG guidelines DRAFT! Erik Huizer
- Re: WG guidelines DRAFT! Frank Kastenholz
- Re: WG guidelines DRAFT! Fred Baker
- Re: WG guidelines DRAFT! Scott_Brim
- Re: WG guidelines DRAFT! Fred Baker
- Re: WG guidelines DRAFT! Scott_Brim