jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-cose-x509

Commentary: as enrollment - roadmap is never gon na get published , and indirection not worth it
In some of these cases, a constrained device is being deployed in the
context of an existing X.509 PKI: for example, in the 6TiSCH
environment, I-D.richardson-enrollment-roadmap describes a device
enrollment solution that relies on the presence of a factory-
installed certificate on the device.  The I-D.ietf-lake-edhoc draft
was also written with the idea that long term certificates could be
used to provide for authentication of devices, and uses them to
establish session keys.  Another possible scenario is the use of COSE
as the basis for a secure messaging application.  This scenario
assumes the presence of long term keys and a central authentication
authority.  Basing such an application on public key certificates
allows it to make use of well established key management disciplines.
In some of these cases, a constrained device is being deployed in the
context of an existing X.509 PKI: for example, I-D.ietf-anima-
constrained-voucher describes a device enrollment solution that
relies on the presence of a factory-installed certificate on the
device.  The I-D.ietf-lake-edhoc draft was also written with the idea
that long term certificates could be used to provide for
authentication of devices, and uses them to establish session keys.
Another possible scenario is the use of COSE as the basis for a
secure messaging application.  This scenario assumes the presence of
long term keys and a central authentication authority.  Basing such
an application on public key certificates allows it to make use of
well established key management disciplines.