|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved as IETF document
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses the reference for version parameters.
|
|
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/?option=rfc_search&rfc_search=6838
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 6838 has been in existence since 2013.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC is a standards-track document and is currently in the "Proposed Standard" state.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
See clause 8
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[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./
/
[RFC2978] Freed, N. and J. Postel, "IANA Charset Registration/
Procedures", BCP 19, RFC 2978, October 2000./
/
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML/
Media Types", RFC 3023, January 2001./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", STD 63, RFC 3629, November 2003./
/
[RFC3979] Bradner, S., "Intellectual Property Rights in IETF/
Technology", BCP 79, RFC 3979, March 2005./
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,/
"Uniform Resource Identifier (URI): Generic/
Syntax", STD 66, RFC 3986, January 2005./
/
[RFC4855] Casner, S., "Media Type Registration of RTP Payload/
Formats", RFC 4855, February 2007./
/
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for/
Writing an IANA Considerations Section in RFCs",/
BCP 26, RFC 5226, May 2008./
/
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for/
Syntax Specifications: ABNF", STD 68, RFC 5234,/
January 2008./
/
[RFC5378] Bradner, S. and J. Contreras, "Rights Contributors/
Provide to the IETF Trust", BCP 78, RFC 5378,/
November 2008./
/
[RFC6532] Yang, A., Steele, S., and N. Freed,/
"Internationalized Email Headers", RFC 6532,/
February 2012./
/
[RFC6657] Melnikov, A. and J. Reschke, "Update to MIME/
regarding "charset" Parameter Handling in Textual/
Media Types", RFC 6657, July 2012./
/
[RFC6839] Hansen, T. and A. Melnikov, "Additional Media Type/
Structured Syntax Suffixes", RFC 6839,/
January 2013./
[MacOSFileTypes] Apple Computer, Inc., "Mac OS: File Type and/
Creator Codes, and File Formats", Apple Knowledge/
Base Article 55381, June 1993,/
http://www.info.apple.com/kbnum/n55381./
/
[RFC2026] Bradner, S., "The Internet Standards Process --/
Revision 3", BCP 9, RFC 2026, October 1996./
/
[RFC2048] Freed, N., Klensin, J., and J. Postel,/
"Multipurpose Internet Mail Extensions (MIME) Part/
Four: Registration Procedures", BCP 13, RFC 2048,/
November 1996./
[RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and/
Encoded Word Extensions:/
Character Sets, Languages, and Continuations",/
RFC 2231, November 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./
/
[RFC4288] Freed, N. and J. Klensin, "Media Type/
Specifications and Registration Procedures",/
BCP 13, RFC 4288, December 2005./
/
[RFC5987] Reschke, J., "Character Set and Language Encoding/
for Hypertext Transfer Protocol (HTTP) Header Field/
Parameters", RFC 5987, August 2010./
/
[RFC6648] Saint-Andre, P., Crocker, D., and M. Nottingham,/
"Deprecating the "X-" Prefix and Similar Constructs/
in Application Protocols", BCP 178, RFC 6648,/
June 2012.
|
|
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):
|
|
|
None
|
|
