Routing Policy System Working Group

Thank you for the feedback. I have incorporated almost all your
suggestions and included the new charter below.

Few questions:

Daniel Karrenberg (Daniel.Karrenberg at ripe.net) on February 28:
>   > and RIPE pride tools will be upgraded to support RPSL
>   > as an initial set of tools.
> out of scope!

Do you mean that the generating tools is out of scope, or upgrading
pride tools?

Even if we do not build tools as a part of the wg effort, we should
still discuss what tools will be of use to the community and try to
come up with definitions for them so that anyone can implement.

> 
>   > The working group will also instigate, review, or (if appropriate)
>   > produce additional RFCs 
>   > to support other protocols such as multicasting and resource reservation.
>   > 
>   > Goals and Milestones:
>   > 
>   >  Apr 95: BOF to discuss scope of work and WG creation
>   > 
>   >  May 95: Publish initial draft specification of RPSL
> 
> Do you have it written NOW?

No. I have changed this date to Jun. This is only initial draft for us
to shoot at.

Charter:

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 database model will be based on the RIPE registry;
and RIPE pride tools will be upgraded to support RPSL
as an initial set of tools.

The working group will also instigate, review, or (if appropriate)
produce additional RFCs 
to support other protocols such as multicasting and resource reservation.

Goals and Milestones:

 Apr 95: BOF to discuss scope of work and WG creation

 Jun 95: Publish initial draft specification of RPSL
      
 Jul 95: Publish draft specification of tools and the database model

 Jul 95: First WG meeting

 Aug 95: Publish second draft specifications
         Begin collecting implementation experience for Standards track RFCs

 Dec 95: Second WG meeting
         Publish RPSL and Experiences RFC

 Jan 96: Submit RFCs for proposed standard

Administrative Structure:

 Chair(s):
   Cengiz Alaettinoglu  <cengiz at isi.edu>
   Another co-chair TBA

 Document Editor(s):
	Cengiz Alaettinoglu <cengiz at isi.edu>

 Internet Area Director(s)
        Mike O'Dell   <odell at uunet.uu.net>

 Area Advisor
        Mike O'Dell   <odell at uunet.uu.net>

 Mailing lists:
        General Discussion:     rps at isi.edu
        To Subscribe:           rps-request at isi.edu
        Archive:                ftp.isi.edu:/pub/rps


Cengiz

-- 
Cengiz Alaettinoglu       Information Sciences Institute
(310) 822-1511            University of Southern California



-------- Logged at  Wed Mar 1 09:37:12 MET 1995  ---------