Draft: draft-ietf-cose-msg

Commentary: The CFRG EC algorithms are currently too far in the future to keep . Remove the ad put in the to be done later document .
The basic mathematics for Elliptic Curve Diffie-Hellman can be found
in RFC6090.  Two new curves have been defined in I-D.irtf-cfrg-
curves.
The basic mathematics for Elliptic Curve Diffie-Hellman can be found
in RFC6090.
This document defines these algorithms to be used with the curves
P-256, P-384, P-521, X25519 and X448.  Implementations MUST verify
that the key type and curve are correct, different curves are
restricted to different key types.  Implementations MUST verify that
the curve and algorithm are appropriate for the entities involved.
This document defines these algorithms to be used with the curves
P-256, P-384, P-521.  Implementations MUST verify that the key type
and curve are correct, different curves are restricted to different
key types.  Implementations MUST verify that the curve and algorithm
are appropriate for the entities involved.
One class of Elliptic Curve mathematics allows for a point to be
completely defined using the curve and the x coordinate of the point
on the curve.  The two curves that are initially setup to use is
point format are Curve 25519 and Curve 448 which are defined in I-
D.irtf-cfrg-curves.
contains an identifier of the curve to be used with the key.
[CREF14] The curves defined in this document for this key type can
be found in table-ec-curves.  Other curves may be registered in
the future and private curves can be used as well.
contains the x coordinate for the EC point.  The octet string
represents a little-endian encoding of x.
contains the private key.
For public keys, it is REQUIRED that 'crv' and 'x' be present in the
structure.  For private keys, it is REQUIRED that 'crv' and 'd' be
present in the structure.  For private keys, it is RECOMMENDED that
'x' also be present, but it can be recomputed from the required
elements and omitting it saves on space.
Two different key structures could be defined for Elliptic Curve
keys.  One version uses both an x and a y coordinate, potentially
with point compression.  This is the traditional EC point
representation that is used in RFC5480.  The other version uses only
the x coordinate as the y coordinate is either to be recomputed or
not needed for the key agreement operation Currently no algorithms
are defined using this key structure.
This registry will be initially populated by the values in table-
ec1-keys, table-ec2-keys, table-rsa-keys, and table-symmetric-keys.
The specification column for all of these entries will be this
document.
This registry will be initially populated by the values in table-
ec2-keys, table-rsa-keys, and table-symmetric-keys.  The
specification column for all of these entries will be this document.
This section registers the "application/cose" and "application/
cose+cbor" media types in the "Media Types" registry.  [CREF17] These
media types are used to indicate that the content is a COSE_MSG.
This section registers the "application/cose" and "application/
cose+cbor" media types in the "Media Types" registry.  [CREF15] These
media types are used to indicate that the content is a COSE_MSG.