"Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4), Second Version", Jeffrey Haas, 22-Jun-08. ( bytes)

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines objects for managing the Border Gateway Protocol, Version 4.

"AS-wide Unique BGP Identifier for BGP-4", Enke Chen, Jenny Yuan, 13-May-08. ( bytes)

To accommodate situations where the current requirements for the BGP Identifier are not met, this document relaxes the definition of the BGP Identifier to be a 4-octet unsigned, non-zero integer, and relaxes the "uniqueness" requirement so that only AS-wide uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any backward compatibility issue.

"Dissemination of flow specification rules", Pedro Roque Marques, Nischal Sheth, Robert Raszuk, Barry Greene, Danny McPherson, 4-Sep-08. ( bytes)

This document defines a new BGP NLRI encoding format that can be used to distribute traffic flow specifications. This allows the routing system to propagate information regarding more-specific components of the traffic aggregate defined by an IP destination prefix. Additionally it defines two applications of that encoding format. One that can be used to automate inter-domain coordination of traffic filtering, such as what is required in order to mitigate (distributed) denial of service attacks. And a second application to traffic filtering in the context of a BGP/MPLS VPN service. The information is carried via the Border Gateway Protocol (BGP), thereby reusing protocol algorithms, operational experience and administrative processes such as inter-provider peering agreements.

"Capabilities Advertisement with BGP-4", John Scudder, Ravi Chandra, 22-May-08. ( bytes)

This document defines an Optional Parameter, called Capabilities, that is expected to facilitate the introduction of new capabilities in the Border Gateway Protocol (BGP) by providing graceful capability advertisement without requiring that BGP peering be terminated. This document obsoletes RFC 3392.

"Textual Representation of AS Numbers", Geoff Huston, George Michaelson, 22-Sep-08. ( bytes)

A textual representation for Autonomous System (AS) numbers is defined as the decimal value of the AS Number. This textual representation is to be used by all documents, systems and user interfaces referring to AS numbers.

"AS Number Reservation for Documentation Use", Geoff Huston, 3-Oct-08. ( bytes)

To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, two blocks of Autonomous System numbers (ASNs) are reserved for use in examples in RFCs, books, documentation, and the like. This document describes the reservation of two blocks of ASNs as reserved numbers for use in documentation.

Return to Internet-Draft directory.

Return to IETF home page.