|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2045 (1996)
|
|
Title:
|
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 2045 contains a complete description of a Base64 encoding. It is not appropriate to include the full text of IETF RFC 2045 here. Rec. X.891 specifies an encoding algorithm for indicating that a Base64 encoding should be used, thus Industry needs to be informed of where the Base64 encoding originated as it was not defined by ISO or ITU-T.
|
|
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=2045
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 2045 was published in November 1996 and is a standards track RFC. Current status: draft standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2045 was published in November 1996 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 2045 is referenced in H.323 and Annex K/H.323. Obsoletes: RFCs 1521, 1522, 1590. Updated by: RFCs 2184, 2231, 5335, RFC 6532. Errata exist.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
None.
|
|
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.
|
