From owner-rap@ops.ietf.org Wed Aug 6 13:35:14 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25922 for ; Wed, 6 Aug 2003 13:35:14 -0400 (EDT) Received: from lserv by psg.com with local (Exim 4.20) id 19kSAR-000ITP-3w for rap-data@psg.com; Wed, 06 Aug 2003 17:33:43 +0000 Received: from [127.0.0.1] (helo=roam.psg.com) by psg.com with esmtp (Exim 4.20) id 19kSAN-000IT8-I8 for rap@ops.ietf.org; Wed, 06 Aug 2003 17:33:41 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com ident=randy) by roam.psg.com with esmtp (Exim 4.20) id 19kSAP-000Mju-KT for rap@ops.ietf.org; Wed, 06 Aug 2003 10:33:41 -0700 Message-Id: <200308061629.h76GTdJ16297@gamma.isi.edu> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart To: IETF-Announce: ; Subject: RFC 3571 on Framework Policy Information Base for Usage Feedback Cc: rfc-editor@rfc-editor.org, rap@ops.ietf.org From: rfc-editor@rfc-editor.org Date: Wed, 06 Aug 2003 09:29:39 -0700 X-Spam-Status: No, hits=3.1 required=5.0 tests=MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED version=2.53 X-Spam-Level: *** X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) Sender: owner-rap@ops.ietf.org Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3571 Title: Framework Policy Information Base for Usage Feedback Author(s): D. Rawlins, A. Kulkarni, K. Ho Chan, M. Bokaemper, D. Dutt Status: Informational Date: August 2003 Mailbox: Diana.Rawlins@mci.com, amol.kulkarni@intel.com, khchan@nortelnetworks.com, mbokaemper@juniper.net, ddutt@cisco.com Pages: 35 Characters: 70894 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rap-feedback-fr-pib-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3571.txt This document describes a portion of the Policy Information Base (PIB) to control policy usage collection and reporting in a device. The provisioning classes specified here allow a Policy Decision Point (PDP) to select which policy objects should collect usage information, what information should be collected and when it should be reported. This PIB requires the presence of other PIBs (defined elsewhere) that provide the policy objects from which usage information is collected. This document is a product of the Resource Allocation Protocol Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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: <030806092818.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3571 --OtherAccess Content-Type: Message/External-body; name="rfc3571.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <030806092818.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-rap@ops.ietf.org Wed Aug 6 13:39:19 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26075 for ; Wed, 6 Aug 2003 13:39:19 -0400 (EDT) Received: from lserv by psg.com with local (Exim 4.20) id 19kSFf-000Iwa-R9 for rap-data@psg.com; Wed, 06 Aug 2003 17:39:07 +0000 Received: from [127.0.0.1] (helo=roam.psg.com) by psg.com with esmtp (Exim 4.20) id 19kSFc-000IwE-9T for rap@ops.ietf.org; Wed, 06 Aug 2003 17:39:05 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com ident=randy) by roam.psg.com with esmtp (Exim 4.20) id 19kSFe-000Mkc-HU for rap@ops.ietf.org; Wed, 06 Aug 2003 10:39:06 -0700 Message-Id: <200308061629.h76GTdJ16297@gamma.isi.edu> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="MIMEStream=_0+22323_443254259715990_4176055022" To: IETF-Announce: ; Subject: RFC 3571 on Framework Policy Information Base for Usage Feedback Cc: rfc-editor@rfc-editor.org, rap@ops.ietf.org From: rfc-editor@rfc-editor.org Date: Wed, 06 Aug 2003 09:29:39 -0700 X-Spam-Status: No, hits=2.8 required=5.0 tests=NO_REAL_NAME,TO_MALFORMED version=2.53 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) Sender: owner-rap@ops.ietf.org Precedence: bulk --MIMEStream=_0+22323_443254259715990_4176055022 A new Request for Comments is now available in online RFC libraries. RFC 3571 Title: Framework Policy Information Base for Usage Feedback Author(s): D. Rawlins, A. Kulkarni, K. Ho Chan, M. Bokaemper, D. Dutt Status: Informational Date: August 2003 Mailbox: Diana.Rawlins@mci.com, amol.kulkarni@intel.com, khchan@nortelnetworks.com, mbokaemper@juniper.net, ddutt@cisco.com Pages: 35 Characters: 70894 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rap-feedback-fr-pib-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3571.txt This document describes a portion of the Policy Information Base (PIB) to control policy usage collection and reporting in a device. The provisioning classes specified here allow a Policy Decision Point (PDP) to select which policy objects should collect usage information, what information should be collected and when it should be reported. This PIB requires the presence of other PIBs (defined elsewhere) that provide the policy objects from which usage information is collected. This document is a product of the Resource Allocation Protocol Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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. --MIMEStream=_0+22323_443254259715990_4176055022 Content-Type: Multipart/Alternative; boundary="MIMEStream=_1+140987_0172993894336_66629960748" --MIMEStream=_1+140987_0172993894336_66629960748 Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <030806092818.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3571 --MIMEStream=_1+140987_0172993894336_66629960748 Content-Type: Message/External-body; name="rfc3571.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <030806092818.RFC@RFC-EDITOR.ORG> --MIMEStream=_1+140987_0172993894336_66629960748-- --MIMEStream=_0+22323_443254259715990_4176055022-- From owner-rap@ops.ietf.org Thu Aug 7 17:42:48 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04431 for ; Thu, 7 Aug 2003 17:42:48 -0400 (EDT) Received: from lserv by psg.com with local (Exim 4.20) id 19ksVb-0004pq-IC for rap-data@psg.com; Thu, 07 Aug 2003 21:41:19 +0000 Received: from [127.0.0.1] (helo=roam.psg.com) by psg.com with esmtp (Exim 4.20) id 19ksVZ-0004pU-NC for rap@ops.ietf.org; Thu, 07 Aug 2003 21:41:17 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com ident=randy) by roam.psg.com with esmtp (Exim 4.20) id 19ksVa-000NEi-EE for rap@ops.ietf.org; Thu, 07 Aug 2003 14:41:18 -0700 Message-ID: <3F321C17.8030403@francetelecom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 07 Aug 2003 11:29:59 +0200 From: Olivier Dubuisson To: Diana.Rawlins@mci.com, amol.kulkarni@intel.com, khchan@nortelnetworks.com, mbokaemper@juniper.net, ddutt@cisco.com CC: rap@ops.ietf.org Subject: OIDs defined in RFC 3571 X-Spam-Status: No, hits=-6.4 required=5.0 tests=BAYES_10,SIGNATURE_SHORT_SPARSE version=2.53 X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) Sender: owner-rap@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit I'm please to inform you that all the object identifiers (OID) defined in RFC 3571 have been automatically extracted and are now available (together with their associated description) in the OID repository at http://oid.elibel.tm.fr -- Olivier DUBUISSON france telecom R&D DTL/TAL - 22307 Lannion Cedex - France t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/