|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
U2FRawMsgs
|
|
Title:
|
FIDO U2F Raw Message Formats v1.0
|
|
|
2.
|
Status of approval:
|
|
|
Approved 11 April 2017 as Proposed Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
The referenced document constitutes provisions of X.1278
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding FIDOs is available at:
https://fidoalliance.org/wp-content/uploads/FIDO_Alliance_-_Membership_Agreement.pdf and summarized at https://fidoalliance.org/wp-content/uploads/FIDO-IPR-flowchart-v255.pdf
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Approved 11 April 2017 as Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This document has been reviewed by FIDO Alliance Members and is endorsed as a Proposed Standard. It is a stable document and may be used as reference material or cited from another document.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ECDSA-ANSI]/
Public Key Cryptography for the Financial Services Industry: The Elliptic Curve Digital Signature Algorithm (ECDSA), ANSI X9.62-2005. American National Standards Institute, November 2005, URL: http://webstore.ansi.org/RecordDetail.aspx?sku=ANSI+X9.62%3A2005 /
[ECMA-262]/
ECMAScript Language Specification. URL: https://tc39.github.io/ecma262/ /
[FIDOAppIDAndFacets]/
D. Balfanz, B. Hill, R. Lindemann, D. Baghdasaryan, FIDO AppID and Facets v1.0. FIDO Alliance Proposed Standard. URLs: /
HTML: https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-appid-and-facets-v1.2-ps-20170411.html/
PDF: https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-appid-and-facets-v1.2-ps-20170411.pdf /
[FIDOGlossary]/
R. Lindemann, D. Baghdasaryan, B. Hill, J. Hodges, FIDO Technical Glossary. FIDO Alliance Implementation Draft. URLs: /
HTML: https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-glossary-v1.2-ps-20170411.html /
PDF: https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-glossary-v1.2-ps-20170411.pdf /
[RFC2119]/
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119 /
[RFC4648]/
S. Josefsson, The Base16, Base32, and Base64 Data Encodings (RFC 4648), IETF, October 2006, URL: http://www.ietf.org/rfc/rfc4648.txt /
[U2FHeader]/
J. Ehrensvard, FIDO U2F HID Header Files v1.0. FIDO Alliance Review Draft (Work in progress.) URL: https://github.com/fido-alliance/u2f-specs/blob/master/inc/u2f.h /
[WebIDL]/
Cameron McCormack; Boris Zbarsky; Tobie Langel. Web IDL. 15 December 2016. W3C Editor's Draft. URL: https://heycam.github.io/webidl/
|
|
9.
|
Qualification of
FIDO:
|
|
|
FIDO Alliance can be considered to meet the qualifying criteria for ITU-T A.5, as long as such qualification is limited only to FIDO standards which have reached the final stage of FIDO development, known as "Proposed Standard Expanded to the world". Any technical documentation of FIDO Alliance which has not reached that stage cannot be considered as a fully developed standard of FIDO Alliance, and consequently, should not be included or referenced in an ITU-T Recommendation. (SG17-TD828 March2018)https://www.itu.int/md/T17-SG17-180320-TD-PLEN-0828/en
|
|
10.
|
Other (for any supplementary information):
|
|
|
None.
|
