IRR & Routing Policy Configuration Considerations
draft-grow-irr-routing-policy-considerations-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Danny McPherson , Shane Amante , Eric Osterweil , Larry Blunk | ||
| Last updated | 2013-06-21 (latest revision 2012-12-18) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-grow-irr-routing-policy-considerations-00.txt
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 McPherson
(dmcpherson@verisign.com)
Shane Amante
(shane@level3.net)
Eric Osterweil
(eosterweil@verisign.com)
Larry Blunk
(ljb@merit.edu)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)