Proposal to use of ABNF in RFC977bis's formal syntax

Paul Overell <paulo@turnpike.com> Thu, 11 July 1996 19:33 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04605; 11 Jul 96 15:33 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04600; 11 Jul 96 15:33 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa27043; 11 Jul 96 15:33 EDT
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by pheasant.academ.com (8.7.5/8.6.9) with ESMTP id OAA08812 for <ietf-nntp@PHEASANT.ACADEM.COM>; Thu, 11 Jul 1996 14:26:30 -0500
Received: from pheasant.academ.com (root@PHEASANT.ACADEM.COM [198.137.249.71]) by academ.com (8.7.5/8.7.1) with ESMTP id OAA29219 for <ietf-nntp@academ.com>; Thu, 11 Jul 1996 14:22:18 -0500 (CDT)
Received: from relay-5.mail.demon.net (relay-5.mail.demon.net [158.152.1.48]) by pheasant.academ.com (8.7.5/8.6.9) with SMTP id OAA08808 for <ietf-nntp@academ.com>; Thu, 11 Jul 1996 14:26:15 -0500
Received: from post.demon.co.uk by relay-5.mail.demon.net id aa28357; 11 Jul 96 13:15 +0100
Received: from pillar.turnpike.com ([194.70.55.2]) by relay-3.mail.demon.net id aa09161; 11 Jul 96 11:05 +0100
Message-ID: <GMUI0HAgHN5xQAcY@turnpike.com>
Date: Thu, 11 Jul 1996 11:05:20 +0100
To: ietf-nntp@academ.com
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Overell <paulo@turnpike.com>
Subject: Proposal to use of ABNF in RFC977bis's formal syntax
MIME-Version: 1.0
X-Mailer: Turnpike Version 1.12 <U2yaxlNz9m7tpk5wwwfqeW1so7>

Both RFC977 and draft-barber-nntp-imp-05.txt give the formal syntax of 
NNTP commands using their own syntactic metalanguage as described in 
RFC977 3.

I would like to propose that RFC977bis should use ABNF for its formal 
syntax.  ABNF is currently being standardized, see draft-drums-abnf-
01.txt.  This is the syntactic metalanguage that is used in RFC822 and
in many other RFC's and drafts.

With a standardized ABNF there is no need for RFC authors to invent (and 
explain) their own variety of syntactic metalanguage. 

So, for example

draft-barber-nntp-imp-05.txt, 2.6 XHDR

   XHDR header [range|<message-id>]

would become

   XHDR-command = "XHDR" header [range / msg-id]

   range = article-number ["-" [article-number]]

   etc.


If this proposal is accepted I would like to offer my help to the 
authors, either by producing the new syntax, or by proof reading, or 
whatever. 


-- 
Paul Overell                                        T U R N P I K E  Ltd