BGP Destination Preference Attribute Extension to Ripe-181

Document Type Expired Internet-Draft (rps WG)
Author Cengiz Alaettinoglu 
Last updated 1995-11-21
Stream Internet Engineering Task Force (IETF)
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Ripe-181 [2] is a language to specify routing policy constraints for inter-domain routing in the Internet. Ripe-181 allows the specification of both import policy constraints (by specifying as-in and interas-in attributes) and export policy constraints (by specifying as-out and interas-out attributes). The Destination Preference Attribute (DPA) [3] is recently added to the BGP [4] routing protocol. This attribute can be used by an autonomous system (AS) to specify a globally transitive preference in its routing announcement via BGP so that the upstream BGP speakers can use this preference to favor certain path for return traffic. This document extends Ripe-181 to enable the setting of the DPA attribute during route announcements. It is assumed that the reader is familiar with BGP, DPA and Ripe-181.


Cengiz Alaettinoglu (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)