Re: Experimental RFC-to-be submission

postel@isi.edu Mon, 01 May 1995 19:59 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09286; 1 May 95 15:59 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09282; 1 May 95 15:59 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa14954; 1 May 95 15:59 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09265; 1 May 95 15:59 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09258; 1 May 95 15:59 EDT
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa14949; 1 May 95 15:59 EDT
Received: from zen.isi.edu by venera.isi.edu (5.65c/5.61+local-21) id <AA13411>; Mon, 1 May 1995 13:00:09 -0700
Date: Mon, 1 May 1995 13:00:28 -0700
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: postel@isi.edu
Posted-Date: Mon, 1 May 1995 13:00:28 -0700
Message-Id: <199505012000.AA24606@zen.isi.edu>
Received: by zen.isi.edu (5.65c/4.0.3-4) id <AA24606>; Mon, 1 May 1995 13:00:28 -0700
To: iesg-secretary@IETF.CNRI.Reston.VA.US
Subject: Re: Experimental RFC-to-be submission
Cc: iesg@isi.edu, rfc-editor@isi.edu

Steve:

Sure, lets set the timeout on these for two weeks from now = 15-May-95.

--jon.


   From scoya@CNRI.Reston.VA.US Mon May  1 12:33:32 1995
   To: rfc-editor@ISI.EDU
   Cc: iesg@CNRI.Reston.VA.US
   Subject: Re: Experimental RFC-to-be submission
   From: IESG Secretary <iesg-secretary@IETF.CNRI.Reston.VA.US>
   Date: Mon, 01 May 95 15:30:17 -0400
   Sender: scoya@CNRI.Reston.VA.US
   
   
   Joyce and --jon,
   
   I would like to ask for an extension to the timeout period for the
   following RFC submissions that were sent to the IESG for comment:
   
   
      Internet Stream Protocol Version 2 (ST2) V2 - Experimental
      <draft-ietf-st2-spec-04.txt>
   
      Common DNS Operational and Configuration Errors - Informational
   
      The Meta-Management MIB (SNMPv1) Network Topology and Set of Agents
      - Experimental
   
      ISO Transport Class 2 Non-use of Explicit Flow Control over TCP
      RFC1006 extension - Informational
   
   
   These documents were sent just before the IESG retreat, and I would
   like the IESG to have more time to review and comment.
   
   Thanks.
   
   
   Steve