< draft-schoenw-opsawg-copspr-historic-03.txt		draft-schoenw-opsawg-copspr-historic-04.txt >
	Network Working Group J. Schoenwaelder		Network Working Group J. Schoenwaelder
	Internet-Draft Jacobs University Bremen		Internet-Draft Jacobs University Bremen
	Obsoletes: 3084, 3159, 3317, 3318, 3571 November 23, 2015		Intended status: Informational April 13, 2016
	(if approved)		Expires: October 15, 2016
	Intended status: Informational
	Expires: May 26, 2016
	Reclassification of COPS-PR and SPPI to Historic		Reclassification of COPS-PR and SPPI to Historic
	draft-schoenw-opsawg-copspr-historic-03.txt		draft-schoenw-opsawg-copspr-historic-04.txt
	Abstract		Abstract
	This memo reclassifies RFC 3084, COPS Usage for Policy Provisioning,		This memo requests the reclassification of RFC 3084, COPS Usage for
	and RFC 3159, Structure of Policy Provisioning Information, to		Policy Provisioning, RFC 3159, Structure of Policy Provisioning
	Historic status. This memo obsoletes RFC 3084, RFC 3159, RFC 3317,		Information, RFC 3317, Differentiated Services Quality of Service
	RFC 3318, and RFC 3571.		Policy Information Base, RFC 3318, Framework Policy Information Base,
			and RFC 3571, Framework Policy Information Base for Usage, Feedback,
			to Historic status.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on May 26, 2016.		This Internet-Draft will expire on October 15, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2016 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	2. Reclassification . . . . . . . . . . . . . . . . . . . . . . 2		2. Reclassification . . . . . . . . . . . . . . . . . . . . . . 2
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 3		3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
	5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3		5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
	5.1. Normative References . . . . . . . . . . . . . . . . . . 3		5.1. Normative References . . . . . . . . . . . . . . . . . . 3
	5.2. Informative References . . . . . . . . . . . . . . . . . 4		5.2. Informative References . . . . . . . . . . . . . . . . . 4
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
	1. Introduction		1. Introduction
	The purpose of this document is to reclassify the COPS Usage for		The purpose of this document is to request and explain the
	Policy Provisioning (COPS-PR) [RFC3084] and the Structure of Policy		reclassification of the COPS Usage for Policy Provisioning (COPS-PR)
	Provisioning Information (SPPI) [RFC3159] along with the		[RFC3084] and the Structure of Policy Provisioning Information (SPPI)
	Differentiated Services Quality of Service Policy Information Base		[RFC3159] along with the Differentiated Services Quality of Service
	[RFC3317], the Framework Policy Information Base [RFC3318], and the		Policy Information Base [RFC3317], the Framework Policy Information
	Framework Policy Information Base for Usage Feedback [RFC3571] to		Base [RFC3318], and the Framework Policy Information Base for Usage
	Historic status.		Feedback [RFC3571] to Historic status.
	2. Reclassification		2. Reclassification
	The COPS-PR protocol was designed to provision policy information		The COPS-PR protocol was designed to provision policy information
	from a Policy Decision Point (PDP) to a Policy Enforcement Point		from a Policy Decision Point (PDP) to a Policy Enforcement Point
	(PEP). The SPPI data modeling language supports COPS-PR by providing		(PEP). The SPPI data modeling language supports COPS-PR by providing
	a data modeling language for specifying Policy Information Bases		a data modeling language for specifying Policy Information Bases
	(PIBs).		(PIBs).
	The COPS-PR / SPPI technology has seen limited deployment. The		The COPS-PR / SPPI technology has seen limited deployment. The
	skipping to change at page 3, line 5 ¶		skipping to change at page 3, line 5 ¶
	creation of the XML-based Network Configuration Protocol (NETCONF)		creation of the XML-based Network Configuration Protocol (NETCONF)
	[RFC6241] and an associated data modeling language called YANG		[RFC6241] and an associated data modeling language called YANG
	[RFC6020]. These new protocols are specifically designed to match		[RFC6020]. These new protocols are specifically designed to match
	the needs of network operators. Configuration management related		the needs of network operators. Configuration management related
	efforts in the IETF Operations and Management Area are now centered		efforts in the IETF Operations and Management Area are now centered
	on NETCONF and YANG.		on NETCONF and YANG.
	It is therefore appropriate to reclassify COPS-PR and SPPI to		It is therefore appropriate to reclassify COPS-PR and SPPI to
	Historic status, as described in [RFC2026]. Along with this action,		Historic status, as described in [RFC2026]. Along with this action,
	the QoS provisioning data models written in the SPPI language and		the QoS provisioning data models written in the SPPI language and
	published in [RFC3317], [RFC3318], and [RFC3571] are reclassified to		published in [RFC3317], [RFC3318], and [RFC3571] are requested to be
	Historic status as well.		reclassified to Historic status as well.
	3. Security Considerations		3. Security Considerations
	Reclassifying RFC 3084, RFC 3159, RFC 3317, RFC 3318, and RFC 3571		Reclassifying RFC 3084, RFC 3159, RFC 3317, RFC 3318, and RFC 3571
	has no security implications.		has no security implications.
	4. IANA Considerations		4. IANA Considerations
	The IANA rules for registering PIB modules defined in [RFC3159]		The IANA rules for registering PIB modules defined in [RFC3159]
	remain in force.		remain in force.
End of changes. 7 change blocks.
	20 lines changed or deleted		20 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/