idnits 2.17.1 draft-yevstifeyev-httpbis-http-warning-registry-01.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 (February 8, 2011) is 4797 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT M. Yevstifeyev 3 Intended Status: Informational February 8, 2011 4 Expires: August 12, 2011 6 IANA 'Hypertext Transfer Protocol (HTTP) Warning Codes' Registry 7 9 Abstract 11 This document establishes IANA 'Hypertext Transfer Protocol (HTTP) 12 Warning Codes' registry. 14 Status of this Memo 16 This Internet-Draft is submitted to IETF in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as 22 Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 Copyright and License Notice 37 Copyright (c) 2011 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Registry Description . . . . . . . . . . . . . . . . . . . . . 2 55 2.1. The Name of the Registry . . . . . . . . . . . . . . . . . 2 56 2.2. The Format of the Registry . . . . . . . . . . . . . . . . 2 57 2.3. Registration Procedures . . . . . . . . . . . . . . . . . . 3 58 2.4. Sub-Registries . . . . . . . . . . . . . . . . . . . . . . 3 59 3. The Initial Contents of the Registry . . . . . . . . . . . . . . 3 60 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 61 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 62 6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 63 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 65 1. Introduction 67 RFC 2616 [RFC2616] - the Hypertext Transfer Protocol (HTTP) 68 specification - defined the 'Warning' header field, that is used to 69 transfer minor warnings to HTTP hosts. This header field uses 70 warning codes, that should be assigned by Internet Assigned Numbers 71 Authority (IANA), for identifying warnings, but no appropriate 72 registry has been created so far. This document establishes such 73 registry. 75 1.1. Terminology 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in RFC 2119 [RFC2119]. 81 2. Registry Description 83 2.1. The Name of the Registry 85 The name of created registry is 'Hypertext Transfer Protocol (HTTP) 86 Warning Codes'. 88 2.2. The Format of the Registry 90 The 'Hypertext Transfer Protocol (HTTP) Warning Codes' registry 91 consists of 3 values: Warning Code, Description and Reference. They 92 are described below: 94 Warning Code - an integer; refers to the value used in 'Warning' 95 header field. Values form 100 to 299 are assigned. Values 100-199 96 are used for identifying warnings connected with caching and refer 97 to freshness and validity of cached data. Values 200-299 refer to 98 other persistent warnings. 100 Description - a brief decryption of warning code. 102 Reference - the reference document, that defines the warning code. 104 2.3. Registration Procedures 106 New assignments to 'Hypertext Transfer Protocol (HTTP) Warning Codes' 107 registry SHALL be made following the 'IETF Consensus' policies. 108 [RFC5226] 110 2.4. Sub-Registries 112 No sub-registries are currently defined in 'Hypertext Transfer 113 Protocol (HTTP) Warning Codes' registry. 115 3. The Initial Contents of the Registry 117 This section contains the initial contents of the 'Hypertext Transfer 118 Protocol (HTTP) Warning Codes' registry. 120 +--------+-------------------------------------+-----------+ 121 | Code | Description | Reference | 122 +--------+-------------------------------------+-----------+ 123 |100-109 | Unassigned | RFC xxxx | 124 |110 | Stale Response | RFC 2616 | 125 |111 | Revalidation Failed | RFC 2616 | 126 |112 | Disconnected Operation | RFC 2616 | 127 |113 | Heuristic Expiration | RFC 2616 | 128 |114-198 | Unassigned | RFC xxxx | 129 |199 | Miscellaneous Warning | RFC 2616 | 130 |200-213 | Unassigned | RFC xxxx | 131 |214 | Transformation Applied | RFC 2616 | 132 |215-298 | Unassigned | RFC xxxx | 133 |299 | Miscellaneous Persistent Warning | RFC 2616 | 134 +--------+-------------------------------------+-----------+ 135 [RFC Editor: Replace xxxx with assigned RFC number] 137 4. Security Considerations 139 Creation of this registry does not introduce any new security issues 140 to HTTP. 142 5. IANA Considerations 144 IANA is asked to create the 'Hypertext Transfer Protocol (HTTP) 145 Warning Codes' registry following Section 2 of this document and 146 populate it with the initial values as described in Section 3. 148 6. Normative References 150 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 151 Requirement Levels", BCP 14, RFC 2119, March 1997. 153 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 154 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 155 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 157 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 158 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 159 May 2008. 161 Author's Addresses 163 Mykyta Yevstifeyev 164 8 Kuzovkov St., flat 25 165 Kotovsk, Ukraine 167 EMail: evnikita2@gmail.com