Moved to Historic: RFC 3318 on Framework Policy Information Base
rfc-editor@rfc-editor.org Wed, 27 April 2016 19:11 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0C1512DBDA for <ietf-announce@ietfa.amsl.com>; Wed, 27 Apr 2016 12:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BhLzsJ9rBPpM for <ietf-announce@ietfa.amsl.com>; Wed, 27 Apr 2016 12:11:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EF0112DB63 for <ietf-announce@ietf.org>; Wed, 27 Apr 2016 12:11:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0378518046A; Wed, 27 Apr 2016 12:11:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Moved to Historic: RFC 3318 on Framework Policy Information Base
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160427191110.0378518046A@rfc-editor.org>
Date: Wed, 27 Apr 2016 12:11:10 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/yEfvnj_mrmLKsSN3QBaCYEsc6Ac>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2016 19:11:30 -0000
RFC 3318 has been reclassified as Historic.
RFC 3318
Title: Framework Policy Information Base
Author: R. Sahita, Ed.,
S. Hahn,
K. Chan,
K. McCloghrie
Status: Historic
Stream: IETF
Date: March 2003
Pages: 70
Characters: 144530
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rap-frameworkpib-09.txt
URL: https://www.rfc-editor.org/info/rfc3318
DOI: http://dx.doi.org/10.17487/RFC3318
This document defines a set of PRovisioning Classes (PRCs) and textual
conventions that are common to all clients that provision policy using
Common Open Policy Service (COPS) protocol for Provisioning.
Structure of Policy Provisioning Information (SPPI) describes a
structure for specifying policy information that can then be
transmitted to a network device for the purpose of configuring
policy at that device. The model underlying this structure is one
of well-defined (PRCs) and instances of these
classes (PRIs) residing in a virtual information store called the
Policy Information Base (PIB).
One way to provision policy is by means of the (COPS) protocol with
the extensions for provisioning. This protocol supports multiple
clients, each of which may provision policy for a specific policy
domain such as QoS, virtual private networks, or security.
As described in COPS usage for Policy Provisioning (COPS-PR), each
client supports a non-overlapping and independent set of PIB
modules. However, some PRovisioning Classes are common to all
subject-categories (client-types) and need to be present in
each.
This document is a product of the Resource Allocation Protocol Working Group of the IETF.
HISTORIC: This memo defines a Historic Document 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC