Automatically BGP Integrity Check using IRR-DB
draft-kengo-bgp-integrity-check-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kengo Nagahashi | ||
| Last updated | 2002-02-21 | ||
| 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
In interdomain routing environment, it is often observed Multiple Origin ASes and it causes instability in interdomain routing. To work around its problem, this draft describes the mechanism of automatically integrity check about origin AS. In this approach, BGP router compares with the origin AS in BGP UPDATE and origin AS in IRR database. Also this draft defines messages between BGP router and IRR-DB to transmit query and reply packet. And by introducing the cache mechanism in BGP router, it can apply route flapping environment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)