INTERNET-DRAFT M. Yevstifeyev Intended Status: Informational February 8, 2011 Expires: August 12, 2011 IANA 'Hypertext Transfer Protocol (HTTP) Warning Codes' Registry Abstract This document establishes IANA 'Hypertext Transfer Protocol (HTTP) Warning Codes' registry. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright and License Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Yevstifeyev Expires August 12, 2011 [Page 1] INTERNET DRAFT HTTP Warnings Registry February 8, 2011 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 2. Registry Description . . . . . . . . . . . . . . . . . . . . . 2 2.1. The Name of the Registry . . . . . . . . . . . . . . . . . 2 2.2. The Format of the Registry . . . . . . . . . . . . . . . . 2 2.3. Registration Procedures . . . . . . . . . . . . . . . . . . 3 2.4. Sub-Registries . . . . . . . . . . . . . . . . . . . . . . 3 3. The Initial Contents of the Registry . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction RFC 2616 [RFC2616] - the Hypertext Transfer Protocol (HTTP) specification - defined the 'Warning' header field, that is used to transfer minor warnings to HTTP hosts. This header field uses warning codes, that should be assigned by Internet Assigned Numbers Authority (IANA), for identifying warnings, but no appropriate registry has been created so far. This document establishes such registry. 1.1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2. Registry Description 2.1. The Name of the Registry The name of created registry is 'Hypertext Transfer Protocol (HTTP) Warning Codes'. 2.2. The Format of the Registry The 'Hypertext Transfer Protocol (HTTP) Warning Codes' registry consists of 3 values: Warning Code, Description and Reference. They Yevstifeyev Expires August 12, 2011 [Page 2] INTERNET DRAFT HTTP Warnings Registry February 8, 2011 are described below: Warning Code - an integer; refers to the value used in 'Warning' header field. Values form 100 to 299 are assigned. Values 100-199 are used for identifying warnings connected with caching and refer to freshness and validity of cached data. Values 200-299 refer to other persistent warnings. Description - a brief decryption of warning code. Reference - the reference document, that defines the warning code. 2.3. Registration Procedures New assignments to 'Hypertext Transfer Protocol (HTTP) Warning Codes' registry SHALL be made following the 'IETF Consensus' policies. [RFC5226] 2.4. Sub-Registries No sub-registries are currently defined in 'Hypertext Transfer Protocol (HTTP) Warning Codes' registry. 3. The Initial Contents of the Registry This section contains the initial contents of the 'Hypertext Transfer Protocol (HTTP) Warning Codes' registry. +--------+-------------------------------------+-----------+ | Code | Description | Reference | +--------+-------------------------------------+-----------+ |100-109 | Unassigned | RFC xxxx | |110 | Stale Response | RFC 2616 | |111 | Revalidation Failed | RFC 2616 | |112 | Disconnected Operation | RFC 2616 | |113 | Heuristic Expiration | RFC 2616 | |114-198 | Unassigned | RFC xxxx | |199 | Miscellaneous Warning | RFC 2616 | |200-213 | Unassigned | RFC xxxx | |214 | Transformation Applied | RFC 2616 | |215-298 | Unassigned | RFC xxxx | |299 | Miscellaneous Persistent Warning | RFC 2616 | +--------+-------------------------------------+-----------+ [RFC Editor: Replace xxxx with assigned RFC number] Yevstifeyev Expires August 12, 2011 [Page 3] INTERNET DRAFT HTTP Warnings Registry February 8, 2011 4. Security Considerations Creation of this registry does not introduce any new security issues to HTTP. 5. IANA Considerations IANA is asked to create the 'Hypertext Transfer Protocol (HTTP) Warning Codes' registry following Section 2 of this document and populate it with the initial values as described in Section 3. 6. Normative References [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. Author's Addresses Mykyta Yevstifeyev 8 Kuzovkov St., flat 25 Kotovsk, Ukraine EMail: evnikita2@gmail.com Yevstifeyev Expires August 12, 2011 [Page 4]