Re: [Sidrops] WG Adoption call for draft-spaghetti-sidrops-rfc6482bis-00 (10/2-10/17)

I support adoption.  I also provide a few comments below.

This draft should be consistent with CMS (RFC 5652) about the use of "content-type" and "ContentType" and "content type".

In CMS, "ContentType" is the ASN.1 type for an OID that tells the content type that be being signed, encrypted, or otherwise protected.

In CMS, the "content-type" attribute carries the OID associated with the EncapsulatedContentInfo, which allows the OID to be covered by the signature.

In CMS, the "content type" phrase is used when not talking about the ContentType or content-type attribute.

Therefore, I think Section 3 should be:

3.  The ROA Content Type

   The ContentType for a ROA is defined as routeOriginAuthz and has the
   numerical value of 1.2.840.113549.1.9.16.1.24.

   This OID MUST appear both within the eContentType in the
   encapContentInfo object as well as the content-type signed attribute
   in the signerInfo object (see [RFC6488]).

In Section 4, I do not think the inclusion of empty "CONSTRAINED BY" will help an implementer.  That said, I do think the comments are very helpful.

Russ

> On Oct 2, 2022, at 7:38 PM, Keyur Patel <keyur@arrcus.com> wrote:
> 
> Hi Folks,
>  
> The draft author has requested SIDROPS working group adoption call of “A Profile for Route Origin Authorizations (ROAs)”, https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rfc6482bis/ <https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rfc6482bis/>.
>  
> Please send your comments to the list. This adoption call will conclude on October 17 2022.
>  
> Regards,
> Chris & Keyur
>  
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org <mailto:Sidrops@ietf.org>
> https://www.ietf.org/mailman/listinfo/sidrops <https://www.ietf.org/mailman/listinfo/sidrops>