RFC 5511 on Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications

rfc-editor@rfc-editor.org Tue, 28 April 2009 23:56 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 185C93A6BE9 for <ietf-announce@core3.amsl.com>; Tue, 28 Apr 2009 16:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.924
X-Spam-Status: No, score=-16.924 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id IB9arjMivpQP for <ietf-announce@core3.amsl.com>; Tue, 28 Apr 2009 16:56:10 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id C93043A67FB for <ietf-announce@ietf.org>; Tue, 28 Apr 2009 16:56:09 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id CE265293E4E; Tue, 28 Apr 2009 16:54:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5511 on Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications
From: rfc-editor@rfc-editor.org
Message-Id: <20090428235448.CE265293E4E@bosco.isi.edu>
Date: Tue, 28 Apr 2009 16:54:48 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2009 23:56:11 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5511

        Title:      Routing Backus-Naur Form (RBNF): A 
                    Syntax Used to Form Encoding Rules 
                    in Various Routing Protocol Specifications 
        Author:     A. Farrel
        Status:     Standards Track
        Date:       April 2009
        Mailbox:    adrian@olddog.co.uk
        Pages:      14
        Characters: 27026
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-farrel-rtg-common-bnf-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5511.txt

Several protocols have been specified in the Routing Area of the IETF
using a common variant of the Backus-Naur Form (BNF) of representing
message syntax.  However, there is no formal definition of this
version of BNF.

There is value in using the same variant of BNF for the set of
protocols that are commonly used together.  This reduces confusion and
simplifies implementation.

Updating existing documents to use some other variant of BNF that is
already formally documented would be a substantial piece of work.

This document provides a formal definition of the variant of BNF that
has been used (that we call Routing BNF) and makes it available
for use by new protocols.  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute