One Administrative Domain
draft-uttaro-idr-oad-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jim Uttaro , Saikat Ray , Prodosh Mohapatra | ||
| Last updated | 2014-07-21 (Latest revision 2014-01-09) | ||
| Replaced by | draft-uttaro-idr-bgp-oad | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-uttaro-idr-bgp-oad | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The notional premise that different Autonomous Systems belong to different administrative authorities may not always hold. A single administrative authority may instantiate services on and across multiple ASes. A customer accessing those services can reasonably expect that attributes such as LOCAL_PREF that influence routing be applicable even across different ASes. This document describes a mechanism to do so.
Authors
Jim Uttaro
Saikat Ray
Prodosh Mohapatra
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)