|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5408 (2009)
|
|
Title:
|
Identity-Based Encryption Architecture and Supporting Data Structures
|
|
|
2.
|
Status of approval:
|
|
|
January 2009 as Internet Standard.
|
|
3.
|
Justification for the specific reference:
|
|
|
Key data structures defined in Annex B of this document uses key data structures protocol specified in IETF RFC 5408
|
|
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 in January 2009 as Informational.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
1 errata are available.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Not known.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[ASCII] ISO/IEC 646:1991 - Information Technology - ISO 7-bit Coded/
Character Set for Information Exchange./
/
[ASN1] ITU-T Recommendation X.680: Information Technology -/
Abstract Syntax Notation One, 1997./
/
[AUTH] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,/
Leach, P., Luotonen, A., and L. Stewart, "HTTP/
Authentication: Basic and Digest Access Authentication",/
RFC 2617, June 1999./
/
[B64] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part One: Format of Internet Message/
Bodies", RFC 2045, November 1996./
/
[CMS] Housley, R., "Cryptographic Message Syntax (CMS)", RFC/
3852, July 2004./
/
[DER] ITU-T Recommendation X.690: OSI Networking and System/
Aspects: Abstract Syntax Notation One (ASN.1), July 2002./
/
[DOS] Ferguson, P. and D. Senie, "Network Ingress Filtering:/
Defeating Denial of Service Attacks which employ IP Source/
Address Spoofing", BCP 38, RFC 2827, May 2000./
/
[HTTP] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter,/
L., Leach, P., and T. Berners-Lee, "Hypertext Transfer/
Protocol -- HTTP/1.1", RFC 2616, June 1999./
/
[HTTPTLS] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000./
/
[IBCS] Boyen, X. and L. Martin, "Identity-Based Cryptography/
Standard (IBCS) #1: Supersingular Curve Implementations of/
the BF and BB1 Cryptosystems", RFC 5091, December 2007./
/
[IRI] Duerst, M. and M. Suignard, "Internationalized Resource/
Identifiers (IRIs)", RFC 3987, January 2005./
/
[KEY] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[PKIX] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,/
Housley, R., and W. Polk, "Internet X.509 Public Key/
Infrastructure Certificate and Certificate Revocation List/
(CRL) Profile", RFC 5280, May 2008./
/
[SMTP] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,/
October 2008./
/
[TLS] Dierks, T. and E. Rescorla, "The Transport Layer Security/
(TLS) Protocol Version 1.2", RFC 5246, August 2008./
/
[URI] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66, RFC/
3986, January 2005./
/
[XML] W3C, Extensible Markup Language (XML) 1.0 (Fourth Edition),/
September 2006./
/
Informative References/
/
[BGPDOS] Turk, D., "Configuring BGP to Block Denial-of-Service/
Attacks", RFC 3882, September 2004./
/
[IBECMS] Martin, L. and M. Schertler, "Using the Boneh-Franklin/
Identity-Based Encryption Algorithm with the Cryptographic/
Message Syntax (CMS)", RFC 5409, January 2009./
/
[NIST] M. Souppaya, J. Wack and K. Kent, "Security Configuration/
Checklist Program for IT Products - Guidance for Checklist/
Users and Developers", NIST Special Publication SP 800-70,/
May 2005./
/
[P1363] IEEE P1363, "Standard Specifications for Public-Key/
Cryptography", 2001./
/
|
|
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.
|
|
