1. The document needs to have a short title added to it. 2. Abstract - The text "FIDO Alliance FIDO2 Client to Authenticator Protocol" needs to get cleaned up. It is not clear to me if FIDO2 is supposed to be an abbreviation of the previous FIDO Alliance or not. Flip the sentence to use from or insert specification earlier.
3. Section 1 - I am not sure why you are using the term "related" rather than "the" in this section. This seems to be different than the abstract in that feature. Relate makes me think that it is something that is different but similar in this case. 4. While I guess it is reasonable to have the description of why things are not recommended in the security considerations, I myself would not really think of them as such. However not having a pointer from section 2 to that information seems harsh as we are saying the are not recommended without have a pointer to the discussion. 5. I have problems with the following text: "Implementation of this algorithm is RECOMMENDED because of its widespread use in decentralized systems and those that chose it over the NIST curves." Firstly, this is an incorrect use of the RFC 2119 language, this is not a protocol statement. Secondly, this is not what the recommended column in table 2 means and thus is trying to overload that column with something that is not real. Third, the fact that people chose this over the NIST curves is not necessarily a reason for the IETF to recommended it's implementation. 6. I still want to see in the text the reasoning behind not just using the current ECDSA algorithm in COSE. 7. Add text on checking point is on the curve to section 5.4 -----Original Message----- From: COSE <[email protected]> On Behalf Of [email protected] Sent: Thursday, October 24, 2019 2:35 PM To: [email protected] Cc: [email protected] Subject: [COSE] I-D Action: draft-ietf-cose-webauthn-algorithms-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CBOR Object Signing and Encryption WG of the IETF. Title : COSE and JOSE Registrations for WebAuthn Algorithms Author : Michael B. Jones Filename : draft-ietf-cose-webauthn-algorithms-02.txt Pages : 13 Date : 2019-10-24 Abstract: The W3C Web Authentication (WebAuthn) specification and the FIDO Alliance FIDO2 Client to Authenticator Protocol (CTAP) specification use CBOR Object Signing and Encryption (COSE) algorithm identifiers. This specification registers the following algorithms in the IANA "COSE Algorithms" registry, which are used by WebAuthn and CTAP implementations: RSASSA-PKCS1-v1_5 using SHA-256, SHA-384, SHA-512, and SHA-1, and ECDSA using the secp256k1 curve and SHA-256. It registers the secp256k1 elliptic curve in the IANA "COSE Elliptic Curves" registry. Also, for use with JSON Object Signing and Encryption (JOSE), it registers the algorithm ECDSA using the secp256k1 curve and SHA-256 in the IANA "JSON Web Signature and Encryption Algorithms" registry and the secp256k1 elliptic curve in the IANA "JSON Web Key Elliptic Curve" registry. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cose-webauthn-algorithms/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-cose-webauthn-algorithms-02 https://datatracker.ietf.org/doc/html/draft-ietf-cose-webauthn-algorithms-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-cose-webauthn-algorithms-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
