|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards track, obsoleted by RFC 4234.
|
|
3.
|
Justification for the specific reference:
|
|
|
BNF syntax is used throughout this Recommendation. Incorporating the full text of the RFC would be inappropriate due to size and specific content should only be referenced.
|
|
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=2234
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 2234 was published November 1997 and is a standards track RFC. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2234 was published November 1997 and is a standards track RFC. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 2234 is referenced in H.248.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Coded Character Set--7-Bit American Standard Code for Information Interchange, ANSI X3.4-1986./
[2] Crocker, D., Vittal, J., Pogran, K., and D. Henderson, "Standard for the Format of ARPA Network Text Message," RFC 733, November 1977./
[3] 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):
|
|
|
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.
|
