Re: RFC 1209 (IP over SMDS) advancement to Draft Standard
stev@ftp.com Fri, 10 February 1995 19:37 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id ab07415; 10 Feb 95 14:37 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id ab07411; 10 Feb 95 14:37 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa12352; 10 Feb 95 14:37 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07378; 10 Feb 95 14:36 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07374; 10 Feb 95 14:36 EST
Received: from wd40.ftp.com by CNRI.Reston.VA.US id aa12317; 10 Feb 95 14:36 EST
Received: from ftp.com by ftp.com ; Fri, 10 Feb 1995 14:36:27 -0500
Received: from mailserv-D.ftp.com by ftp.com ; Fri, 10 Feb 1995 14:36:27 -0500
Received: from stev.d-cell.ftp.com by mailserv-D.ftp.com (5.0/SMI-SVR4) id AA13502; Fri, 10 Feb 95 14:32:49 EST
Date: Fri, 10 Feb 1995 14:32:49 -0500
Message-Id: <9502101932.AA13502@mailserv-D.ftp.com>
To: malis@maelstrom.timeplex.com
Subject: Re: RFC 1209 (IP over SMDS) advancement to Draft Standard
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: stev@ftp.com
Cc: iesg@CNRI.Reston.VA.US, iplpdn@CNRI.Reston.VA.US, malis@maelstrom.acton.timeplex.com, dave@corecom.com, jcl@mail.bellcore.com, clapp@ameris.center.il.ameritech.com, stev+iesg@ftp.com
X-Orig-Sender: stev@mailserv-d.ftp.com
Repository: mailserv-D.ftp.com, [message accepted at Fri Feb 10 14:32:39 1995]
Originating-Client: d-cell.ftp.com
Content-Length: 157
this is an interesting message. is there one implementation that does *everything* in the RFC? other than this question, there should be no problem.