DNS Resource Records for Authorized Routing Information
draft-gersch-grow-revdns-bgp-02

Document Type Expired Internet-Draft (individual)
Last updated 2013-08-29 (latest revision 2013-02-25)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-gersch-grow-revdns-bgp-02.txt

Abstract

This draft discusses the use of two DNS record types for storing BGP routing information in the reverse DNS. The RLOCK record allows prefix owners to indicate whether the DNS is being used to publish routing data. The SRO record allows operators to indicate whether an IPv4 or IPv6 prefix ought to appear in global routing tables and identifies authorized origin Autonomous System Number(s) for that prefix. The resulting published data can be used in a variety of contexts from routing security to address ownership.

Authors

Joe Gersch (joe.gersch@secure64.com)
Dan Massey (massey@cs.colostate.edu)
Cathie Olschanowsky (cathie@cs.colostate.edu)
Lixia Zhang (lixia@cs.ucla.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)