From owner-rap@ops.ietf.org Tue Oct 16 11:47:12 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04877 for ; Tue, 16 Oct 2001 11:47:11 -0400 (EDT) Received: from lserv by psg.com with local (Exim 3.33 #1) id 15tWNu-0000hj-00 for rap-data@psg.com; Tue, 16 Oct 2001 08:44:02 -0700 Received: from mailweb3.inwind.it ([212.141.54.113]) by psg.com with esmtp (Exim 3.33 #1) id 15tWNs-0000hP-00 for rap@ops.ietf.org; Tue, 16 Oct 2001 08:44:01 -0700 Received: from inwind.it (127.0.0.1) by mailweb3.inwind.it (5.5.029) id 3BBC29070000D5E7 for rap@ops.ietf.org; Tue, 16 Oct 2001 17:43:46 +0200 Date: Tue, 16 Oct 2001 17:43:46 +0200 Message-Id: Subject: Subscribed MIME-Version: 1.0 Content-Type: text/plain From: "lucagreco74@inwind.it" To: "RAP-Mail-List" X-XaM3-API-Version: 1.1.9.1.36 X-SenderIP: 193.204.78.97 Sender: owner-rap@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA04877 Luca is now subscribed From owner-rap@ops.ietf.org Wed Oct 17 04:21:39 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16151 for ; Wed, 17 Oct 2001 04:21:39 -0400 (EDT) Received: from lserv by psg.com with local (Exim 3.33 #1) id 15tlvs-000Id7-00 for rap-data@psg.com; Wed, 17 Oct 2001 01:20:08 -0700 Received: from mailweb2.inwind.it ([212.141.54.112]) by psg.com with esmtp (Exim 3.33 #1) id 15tlvr-000Ice-00 for rap@ops.ietf.org; Wed, 17 Oct 2001 01:20:08 -0700 Received: from inwind.it (127.0.0.1) by mailweb2.inwind.it (5.5.029) id 3BC19E330000996F for rap@ops.ietf.org; Wed, 17 Oct 2001 10:20:02 +0200 Date: Wed, 17 Oct 2001 10:20:02 +0200 Message-Id: Subject: Cops for Rsvp API MIME-Version: 1.0 Content-Type: text/plain From: "lucagreco74@inwind.it" To: "RAP-Mail-List" X-XaM3-API-Version: 1.1.9.1.36 X-SenderIP: 193.204.78.97 Sender: owner-rap@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA16151 I would know if someone knows where I can find API Cops for RSVP, and eventually associated RSVP API. Best regards! Luca. From owner-rap@ops.ietf.org Wed Oct 17 15:48:27 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05611 for ; Wed, 17 Oct 2001 15:48:26 -0400 (EDT) Received: from lserv by psg.com with local (Exim 3.33 #1) id 15tweQ-0005YU-00 for rap-data@psg.com; Wed, 17 Oct 2001 12:46:50 -0700 Received: from rip.psg.com ([147.28.0.39]) by psg.com with esmtp (Exim 3.33 #1) id 15tweP-0005YO-00 for rap@ops.ietf.org; Wed, 17 Oct 2001 12:46:49 -0700 Received: from randy by rip.psg.com with local (Exim 3.33 #1) id 15tweP-0006B7-00 for rap@ops.ietf.org; Wed, 17 Oct 2001 12:46:49 -0700 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by psg.com with esmtp (Exim 3.33 #1) id 15tvgI-0004Fx-00 for rap@ops.ietf.org; Wed, 17 Oct 2001 11:44:42 -0700 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03330; Wed, 17 Oct 2001 14:44:36 -0400 (EDT) Message-Id: <200110171844.OAA03330@ietf.org> To: IETF-Announce: ; Subject: RFC 3159 on SPPI Cc: rfc-ed@ISI.EDU, rap@ops.ietf.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: RFC Editor Date: Wed, 17 Oct 2001 14:44:36 -0400 Sender: owner-rap@ops.ietf.org Precedence: bulk A new Request for Comments is now available in online RFC libraries. RFC 3159 Title: Structure of Policy Provisioning Information (SPPI) Author(s): K. McCloghrie, M. Fine, J. Seligson, K. Chan, S. Hahn, R. Sahita, A. Smith, F. Reichmeyer Status: Standards Track Date: August 2001 Mailbox: kzm@cisco.com, mfine@cisco.com, jseligso@nortelnetworks.com, khchan@nortelnetworks.com, scott.hahn@intel.com, ravi.sahita@intel.com, andrew@allegronetworks.com, franr@pfn.com Pages: 40 Characters: 78621 Obsoletes/Updates/SeeAlso: None I-D Tag: draft-ietf-rap-sppi-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3159.txt This document, the Structure of Policy Provisioning Information (SPPI), defines the adapted subset of SNMP's Structure of Management Information (SMI) used to write Policy Information Base (PIB) modules. RFC 2748 defines the COPS protocol, and RFC 2749 describes how the COPS protocol is used to provide for the outsourcing of policy decisions for RSVP. Another usage of the COPS protocol, for the provisioning of policy, is introduced in RFC 3084. In this provisioning model, the policy information is viewed as a collection of Provisioning Classes (PRCs) and Provisioning Instances (PRIs) residing in a virtual information store, termed the Policy Information Base (PIB). Collections of related Provisioning Classes are defined in a PIB module. This document is a product of the Resource Allocation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ----- End Included Message ----- ---------- X-Sun-Data-Type: Multipart X-Sun-Content-Length: 490 X-Sun-Charset: us-ascii X-Sun-Content-Lines: 22 --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <010830161118.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3159 --OtherAccess Content-Type: Message/External-body; name="rfc3159.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <010830161118.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-rap@ops.ietf.org Fri Oct 19 07:13:47 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14164 for ; Fri, 19 Oct 2001 07:13:46 -0400 (EDT) Received: from lserv by psg.com with local (Exim 3.33 #1) id 15uXY3-000COc-00 for rap-data@psg.com; Fri, 19 Oct 2001 04:10:43 -0700 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by psg.com with esmtp (Exim 3.33 #1) id 15uXY2-000COW-00 for rap@ops.ietf.org; Fri, 19 Oct 2001 04:10:43 -0700 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14054; Fri, 19 Oct 2001 07:10:39 -0400 (EDT) Message-Id: <200110191110.HAA14054@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rap@ops.ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-rap-cops-tls-02.txt Date: Fri, 19 Oct 2001 07:10:39 -0400 Sender: owner-rap@ops.ietf.org Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Resource Allocation Protocol Working Group of the IETF. Title : COPS Over TLS Author(s) : J. Walker, A. Kulkarni Filename : draft-ietf-rap-cops-tls-02.txt Pages : 7 Date : 18-Oct-01 This memo describes how to use TLS to secure COPS connections over the Internet. Please send comments on this document to the rap@ops.ietf.org mailing list. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rap-cops-tls-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-rap-cops-tls-02.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-rap-cops-tls-02.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: <20011018141709.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rap-cops-tls-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rap-cops-tls-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20011018141709.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-rap@ops.ietf.org Fri Oct 19 18:27:32 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03330 for ; Fri, 19 Oct 2001 18:27:32 -0400 (EDT) Received: from lserv by psg.com with local (Exim 3.33 #1) id 15ui5k-000FC6-00 for rap-data@psg.com; Fri, 19 Oct 2001 15:26:12 -0700 Received: from gamma.isi.edu ([128.9.144.145]) by psg.com with esmtp (Exim 3.33 #1) id 15ui5i-000FBo-00 for rap@ops.ietf.org; Fri, 19 Oct 2001 15:26:10 -0700 Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id f9JMPtH29310; Fri, 19 Oct 2001 15:25:56 -0700 (PDT) Message-Id: <200110192225.f9JMPtH29310@gamma.isi.edu> To: IETF-Announce: ; Subject: RFC 3159 on SPPI Cc: rfc-ed@ISI.EDU, rap@ops.ietf.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 19 Oct 2001 15:25:55 -0700 From: RFC Editor Sender: owner-rap@ops.ietf.org Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3159 Title: Structure of Policy Provisioning Information (SPPI) Author(s): K. McCloghrie, M. Fine, J. Seligson, K. Chan, S. Hahn, R. Sahita, A. Smith, F. Reichmeyer Status: Standards Track Date: August 2001 Mailbox: kzm@cisco.com, mfine@cisco.com, jseligso@nortelnetworks.com, khchan@nortelnetworks.com, scott.hahn@intel.com, ravi.sahita@intel.com, andrew@allegronetworks.com, franr@pfn.com Pages: 40 Characters: 78621 Obsoletes/Updates/SeeAlso: None I-D Tag: draft-ietf-rap-sppi-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3159.txt This document, the Structure of Policy Provisioning Information (SPPI), defines the adapted subset of SNMP's Structure of Management Information (SMI) used to write Policy Information Base (PIB) modules. RFC 2748 defines the COPS protocol, and RFC 2749 describes how the COPS protocol is used to provide for the outsourcing of policy decisions for RSVP. Another usage of the COPS protocol, for the provisioning of policy, is introduced in RFC 3084. In this provisioning model, the policy information is viewed as a collection of Provisioning Classes (PRCs) and Provisioning Instances (PRIs) residing in a virtual information store, termed the Policy Information Base (PIB). Collections of related Provisioning Classes are defined in a PIB module. This document is a product of the Resource Allocation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <011019152507.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3159 --OtherAccess Content-Type: Message/External-body; name="rfc3159.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <011019152507.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--