nits with RFC 1398
Jim Barnes <barnes@xylogics.com> Fri, 12 February 1993 14:56 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04977; 12 Feb 93 9:56 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04973; 12 Feb 93 9:56 EST
Received: from babyoil.ftp.com by CNRI.Reston.VA.US id aa03472; 12 Feb 93 9:56 EST
Received: from atlas.xylogics.com by ftp.com with SMTP id AA16969; Fri, 12 Feb 93 09:48:56 -0500
Received: from spock.xylogics.com by atlas.xylogics.com with SMTP id AA05024 (5.65c/UK-2.1-930202); Fri, 12 Feb 1993 09:52:32 -0500
Received: by spock.xylogics.com id AA26400 (4.1/UK-2.1-921215); Fri, 12 Feb 93 09:50:18 EST
Message-Id: <26400.9302121450@spock.xylogics.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jim Barnes <barnes@xylogics.com>
Date: Fri, 12 Feb 1993 09:50:17 -0500
X-Mailer: Mail User's Shell (7.1.0 4/25/90)
To: enet_mib@ftp.com
Subject: nits with RFC 1398
I just tried to extract the mib definition from the RFC document. After removing the text, the page headers and footers, and the embedded section headers, I found that the MIB would still not compile correctly because some of the comments on page 13 of the document were mangled. Jim Barnes (barnes@xylogics.com)
- nits with RFC 1398 Jim Barnes