Committed to connecting the world

  •  

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : X.609.5     
  ITU-T A.5 justification information for referenced document IETF RFC 7231 (2014) in draft X.609.5
1. Clear description of the referenced document:
Name: IETF RFC 7231 (2014)
Title: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
2. Status of approval:
Approved as standards track document (Proposed Standard). It obsoletes RFC2616 and updates RFC 2817. Errata exist.
3. Justification for the specific reference:
Protocol messages are delivered over HTTP.
4. Current information, if any, about IPR issues:
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?draft=&rfc=7231&submit=rfc&doctitle=&group=&holder=&iprtitle=&patent=
5. Other useful information describing the "Quality" of the document:
RFC 7231 was published in June 2014 and is a standards track RFC. It is largely used for World Wide Web service and related Web Browsers. It obsoletes RFC 2616, and updates RFC 2817.
6. The degree of stability or maturity of the document:
RFC 7231 was published in June 2014 and is a standards track RFC. Current standards status of this document can be found at http://tools.ietf.org/html/rfc7231
7. Relationship with other existing or emerging documents:
N/A
8. Any explicit references within that referenced document should also be listed:
Normative References/
/
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part One: Format of Internet Message/
Bodies", RFC 2045, November 1996./
/
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part Two: Media Types", RFC 2046,/
November 1996./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
/
/
Fielding & Reschke Standards Track [Page 85]/
/
/
RFC 7231 HTTP/1.1 Semantics and Content June 2014/
/
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66,/
RFC 3986, January 2005./
/
[RFC4647] Phillips, A., Ed. and M. Davis, Ed., "Matching of Language/
Tags", BCP 47, RFC 4647, September 2006./
/
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234, January 2008./
/
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying/
Languages", BCP 47, RFC 5646, September 2009./
/
[RFC6365] Hoffman, P. and J. Klensin, "Terminology Used in/
Internationalization in the IETF", BCP 166, RFC 6365,/
September 2011./
/
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer/
Protocol (HTTP/1.1): Message Syntax and Routing",/
RFC 7230, June 2014./
/
[RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer/
Protocol (HTTP/1.1): Conditional Requests", RFC 7232,/
June 2014./
/
[RFC7233] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,/
"Hypertext Transfer Protocol (HTTP/1.1): Range Requests",/
RFC 7233, June 2014./
/
[RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,/
Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",/
RFC 7234, June 2014./
/
[RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer/
Protocol (HTTP/1.1): Authentication", RFC 7235, June 2014./
/
11.2. Informative References/
/
/
[BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type/
Specifications and Registration Procedures", BCP 13,/
RFC 6838, January 2013./
/
[BCP178] Saint-Andre, P., Crocker, D., and M. Nottingham,/
"Deprecating the "X-" Prefix and Similar Constructs in/
Application Protocols", BCP 178, RFC 6648, June 2012./
/
/
/
/
/
/
Fielding & Reschke Standards Track [Page 86]/
/
/
RFC 7231 HTTP/1.1 Semantics and Content June 2014/
/
/
[BCP90] Klyne, G., Nottingham, M., and J. Mogul, "Registration/
Procedures for Message Header Fields", BCP 90, RFC 3864,/
September 2004./
/
[OWASP] van der Stock, A., Ed., "A Guide to Building Secure Web/
Applications and Web Services", The Open Web Application/
Security Project (OWASP) 2.0.1, July 2005,/
./
/
[REST] Fielding, R., "Architectural Styles and the Design of/
Network-based Software Architectures",/
Doctoral Dissertation, University of California, Irvine,/
September 2000,/
./
/
[RFC1945] Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext/
Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996./
/
[RFC2049] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part Five: Conformance Criteria and/
Examples", RFC 2049, November 1996./
/
[RFC2068] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T./
Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",/
RFC 2068, January 1997./
/
[RFC2295] Holtman, K. and A. Mutz, "Transparent Content Negotiation/
in HTTP", RFC 2295, March 1998./
/
[RFC2388] Masinter, L., "Returning Values from Forms: multipart//
form-data", RFC 2388, August 1998./
/
[RFC2557] Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,/
"MIME Encapsulation of Aggregate Documents, such as HTML/
(MHTML)", RFC 2557, March 1999./
/
[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./
/
[RFC2774] Frystyk, H., Leach, P., and S. Lawrence, "An HTTP/
Extension Framework", RFC 2774, February 2000./
/
[RFC2817] Khare, R. and S. Lawrence, "Upgrading to TLS Within/
HTTP/1.1", RFC 2817, May 2000./
/
[RFC2978] Freed, N. and J. Postel, "IANA Charset Registration/
Procedures", BCP 19, RFC 2978, October 2000./
/
/
/
Fielding & Reschke Standards Track [Page 87]/
/
/
RFC 7231 HTTP/1.1 Semantics and Content June 2014/
/
/
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 5226,/
May 2008./
/
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security/
(TLS) Protocol Version 1.2", RFC 5246, August 2008./
/
[RFC5322] Resnick, P., "Internet Message Format", RFC 5322,/
October 2008./
/
[RFC5789] Dusseault, L. and J. Snell, "PATCH Method for HTTP",/
RFC 5789, March 2010./
/
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,/
"Network Time Protocol Version 4: Protocol and Algorithms/
Specification", RFC 5905, June 2010./
/
[RFC5987] Reschke, J., "Character Set and Language Encoding for/
Hypertext Transfer Protocol (HTTP) Header Field/
Parameters", RFC 5987, August 2010./
/
[RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010./
/
[RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265,/
April 2011./
/
[RFC6266] Reschke, J., "Use of the Content-Disposition Header Field/
in the Hypertext Transfer Protocol (HTTP)", RFC 6266,/
June 2011./
/
[RFC7238] Reschke, J., "The Hypertext Transfer Protocol (HTTP)/
Status Code 308 (Permanent Redirect)", RFC 7238,/
June 2014./
/
9. Qualification of ISOC/IETF:
9.1-9.6     Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7     The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8     Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
10. Other (for any supplementary information):
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
Note: This form is based on Recommendation ITU-T A.5