Yes, thanks.

> On Apr 11, 2026, at 7:45 AM, Lijun Liao <[email protected]> wrote:
> 
> Hi Russ,
> 
> Thank you for the suggestion. I hope this PR 
> https://github.com/cose-wg/CBOR-certificates/pull/344 reflects your idea.
> 
> Lijun
> 
> 
>> On 7. Apr 2026, at 21:53, Russ Housley <[email protected]> wrote:
>> 
>> There is a registry for RDN attributes. It was created ny RFC 9925, and the 
>> ASN.1 module in RFC 9925 can be used as a template for the assignment of the 
>> naming attribute defined here.
>> 
>> https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.25
>> 
>> Can we change id-at-c509Name to id-rdna-c509Name and assign it in this 
>> registry?
>> 
>> Russ
>> 
>> 
>>> On Mar 2, 2026, at 5:07 PM, [email protected] wrote:
>>> 
>>> Internet-Draft draft-ietf-cose-cbor-encoded-cert-17.txt is now available. It
>>> is a work item of the CBOR Object Signing and Encryption (COSE) WG of the
>>> IETF.
>>> 
>>>   Title:   CBOR Encoded X.509 Certificates (C509 Certificates)
>>>   Authors: John Preuß Mattsson
>>>            Göran Selander
>>>            Shahid Raza
>>>            Joel Höglund
>>>            Martin Furuhed
>>>   Name:    draft-ietf-cose-cbor-encoded-cert-17.txt
>>>   Pages:   88
>>>   Dates:   2026-03-02
>>> 
>>> Abstract:
>>> 
>>>   This document specifies a CBOR encoding of X.509 certificates.  The
>>>   resulting certificates are called C509 certificates.  The CBOR
>>>   encoding supports a large subset of RFC 5280, common certificate
>>>   profiles and is extensible.
>>> 
>>>   Two types of C509 certificates are defined.  One type is an
>>>   invertible CBOR re-encoding of DER-encoded X.509 certificates with
>>>   the signature field copied from the DER encoding.  The other type is
>>>   identical except that the signature is over the CBOR encoding instead
>>>   of the DER encoding, avoiding the use of ASN.1.  Both types of
>>>   certificates have the same semantics as X.509 and the same reduced
>>>   size compared to X.509.
>>> 
>>>   The document also specifies CBOR encoded data structures for
>>>   certificate (signing) requests and certificate request templates, new
>>>   COSE headers, as well as a TLS certificate type and a file format for
>>>   C509.  This document updates RFC 6698; the TLSA selectors registry is
>>>   extended to include C509 certificates.
>>> 
>>> The IETF datatracker status page for this Internet-Draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/
>>> 
>>> There is also an HTML version available at:
>>> https://www.ietf.org/archive/id/draft-ietf-cose-cbor-encoded-cert-17.html
>>> 
>>> A diff from the previous version is available at:
>>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-cose-cbor-encoded-cert-17
>>> 
>>> Internet-Drafts are also available by rsync at:
>>> rsync.ietf.org::internet-drafts
>>> 
>>> 
>>> _______________________________________________
>>> COSE mailing list -- [email protected]
>>> To unsubscribe send an email to [email protected]
>> 
>> _______________________________________________
>> COSE mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
> 
> _______________________________________________
> COSE mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to