Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Representation of IP Routing Policies in a Routing Registry (ripe-81++) (RFC1786)

IP.com Disclosure Number: IPCOM000004039D
Original Publication Date: 1995-Mar-01
Included in the Prior Art Database: 2000-Sep-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Bates: AUTHOR [+7]

Abstract

This document was originally published as a RIPE document known as ripe-181 but is also being published as an Informational RFC to reach a larger audience than its original scope. It has received community wide interest and acknowledgment throughout the Internet service provider community and will be used as the basic starting point for future work on Internet Routing Registries and routing policy representation. It can also be referred to as ripe-81++. This document is an update to the original `ripe-81'[1] proposal for representing and storing routing polices within the RIPE database. It incorporates several extensions proposed by Merit Inc.[2] and gives details of a generalized IP routing policy representation to be used by all Internet routing registries. It acts as both tutorial and provides details of database objects and attributes that use and make up a routing registry.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group T. Bates

Request for Comments: 1786 MCI Telecommunications Corporation

Category: Informational E. Gerich

Merit, Inc.

L. Joncheray

Merit, Inc.

J-M. Jouanigot

CERN

D. Karrenberg

RIPE NCC

M. Terpstra

Bay Networks, Inc.

J. Yu

Merit, Inc.

March 1995

Representation of IP Routing Policies

in a Routing Registry

(ripe-81++)

Status of this Memo

This memo provides information for the Internet community. This memo

does not specify an Internet standard of any kind. Distribution of

this memo is unlimited.

Abstract

This document was originally published as a RIPE document known as

ripe-181 but is also being published as an Informational RFC to reach

a larger audience than its original scope. It has received community

wide interest and acknowledgment throughout the Internet service

provider community and will be used as the basic starting point for

future work on Internet Routing Registries and routing policy

representation. It can also be referred to as ripe-81++. This

document is an update to the original `ripe-81'[1] proposal for

representing and storing routing polices within the RIPE database. It

incorporates several extensions proposed by Merit Inc.[2] and gives

details of a generalized IP routing policy representation to be used

by all Internet routing registries. It acts as both tutorial and

provides details of database objects and attributes that use and make

up a routing registry.

Table of Contents

1. Introduction ................................................ 3

2. Organization of this Document ............................... 3

3. General Representation of Policy Information ............... 5

4. The Routing Registry and the RIPE Database .................. 11

<...