BGP Community for PA Multihoming
draft-van-beijnum-v6ops-pa-mhome-community-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Iljitsch van Beijnum | ||
| Last updated | 2006-09-28 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
When an organization wants to connect to the internet using two or more Internet Service Providers (multihoming), this is usually done by setting up BGP routing between the organization in question and each of its ISPs. For this, the multihomed organization needs a block of address space. This can either be a provider independent (PI) address block that belongs to the organization, or a block out of the provider aggregatable (PA) address space of one its ISPs. With IPv4, an address block of at least /24 will generally be suitable for multihoming, whether its origin is PI or PA. However, until now, ISPs were encouraged to only accept /32 and shorter prefixes from IPv6 PA space, while end-users generally receive a /48. This makes multihoming with PA address space in IPv6 very difficult. This memo describes a new well-known BGP community attribute for tagging prefixes used for multihoming with PA space in order to facilitate filtering, rather than filter based on prefix length alone.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)