FW: RFC 3084 on COPS-PR

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

Good work by the authors and the WG.

SPPI and Framework PIB are next

Bert

> ----------
> From: 	RFC Editor[SMTP:rfc-ed@ISI.EDU]
> Sent: 	Thursday, March 22, 2001 4:22 AM
> Cc: 	rfc-ed@ISI.EDU; rap@ops.ietf.org
> Subject: 	RFC 3084 on COPS-PR
> 
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 3084
> 
>         Title:	    COPS Usage for Policy Provisioning (COPS-PR)
>         Author(s):  K. Chan, J. Seligson, D. Durham, S. Gai,
>                     K. McCloghrie, S. Herzog, F. Reichmeyer,
>                     R. Yavatkar, A. Smith 
>         Status:     Standards Track
> 	Date:       March 2001
>         Mailbox:    khchan@nortelnetworks.com, david.durham@intel.com,
>                     sgai@cisco.com, Herzog@iphighway.com,
>                     kzm@cisco.com, franr@pfn.com,
>                     jseligso@nortelnetworks.com,
>                     raj.yavatkar@intel.com, andrew@allegronetworks.com
> 
>         Pages:      34
>         Characters: 79341
>         Updates/Obsoletes/SeeAlso:    None
> 
>         I-D Tag:    draft-ietf-rap-pr-05.txt
> 
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3084.txt
> 
> 
> This document describes the use of the Common Open Policy Service
> (COPS) protocol for support of policy provisioning (COPS-PR).  This
> specification is independent of the type of policy being provisioned
> (QoS, Security, etc.) but focuses on the mechanisms and conventions
> used to communicate provisioned information between PDPs and PEPs.
> The protocol extensions described in this document do not make any
> assumptions about the policy data model being communicated, but
> describe the message formats and objects that carry the modeled policy
> data.
> 
> This document is a product of the Resource Allocation Protocol Working
> Group of 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.
>