Routing Policy System (rps) Charter
NOTE: This charter is accurate as of the 37th IETF Meeting in San Jose. It
may now be out-of-date. (Consider this a "snapshot" of the working
group from that meeting.) Up-to-date charters for all active working
groups can be found elsewhere in this Web server.
- Cengiz Alaettinoglu <firstname.lastname@example.org>
- Daniel Karrenberg <email@example.com>
Operational Requirements Area Director(s):
- Scott Bradner <firstname.lastname@example.org>
- Michael O'Dell <email@example.com>
Mailing List Information
- General Discussion:firstname.lastname@example.org
- To Subscribe: email@example.com
- Archive: ftp://ftp.isi.edu/rps
Description of Working Group
The Routing Policy System Working Group will (1) define a language,
referred to as Routing Policy Specification Language (RPSL), for
describing routing policy constraints; (2) define a simple and robust
distributed registry model for publishing routing policy constraints;
and (3) define a set of tools for analysing registered policy
constraints, for checking global consistency, for generating router
configurations, and for diagnosing operational routing problems. It is
expected that RPSL will enter the standards track.
The RPSL will be routing protocol independent as well as router
configuration format independent to support various routing protocols
such as BGP, IDRP, SDRP, and various router technologies. The RPSL will
be backward compatible with RIPE-181 whenever possible; the registry
model will be based on the RIPE database.
The working group will focus on inter-domain routing protocols, but
will also instigate, review, or (if appropriate) produce additional
RFCs to support other protocols such as multicasting and resource
Goals and Milestones
- Hold BOF to discuss scope of work and working group creation.
- Jul 95
- Submit initial draft specification of RPSL as an Internet-Draft.
- Jul 95
- Submit draft specification of tools and the database model as an Internet-Draft.
- Sep 95
- Submit revised Internet-Draft.
- Dec 95
- Submit document on RPSL and Experiences to IESG to be considered for publication as an RFC.
- Jan 96
- Submit RPSL specification to IESG for consideration as a Proposed Standard.
No Request for Comments