RIPE-181 to RPSL Transition Plan
draft-ietf-rps-transition-02

Document Type Expired Internet-Draft (rps WG)
Authors David Kessens  , Carol Orange 
Last updated 2000-02-14 (latest revision 1998-04-10)
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-ietf-rps-transition-02.txt

Abstract

The standardization of RPSL (Routing Policy Specification Language) is imminent, and there is a user community eager to make use of the power- ful features it offers in the Routing Registry (IRR). Thus, a plan of action is needed to assure a successful transition from the RIPE-181 language currently employed to describe routing policies in the IRR to the more expressive RPSL. This document describes such a plan, which the authors believe can be used to bring about a successful transition in a timely fashion with a minimum of disruption to the IRR and its cur- rent role in Internet routing. This document will be modified to reflect the progress of the transition if appropriate.

Authors

David Kessens (david.kessens@nokia.com)
Carol Orange (orange@ripe.net)

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