IRR & Routing Policy Configuration Considerations
draft-grow-irr-routing-policy-considerations-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Danny R. McPherson , Shane Amante , Eric Osterweil , Larry Blunk | ||
| Last updated | 2013-06-21 (Latest revision 2012-12-18) | ||
| 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
The purpose of this document is to catalog past issues influencing the efficacy of Internet Routing Registries (IRR) for inter-domain routing policy specification and application in the global routing system over the past two decades. Additionally, it provides a discussion regarding which of these issues are still problematic in practice, and which are simply artifacts that are no longer applicable but continue to stifle inter-provider policy-based filtering adoption and IRR utility to this day.
Authors
Danny R. McPherson
Shane Amante
Eric Osterweil
Larry Blunk
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)