|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved Internet Standard.
|
|
3.
|
Justification for the specific reference:
|
|
|
This IETF standard is referenced in ITU-T Y.oneM2M.SEC.SOL
|
|
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=3548
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 3548 has been in existence since 2003. Obsoleted by RFC 4648. Errata exist.
|
|
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:
|
|
|
RFC 3548 describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, and use of different encoding alphabets.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
[2] Linn, J., "Privacy Enhancement for Internet Electronic Mail:/
Part I: Message Encryption and Authentication Procedures", RFC/
1421, February 1993./
[3] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies",/
RFC 2045, November 1996./
[4] Callas, J., Donnerhacke, L., Finney, H. and R. Thayer, "OpenPGP Message Format", RFC 2440, November 1998./
[5] Eastlake, D., "Domain Name System Security Extensions", RFC 2535, March 1999./
[6] Klyne, G. and L. Masinter, "Identifying Composite Media Features", RFC 2938, September 2000./
[7] Myers, J., "SASL GSSAPI mechanisms", Work in Progress./
[8] Wilcox-O'Hearn, B., "Post to P2P-hackers mailing list", World Wide Web http://zgp.org/pipermail/p2p-hackers/2001-/
September/000315.html, September 2001./
[9] Cerf, V., "ASCII format for Network Interchange", RFC 20, October 1969.
|
|
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
|
|
