From rps-owner@ISI.EDU  Thu Apr  1 15:40:41 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02675
	for <rps-archive@lists.ietf.org>; Thu, 1 Apr 1999 15:40:40 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id MAA20909
	for rps-outgoing; Thu, 1 Apr 1999 12:04:26 -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 MAA20904
	for <rps@zephyr.isi.edu>; Thu, 1 Apr 1999 12:04:25 -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 MAA05982
	for <rps@ISI.EDU>; Thu, 1 Apr 1999 12:04:24 -0800 (PST)
Received: (from cengiz@localhost)
	by cat.isi.edu (8.8.7/8.8.7) id MAA15515;
	Thu, 1 Apr 1999 12:04:16 -0800
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14083.53567.568543.444275@cat.isi.edu>
Date: Thu, 1 Apr 1999 12:04:15 -0800 (PST)
To: Internet-Drafts Administrator <Internet-Drafts@ietf.org>
CC: rps@ISI.EDU, Randy Bush <rbush@bainbridge.verio.net>,
        Bert Wijnen <WIJNEN@VNET.IBM.COM>
Subject: New drafts available
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
Content-Transfer-Encoding: 7bit


Internet-Drafts Administrator:

Please find and publish:
	ftp://ftp.isi.edu/rps/doc/draft-ietf-rps-rpsl-v2-03.ps
	ftp://ftp.isi.edu/rps/doc/draft-ietf-rps-rpsl-v2-03.txt

Thank you.

Randy:

This version reflects the feedback during the IESG last call. Mainly
there are 3 changes, 1) a typo, 2) ragged right formatting, 3) The
format of the grammar rules is now specified (i.e. bison).

RPS wg would like to ask IESG to advance this document to proposed
standard.

Thank you very much.

Cengiz

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


From rps-owner@ISI.EDU  Thu Apr  1 16:30:42 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03701
	for <rps-archive@lists.ietf.org>; Thu, 1 Apr 1999 16:30:41 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id NAA24589
	for rps-outgoing; Thu, 1 Apr 1999 13:12:56 -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 NAA24584
	for <rps@zephyr.isi.edu>; Thu, 1 Apr 1999 13:12:54 -0800 (PST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id NAA12570;
	Thu, 1 Apr 1999 13:12:52 -0800 (PST)
Received: from localhost (593 bytes) by rip.psg.com
	via sendmail with P:stdio/R:inet_resolve/T:smtp
	(sender: <randy>) (ident <randy> using unix)
	id <m10Sole-0008G4C@rip.psg.com>
	for <rps@ISI.EDU>; Thu, 1 Apr 1999 13:12:50 -0800 (PST)
	(Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1)
Message-Id: <m10Sole-0008G4C@rip.psg.com>
Date: Thu, 1 Apr 1999 13:12:50 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: cengiz@ISI.EDU
Cc: Internet-Drafts Administrator <Internet-Drafts@ietf.org>, rps@ISI.EDU,
        Bert Wijnen <WIJNEN@VNET.IBM.COM>
Subject: Re: New drafts available
References: <14083.53567.568543.444275@cat.isi.edu>
Sender: owner-rps@ISI.EDU
Precedence: rps-list
Content-Transfer-Encoding: 7bit

as it has yet to arrive in the i-d directory, i must ask.

does it have current boilerplate?  i.e. copyright, 2119 reference, security
and iana (if needed) considerations?

randy


From rps-owner@ISI.EDU  Sat Apr  3 07:10:21 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02575
	for <rps-archive@lists.ietf.org>; Sat, 3 Apr 1999 07:10:20 -0500 (EST)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id DAA20971
	for rps-outgoing; Sat, 3 Apr 1999 03:55:29 -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 DAA20966
	for <rps@zephyr.isi.edu>; Sat, 3 Apr 1999 03:55:27 -0800 (PST)
Received: from citicom.com (citicom.com [207.138.160.1])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id DAA07069
	for <rps@isi.edu>; Sat, 3 Apr 1999 03:55:25 -0800 (PST)
Received: from defiant (defiant.citicom.com [207.138.160.30])
	by citicom.com (8.9.3/CITI-E-8.9.3) with SMTP id GAA03667
	for <rps@isi.edu>; Sat, 3 Apr 1999 06:55:20 -0500
Reply-To: <dandersn@citicom.com>
From: "Dave Anderson" <dandersn@citicom.com>
To: <rps@ISI.EDU>
Subject: RIPE-181 -> RPSL
Date: Sat, 3 Apr 1999 06:55:20 -0500
Message-ID: <000301be7dc8$d9471c80$1ea08acf@citicom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-rps@ISI.EDU
Precedence: rps-list
Content-Transfer-Encoding: 7bit


Hi,

I work for a regional multihomed ISP in the Tampa Florida 
area.

I currently have our maintainer, AS, and route objects
all current via the RADB.  (maint-as11656, as11656, and
207.138.160.0/20)

My question is this - i've read most of the information about
the transition between 181 and RPSL, but the one thing i'm
not sure about is "what do I need to do" to make sure
my current objects are correct, and will continue to work,
or if I need to transition them.

Is there any documentation or quick FAQ on what current 181 RADB
users should do in preperation for RPSL?

Sorry to bother, just wanting to make sure we're not missing
something important here....

Thanks in advance for you time!


Seeya,

Dave Anderson
Citicom Online



From rps-owner@ISI.EDU  Tue Apr  6 19:58:45 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20357
	for <rps-archive@lists.ietf.org>; Tue, 6 Apr 1999 19:58:44 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id QAA28998
	for rps-outgoing; Tue, 6 Apr 1999 16:44:02 -0700 (PDT)
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 QAA28993
	for <rps@zephyr.isi.edu>; Tue, 6 Apr 1999 16:44:01 -0700 (PDT)
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 QAA23049
	for <rps@ISI.EDU>; Tue, 6 Apr 1999 16:44:00 -0700 (PDT)
Received: (from cengiz@localhost)
	by cat.isi.edu (8.8.7/8.8.7) id QAA11468;
	Tue, 6 Apr 1999 16:43:58 -0700
From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14090.39998.128864.176725@cat.isi.edu>
Date: Tue, 6 Apr 1999 16:43:58 -0700 (PDT)
To: <dandersn@citicom.com>
Cc: <rps@ISI.EDU>
Subject: Re: RIPE-181 -> RPSL
In-Reply-To: <000301be7dc8$d9471c80$1ea08acf@citicom.com>
References: <000301be7dc8$d9471c80$1ea08acf@citicom.com>
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
Content-Transfer-Encoding: 7bit


Dave,

All route objects will work as is. 99% of aut-num objects will also
automatically converted to rpsl. Hence, for most ISP's the transition
is going to be transparent. The 1% are the ones whose aut-num is
already syntactically wrong. (e.g. some one has "accept and asXXX"). 

You can check out your converted aut-num and related transition
documentation at http://www.isi.edu/ra/rps/transition

Dave Anderson (dandersn@citicom.com) on April 3:
> 
> Hi,
> 
> I work for a regional multihomed ISP in the Tampa Florida 
> area.
> 
> I currently have our maintainer, AS, and route objects
> all current via the RADB.  (maint-as11656, as11656, and
> 207.138.160.0/20)
> 
> My question is this - i've read most of the information about
> the transition between 181 and RPSL, but the one thing i'm
> not sure about is "what do I need to do" to make sure
> my current objects are correct, and will continue to work,
> or if I need to transition them.
> 
> Is there any documentation or quick FAQ on what current 181 RADB
> users should do in preperation for RPSL?
> 
> Sorry to bother, just wanting to make sure we're not missing
> something important here....
> 
> Thanks in advance for you time!
> 
> 
> Seeya,
> 
> Dave Anderson
> Citicom Online


Cengiz

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


From rps-owner@ISI.EDU  Sun Apr 11 14:05:50 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03868
	for <rps-archive@lists.ietf.org>; Sun, 11 Apr 1999 14:05:49 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id KAA19441
	for rps-outgoing; Sun, 11 Apr 1999 10:50:18 -0700 (PDT)
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 KAA19436
	for <rps@zephyr.isi.edu>; Sun, 11 Apr 1999 10:50:17 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id KAA04934
	for <rps@isi.edu>; Sun, 11 Apr 1999 10:50:16 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03591;
	Sun, 11 Apr 1999 13:49:40 -0400 (EDT)
Message-Id: <199904111749.NAA03591@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-03.txt
Date: Sun, 11 Apr 1999 13:49:40 -0400
Sender: owner-rps@ISI.EDU
Precedence: rps-list

--NextPart

A Revised 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.

Note: This revision reflects comments received during the last call period.

	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-03.txt
	Pages		: 68
	Date		: 07-Apr-99
	
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.


Internet-Drafts are available by anonymous FTP.  Login wih 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-03.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-ietf-rps-rpsl-v2-03.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	
	Europe: ftp.nordu.net
		ftp.nis.garr.it
			
	Pacific Rim: munnari.oz.au
	
	US East Coast: ds.internic.net
	
	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ds.internic.net.  In the body type:
	"FILE /internet-drafts/draft-ietf-rps-rpsl-v2-03.txt".
	
NOTE:	The mail server at ds.internic.net 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@ds.internic.net"

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

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

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

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

--OtherAccess--

--NextPart--





From rps-owner@ISI.EDU  Wed Apr 21 18:49:04 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27506
	for <rps-archive@lists.ietf.org>; Wed, 21 Apr 1999 18:49:03 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id PAA13595
	for rps-outgoing; Wed, 21 Apr 1999 15:27:30 -0700 (PDT)
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 PAA13588
	for <rps@zephyr.isi.edu>; Wed, 21 Apr 1999 15:27:28 -0700 (PDT)
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 PAA11319
	for <rps@isi.edu>; Wed, 21 Apr 1999 15:27:25 -0700 (PDT)
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 SAA23998;
	Wed, 21 Apr 1999 18:27:09 -0400 (EDT)
	(envelope-from curtis@brookfield.ans.net)
Message-Id: <199904212227.SAA23998@brookfield.ans.net>
To: David Woodgate <David.Woodgate@telstra.net>
cc: curtis@ans.net, rps@ISI.EDU
Reply-To: curtis@ans.net
Subject: Re: Comments on rps-auth-02 draft 
In-reply-to: Your message of "Thu, 18 Mar 1999 01:38:30 +1100."
             <3.0.1.32.19990318013830.0076803c@nico.telstra.net> 
Date: Wed, 21 Apr 1999 18:27:08 -0400
From: Curtis Villamizar <curtis@brookfield.ans.net>
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Getting ready to send this draft to the internet-drafts editor again..

In message <3.0.1.32.19990318013830.0076803c@nico.telstra.net>, David Woodgate 
writes:
> 
> Here are a few comments on the auth draft:
> 
> 1.	Trust Model
> 
> 	A.	I believe that (intentionally) the document does not deal
> 		with any issues concerning the security of queries to the
> 		database. This may be obvious, but it should probably be
> 		stated explicitly somewhere anyway.

After the section "Implicit Policy Assumptions" I added:

  \section{Scope of Security Coverage}

  This document is intended only to provide an authentication and
  authorization model to insure the integrety of the policy data in a
  registry.  Only authetication and authorization of additions,
  deletions, and changes to the database are within the scope of this
  document.  Authentication and authorization of database queries is
  explicitly out of scope.  Mutual authentication of queries, that is
  authenticating both the origin of the query and the repository from
  which query results are obtained, is also out of scope.


> 	B.	My understanding of the processes surrounding the submission
> 		of a new object to a registry is that it only relies
> 		on checks from the immediate (potential) parent objects.
> 		However, I don't believe that at any stage is the authenticatio
> n
> 		or the integrity of those parent objects rechecked. In other
> 		words, once the data is in the repository, it is assumed
> 		to be valid - there are no subsequent rechecks of validity.
> 
> 		(Please correct me if I'm wrong about this.)
> 
> 		This is a fine assumption to make, but it probably should
> 		be stated explicitly - at least in a comment in the security
> 		section, and possibly even in a separate, small (one sentence)
> 		section around the same area in the document, as the
> 		"Implicit Policy Assumptions" section.

This is covered in rps-dist by the "integrety" attribute used to allow
grandfathered data of questionable origin.  I can't reference rps-dist
because we plan to move forward with that later than rps-auth.


> 2.	mnt-routes vs. mnt-lower
> 
> 	After our discussion, I understand some of the historical and
> 	legacy issues involved in these attributes. Nevertheless, I'm
> 	still concerned that there is significant potential for confusion
> 	about which gets used where and why.
> 
> 	Would there be a possibility of either:
> 	(a)	Deprecating the use of one, and prefer the other;
> 	(b)	Merging the two attributes into one?
> 
> 	With respect to the definition of the mnt-routes attribute
> 	in section 9.1, it might be worth reusing the bulk of the last
> 	paragraph in section 8.1 to replace the second and third sentences
> 	of the section 9.1 definition, as I think the 8.1 paragraph
> 	was clearer about the functions of mnt-routes.

At the meeting we agreed to keep these but simplify these a bit.  In
the minutes Cengiz has:

   The working grouped is explicitly provided consensus on:
        - dont use mnt-routes to provide authorization to inetnum objects
        - any maintainer in mnt-routes, mnt-lower and mnt-by are
          authorized for route objects. any maintainer in mnt-lower
          and mnt-by for other objects.
        - to go to the last call after ietf on rps-auth and rps-dbsec-pgp

This is reflected in the following diffs:

  +Where ``mnt-routes'' or ``mnt-lower'' are applicable, any maintainer
  +referenced in the ``mnt-by'' still apply.  The set of applicable
  +maintainers for whatever check is being made is the union of the
  +``mnt-routes'' or ``mnt-lower'' and the ``mnt-by''.

  @@ -1052,16 +1057,11 @@
                        When used with a aut-num, inetnum, or route
                        object, this attribute references a maintainer object
                        which is used in determining authorization for
  -                     the addition of route objects.  When placed in
  -                     a less specific inetnum it is used in
  -                     determining authorization for the addition of 
  -                     more specific inetnum objects.
  +                     the addition of route objects.
                        After the reference to the
                        maintainer, an optional list of prefix ranges
                        (as defined in RPSL) inside of curly braces or
  -                     the keyword ``ANY'' may follow.  If a mnt-routes  
  -                     attribute is absent, the mnt-lower or mnt-by
  -                     mnt-by attribute is used for this purpose.
  +                     the keyword ``ANY'' may follow.
                        The mnt-routes attribute is optional and multiple.
   \item[mnt-lower]     The mnt-lower attribute may appear in an
                        inetnum, route, as-block or aut-num object.
  @@ -1076,9 +1076,7 @@
                        the mnt-lower attribute specifies a maintainer
                        that can be used to add objects with
                        hierarchical names as described in
  -                     Section~\ref{sec:hierarchical-names}.  If a
  -                     mnt-lower attribute is absent, the mnt-by
  -                     attribute is used.
  +                     Section~\ref{sec:hierarchical-names}.
   \item[reclaim]       The reclaim attribute may appear in as-block,
                        aut-num, inetnum, or route objects.  Any
                        object of the same type below in the hierarchy

This simplifies things and it is what we agreed to at the meeting.


> 3.	Section 8.8 "Query Processing"
> 
> 	Since the document doesn't really deal with queries, is there
> 	a real need for this section? Or could it be deleted? (Not
> 	that I'm particularly worried by it.)

The purpose is to describe the search order in querying and nothing
more.  The new section above providing the scope should make this
clear enough.


> 4.	Examples
> 
> 	I think some examples of object/attribute addition/deletion/modificatio
> n
> 	could be useful in making some concepts unambiguous.

Look for an appendix named "Examples".  I'll put in a few.  I can't
cover ever conceivable case.


> 5.	Editorial
> 	
> 	A.	Typo - section 9.1, definition of mnt-routes, second-last
> 		sentence - "the mnt-lower or mnt-by mnt-by attribute"
> 		Too many mnt-by's.

Thanks but this sentence is gone (see diffs above).


> 	B.	Section 8.5, second-last paragraph
> 
>   "Similarly a no-reclaim attribute cannot be deleted unless there are
>   no overlapped objects for which the submitter is not listed in the
>   maintainer pointed to be the mnt-by of the overlapped object."
> 
> 		I would suggest that it can be difficult to think through
> 		all the negatives. May I suggest something like the
> 		following instead?
> 
>   "Similarly, a submitter may delete a no-reclaim attribute from
>   an object only when that submitter is the only maintainer listed
>   in the mnt-by attributes of any overlapped objects. If the mnt-by
>   attributes of any overlapped objects point to maintainers other than
>   the submitter, then it is not permitted to delete the no-reclaim
>   attribute."

I see your point regarding the lack of clarity.  The substitute text
isn't quite right so I used the following:

  Similarly, a submitter may delete a no-reclaim attribute from an
  object only when that submitter is the only maintainer listed in the
  mnt-by attributes of any overlapped objects. If the submitter is not
  listed in any of the maintainers pointed to by the mnt-by attributes
  for one or more overlapped object, then the submitter is not permitted
  to delete the no-reclaim attribute.


> 								davidw

Thanks for the comments,

Curtis


From rps-owner@ISI.EDU  Thu Apr 22 16:30:52 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28498
	for <rps-archive@lists.ietf.org>; Thu, 22 Apr 1999 16:30:52 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id NAA08519
	for rps-outgoing; Thu, 22 Apr 1999 13:04:32 -0700 (PDT)
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 NAA08512
	for <rps@zephyr.isi.edu>; Thu, 22 Apr 1999 13:04:31 -0700 (PDT)
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 NAA03660
	for <rps@isi.edu>; Thu, 22 Apr 1999 13:04:29 -0700 (PDT)
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 QAA27663;
	Thu, 22 Apr 1999 16:04:27 -0400 (EDT)
	(envelope-from curtis@brookfield.ans.net)
Message-Id: <199904222004.QAA27663@brookfield.ans.net>
To: rps@ISI.EDU
cc: curtis@ans.net
Reply-To: curtis@ans.net
Subject: rps-dist respin
Date: Thu, 22 Apr 1999 16:04:26 -0400
From: Curtis Villamizar <curtis@brookfield.ans.net>
Sender: owner-rps@ISI.EDU
Precedence: rps-list


I'm updating rps-dist.  The minutes of our last meeting contained:

   Curtis suggested that (upon request from RIPE and ARIN) the people and
   role objects should not be distributed. The main reason is the
   spammers. Instead queries should be referred to the appropriate
   repositories. Also for attributes with email values, a nic handle can
   be used to overcome privacy issue of emails. For legacy objects, the
   emails can be stripped out before forwarding.

   Harald did not liked the fact that the standard specified which
   classes are not distributed. WG reached a consensus on allowing
   selected classes not to be distributed, but leaving the decision of
   which classes are not distributed to each registry. However, the
   policy objects have to be distributed. There was also a per object
   field, settable by the user, to allow redistribution or not. It was
   objected by the WG.

The slides I presented at the meeting had:

  Requested Changes:

    .  Add a section addressing the privacy of contact information.

      - The people and role objects are not distributed to other
	registries.  Any query must be referred to the authoritative
	registry where local restrictions on redistribution of
	contact information can be enforced.

      - The option is needed to use NIC handles in attributes that now
        require and email address.  Some examples are the changed and
        notify attributes.  This will allow signing of an object and
        not reuire removal of any attribute.  Users must put in a NIC
        handle to maintain privacy.

      - Older data can have contact information stripped before being
        redistributed on a one time basis, with the integrity field
        marked as legacy.

AFAIK these are the only requested changes to rps-dist.

I have added an appendix entitled "Privacy of Contact Information".

   The routing registries have contained contact information.  The
   redistribution of this contact information has been a delicate issue
   an in some countries has legal implications.

   The person and role objects contain contact information.  These
   objects are referenced by NIC-handles.  There are some attributes such
   as the "changed" and "notify" attributes that require an email
   address.  All of the fields that currently require an email address
   must also accept a NIC-handle.

   The person and role objects should not be redistributed by default.
   If a submission contains an email address in a field such as a changed
   field rather than a NIC-handle the submitter should be aware that they
   are allowing that email address to be redistributed and forfeiting any
   privacy.  Repositories which do not feel that prior warnings of this
   forfeiture are sufficient legal protection should reject the
   submission requesting that a NIC-handle be used.

   Queries to role and person objects arriving at a mirror must be
   referred to the authoritative repository where whatever
   authentication, restrictions, or limitations deemed appropriate by
   that repository can be enforced directly.

   Software should make it possible to restrict the redistribution of
   other entire object types as long as those object types are not
   required for the authorization of additions of other object types.  It
   is not possible to redistribute objects with attributes removed or
   altered since this would invalidate the submitter's signature and make
   subsequent authentication checks impossible.  Repositories should not
   redistribute a subset of the objects of a given type.

   When redistributing legacy data, contact information in attributes
   such as "changed" and "notify" should be stripped to maintain privacy.
   The "integrity" attribute on these objects should already be set to
   "legacy" indicating that their origin is questionable, so the issue of
   not being able to recheck signatures is not as significant.

I've also filled in the security section.

Curtis


From rps-owner@ISI.EDU  Thu Apr 29 08:42:46 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12822
	for <rps-archive@lists.ietf.org>; Thu, 29 Apr 1999 08:42:45 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id FAA06448
	for rps-outgoing; Thu, 29 Apr 1999 05:15:10 -0700 (PDT)
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 FAA06441
	for <rps@zephyr.isi.edu>; Thu, 29 Apr 1999 05:15:08 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id FAA00200;
	Thu, 29 Apr 1999 05:15:04 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11955;
	Thu, 29 Apr 1999 08:14:29 -0400 (EDT)
Message-Id: <199904291214.IAA11955@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@ISI.EDU>
Cc: Internet Architecture Board <iab@ISI.EDU>
Cc: rps@ISI.EDU
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Routing Policy Specification Language (RPSL)
	 to Proposed Standard
Date: Thu, 29 Apr 1999 08:14:29 -0400
Sender: owner-rps@ISI.EDU
Precedence: rps-list



The IESG has approved the Internet-Draft 'Routing Policy Specification
Language (RPSL)' <draft-ietf-rps-rpsl-v2-03.txt> as a Proposed
Standard, obsoleting RFC2280. This document is the product of the
Routing Policy System Working Group.  The IESG contact persons are Bert
Wijnen and Randy Bush.


Technical Summary
 
   RPSL is a language syntax which allows a network operator 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.


Working Group Summary

    Discussion on the technical details of this revision has been
    negligible; there seems to be consensus that the current text is
    an improvement over the previous version.

    The ongoing debate on whether the system described is too complex
    and overreaching to be useful was not deemed relevant to this
    recycling of the spec at Proposed status.

Protocol Quality

    Spec review was by Harald Alvestrand, with the changes in the new
    revision looked at by Randy Bush, previous and current Ops AD
    respectively.



From rps-owner@ISI.EDU  Fri Apr 30 11:27:00 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01897
	for <rps-archive@lists.ietf.org>; Fri, 30 Apr 1999 11:26:58 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id IAA01358
	for rps-outgoing; Fri, 30 Apr 1999 08:11:27 -0700 (PDT)
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 IAA01353
	for <rps@zephyr.isi.edu>; Fri, 30 Apr 1999 08:11:26 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id IAA11664
	for <rps@isi.edu>; Fri, 30 Apr 1999 08:11:25 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00835;
	Fri, 30 Apr 1999 11:10:51 -0400 (EDT)
Message-Id: <199904301510.LAA00835@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-auth-03.txt,.ps
Date: Fri, 30 Apr 1999 11:10:50 -0400
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 System Security
	Author(s)	: D. Meyer, C. Villamizar, C. Alaettinoglu, S. Murphy
	Filename	: draft-ietf-rps-auth-03.txt,.ps
	Pages		: 40
	Date		: 29-Apr-99
	
The RIPE database specifications [2] and RPSL language [1] define lan-
guages used as the basis for representing information in a routing
policy system.  A repository for routing policy system information is
known as a routing registry.  A routing registry provides a means of
exchanging information needed to address many issues on importance to
the operation of the Internet.  The implementation and deployment of
a routing policy system must maintain some degree of integrity to be
of any operational use.  This document addresses the need to assure
integrity of the data by providing an authentication and authorization
model.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rps-auth-03.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-auth-03.txt".

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


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-auth-03.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:	<19990429162938.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rps-auth-03.txt

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

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

--OtherAccess--

--NextPart--




From rps-owner@ISI.EDU  Fri Apr 30 12:20:29 1999
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05172
	for <rps-archive@lists.ietf.org>; Fri, 30 Apr 1999 12:20:28 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id JAA03569
	for rps-outgoing; Fri, 30 Apr 1999 09:04:24 -0700 (PDT)
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 JAA03564
	for <rps@zephyr.isi.edu>; Fri, 30 Apr 1999 09:04:22 -0700 (PDT)
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 JAA16302;
	Fri, 30 Apr 1999 09:04:20 -0700 (PDT)
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 MAA02320;
	Fri, 30 Apr 1999 12:04:17 -0400 (EDT)
	(envelope-from curtis@brookfield.ans.net)
Message-Id: <199904301604.MAA02320@brookfield.ans.net>
To: cengiz@ISI.EDU
cc: curtis@ans.net, srh@merit.edu, rps@ISI.EDU, dbsec@ripe.net
Reply-To: curtis@ans.net
Subject: rps-auth
Date: Fri, 30 Apr 1999 12:04:16 -0400
From: Curtis Villamizar <curtis@brookfield.ans.net>
Sender: owner-rps@ISI.EDU
Precedence: rps-list


Cengiz,

I'd rather you made the last call issue on rps-auth since I'm the
primary author.  I was not planning to send in an -04 update before
the last call to get Susan's mostly editorial changes in (spelling,
grammar, prurality of verbs, etc).  This was my error since I
temporarily misplaced Susan's email while doing the edits for the -03.

The reason I decided not to send a draft in with Susan's changes is
that we may get feedback as a result of the RIPE dbsec meeting.  I'd
rather we made the end of last call fall at least a full week after
the RIPE dbsec meeting where dbsec will be specifically discussing
rps-auth.  The dbsec meeting is May 4.

We could begin last call now and end last call on either May 14 (two
week last call, 8 business days after dbsec) or May 17 (3 weeks).  If
dbsec asks for changes which the WG agrees to, I will incorporate them
in the -04 version and we can repeat las call if necessary.  If not,
we can just make editorial changes (Susan's and any others we find)
and ask the ADs to forward the -04 draft to the IESG.  

The source diffs for the editorial changes so far are at
ftp://engr.ans.net/pub/internet-drafts/rps-auth-03-to-04-preview.diffs

If you agree with this approach, please make the last call.  Otherwise
I'll submit a -04 and we can do last call when that clears.

Thanks,

Curtis


