RFC 2622 on RPSL

RFC Editor <rfc-ed@ISI.EDU> Thu, 24 June 1999 23:41 UTC

Message-Id: <199906242325.QAA03041@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2622 on RPSL
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 24 Jun 1999 16:25:13 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2622:

        Title:	    Routing Policy Specification Language (RPSL
	Author(s):  C. Alaettinoglu, C. Villamizar, E. Gerich,
		    D. Kessens, D. Meyer, T. Bates, D. Karrenberg, 
		    M. Terpstra
        Status:     Proposed Standard
	Date:       June 1999
        Mailbox:    cengiz@isi.edu, curtis@avici.com, epg@home.net,
		    David.Kessens@qwest.net, meyer@antc.uoregon.edu,
		    tbates@cisco.com, dfk@ripe.net,
		    marten@BayNetworks.com
        Pages:      69
        Characters: 140811
	Obsoletes:  2280
        I-D Tag:    draft-ietf-rps-rpsl-v2-03.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2622.txt


RPSL allows a network operator to be able to specify routing policies
at various levels in the Internet hierarchy; for example at the
Autonomous System (AS) level.  At the same time, policies can be
specified with sufficient detail in RPSL so that low level router
configurations can be generated from them.  RPSL is extensible; new
routing protocols and new protocol features can be introduced at any
time.

This document is a product of the Routing Policy System Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2622.txt"><ftp://ftp.isi.edu/in-notes/rfc2622.txt>

RFC 2622 on RPSL RFC Editor