Syntax for format definitions

Brian E Carpenter <chair@ietf.org> Thu, 12 May 2005 18:42 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DWIe0-0002KL-Ut; Thu, 12 May 2005 14:42:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DWIdz-0002KG-LW for ietf-announce@megatron.ietf.org; Thu, 12 May 2005 14:42:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19971 for <ietf-announce@ietf.org>; Thu, 12 May 2005 14:42:46 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DWItl-0000oc-V7 for ietf-announce@ietf.org; Thu, 12 May 2005 14:59:06 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1DWIdy-0004gS-Ug for ietf-announce@ietf.org; Thu, 12 May 2005 14:42:46 -0400
Content-Type: text/plain;
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: Brian E Carpenter <chair@ietf.org>
Message-Id: <E1DWIdy-0004gS-Ug@newodin.ietf.org>
Date: Thu, 12 May 2005 14:42:46 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: Syntax for format definitions
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

The IESG does not prescribe the use of any single syntax for format
definitions. It does require that documents making use of such
provide a normative reference to a document laying out the syntax.
The IESG recommends that authors choose a syntax for which automated
validation is available, as an aid to production and review. At the
time of this statement, ABNF is most common in Standards Track RFCs,
and authors are encouraged to review draft-crocker-abnf-rfc2234bis-00.txt.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce