Thank you. I have sent a follow up message to the secretariat to
correct the text in the errata marked as HFDU.
Best regards,
Kathleen
On Wed, Mar 21, 2018 at 3:29 AM, Jim Schaad <ietf(_at_)augustcellars(_dot_)com>
wrote:
It would be
id-aa-encrypKeyPref -- sic -- OBJECT IDENTIFIER ::= ...
Jim
-----Original Message-----
From: smime <smime-bounces(_at_)ietf(_dot_)org> On Behalf Of Sean Turner
Sent: Tuesday, March 20, 2018 10:14 AM
To: Kathleen Moriarty
<Kathleen(_dot_)Moriarty(_dot_)ietf(_at_)gmail(_dot_)com>
Cc: Josh Soref <jsoref(_at_)gmail(_dot_)com>; The IESG
<iesg(_at_)ietf(_dot_)org>; IETF SMIME
<smime(_at_)ietf(_dot_)org>
Subject: Re: [smime] [Errata Held for Document Update] RFC2633 (5019)
On Mar 19, 2018, at 10:52, RFC Errata System
<rfc-editor(_at_)rfc-editor(_dot_)org>
wrote:
Any objections to adding a note in draft-ietf-lamps-rfc5751-bis along the
same lines as the note for receipentKeyId?
It’s slightly different than renaming receipentKeyId because this is an OID
so
you could also do this:
id-aa-encryptKeyPref OBJECT IDENTIFIER ::= id-aa-encrypKeyPref
But I also don’t have an issue with just adding the note.
spt
_______________________________________________
smime mailing list
smime(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/smime
--
Best regards,
Kathleen
_______________________________________________
smime mailing list
smime(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/smime