Re: Proposal to use of ABNF in RFC977bis's formal syntax

Stan Barber <sob@academ.com> Thu, 11 July 1996 21:59 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07725; 11 Jul 96 17:59 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07720; 11 Jul 96 17:59 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa03825; 11 Jul 96 17:59 EDT
Received: from academ.com (sob@ACADEM.COM [198.137.249.2]) by pheasant.academ.com (8.7.5/8.6.9) with ESMTP id QAA09172 for <ietf-nntp@PHEASANT.ACADEM.COM>; Thu, 11 Jul 1996 16:57:39 -0500
Received: (from sob@localhost) by academ.com (8.7.5/8.7.1) id QAA01150; Thu, 11 Jul 1996 16:53:25 -0500 (CDT)
Message-Id: <199607112153.QAA01150@academ.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Stan Barber <sob@academ.com>
Date: Thu, 11 Jul 1996 16:53:24 CDT
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Jonathan Grobe <grobe@netins.net>, ietf-nntp@academ.com
Subject: Re: Proposal to use of ABNF in RFC977bis's formal syntax
Cc: ietf-nntp@academ.com

I would strongly recommend that anyone wanting to refer to any
document available through a URL, please post the URL, not the document.
If the document is not available via a URL, then mail it to me and I 
will put it up for anonymous ftp here at academ.com.

There are probably some folks in this group that may not have large mail
spools and getting multiple megabyte mail may be hard to accomodate on
a regular basis.

Of course, I could be completely off-base about this. After all, this is
a discussion group for NNTP and netnews has used a flooding mechanism for
years. :-)



-- 
Stan   | Academ Consulting Services        |internet: sob@academ.com
Olan   | For more info on academ, see this |uucp: {mcsun|amdahl}!academ!sob
Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.