|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards track RFC - Proposed Standard (approved October 1969)
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses ASCII as specified in the reference.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR: https://datatracker.ietf.org/ipr/search/?draft=&rfc=0020&doctitle=&group=&holder=&iprtitle=&patent=&submit=
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 0020 is a Proposed Standard. This document has been reviewed extensively in IETF and widely used in real world.
|
|
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:
|
|
|
ITU-T X.419 Unicode uses ASCII
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
|
|
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):
|
|
|
This coded character set is to be used for the general interchange of information among information processing systems, communication systems, and associated equipment.
|
