|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Proposed Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses JSON as defined in the reference.
|
|
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=7493
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 7493 was published in March 2015 and is a standards track RFC. This RFC is used by all browsers for all internet based JSON traffic today.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
N/A
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic", IEEE/
754-2008, 2008, ./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997,/
./
/
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:/
Timestamps", RFC 3339, July 2002,/
./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", STD 63, RFC 3629, November 2003,/
./
/
[RFC4627] Crockford, D., "The application/json Media Type for/
JavaScript Object Notation (JSON)", RFC 4627, July 2006,/
./
/
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 4648, October 2006,/
./
/
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data/
Interchange Format", RFC 7159, March 2014,/
./
/
[UNICODE] The Unicode Consortium, "The Unicode Standard",/
.
|
|
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
|
|
