Routing Policy System Working Group

Cengiz: 
I would like to suggest that some text be added to clarify the 
focus of the working group -- inter-domain routing.  This should 
not exclude the possiblity of touch general intra-domain issues.  
For example, I am thinking of a static-route-object to better 
handle the increasing number of customers that need static 
configuration. 

-- Enke

> Date:    Wed, 1 Mar 1995 17:53:50 -0800
> From:    cengiz at ISI.EDU (Cengiz Alaettinoglu)
> To:      cengiz at ISI.EDU (Cengiz Alaettinoglu)
> CC:      Daniel Karrenberg <Daniel.Karrenberg at ripe.net>, rr-impl at ripe.net

> 
> This is the final charter that I will mail to Megan tomorrow. Last
> chance to make comments.
> 
> Cengiz
> 
> -- 
> Cengiz Alaettinoglu       Information Sciences Institute
> (310) 822-1511            University of Southern California
> 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, fo
r
> checking global consistency, for generating router configurations, and fo
r
> 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 suc
h
> 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 also instigate, review, or (if appropriate) produc
e
> 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 R
FCs
> 
>  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



-------- Logged at  Thu Mar 2 16:24:07 MET 1995  ---------