idnits 2.17.1 draft-schoenw-opsawg-copspr-historic-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 13, 2016) is 2933 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Schoenwaelder 3 Internet-Draft Jacobs University Bremen 4 Intended status: Informational April 13, 2016 5 Expires: October 15, 2016 7 Reclassification of COPS-PR and SPPI to Historic 8 draft-schoenw-opsawg-copspr-historic-04.txt 10 Abstract 12 This memo requests the reclassification of RFC 3084, COPS Usage for 13 Policy Provisioning, RFC 3159, Structure of Policy Provisioning 14 Information, RFC 3317, Differentiated Services Quality of Service 15 Policy Information Base, RFC 3318, Framework Policy Information Base, 16 and RFC 3571, Framework Policy Information Base for Usage, Feedback, 17 to Historic status. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on October 15, 2016. 36 Copyright Notice 38 Copyright (c) 2016 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Reclassification . . . . . . . . . . . . . . . . . . . . . . 2 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 57 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 59 5.2. Informative References . . . . . . . . . . . . . . . . . 4 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 62 1. Introduction 64 The purpose of this document is to request and explain the 65 reclassification of the COPS Usage for Policy Provisioning (COPS-PR) 66 [RFC3084] and the Structure of Policy Provisioning Information (SPPI) 67 [RFC3159] along with the Differentiated Services Quality of Service 68 Policy Information Base [RFC3317], the Framework Policy Information 69 Base [RFC3318], and the Framework Policy Information Base for Usage 70 Feedback [RFC3571] to Historic status. 72 2. Reclassification 74 The COPS-PR protocol was designed to provision policy information 75 from a Policy Decision Point (PDP) to a Policy Enforcement Point 76 (PEP). The SPPI data modeling language supports COPS-PR by providing 77 a data modeling language for specifying Policy Information Bases 78 (PIBs). 80 The COPS-PR / SPPI technology has seen limited deployment. The 81 Quality of Service (QoS) provisioning data models created within the 82 IETF [RFC3317], [RFC3318], [RFC3571] did not reach IETF consensus for 83 publication on the standards-track and have since then been 84 Informational documents. 86 An IAB Network Management Workshop held in 2002 [RFC3535] led to the 87 creation of the XML-based Network Configuration Protocol (NETCONF) 88 [RFC6241] and an associated data modeling language called YANG 89 [RFC6020]. These new protocols are specifically designed to match 90 the needs of network operators. Configuration management related 91 efforts in the IETF Operations and Management Area are now centered 92 on NETCONF and YANG. 94 It is therefore appropriate to reclassify COPS-PR and SPPI to 95 Historic status, as described in [RFC2026]. Along with this action, 96 the QoS provisioning data models written in the SPPI language and 97 published in [RFC3317], [RFC3318], and [RFC3571] are requested to be 98 reclassified to Historic status as well. 100 3. Security Considerations 102 Reclassifying RFC 3084, RFC 3159, RFC 3317, RFC 3318, and RFC 3571 103 has no security implications. 105 4. IANA Considerations 107 The IANA rules for registering PIB modules defined in [RFC3159] 108 remain in force. 110 5. References 112 5.1. Normative References 114 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 115 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 116 . 118 [RFC3084] Chan, K., Seligson, J., Durham, D., Gai, S., McCloghrie, 119 K., Herzog, S., Reichmeyer, F., Yavatkar, R., and A. 120 Smith, "COPS Usage for Policy Provisioning (COPS-PR)", RFC 121 3084, DOI 10.17487/RFC3084, March 2001, 122 . 124 [RFC3159] McCloghrie, K., Fine, M., Seligson, J., Chan, K., Hahn, 125 S., Sahita, R., Smith, A., and F. Reichmeyer, "Structure 126 of Policy Provisioning Information (SPPI)", RFC 3159, DOI 127 10.17487/RFC3159, August 2001, 128 . 130 [RFC3317] Chan, K., Sahita, R., Hahn, S., and K. McCloghrie, 131 "Differentiated Services Quality of Service Policy 132 Information Base", RFC 3317, DOI 10.17487/RFC3317, March 133 2003, . 135 [RFC3318] Sahita, R., Ed., Hahn, S., Chan, K., and K. McCloghrie, 136 "Framework Policy Information Base", RFC 3318, DOI 10 137 .17487/RFC3318, March 2003, 138 . 140 [RFC3571] Rawlins, D., Kulkarni, A., Ho Chan, K., Bokaemper, M., and 141 D. Dutt, "Framework Policy Information Base for Usage 142 Feedback", RFC 3571, DOI 10.17487/RFC3571, August 2003, 143 . 145 5.2. Informative References 147 [RFC3535] Schoenwaelder, J., "Overview of the 2002 IAB Network 148 Management Workshop", RFC 3535, DOI 10.17487/RFC3535, May 149 2003, . 151 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 152 the Network Configuration Protocol (NETCONF)", RFC 6020, 153 DOI 10.17487/RFC6020, October 2010, 154 . 156 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 157 and A. Bierman, Ed., "Network Configuration Protocol 158 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 159 . 161 Author's Address 163 Juergen Schoenwaelder 164 Jacobs University Bremen 165 Campus Ring 1 166 28725 Bremen 167 Germany 169 Email: j.schoenwaelder@jacobs-university.de