Moving RFC 1137 to Historical?
Harald.T.Alvestrand@uninett.no Tue, 03 October 1995 13:36 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09869; 3 Oct 95 9:36 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09865; 3 Oct 95 9:36 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09568; 3 Oct 95 9:36 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09856; 3 Oct 95 9:36 EDT
Received: from domen.uninett.no by IETF.CNRI.Reston.VA.US id aa09852; 3 Oct 95 9:35 EDT
Received: from domen.uninett.no by domen.uninett.no with SMTP (PP) id <14285-0@domen.uninett.no>; Tue, 3 Oct 1995 13:55:15 +0100
X-Mailer: exmh version 1.6.2 7/18/95
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Harald.T.Alvestrand@uninett.no
To: iesg@IETF.CNRI.Reston.VA.US
cc: ietf-mixer@innosoft.com
Subject: Moving RFC 1137 to Historical?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 03 Oct 1995 13:55:13 +0100
X-Orig-Sender: Harald.T.Alvestrand@uninett.no
Message-ID: <9510030935.aa09852@IETF.CNRI.Reston.VA.US>
RFC 1137 (Mapping Between Full RFC 822 and RFC 822 with Restricted Encoding)
is an Experimental document.
The author and (at least some of) the community of interest think that the
experiment failed, and use of this doc should be actively discouraged.
Is there a history of moving failed experiments to Historic, or do we just
leave them as Experimental?
Harald A
- Moving RFC 1137 to Historical? Harald.T.Alvestrand
- Moving RFC 1137 to Historical? /G=Bengt/S=Ackzell/O=AIT/