|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 8037 (2017)
|
|
Title:
|
CFRG Elliptic Curve Diffie-Hellman (ECDH) and Signatures in JSON Object Signing and Encryption (JOSE), January 2017.
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
This specification allows the use of CFRG
|
|
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=8037
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
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:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
./
/
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,/
./
/
[RFC7515] Jones, M., Bradley, J., and N. Sakimura, "JSON Web/
Signature (JWS)", RFC 7515, DOI 10.17487/RFC7515, May/
2015, ./
/
[RFC7517] Jones, M., "JSON Web Key (JWK)", RFC 7517,/
DOI 10.17487/RFC7517, May 2015,/
./
/
[RFC7518] Jones, M., "JSON Web Algorithms (JWA)", RFC 7518,/
DOI 10.17487/RFC7518, May 2015,/
./
/
[RFC7638] Jones, M. and N. Sakimura, "JSON Web Key (JWK)/
Thumbprint", RFC 7638, DOI 10.17487/RFC7638, September/
2015, ./
/
[RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves/
for Security", RFC 7748, DOI 10.17487/RFC7748, January/
2016, ./
/
[RFC8032] Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital/
Signature Algorithm (EdDSA)", RFC 8032,/
DOI 10.17487/RFC8032, January 2017,/
.
|
|
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
|
|
