1.
|
Clear description of the referenced document:
|
|
|
2.
|
Status of approval:
|
|
Approved standards track document. Obsoletes RFC 4234. Also known as STD 68.
|
3.
|
Justification for the specific reference:
|
|
RFC 2234, which was referenced in the first version of this Recommendation, has been declared obsoleted by RFC 4234, which has been declared obsoleted by RFC 5234. Thus, the original reference has been replaced with a reference to the updated specification.
|
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=5234
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
Internet Standard approved 2008-01, also Known As STD 68. Updated by RFC 7405. Obsoletes RFC 4234. Errata exist.
|
6.
|
The degree of stability or maturity of the document:
|
|
See 5.
|
7.
|
Relationship with other existing or emerging documents:
|
|
References within the referenced RFCs are listed under item 8.
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
Normative References/
/
[US-ASCII] American National Standards Institute, "Coded Character/
Set -- 7-bit American Standard Code for Information/
Interchange", ANSI X3.4, 1986./
/
6.2. Informative References/
/
[RFC733] Crocker, D., Vittal, J., Pogran, K., and D. Henderson,/
"Standard for the format of ARPA network text messages",/
RFC 733, November 1977./
/
[RFC822] Crocker, D., "Standard for the format of ARPA Internet/
text messages", STD 11, RFC 822, August 1982./
|
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
|