From rps-owner@ISI.EDU  Mon Jan  4 14:31:01 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA20614
	for <rps-archive@lists.ietf.org>; Mon, 4 Jan 1999 14:31:00 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id LAA00528
	for rps-outgoing; Mon, 4 Jan 1999 11:15:51 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id LAA00523
	for <rps@zephyr.isi.edu>; Mon, 4 Jan 1999 11:15:49 -0800 (PST)
Received: from brookfield.ans.net (brookfield-ef0.brookfield.ans.net [204.148.1.20])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id LAA03267
	for <rps@isi.edu>; Mon, 4 Jan 1999 11:15:46 -0800 (PST)
Received: from brookfield.ans.net (localhost.brookfield.ans.net [127.0.0.1])
	by brookfield.ans.net (8.8.8/8.8.8) with ESMTP id OAA15586;
	Mon, 4 Jan 1999 14:15:45 -0500 (EST)
	(envelope-from curtis@brookfield.ans.net)
Message-Id: <199901041915.OAA15586@brookfield.ans.net>
To: rps@ISI.EDU
cc: curtis@ans.net
Reply-To: curtis@ans.net
Subject: Reminder - Last call (was: Re: Amended RPS Work Group Charter)
Date: Mon, 04 Jan 1999 14:15:45 -0500
From: Curtis Villamizar <curtis@brookfield.ans.net>
Sender: owner-rps@ISI.EDU
Precedence: rps-list



Just a reminder to comment before Jan 7 if you have any comments.  We
issued an extended last call on the Work Group Charter.  The proposed
charter further ammended to reflect comments appears below followed by
the comments so far.

Changes are:

  1.  Changed Spring to April.  Changed Summer to August.

  2.  Separated milestones for April that are not interdependent.

  3.  Added "Advance RPSL to Draft Standard" but put it at December
      since we must wait at least 6 months after IESG approval of the
      reissued Proposed Standard.

  4.  We'll be advancing draft-ietf-rps-appl-rpsl to Informational and
      draft-ietf-rps-transition to vapor.

The biggest controversy so far is the choice of the word "spring" to
describe a milestone date which is now resolved.  :-)

Curtis


Routing Policy System (rps)
 ---------------------------

 Charter
 Last Modified: ---new-date-here---

 Current Status: Active Working Group

 Chair(s):
     Cengiz Alaettinoglu <cengiz@isi.edu>
     Curtis Villamizar <curtis@ans.net>

 Operations and Management Area Director(s):
     Harald Alvestrand  <Harald.Alvestrand@maxware.no>
     Bert Wijnen  <wijnen@vnet.ibm.com>

 Operations and Management Area Advisor:
     Bert Wijnen  <wijnen@vnet.ibm.com>

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

Description of Working Group:

The Routing Policy System Working Group intends to provide
standardization of protocols and recommended practices neccesary to
support interoperability of the Internet Routing Registry (IRR).  The
IRR has been in use since 1995 based initially on the RIPE-181 policy
language.

The activities of the RPS Working Group shall include (1) defining a
language, referred to as Routing Policy Specification Language (RPSL),
for describing routing policy constraints, (2) defining a simple and
robust distributed registry model for publishing routing policy
constraints, and (3) providing a forum for the discussion of tools
for analysing registered policy constraints, for checking global
consistency, for generating router configurations, and for diagnosing
operational routing problems.

 Goals and Milestones:

   Dec 1998	Reissue RPSL as a Proposed Standard with modifications
		resulting from deployment experience.

   Apr 1999	Advance draft-ietf-rps-appl-rpsl to Informational and
		withdraw draft-ietf-rps-transition.

   Apr 1999	Advance draft-ietf-rps-dbsec-pgp-authent to Proposed
		Standard.

   Apr 1999	Advance draft-ietf-rps-auth to Proposed Standard. 

   Aug 1999	Advance draft-ietf-rps-dist to Proposed Standard.

   Dec 1999     Advance RPSL to Draft Standard.

 Internet-Drafts:

  Posted   Revised       I-D Title  <Filename>
  ------   -------   ------------------------------------------
 Mar 1997  Nov 1998  <draft-ietf-rps-transition-02.txt>
		     RIPE-181 to RPSL Transition Plan

 Mar 1997  Jul 1998  <draft-ietf-rps-appl-rpsl-02.txt,.ps>
		     Using RPSL in Practice

 Mar 1998  May 1998  <draft-ietf-rps-auth-01.txt,.ps>
		     Routing Policy System Security

 Sep 1998  Sep 1998  <draft-ietf-rps-dist-00.txt,.ps>
                     Distributed Routing Policy System

 Nov 1998  Nov 1998  <draft-ietf-rps-appl-rpsl-03.txt,.ps>
                     Using RPSL in Practice

 Nov 1998  Nov 1998  <draft-ietf-rps-dbsec-pgp-authent-00.txt>
                     PGP authentication for RIPE database updates

 Nov 1998  Nov 1998  <draft-ietf-rps-rpsl-v2-00.txt,.ps>
                     Routing Policy Specification Language (RPSL)

 Request For Comments:

  RFC  Stat Published       Title
- ------- -- ----------     -----------------------------------------
RFC2280 PS   Jan 1998     Routing Policy Specification Language (RPSL)




============ comments so far ============

: Mark Prior <mrp@connect.com.au>

        Spring 1999     Advance draft-ietf-rps-transition,
                draft-ietf-rps-appl-rpsl,
                draft-ietf-rps-dbsec-pgp-authent, and
                draft-ietf-rps-auth to
                Proposed Standard.

I don't believe these are all to be advanced to PS, I thought the
"Using RPSL in Practice" document would be informational. I'm also not
sure that it would be ready for advancement in spring.

I thought the original intent of the transition document was to keep
it an I-D and let it document the progress of the transition. When the
transition was finished then there would be no need for the document
and so it would just vapourize.

Mark.


curtis>  OK.  Then the milestone is advance draft-ietf-rps-appl-rpsl to
curtis>  informational and vaporize draft-ietf-rps-transition.  ;-)

Curtis


: Harald Tveit Alvestrand <Harald@Alvestrand.no>

At 12:41 11.12.98 +1030, Mark Prior wrote:
>        Spring 1999     Advance draft-ietf-rps-transition,
>                draft-ietf-rps-appl-rpsl,
>                draft-ietf-rps-dbsec-pgp-authent, and
>                draft-ietf-rps-auth to
>                Proposed Standard.
>

Useful trick of milestone writing:
If I-Ds are linked to such a degree that one can't be published without
the other, they should be on the same milestone.

If they are not, they should be separate milestones, even if they are
the same date.

BTW, "spring" isn't a month name.

                Harald A

: Cengiz Alaettinoglu <cengiz@ISI.EDU>

Curtis,

The charter and milestones seems to capture the WG discussions.  We
also agreed to move RPSL to draft standard 6 months after it becomes
proposed standard again. Please add it as a milestone to summer 1999.

Lets use April instead of spring and August instead of summer as they
are a month after the IETF's.

Cengiz


: Joe Abley <jabley@clear.co.nz>

On Mon, Dec 14, 1998 at 11:16:23AM -0800, Cengiz Alaettinoglu wrote:
> 
> Lets use April instead of spring and August instead of summer as they
> are a month after the IETF's.

Also, August is in Winter and April is in Autumn, so the original wording
was extremely confusing.

You blinkered northern-hemispherics! :)

Joe


: Mark Prior <mrp@connect.com.au>

     If they are not, they should be separate milestones, even if they are
     the same date.

I would think they should all be separate.

     BTW, "spring" isn't a month name.

And where I'm from it's not even the same range of months :-)

Mark.


From rps-owner@ISI.EDU  Wed Jan  6 00:16:00 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id AAA16520
	for <rps-archive@lists.ietf.org>; Wed, 6 Jan 1999 00:15:59 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id UAA14807
	for rps-outgoing; Tue, 5 Jan 1999 20:56:35 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id UAA14802
	for <rps@zephyr.isi.edu>; Tue, 5 Jan 1999 20:56:34 -0800 (PST)
Received: from brookfield.ans.net (brookfield-ef0.brookfield.ans.net [204.148.1.20])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id UAA21818;
	Tue, 5 Jan 1999 20:56:32 -0800 (PST)
Received: from brookfield.ans.net (localhost.brookfield.ans.net [127.0.0.1])
	by brookfield.ans.net (8.8.8/8.8.8) with ESMTP id XAA22858;
	Tue, 5 Jan 1999 23:56:31 -0500 (EST)
	(envelope-from curtis@brookfield.ans.net)
Message-Id: <199901060456.XAA22858@brookfield.ans.net>
To: cengiz@ISI.EDU
cc: curtis@ans.net, rps@ISI.EDU
Reply-To: curtis@ans.net
Subject: Re: draft of RPS meeting minutes 
In-reply-to: Your message of "Wed, 16 Dec 1998 10:17:30 PST."
             <13943.63802.215366.881321@dog.isi.edu> 
Date: Tue, 05 Jan 1999 23:56:30 -0500
From: Curtis Villamizar <curtis@brookfield.ans.net>
Sender: owner-rps@ISI.EDU
Precedence: rps-list


In message <13943.63802.215366.881321@dog.isi.edu>, Cengiz Alaettinoglu writes:
> 
> I did minor editing of the minutes and I am about to send it to the
> list. One question:
> 
> Curtis Villamizar (curtis@brookfield.ans.net) on December 10:
> >     The default for reclaim/no-reclaim is currently implied to be
> >     no-reclaim but should be explicitly stated and should be reclaim.
> 
> I thought we decided to make it explicit but keep it as no-reclaim?
> 
> Cengiz


Did I reply to this?  I added the list to the Cc for comment from the
whole WG.

All existing route objects do not have this field and the behavior is
no-reclaim.  That was my reason for favoring no-reclaim.

I thought at the meeting RIPE wanted reclaim because in effect being
able to edit the database with an editor or change any maintainer in
the database at will gives them reclaim.  They'd rather see the
default be reclaim.  This also follows some existing BCPs.

We've been back and forth on this so many times I forget where we
ended up on any given day.

reclaim?  no-reclaim?  ???  rps-auth needs a decision.

Curtis


From rps-owner@ISI.EDU  Fri Jan  8 03:47:08 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id DAA08775
	for <rps-archive@lists.ietf.org>; Fri, 8 Jan 1999 03:47:07 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id AAA05497
	for rps-outgoing; Fri, 8 Jan 1999 00:27:13 -0800 (PST)
Received: from mail.cybermax.net (root@mail.cybermax.net [207.19.133.6])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id AAA05482;
	Fri, 8 Jan 1999 00:27:05 -0800 (PST)
Received: from [207.240.233.21] (01-021.012.popsite.net [207.240.233.21])
	by mail.cybermax.net (8.8.5/8.8.5) with ESMTP id DAA21986;
	Fri, 8 Jan 1999 03:23:41 -0500 (EST)
Message-Id: <v03010d06b2ba96384d6e@[207.240.233.71]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Priority: 1 (Highest)
Date: Fri, 8 Jan 1999 03:00:08 -0400
To: Tempting Tear-Outs <temptingtearouts@1stconnect.com>
From: Tempting Tear-Outs <temptingtearouts@1stconnect.com>
Subject: >>>>>>  L@@K!    Amazing Free Offer!!!   Unbelievable, but True!
 <<<<<<<   83
Sender: owner-rps@ISI.EDU
Precedence: rps-list

To be removed from our mailing list, please send email to:
temptingtearouts@1stconnect.com with the subject line of "remove."

FOR MORE INFO:   please "cut out" the below form on the "cut" lines shown,
and fax it, for the fastest reply to:                1-718-227-9125   (this
is a fax # in the USA)

or send via smail (first class mail or airmail) to:
                                         Tempting Tear-Outs
                                         Att. Free-catalogue-by-email Dept
                                         3835 Richmond Ave.  Suite #200
                                         Staten Island NY  10312-3828
                                         USA

SORRY, BUT.... our software is not set up to accept the below form via
return email;   WE CAN ONLY acknowledge forms sent in via fax or smail.

--> IMPORTANT complete directions, to ensure that you get a reply, and more
info follow, below the reply form and the catalogue options.


*------------cut here/begin-------------------------------------------*

Name (First Middle Last):
Internet email address:
Smail home address:
City-State-Zip:
Country:
Work Tel. #:
Work Fax #:
Home Tel. #:
Home Fax #:
Cellular (Mobile) Tel. #:
Beeper (Pager) Tel. #:

How did you hear about us (name of person/company who referred you or the
area of
the internet that you saw us mentioned in):  Referred by:  Tempting
Tear-Outs
010699-ls83-lafoubt-la

Name of USA mags you currently get on the newsstand or in the store:

Name of USA mags you currently get on a subscription basis, through the mail:

Name of USA mags you would like price quotes on when we call you:

Catalogue version desired (list number of choice below):

*------------cut here/end--------------------------------------------*



CATALOGUE VERSION CHOICES:

1.  This version can be read by everyone, no matter what type of
     computer you use, or what type of software you use.  It is a simple
     format, with just our entire catalogue pasted into the body of a
     single email message, 316K in size.  If you use pine or elm on a unix
     system or an advanced software version such as Eudora Pro 3.0 or
     later, you will most likely receive it as a single email message.
     However, if your software limits incoming email messages to a
     certain size, say 32K or so, then your software will split it into
     multiple email message parts.   Whether you receive it as a single
     email message or multiple part email messages, you can easily
     paste it into one whole text document with your word processor, in
     about 10 minutes or so.
2.  For more advanced computer users:  attached plain ascii text file
     ~316K - you must know how to download an attached text file and
     then be able to locate it on your hard drive or system home
     directory;  it can then be opened with any pc or mac word processing
     software.  If in doubt, don't ask for this version.  This isn't for
     internet *newbies.* Better to order option 1 and spend a few minutes
     pasting them into one whole text document with your word processor,
     than to waste hours trying to figure how to deal with this option.
     This version is great for doing keyword searches and jumping around
     within the catalogue with your word processing software, if your
     normal email reading software doesn't allow this.


VERY IMPORTANT DIRECTIONS TO ENSURE THAT YOU GET A REPLY:

1.   you must call from an "unblocked number," ie. one that is not blocked
from caller id.  We are very sorry for this requirement, but our fax
software requires this before it allows an incoming fax call to connect.
If you have a blocked number, you must first unblock it.  In most cases
this means dialing *82 from a touch-tone phone (or 1182 from a rotary
phone) before you dial 1-718-227-9125.     NOTE:  If you are not sure if
your number is blocked, just try dialing our fax # normally.  If you don't
get a recording telling you your number is blocked, your number has been
transmitted and you may press the start button on your fax when you hear
the fax tone from our fax.
2.   no reply forms can be accepted by email....only via fax or smail.
3.   your form must be typewritten or printed out on your computer printer
before you fax it;  sorry, but *no* handwritten forms will be acknowledged.
If you can't find someone with a typewriter or a computer printer, we
apologize for not being able to reply to you.
4.   faxes with cover pages will be rejected.  You must send *only* the
reply form.
5.   forms not *completely* filled in will not be acknowledged.
6.   you will receive a reply within 1 business day directly from the
company making the offer via email.  Therefore you must have an email
address.  If you read this message, then you must have an email address, or
access to one, at least.   :-)
7.   your fax must not exceed 1 page in length.   Faxes of 2 or more pages
will be sensed, then auto-terminated and deleted.  Your fax goes directly
onto our 5.0 gigabyte hard drive and we must limit all incoming faxes to 1
page.
8.   all faxes must begin with:
*------------cut here/begin-------------------------------------------*
and must end with:
*------------cut here/end--------------------------------------------*
9. Any fax not conforming to this format will be sensed by our software,
then auto-terminated and deleted from the hard drive, before any human ever
gets to see it.
10. The type on your fax must be dark and legible.   If in doubt, please
print it out darker before faxing it in.  If we can't read it, we can't
reply to you or send you our FREE catalogue.     :-(
11.  If this all seems too complicated for faxing, just do it the old
fashioned way via smail!!!


WHO WE ARE:

Tempting Tear-Outs is an advertising company that brings potential new
customers to the companies they advertise for.

MORE ABOUT THE COMPANY MAKING THE FREE OFFER:

The company making the offer is a magazine subscription agency based in the
USA.  They have over 1,100 popular USA titles available to be shipped to
*any* country, including of course, to anywhere in the USA!    They offer a
FREE 1 yr. subscription to your choice of over 200 of the titles in their
catalogue to any new customer using them for the first time.       The
dollar value of the freebies, based on the subscription prices directly
from the publishers, ranges from $6.97 all the way up to $50.00!

For new customers in the USA, there is no charge for FPH (foreign postage &
handling), so the freebie is 100% free!   For new customers living
overseas, the only charge on the freebie would be for the FPH (foreign
postage & handling).

Their president has been in the magazine subscription business since 1973
and they are very customer-service oriented.   They will even help you with
address changes on your magazines, even if you move from one country to
another country.   They have thousands of happy customers in over 59
countries.

Their price guarantee is very simple:       they guarantee that their
subscription prices are the lowest available and they will BEAT any
legitimate, verifiable offer before you pay them or match it afterwards, by
refunding you the difference in price PLUS the cost of the postage stamp
you would use sending in the special offer to them, even 6 months after you
pay them, as long as it was current at the time of your offer.    Does that
sound fair?       Wouldn't it be great if everything you bought came with
that price guarantee?

Sometimes they are less than half of the next best deal out there,
sometimes just a little cheaper, but always you get the lowest rates
without having to shop around.     With 1,100+ titles on their list, they
would like to think that they have also the best selection around!

Within the USA, for their USA customers, they are cheaper than all their
competitors and even the publishers themselves.  This is their price
guarantee.         The 1 yr. freebie that you get with your first order is
completely free!

Overseas, (even after you factor in the cost of the FPH (foreign postage &
handling) and the conversion from USA Dollars to your currency), on the
average, they are generally around one-fourth to one-half of what the
newsstands overseas charge locally for USA magazines.  On some titles they
are as little as one-tenth of what the newsstands charge.  They are also
the cheapest subscription source for delivery overseas, including directly
from the publishers themselves!   Some publishers don't even offer
subscriptions overseas.........but overseas subscriptions are this
company's specialty!  They feel that magazines should not be a luxury
overseas.   In the USA, people buy magazines and then toss them after
reading them for just a few minutes or hours.  They are so cheap in the
USA!   Well, this company would like to make it the same way for their
overseas customers.  They are also cheaper than all their competitors in
the USA and overseas, including the publishers themselves!   It is also
*highly unlikely* you will find any of their USA competitors calling you
overseas, in order to offer that personal touch, just to sell you a couple
of magazines!  But that is what this company specializes in and loves
doing!     Around one-half their business comes from overseas, so they are
very patient with new customers who only speak limited English as a 2nd
language.    Subscription prices quoted for overseas consist of the
subscription price, plus the FPH.   You add the two together and that is
your total cost.   The exception is the 1 yr. freebie you get with your
first order.   On that title, you pay *only* the FPH for the 1 yr. term.

Their prices are so cheap because when you deal with them, you cut-out all
the middlemen.


HERE IS HOW YOU CAN GET MORE INFO AND GET STARTED WITH THEM:

Simply fax or smail back to us the reply form listed at the top of this
message.   We will then forward your form on to the subscription agency.
They will then email their "big and juicy" catalogue to you, in whichever
of the two formats you chose.   The catalogue is FREE and makes for hours
of fascinating reading, on its own. It includes the complete list of
freebies, a complete list of all the titles they sell, as well as detailed
descriptions on most of the titles, along with lists of titles by category
of interest and their terms of sale.

They will then give you a friendly, no-pressure, no obligation, 5-minute
call to go over how they work and to answer any questions that you might
have, as well as give you up-to-the minute price quotes on any titles you
might be considering.     They will call you in whatever country you live
in, taking the time difference into account.        As they like to
emphasize the personal touch they give to each new customer, all first-time
orders can only be done via phone, so they can answer all your questions
completely and personally.   Once you have placed your first order via
phone, you will be able to place future orders and make inquiries on your
account, get price quotes, etc., all via email, if that is most convenient
for you.

Within the USA, they accept payment via check over the phone, Mastercard,
Visa, American Express, Diner's Club and Carte Blanche.    Overseas, they
accept Mastercard, Visa, American Express, Diner's Club and Carte Blanche,
even if your credit card is a local one in local currency (that most
merchants in the USA would not normally be willing to accept).

That's our introduction of our client that we represent.   We hope that we
have piqued your interest and that you will take the next step to get their
free catalogue!   Thank you for your time and interest.

--
Tempting Tear-Outs.
For more info on advertising rates, please write us on your company
letterhead, w/business card, via smail to:   Tempting Tear-Outs, 3835
Richmond Ave. Suite #200, Staten Island NY  10312-3828, USA.




From rps-owner@ISI.EDU  Tue Jan 12 20:27:55 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id UAA27670
	for <rps-archive@lists.ietf.org>; Tue, 12 Jan 1999 20:27:55 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id RAA16817
	for rps-outgoing; Tue, 12 Jan 1999 17:09:05 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id RAA16812
	for <rps@zephyr.isi.edu>; Tue, 12 Jan 1999 17:09:04 -0800 (PST)
Received: from brookfield.ans.net (brookfield-ef0.brookfield.ans.net [204.148.1.20])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id RAA14750
	for <rps@isi.edu>; Tue, 12 Jan 1999 17:09:01 -0800 (PST)
Received: from brookfield.ans.net (localhost.brookfield.ans.net [127.0.0.1])
	by brookfield.ans.net (8.8.8/8.8.8) with ESMTP id UAA19310;
	Tue, 12 Jan 1999 20:08:49 -0500 (EST)
	(envelope-from curtis@brookfield.ans.net)
Message-Id: <199901130108.UAA19310@brookfield.ans.net>
To: Harald Alvestrand <Harald.Alvestrand@maxware.no>,
        Bert Wijnen <wijnen@vnet.ibm.com>
cc: curtis@ans.net, rps@ISI.EDU
Reply-To: curtis@ans.net
Subject: RPS Work Group Charter
Date: Tue, 12 Jan 1999 20:08:49 -0500
From: Curtis Villamizar <curtis@brookfield.ans.net>
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Harald, Bert,

Comments from the Work Group during the prior meeting at Orlando and
comments made since on the mailing list are reflected in the revised
RPS work group charter below.  The last call comment period was closed
on Jan 8, 1999 with no unaddressed comments.  The work group appears
to have strong concesus on the revised charter as it stands below.

Curtis


  Routing Policy System (rps)
   ---------------------------

   Charter
   Last Modified: January 12, 1999

   Current Status: Active Working Group

   Chair(s):
       Cengiz Alaettinoglu <cengiz@isi.edu>
       Curtis Villamizar <curtis@ans.net>

   Operations and Management Area Director(s):
       Harald Alvestrand  <Harald.Alvestrand@maxware.no>
       Bert Wijnen  <wijnen@vnet.ibm.com>

   Operations and Management Area Advisor:
       Bert Wijnen  <wijnen@vnet.ibm.com>

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

  Description of Working Group:

  The Routing Policy System Working Group intends to provide
  standardization of protocols and recommended practices neccesary to
  support interoperability of the Internet Routing Registry (IRR).  The
  IRR has been in use since 1995 based initially on the RIPE-181 policy
  language.

  The activities of the RPS Working Group shall include (1) defining a
  language, referred to as Routing Policy Specification Language (RPSL),
  for describing routing policy constraints, (2) defining a simple and
  robust distributed registry model for publishing routing policy
  constraints, and (3) providing a forum for the discussion of tools
  for analysing registered policy constraints, for checking global
  consistency, for generating router configurations, and for diagnosing
  operational routing problems.

   Goals and Milestones:

     Dec 1998	Reissue RPSL as a Proposed Standard with modifications
  		resulting from deployment experience.

     Apr 1999	Advance draft-ietf-rps-appl-rpsl to Informational and
  		withdraw draft-ietf-rps-transition.

     Apr 1999	Advance draft-ietf-rps-dbsec-pgp-authent to Proposed
  		Standard.

     Apr 1999	Advance draft-ietf-rps-auth to Proposed Standard. 

     Aug 1999	Advance draft-ietf-rps-dist to Proposed Standard.

     Dec 1999   Advance RPSL to Draft Standard.

   Internet-Drafts:

    Posted   Revised       I-D Title  <Filename>
    ------   -------   ------------------------------------------
   Mar 1997  Nov 1998  <draft-ietf-rps-transition-02.txt>
  		       RIPE-181 to RPSL Transition Plan

   Mar 1997  Jul 1998  <draft-ietf-rps-appl-rpsl-02.txt,.ps>
  		       Using RPSL in Practice

   Mar 1998  May 1998  <draft-ietf-rps-auth-01.txt,.ps>
  		       Routing Policy System Security

   Sep 1998  Sep 1998  <draft-ietf-rps-dist-00.txt,.ps>
                       Distributed Routing Policy System

   Nov 1998  Nov 1998  <draft-ietf-rps-appl-rpsl-03.txt,.ps>
                       Using RPSL in Practice

   Nov 1998  Nov 1998  <draft-ietf-rps-dbsec-pgp-authent-00.txt>
                       PGP authentication for RIPE database updates

   Nov 1998  Nov 1998  <draft-ietf-rps-rpsl-v2-00.txt,.ps>
                       Routing Policy Specification Language (RPSL)

   Request For Comments:

    RFC  Stat Published       Title
  ------- -- ----------     -----------------------------------------
  RFC2280 PS   Jan 1998     Routing Policy Specification Language (RPSL)


From rps-owner@ISI.EDU  Wed Jan 13 03:25:26 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id DAA08546
	for <rps-archive@lists.ietf.org>; Wed, 13 Jan 1999 03:25:26 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id AAA00539
	for rps-outgoing; Wed, 13 Jan 1999 00:10:57 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id AAA00534
	for <rps@zephyr.isi.edu>; Wed, 13 Jan 1999 00:10:56 -0800 (PST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id AAA06490
	for <rps@isi.edu>; Wed, 13 Jan 1999 00:10:53 -0800 (PST)
Received: from alden (hta@ALDEN.maxware.no [10.128.1.228])
	by dokka.maxware.no (8.8.7/8.8.7) with SMTP id JAA27594;
	Wed, 13 Jan 1999 09:10:43 +0100
Message-Id: <3.0.2.32.19990113085008.01dbfda0@dokka.maxware.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32)
Date: Wed, 13 Jan 1999 08:50:08 +0100
To: curtis@ans.net, Bert Wijnen <wijnen@vnet.ibm.com>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: RPS Work Group Charter
Cc: iesg-secretary@ietf.org, rps@ISI.EDU
In-Reply-To: <199901130108.UAA19310@brookfield.ans.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-rps@ISI.EDU
Precedence: rps-list

Thanks Curtis - Steve, I think we can accept this as "minor changes",
and not have to wait for an IESG review in 2 weeks.

Please update and forward as appropriate.

I assume that the first milestone is "Jan 1999"; you still have
18 days to make it....

                        Harald A


At 20:08 12.01.99 -0500, Curtis Villamizar wrote:
>
>Harald, Bert,
>
>Comments from the Work Group during the prior meeting at Orlando and
>comments made since on the mailing list are reflected in the revised
>RPS work group charter below.  The last call comment period was closed
>on Jan 8, 1999 with no unaddressed comments.  The work group appears
>to have strong concesus on the revised charter as it stands below.
>
>Curtis
>
>
>  Routing Policy System (rps)
>   ---------------------------
>
>   Charter
>   Last Modified: January 12, 1999
>
>   Current Status: Active Working Group
>
>   Chair(s):
>       Cengiz Alaettinoglu <cengiz@isi.edu>
>       Curtis Villamizar <curtis@ans.net>
>
>   Operations and Management Area Director(s):
>       Harald Alvestrand  <Harald.Alvestrand@maxware.no>
>       Bert Wijnen  <wijnen@vnet.ibm.com>
>
>   Operations and Management Area Advisor:
>       Bert Wijnen  <wijnen@vnet.ibm.com>
>
>   Mailing Lists:
>       General Discussion:rps@isi.edu
>       To Subscribe:      rps-request@isi.edu
>       Archive:           ftp://ftp.isi.edu/rps
>
>  Description of Working Group:
>
>  The Routing Policy System Working Group intends to provide
>  standardization of protocols and recommended practices neccesary to
>  support interoperability of the Internet Routing Registry (IRR).  The
>  IRR has been in use since 1995 based initially on the RIPE-181 policy
>  language.
>
>  The activities of the RPS Working Group shall include (1) defining a
>  language, referred to as Routing Policy Specification Language (RPSL),
>  for describing routing policy constraints, (2) defining a simple and
>  robust distributed registry model for publishing routing policy
>  constraints, and (3) providing a forum for the discussion of tools
>  for analysing registered policy constraints, for checking global
>  consistency, for generating router configurations, and for diagnosing
>  operational routing problems.
>
>   Goals and Milestones:
>
>     Dec 1998	Reissue RPSL as a Proposed Standard with modifications
>  		resulting from deployment experience.
>
>     Apr 1999	Advance draft-ietf-rps-appl-rpsl to Informational and
>  		withdraw draft-ietf-rps-transition.
>
>     Apr 1999	Advance draft-ietf-rps-dbsec-pgp-authent to Proposed
>  		Standard.
>
>     Apr 1999	Advance draft-ietf-rps-auth to Proposed Standard. 
>
>     Aug 1999	Advance draft-ietf-rps-dist to Proposed Standard.
>
>     Dec 1999   Advance RPSL to Draft Standard.
>
>   Internet-Drafts:
>
>    Posted   Revised       I-D Title  <Filename>
>    ------   -------   ------------------------------------------
>   Mar 1997  Nov 1998  <draft-ietf-rps-transition-02.txt>
>  		       RIPE-181 to RPSL Transition Plan
>
>   Mar 1997  Jul 1998  <draft-ietf-rps-appl-rpsl-02.txt,.ps>
>  		       Using RPSL in Practice
>
>   Mar 1998  May 1998  <draft-ietf-rps-auth-01.txt,.ps>
>  		       Routing Policy System Security
>
>   Sep 1998  Sep 1998  <draft-ietf-rps-dist-00.txt,.ps>
>                       Distributed Routing Policy System
>
>   Nov 1998  Nov 1998  <draft-ietf-rps-appl-rpsl-03.txt,.ps>
>                       Using RPSL in Practice
>
>   Nov 1998  Nov 1998  <draft-ietf-rps-dbsec-pgp-authent-00.txt>
>                       PGP authentication for RIPE database updates
>
>   Nov 1998  Nov 1998  <draft-ietf-rps-rpsl-v2-00.txt,.ps>
>                       Routing Policy Specification Language (RPSL)
>
>   Request For Comments:
>
>    RFC  Stat Published       Title
>  ------- -- ----------     -----------------------------------------
>  RFC2280 PS   Jan 1998     Routing Policy Specification Language (RPSL)
>
-- 
Harald Tveit Alvestrand, Maxware, Norway
Harald.Alvestrand@maxware.no



From rps-owner@ISI.EDU  Wed Jan 13 13:05:09 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA13352
	for <rps-archive@lists.ietf.org>; Wed, 13 Jan 1999 13:05:08 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id JAA17452
	for rps-outgoing; Wed, 13 Jan 1999 09:40:07 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id JAA17447
	for <rps@zephyr.isi.edu>; Wed, 13 Jan 1999 09:40:05 -0800 (PST)
Received: from dog.isi.edu (cengiz@dog-h.isi.edu [128.9.100.4])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA02613
	for <rps@ISI.EDU>; Wed, 13 Jan 1999 09:40:03 -0800 (PST)
Received: (from cengiz@localhost)
	by dog.isi.edu (8.8.7/8.8.7) id JAA01796;
	Wed, 13 Jan 1999 09:37:22 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 13 Jan 1999 09:37:22 -0800 (PST)
To: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Cc: curtis@ans.net, Bert Wijnen <wijnen@vnet.ibm.com>, iesg-secretary@ietf.org,
        rps@ISI.EDU
Subject: Re: RPS Work Group Charter
In-Reply-To: <3.0.2.32.19990113085008.01dbfda0@dokka.maxware.no>
References: <199901130108.UAA19310@brookfield.ans.net>
	<3.0.2.32.19990113085008.01dbfda0@dokka.maxware.no>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13980.55671.135841.521404@dog.isi.edu>
Reply-to: cengiz@ISI.EDU
X-Organisation: USC / Information Sciences Institute
X-Phone: +1 (310) 822 1511 x219
X-Fax: +1 (310) 823 6714
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Harald Tveit Alvestrand (Harald@Alvestrand.no) on January 13:
> Thanks Curtis - Steve, I think we can accept this as "minor changes",
> and not have to wait for an IESG review in 2 weeks.
> 
> Please update and forward as appropriate.
> 
> I assume that the first milestone is "Jan 1999"; you still have
> 18 days to make it....

It will be coming this week, perhaps even today. I wanted to implement 
RPSL 100% and append the verified bison rules as the grammar. I am
almost done.

> 
>                         Harald A
> 
> 
> At 20:08 12.01.99 -0500, Curtis Villamizar wrote:
> >
> >Harald, Bert,
> >
> >Comments from the Work Group during the prior meeting at Orlando and
> >comments made since on the mailing list are reflected in the revised
> >RPS work group charter below.  The last call comment period was closed
> >on Jan 8, 1999 with no unaddressed comments.  The work group appears
> >to have strong concesus on the revised charter as it stands below.
> >
> >Curtis
> >
> >
> >  Routing Policy System (rps)
> >   ---------------------------
> >
> >   Charter
> >   Last Modified: January 12, 1999
> >
> >   Current Status: Active Working Group
> >
> >   Chair(s):
> >       Cengiz Alaettinoglu <cengiz@isi.edu>
> >       Curtis Villamizar <curtis@ans.net>
> >
> >   Operations and Management Area Director(s):
> >       Harald Alvestrand  <Harald.Alvestrand@maxware.no>
> >       Bert Wijnen  <wijnen@vnet.ibm.com>
> >
> >   Operations and Management Area Advisor:
> >       Bert Wijnen  <wijnen@vnet.ibm.com>
> >
> >   Mailing Lists:
> >       General Discussion:rps@isi.edu
> >       To Subscribe:      rps-request@isi.edu
> >       Archive:           ftp://ftp.isi.edu/rps
> >
> >  Description of Working Group:
> >
> >  The Routing Policy System Working Group intends to provide
> >  standardization of protocols and recommended practices neccesary to
> >  support interoperability of the Internet Routing Registry (IRR).  The
> >  IRR has been in use since 1995 based initially on the RIPE-181 policy
> >  language.
> >
> >  The activities of the RPS Working Group shall include (1) defining a
> >  language, referred to as Routing Policy Specification Language (RPSL),
> >  for describing routing policy constraints, (2) defining a simple and
> >  robust distributed registry model for publishing routing policy
> >  constraints, and (3) providing a forum for the discussion of tools
> >  for analysing registered policy constraints, for checking global
> >  consistency, for generating router configurations, and for diagnosing
> >  operational routing problems.
> >
> >   Goals and Milestones:
> >
> >     Dec 1998	Reissue RPSL as a Proposed Standard with modifications
> >  		resulting from deployment experience.
> >
> >     Apr 1999	Advance draft-ietf-rps-appl-rpsl to Informational and
> >  		withdraw draft-ietf-rps-transition.
> >
> >     Apr 1999	Advance draft-ietf-rps-dbsec-pgp-authent to Proposed
> >  		Standard.
> >
> >     Apr 1999	Advance draft-ietf-rps-auth to Proposed Standard. 
> >
> >     Aug 1999	Advance draft-ietf-rps-dist to Proposed Standard.
> >
> >     Dec 1999   Advance RPSL to Draft Standard.
> >
> >   Internet-Drafts:
> >
> >    Posted   Revised       I-D Title  <Filename>
> >    ------   -------   ------------------------------------------
> >   Mar 1997  Nov 1998  <draft-ietf-rps-transition-02.txt>
> >  		       RIPE-181 to RPSL Transition Plan
> >
> >   Mar 1997  Jul 1998  <draft-ietf-rps-appl-rpsl-02.txt,.ps>
> >  		       Using RPSL in Practice
> >
> >   Mar 1998  May 1998  <draft-ietf-rps-auth-01.txt,.ps>
> >  		       Routing Policy System Security
> >
> >   Sep 1998  Sep 1998  <draft-ietf-rps-dist-00.txt,.ps>
> >                       Distributed Routing Policy System
> >
> >   Nov 1998  Nov 1998  <draft-ietf-rps-appl-rpsl-03.txt,.ps>
> >                       Using RPSL in Practice
> >
> >   Nov 1998  Nov 1998  <draft-ietf-rps-dbsec-pgp-authent-00.txt>
> >                       PGP authentication for RIPE database updates
> >
> >   Nov 1998  Nov 1998  <draft-ietf-rps-rpsl-v2-00.txt,.ps>
> >                       Routing Policy Specification Language (RPSL)
> >
> >   Request For Comments:
> >
> >    RFC  Stat Published       Title
> >  ------- -- ----------     -----------------------------------------
> >  RFC2280 PS   Jan 1998     Routing Policy Specification Language (RPSL)
> >
> -- 
> Harald Tveit Alvestrand, Maxware, Norway
> Harald.Alvestrand@maxware.no


Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California


From rps-owner@ISI.EDU  Fri Jan 15 03:09:58 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id DAA03054
	for <rps-archive@lists.ietf.org>; Fri, 15 Jan 1999 03:09:57 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id XAA13888
	for rps-outgoing; Thu, 14 Jan 1999 23:50:55 -0800 (PST)
Received: from mailhost.axime.com (net01.axime.com [160.92.120.1])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id XAA13873;
	Thu, 14 Jan 1999 23:50:49 -0800 (PST)
Received: from [169.132.119.90] (ppp-18.ts-2.fpk.idt.net [169.132.119.90]) by mailhost.axime.com (8.8.8/[Atos MultiMedia]) with ESMTP id IAA23395; Fri, 15 Jan 1999 08:46:01 +0100 (MET)
Message-Id: <v03010d51b2c459b87fb7@[internet.email]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Approved-by: Tempting Tear-Outs for general release
X-Priority: 1 (Highest)
Date: Thu, 14 Jan 1999 22:44:31 -0400
To: Tempting Tear-Outs <temptingtearouts@1stconnect.com>
From: Tempting Tear-Outs <temptingtearouts@1stconnect.com>
Subject: Hi
Sender: owner-rps@ISI.EDU
Precedence: rps-list

===>> FREE 1 yr USA Magazine Sub sent worldwide-200+ Choices!  Up to $81.00
value!

To be removed from our mailing list, please send email to:
temptingtearouts@1stconnect.com with the subject line of "remove."


FOR MORE INFO:   please "cut out" the below form on the "cut" lines shown,
and fax it, for the fastest reply to:                1-718-227-9125   (this
is a fax # in the USA)

or send via smail (first class mail or airmail) to:
                                         Tempting Tear-Outs
                                         Att. Free-catalogue-by-email Dept
                                         3835 Richmond Ave.  Suite #200
                                         Staten Island NY  10312-3828
                                         USA

SORRY, BUT.... our software is not set up to accept the below form via
return email;   WE CAN ONLY acknowledge forms sent in via fax or smail.

--> IMPORTANT complete directions, to ensure that you get a reply, and more
info follow, below the reply form and the catalogue options.


*------------cut here/begin-------------------------------------------*

Name (First Middle Last):
Internet email address:
Smail home address:
City-State-Zip:
Country:
Work Tel. #:
Work Fax #:
Home Tel. #:
Home Fax #:
Cellular (Mobile) Tel. #:
Beeper (Pager) Tel. #:

How did you hear about us (name of person/company who referred you or the
area of
the internet that you saw us mentioned in):  Referred by:  Tempting
Tear-Outs
011499-l-hi

Name of USA mags you currently get on the newsstand or in the store:

Name of USA mags you currently get on a subscription basis, through the mail:

Name of USA mags you would like price quotes on when we call you:

Catalogue version desired (list number of choice below):

*------------cut here/end--------------------------------------------*



CATALOGUE VERSION CHOICES:

1.  This version can be read by everyone, no matter what type of
     computer you use, or what type of software you use.  It is a simple
     format, with just our entire catalogue pasted into the body of a
     single email message, 316K in size.  If you use pine or elm on a unix
     system or an advanced software version such as Eudora Pro 3.0 or
     later, you will most likely receive it as a single email message.
     However, if your software limits incoming email messages to a
     certain size, say 32K or so, then your software will split it into
     multiple email message parts.   Whether you receive it as a single
     email message or multiple part email messages, you can easily
     paste it into one whole text document with your word processor, in
     about 10 minutes or so.
2.  For more advanced computer users:  attached plain ascii text file
     ~316K - you must know how to download an attached text file and
     then be able to locate it on your hard drive or system home
     directory;  it can then be opened with any pc or mac word processing
     software.  If in doubt, don't ask for this version.  This isn't for
     internet *newbies.* Better to order option 1 and spend a few minutes
     pasting them into one whole text document with your word processor,
     than to waste hours trying to figure how to deal with this option.
     This version is great for doing keyword searches and jumping around
     within the catalogue with your word processing software, if your
     normal email reading software doesn't allow this.


VERY IMPORTANT DIRECTIONS TO ENSURE THAT YOU GET A REPLY:

1.   you must call from an "unblocked number," ie. one that is not blocked
from caller id.  We are very sorry for this requirement, but our fax
software requires this before it allows an incoming fax call to connect.
If you have a blocked number, you must first unblock it.  In most cases
this means dialing *82 from a touch-tone phone (or 1182 from a rotary
phone) before you dial 1-718-227-9125.     NOTE:  If you are not sure if
your number is blocked, just try dialing our fax # normally.  If you don't
get a recording telling you your number is blocked, your number has been
transmitted and you may press the start button on your fax when you hear
the fax tone from our fax.
2.   no reply forms can be accepted by email....only via fax or smail.
3.   your form must be typewritten or printed out on your computer printer
before you fax it;  sorry, but *no* handwritten forms will be acknowledged.
If you can't find someone with a typewriter or a computer printer, we
apologize for not being able to reply to you.
4.   faxes with cover pages will be rejected.  You must send *only* the
reply form.
5.   forms not *completely* filled in will not be acknowledged.
6.   you will receive a reply within 1 business day directly from the
company making the offer via email.  Therefore you must have an email
address.  If you read this message, then you must have an email address, or
access to one, at least.   :-)
7.   your fax must not exceed 1 page in length.   Faxes of 2 or more pages
will be sensed, then auto-terminated and deleted.  Your fax goes directly
onto our 5.0 gigabyte hard drive and we must limit all incoming faxes to 1
page.
8.   all faxes must begin with:
*------------cut here/begin-------------------------------------------*
and must end with:
*------------cut here/end--------------------------------------------*
9. Any fax not conforming to this format will be sensed by our software,
then auto-terminated and deleted from the hard drive, before any human ever
gets to see it.
10. The type on your fax must be dark and legible.   If in doubt, please
print it out darker before faxing it in.  If we can't read it, we can't
reply to you or send you our FREE catalogue.     :-(
11.  If this all seems too complicated for faxing, just do it the old
fashioned way via smail!!!


WHO WE ARE:

Tempting Tear-Outs is an advertising company that brings potential new
customers to the companies they advertise for.

MORE ABOUT THE COMPANY MAKING THE FREE OFFER:

The company making the offer is a magazine subscription agency based in the
USA.  They have over 1,100 popular USA titles available to be shipped to
*any* country, including of course, to anywhere in the USA!    They offer a
FREE 1 yr. subscription to your choice of over 200 of the titles in their
catalogue to any new customer using them for the first time.       The
dollar value of the freebies, based on the subscription prices directly
from the publishers, ranges from $6.97 all the way up to $50.00!

For new customers in the USA, there is no charge for FPH (foreign postage &
handling), so the freebie is 100% free!   For new customers living
overseas, the only charge on the freebie would be for the FPH (foreign
postage & handling).

Their president has been in the magazine subscription business since 1973
and they are very customer-service oriented.   They will even help you with
address changes on your magazines, even if you move from one country to
another country.   They have thousands of happy customers in over 59
countries.

Their price guarantee is very simple:       they guarantee that their
subscription prices are the lowest available and they will BEAT any
legitimate, verifiable offer before you pay them or match it afterwards, by
refunding you the difference in price PLUS the cost of the postage stamp
you would use sending in the special offer to them, even 6 months after you
pay them, as long as it was current at the time of your offer.    Does that
sound fair?       Wouldn't it be great if everything you bought came with
that price guarantee?

Sometimes they are less than half of the next best deal out there,
sometimes just a little cheaper, but always you get the lowest rates
without having to shop around.     With 1,100+ titles on their list, they
would like to think that they have also the best selection around!

Within the USA, for their USA customers, they are cheaper than all their
competitors and even the publishers themselves.  This is their price
guarantee.         The 1 yr. freebie that you get with your first order is
completely free!

Overseas, (even after you factor in the cost of the FPH (foreign postage &
handling) and the conversion from USA Dollars to your currency), on the
average, they are generally around one-fourth to one-half of what the
newsstands overseas charge locally for USA magazines.  On some titles they
are as little as one-tenth of what the newsstands charge.  They are also
the cheapest subscription source for delivery overseas, including directly
from the publishers themselves!   Some publishers don't even offer
subscriptions overseas.........but overseas subscriptions are this
company's specialty!  They feel that magazines should not be a luxury
overseas.   In the USA, people buy magazines and then toss them after
reading them for just a few minutes or hours.  They are so cheap in the
USA!   Well, this company would like to make it the same way for their
overseas customers.  They are also cheaper than all their competitors in
the USA and overseas, including the publishers themselves!   It is also
*highly unlikely* you will find any of their USA competitors calling you
overseas, in order to offer that personal touch, just to sell you a couple
of magazines!  But that is what this company specializes in and loves
doing!     Around one-half their business comes from overseas, so they are
very patient with new customers who only speak limited English as a 2nd
language.    Subscription prices quoted for overseas consist of the
subscription price, plus the FPH.   You add the two together and that is
your total cost.   The exception is the 1 yr. freebie you get with your
first order.   On that title, you pay *only* the FPH for the 1 yr. term.

Their prices are so cheap because when you deal with them, you cut-out all
the middlemen.


HERE IS HOW YOU CAN GET MORE INFO AND GET STARTED WITH THEM:

Simply fax or smail back to us the reply form listed at the top of this
message.   We will then forward your form on to the subscription agency.
They will then email their "big and juicy" catalogue to you, in whichever
of the two formats you chose.   The catalogue is FREE and makes for hours
of fascinating reading, on its own. It includes the complete list of
freebies, a complete list of all the titles they sell, as well as detailed
descriptions on most of the titles, along with lists of titles by category
of interest and their terms of sale.

They will then give you a friendly, no-pressure, no obligation, 5-minute
call to go over how they work and to answer any questions that you might
have, as well as give you up-to-the minute price quotes on any titles you
might be considering.     They will call you in whatever country you live
in, taking the time difference into account.        As they like to
emphasize the personal touch they give to each new customer, all first-time
orders can only be done via phone, so they can answer all your questions
completely and personally.   Once you have placed your first order via
phone, you will be able to place future orders and make inquiries on your
account, get price quotes, etc., all via email, if that is most convenient
for you.

Within the USA, they accept payment via check over the phone, Mastercard,
Visa, American Express, Diner's Club and Carte Blanche.    Overseas, they
accept Mastercard, Visa, American Express, Diner's Club and Carte Blanche,
even if your credit card is a local one in local currency (that most
merchants in the USA would not normally be willing to accept).

That's our introduction of our client that we represent.   We hope that we
have piqued your interest and that you will take the next step to get their
free catalogue!   Thank you for your time and interest.

--
Tempting Tear-Outs.
For more info on advertising rates, please write us on your company
letterhead, w/business card, via smail to:   Tempting Tear-Outs, 3835
Richmond Ave. Suite #200, Staten Island NY  10312-3828, USA.




From rps-owner@ISI.EDU  Tue Jan 19 11:35:37 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA14649
	for <rps-archive@lists.ietf.org>; Tue, 19 Jan 1999 11:35:36 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id IAA23509
	for rps-outgoing; Tue, 19 Jan 1999 08:08:57 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id IAA23504
	for <rps@zephyr.isi.edu>; Tue, 19 Jan 1999 08:08:56 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id IAA22891
	for <rps@isi.edu>; Tue, 19 Jan 1999 08:08:55 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA13596;
	Tue, 19 Jan 1999 11:08:21 -0500 (EST)
Message-Id: <199901191608.LAA13596@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rps@ISI.EDU
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rps-rpsl-v2-01.txt,.ps
Date: Tue, 19 Jan 1999 11:08:20 -0500
Sender: owner-rps@ISI.EDU
Precedence: rps-list

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Policy System Working Group of the IETF.

	Title		: Routing Policy Specification Language (RPSL)
	Author(s)	: C. Alaettinoglu, C. Villamizar, E. Gerich, D. Kessens,   
                          D. Meyer, T. Bates, D. Karrenberg, M. Terpstra 
	Filename	: draft-ietf-rps-rpsl-v2-01.txt,.ps
	Pages		: 64
	Date		: 18-Jan-99
	
This Internet  Draft  is  the  reference document  for  the  Routing  Policy
Specification Language (RPSL). 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.
 
RPSL is a replacement for the current Internet policy specification language
known as RIPE-181 [6] or RFC-1786 [7].   RIPE-81 [8] was the first  language
deployed in the  Internet for  specifying routing policies.    It was  later
replaced by  RIPE-181 [6].    Through  operational use  of RIPE-181  it  has
become apparent that certain policies cannot be specified and a need for  an
enhanced and more generalized language is needed.  RPSL addresses RIPE-181's
limitations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rps-rpsl-v2-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rps-rpsl-v2-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rps-rpsl-v2-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990118131934.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rps-rpsl-v2-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rps-rpsl-v2-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990118131934.I-D@ietf.org>

--OtherAccess--

--NextPart--




From rps-owner@ISI.EDU  Tue Jan 19 13:19:08 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA20219
	for <rps-archive@lists.ietf.org>; Tue, 19 Jan 1999 13:19:07 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id JAA28093
	for rps-outgoing; Tue, 19 Jan 1999 09:59:14 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id JAA28088
	for <rps@zephyr.isi.edu>; Tue, 19 Jan 1999 09:59:13 -0800 (PST)
Received: from cat.isi.edu (cengiz@cat.isi.edu [128.9.160.205])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA03181
	for <rps@ISI.EDU>; Tue, 19 Jan 1999 09:59:12 -0800 (PST)
Received: (from cengiz@localhost)
	by cat.isi.edu (8.8.7/8.8.7) id JAA08999;
	Tue, 19 Jan 1999 09:59:13 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <13988.51184.864206.811856@cat.isi.edu>
Date: Tue, 19 Jan 1999 09:59:12 -0800 (PST)
To: rps@ISI.EDU
Subject: WG Last Call on draft-ietf-rps-rpsl-v2-01
X-Mailer: VM 6.63 under 20.4 "Emerald" XEmacs  Lucid
Reply-to: cengiz@ISI.EDU
X-Organisation: USC / Information Sciences Institute
X-Phone: +1 (310) 822 1511 x219
X-Fax: +1 (310) 823 6714
Sender: owner-rps@ISI.EDU
Precedence: rps-list


As we agreed in Orlando, we are going to ask IESG to advance the
following i-d to proposed standard. Please give your last minute
comments/feeback by January 29th.

   Title	: Routing Policy Specification Language (RPSL)
   Author(s)	: C. Alaettinoglu, C. Villamizar, E. Gerich, D. Kessens,   
	          D. Meyer, T. Bates, D. Karrenberg, M. Terpstra 
   Filename	: draft-ietf-rps-rpsl-v2-01.txt,.ps
   Pages	: 64
   Date		: 18-Jan-99

The changes between 00 and 01 of this document are addition of two
appendixes, one providing formal grammar rules, and one that lists the
changes since RFC 2280, deletion of withdrawn attribute and some
editorial changes (all of which we agreed in Orlando). I am attaching
the changes appendix below.

I have implemented RPSL 100% in RAToolSet/BIRD. The bison grammar
rules are straight from there.

Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California
============================================================================
C Changes from RFC 2280


RFC 2280 [3] contains  an earlier version of  RPSL. This section  summarizes
the changes since then.  They are as follows:


 o  It is  now  possible to  write  integers  as sequence  of  four  1-octet
    integers (e.g. 1.1.1.1)  or as  sequence of two  2-octet integers  (e.g.
    3561:70).  Please see Section 2.

 o  The definition of address  prefix range is extended  so that an  address
    prefix is also an address prefix range.  Please see Section 2.

 o  The semantics for a range operator  applied to a set containing  address
    prefix ranges is  defined (e.g. {30.0.0.0/8^24-28}^27-30).    Please see
    Section 2.

 o  All dates are now in UTC. Please see Section 2.

 o  Plus ('+') character is  added to space and  tab characters to split  an
    attribute's value  to multiple  lines (i.e.  by starting  the  following
    lines with  a space,  a tab  or a  plus ('+')  character).   Please  see
    Section 2.

 o  The withdrawn attribute of route class is removed from the language.




Alaettinoglu et.  al.            Expires  July 15, 1999            [Page 62]
Internet Draft                     RPSL                     January 15, 1999

 o  The syntax and semantics of union, and list types and typedef  attribute
    have changed.  Please see Section 7.

 o  In  the  initial   dictionary,  the   typedef  attribute  defining   the
    community_elm,   rp-attribute  defining  the   community  attribute   has
    changed.  Please see Section 7.

 o  The syntax and semantics of  export-comps attribute of route class  have
    changed.  Please see Section 8.

 o  Guideliness for extending RPSL is added.  Please see Section 10.

 o  Formal grammar rules are added.  Please see Appendix B.


From rps-owner@ISI.EDU  Wed Jan 20 12:24:04 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA22204
	for <rps-archive@lists.ietf.org>; Wed, 20 Jan 1999 12:24:03 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id JAA11817
	for rps-outgoing; Wed, 20 Jan 1999 09:05:40 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id JAA11811
	for <rps@zephyr.isi.edu>; Wed, 20 Jan 1999 09:05:38 -0800 (PST)
Received: from dog.isi.edu (cengiz@dog-h.isi.edu [128.9.100.4])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA28892;
	Wed, 20 Jan 1999 09:05:36 -0800 (PST)
Received: (from cengiz@localhost)
	by dog.isi.edu (8.8.7/8.8.7) id JAA00810;
	Wed, 20 Jan 1999 09:06:12 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 20 Jan 1999 09:06:10 -0800 (PST)
To: cengiz@ISI.EDU
Cc: rps@ISI.EDU
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
In-Reply-To: <13988.51184.864206.811856@cat.isi.edu>
References: <13988.51184.864206.811856@cat.isi.edu>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13990.2805.698337.12352@dog.isi.edu>
Reply-to: cengiz@ISI.EDU
X-Organisation: USC / Information Sciences Institute
X-Phone: +1 (310) 822 1511 x219
X-Fax: +1 (310) 823 6714
Sender: owner-rps@ISI.EDU
Precedence: rps-list


I realize I forgot to add one other change to the changes appendix:
For peering specification, we had two rules:
    <peer-as> [<peer-router>] [at <local-router>]
    <as-expression> [at <router-expression>]
Having these two rules leads to several reduce/reduce conflicts in
bison, with no obvious way around it. The fix is to have one rule
which supercedes the two rules:
    <as-expression> [<router-expression>] [at <router-expression>]
This is also totally backward compatible.

I am going to modify the changes appendix to include one other item
before sending it to IESG:
	o A <router-expression> is now allowed as the peer router in a
	  peering. Please see Section x.
(Along with other comments from you folks).

Cengiz

Cengiz Alaettinoglu (cengiz@ISI.EDU) on January 19:
> 
> As we agreed in Orlando, we are going to ask IESG to advance the
> following i-d to proposed standard. Please give your last minute
> comments/feeback by January 29th.
> 
>    Title	: Routing Policy Specification Language (RPSL)
>    Author(s)	: C. Alaettinoglu, C. Villamizar, E. Gerich, D. Kessens,   
> 	          D. Meyer, T. Bates, D. Karrenberg, M. Terpstra 
>    Filename	: draft-ietf-rps-rpsl-v2-01.txt,.ps
>    Pages	: 64
>    Date		: 18-Jan-99
> 
> The changes between 00 and 01 of this document are addition of two
> appendixes, one providing formal grammar rules, and one that lists the
> changes since RFC 2280, deletion of withdrawn attribute and some
> editorial changes (all of which we agreed in Orlando). I am attaching
> the changes appendix below.
> 
> I have implemented RPSL 100% in RAToolSet/BIRD. The bison grammar
> rules are straight from there.
> 
> Cengiz
> 
> -- 
> Cengiz Alaettinoglu           Information Sciences Institute
> http://www.isi.edu/~cengiz    University of Southern California
> ============================================================================
> C Changes from RFC 2280
> 
> 
> RFC 2280 [3] contains  an earlier version of  RPSL. This section  summarizes
> the changes since then.  They are as follows:
> 
> 
>  o  It is  now  possible to  write  integers  as sequence  of  four  1-octet
>     integers (e.g. 1.1.1.1)  or as  sequence of two  2-octet integers  (e.g.
>     3561:70).  Please see Section 2.
> 
>  o  The definition of address  prefix range is extended  so that an  address
>     prefix is also an address prefix range.  Please see Section 2.
> 
>  o  The semantics for a range operator  applied to a set containing  address
>     prefix ranges is  defined (e.g. {30.0.0.0/8^24-28}^27-30).    Please see
>     Section 2.
> 
>  o  All dates are now in UTC. Please see Section 2.
> 
>  o  Plus ('+') character is  added to space and  tab characters to split  an
>     attribute's value  to multiple  lines (i.e.  by starting  the  following
>     lines with  a space,  a tab  or a  plus ('+')  character).   Please  see
>     Section 2.
> 
>  o  The withdrawn attribute of route class is removed from the language.
> 
> 
> 
> 
> Alaettinoglu et.  al.            Expires  July 15, 1999            [Page 62]
> Internet Draft                     RPSL                     January 15, 1999
> 
>  o  The syntax and semantics of union, and list types and typedef  attribute
>     have changed.  Please see Section 7.
> 
>  o  In  the  initial   dictionary,  the   typedef  attribute  defining   the
>     community_elm,   rp-attribute  defining  the   community  attribute   has
>     changed.  Please see Section 7.
> 
>  o  The syntax and semantics of  export-comps attribute of route class  have
>     changed.  Please see Section 8.
> 
>  o  Guideliness for extending RPSL is added.  Please see Section 10.
> 
>  o  Formal grammar rules are added.  Please see Appendix B.


Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California


From rps-owner@ISI.EDU  Fri Jan 22 07:10:35 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA17422
	for <rps-archive@lists.ietf.org>; Fri, 22 Jan 1999 07:10:34 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id DAA15233
	for rps-outgoing; Fri, 22 Jan 1999 03:45:14 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id DAA15228
	for <rps@zephyr.isi.edu>; Fri, 22 Jan 1999 03:45:11 -0800 (PST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id DAA15713;
	Fri, 22 Jan 1999 03:45:08 -0800 (PST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id WAA25160
  (8.8.8/IDA-1.6); Fri, 22 Jan 1999 22:14:29 +1030 (CST)
Message-ID: <199901221144.WAA25160@kuji.off.connect.com.au>
To: cengiz@ISI.EDU
cc: rps@ISI.EDU
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
In-reply-to: Your message of "Tue, 19 Jan 1999 09:59:12 -0800."
             <13988.51184.864206.811856@cat.isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25158.917005469.1@connect.com.au>
Date: Fri, 22 Jan 1999 22:14:29 +1030
From: Mark Prior <mrp@connect.com.au>
Sender: owner-rps@ISI.EDU
Precedence: rps-list

      o  The withdrawn attribute of route class is removed from the language.

Being a user of the withdrawn attribute I guess I should speak up in
its defense :-) While I have previously said that I only use withdrawn
because I consider the implementation of delete to be broken it has
proved to be useful at times to have the withdrawn record "lying
around" when mistakes are made so perhaps it should survive. I would
like an automatic mechanism in the server to clean them up though as
while the record exists some other maintainer can't come along and
recreate the original record.

Mark.


From rps-owner@ISI.EDU  Fri Jan 22 16:12:41 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA03326
	for <rps-archive@lists.ietf.org>; Fri, 22 Jan 1999 16:12:40 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id MAA04185
	for rps-outgoing; Fri, 22 Jan 1999 12:42:17 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id MAA04180
	for <rps@zephyr.isi.edu>; Fri, 22 Jan 1999 12:42:16 -0800 (PST)
Received: from cat.isi.edu (cengiz@cat.isi.edu [128.9.160.205])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id MAA03279;
	Fri, 22 Jan 1999 12:42:15 -0800 (PST)
Received: (from cengiz@localhost)
	by cat.isi.edu (8.8.7/8.8.7) id MAA01275;
	Fri, 22 Jan 1999 12:42:10 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <13992.58018.357745.753680@cat.isi.edu>
Date: Fri, 22 Jan 1999 12:42:10 -0800 (PST)
To: Mark Prior <mrp@connect.com.au>
Cc: cengiz@ISI.EDU, rps@ISI.EDU
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
In-Reply-To: <199901221144.WAA25160@kuji.off.connect.com.au>
References: <13988.51184.864206.811856@cat.isi.edu>
	<199901221144.WAA25160@kuji.off.connect.com.au>
X-Mailer: VM 6.63 under 20.4 "Emerald" XEmacs  Lucid
Reply-to: cengiz@ISI.EDU
X-Organisation: USC / Information Sciences Institute
X-Phone: +1 (310) 822 1511 x219
X-Fax: +1 (310) 823 6714
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Mark Prior (mrp@connect.com.au) on January 22:
>       o  The withdrawn attribute of route class is removed from the language.
> 
> Being a user of the withdrawn attribute I guess I should speak up in
> its defense :-) While I have previously said that I only use withdrawn
> because I consider the implementation of delete to be broken it has
> proved to be useful at times to have the withdrawn record "lying
> around" when mistakes are made so perhaps it should survive. I would
> like an automatic mechanism in the server to clean them up though as
> while the record exists some other maintainer can't come along and
> recreate the original record.

Mark,

withdrawn is implementors headache. You yourself have run into
problems in some alpha software in the past.

rps-auth solves "some other maintainer can't come along and recreate
the original record" problem.

Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California


From rps-owner@ISI.EDU  Sun Jan 24 19:03:26 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id TAA05664
	for <rps-archive@lists.ietf.org>; Sun, 24 Jan 1999 19:03:25 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id PAA10076
	for rps-outgoing; Sun, 24 Jan 1999 15:44:49 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id PAA10071
	for <rps@zephyr.isi.edu>; Sun, 24 Jan 1999 15:44:48 -0800 (PST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id PAA09699;
	Sun, 24 Jan 1999 15:44:45 -0800 (PST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id KAA15957
  (8.8.8/IDA-1.6); Mon, 25 Jan 1999 10:14:12 +1030 (CST)
Message-ID: <199901242344.KAA15957@kuji.off.connect.com.au>
To: cengiz@ISI.EDU
cc: rps@ISI.EDU
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
In-reply-to: Your message of "Fri, 22 Jan 1999 12:42:10 -0800."
             <13992.58018.357745.753680@cat.isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15955.917221451.1@connect.com.au>
Date: Mon, 25 Jan 1999 10:14:11 +1030
From: Mark Prior <mrp@connect.com.au>
Sender: owner-rps@ISI.EDU
Precedence: rps-list

     rps-auth solves "some other maintainer can't come along and recreate
     the original record" problem.

I am not convinced that it will. It is fine in theory but practice
will be an entirely different matter.

In Australia there are 4 main IAPs (Connect, Optus, OzEmail and
Telstra). We each register our customers routes in the IRR (Telstra
uses CW and registers all customers under their AS while the rest of
us register in RADB). Just about none of the smaller ISPs appear to
know/care about the IRR and leave it up to the big 4 to register their
routes (it's pretty rare that an Australian ISP doesn't have a link to
at least one of the big 4). Internet charging being what it is the
smaller ISPs move around, don't send all their routes to all their
upstreams etc. If a customer connects to Connect (say) we will
register their route in RADB (under their AS). If they then get
another link to Optus then they will try to register their route but
will fail since we have already hijacked it (we get a nice message
from RADB telling us that the customer now has a link to Optus :-) Now
should the customer sometime later cancel their link to Connect we
will (currently) withdraw the route. There is no mechansim to warn
Optus that we have done this so the first they know about it is when
the customer complains.

We won't suffer from this problem since we have our own DB and only
use the RADB for info but this problem sort of forces you down that
path.

Mark.


From rps-owner@ISI.EDU  Tue Jan 26 21:08:54 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA10134
	for <rps-archive@lists.ietf.org>; Tue, 26 Jan 1999 21:08:54 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id RAA24468
	for rps-outgoing; Tue, 26 Jan 1999 17:46:37 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id RAA24463
	for <rps@zephyr.isi.edu>; Tue, 26 Jan 1999 17:46:35 -0800 (PST)
Received: from brookfield.ans.net (brookfield-ef0.brookfield.ans.net [204.148.1.20])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id RAA06074
	for <rps@isi.edu>; Tue, 26 Jan 1999 17:46:32 -0800 (PST)
Received: from brookfield.ans.net (localhost.brookfield.ans.net [127.0.0.1])
	by brookfield.ans.net (8.8.8/8.8.8) with ESMTP id UAA21233;
	Tue, 26 Jan 1999 20:46:28 -0500 (EST)
	(envelope-from curtis@brookfield.ans.net)
Message-Id: <199901270146.UAA21233@brookfield.ans.net>
To: rps@ISI.EDU
cc: curtis@ans.net
Reply-To: curtis@ans.net
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
Date: Tue, 26 Jan 1999 20:46:28 -0500
From: Curtis Villamizar <curtis@brookfield.ans.net>
Sender: owner-rps@ISI.EDU
Precedence: rps-list


   Title	: Routing Policy Specification Language (RPSL)
   Author(s)	: C. Alaettinoglu, C. Villamizar, E. Gerich, D. Kessens,   
	          D. Meyer, T. Bates, D. Karrenberg, M. Terpstra 
   Filename	: draft-ietf-rps-rpsl-v2-01.txt,.ps
   Pages	: 64
   Date		: 18-Jan-99

> I have implemented RPSL 100% in RAToolSet/BIRD. The bison grammar
> rules are straight from there.

This is really useful.  Unfortunately the names in the bison don't
match the names in the draft.  At the very minimum you need to have
comments which map each expression in the document to the bison.  For
example: 

  //// router-expression == rtr_expr ////

rahter than just:

  //// rtr_expr ////...

This way we could easily get a precise clarification from the grammar
when reading the text.

We also need definitions of the tokens.  See bleow.

>  o  All dates are now in UTC. Please see Section 2.

Grumble.  OK.

>  o  The syntax and semantics of  export-comps attribute of route class  have
>     changed.  Please see Section 8.

I don't remember any discussion of this change.  It is all wrong.  If
the scope of an aggregate is multiple providers it makes absolutely no
sense to specify the export policy of the components in the aggregate.

The export-comps is supposed to be just a list, nothing more.  If a
prefix falls under an aggregate it is omitted from any export
statements in which it would otherwise appear unless it falls within
the export-comps list for the aggregate in which case it is not
omitted.  This was the functionality agreed to.

Could you please forward any email discussing this change or restore
it to what we had agreed to before.

> I realize I forgot to add one other change to the changes appendix:
> For peering specification, we had two rules:
>     <peer-as> [<peer-router>] [at <local-router>]
>     <as-expression> [at <router-expression>]
> Having these two rules leads to several reduce/reduce conflicts in
> bison, with no obvious way around it. The fix is to have one rule
> which supercedes the two rules:
>     <as-expression> [<router-expression>] [at <router-expression>]
> This is also totally backward compatible.

This is a much needed change.  Looks a lot better.  However see below.

> I am going to modify the changes appendix to include one other item
> before sending it to IESG:
> 	o A <router-expression> is now allowed as the peer router in a
> 	  peering. Please see Section x.
> (Along with other comments from you folks).
>  
> Cengiz

Here are some comments that I've made in private exchanges.  I don't
know whether these sort of changes should go into this cut of RPSL or
go into a later version to be recycled yet again as PS.  This may
largely depend on the OPs ADs preferences.

We've been experimenting with RPSL to configure policy on
route-reflector clients to give some full routing, some partial (our
customers only or some other subset), and some just default and a few
others.  In addition there is import policy on each.  What this is
doing is moving policy for customers (mostly single homed) to the
access router rather than CPE router.  If the CPE becomes customer
managed this becomes EBGP rather than IBGP route-reflector.

One thing that would be very useful is a "filter" object that could be
referenced anywhere that <filter> appears.  This would be useful for
someone with multiple AS that all have similar import or export
policies.  We might even want to consider a "hints" attribute where we
could put such things as "route-map-name" or "prefix-list-name" for
routers that support named policy stanzas.  The hint could be used in
the simple case where an import or export just references a single
filter object otherwise ignored and ignored if the router being
configured did not support named policy stanzas.

In addition it would be useful to have a "peer-group" object that
could be used in the router-expression in <as-expression>
[<router-expression>] [at <router-expression>].  The name of the
peer-group might be used in generating router configurations that
support named peer-groups.  The alternate that we were counting on was
to use a route-set with /32s in it.  It doesn't look like this is
supported:

rtr_expr_operand: TKN_IPV4 | TKN_DNS

Since the tokens are not defined it is not entirely clear what
TKN_IPV4 and TKN_DNS are.  The text just says:

  and <router-expression-1> and <router-expression-2> are expressions
  over router IP addresses and DNS names using operators AND, OR, and
  NOT. The DNS name can only be used if there is an inet-rtr object
  for that name that binds the name to IP addresses.

It would appear that router IP addresses means fully dotted IPv4 quad.

Allowing an object named "peer-group" might be preferable to allowing
a route-set and accepting all routers falling within the route-set.
The route set would be OK too.  Adding one or the other to
rtr_expr_operand would be a good thing.  Having no ability to name
these sets will bloat our aut-nums a bit and give us cause to
preprocess aut-nums and use the source prior to preprocessing for the
actual configuration.

Neither of these changes are essential.  We can use aut-num source
prior to preprocessing in our configuration generation (as we already
do) and submit the aut-num after preprocessing if there are any
significant changes.  These aut-nums may never be submited to a
publicly readable database anyway (at least not before stripping the
route-reflector policy).  We might want to consider these two changes
for the next round of RPSL.

I'd also like to point out that as much as some people would like to
see no changes at all it is likely that we will need to have a next
round of RPSL because people are using RPSL and through using it will
come up with more efficient ways to express routing policy.

Curtis


From rps-owner@ISI.EDU  Wed Jan 27 13:19:46 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA00817
	for <rps-archive@lists.ietf.org>; Wed, 27 Jan 1999 13:19:45 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id JAA28487
	for rps-outgoing; Wed, 27 Jan 1999 09:47:45 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id JAA28475
	for <rps@zephyr.isi.edu>; Wed, 27 Jan 1999 09:47:42 -0800 (PST)
Received: from dog.isi.edu ([4.3.130.214])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA01592
	for <rps@ISI.EDU>; Wed, 27 Jan 1999 09:47:41 -0800 (PST)
Received: (from cengiz@localhost)
	by dog.isi.edu (8.8.7/8.8.7) id JAA01096;
	Wed, 27 Jan 1999 09:48:12 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 27 Jan 1999 09:48:11 -0800 (PST)
To: curtis@ans.net
Cc: rps@ISI.EDU
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
In-Reply-To: <199901270146.UAA21233@brookfield.ans.net>
References: <199901270146.UAA21233@brookfield.ans.net>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13999.18123.62615.786761@dog.isi.edu>
Reply-to: cengiz@ISI.EDU
X-Organisation: USC / Information Sciences Institute
X-Phone: +1 (310) 822 1511 x219
X-Fax: +1 (310) 823 6714
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Curtis Villamizar (curtis@brookfield.ans.net) on January 26:
> This is really useful.  Unfortunately the names in the bison don't
> match the names in the draft.  At the very minimum you need to have
> comments which map each expression in the document to the bison.  For
> example: 
> 
>   //// router-expression == rtr_expr ////
> 
> rahter than just:
> 
>   //// rtr_expr ////...
> 
> This way we could easily get a precise clarification from the grammar
> when reading the text.

grumble.
will do where possible.

> 
> We also need definitions of the tokens.  See bleow.

Tokens match the definitions in Section 2 of rpsl. Names may not match
exactly. I will also add comments on this.

> 
> >  o  All dates are now in UTC. Please see Section 2.
> 
> Grumble.  OK.
> 
> >  o  The syntax and semantics of  export-comps attribute of route class  have
> >     changed.  Please see Section 8.
> 
> I don't remember any discussion of this change.  It is all wrong.  If
> the scope of an aggregate is multiple providers it makes absolutely no
> sense to specify the export policy of the components in the aggregate.
> 
> The export-comps is supposed to be just a list, nothing more.  If a
> prefix falls under an aggregate it is omitted from any export
> statements in which it would otherwise appear unless it falls within
> the export-comps list for the aggregate in which case it is not
> omitted.  This was the functionality agreed to.
> 
> Could you please forward any email discussing this change or restore
> it to what we had agreed to before.

This was suggested by the Fore folks and was discussed in the LA IETF
WG meeting.

Please see ftp://ftp.isi.edu/rps/la-ietf-98/implementation-experience.ps

You could get the older behavior by:

	export-comps: to as-any announce <whatever>

Hence, it can not be "all wrong".  May be someone from Fore may
comment, or I can dig the mail archives if you insist.

> 
> > I realize I forgot to add one other change to the changes appendix:
> > For peering specification, we had two rules:
> >     <peer-as> [<peer-router>] [at <local-router>]
> >     <as-expression> [at <router-expression>]
> > Having these two rules leads to several reduce/reduce conflicts in
> > bison, with no obvious way around it. The fix is to have one rule
> > which supercedes the two rules:
> >     <as-expression> [<router-expression>] [at <router-expression>]
> > This is also totally backward compatible.
> 
> This is a much needed change.  Looks a lot better.  However see below.

When I did this, it was a grammar fix. I did not know there was a need 
for it. I am glad.

> 
> > I am going to modify the changes appendix to include one other item
> > before sending it to IESG:
> > 	o A <router-expression> is now allowed as the peer router in a
> > 	  peering. Please see Section x.
> > (Along with other comments from you folks).
> >  
> > Cengiz
> 
> Here are some comments that I've made in private exchanges.  I don't
> know whether these sort of changes should go into this cut of RPSL or
> go into a later version to be recycled yet again as PS.  This may
> largely depend on the OPs ADs preferences.
> 
> We've been experimenting with RPSL to configure policy on
> route-reflector clients to give some full routing, some partial (our
> customers only or some other subset), and some just default and a few
> others.  In addition there is import policy on each.  What this is
> doing is moving policy for customers (mostly single homed) to the
> access router rather than CPE router.  If the CPE becomes customer
> managed this becomes EBGP rather than IBGP route-reflector.
> 
> One thing that would be very useful is a "filter" object that could be
> referenced anywhere that <filter> appears.  This would be useful for
> someone with multiple AS that all have similar import or export
> policies.  We might even want to consider a "hints" attribute where we
> could put such things as "route-map-name" or "prefix-list-name" for
> routers that support named policy stanzas.  The hint could be used in
> the simple case where an import or export just references a single
> filter object otherwise ignored and ignored if the router being
> configured did not support named policy stanzas.

I favor this one. Mark also wanted a way to name a set of communities
for private use. He could use the filter object as well. Something
like:

route-filter: rf-foo
filter: <filter>

Wearing an RPS hat, I dont like the hint attribute. I think it is
configuration information that should not be included.  Wearing an
RAToolSet hat, I dont mind implementing such a feature even if it is
left outside of RPSL.

> 
> In addition it would be useful to have a "peer-group" object that
> could be used in the router-expression in <as-expression>
> [<router-expression>] [at <router-expression>].  The name of the
> peer-group might be used in generating router configurations that
> support named peer-groups.  The alternate that we were counting on was
> to use a route-set with /32s in it.  It doesn't look like this is
> supported:
> 
> rtr_expr_operand: TKN_IPV4 | TKN_DNS
> 
> Since the tokens are not defined it is not entirely clear what
> TKN_IPV4 and TKN_DNS are.  The text just says:
> 
>   and <router-expression-1> and <router-expression-2> are expressions
>   over router IP addresses and DNS names using operators AND, OR, and
>   NOT. The DNS name can only be used if there is an inet-rtr object
>   for that name that binds the name to IP addresses.
> 
> It would appear that router IP addresses means fully dotted IPv4 quad.
> 

yes

> Allowing an object named "peer-group" might be preferable to allowing
> a route-set and accepting all routers falling within the route-set.
> The route set would be OK too.  Adding one or the other to
> rtr_expr_operand would be a good thing.  Having no ability to name
> these sets will bloat our aut-nums a bit and give us cause to
> preprocess aut-nums and use the source prior to preprocessing for the
> actual configuration.
> 

You are suggesting:

rtr-set: <an hierarchical name, e.g. as1:rtr-core>
members: list of IPv4 or dns names 
member-by-ref: list of maintainers

(I called it rtr-set to be consistent and more general). DNS names can 
only be used if there is an inet-rtr for that name.

> Neither of these changes are essential.  We can use aut-num source
> prior to preprocessing in our configuration generation (as we already
> do) and submit the aut-num after preprocessing if there are any
> significant changes.  These aut-nums may never be submited to a
> publicly readable database anyway (at least not before stripping the
> route-reflector policy).  We might want to consider these two changes
> for the next round of RPSL.

I can incorporate these changes next week, give another week or two to
the WG for review and submit the draft to IESG for movement. This
would be the least delay path.

The changes are small (rtr-set is very much like rs-set and
route-filter is more like a preprocessor macro).

The question to the the WG and ADs is: do you support these changes,
if so, is it OK to incorporate them next week before submitting them
to IESG.

> 
> I'd also like to point out that as much as some people would like to
> see no changes at all it is likely that we will need to have a next
> round of RPSL because people are using RPSL and through using it will
> come up with more efficient ways to express routing policy.
> 

I think it is important that we finish up with the document and
implementation and refocus on deployment. We had over a year in phase
II of the transition for people to play with the language and tell us
all these nice extensions during this phase. However, with the
exception of few (thanks Mark:-), most people only recently started to
play with it. The encouraging news is that there are quiet a few
people now who are non implementors and play with the language.

> Curtis


Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California


From rps-owner@ISI.EDU  Wed Jan 27 13:24:44 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA01081
	for <rps-archive@lists.ietf.org>; Wed, 27 Jan 1999 13:24:38 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id JAA28894
	for rps-outgoing; Wed, 27 Jan 1999 09:57:57 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id JAA28888
	for <rps@zephyr.isi.edu>; Wed, 27 Jan 1999 09:57:55 -0800 (PST)
Received: from dog.isi.edu ([4.3.130.214])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA02716;
	Wed, 27 Jan 1999 09:57:53 -0800 (PST)
Received: (from cengiz@localhost)
	by dog.isi.edu (8.8.7/8.8.7) id JAA01116;
	Wed, 27 Jan 1999 09:58:26 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 27 Jan 1999 09:58:26 -0800 (PST)
To: Mark Prior <mrp@connect.com.au>
Cc: cengiz@ISI.EDU, rps@ISI.EDU
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
In-Reply-To: <199901242344.KAA15957@kuji.off.connect.com.au>
References: <13992.58018.357745.753680@cat.isi.edu>
	<199901242344.KAA15957@kuji.off.connect.com.au>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13999.20834.352162.293795@dog.isi.edu>
Reply-to: cengiz@ISI.EDU
X-Organisation: USC / Information Sciences Institute
X-Phone: +1 (310) 822 1511 x219
X-Fax: +1 (310) 823 6714
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Mark Prior (mrp@connect.com.au) on January 25:
>      rps-auth solves "some other maintainer can't come along and recreate
>      the original record" problem.
> 
> I am not convinced that it will. It is fine in theory but practice
> will be an entirely different matter.
> 
> In Australia there are 4 main IAPs (Connect, Optus, OzEmail and
> Telstra). We each register our customers routes in the IRR (Telstra
> uses CW and registers all customers under their AS while the rest of
> us register in RADB). Just about none of the smaller ISPs appear to
> know/care about the IRR and leave it up to the big 4 to register their
> routes (it's pretty rare that an Australian ISP doesn't have a link to
> at least one of the big 4). Internet charging being what it is the
> smaller ISPs move around, don't send all their routes to all their
> upstreams etc. If a customer connects to Connect (say) we will
> register their route in RADB (under their AS). If they then get
> another link to Optus then they will try to register their route but
> will fail since we have already hijacked it (we get a nice message
> from RADB telling us that the customer now has a link to Optus :-) Now
> should the customer sometime later cancel their link to Connect we
> will (currently) withdraw the route. There is no mechansim to warn
> Optus that we have done this so the first they know about it is when
> the customer complains.

I dont see why withdrawing in this case helps over deleting. In either
case people who configure from IRR will not use these routes,
withdrawn or deleted. You also make it harder for your competition to
un-withdraw these routes since you are the maintainer of them.

What I would have done (with no business objectives): Register the
routes using a different maintainer than my own, but include access to
myself in that maintainer. When the customer leaves, delete access to
myself, but leave the objects in tact for the next ISP or customer to
take over. I think this is the best for the customer.

I really would like opinion from others on this.

> 
> We won't suffer from this problem since we have our own DB and only
> use the RADB for info but this problem sort of forces you down that
> path.
> 
> Mark.


Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California


From rps-owner@ISI.EDU  Wed Jan 27 18:33:06 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA08928
	for <rps-archive@lists.ietf.org>; Wed, 27 Jan 1999 18:33:00 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id PAA14862
	for rps-outgoing; Wed, 27 Jan 1999 15:06:36 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id PAA14857
	for <rps@zephyr.isi.edu>; Wed, 27 Jan 1999 15:06:34 -0800 (PST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id PAA02455;
	Wed, 27 Jan 1999 15:06:32 -0800 (PST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id JAA18969
  (8.8.8/IDA-1.6); Thu, 28 Jan 1999 09:35:58 +1030 (CST)
Message-ID: <199901272305.JAA18969@kuji.off.connect.com.au>
To: cengiz@ISI.EDU
cc: rps@ISI.EDU
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
In-reply-to: Your message of "Wed, 27 Jan 1999 09:58:26 -0800."
             <13999.20834.352162.293795@dog.isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18967.917478358.1@connect.com.au>
Date: Thu, 28 Jan 1999 09:35:58 +1030
From: Mark Prior <mrp@connect.com.au>
Sender: owner-rps@ISI.EDU
Precedence: rps-list

     I dont see why withdrawing in this case helps over deleting. In either
     case people who configure from IRR will not use these routes,
     withdrawn or deleted. You also make it harder for your competition to
     un-withdraw these routes since you are the maintainer of them.

It was more of a case of "rps-auth doesn't fix everything" than
withdrawn is needed in this context.

     What I would have done (with no business objectives): Register the
     routes using a different maintainer than my own, but include access to
     myself in that maintainer. When the customer leaves, delete access to
     myself, but leave the objects in tact for the next ISP or customer to
     take over. I think this is the best for the customer.

Oh yeah? You are expecting ISPs to cooperate, and we know that aight
gunna happen.

Mark.


From rps-owner@ISI.EDU  Wed Jan 27 20:02:12 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id UAA09929
	for <rps-archive@lists.ietf.org>; Wed, 27 Jan 1999 20:02:11 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id QAA19748
	for rps-outgoing; Wed, 27 Jan 1999 16:33:53 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id QAA19743
	for <rps@zephyr.isi.edu>; Wed, 27 Jan 1999 16:33:52 -0800 (PST)
Received: from brookfield.ans.net (brookfield-ef0.brookfield.ans.net [204.148.1.20])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id QAA10933;
	Wed, 27 Jan 1999 16:33:45 -0800 (PST)
Received: from brookfield.ans.net (localhost.brookfield.ans.net [127.0.0.1])
	by brookfield.ans.net (8.8.8/8.8.8) with ESMTP id TAA26138;
	Wed, 27 Jan 1999 19:33:44 -0500 (EST)
	(envelope-from curtis@brookfield.ans.net)
Message-Id: <199901280033.TAA26138@brookfield.ans.net>
To: cengiz@ISI.EDU
cc: curtis@ans.net, rps@ISI.EDU
Reply-To: curtis@ans.net
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01 
In-reply-to: Your message of "Wed, 27 Jan 1999 09:48:11 PST."
             <13999.18123.62615.786761@dog.isi.edu> 
Date: Wed, 27 Jan 1999 19:33:43 -0500
From: Curtis Villamizar <curtis@brookfield.ans.net>
Sender: owner-rps@ISI.EDU
Precedence: rps-list


In message <13999.18123.62615.786761@dog.isi.edu>, Cengiz Alaettinoglu writes:
> 
> > >  o  The syntax and semantics of  export-comps attribute of route class  h
> ave
> > >     changed.  Please see Section 8.
> > 
> > I don't remember any discussion of this change.  It is all wrong.  If
> > the scope of an aggregate is multiple providers it makes absolutely no
> > sense to specify the export policy of the components in the aggregate.
> > 
> > The export-comps is supposed to be just a list, nothing more.  If a
> > prefix falls under an aggregate it is omitted from any export
> > statements in which it would otherwise appear unless it falls within
> > the export-comps list for the aggregate in which case it is not
> > omitted.  This was the functionality agreed to.
> > 
> > Could you please forward any email discussing this change or restore
> > it to what we had agreed to before.
> 
> This was suggested by the Fore folks and was discussed in the LA IETF
> WG meeting.
> 
> Please see ftp://ftp.isi.edu/rps/la-ietf-98/implementation-experience.ps

If I remember correctly the reason was along the lines of "easier to
code in RPSL this way" and this was objected to at the meeting.

> You could get the older behavior by:
> 
> 	export-comps: to as-any announce <whatever>
> 
> Hence, it can not be "all wrong".  May be someone from Fore may
> comment, or I can dig the mail archives if you insist.

The document doesn't agree with what you've said above.

   When a  set of  routes are  aggregated, the  intent is  to  export only  the
   aggregate route and  suppress exporting  of the more  specifics outside  the
   aggregation boundary.    However,  to satisfy  certain policy  and  topology
   constraints (e.g. a multi-homed component),  it is often required to  export
   some of the components.  The export-comps attribute serves this purpose.  It
   equals an RPSL export policy expression as follows (see Section6.2):


    export-comps: to <peering-1> [action <action-1>]
                  . . .
                  to <peering-N> [action <action-N>]
                  announce <filter>


   where <filter> matches the  more specifics that need  to be exported to  the
   peerings specified.    While exporting  to  <peering-i>, the  <action-i>  is
   executed to set the  path attributes.   If this  attribute is missing,  more
   specifics are not exported outside the aggregation boundary.  Note that, the
   <filter> contains an  implicit "AND"  term with  the more  specifics of  the
   aggregate.

What you've said above in email is 'export-comps: to as-any announce
ANY' would be equivalent to the old behavior in which export statement
in the aut-num for the announcing AS applied if there was an
export-comp attribute in the aggregate.  What the document says is
that the "to" and "action" and "filter" in the route object is in
effect the export policy.  You need to change the document.

I object to any policy being placed in the route object itself since
multiple providers will be announcing the route and many are likely to
have different export policies.

The export-comp should be a filter only and specify those prefixes
which slip through the implicit export blocking of the aggregate.  Any
"to" and "action" should be specified in the export policy for the AS
making the announcement.

> > One thing that would be very useful is a "filter" object that could be
> > referenced anywhere that <filter> appears.  This would be useful for
> > someone with multiple AS that all have similar import or export
> > policies.  We might even want to consider a "hints" attribute where we
> > could put such things as "route-map-name" or "prefix-list-name" for
> > routers that support named policy stanzas.  The hint could be used in
> > the simple case where an import or export just references a single
> > filter object otherwise ignored and ignored if the router being
> > configured did not support named policy stanzas.
> 
> I favor this one. Mark also wanted a way to name a set of communities
> for private use. He could use the filter object as well. Something
> like:
> 
> route-filter: rf-foo
> filter: <filter>
> 
> Wearing an RPS hat, I dont like the hint attribute. I think it is
> configuration information that should not be included.  Wearing an
> RAToolSet hat, I dont mind implementing such a feature even if it is
> left outside of RPSL.

In RaToolSet it would have to be:

  remarks:  cisco-hint: <cisco-hint>
  <cisco-hint>: |
     <cisco-hint> route-map-name <name> |
     <cisco-hint> prefix-list-name <name> ;

(please excuse the mixed bison syntax).  This would need to be in
remarks if it is not an attribute supported by other tools.  If so, it
is sort of ugly but there is no need to change the RPSL doc to support
this.

> > In addition it would be useful to have a "peer-group" object that
> > could be used in the router-expression in <as-expression>
> > [<router-expression>] [at <router-expression>].  The name of the
> > peer-group might be used in generating router configurations that
> > support named peer-groups.  The alternate that we were counting on was
> > to use a route-set with /32s in it.  It doesn't look like this is
> > supported:
> > 
> > rtr_expr_operand: TKN_IPV4 | TKN_DNS
> > 
> > Since the tokens are not defined it is not entirely clear what
> > TKN_IPV4 and TKN_DNS are.  The text just says:
> > 
> >   and <router-expression-1> and <router-expression-2> are expressions
> >   over router IP addresses and DNS names using operators AND, OR, and
> >   NOT. The DNS name can only be used if there is an inet-rtr object
> >   for that name that binds the name to IP addresses.
> > 
> > It would appear that router IP addresses means fully dotted IPv4 quad.
> 
> yes
> 
> > Allowing an object named "peer-group" might be preferable to allowing
> > a route-set and accepting all routers falling within the route-set.
> > The route set would be OK too.  Adding one or the other to
> > rtr_expr_operand would be a good thing.  Having no ability to name
> > these sets will bloat our aut-nums a bit and give us cause to
> > preprocess aut-nums and use the source prior to preprocessing for the
> > actual configuration.
> > 
> 
> You are suggesting:
> 
> rtr-set: <an hierarchical name, e.g. as1:rtr-core>
> members: list of IPv4 or dns names 
> member-by-ref: list of maintainers
> 
> (I called it rtr-set to be consistent and more general). DNS names can 
> only be used if there is an inet-rtr for that name.

You can call it peer-group or rtr-set.  If building Cisco configs it
maps directly to a peer-group and gives the OPs folks here the
peer-group names they already know and love.

This look like you are saying "yes" in support of the idea but calling
it rtr-set?  If so, fine with me.

> > Neither of these changes are essential.  We can use aut-num source
> > prior to preprocessing in our configuration generation (as we already
> > do) and submit the aut-num after preprocessing if there are any
> > significant changes.  These aut-nums may never be submited to a
> > publicly readable database anyway (at least not before stripping the
> > route-reflector policy).  We might want to consider these two changes
> > for the next round of RPSL.
> 
> I can incorporate these changes next week, give another week or two to
> the WG for review and submit the draft to IESG for movement. This
> would be the least delay path.
> 
> The changes are small (rtr-set is very much like rs-set and
> route-filter is more like a preprocessor macro).
> 
> The question to the the WG and ADs is: do you support these changes,
> if so, is it OK to incorporate them next week before submitting them
> to IESG.

Cool.  Thanks.

> > I'd also like to point out that as much as some people would like to
> > see no changes at all it is likely that we will need to have a next
> > round of RPSL because people are using RPSL and through using it will
> > come up with more efficient ways to express routing policy.
> 
> I think it is important that we finish up with the document and
> implementation and refocus on deployment. We had over a year in phase
> II of the transition for people to play with the language and tell us
> all these nice extensions during this phase. However, with the
> exception of few (thanks Mark:-), most people only recently started to
> play with it. The encouraging news is that there are quiet a few
> people now who are non implementors and play with the language.

My preference would also be to get these changes in now rather than
later.

Curtis

btw- Please define "play".  ;-)

Actually it is only recently we've tried to figure out how to do
route-reflectors and support Cisco configs rather than Bay and gated,
generate the whole Cisco config and preserve what our operational
people like about their hand edited Cisco configs.  Before that we've
made sure that there was support in RPSL so we could remove all of the
kludges we had to work around limitations in RIPE-181 but we haven't
removed those kludges in our config software.


From rps-owner@ISI.EDU  Wed Jan 27 20:26:00 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id UAA10060
	for <rps-archive@lists.ietf.org>; Wed, 27 Jan 1999 20:26:00 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id QAA20981
	for rps-outgoing; Wed, 27 Jan 1999 16:59:17 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id QAA20976
	for <rps@zephyr.isi.edu>; Wed, 27 Jan 1999 16:59:16 -0800 (PST)
Received: from dog.isi.edu ([4.3.130.214])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id QAA13400;
	Wed, 27 Jan 1999 16:59:14 -0800 (PST)
Received: (from cengiz@localhost)
	by dog.isi.edu (8.8.7/8.8.7) id QAA01196;
	Wed, 27 Jan 1999 16:59:48 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 27 Jan 1999 16:59:48 -0800 (PST)
To: Mark Prior <mrp@connect.com.au>
Cc: cengiz@ISI.EDU, rps@ISI.EDU
Subject: Re: WG Last Call on draft-ietf-rps-rpsl-v2-01
In-Reply-To: <199901272305.JAA18969@kuji.off.connect.com.au>
References: <13999.20834.352162.293795@dog.isi.edu>
	<199901272305.JAA18969@kuji.off.connect.com.au>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13999.46680.834213.825588@dog.isi.edu>
Reply-to: cengiz@ISI.EDU
X-Organisation: USC / Information Sciences Institute
X-Phone: +1 (310) 822 1511 x219
X-Fax: +1 (310) 823 6714
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Please let me know of a case (good one) for withdrawn, otherwise it is 
going away for forever:-)

Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California


From rps-owner@ISI.EDU  Fri Jan 29 16:13:15 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA08342
	for <rps-archive@lists.ietf.org>; Fri, 29 Jan 1999 16:13:14 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id MAA12544
	for rps-outgoing; Fri, 29 Jan 1999 12:48:12 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id MAA12539
	for <rps@zephyr.isi.edu>; Fri, 29 Jan 1999 12:48:11 -0800 (PST)
Received: from cat.isi.edu (cat.isi.edu [128.9.160.205])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id MAA28638
	for <rps@ISI.EDU>; Fri, 29 Jan 1999 12:48:10 -0800 (PST)
Received: (from cengiz@localhost)
	by cat.isi.edu (8.8.7/8.8.7) id MAA09809;
	Fri, 29 Jan 1999 12:48:08 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14002.7816.493872.232005@cat.isi.edu>
Date: Fri, 29 Jan 1999 12:48:08 -0800 (PST)
To: Curtis Villamizar <curtis@ans.net>
CC: rps@ISI.EDU
Subject: rps auth todo list
X-Mailer: VM 6.63 under 20.4 "Emerald" XEmacs  Lucid
Reply-to: cengiz@ISI.EDU
X-Organisation: USC / Information Sciences Institute
X-Phone: +1 (310) 822 1511 x219
X-Fax: +1 (310) 823 6714
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Curtis,

Here is a summary of our December WG discussion on rps-auth. Please
make the appropriate changes to the document, and issue a WG last call 
to move it to proposed standard:

- add syntax of mnt-routes which is:
	list of 1. <mntnr>
		2. <mntnr> KEYW_ANY
		3. <mntnr> { list of address prefix ranges }

   the 1 and 2 are equivalent in semantics. The syntax is negotiable
   but needs to be explicit.

- add mnt-lower: <list of maintainers>. 

- you may consider adding an early section which contains the syntax
  and semantics of mnt-routes, mnt-lower, and mnt-by and states:

	when authorizing a route object look at mnt-routes, if it does 
	not exist, look at mnt-lower, if that does not exist either look at
	mnt-by 

	For all other objects loot at mnt-lower followed by mnt-by.

- delete referral-in (since it can be done by reverse lookup on
  referral-by) 

- I forgot what we agreed on what to do when authorizing a route
  object r and we hit a less specific route object which has a hole
  covering the route object r.

- auth-override is only placable if there is no activity by the
maintainer it is placed on in the last 60 days and it is only
effective after 60 days.

- decide the defualt of reclaim/no-reclaim, and make it explicit in
the document

- add as-set, route-set, rtr-set, filter authorization. These have
names like AS1:as-foo. They authorized by the object whose key is the
same name except the last part (already in rpsl document, same
mnt-lower, mnt-by mechanism when the name is hierarchical).

- delete the repository object and delegated attribute discussions and
move them to the rps-dist document

- move reclaim/no-reclaim/auth-overrride to the end of the document
(they are not first things to implement).

Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California


