Ines Robles via Datatracker <noreply@xxxxxxxx> wrote:
> 1- It would be nice to add in Terminology section that the document uses the
> terminology of RFC7030 and RFC5272
> 2- Introduction: "reports from implementers suggest..." It would be nice to add
> reference/s here
> 3- Security Considerations:
> It would be nice to add smth like "security considerations from RFC7030 applies
> also for the clarifications described in this document."
done.
> 5- IANA Considerations:
> It would be nice to add the specific registry that IANA should update.
> For example, instead of "IANA is requested to update the "Reference" column for
> the Asymmetric Decryption Key Identifier attribute to also include a reference
> to
> this document." you could add smth like (if applicable): " IANA is requested
> to update the registry SMI Security for S/MIME Attributes
> (1.2.840.113549.1.9.16.2) "
> with the reference of this document as follows:
> Decimal - Description -Reference
> 54 id-aa-asymmDecryptKeyID [RFC7030] [ThisDocument]
> 4- Appendix A: In id-aa-asymmDecryptKeyID OBJECT IDENTIFIER ::= {...}
> 4.1- pkcs9(9) should be pkcs-9(9) ?
I have done this as per Russ Housley's suggestion.
> 4.2- aa(2) should be id-aa(2) ?
I have not done this.
This is in version -09.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
