DNS-based NLRI origin AS verification in BGP
draft-bates-bgp4-nlri-orig-verif-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Tony Li , Randy Bush , Yakov Rekhter , Tony Bates | ||
| Last updated | 1998-02-06 | ||
| 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-bates-bgp4-nlri-orig-verif-00.txt
Abstract
This document describes how a BGP speaker may verify that the Network Layer Reachability Information (NLRI) of a prefix received from a peer is consistent with the allocation of IP address space as determined by the Internet Registry system. These verification procedures rely on the DNS to provide a repository of information about address space allocation provided by the Internet Registry system. Note that this is not a repository of announceable prefixes, but rather of allocation of delegated address space.
Authors
Tony Li
(tli@cisco.com)
Randy Bush
(randy@psg.com)
Yakov Rekhter
(yakov@juniper.net)
Tony Bates
(tbates@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)