I suggest an Appendix with this ASN.1 Module:
~~~
PrefixLengthsModule-2025
{ iso(1) member-body(2) us(840) rsadsi(113549)
pkcs(1) pkcs9(9) smime(16) mod(0) TBD0 }
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
-- EXPORTS ALL --
IMPORTS
CONTENT-TYPE
FROM CryptographicMessageSyntax-2010 -- in [RFC6268]
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
pkcs-9(9) smime(16) modules(0) id-mod-cms-2009(58) } ;
ContentSet CONTENT-TYPE ::= { ct-prefixlenCSVwithCRLF, ... }
ct-prefixlenCSVwithCRLF CONTENT-TYPE ::=
{ TYPE OCTET STRING IDENTIFIED BY id-ct-prefixlenCSVwithCRLF }
id-ct-prefixlenCSVwithCRLF OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
pkcs-9(9) smime(16) ct(1) TBD1 }
END
~~~
We will also need IANA to assign an OID for the module. This is a minor update
to the IANA considerations section.
Russ
> On Dec 2, 2025, at 5:09 PM, David Dong via RT
> <[email protected]> wrote:
>
> Dear Authors/Chairs/ADs,
>
> Please see below for feedback for the SMI Security for S/MIME CMS Content
> Type registration from the expert.
>
> Best regards,
>
> David Dong
> IANA Services Sr. Specialist
>
> On Tue Dec 02 20:45:44 2025, [email protected] wrote:
>> Did a quick look at this and have a questions about why there’s no
>> ASN.1 module that formally defines the content type? The knock on
>> effects for adding a module that come to mind would be:
>> - another section for the ASN.1 module
>> - another IANA request for SMIME ASN.1 Module Arc
>> - normative refs to X.680, X.690, & RFC 5911 (imports CONTENT-TYPE)
>>
>> Cheers,
>> spt
>>
>>> On Dec 1, 2025, at 18:50, David Dong via RT <drafts-expert-review-
>>> [email protected]> wrote:
>>>
>>> Dear Sean Turner (cc: opsawg WG),
>>>
>>> As the backup designated expert for the SMI Security for S/MIME CMS
>>> Content Type registry, can you review the proposed registration in
>>> draft-ietf-opsawg-prefix-lengths-08 for us? Would you be able to
>>> review this before the IESG telechat this week?
>>>
>>> Please note that Russ is a co-author on this document.
>>>
>>> Please see:
>>>
>>> https://datatracker.ietf.org/doc/draft-ietf-opsawg-prefix-lengths/
>>>
>>> If this is OK, when the IESG approves the document for publication,
>>> we'll make the registration at:
>>>
>>> https://www.iana.org/assignments/smi-numbers/
>>>
>>> With thanks,
>>>
>>> David Dong
>>> IANA Services Sr. Specialist
>>>
>>> On Thu Nov 13 23:10:41 2025, david.dong wrote:
>>>> Dear Sean Turner (cc: opsawg WG),
>>>>
>>>> As the backup designated expert for the SMI Security for S/MIME CMS
>>>> Content Type registry, can you review the proposed registration in
>>>> draft-ietf-opsawg-prefix-lengths-08 for us? Please note that Russ is
>>>> a
>>>> co-author on this document.
>>>>
>>>> Please see:
>>>>
>>>> https://datatracker.ietf.org/doc/draft-ietf-opsawg-prefix-lengths/
>>>>
>>>> The due date is November 27th.
>>>>
>>>> If this is OK, when the IESG approves the document for publication,
>>>> we'll make the registration at:
>>>>
>>>> https://www.iana.org/assignments/smi-numbers/
>>>>
>>>> With thanks,
>>>>
>>>> David Dong
>>>> IANA Services Sr. Specialist
>>>
>
_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
