Re: [secdir] Security review of draft-ietf-core-coap-14

[Carsten Bormann <[e-mail]>]

Alexey,

thank you for this thoughtful review.

Re your two minor items:

>   raw public key depends on the cipher suite used.  Implementations in
>   RawPublicKey mode MUST support the mandatory to implement cipher
>   suite TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 as specified in
>   [I-D.mcgrew-tls-aes-ccm-ecc],
> 
> It looks like this reference is Normative, while you have it as Informative.

We will add this as a normative reference in draft-ietf-core-coap-15.

>   asymmetric public key pair installed.  An identifier is calculated
>   from the public key as described in Section 2 of
>   [I-D.farrell-decade-ni].  All implementations that support checking
>   RawPublicKey identities MUST support at least the sha-256-120 mode
>   (SHA-256 truncated to 120 bits).  Implementations SHOULD support also
> 
> I think you need a Normative reference to SHA-256 here.

Actually, we specifically require the sha-256-120 mode from draft-farrell-decade-ni (the parenthetical remark is just explanatory), which is a normative reference and in turn has SHA-256 (FIPS PUB 180-3) as a normative reference.

(We also reference RFC 6347, which does not reference SHA-256, but references RFC 5246, which finally references FIPS PUB 180-2.   Of course, we could reference FIPS PUB 180-4, if that helps, but we would like to avoid the "transitive closure" effect.  Or maybe draft-farrell-decade-ni should be updated to FIPS PUB 180-4 before publication.  Or maybe not, which is another reason not to try doing the transitive closure.)

> P.S. I have some Apps specific issues with the document, but I send these separately in my AppsDir review.

Looking forward to it!

Grüße, Carsten