Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications
RFC 5511
Document | Type |
RFC - Proposed Standard
(April 2009; No errata)
Was draft-farrel-rtg-common-bnf (individual in gen area)
|
|
---|---|---|---|
Last updated | 2018-12-20 | ||
Stream | IETF | ||
Formats | plain text pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5511 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ross Callon | ||
Send notices to | (None) |
Network Working Group A. Farrel Request for Comments: 5511 Old Dog Consulting Category: Standards Track April 2009 Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications Status of This Memo 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. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Farrel Standards Track [Page 1] RFC 5511 Routing BNF April 2009 Abstract 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. Table of Contents 1. Introduction ....................................................3 1.1. Terminology ................................................3 1.2. Existing Uses ..............................................3 1.3. Applicability Statement ....................................4 2. Formal Definitions ..............................................4 2.1. Rule Definitions ...........................................5 2.1.1. Rule Name Delimitation ..............................5 2.1.2. Objects .............................................5 2.1.3. Constructs ..........................................6 2.1.4. Messages ............................................6 2.2. Operators ..................................................6 2.2.1. Assignment ..........................................6 2.2.2. Concatenation .......................................7 2.2.3. Optional Presence ...................................7 2.2.4. Alternatives ........................................8 2.2.5. Repetition ..........................................9 2.2.6. Grouping ...........................................10 2.3. Editorial Conventions .....................................11 2.3.1. White Space ........................................11 2.3.2. Line Breaks ........................................11 2.3.3. Ordering ...........................................11 2.4. Precedence ................................................11 3. Automated Validation ...........................................13 4. Security Considerations ........................................13 5. Acknowledgments ................................................13 6. References .....................................................13 6.1. Normative References ......................................13 6.2. Informative References ....................................13 Farrel Standards Track [Page 2] RFC 5511 Routing BNF April 2009Show full document text