RPS BOF at Danvers IETF

Cengiz Alaettinoglu <cengiz@isi.edu> Thu, 30 March 1995 23:49 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17721; 30 Mar 95 18:49 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17717; 30 Mar 95 18:49 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa27430; 30 Mar 95 18:49 EST
Received: by interlock.ans.net id AA23673 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Thu, 30 Mar 1995 18:20:29 -0500
Message-Id: <199503302320.AA23673@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-3); Thu, 30 Mar 1995 18:20:29 -0500
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Thu, 30 Mar 1995 18:20:29 -0500
Date: Thu, 30 Mar 1995 15:19:57 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Cengiz Alaettinoglu <cengiz@isi.edu>
Posted-Date: Thu, 30 Mar 1995 15:19:57 -0800
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Thu, 30 Mar 1995 18:20:29 -0500
To: bgp@ans.net
Subject: RPS BOF at Danvers IETF

Hi,

We are forming a new working group called Routing Policy System
(RPS). We will have our first meeting Thursday morning at 9am (with
mbone coverage). Here is the charter if you are interested. 

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 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 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@isi.edu>
        Daniel Karrenberg    <Daniel.Karrenberg@ripe.net>

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

 Operational Requirements Area Director(s):
	Scott Bradner <sob@harvard.edu>
	Mike O'Dell   <mo@uunet.uu.net>

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


Cengiz

-- 
Cengiz Alaettinoglu       Information Sciences Institute
(310) 822-1511            University of Southern California
http://www.isi.edu/div7/people/cengiz.home