|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFC was approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 8017 (2016), RSA Cryptography Specifications Version 2.2, contains recommendations for the implementation of public-key cryptography and thus is a normative reference for J.dmcd-kl-as.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Approved and implemented specification.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Stable specification.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
This document represents a republication of RSA Laboratories: "PKCS #1 v2.2: RSA Cryptography Standard". Obsoletes: RFC3447
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[GARNER] Garner, H., "The Residue Number System", IRE Transactions/
on Electronic Computers, Volume EC-8, Issue 2, pp./
140-147, DOI 10.1109/TEC.1959.5219515, June 1959./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
http://www.rfc-editor.org/info/rfc2119./
/
[RSA] Rivest, R., Shamir, A., and L. Adleman, "A Method for/
Obtaining Digital Signatures and Public-Key/
Cryptosystems", Communications of the ACM, Volume 21,/
Issue 2, pp. 120-126, DOI 10.1145/359340.359342, February/
1978.
|
|
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):
|
|
|
Reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or to IETF RFCs categorized as Historic or Experimental. Normative references must only be made to IETF RFCs that are Standards Track or to Informational RFCs that have IETF consensus.
|
