
From nobody Wed Jan  6 05:21:01 2021
Return-Path: <ietf@kuehlewind.net>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C90983A0927; Wed,  6 Jan 2021 05:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Bj3eaQI705T; Wed,  6 Jan 2021 05:20:57 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCB3A3A0657; Wed,  6 Jan 2021 05:20:56 -0800 (PST)
Received: from [2a00:20:a013:f004:9de3:73c7:473b:11a2]; authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1kx8k3-0003cK-KX; Wed, 06 Jan 2021 14:20:47 +0100
Content-Type: multipart/alternative; boundary=Apple-Mail-A50AD5CB-5CC8-4146-A45F-E48686A4AA0D
Content-Transfer-Encoding: 7bit
From: =?utf-8?Q?"Mirja_K=C3=BChlewind_=28IETF=29"?= <ietf@kuehlewind.net>
Mime-Version: 1.0 (1.0)
Date: Wed, 6 Jan 2021 14:20:46 +0100
Message-Id: <AD171E90-8F99-44FA-990C-BC4878A20772@kuehlewind.net>
References: <52B573D6-5DB4-41DA-95F1-20C3EB5EEAC0@vigilsec.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, LAMPS <spasm@ietf.org>, IAB <iab@iab.org>
In-Reply-To: <52B573D6-5DB4-41DA-95F1-20C3EB5EEAC0@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: iPhone Mail (18B92)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1609939256;4fb79ca5;
X-HE-SMSGID: 1kx8k3-0003cK-KX
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/X7Uv3GFQg5xAZUj3BM6xHk1MjEU>
Subject: Re: [lamps] [IAB]  Conflict between RFC8954 and ISO 14533-4
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 13:21:00 -0000

--Apple-Mail-A50AD5CB-5CC8-4146-A45F-E48686A4AA0D
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Russ,

Thanks for noting this. Do we know if this concern was already raised (infor=
mally) with ISO?=20

If we don=E2=80=99t have people who are participating also in ISO and can ea=
sily start the discussion directly, sending a LS seems to be appropriate tha=
t reflects the concept of the lamps group. In this case you/the chairs shoul=
d get in touch with your AD and maybe some of the key participants for this d=
iscussion and draft some text for discussion in the group. The IAB doesn=E2=80=
=99t necessarily need to be involved to send out the LS but we are happy to h=
elp or serve as the official sender if that=E2=80=99s most appropriate in th=
e ISO context.

Mirja


> Am 23.12.2020 um 17:21 schrieb Russ Housley <housley@vigilsec.com>:
>=20
> =EF=BB=BF
> Marian =C4=8Eurkovi=C4=8D <md@bts.sk> brought it to the attention of the L=
AMPS WG.  That was a message out of the blue from my perspective.
>=20
> Russ
>=20
>=20
>=20
>> On Dec 23, 2020, at 11:09 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>=
 wrote:
>>=20
>> Signed PGP part
>>=20
>> Hi Russ,
>>=20
>>> On 23/12/2020 15:41, Russ Housley wrote:
>>> Dear  IAB:
>>> The IETF does not have a liaison relationship with the ISO TC that
>>> produced ISO 14533-4:2019.  It would be a good think to tell that
>>> group that we disagree with the approach that was taken.  What does
>>> the IAB suggest?
>>=20
>> I've not followed this discussion, nor am I at all familiar
>> with that ISO spec, so I'd have to get up to speed before I'd
>> have an informed opinion.
>>=20
>> Does anyone know someone involved with that ISO group/spec?
>> If so, I'd say trying to see if it can be sorted out at that
>> level would be good (if it's not happened already).
>>=20
>> If there's no good contact available then yeah I guess the
>> IAB might try find a way to send a message to ISO. First up
>> though might be for lamps to craft the message to be sent
>> (including enough background that IAB and ISO folks will get
>> the point). I'd be happy to bring such a message to the IAB
>> and ask that we figure out how to get it sent to the right
>> place/people.
>>=20
>> Cheers,
>> S.
>>=20
>> PS: The above is clearly just me speaking, and isn't the
>> consensus of the IAB:-)
>>=20
>>> Russ
>>>> On Dec 23, 2020, at 2:40 AM, Tomas Gustavsson
>>>> <tomas.gustavsson@primekey.com> wrote:
>>>> Hi,
>>>> I'd like to give my view on this.
>>>> I support not changing anything in RFC8954.
>>>> I recently started using the term "tweaking standards" for when you
>>>> take an existing field in a standard and use it for other purposes
>>>> than the one stated in the standard, just because it is technically
>>>> possible and not explicitly forbidden in the standard. This has
>>>> been done many times before, and many times it leads to
>>>> interoperability issues, severe spending of time, money and
>>>> resources, and in severe cases even downtime. Tweaking standards is
>>>> a short term short-cut, ignoring long term costs.
>>>> ISO 14533 clearly tweaked RFC6960 section 4.4.1.
>>>> Many internet scale OCSP responders today do not include Nonce in
>>>> the response. Regardless if the client sends it. This is for
>>>> caching reasons, and is for both GET and POST requests.
>>>> Using nonce as MessageImprint is non-interoperable with RFC6960 and
>>>> with the real world.
>>>> I'd like to say it again: ISO 14533 is non-interoperable with how
>>>> OCSP is deployed on the internet today.
>>>> It is a disaster waiting to happen. The reason it hasn't happened
>>>> yet is likely due to ISO 14533 not being widely used. Let's fix it
>>>> before it falls apart. The solution is not to force RFC6960
>>>> compliant OCSP responders into submission to ISO 14533, but to fix
>>>> ISO 14533. ISO 14533 should recognize that the suggested solution
>>>> is non-compliant, causing interoperability issues, and go back and
>>>> create an extension. Yes, it's a little more work, and may result
>>>> in a new RFC, or a replacement of RFC6960 (but the extension can be
>>>> private to ISO 14533 to start with), but it's the right thing to do
>>>> imho.
>>>> There is already an extension, a bit similar to this, specified in
>>>> the German Common PKI. https://de.wikipedia.org/wiki/Common_PKI It's ca=
lled CertHash and can be copied. The specification isn't available any longe=
r, but I have an off-line copy that I share
>>>> here: https://app.box.com/s/lk1g4a3h75icirnu6xqrqhee8h5kmv54
>>>> It's a SingleResponse extension, section 3.1.2:
>>>> id-commonpki-at-certHash OBJECT IDENTIFIER ::=3D=3D {1 3 36 8 3 13}
>>>> CertHash ::=3D SEQUENCE { hashAlgorithm AlgorithmIdentifier, // The
>>>> identifier of the algorithm // that has been used the for hash //value b=
elow.
>>>> certificateHash OCTET STRING // A hash over the DER-encoding of
>>>> the // entire PKC or AC (i.e. NOT a hash // over tbsCertificate). }
>>>> There are OCSP responders out there supporting the old CertHash
>>>> extension.
>>>> Not saying to use it "as is", it has another purpose, but very
>>>> very similar. Just put a new OID and rename it to
>>>> MessageImprint...
>>>> Best regards, Tomas
>>>>> On 2020-12-21 17:36, Marian =C4=8Eurkovi=C4=8D wrote:
>>>>> *On Sat, 19 Dec 2020 13:12:17 -0800, Mohit Sahni wrote*
>>>>>> =46rom OCSP point of view the MessageImprint is not a random
>>>>>> value but
>>>>> it is a deterministic value generated for a given input by a
>>>>> collision resistant one way hash function.
>>>>> This input, however, consists of multiple parts: some of them
>>>>> being random, some of them being unknown even to document signer
>>>>> (private key). In any case, an attacker is not able to guess this
>>>>> value so it serves against reply attack very well.
>>>>>> One more reason I see for not changing the Nonce extension
>>>>>> length is
>>>>> that the length of MessageImprint is not fixed but varies based
>>>>> on the underlying hash algorithm.  Since RFC3161 does not provide
>>>>> a fixed list of Hash functions, let's say we change the size to
>>>>> Nonce extension to 64 bytes, what if in the future there is a new
>>>>> hash algorithm or some proprietary hash function that requires
>>>>> size to be 128 bytes or 256 bytes or may be 100 GigaBytes, are we
>>>>> going to increase the size of the Nonce extension again?  How can
>>>>> we set an upper limit on Nonce which also serves the regular
>>>>> Nonce use case of just avoiding the replay attacks ?
>>>>> I proposed 2 values: 96 bytes if we want to accomodate 512-bit
>>>>> hashes, or 160 bytes, if we want to accomodate (future) 1024-bit
>>>>> hashes. Any hashing algorithm is designed to yield a relatively
>>>>> small result, so we're certainly not talking about GigaBytes
>>>>> here...
>>>>>> In my opinion, ISO 14533 took advantage of the security
>>>>>> vulnerability
>>>>> that existed in RFC6960 and tried using Nonce extension in a way
>>>>> it was not intended to be used as i.e. using an ASN.1 SEQUENCE
>>>>> where the standard requires use of OCTET STRING.
>>>>> OCTET STRING means arbitrary sequence of bytes, which OCSP
>>>>> responder shouldn't interpret in any way - just echo them back in
>>>>> its response. It's completely irrelevant, what's encoded inside -
>>>>> after all, a random number could also start with 0x30 which
>>>>> corresponds to SEQUENCE.
>>>>>> We should come up with a new extension for associating the
>>>>>> OCSP
>>>>> response with the context where OCSP is being used for long term valid=
ation. That is the right thing to do.
>>>>> And what will be the advantage of having yet another extension
>>>>> doing the same thing? Both use cases require nothing else from
>>>>> OCSP responder than to echo back exactly the same bytes it
>>>>> received in request. Do you propose to have 2 extensions, one of
>>>>> them being able to only echo 32 bytes and another being able to
>>>>> echo 96? or 160? or unlimited bytes? Isn't it much more
>>>>> straightforward to have only one "echoing" extension being able
>>>>> to echo as many bytes as needed for both use cases?
>>>>> On the other hand, the disadvantages are significant - I
>>>>> mentioned some of them in my previous email. Also please keep in
>>>>> mind, that RFC 8954 (if applied by OCSP responder or by some
>>>>> firewall doing deep packet inspection) will immediately break
>>>>> digital signing - since it says:
>>>>> A server *MUST* reject any OCSP request that has a nonce in the
>>>>> Nonce extension with a length of either 0 octets or more than 32
>>>>> octets with the malformedRequest OCSPResponseStatus
>>>>> Last but not least, introducing another extension is more complex
>>>>> than you assume - it will require modification of (at least)
>>>>> RFC6960, RFC5019, ISO 14533-4. When will that solution be
>>>>> available and what to do until then?
>>>>> With kind regards, MD
>>>>> _______________________________________________ Spasm mailing
>>>>> list Spasm@ietf.org https://www.ietf.org/mailman/listinfo/spasm
>>>> _______________________________________________ Spasm mailing list Spas=
m@ietf.org https://www.ietf.org/mailman/listinfo/spasm
>>> _______________________________________________ Spasm mailing list Spasm=
@ietf.org https://www.ietf.org/mailman/listinfo/spasm
>> <OpenPGP_0x5AB2FAF17B172BEA.asc>
>>=20
>>=20
>=20

--Apple-Mail-A50AD5CB-5CC8-4146-A45F-E48686A4AA0D
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr">Hi Russ,</div><div dir=3D"=
ltr"><br></div><div dir=3D"ltr">Thanks for noting this. Do we know if this c=
oncern was already raised (informally) with ISO?&nbsp;</div><div dir=3D"ltr"=
><br></div><div dir=3D"ltr">If we don=E2=80=99t have people who are particip=
ating also in ISO and can easily start the discussion directly, sending a LS=
 seems to be appropriate that reflects the concept of the lamps group. In th=
is case you/the chairs should get in touch with your AD and maybe some of th=
e key participants for this discussion and draft some text for discussion in=
 the group. The IAB doesn=E2=80=99t necessarily need to be involved to send o=
ut the LS but we are happy to help or serve as the official sender if that=E2=
=80=99s most appropriate in the ISO context.</div><div dir=3D"ltr"><br></div=
><div dir=3D"ltr">Mirja</div><div dir=3D"ltr"><br></div><div dir=3D"ltr"><br=
><blockquote type=3D"cite">Am 23.12.2020 um 17:21 schrieb Russ Housley &lt;h=
ousley@vigilsec.com&gt;:<br><br></blockquote></div><blockquote type=3D"cite"=
><div dir=3D"ltr">=EF=BB=BF<meta http-equiv=3D"Content-Type" content=3D"text=
/html; charset=3Dutf-8"><p style=3D"margin: 0px 0px 2px; font-stretch: norma=
l; font-size: 14px; line-height: normal; font-family: &quot;Helvetica Neue&q=
uot;; color: rgba(0, 0, 0, 0.85098);" class=3D"">Marian =C4=8Eurkovi=C4=8D &=
lt;<a href=3D"mailto:md@bts.sk" class=3D"">md@bts.sk</a>&gt; brought it to t=
he attention of the LAMPS WG. &nbsp;That was a message out of the blue from m=
y perspective.</p><p style=3D"margin: 0px 0px 2px; font-stretch: normal; fon=
t-size: 14px; line-height: normal; font-family: &quot;Helvetica Neue&quot;; c=
olor: rgba(0, 0, 0, 0.85098);" class=3D""><br class=3D""></p><p style=3D"mar=
gin: 0px 0px 2px; font-stretch: normal; font-size: 14px; line-height: normal=
; font-family: &quot;Helvetica Neue&quot;; color: rgba(0, 0, 0, 0.85098);" c=
lass=3D"">Russ</p><div class=3D""><br class=3D""></div><div class=3D""><br c=
lass=3D""></div><div><br class=3D""><blockquote type=3D"cite" class=3D""><di=
v class=3D"">On Dec 23, 2020, at 11:09 AM, Stephen Farrell &lt;<a href=3D"ma=
ilto:stephen.farrell@cs.tcd.ie" class=3D"">stephen.farrell@cs.tcd.ie</a>&gt;=
 wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div cl=
ass=3D""><div class=3D"protected-part"><div class=3D"protected-title">Signed=
 PGP part</div><div class=3D"protected-content"><br class=3D"">Hi Russ,<br c=
lass=3D""><br class=3D"">On 23/12/2020 15:41, Russ Housley wrote:<br class=3D=
""><blockquote type=3D"cite" class=3D"">Dear &nbsp;IAB:<br class=3D"">The IE=
TF does not have a liaison relationship with the ISO TC that<br class=3D"">p=
roduced ISO 14533-4:2019. &nbsp;It would be a good think to tell that<br cla=
ss=3D"">group that we disagree with the approach that was taken. &nbsp;What d=
oes<br class=3D"">the IAB suggest?<br class=3D""></blockquote><br class=3D""=
>I've not followed this discussion, nor am I at all familiar<br class=3D"">w=
ith that ISO spec, so I'd have to get up to speed before I'd<br class=3D"">h=
ave an informed opinion.<br class=3D""><br class=3D"">Does anyone know someo=
ne involved with that ISO group/spec?<br class=3D"">If so, I'd say trying to=
 see if it can be sorted out at that<br class=3D"">level would be good (if i=
t's not happened already).<br class=3D""><br class=3D"">If there's no good c=
ontact available then yeah I guess the<br class=3D"">IAB might try find a wa=
y to send a message to ISO. First up<br class=3D"">though might be for lamps=
 to craft the message to be sent<br class=3D"">(including enough background t=
hat IAB and ISO folks will get<br class=3D"">the point). I'd be happy to bri=
ng such a message to the IAB<br class=3D"">and ask that we figure out how to=
 get it sent to the right<br class=3D"">place/people.<br class=3D""><br clas=
s=3D"">Cheers,<br class=3D"">S.<br class=3D""><br class=3D"">PS: The above i=
s clearly just me speaking, and isn't the<br class=3D"">consensus of the IAB=
:-)<br class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">Russ<b=
r class=3D""><blockquote type=3D"cite" class=3D"">On Dec 23, 2020, at 2:40 A=
M, Tomas Gustavsson<br class=3D"">&lt;<a href=3D"mailto:tomas.gustavsson@pri=
mekey.com" class=3D"">tomas.gustavsson@primekey.com</a>&gt; wrote:<br class=3D=
"">Hi,<br class=3D"">I'd like to give my view on this.<br class=3D"">I suppo=
rt not changing anything in RFC8954.<br class=3D"">I recently started using t=
he term "tweaking standards" for when you<br class=3D"">take an existing fie=
ld in a standard and use it for other purposes<br class=3D"">than the one st=
ated in the standard, just because it is technically<br class=3D"">possible a=
nd not explicitly forbidden in the standard. This has<br class=3D"">been don=
e many times before, and many times it leads to<br class=3D"">interoperabili=
ty issues, severe spending of time, money and<br class=3D"">resources, and i=
n severe cases even downtime. Tweaking standards is<br class=3D"">a short te=
rm short-cut, ignoring long term costs.<br class=3D"">ISO 14533 clearly twea=
ked RFC6960 section 4.4.1.<br class=3D"">Many internet scale OCSP responders=
 today do not include Nonce in<br class=3D"">the response. Regardless if the=
 client sends it. This is for<br class=3D"">caching reasons, and is for both=
 GET and POST requests.<br class=3D"">Using nonce as MessageImprint is non-i=
nteroperable with RFC6960 and<br class=3D"">with the real world.<br class=3D=
"">I'd like to say it again: ISO 14533 is non-interoperable with how<br clas=
s=3D"">OCSP is deployed on the internet today.<br class=3D"">It is a disaste=
r waiting to happen. The reason it hasn't happened<br class=3D"">yet is like=
ly due to ISO 14533 not being widely used. Let's fix it<br class=3D"">before=
 it falls apart. The solution is not to force RFC6960<br class=3D"">complian=
t OCSP responders into submission to ISO 14533, but to fix<br class=3D"">ISO=
 14533. ISO 14533 should recognize that the suggested solution<br class=3D""=
>is non-compliant, causing interoperability issues, and go back and<br class=
=3D"">create an extension. Yes, it's a little more work, and may result<br c=
lass=3D"">in a new RFC, or a replacement of RFC6960 (but the extension can b=
e<br class=3D"">private to ISO 14533 to start with), but it's the right thin=
g to do<br class=3D"">imho.<br class=3D"">There is already an extension, a b=
it similar to this, specified in<br class=3D"">the German Common PKI. <a hre=
f=3D"https://de.wikipedia.org/wiki/Common_PKI" class=3D"">https://de.wikiped=
ia.org/wiki/Common_PKI</a> It's called CertHash and can be copied. The speci=
fication isn't available any longer, but I have an off-line copy that I shar=
e<br class=3D"">here: <a href=3D"https://app.box.com/s/lk1g4a3h75icirnu6xqrq=
hee8h5kmv54" class=3D"">https://app.box.com/s/lk1g4a3h75icirnu6xqrqhee8h5kmv=
54</a><br class=3D"">It's a SingleResponse extension, section 3.1.2:<br clas=
s=3D"">id-commonpki-at-certHash OBJECT IDENTIFIER ::=3D=3D {1 3 36 8 3 13}<b=
r class=3D"">CertHash ::=3D SEQUENCE { hashAlgorithm AlgorithmIdentifier, //=
 The<br class=3D"">identifier of the algorithm // that has been used the for=
 hash //value below.<br class=3D"">certificateHash OCTET STRING // A hash ov=
er the DER-encoding of<br class=3D"">the // entire PKC or AC (i.e. NOT a has=
h // over tbsCertificate). }<br class=3D"">There are OCSP responders out the=
re supporting the old CertHash<br class=3D"">extension.<br class=3D"">Not sa=
ying to use it "as is", it has another purpose, but very<br class=3D"">very s=
imilar. Just put a new OID and rename it to<br class=3D"">MessageImprint...<=
br class=3D"">Best regards, Tomas<br class=3D"">On 2020-12-21 17:36, Marian =C4=
=8Eurkovi=C4=8D wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">*O=
n Sat, 19 Dec 2020 13:12:17 -0800, Mohit Sahni wrote*<br class=3D""><blockqu=
ote type=3D"cite" class=3D"">=46rom OCSP point of view the MessageImprint is=
 not a random<br class=3D"">value but<br class=3D""></blockquote>it is a det=
erministic value generated for a given input by a<br class=3D"">collision re=
sistant one way hash function.<br class=3D"">This input, however, consists o=
f multiple parts: some of them<br class=3D"">being random, some of them bein=
g unknown even to document signer<br class=3D"">(private key). In any case, a=
n attacker is not able to guess this<br class=3D"">value so it serves agains=
t reply attack very well.<br class=3D""><blockquote type=3D"cite" class=3D""=
>One more reason I see for not changing the Nonce extension<br class=3D"">le=
ngth is<br class=3D""></blockquote>that the length of MessageImprint is not f=
ixed but varies based<br class=3D"">on the underlying hash algorithm. &nbsp;=
Since RFC3161 does not provide<br class=3D"">a fixed list of Hash functions,=
 let's say we change the size to<br class=3D"">Nonce extension to 64 bytes, w=
hat if in the future there is a new<br class=3D"">hash algorithm or some pro=
prietary hash function that requires<br class=3D"">size to be 128 bytes or 2=
56 bytes or may be 100 GigaBytes, are we<br class=3D"">going to increase the=
 size of the Nonce extension again? &nbsp;How can<br class=3D"">we set an up=
per limit on Nonce which also serves the regular<br class=3D"">Nonce use cas=
e of just avoiding the replay attacks ?<br class=3D"">I proposed 2 values: 9=
6 bytes if we want to accomodate 512-bit<br class=3D"">hashes, or 160 bytes,=
 if we want to accomodate (future) 1024-bit<br class=3D"">hashes. Any hashin=
g algorithm is designed to yield a relatively<br class=3D"">small result, so=
 we're certainly not talking about GigaBytes<br class=3D"">here...<br class=3D=
""><blockquote type=3D"cite" class=3D"">In my opinion, ISO 14533 took advant=
age of the security<br class=3D"">vulnerability<br class=3D""></blockquote>t=
hat existed in RFC6960 and tried using Nonce extension in a way<br class=3D"=
">it was not intended to be used as i.e. using an ASN.1 SEQUENCE<br class=3D=
"">where the standard requires use of OCTET STRING.<br class=3D"">OCTET STRI=
NG means arbitrary sequence of bytes, which OCSP<br class=3D"">responder sho=
uldn't interpret in any way - just echo them back in<br class=3D"">its respo=
nse. It's completely irrelevant, what's encoded inside -<br class=3D"">after=
 all, a random number could also start with 0x30 which<br class=3D"">corresp=
onds to SEQUENCE.<br class=3D""><blockquote type=3D"cite" class=3D"">We shou=
ld come up with a new extension for associating the<br class=3D"">OCSP<br cl=
ass=3D""></blockquote>response with the context where OCSP is being used for=
 long term validation. That is the right thing to do.<br class=3D"">And what=
 will be the advantage of having yet another extension<br class=3D"">doing t=
he same thing? Both use cases require nothing else from<br class=3D"">OCSP r=
esponder than to echo back exactly the same bytes it<br class=3D"">received i=
n request. Do you propose to have 2 extensions, one of<br class=3D"">them be=
ing able to only echo 32 bytes and another being able to<br class=3D"">echo 9=
6? or 160? or unlimited bytes? Isn't it much more<br class=3D"">straightforw=
ard to have only one "echoing" extension being able<br class=3D"">to echo as=
 many bytes as needed for both use cases?<br class=3D"">On the other hand, t=
he disadvantages are significant - I<br class=3D"">mentioned some of them in=
 my previous email. Also please keep in<br class=3D"">mind, that RFC 8954 (i=
f applied by OCSP responder or by some<br class=3D"">firewall doing deep pac=
ket inspection) will immediately break<br class=3D"">digital signing - since=
 it says:<br class=3D"">A server *MUST* reject any OCSP request that has a n=
once in the<br class=3D"">Nonce extension with a length of either 0 octets o=
r more than 32<br class=3D"">octets with the malformedRequest OCSPResponseSt=
atus<br class=3D"">Last but not least, introducing another extension is more=
 complex<br class=3D"">than you assume - it will require modification of (at=
 least)<br class=3D"">RFC6960, RFC5019, ISO 14533-4. When will that solution=
 be<br class=3D"">available and what to do until then?<br class=3D"">With ki=
nd regards, MD<br class=3D"">_______________________________________________=
 Spasm mailing<br class=3D"">list <a href=3D"mailto:Spasm@ietf.org" class=3D=
"">Spasm@ietf.org</a> <a href=3D"https://www.ietf.org/mailman/listinfo/spasm=
" class=3D"">https://www.ietf.org/mailman/listinfo/spasm</a><br class=3D""><=
/blockquote>_______________________________________________ Spasm mailing li=
st <a href=3D"mailto:Spasm@ietf.org" class=3D"">Spasm@ietf.org</a> <a href=3D=
"https://www.ietf.org/mailman/listinfo/spasm" class=3D"">https://www.ietf.or=
g/mailman/listinfo/spasm</a><br class=3D""></blockquote>____________________=
___________________________ Spasm mailing list <a href=3D"mailto:Spasm@ietf.=
org" class=3D"">Spasm@ietf.org</a> <a href=3D"https://www.ietf.org/mailman/l=
istinfo/spasm" class=3D"">https://www.ietf.org/mailman/listinfo/spasm</a><br=
 class=3D""></blockquote><span id=3D"cid:BB989B60-8E12-47E3-8F01-892C145CD27=
2@fios-router.home">&lt;OpenPGP_0x5AB2FAF17B172BEA.asc&gt;</span></div></div=
><br class=3D""><iframe class=3D"untrusted-content-test" scrolling=3D"auto" w=
idth=3D"200" height=3D"20" style=3D"border:none;display:block;overflow:auto;=
" data-src=3D"data:text/html;charset=3DUTF-8;base64,PGlmcmFtZS1jb250ZW50Pl9f=
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPEJSPlNwYXNtIG1h=
aWxpbmcgbGlzdDxCUj5TcGFzbUBpZXRmLm9yZzxCUj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWls=
bWFuL2xpc3RpbmZvL3NwYXNtPEJSPjwvaWZyYW1lLWNvbnRlbnQ+" sandbox=3D"allow-scrip=
ts"></iframe></div></div></blockquote></div><br class=3D""></div></blockquot=
e></body></html>=

--Apple-Mail-A50AD5CB-5CC8-4146-A45F-E48686A4AA0D--


From nobody Wed Jan  6 08:02:55 2021
Return-Path: <ms@savignano.net>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5AB3A0DF3 for <spasm@ietfa.amsl.com>; Tue,  5 Jan 2021 05:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvgL_BWeN94o for <spasm@ietfa.amsl.com>; Tue,  5 Jan 2021 05:11:28 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 432383A0DFC for <spasm@ietf.org>; Tue,  5 Jan 2021 05:11:27 -0800 (PST)
Received: from macsilver-2.fritz.box ([62.54.177.99]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1Mq2za-1kB3Dr0DZ4-00n6Kd; Tue, 05 Jan 2021 14:11:25 +0100
From: Metin Savignano <ms@savignano.net>
Message-Id: <8492B594-C1D1-4368-8B1A-6B5B9E5CCE32@savignano.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_0293223D-4BF5-4026-97AB-21710CFB2665"; protocol="application/pkcs7-signature"; micalg=sha-256
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Tue, 5 Jan 2021 14:11:21 +0100
In-Reply-To: <A31D7B58-FC12-4F04-A04A-D6AFB11D1901@sn3rd.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, LAMPS <spasm@ietf.org>
To: Sean Turner <sean@sn3rd.com>
References: <5F4E87EE-4CD1-4A9F-BDE2-82AD8FD6EFB1@savignano.net> <B9F4B837-8065-4D11-8A4C-113C14DD6986@savignano.net> <017ca985-ac25-b318-c259-24b08344bd0e@isode.com> <A31D7B58-FC12-4F04-A04A-D6AFB11D1901@sn3rd.com>
X-Mailer: Apple Mail (2.3445.104.17)
X-Provags-ID: V03:K1:wReW9PP4awo+vce013LHYO7xDa7U1AV3GEqA0U9VC490Kgim9ue q+/VS9iUOm0TI8tAmUxOTelysOVcvlbUjqueIS7wdpTg5tjcsJYwY/5RNH7cc7CT0WA6Oa6 48gt9/vh9uozmnfO2d9QHNQWvTAXXj3e2TgV+2ztJicpZpFJyJM+Q746qJKBiWLl0lOEScX JD4CIjJsDvWUZzzhIdrwQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:G4bBaCKAx3c=:KTnKBeXfBt4PHp1U9DYzeR Hox4SI4fzJp3o2KYORCH8rDOt83/bqwgPDP9ujR2xzYDvTjOAJC5Y4p5S+luQDt93sAn1AHxV jLkxdxojM/gPIkczROuSQOXv44NuWts6+smjYdIS+8nR7Ub3JI+zpofHJ1KU0MJgAdJZ+1ClO 0qdiCwsVmCjSzsvsLsqV7wvUmd2C1k7d2vBccz8uFhHJJK/JFCqyS2zEoc63fuQ4EqnmthdSO JnbeyaRxzQWTcI+M2nInYGryX+w6cTPKCSb1Sqh7Cx4hXmCb43Gqd/Rf4XbQtRsEEe7lno9oQ kIfv2qqhmW+jGV6EY/mGwDARF4+wFINFoptgksEwd73+/VP8MlYsakFNjywIvJkWHWp0/0Xjw Gf3fT5pJxu9UyX7+8+32RDhwnF7HAT4N9WSIuHIrTF9wsOUdsXAwofRXZlqfh
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/g30F73OyTUW5TakFqUtpWSfJssY>
X-Mailman-Approved-At: Wed, 06 Jan 2021 08:02:54 -0800
Subject: Re: [lamps] Possible inconsistencies or ambiguities in RFC 8551
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2021 13:11:31 -0000

--Apple-Mail=_0293223D-4BF5-4026-97AB-21710CFB2665
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_436EBD0D-E57C-4229-8601-E3B5A0C82E93"


--Apple-Mail=_436EBD0D-E57C-4229-8601-E3B5A0C82E93
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi all,

Thank you very much for your replies and insights.

I=E2=80=99d like to comment back as follows:

> The meta point here is that as S/MIME has moved from RC4 to tripleDES =
(RFC 3851 v3.1), from tripleDES to AES-CBC (RFC 5751), and now from =
AES-CBC to AES-GCM (RFC 8751) the logic has been the same:
>=20
>   If you do not know what the receiving side
>   supports send the best you got.

My memory can deceive, but I believe that when 3DES was recommended in =
2004, and AES-CBC in 2010, these ciphers have already been in use for a =
while, didn=E2=80=99t they?

3DES was recommended in RFC 2633, and AES-CBC was included as SHOULD in =
RFC 3851, so these ciphers have been kind of announced before. AES-GCM =
block mode, however, is not announced or even mentioned in earlier =
publications, so comes as a surprise in RFC 8551.

My problem with AES-GCM is that we=E2=80=99ve run a few tests, and the =
mail clients we used were all unable to decrypt AES-GCM encrypted =
emails:
Outlook 2016=20
Apple Mail on macOS 10.14.6=20
Apple Mail on iOS 13.6=20
Thunderbird 68.11.0
Considering the fact that you it=E2=80=99s not normally known what the =
other side supports, the advice to always send the best would now =
effectively disable encrypted communication with most clients for the =
moment being. Definitely something no one wants to explain their users.


> You should also note that there is a big out in s2.7.1 in the last =
paragraph. All of 2.7.1.* is a SHOULD.


That=E2=80=99s correct, but as I understand the definition of SHOULD, it =
is relatively strong and should be ignored only in very specific cases =
for good reasons. However, trying to be compatible with other mail =
clients is by no means a specific scenario but the general scenario.

So all we can do for now is to implement AES-GCM for incoming emails =
only. But we can=E2=80=99t say we follow RFC 8551 without breaking =
compatibility.

=46rom a PRACTICAL (=3D implementation) point of view, this IS a =
problem.

> ORIGINAL (wordy):
> given the presumption is that a client implementing=20
> MAYBE (less wordy):
> given the presumption that a client implementing
> OR (even more wordy):
> given that the presumption is that a client implementing
> OR (even less wordy):
> assuming a client implementing

I can say for myself that these versions are the easiest for me to =
understand:

> MAYBE (less wordy):
> given the presumption that a client implementing

and

> OR (even less wordy):
> assuming a client implementing


The last one is the clearest to me. I=E2=80=99d suggest an edit here.


Take care
Metin




> Am 23.12.2020 um 19:11 schrieb Sean Turner <sean@sn3rd.com>:
>=20
> Hi! Sorry it=E2=80=99s taken me forever to get to this.
>=20
> I just want to be clear that the proposal here is not trying to =
change, what I believe and somebody else should correct me if they think =
otherwise, the consensus decision that GCM is the MUST.
>=20
> The meta point here is that as S/MIME has moved from RC4 to tripleDES =
(RFC 3851 v3.1), from tripleDES to AES-CBC (RFC 5751), and now from =
AES-CBC to AES-GCM (RFC 8751) the logic has been the same:
>=20
>   If you do not know what the receiving side
>   supports send the best you got.
>=20
> There is no negotiation so better to err on the side of caution (for =
human controlled agents) even (s2.7.2) "if there is a possibility that =
the recipient will not be able to process that algorithm."
>=20
> I would not read the paragraphs in question as a cookbook to get the =
most interoperability. If we want that, then we either switch to =
plaintext or we would need to decide on which version to most =
interoperable with. I would hazard a guess that that CBC based on v3.2 =
wouldn=E2=80=99t be the choice but instead tripleDES based on v3.1/v3.0.
>=20
> You should also note that there is a big out in s2.7.1 in the last =
paragraph. All of 2.7.1.* is a SHOULD.
>=20
> WRT the ambiguity between s1.4 and s2.7.1.2, I am not so sure there is =
one as I consider s1.4 to be feel good deployment consideration text =
lacking any requirements. It provides some history for readers unaware =
of it. But, that =E2=80=9Cought=E2=80=9D in s1.4 only applies some of =
the times, e.g., if this is a high security environment maybe do not use =
RC4 as specified in v2.
>=20
> I could go either way on removing the =E2=80=9Cis=E2=80=9D. I think it =
is wordy, but not necessarily wrong. Then again I am no grammar scholar. =
I would certainly not object to an editorial errata if the WG felt it =
necessary. Some options:
>=20
> ORIGINAL (wordy):
> given the presumption is that a client implementing=20
> MAYBE (less wordy):
> given the presumption that a client implementing
> OR (even more wordy):
> given that the presumption is that a client implementing
> OR (even less wordy):
> assuming a client implementing
>=20
> Alexey is right in that what it is trying to say is that if a client =
supports AES it=E2=80=99s like to also support CBC. That is there so =
that implementations do not choose tripleDES, which was the old SHOULD-.
>=20
> spt
>=20
>> On Dec 8, 2020, at 12:48, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:
>>=20
>> Hi Metin,
>>=20
>> I am not an author/editor of RFC 8551, but I will reply with my =
opinions in order to stimulate some discussion of issues that you've =
raised.
>>=20
>> On 07/12/2020 09:06, Metin Savignano wrote:
>>=20
>>> Hi,
>>>=20
>>> referring to my email quoted below of 7th August, may I ask if and =
how I would get a reply? I haven=E2=80=99t seen one,         and I am =
wondering if I would have to look at some other place?
>>>=20
>>> Thanks
>>> Metin
>>>=20
>>>=20
>>>> Anfang der weitergeleiteten Nachricht:
>>>>=20
>>>> Von: Metin Savignano <ms@savignano.net>
>>>> Betreff: Possible inconsistencies or ambiguities in RFC 8551
>>>> Datum: 7. August 2020 um 13:01:53 MESZ
>>>> An: spasm@ietf.org
>>>>=20
>>>> Dear authors,
>>>>=20
>>>> First of all, thank you very much for your work to create a new and =
better version of S/MIME!=20
>>>>=20
>>>> As an author of an S/MIME app, we are working through RFC 8551 to =
determine the changes we have to implement in order to fully comply to =
the S/MIME 4.0 specs.
>>>>=20
>>>> However, I=E2=80=99ve come to a point where I seem unable to =
understand what the RFC actually recommends with regard to the backward =
compatibility. I=E2=80=99ve also discussed this with another software =
developer, but we both weren=E2=80=99t sure how to read it. It would be =
awesome if you could help me with a clarification.
>>>>=20
>>>> In the relevant scenario, the sending agent wants to send encrypted =
email to a recipient with unknown capabilities.
>>>>=20
>>>> With regard to backward compatibility, RFC 8551 states in section =
1.4:
>>>>=20
>>>>   S/MIME version 4.0 agents ought to attempt to have the greatest
>>>>   interoperability possible with agents for prior versions of =
S/MIME.
>>>>=20
>>>>=20
>>>> Although this is a very general statement, I believe it is =
contradictory to the description about how to decide which content =
encryption cipher to use in section 2.7.1.2:
>>>>=20
>>>>   If the following two conditions are met, the sending agent SHOULD =
use
>>>>   AES-256 GCM, as AES-256 GCM is a stronger algorithm and is =
required
>>>>   by S/MIME v4.0:
>>>>=20
>>>>   -  The sending agent has no knowledge of the encryption =
capabilities
>>>>      of the recipient.
>>>>=20
>>>>   -  The sending agent has no knowledge of the version of S/MIME =
used
>>>>      or supported by the recipient.
>>>>=20
>>>> I don=E2=80=99t understand why we should choose AES-256-GCM if we =
don=E2=80=99t know about the recipients capabilities and S/MIME version.
>> I agree with you that text from Sections 1.4 and 2.7.1.2 is =
contradictory.
>>=20
>>>> For example, if the recipient uses an S/MIME 3.2 compliant =
software, as I understand RFC 5751, that software need not know about =
AES-256-GCM. The GCM block mode is not even mentioned in earlier S/MIME =
versions.  As a consequence, doesn=E2=80=99t the selection of =
AES-256-GCM contradict the "attempt to have the greatest =
interoperability possible with agents for prior versions of S/MIME=E2=80=9C=
?
>> Yes, there is contradiction in the RFC as written.
>>=20
>> I think some implementations would value interoperability with =
earlier versions of S/MIME higher than security and others would choose =
the opposite. Text in 2.7.1.2 seems to be written with the latter case =
in mind.
>>=20
>> For new implementations or implementations more concerned with =
security, using more modern crypto algorithms can be a good default.
>>=20
>>>> The common capability in both S/MIME versions would be AES-128-CBC, =
wouldn=E2=80=99t it?
>>>>=20
>>>> Also, I do not really understand the following sentence:
>>>>=20
>>>>   If the sending agent chooses not to use AES-256 GCM in this step,
>>>>   given the presumption is that a client implementing AES-GCM would =
do
>>>>   both AES-256 and AES-128, it SHOULD use AES-128 CBC.
>>>>=20
>>>> It appears to me as if this sentence was grammatically either wrong =
or uses a construct that I don=E2=80=99t understand (I=E2=80=99m not a =
native speaker).
>> You are right, the above seems wrong. I think "is" needs to be =
dropped after "presumption".
>>>> I don=E2=80=99t understand what "given the presumption is that a =
client implementing AES-GCM would do both AES-256 and AES-128=E2=80=9C  =
is meant to tell me in that context. Also, I=E2=80=99m not sure if the =
word =E2=80=9Eclient=E2=80=9C is meant to refer to the sending or =
receiving client. At first, I thought it=E2=80=99s the receiving client, =
but after re-reading a few times, I=E2=80=99m unsure if it=E2=80=99s the =
sending agent, because I don=E2=80=99t understand why I should make =
presumptions about the receiving client implementing AES-GCM when I =
don=E2=80=99t know anything about it.
>> I think the text is trying to say that as the client supports AES, it =
is likely to support AES-128 CBC.
>>>>=20
>>>> I would recommend that this sentence maybe rephrase to make it more =
understandable for non-native speakers.
>>>>=20
>>>> What I would have expected in section 2.7.1.2:
>>>>=20
>>>> To maintain "greatest interoperability possible with agents for =
prior versions of S/MIME=E2=80=9C, the RFC would select AES-128-CBC if =
the recipient=E2=80=99s capabilities and S/MIME version aren=E2=80=99t =
known.
>>>>=20
>>>> Where am I off the track?
>>>>=20
>>>>=20
>>>> Thanks a lot!
>>>>=20
>>>> Metin Savignano
>> Best Regards,
>>=20
>> Alexey
>>=20
>>=20
>>=20
>> _______________________________________________
>> Spasm mailing list
>> Spasm@ietf.org
>> https://www.ietf.org/mailman/listinfo/spasm
>=20


--Apple-Mail=_436EBD0D-E57C-4229-8601-E3B5A0C82E93
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
all,<div class=3D""><br class=3D""></div><div class=3D"">Thank you very =
much for your replies and insights.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I=E2=80=99d like to comment back as =
follows:</div><div class=3D""><br class=3D""></div><div =
class=3D""><blockquote type=3D"cite" class=3D"">The meta point here is =
that as S/MIME has moved from RC4 to tripleDES (RFC 3851 v3.1), from =
tripleDES to AES-CBC (RFC 5751), and now from AES-CBC to AES-GCM (RFC =
8751) the logic has been the same:<br class=3D""><br =
class=3D"">&nbsp;&nbsp;If you do not know what the receiving side<br =
class=3D"">&nbsp;&nbsp;supports send the best you got.</blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">My memory can deceive, =
but I believe that when 3DES was recommended in 2004, and AES-CBC in =
2010, these ciphers have already been in use for a while, didn=E2=80=99t =
they?</div><div class=3D""><br class=3D""></div><div class=3D""><div =
class=3D"">3DES was recommended in RFC 2633, and AES-CBC was included as =
SHOULD in RFC 3851, so these ciphers have been kind of announced before. =
AES-GCM block mode, however, is not announced or even mentioned in =
earlier publications, so comes as a surprise in RFC =
8551.</div></div><div class=3D""><br class=3D""></div><div class=3D"">My =
problem with AES-GCM is that we=E2=80=99ve run a few tests, and the mail =
clients we used were all unable to decrypt AES-GCM encrypted =
emails:</div><div class=3D""><ul class=3D""><li class=3D"">Outlook =
2016&nbsp;</li><li class=3D"">Apple Mail on macOS 10.14.6&nbsp;</li><li =
class=3D"">Apple Mail on iOS 13.6&nbsp;</li><li class=3D"">Thunderbird =
68.11.0</li></ul></div><div class=3D"">Considering the fact that you =
it=E2=80=99s not normally known what the other side supports, the advice =
to always send the best would now effectively disable encrypted =
communication with most clients for the moment being. Definitely =
something no one wants to explain their users.</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D""><blockquote type=3D"cite" class=3D"">You should also note =
that there is a big out in s2.7.1 in the last paragraph. All of 2.7.1.* =
is a SHOULD.<br class=3D""></blockquote></div><div class=3D""><br =
class=3D""></div>That=E2=80=99s correct, but as I understand the =
definition of SHOULD, it is relatively strong and should be ignored only =
in very specific cases for good reasons. However, trying to be =
compatible with other mail clients is by no means a specific scenario =
but the general scenario.</div><div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D"">So all we can do for now is to implement =
AES-GCM for incoming emails only. But we can=E2=80=99t say we follow RFC =
8551 without breaking compatibility.</div><div class=3D""><br =
class=3D""></div><div class=3D"">=46rom a PRACTICAL (=3D implementation) =
point of view, this IS a problem.</div></div><div class=3D""><br =
class=3D""></div><div class=3D""><blockquote type=3D"cite" =
class=3D"">ORIGINAL (wordy):<br class=3D"">given the presumption is that =
a client implementing&nbsp;<br class=3D"">MAYBE (less wordy):<br =
class=3D"">given the presumption that a client implementing<br =
class=3D"">OR (even more wordy):<br class=3D"">given that the =
presumption is that a client implementing<br class=3D"">OR (even less =
wordy):<br class=3D"">assuming a client implementing</blockquote><br =
class=3D""></div><div class=3D"">I can say for myself that these =
versions are the easiest for me to understand:</div><div class=3D""><br =
class=3D""></div><div class=3D""><div><blockquote type=3D"cite" =
class=3D"">MAYBE (less wordy):<br class=3D"">given the presumption that =
a client implementing</blockquote><br =
class=3D""></div><div>and</div><div><br class=3D""></div><div><blockquote =
type=3D"cite" class=3D"">OR (even less wordy):<br class=3D"">assuming a =
client implementing</blockquote></div><div><br class=3D""></div><div>The =
last one is the clearest to me. I=E2=80=99d suggest an edit =
here.</div><div><br class=3D""></div><div><br class=3D""></div><div>Take =
care</div><div>Metin</div><div><br class=3D""></div><div><br =
class=3D""></div><div><br class=3D""></div><div><br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D"">Am 23.12.2020 um 19:11 schrieb =
Sean Turner &lt;<a href=3D"mailto:sean@sn3rd.com" =
class=3D"">sean@sn3rd.com</a>&gt;:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Hi! =
Sorry it=E2=80=99s taken me forever to get to this.<br class=3D""><br =
class=3D"">I just want to be clear that the proposal here is not trying =
to change, what I believe and somebody else should correct me if they =
think otherwise, the consensus decision that GCM is the MUST.<br =
class=3D""><br class=3D"">The meta point here is that as S/MIME has =
moved from RC4 to tripleDES (RFC 3851 v3.1), from tripleDES to AES-CBC =
(RFC 5751), and now from AES-CBC to AES-GCM (RFC 8751) the logic has =
been the same:<br class=3D""><br class=3D""> &nbsp;&nbsp;If you do not =
know what the receiving side<br class=3D""> &nbsp;&nbsp;supports send =
the best you got.<br class=3D""><br class=3D"">There is no negotiation =
so better to err on the side of caution (for human controlled agents) =
even (s2.7.2) "if there is a possibility that the recipient will not be =
able to process that algorithm."<br class=3D""><br class=3D"">I would =
not read the paragraphs in question as a cookbook to get the most =
interoperability. If we want that, then we either switch to plaintext or =
we would need to decide on which version to most interoperable with. I =
would hazard a guess that that CBC based on v3.2 wouldn=E2=80=99t be the =
choice but instead tripleDES based on v3.1/v3.0.<br class=3D""><br =
class=3D"">You should also note that there is a big out in s2.7.1 in the =
last paragraph. All of 2.7.1.* is a SHOULD.<br class=3D""><br =
class=3D"">WRT the ambiguity between s1.4 and s2.7.1.2, I am not so sure =
there is one as I consider s1.4 to be feel good deployment consideration =
text lacking any requirements. It provides some history for readers =
unaware of it. But, that =E2=80=9Cought=E2=80=9D in s1.4 only applies =
some of the times, e.g., if this is a high security environment maybe do =
not use RC4 as specified in v2.<br class=3D""><br class=3D"">I could go =
either way on removing the =E2=80=9Cis=E2=80=9D. I think it is wordy, =
but not necessarily wrong. Then again I am no grammar scholar. I would =
certainly not object to an editorial errata if the WG felt it necessary. =
Some options:<br class=3D""><br class=3D"">ORIGINAL (wordy):<br =
class=3D"">given the presumption is that a client implementing <br =
class=3D"">MAYBE (less wordy):<br class=3D"">given the presumption that =
a client implementing<br class=3D"">OR (even more wordy):<br =
class=3D"">given that the presumption is that a client implementing<br =
class=3D"">OR (even less wordy):<br class=3D"">assuming a client =
implementing<br class=3D""><br class=3D"">Alexey is right in that what =
it is trying to say is that if a client supports AES it=E2=80=99s like =
to also support CBC. That is there so that implementations do not choose =
tripleDES, which was the old SHOULD-.<br class=3D""><br class=3D"">spt<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">On Dec 8, =
2020, at 12:48, Alexey Melnikov &lt;<a =
href=3D"mailto:alexey.melnikov@isode.com" =
class=3D"">alexey.melnikov@isode.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">Hi Metin,<br class=3D""><br class=3D"">I am not an =
author/editor of RFC 8551, but I will reply with my opinions in order to =
stimulate some discussion of issues that you've raised.<br class=3D""><br =
class=3D"">On 07/12/2020 09:06, Metin Savignano wrote:<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">Hi,<br class=3D""><br =
class=3D"">referring to my email quoted below of 7th August, may I ask =
if and how I would get a reply? I haven=E2=80=99t seen one, =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and I am wondering if I =
would have to look at some other place?<br class=3D""><br =
class=3D"">Thanks<br class=3D"">Metin<br class=3D""><br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">Anfang der =
weitergeleiteten Nachricht:<br class=3D""><br class=3D"">Von: Metin =
Savignano &lt;<a href=3D"mailto:ms@savignano.net" =
class=3D"">ms@savignano.net</a>&gt;<br class=3D"">Betreff: Possible =
inconsistencies or ambiguities in RFC 8551<br class=3D"">Datum: 7. =
August 2020 um 13:01:53 MESZ<br class=3D"">An: <a =
href=3D"mailto:spasm@ietf.org" class=3D"">spasm@ietf.org</a><br =
class=3D""><br class=3D"">Dear authors,<br class=3D""><br class=3D"">First=
 of all, thank you very much for your work to create a new and better =
version of S/MIME! <br class=3D""><br class=3D"">As an author of an =
S/MIME app, we are working through RFC 8551 to determine the changes we =
have to implement in order to fully comply to the S/MIME 4.0 specs.<br =
class=3D""><br class=3D"">However, I=E2=80=99ve come to a point where I =
seem unable to understand what the RFC actually recommends with regard =
to the backward compatibility. I=E2=80=99ve also discussed this with =
another software developer, but we both weren=E2=80=99t sure how to read =
it. It would be awesome if you could help me with a clarification.<br =
class=3D""><br class=3D"">In the relevant scenario, the sending agent =
wants to send encrypted email to a recipient with unknown =
capabilities.<br class=3D""><br class=3D"">With regard to backward =
compatibility, RFC 8551 states in section 1.4:<br class=3D""><br =
class=3D""> &nbsp;&nbsp;S/MIME version 4.0 agents ought to attempt to =
have the greatest<br class=3D""> &nbsp;&nbsp;interoperability possible =
with agents for prior versions of S/MIME.<br class=3D""><br class=3D""><br=
 class=3D"">Although this is a very general statement, I believe it is =
contradictory to the description about how to decide which content =
encryption cipher to use in section 2.7.1.2:<br class=3D""><br class=3D"">=
 &nbsp;&nbsp;If the following two conditions are met, the sending agent =
SHOULD use<br class=3D""> &nbsp;&nbsp;AES-256 GCM, as AES-256 GCM is a =
stronger algorithm and is required<br class=3D""> &nbsp;&nbsp;by S/MIME =
v4.0:<br class=3D""><br class=3D""> &nbsp;&nbsp;- &nbsp;The sending =
agent has no knowledge of the encryption capabilities<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;of the recipient.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;- &nbsp;The sending agent has no knowledge of =
the version of S/MIME used<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;or supported by the recipient.<br =
class=3D""><br class=3D"">I don=E2=80=99t understand why we should =
choose AES-256-GCM if we don=E2=80=99t know about the recipients =
capabilities and S/MIME version.<br class=3D""></blockquote></blockquote>I=
 agree with you that text from Sections 1.4 and 2.7.1.2 is =
contradictory.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">For example, if the =
recipient uses an S/MIME 3.2 compliant software, as I understand RFC =
5751, that software need not know about AES-256-GCM. The GCM block mode =
is not even mentioned in earlier S/MIME versions. &nbsp;As a =
consequence, doesn=E2=80=99t the selection of AES-256-GCM contradict the =
"attempt to have the greatest interoperability possible with agents for =
prior versions of S/MIME=E2=80=9C?<br =
class=3D""></blockquote></blockquote>Yes, there is contradiction in the =
RFC as written.<br class=3D""><br class=3D"">I think some =
implementations would value interoperability with earlier versions of =
S/MIME higher than security and others would choose the opposite. Text =
in 2.7.1.2 seems to be written with the latter case in mind.<br =
class=3D""><br class=3D"">For new implementations or implementations =
more concerned with security, using more modern crypto algorithms can be =
a good default.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">The common capability in =
both S/MIME versions would be AES-128-CBC, wouldn=E2=80=99t it?<br =
class=3D""><br class=3D"">Also, I do not really understand the following =
sentence:<br class=3D""><br class=3D""> &nbsp;&nbsp;If the sending agent =
chooses not to use AES-256 GCM in this step,<br class=3D""> =
&nbsp;&nbsp;given the presumption is that a client implementing AES-GCM =
would do<br class=3D""> &nbsp;&nbsp;both AES-256 and AES-128, it SHOULD =
use AES-128 CBC.<br class=3D""><br class=3D"">It appears to me as if =
this sentence was grammatically either wrong or uses a construct that I =
don=E2=80=99t understand (I=E2=80=99m not a native speaker).<br =
class=3D""></blockquote></blockquote>You are right, the above seems =
wrong. I think "is" needs to be dropped after "presumption".<br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D"">I don=E2=80=99t understand what "given the presumption is =
that a client implementing AES-GCM would do both AES-256 and AES-128=E2=80=
=9C &nbsp;is meant to tell me in that context. Also, I=E2=80=99m not =
sure if the word =E2=80=9Eclient=E2=80=9C is meant to refer to the =
sending or receiving client. At first, I thought it=E2=80=99s the =
receiving client, but after re-reading a few times, I=E2=80=99m unsure =
if it=E2=80=99s the sending agent, because I don=E2=80=99t understand =
why I should make presumptions about the receiving client implementing =
AES-GCM when I don=E2=80=99t know anything about it.<br =
class=3D""></blockquote></blockquote>I think the text is trying to say =
that as the client supports AES, it is likely to support AES-128 CBC.<br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">I would recommend that this sentence maybe =
rephrase to make it more understandable for non-native speakers.<br =
class=3D""><br class=3D"">What I would have expected in section =
2.7.1.2:<br class=3D""><br class=3D"">To maintain "greatest =
interoperability possible with agents for prior versions of S/MIME=E2=80=9C=
, the RFC would select AES-128-CBC if the recipient=E2=80=99s =
capabilities and S/MIME version aren=E2=80=99t known.<br class=3D""><br =
class=3D"">Where am I off the track?<br class=3D""><br class=3D""><br =
class=3D"">Thanks a lot!<br class=3D""><br class=3D"">Metin Savignano<br =
class=3D""></blockquote></blockquote>Best Regards,<br class=3D""><br =
class=3D"">Alexey<br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">Spasm mailing list<br class=3D""><a =
href=3D"mailto:Spasm@ietf.org" class=3D"">Spasm@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/spasm<br =
class=3D""></blockquote><br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_436EBD0D-E57C-4229-8601-E3B5A0C82E93--

--Apple-Mail=_0293223D-4BF5-4026-97AB-21710CFB2665
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCBDQw
ggQwMIIDGKADAgECAgEgMA0GCSqGSIb3DQEBCwUAMIG1MRowGAYDVQQDDBFzYXZpZ25hbm8gQ0VS
VC1pMzElMCMGA1UECgwcc2F2aWduYW5vIHNvZnR3YXJlIHNvbHV0aW9uczEdMBsGA1UECwwUQ2Vy
dGlmY2F0aW9uIFNlcnZpY2UxCzAJBgNVBAgMAkJXMQswCQYDVQQGEwJERTEUMBIGA1UEBwwLTHVk
d2lnc2J1cmcxITAfBgkqhkiG9w0BCQEWEmNlcnRAc2F2aWduYW5vLm5ldDAeFw0xOTExMDUyMDI2
MjJaFw0yMjAxMzEyMDI2MjJaMIGSMRgwFgYDVQQDDA9NZXRpbiBTYXZpZ25hbm8xJTAjBgNVBAoM
HHNhdmlnbmFubyBzb2Z0d2FyZSBzb2x1dGlvbnMxCzAJBgNVBAgMAkJXMQswCQYDVQQGEwJERTEU
MBIGA1UEBwwLTHVkd2lnc2J1cmcxHzAdBgkqhkiG9w0BCQEWEG1zQHNhdmlnbmFuby5uZXQwggEi
MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCxnKn6b7wTrY7G4ov3Hdt6Z9Q4p3obZ8WFzXyg
++Vlf7FnPQL9wIYNfpMRexAZK1/y6kiaPhVFArm6/RZicRDv8/89IB8SlITGqXx0/Y+S4jSxre8E
FUXi/BFhbI/F/jMv+YUUgUf/cMpu62F726u0PSUgX+4UQgmV9ksex3UV2KF7juHjuibUqYmHldWt
6lfDaAf5fBBlhL/x8cF6KjPjTC3DUrL1GMga8ZQfNfyPRpwVudgrK40yaTda+eHU8dLjOtrc6K/p
PM/cx90RfL9IrLiyx1dZMPvjNHcxVwPdsTIrqom4DSNX9s4wRf70f/MpHL6aZ7IxuhdQO1bqd3Ah
AgMBAAGjbDBqMA4GA1UdDwEB/wQEAwIFoDAmBgNVHSUEHzAdBggrBgEFBQcDBAYIKwYBBQUHAwIG
BysGAQUCAwQwMAYDVR0RBCkwJ4EQbXNAc2F2aWduYW5vLm5ldIETbWV0aW5Ac2F2aWduYW5vLm5l
dDANBgkqhkiG9w0BAQsFAAOCAQEAnvw8CEHRy3xCSHrcmCh1/b6PlxCURYynWgABvJgd3+0Acw4V
DRgtA7vnozkSu/FHZy2pNv1wOf2F3AWIU9qUxqssZogvIgI1LwKQZ2YO+ymkous4qBWc44Twmhi2
2juBjuxEUPC3+x/ZEmkCz4z95qtHeL+B3EqpcGgDemkTgtT7mv0053mN+vyFOxpxQiSKfMAVwvJe
lTLax2g3MXbT7ycZpHXJ2nnA/ZprqJg5+bFMg9J/Q9Vvc5q3d6qFU+Od7JzKg79gWe8p7S8Dul0b
Bcl0phLIgPHk++lxlGDtizzOt5DZWcVyKKGeMDNPPKtopb9ZQulRKJj20szhznopKzGCA/QwggPw
AgEBMIG7MIG1MRowGAYDVQQDDBFzYXZpZ25hbm8gQ0VSVC1pMzElMCMGA1UECgwcc2F2aWduYW5v
IHNvZnR3YXJlIHNvbHV0aW9uczEdMBsGA1UECwwUQ2VydGlmY2F0aW9uIFNlcnZpY2UxCzAJBgNV
BAgMAkJXMQswCQYDVQQGEwJERTEUMBIGA1UEBwwLTHVkd2lnc2J1cmcxITAfBgkqhkiG9w0BCQEW
EmNlcnRAc2F2aWduYW5vLm5ldAIBIDANBglghkgBZQMEAgEFAKCCAgkwGAYJKoZIhvcNAQkDMQsG
CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMjEwMTA1MTMxMTIxWjAvBgkqhkiG9w0BCQQxIgQg
pni47zyYKGgYZXC2elyUlux9hn3AN6ama0KKuvltIn4wgcwGCSsGAQQBgjcQBDGBvjCBuzCBtTEa
MBgGA1UEAwwRc2F2aWduYW5vIENFUlQtaTMxJTAjBgNVBAoMHHNhdmlnbmFubyBzb2Z0d2FyZSBz
b2x1dGlvbnMxHTAbBgNVBAsMFENlcnRpZmNhdGlvbiBTZXJ2aWNlMQswCQYDVQQIDAJCVzELMAkG
A1UEBhMCREUxFDASBgNVBAcMC0x1ZHdpZ3NidXJnMSEwHwYJKoZIhvcNAQkBFhJjZXJ0QHNhdmln
bmFuby5uZXQCASAwgc4GCyqGSIb3DQEJEAILMYG+oIG7MIG1MRowGAYDVQQDDBFzYXZpZ25hbm8g
Q0VSVC1pMzElMCMGA1UECgwcc2F2aWduYW5vIHNvZnR3YXJlIHNvbHV0aW9uczEdMBsGA1UECwwU
Q2VydGlmY2F0aW9uIFNlcnZpY2UxCzAJBgNVBAgMAkJXMQswCQYDVQQGEwJERTEUMBIGA1UEBwwL
THVkd2lnc2J1cmcxITAfBgkqhkiG9w0BCQEWEmNlcnRAc2F2aWduYW5vLm5ldAIBIDANBgkqhkiG
9w0BAQEFAASCAQCQ7tfYJbkObgu5gqx3ssr4UjECDRxfIUoYYQ3MFMwNhhP1ditZGAOHBZkXEKH5
g4HAFjnEtP4eR8ijDbESa6yMS4fJBkUB7txF4CBccb//DibkrfjHaVG+VQSynMrVGghCp4B7D55r
/i8BiFwANu4ZcACyoXV+ANU1FegVpPBrO2WwwvAsdAbkz/mMd6Qaa+N4kp8Rvs19781ib/qxof2L
VoTceqNH/AkoiSM8V5fdzyNCB0nD1q4EmAhJfTsge4bWa+CR6upQHl6oAd+jRsaVW5hXNAmn8wIB
XYwsw4HVmPlukpmWSlbVaDqSA7niCdhr1krYRMlpjDTdI87JQcSDAAAAAAAA
--Apple-Mail=_0293223D-4BF5-4026-97AB-21710CFB2665--


From nobody Wed Jan  6 08:11:17 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A25D3A0F47 for <spasm@ietfa.amsl.com>; Wed,  6 Jan 2021 08:11:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DyXokvbGAlbS for <spasm@ietfa.amsl.com>; Wed,  6 Jan 2021 08:11:10 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5F113A11D8 for <spasm@ietf.org>; Wed,  6 Jan 2021 08:10:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 51D7E300BD1 for <spasm@ietf.org>; Wed,  6 Jan 2021 11:10:38 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EZkwrG1raO4B for <spasm@ietf.org>; Wed,  6 Jan 2021 11:10:31 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 1B452300A48; Wed,  6 Jan 2021 11:10:31 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <EC4D0AF0-5558-440D-810C-ADD56BDFC535@vigilsec.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_DA8E83F1-0116-4055-AAF3-68E641555182"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Wed, 6 Jan 2021 11:10:32 -0500
In-Reply-To: <8492B594-C1D1-4368-8B1A-6B5B9E5CCE32@savignano.net>
Cc: Sean Turner <sean@sn3rd.com>, LAMPS <spasm@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>
To: Metin Savignano <ms@savignano.net>
References: <5F4E87EE-4CD1-4A9F-BDE2-82AD8FD6EFB1@savignano.net> <B9F4B837-8065-4D11-8A4C-113C14DD6986@savignano.net> <017ca985-ac25-b318-c259-24b08344bd0e@isode.com> <A31D7B58-FC12-4F04-A04A-D6AFB11D1901@sn3rd.com> <8492B594-C1D1-4368-8B1A-6B5B9E5CCE32@savignano.net>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/wxI6XQ-CYUNmDQeHS9FXdj1PW88>
Subject: Re: [lamps] Possible inconsistencies or ambiguities in RFC 8551
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 16:11:15 -0000

--Apple-Mail=_DA8E83F1-0116-4055-AAF3-68E641555182
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_603E0545-9199-469A-97E1-5F141363B7DF"


--Apple-Mail=_603E0545-9199-469A-97E1-5F141363B7DF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The IETF is moving toward AEAD algorithms, and it will take a while for =
the products to add this capabaility.  The AES-CBC is retained as a =
SHOULD requirement for transition.

Russ


> On Jan 5, 2021, at 8:11 AM, Metin Savignano <ms@savignano.net> wrote:
>=20
> Hi all,
>=20
> Thank you very much for your replies and insights.
>=20
> I=E2=80=99d like to comment back as follows:
>=20
>> The meta point here is that as S/MIME has moved from RC4 to tripleDES =
(RFC 3851 v3.1), from tripleDES to AES-CBC (RFC 5751), and now from =
AES-CBC to AES-GCM (RFC 8751) the logic has been the same:
>>=20
>>   If you do not know what the receiving side
>>   supports send the best you got.
>=20
> My memory can deceive, but I believe that when 3DES was recommended in =
2004, and AES-CBC in 2010, these ciphers have already been in use for a =
while, didn=E2=80=99t they?
>=20
> 3DES was recommended in RFC 2633, and AES-CBC was included as SHOULD =
in RFC 3851, so these ciphers have been kind of announced before. =
AES-GCM block mode, however, is not announced or even mentioned in =
earlier publications, so comes as a surprise in RFC 8551.
>=20
> My problem with AES-GCM is that we=E2=80=99ve run a few tests, and the =
mail clients we used were all unable to decrypt AES-GCM encrypted =
emails:
> Outlook 2016
> Apple Mail on macOS 10.14.6
> Apple Mail on iOS 13.6
> Thunderbird 68.11.0
> Considering the fact that you it=E2=80=99s not normally known what the =
other side supports, the advice to always send the best would now =
effectively disable encrypted communication with most clients for the =
moment being. Definitely something no one wants to explain their users.
>=20
>=20
>> You should also note that there is a big out in s2.7.1 in the last =
paragraph. All of 2.7.1.* is a SHOULD.
>=20
>=20
> That=E2=80=99s correct, but as I understand the definition of SHOULD, =
it is relatively strong and should be ignored only in very specific =
cases for good reasons. However, trying to be compatible with other mail =
clients is by no means a specific scenario but the general scenario.
>=20
> So all we can do for now is to implement AES-GCM for incoming emails =
only. But we can=E2=80=99t say we follow RFC 8551 without breaking =
compatibility.
>=20
> =46rom a PRACTICAL (=3D implementation) point of view, this IS a =
problem.
>=20
>> ORIGINAL (wordy):
>> given the presumption is that a client implementing
>> MAYBE (less wordy):
>> given the presumption that a client implementing
>> OR (even more wordy):
>> given that the presumption is that a client implementing
>> OR (even less wordy):
>> assuming a client implementing
>=20
> I can say for myself that these versions are the easiest for me to =
understand:
>=20
>> MAYBE (less wordy):
>> given the presumption that a client implementing
>=20
> and
>=20
>> OR (even less wordy):
>> assuming a client implementing
>=20
>=20
> The last one is the clearest to me. I=E2=80=99d suggest an edit here.
>=20
>=20
> Take care
> Metin
>=20
>=20
>=20
>=20
>> Am 23.12.2020 um 19:11 schrieb Sean Turner <sean@sn3rd.com =
<mailto:sean@sn3rd.com>>:
>>=20
>> Hi! Sorry it=E2=80=99s taken me forever to get to this.
>>=20
>> I just want to be clear that the proposal here is not trying to =
change, what I believe and somebody else should correct me if they think =
otherwise, the consensus decision that GCM is the MUST.
>>=20
>> The meta point here is that as S/MIME has moved from RC4 to tripleDES =
(RFC 3851 v3.1), from tripleDES to AES-CBC (RFC 5751), and now from =
AES-CBC to AES-GCM (RFC 8751) the logic has been the same:
>>=20
>>   If you do not know what the receiving side
>>   supports send the best you got.
>>=20
>> There is no negotiation so better to err on the side of caution (for =
human controlled agents) even (s2.7.2) "if there is a possibility that =
the recipient will not be able to process that algorithm."
>>=20
>> I would not read the paragraphs in question as a cookbook to get the =
most interoperability. If we want that, then we either switch to =
plaintext or we would need to decide on which version to most =
interoperable with. I would hazard a guess that that CBC based on v3.2 =
wouldn=E2=80=99t be the choice but instead tripleDES based on v3.1/v3.0.
>>=20
>> You should also note that there is a big out in s2.7.1 in the last =
paragraph. All of 2.7.1.* is a SHOULD.
>>=20
>> WRT the ambiguity between s1.4 and s2.7.1.2, I am not so sure there =
is one as I consider s1.4 to be feel good deployment consideration text =
lacking any requirements. It provides some history for readers unaware =
of it. But, that =E2=80=9Cought=E2=80=9D in s1.4 only applies some of =
the times, e.g., if this is a high security environment maybe do not use =
RC4 as specified in v2.
>>=20
>> I could go either way on removing the =E2=80=9Cis=E2=80=9D. I think =
it is wordy, but not necessarily wrong. Then again I am no grammar =
scholar. I would certainly not object to an editorial errata if the WG =
felt it necessary. Some options:
>>=20
>> ORIGINAL (wordy):
>> given the presumption is that a client implementing
>> MAYBE (less wordy):
>> given the presumption that a client implementing
>> OR (even more wordy):
>> given that the presumption is that a client implementing
>> OR (even less wordy):
>> assuming a client implementing
>>=20
>> Alexey is right in that what it is trying to say is that if a client =
supports AES it=E2=80=99s like to also support CBC. That is there so =
that implementations do not choose tripleDES, which was the old SHOULD-.
>>=20
>> spt
>>=20
>>> On Dec 8, 2020, at 12:48, Alexey Melnikov <alexey.melnikov@isode.com =
<mailto:alexey.melnikov@isode.com>> wrote:
>>>=20
>>> Hi Metin,
>>>=20
>>> I am not an author/editor of RFC 8551, but I will reply with my =
opinions in order to stimulate some discussion of issues that you've =
raised.
>>>=20
>>> On 07/12/2020 09:06, Metin Savignano wrote:
>>>=20
>>>> Hi,
>>>>=20
>>>> referring to my email quoted below of 7th August, may I ask if and =
how I would get a reply? I haven=E2=80=99t seen one,         and I am =
wondering if I would have to look at some other place?
>>>>=20
>>>> Thanks
>>>> Metin
>>>>=20
>>>>=20
>>>>> Anfang der weitergeleiteten Nachricht:
>>>>>=20
>>>>> Von: Metin Savignano <ms@savignano.net <mailto:ms@savignano.net>>
>>>>> Betreff: Possible inconsistencies or ambiguities in RFC 8551
>>>>> Datum: 7. August 2020 um 13:01:53 MESZ
>>>>> An: spasm@ietf.org <mailto:spasm@ietf.org>
>>>>>=20
>>>>> Dear authors,
>>>>>=20
>>>>> First of all, thank you very much for your work to create a new =
and better version of S/MIME!
>>>>>=20
>>>>> As an author of an S/MIME app, we are working through RFC 8551 to =
determine the changes we have to implement in order to fully comply to =
the S/MIME 4.0 specs.
>>>>>=20
>>>>> However, I=E2=80=99ve come to a point where I seem unable to =
understand what the RFC actually recommends with regard to the backward =
compatibility. I=E2=80=99ve also discussed this with another software =
developer, but we both weren=E2=80=99t sure how to read it. It would be =
awesome if you could help me with a clarification.
>>>>>=20
>>>>> In the relevant scenario, the sending agent wants to send =
encrypted email to a recipient with unknown capabilities.
>>>>>=20
>>>>> With regard to backward compatibility, RFC 8551 states in section =
1.4:
>>>>>=20
>>>>>   S/MIME version 4.0 agents ought to attempt to have the greatest
>>>>>   interoperability possible with agents for prior versions of =
S/MIME.
>>>>>=20
>>>>>=20
>>>>> Although this is a very general statement, I believe it is =
contradictory to the description about how to decide which content =
encryption cipher to use in section 2.7.1.2:
>>>>>=20
>>>>>   If the following two conditions are met, the sending agent =
SHOULD use
>>>>>   AES-256 GCM, as AES-256 GCM is a stronger algorithm and is =
required
>>>>>   by S/MIME v4.0:
>>>>>=20
>>>>>   -  The sending agent has no knowledge of the encryption =
capabilities
>>>>>      of the recipient.
>>>>>=20
>>>>>   -  The sending agent has no knowledge of the version of S/MIME =
used
>>>>>      or supported by the recipient.
>>>>>=20
>>>>> I don=E2=80=99t understand why we should choose AES-256-GCM if we =
don=E2=80=99t know about the recipients capabilities and S/MIME version.
>>> I agree with you that text from Sections 1.4 and 2.7.1.2 is =
contradictory.
>>>=20
>>>>> For example, if the recipient uses an S/MIME 3.2 compliant =
software, as I understand RFC 5751, that software need not know about =
AES-256-GCM. The GCM block mode is not even mentioned in earlier S/MIME =
versions.  As a consequence, doesn=E2=80=99t the selection of =
AES-256-GCM contradict the "attempt to have the greatest =
interoperability possible with agents for prior versions of S/MIME=E2=80=9C=
?
>>> Yes, there is contradiction in the RFC as written.
>>>=20
>>> I think some implementations would value interoperability with =
earlier versions of S/MIME higher than security and others would choose =
the opposite. Text in 2.7.1.2 seems to be written with the latter case =
in mind.
>>>=20
>>> For new implementations or implementations more concerned with =
security, using more modern crypto algorithms can be a good default.
>>>=20
>>>>> The common capability in both S/MIME versions would be =
AES-128-CBC, wouldn=E2=80=99t it?
>>>>>=20
>>>>> Also, I do not really understand the following sentence:
>>>>>=20
>>>>>   If the sending agent chooses not to use AES-256 GCM in this =
step,
>>>>>   given the presumption is that a client implementing AES-GCM =
would do
>>>>>   both AES-256 and AES-128, it SHOULD use AES-128 CBC.
>>>>>=20
>>>>> It appears to me as if this sentence was grammatically either =
wrong or uses a construct that I don=E2=80=99t understand (I=E2=80=99m =
not a native speaker).
>>> You are right, the above seems wrong. I think "is" needs to be =
dropped after "presumption".
>>>>> I don=E2=80=99t understand what "given the presumption is that a =
client implementing AES-GCM would do both AES-256 and AES-128=E2=80=9C  =
is meant to tell me in that context. Also, I=E2=80=99m not sure if the =
word =E2=80=9Eclient=E2=80=9C is meant to refer to the sending or =
receiving client. At first, I thought it=E2=80=99s the receiving client, =
but after re-reading a few times, I=E2=80=99m unsure if it=E2=80=99s the =
sending agent, because I don=E2=80=99t understand why I should make =
presumptions about the receiving client implementing AES-GCM when I =
don=E2=80=99t know anything about it.
>>> I think the text is trying to say that as the client supports AES, =
it is likely to support AES-128 CBC.
>>>>>=20
>>>>> I would recommend that this sentence maybe rephrase to make it =
more understandable for non-native speakers.
>>>>>=20
>>>>> What I would have expected in section 2.7.1.2:
>>>>>=20
>>>>> To maintain "greatest interoperability possible with agents for =
prior versions of S/MIME=E2=80=9C, the RFC would select AES-128-CBC if =
the recipient=E2=80=99s capabilities and S/MIME version aren=E2=80=99t =
known.
>>>>>=20
>>>>> Where am I off the track?
>>>>>=20
>>>>>=20
>>>>> Thanks a lot!
>>>>>=20
>>>>> Metin Savignano
>>> Best Regards,
>>>=20
>>> Alexey
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> Spasm mailing list
>>> Spasm@ietf.org <mailto:Spasm@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/spasm
>>=20
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


--Apple-Mail=_603E0545-9199-469A-97E1-5F141363B7DF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">The =
IETF is moving toward AEAD algorithms, and it will take a while for the =
products to add this capabaility. &nbsp;The AES-CBC is retained as a =
SHOULD requirement for transition.<div class=3D""><br =
class=3D""></div><div class=3D"">Russ</div><div class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 5, 2021, at 8:11 AM, Metin Savignano &lt;<a =
href=3D"mailto:ms@savignano.net" class=3D"">ms@savignano.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D"">Hi all,<div =
class=3D""><br class=3D""></div><div class=3D"">Thank you very much for =
your replies and insights.</div><div class=3D""><br class=3D""></div><div =
class=3D"">I=E2=80=99d like to comment back as follows:</div><div =
class=3D""><br class=3D""></div><div class=3D""><blockquote type=3D"cite" =
class=3D"">The meta point here is that as S/MIME has moved from RC4 to =
tripleDES (RFC 3851 v3.1), from tripleDES to AES-CBC (RFC 5751), and now =
from AES-CBC to AES-GCM (RFC 8751) the logic has been the same:<br =
class=3D""><br class=3D"">&nbsp;&nbsp;If you do not know what the =
receiving side<br class=3D"">&nbsp;&nbsp;supports send the best you =
got.</blockquote><div class=3D""><br class=3D""></div><div class=3D"">My =
memory can deceive, but I believe that when 3DES was recommended in =
2004, and AES-CBC in 2010, these ciphers have already been in use for a =
while, didn=E2=80=99t they?</div><div class=3D""><br class=3D""></div><div=
 class=3D""><div class=3D"">3DES was recommended in RFC 2633, and =
AES-CBC was included as SHOULD in RFC 3851, so these ciphers have been =
kind of announced before. AES-GCM block mode, however, is not announced =
or even mentioned in earlier publications, so comes as a surprise in RFC =
8551.</div></div><div class=3D""><br class=3D""></div><div class=3D"">My =
problem with AES-GCM is that we=E2=80=99ve run a few tests, and the mail =
clients we used were all unable to decrypt AES-GCM encrypted =
emails:</div><div class=3D""><ul class=3D""><li class=3D"">Outlook =
2016&nbsp;</li><li class=3D"">Apple Mail on macOS 10.14.6&nbsp;</li><li =
class=3D"">Apple Mail on iOS 13.6&nbsp;</li><li class=3D"">Thunderbird =
68.11.0</li></ul></div><div class=3D"">Considering the fact that you =
it=E2=80=99s not normally known what the other side supports, the advice =
to always send the best would now effectively disable encrypted =
communication with most clients for the moment being. Definitely =
something no one wants to explain their users.</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D""><blockquote type=3D"cite" class=3D"">You should also note =
that there is a big out in s2.7.1 in the last paragraph. All of 2.7.1.* =
is a SHOULD.<br class=3D""></blockquote></div><div class=3D""><br =
class=3D""></div>That=E2=80=99s correct, but as I understand the =
definition of SHOULD, it is relatively strong and should be ignored only =
in very specific cases for good reasons. However, trying to be =
compatible with other mail clients is by no means a specific scenario =
but the general scenario.</div><div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D"">So all we can do for now is to implement =
AES-GCM for incoming emails only. But we can=E2=80=99t say we follow RFC =
8551 without breaking compatibility.</div><div class=3D""><br =
class=3D""></div><div class=3D"">=46rom a PRACTICAL (=3D implementation) =
point of view, this IS a problem.</div></div><div class=3D""><br =
class=3D""></div><div class=3D""><blockquote type=3D"cite" =
class=3D"">ORIGINAL (wordy):<br class=3D"">given the presumption is that =
a client implementing&nbsp;<br class=3D"">MAYBE (less wordy):<br =
class=3D"">given the presumption that a client implementing<br =
class=3D"">OR (even more wordy):<br class=3D"">given that the =
presumption is that a client implementing<br class=3D"">OR (even less =
wordy):<br class=3D"">assuming a client implementing</blockquote><br =
class=3D""></div><div class=3D"">I can say for myself that these =
versions are the easiest for me to understand:</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><blockquote type=3D"cite"=
 class=3D"">MAYBE (less wordy):<br class=3D"">given the presumption that =
a client implementing</blockquote><br class=3D""></div><div =
class=3D"">and</div><div class=3D""><br class=3D""></div><div =
class=3D""><blockquote type=3D"cite" class=3D"">OR (even less wordy):<br =
class=3D"">assuming a client implementing</blockquote></div><div =
class=3D""><br class=3D""></div><div class=3D"">The last one is the =
clearest to me. I=E2=80=99d suggest an edit here.</div><div class=3D""><br=
 class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D"">Take care</div><div class=3D"">Metin</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">Am 23.12.2020 um 19:11 schrieb Sean Turner =
&lt;<a href=3D"mailto:sean@sn3rd.com" =
class=3D"">sean@sn3rd.com</a>&gt;:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Hi! =
Sorry it=E2=80=99s taken me forever to get to this.<br class=3D""><br =
class=3D"">I just want to be clear that the proposal here is not trying =
to change, what I believe and somebody else should correct me if they =
think otherwise, the consensus decision that GCM is the MUST.<br =
class=3D""><br class=3D"">The meta point here is that as S/MIME has =
moved from RC4 to tripleDES (RFC 3851 v3.1), from tripleDES to AES-CBC =
(RFC 5751), and now from AES-CBC to AES-GCM (RFC 8751) the logic has =
been the same:<br class=3D""><br class=3D""> &nbsp;&nbsp;If you do not =
know what the receiving side<br class=3D""> &nbsp;&nbsp;supports send =
the best you got.<br class=3D""><br class=3D"">There is no negotiation =
so better to err on the side of caution (for human controlled agents) =
even (s2.7.2) "if there is a possibility that the recipient will not be =
able to process that algorithm."<br class=3D""><br class=3D"">I would =
not read the paragraphs in question as a cookbook to get the most =
interoperability. If we want that, then we either switch to plaintext or =
we would need to decide on which version to most interoperable with. I =
would hazard a guess that that CBC based on v3.2 wouldn=E2=80=99t be the =
choice but instead tripleDES based on v3.1/v3.0.<br class=3D""><br =
class=3D"">You should also note that there is a big out in s2.7.1 in the =
last paragraph. All of 2.7.1.* is a SHOULD.<br class=3D""><br =
class=3D"">WRT the ambiguity between s1.4 and s2.7.1.2, I am not so sure =
there is one as I consider s1.4 to be feel good deployment consideration =
text lacking any requirements. It provides some history for readers =
unaware of it. But, that =E2=80=9Cought=E2=80=9D in s1.4 only applies =
some of the times, e.g., if this is a high security environment maybe do =
not use RC4 as specified in v2.<br class=3D""><br class=3D"">I could go =
either way on removing the =E2=80=9Cis=E2=80=9D. I think it is wordy, =
but not necessarily wrong. Then again I am no grammar scholar. I would =
certainly not object to an editorial errata if the WG felt it necessary. =
Some options:<br class=3D""><br class=3D"">ORIGINAL (wordy):<br =
class=3D"">given the presumption is that a client implementing <br =
class=3D"">MAYBE (less wordy):<br class=3D"">given the presumption that =
a client implementing<br class=3D"">OR (even more wordy):<br =
class=3D"">given that the presumption is that a client implementing<br =
class=3D"">OR (even less wordy):<br class=3D"">assuming a client =
implementing<br class=3D""><br class=3D"">Alexey is right in that what =
it is trying to say is that if a client supports AES it=E2=80=99s like =
to also support CBC. That is there so that implementations do not choose =
tripleDES, which was the old SHOULD-.<br class=3D""><br class=3D"">spt<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">On Dec 8, =
2020, at 12:48, Alexey Melnikov &lt;<a =
href=3D"mailto:alexey.melnikov@isode.com" =
class=3D"">alexey.melnikov@isode.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">Hi Metin,<br class=3D""><br class=3D"">I am not an =
author/editor of RFC 8551, but I will reply with my opinions in order to =
stimulate some discussion of issues that you've raised.<br class=3D""><br =
class=3D"">On 07/12/2020 09:06, Metin Savignano wrote:<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">Hi,<br class=3D""><br =
class=3D"">referring to my email quoted below of 7th August, may I ask =
if and how I would get a reply? I haven=E2=80=99t seen one, =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and I am wondering if I =
would have to look at some other place?<br class=3D""><br =
class=3D"">Thanks<br class=3D"">Metin<br class=3D""><br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">Anfang der =
weitergeleiteten Nachricht:<br class=3D""><br class=3D"">Von: Metin =
Savignano &lt;<a href=3D"mailto:ms@savignano.net" =
class=3D"">ms@savignano.net</a>&gt;<br class=3D"">Betreff: Possible =
inconsistencies or ambiguities in RFC 8551<br class=3D"">Datum: 7. =
August 2020 um 13:01:53 MESZ<br class=3D"">An: <a =
href=3D"mailto:spasm@ietf.org" class=3D"">spasm@ietf.org</a><br =
class=3D""><br class=3D"">Dear authors,<br class=3D""><br class=3D"">First=
 of all, thank you very much for your work to create a new and better =
version of S/MIME! <br class=3D""><br class=3D"">As an author of an =
S/MIME app, we are working through RFC 8551 to determine the changes we =
have to implement in order to fully comply to the S/MIME 4.0 specs.<br =
class=3D""><br class=3D"">However, I=E2=80=99ve come to a point where I =
seem unable to understand what the RFC actually recommends with regard =
to the backward compatibility. I=E2=80=99ve also discussed this with =
another software developer, but we both weren=E2=80=99t sure how to read =
it. It would be awesome if you could help me with a clarification.<br =
class=3D""><br class=3D"">In the relevant scenario, the sending agent =
wants to send encrypted email to a recipient with unknown =
capabilities.<br class=3D""><br class=3D"">With regard to backward =
compatibility, RFC 8551 states in section 1.4:<br class=3D""><br =
class=3D""> &nbsp;&nbsp;S/MIME version 4.0 agents ought to attempt to =
have the greatest<br class=3D""> &nbsp;&nbsp;interoperability possible =
with agents for prior versions of S/MIME.<br class=3D""><br class=3D""><br=
 class=3D"">Although this is a very general statement, I believe it is =
contradictory to the description about how to decide which content =
encryption cipher to use in section 2.7.1.2:<br class=3D""><br class=3D"">=
 &nbsp;&nbsp;If the following two conditions are met, the sending agent =
SHOULD use<br class=3D""> &nbsp;&nbsp;AES-256 GCM, as AES-256 GCM is a =
stronger algorithm and is required<br class=3D""> &nbsp;&nbsp;by S/MIME =
v4.0:<br class=3D""><br class=3D""> &nbsp;&nbsp;- &nbsp;The sending =
agent has no knowledge of the encryption capabilities<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;of the recipient.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;- &nbsp;The sending agent has no knowledge of =
the version of S/MIME used<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;or supported by the recipient.<br =
class=3D""><br class=3D"">I don=E2=80=99t understand why we should =
choose AES-256-GCM if we don=E2=80=99t know about the recipients =
capabilities and S/MIME version.<br class=3D""></blockquote></blockquote>I=
 agree with you that text from Sections 1.4 and 2.7.1.2 is =
contradictory.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">For example, if the =
recipient uses an S/MIME 3.2 compliant software, as I understand RFC =
5751, that software need not know about AES-256-GCM. The GCM block mode =
is not even mentioned in earlier S/MIME versions. &nbsp;As a =
consequence, doesn=E2=80=99t the selection of AES-256-GCM contradict the =
"attempt to have the greatest interoperability possible with agents for =
prior versions of S/MIME=E2=80=9C?<br =
class=3D""></blockquote></blockquote>Yes, there is contradiction in the =
RFC as written.<br class=3D""><br class=3D"">I think some =
implementations would value interoperability with earlier versions of =
S/MIME higher than security and others would choose the opposite. Text =
in 2.7.1.2 seems to be written with the latter case in mind.<br =
class=3D""><br class=3D"">For new implementations or implementations =
more concerned with security, using more modern crypto algorithms can be =
a good default.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">The common capability in =
both S/MIME versions would be AES-128-CBC, wouldn=E2=80=99t it?<br =
class=3D""><br class=3D"">Also, I do not really understand the following =
sentence:<br class=3D""><br class=3D""> &nbsp;&nbsp;If the sending agent =
chooses not to use AES-256 GCM in this step,<br class=3D""> =
&nbsp;&nbsp;given the presumption is that a client implementing AES-GCM =
would do<br class=3D""> &nbsp;&nbsp;both AES-256 and AES-128, it SHOULD =
use AES-128 CBC.<br class=3D""><br class=3D"">It appears to me as if =
this sentence was grammatically either wrong or uses a construct that I =
don=E2=80=99t understand (I=E2=80=99m not a native speaker).<br =
class=3D""></blockquote></blockquote>You are right, the above seems =
wrong. I think "is" needs to be dropped after "presumption".<br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D"">I don=E2=80=99t understand what "given the presumption is =
that a client implementing AES-GCM would do both AES-256 and AES-128=E2=80=
=9C &nbsp;is meant to tell me in that context. Also, I=E2=80=99m not =
sure if the word =E2=80=9Eclient=E2=80=9C is meant to refer to the =
sending or receiving client. At first, I thought it=E2=80=99s the =
receiving client, but after re-reading a few times, I=E2=80=99m unsure =
if it=E2=80=99s the sending agent, because I don=E2=80=99t understand =
why I should make presumptions about the receiving client implementing =
AES-GCM when I don=E2=80=99t know anything about it.<br =
class=3D""></blockquote></blockquote>I think the text is trying to say =
that as the client supports AES, it is likely to support AES-128 CBC.<br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">I would recommend that this sentence maybe =
rephrase to make it more understandable for non-native speakers.<br =
class=3D""><br class=3D"">What I would have expected in section =
2.7.1.2:<br class=3D""><br class=3D"">To maintain "greatest =
interoperability possible with agents for prior versions of S/MIME=E2=80=9C=
, the RFC would select AES-128-CBC if the recipient=E2=80=99s =
capabilities and S/MIME version aren=E2=80=99t known.<br class=3D""><br =
class=3D"">Where am I off the track?<br class=3D""><br class=3D""><br =
class=3D"">Thanks a lot!<br class=3D""><br class=3D"">Metin Savignano<br =
class=3D""></blockquote></blockquote>Best Regards,<br class=3D""><br =
class=3D"">Alexey<br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">Spasm mailing list<br class=3D""><a =
href=3D"mailto:Spasm@ietf.org" class=3D"">Spasm@ietf.org</a><br =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/spasm" =
class=3D"">https://www.ietf.org/mailman/listinfo/spasm</a><br =
class=3D""></blockquote><br class=3D""></div></div></blockquote></div><br =
class=3D""></div></div>_______________________________________________<br =
class=3D"">Spasm mailing list<br class=3D""><a =
href=3D"mailto:Spasm@ietf.org" class=3D"">Spasm@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/spasm<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_603E0545-9199-469A-97E1-5F141363B7DF--

--Apple-Mail=_DA8E83F1-0116-4055-AAF3-68E641555182
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iF0EARECAB0WIQRJuTEKFXbtfFQz5huK5O7Q9ZwRywUCX/Xg+AAKCRCK5O7Q9ZwR
yzo3AKCcPb39+9W60acAfTsNwffAUPajDACbBmLtsLefWanztuMuwemml0kTm5M=
=FbGK
-----END PGP SIGNATURE-----

--Apple-Mail=_DA8E83F1-0116-4055-AAF3-68E641555182--


From nobody Wed Jan  6 08:21:30 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5BA73A0FC2 for <spasm@ietfa.amsl.com>; Wed,  6 Jan 2021 08:21:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WzV3-ZyuGBw1 for <spasm@ietfa.amsl.com>; Wed,  6 Jan 2021 08:21:25 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A099A3A0DD5 for <spasm@ietf.org>; Wed,  6 Jan 2021 08:21:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 15844300B90 for <spasm@ietf.org>; Wed,  6 Jan 2021 11:21:23 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id WboBOrmrdBFR for <spasm@ietf.org>; Wed,  6 Jan 2021 11:21:17 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 1264F300A48; Wed,  6 Jan 2021 11:21:17 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <E04D2C20-2BFB-447F-A59D-48E7C98A3F6D@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4FF83813-219A-47D8-8E57-A05C633EA904"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Wed, 6 Jan 2021 11:21:18 -0500
In-Reply-To: <AD171E90-8F99-44FA-990C-BC4878A20772@kuehlewind.net>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, LAMPS <spasm@ietf.org>, IAB <iab@iab.org>
To: =?utf-8?B?Ik1pcmphIEvDvGhsZXdpbmQgKElFVEYpIg==?= <ietf@kuehlewind.net>
References: <52B573D6-5DB4-41DA-95F1-20C3EB5EEAC0@vigilsec.com> <AD171E90-8F99-44FA-990C-BC4878A20772@kuehlewind.net>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/huFfalg2vi9P1m9Qt56HbO3BmVU>
Subject: Re: [lamps] [IAB]  Conflict between RFC8954 and ISO 14533-4
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 16:21:29 -0000

--Apple-Mail=_4FF83813-219A-47D8-8E57-A05C633EA904
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Mirja:

We do not know whether the ISO TC has been notified.  I am guessing that =
a participant in that group rasided the issue with the LAMPS WG, butwe =
do not know that for sure.

Russ

> On Jan 6, 2021, at 8:20 AM, Mirja K=C3=BChlewind (IETF) =
<ietf@kuehlewind.net> wrote:
>=20
> Hi Russ,
>=20
> Thanks for noting this. Do we know if this concern was already raised =
(informally) with ISO?=20
>=20
> If we don=E2=80=99t have people who are participating also in ISO and =
can easily start the discussion directly, sending a LS seems to be =
appropriate that reflects the concept of the lamps group. In this case =
you/the chairs should get in touch with your AD and maybe some of the =
key participants for this discussion and draft some text for discussion =
in the group. The IAB doesn=E2=80=99t necessarily need to be involved to =
send out the LS but we are happy to help or serve as the official sender =
if that=E2=80=99s most appropriate in the ISO context.
>=20
> Mirja
>=20
>=20
>> Am 23.12.2020 um 17:21 schrieb Russ Housley <housley@vigilsec.com>:
>>=20
>> =EF=BB=BF
>> Marian =C4=8Eurkovi=C4=8D <md@bts.sk <mailto:md@bts.sk>> brought it =
to the attention of the LAMPS WG.  That was a message out of the blue =
from my perspective.
>>=20
>> Russ
>>=20
>>=20
>>=20
>>> On Dec 23, 2020, at 11:09 AM, Stephen Farrell =
<stephen.farrell@cs.tcd.ie <mailto:stephen.farrell@cs.tcd.ie>> wrote:
>>>=20
>>> Signed PGP part
>>>=20
>>> Hi Russ,
>>>=20
>>> On 23/12/2020 15:41, Russ Housley wrote:
>>>> Dear  IAB:
>>>> The IETF does not have a liaison relationship with the ISO TC that
>>>> produced ISO 14533-4:2019.  It would be a good think to tell that
>>>> group that we disagree with the approach that was taken.  What does
>>>> the IAB suggest?
>>>=20
>>> I've not followed this discussion, nor am I at all familiar
>>> with that ISO spec, so I'd have to get up to speed before I'd
>>> have an informed opinion.
>>>=20
>>> Does anyone know someone involved with that ISO group/spec?
>>> If so, I'd say trying to see if it can be sorted out at that
>>> level would be good (if it's not happened already).
>>>=20
>>> If there's no good contact available then yeah I guess the
>>> IAB might try find a way to send a message to ISO. First up
>>> though might be for lamps to craft the message to be sent
>>> (including enough background that IAB and ISO folks will get
>>> the point). I'd be happy to bring such a message to the IAB
>>> and ask that we figure out how to get it sent to the right
>>> place/people.
>>>=20
>>> Cheers,
>>> S.
>>>=20
>>> PS: The above is clearly just me speaking, and isn't the
>>> consensus of the IAB:-)
>>>=20
>>>> Russ
>>>>> On Dec 23, 2020, at 2:40 AM, Tomas Gustavsson
>>>>> <tomas.gustavsson@primekey.com =
<mailto:tomas.gustavsson@primekey.com>> wrote:
>>>>> Hi,
>>>>> I'd like to give my view on this.
>>>>> I support not changing anything in RFC8954.
>>>>> I recently started using the term "tweaking standards" for when =
you
>>>>> take an existing field in a standard and use it for other purposes
>>>>> than the one stated in the standard, just because it is =
technically
>>>>> possible and not explicitly forbidden in the standard. This has
>>>>> been done many times before, and many times it leads to
>>>>> interoperability issues, severe spending of time, money and
>>>>> resources, and in severe cases even downtime. Tweaking standards =
is
>>>>> a short term short-cut, ignoring long term costs.
>>>>> ISO 14533 clearly tweaked RFC6960 section 4.4.1.
>>>>> Many internet scale OCSP responders today do not include Nonce in
>>>>> the response. Regardless if the client sends it. This is for
>>>>> caching reasons, and is for both GET and POST requests.
>>>>> Using nonce as MessageImprint is non-interoperable with RFC6960 =
and
>>>>> with the real world.
>>>>> I'd like to say it again: ISO 14533 is non-interoperable with how
>>>>> OCSP is deployed on the internet today.
>>>>> It is a disaster waiting to happen. The reason it hasn't happened
>>>>> yet is likely due to ISO 14533 not being widely used. Let's fix it
>>>>> before it falls apart. The solution is not to force RFC6960
>>>>> compliant OCSP responders into submission to ISO 14533, but to fix
>>>>> ISO 14533. ISO 14533 should recognize that the suggested solution
>>>>> is non-compliant, causing interoperability issues, and go back and
>>>>> create an extension. Yes, it's a little more work, and may result
>>>>> in a new RFC, or a replacement of RFC6960 (but the extension can =
be
>>>>> private to ISO 14533 to start with), but it's the right thing to =
do
>>>>> imho.
>>>>> There is already an extension, a bit similar to this, specified in
>>>>> the German Common PKI. https://de.wikipedia.org/wiki/Common_PKI =
<https://de.wikipedia.org/wiki/Common_PKI> It's called CertHash and can =
be copied. The specification isn't available any longer, but I have an =
off-line copy that I share
>>>>> here: https://app.box.com/s/lk1g4a3h75icirnu6xqrqhee8h5kmv54 =
<https://app.box.com/s/lk1g4a3h75icirnu6xqrqhee8h5kmv54>
>>>>> It's a SingleResponse extension, section 3.1.2:
>>>>> id-commonpki-at-certHash OBJECT IDENTIFIER ::=3D=3D {1 3 36 8 3 =
13}
>>>>> CertHash ::=3D SEQUENCE { hashAlgorithm AlgorithmIdentifier, // =
The
>>>>> identifier of the algorithm // that has been used the for hash =
//value below.
>>>>> certificateHash OCTET STRING // A hash over the DER-encoding of
>>>>> the // entire PKC or AC (i.e. NOT a hash // over tbsCertificate). =
}
>>>>> There are OCSP responders out there supporting the old CertHash
>>>>> extension.
>>>>> Not saying to use it "as is", it has another purpose, but very
>>>>> very similar. Just put a new OID and rename it to
>>>>> MessageImprint...
>>>>> Best regards, Tomas
>>>>> On 2020-12-21 17:36, Marian =C4=8Eurkovi=C4=8D wrote:
>>>>>> *On Sat, 19 Dec 2020 13:12:17 -0800, Mohit Sahni wrote*
>>>>>>> =46rom OCSP point of view the MessageImprint is not a random
>>>>>>> value but
>>>>>> it is a deterministic value generated for a given input by a
>>>>>> collision resistant one way hash function.
>>>>>> This input, however, consists of multiple parts: some of them
>>>>>> being random, some of them being unknown even to document signer
>>>>>> (private key). In any case, an attacker is not able to guess this
>>>>>> value so it serves against reply attack very well.
>>>>>>> One more reason I see for not changing the Nonce extension
>>>>>>> length is
>>>>>> that the length of MessageImprint is not fixed but varies based
>>>>>> on the underlying hash algorithm.  Since RFC3161 does not provide
>>>>>> a fixed list of Hash functions, let's say we change the size to
>>>>>> Nonce extension to 64 bytes, what if in the future there is a new
>>>>>> hash algorithm or some proprietary hash function that requires
>>>>>> size to be 128 bytes or 256 bytes or may be 100 GigaBytes, are we
>>>>>> going to increase the size of the Nonce extension again?  How can
>>>>>> we set an upper limit on Nonce which also serves the regular
>>>>>> Nonce use case of just avoiding the replay attacks ?
>>>>>> I proposed 2 values: 96 bytes if we want to accomodate 512-bit
>>>>>> hashes, or 160 bytes, if we want to accomodate (future) 1024-bit
>>>>>> hashes. Any hashing algorithm is designed to yield a relatively
>>>>>> small result, so we're certainly not talking about GigaBytes
>>>>>> here...
>>>>>>> In my opinion, ISO 14533 took advantage of the security
>>>>>>> vulnerability
>>>>>> that existed in RFC6960 and tried using Nonce extension in a way
>>>>>> it was not intended to be used as i.e. using an ASN.1 SEQUENCE
>>>>>> where the standard requires use of OCTET STRING.
>>>>>> OCTET STRING means arbitrary sequence of bytes, which OCSP
>>>>>> responder shouldn't interpret in any way - just echo them back in
>>>>>> its response. It's completely irrelevant, what's encoded inside -
>>>>>> after all, a random number could also start with 0x30 which
>>>>>> corresponds to SEQUENCE.
>>>>>>> We should come up with a new extension for associating the
>>>>>>> OCSP
>>>>>> response with the context where OCSP is being used for long term =
validation. That is the right thing to do.
>>>>>> And what will be the advantage of having yet another extension
>>>>>> doing the same thing? Both use cases require nothing else from
>>>>>> OCSP responder than to echo back exactly the same bytes it
>>>>>> received in request. Do you propose to have 2 extensions, one of
>>>>>> them being able to only echo 32 bytes and another being able to
>>>>>> echo 96? or 160? or unlimited bytes? Isn't it much more
>>>>>> straightforward to have only one "echoing" extension being able
>>>>>> to echo as many bytes as needed for both use cases?
>>>>>> On the other hand, the disadvantages are significant - I
>>>>>> mentioned some of them in my previous email. Also please keep in
>>>>>> mind, that RFC 8954 (if applied by OCSP responder or by some
>>>>>> firewall doing deep packet inspection) will immediately break
>>>>>> digital signing - since it says:
>>>>>> A server *MUST* reject any OCSP request that has a nonce in the
>>>>>> Nonce extension with a length of either 0 octets or more than 32
>>>>>> octets with the malformedRequest OCSPResponseStatus
>>>>>> Last but not least, introducing another extension is more complex
>>>>>> than you assume - it will require modification of (at least)
>>>>>> RFC6960, RFC5019, ISO 14533-4. When will that solution be
>>>>>> available and what to do until then?
>>>>>> With kind regards, MD
>>>>>> _______________________________________________ Spasm mailing
>>>>>> list Spasm@ietf.org <mailto:Spasm@ietf.org> =
https://www.ietf.org/mailman/listinfo/spasm =
<https://www.ietf.org/mailman/listinfo/spasm>
>>>>> _______________________________________________ Spasm mailing list =
Spasm@ietf.org <mailto:Spasm@ietf.org> =
https://www.ietf.org/mailman/listinfo/spasm =
<https://www.ietf.org/mailman/listinfo/spasm>
>>>> _______________________________________________ Spasm mailing list =
Spasm@ietf.org <mailto:Spasm@ietf.org> =
https://www.ietf.org/mailman/listinfo/spasm =
<https://www.ietf.org/mailman/listinfo/spasm>
>>> <OpenPGP_0x5AB2FAF17B172BEA.asc>
>>>=20
>>>=20
>>=20


--Apple-Mail=_4FF83813-219A-47D8-8E57-A05C633EA904
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Mirja:<div class=3D""><br class=3D""></div><div class=3D"">We =
do not know whether the ISO TC has been notified. &nbsp;I am guessing =
that a participant in that group rasided the issue with the LAMPS WG, =
butwe do not know that for sure.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Russ<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Jan =
6, 2021, at 8:20 AM, Mirja K=C3=BChlewind (IETF) &lt;<a =
href=3D"mailto:ietf@kuehlewind.net" class=3D"">ietf@kuehlewind.net</a>&gt;=
 wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta=
 http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div dir=3D"auto" class=3D""><div dir=3D"ltr" class=3D"">Hi =
Russ,</div><div dir=3D"ltr" class=3D""><br class=3D""></div><div =
dir=3D"ltr" class=3D"">Thanks for noting this. Do we know if this =
concern was already raised (informally) with ISO?&nbsp;</div><div =
dir=3D"ltr" class=3D""><br class=3D""></div><div dir=3D"ltr" class=3D"">If=
 we don=E2=80=99t have people who are participating also in ISO and can =
easily start the discussion directly, sending a LS seems to be =
appropriate that reflects the concept of the lamps group. In this case =
you/the chairs should get in touch with your AD and maybe some of the =
key participants for this discussion and draft some text for discussion =
in the group. The IAB doesn=E2=80=99t necessarily need to be involved to =
send out the LS but we are happy to help or serve as the official sender =
if that=E2=80=99s most appropriate in the ISO context.</div><div =
dir=3D"ltr" class=3D""><br class=3D""></div><div dir=3D"ltr" =
class=3D"">Mirja</div><div dir=3D"ltr" class=3D""><br =
class=3D""></div><div dir=3D"ltr" class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">Am 23.12.2020 um 17:21 schrieb Russ Housley =
&lt;<a href=3D"mailto:housley@vigilsec.com" =
class=3D"">housley@vigilsec.com</a>&gt;:<br class=3D""><br =
class=3D""></blockquote></div><blockquote type=3D"cite" class=3D""><div =
dir=3D"ltr" class=3D"">=EF=BB=BF<meta http-equiv=3D"Content-Type" =
content=3D"text/html; charset=3Dutf-8" class=3D""><p style=3D"margin: =
0px 0px 2px; font-stretch: normal; font-size: 14px; line-height: normal; =
font-family: &quot;Helvetica Neue&quot;;" class=3D"">Marian =C4=8Eurkovi=C4=
=8D &lt;<a href=3D"mailto:md@bts.sk" class=3D"">md@bts.sk</a>&gt; =
brought it to the attention of the LAMPS WG. &nbsp;That was a message =
out of the blue from my perspective.</p><p style=3D"margin: 0px 0px 2px; =
font-stretch: normal; font-size: 14px; line-height: normal; font-family: =
&quot;Helvetica Neue&quot;;" class=3D""><br class=3D""></p><p =
style=3D"margin: 0px 0px 2px; font-stretch: normal; font-size: 14px; =
line-height: normal; font-family: &quot;Helvetica Neue&quot;;" =
class=3D"">Russ</p><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D""><br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D"">On Dec 23, 2020, at 11:09 AM, =
Stephen Farrell &lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" =
class=3D"">stephen.farrell@cs.tcd.ie</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D""><div =
class=3D"protected-part"><div class=3D"protected-title">Signed PGP =
part</div><div class=3D"protected-content"><br class=3D"">Hi Russ,<br =
class=3D""><br class=3D"">On 23/12/2020 15:41, Russ Housley wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">Dear &nbsp;IAB:<br =
class=3D"">The IETF does not have a liaison relationship with the ISO TC =
that<br class=3D"">produced ISO 14533-4:2019. &nbsp;It would be a good =
think to tell that<br class=3D"">group that we disagree with the =
approach that was taken. &nbsp;What does<br class=3D"">the IAB =
suggest?<br class=3D""></blockquote><br class=3D"">I've not followed =
this discussion, nor am I at all familiar<br class=3D"">with that ISO =
spec, so I'd have to get up to speed before I'd<br class=3D"">have an =
informed opinion.<br class=3D""><br class=3D"">Does anyone know someone =
involved with that ISO group/spec?<br class=3D"">If so, I'd say trying =
to see if it can be sorted out at that<br class=3D"">level would be good =
(if it's not happened already).<br class=3D""><br class=3D"">If there's =
no good contact available then yeah I guess the<br class=3D"">IAB might =
try find a way to send a message to ISO. First up<br class=3D"">though =
might be for lamps to craft the message to be sent<br =
class=3D"">(including enough background that IAB and ISO folks will =
get<br class=3D"">the point). I'd be happy to bring such a message to =
the IAB<br class=3D"">and ask that we figure out how to get it sent to =
the right<br class=3D"">place/people.<br class=3D""><br =
class=3D"">Cheers,<br class=3D"">S.<br class=3D""><br class=3D"">PS: The =
above is clearly just me speaking, and isn't the<br class=3D"">consensus =
of the IAB:-)<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">Russ<br class=3D""><blockquote type=3D"cite" class=3D"">On =
Dec 23, 2020, at 2:40 AM, Tomas Gustavsson<br class=3D"">&lt;<a =
href=3D"mailto:tomas.gustavsson@primekey.com" =
class=3D"">tomas.gustavsson@primekey.com</a>&gt; wrote:<br =
class=3D"">Hi,<br class=3D"">I'd like to give my view on this.<br =
class=3D"">I support not changing anything in RFC8954.<br class=3D"">I =
recently started using the term "tweaking standards" for when you<br =
class=3D"">take an existing field in a standard and use it for other =
purposes<br class=3D"">than the one stated in the standard, just because =
it is technically<br class=3D"">possible and not explicitly forbidden in =
the standard. This has<br class=3D"">been done many times before, and =
many times it leads to<br class=3D"">interoperability issues, severe =
spending of time, money and<br class=3D"">resources, and in severe cases =
even downtime. Tweaking standards is<br class=3D"">a short term =
short-cut, ignoring long term costs.<br class=3D"">ISO 14533 clearly =
tweaked RFC6960 section 4.4.1.<br class=3D"">Many internet scale OCSP =
responders today do not include Nonce in<br class=3D"">the response. =
Regardless if the client sends it. This is for<br class=3D"">caching =
reasons, and is for both GET and POST requests.<br class=3D"">Using =
nonce as MessageImprint is non-interoperable with RFC6960 and<br =
class=3D"">with the real world.<br class=3D"">I'd like to say it again: =
ISO 14533 is non-interoperable with how<br class=3D"">OCSP is deployed =
on the internet today.<br class=3D"">It is a disaster waiting to happen. =
The reason it hasn't happened<br class=3D"">yet is likely due to ISO =
14533 not being widely used. Let's fix it<br class=3D"">before it falls =
apart. The solution is not to force RFC6960<br class=3D"">compliant OCSP =
responders into submission to ISO 14533, but to fix<br class=3D"">ISO =
14533. ISO 14533 should recognize that the suggested solution<br =
class=3D"">is non-compliant, causing interoperability issues, and go =
back and<br class=3D"">create an extension. Yes, it's a little more =
work, and may result<br class=3D"">in a new RFC, or a replacement of =
RFC6960 (but the extension can be<br class=3D"">private to ISO 14533 to =
start with), but it's the right thing to do<br class=3D"">imho.<br =
class=3D"">There is already an extension, a bit similar to this, =
specified in<br class=3D"">the German Common PKI. <a =
href=3D"https://de.wikipedia.org/wiki/Common_PKI" =
class=3D"">https://de.wikipedia.org/wiki/Common_PKI</a> It's called =
CertHash and can be copied. The specification isn't available any =
longer, but I have an off-line copy that I share<br class=3D"">here: <a =
href=3D"https://app.box.com/s/lk1g4a3h75icirnu6xqrqhee8h5kmv54" =
class=3D"">https://app.box.com/s/lk1g4a3h75icirnu6xqrqhee8h5kmv54</a><br =
class=3D"">It's a SingleResponse extension, section 3.1.2:<br =
class=3D"">id-commonpki-at-certHash OBJECT IDENTIFIER ::=3D=3D {1 3 36 8 =
3 13}<br class=3D"">CertHash ::=3D SEQUENCE { hashAlgorithm =
AlgorithmIdentifier, // The<br class=3D"">identifier of the algorithm // =
that has been used the for hash //value below.<br =
class=3D"">certificateHash OCTET STRING // A hash over the DER-encoding =
of<br class=3D"">the // entire PKC or AC (i.e. NOT a hash // over =
tbsCertificate). }<br class=3D"">There are OCSP responders out there =
supporting the old CertHash<br class=3D"">extension.<br class=3D"">Not =
saying to use it "as is", it has another purpose, but very<br =
class=3D"">very similar. Just put a new OID and rename it to<br =
class=3D"">MessageImprint...<br class=3D"">Best regards, Tomas<br =
class=3D"">On 2020-12-21 17:36, Marian =C4=8Eurkovi=C4=8D wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">*On Sat, 19 Dec 2020 =
13:12:17 -0800, Mohit Sahni wrote*<br class=3D""><blockquote type=3D"cite"=
 class=3D"">=46rom OCSP point of view the MessageImprint is not a =
random<br class=3D"">value but<br class=3D""></blockquote>it is a =
deterministic value generated for a given input by a<br =
class=3D"">collision resistant one way hash function.<br class=3D"">This =
input, however, consists of multiple parts: some of them<br =
class=3D"">being random, some of them being unknown even to document =
signer<br class=3D"">(private key). In any case, an attacker is not able =
to guess this<br class=3D"">value so it serves against reply attack very =
well.<br class=3D""><blockquote type=3D"cite" class=3D"">One more reason =
I see for not changing the Nonce extension<br class=3D"">length is<br =
class=3D""></blockquote>that the length of MessageImprint is not fixed =
but varies based<br class=3D"">on the underlying hash algorithm. =
&nbsp;Since RFC3161 does not provide<br class=3D"">a fixed list of Hash =
functions, let's say we change the size to<br class=3D"">Nonce extension =
to 64 bytes, what if in the future there is a new<br class=3D"">hash =
algorithm or some proprietary hash function that requires<br =
class=3D"">size to be 128 bytes or 256 bytes or may be 100 GigaBytes, =
are we<br class=3D"">going to increase the size of the Nonce extension =
again? &nbsp;How can<br class=3D"">we set an upper limit on Nonce which =
also serves the regular<br class=3D"">Nonce use case of just avoiding =
the replay attacks ?<br class=3D"">I proposed 2 values: 96 bytes if we =
want to accomodate 512-bit<br class=3D"">hashes, or 160 bytes, if we =
want to accomodate (future) 1024-bit<br class=3D"">hashes. Any hashing =
algorithm is designed to yield a relatively<br class=3D"">small result, =
so we're certainly not talking about GigaBytes<br class=3D"">here...<br =
class=3D""><blockquote type=3D"cite" class=3D"">In my opinion, ISO 14533 =
took advantage of the security<br class=3D"">vulnerability<br =
class=3D""></blockquote>that existed in RFC6960 and tried using Nonce =
extension in a way<br class=3D"">it was not intended to be used as i.e. =
using an ASN.1 SEQUENCE<br class=3D"">where the standard requires use of =
OCTET STRING.<br class=3D"">OCTET STRING means arbitrary sequence of =
bytes, which OCSP<br class=3D"">responder shouldn't interpret in any way =
- just echo them back in<br class=3D"">its response. It's completely =
irrelevant, what's encoded inside -<br class=3D"">after all, a random =
number could also start with 0x30 which<br class=3D"">corresponds to =
SEQUENCE.<br class=3D""><blockquote type=3D"cite" class=3D"">We should =
come up with a new extension for associating the<br class=3D"">OCSP<br =
class=3D""></blockquote>response with the context where OCSP is being =
used for long term validation. That is the right thing to do.<br =
class=3D"">And what will be the advantage of having yet another =
extension<br class=3D"">doing the same thing? Both use cases require =
nothing else from<br class=3D"">OCSP responder than to echo back exactly =
the same bytes it<br class=3D"">received in request. Do you propose to =
have 2 extensions, one of<br class=3D"">them being able to only echo 32 =
bytes and another being able to<br class=3D"">echo 96? or 160? or =
unlimited bytes? Isn't it much more<br class=3D"">straightforward to =
have only one "echoing" extension being able<br class=3D"">to echo as =
many bytes as needed for both use cases?<br class=3D"">On the other =
hand, the disadvantages are significant - I<br class=3D"">mentioned some =
of them in my previous email. Also please keep in<br class=3D"">mind, =
that RFC 8954 (if applied by OCSP responder or by some<br =
class=3D"">firewall doing deep packet inspection) will immediately =
break<br class=3D"">digital signing - since it says:<br class=3D"">A =
server *MUST* reject any OCSP request that has a nonce in the<br =
class=3D"">Nonce extension with a length of either 0 octets or more than =
32<br class=3D"">octets with the malformedRequest OCSPResponseStatus<br =
class=3D"">Last but not least, introducing another extension is more =
complex<br class=3D"">than you assume - it will require modification of =
(at least)<br class=3D"">RFC6960, RFC5019, ISO 14533-4. When will that =
solution be<br class=3D"">available and what to do until then?<br =
class=3D"">With kind regards, MD<br =
class=3D"">_______________________________________________ Spasm =
mailing<br class=3D"">list <a href=3D"mailto:Spasm@ietf.org" =
class=3D"">Spasm@ietf.org</a> <a =
href=3D"https://www.ietf.org/mailman/listinfo/spasm" =
class=3D"">https://www.ietf.org/mailman/listinfo/spasm</a><br =
class=3D""></blockquote>_______________________________________________ =
Spasm mailing list <a href=3D"mailto:Spasm@ietf.org" =
class=3D"">Spasm@ietf.org</a> <a =
href=3D"https://www.ietf.org/mailman/listinfo/spasm" =
class=3D"">https://www.ietf.org/mailman/listinfo/spasm</a><br =
class=3D""></blockquote>_______________________________________________ =
Spasm mailing list <a href=3D"mailto:Spasm@ietf.org" =
class=3D"">Spasm@ietf.org</a> <a =
href=3D"https://www.ietf.org/mailman/listinfo/spasm" =
class=3D"">https://www.ietf.org/mailman/listinfo/spasm</a><br =
class=3D""></blockquote><span =
id=3D"cid:BB989B60-8E12-47E3-8F01-892C145CD272@fios-router.home" =
class=3D"">&lt;OpenPGP_0x5AB2FAF17B172BEA.asc&gt;</span></div></div><br =
class=3D""><iframe class=3D"untrusted-content-test" scrolling=3D"auto" =
width=3D"200" height=3D"20" =
style=3D"border:none;display:block;overflow:auto;" =
data-src=3D"data:text/html;charset=3DUTF-8;base64,PGlmcmFtZS1jb250ZW50Pl9f=
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPEJSPlNwYXNtIG=
1haWxpbmcgbGlzdDxCUj5TcGFzbUBpZXRmLm9yZzxCUj5odHRwczovL3d3dy5pZXRmLm9yZy9t=
YWlsbWFuL2xpc3RpbmZvL3NwYXNtPEJSPjwvaWZyYW1lLWNvbnRlbnQ+" =
sandbox=3D"allow-scripts"></iframe></div></div></blockquote></div><br =
class=3D""></div></blockquote></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_4FF83813-219A-47D8-8E57-A05C633EA904--


From nobody Fri Jan  8 14:38:45 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3F03A1351 for <spasm@ietfa.amsl.com>; Fri,  8 Jan 2021 14:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id leKTTb240jlZ for <spasm@ietfa.amsl.com>; Fri,  8 Jan 2021 14:38:42 -0800 (PST)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2112.outbound.protection.outlook.com [40.107.236.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 344B13A03F5 for <spasm@ietf.org>; Fri,  8 Jan 2021 14:38:42 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hkQqIupBUN3Lie8QGgFs/e9yPzxSrhhTwVZnUcaYk2aYOI9oKBWC3d1tJX7DqKKmXmZ0Yt7PlbKLW02RchJbSnieuOdXGyhy5f3vRCSK76+BSCCYRVw8BHj6O8Sf56c9bUhs1ChSy3cwsIXzfBC8kRp3GircUFLH3yqziI0TSa+wefvi1HiDHhVm/mGpxTaklnMuCQ0eWpFzGLSaivRX7oT1hLeRNF0XPv3yzu4ozPd/VbbLL36c/BNq68T+ah7874rWK87XUriCr5FpLaEgQf+bJ3OTNjkIsdu5LIn54jDxBz6ELd17LRfj3Z3ORJolQ5sU4XpnVBsLNQKREYZ0pQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9MLgnNcDbJmweWQs6nc6dKBjsHCDmHlXQUjlzbRPio8=; b=kldg5l7Qd8Qw2zvp3BeMXQaCA9YZrEFGK+Dp1eaHaWWZ82Bq6KtnGkmvyed3QaJB2T3GPj+lUFKE9hO2J3CpLbzW/gJXjPBdKhxtysKEbaRZ9Db+ghHpdgpxJnCiHeItYpO917w1jhUOpA+f4MCQerXJDSom3YLRFo7bVozxw4qvqoCDMBO3Oojj6NWLUswLYwhKY4GCKPbz5blV9/4RQdBnaM3NwiHNGznbkl1yIOs5zFqbueYpCpS+UnvnXRkjcY2z56aHMIHCE6dAATR+W77vgqidImae18WsW57HZCGKS6SWFT8tVPsu8zcDCQ/NKU3Q4qJCkGKKybVy1dqDEQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9MLgnNcDbJmweWQs6nc6dKBjsHCDmHlXQUjlzbRPio8=; b=UfIJlIJI5uBlrh6s1PWp1Cq3yrRb7kqIfnlING6L1Pu8mQb4OvQvBlLZ72YeKgDRGYT2kw9bYmNal19xuFa6jeZFP5u8JbWBjeRTD0XXCYPs4zqdiBOFpPEWxhJM0X971RMb2wd8bEHI0G2cdrSud4+iCRhvWZaYOfNrdrSNsZtVEd92E4Ryip3Glr0VKv4f54pkXIo3lJprXnacml5UZ57RnBdihz85uWggYCNfMFmfaBGAfCR50dCQ0Sb6Wtnjcub0HzrdpVpBGZgx/X9uXqUPMN8/Syf7MlWLjIssZieFA/iKp2rZ/5cUqnP8Egjark5dF2GkkHy0AulPELuu/g==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB4563.namprd11.prod.outlook.com (2603:10b6:5:28e::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Fri, 8 Jan 2021 22:38:39 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.006; Fri, 8 Jan 2021 22:38:39 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: "spasm@ietf.org" <spasm@ietf.org>
CC: Russ Housley <housley@vigilsec.com>
Thread-Topic: Mail regarding draft-ietf-lamps-crmf-update-algs-02
Thread-Index: AdbmDrJ8XClSyQZRTI2kM/VC377vqg==
Date: Fri, 8 Jan 2021 22:38:39 +0000
Message-ID: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [72.136.100.224]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b48b447b-8494-4010-dd06-08d8b4262530
x-ms-traffictypediagnostic: DM6PR11MB4563:
x-microsoft-antispam-prvs: <DM6PR11MB4563C20B8269E8EECCCEC9D79FAE0@DM6PR11MB4563.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: dig3MjUkoaZjlQyKuhQohBYr4gGghf2QnHV4VmdFmRBpd+vSkq+sJZvcYeSZAwvh+/HjQTet/b07L3M7F6lz3U+3IVpIQVLef4HS4V249BOlcXqSa3mzIgk2u2vi/GyYajrVKZtABXxIqok6iA0rRdSAbrXyfmIsid9ItSrYuCdpUu97uDHcQ1UYS9qLL4WbdznyeashdjRI1CkSgPFcVamQkxxU7UvTlIWQfN6b1XqaWEMphj7WAYJCCX6pnoBSdgJzwXdBWGwJluBabvSQW+NUuHK3hRr9rhsuJWcGkzQIU7YB3/3q6iNSv0LNEiaXBNYTYhFIqngTMZfGXnN4FSm1FfvxLk8o8LG3/Pd9VPO4P3cusEiqk4tTljPRhwk1ZsvjZuewxU7yHBFgyXa3Gw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(376002)(396003)(346002)(136003)(39850400004)(55016002)(186003)(26005)(316002)(33656002)(478600001)(6506007)(9686003)(8936002)(4326008)(86362001)(71200400001)(7696005)(64756008)(66556008)(66476007)(66946007)(66446008)(83380400001)(15650500001)(52536014)(2906002)(76116006)(8676002)(6916009)(5660300002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?+I9+L5b2OtPNP8ph0bJ8/DHYETJH3fl6eyatAEf2wSSXXRbiNyoLKhaw+9dm?= =?us-ascii?Q?+Xnn59w+FRw6THGz8CJ9iEleYkFD51q8NMYtOX2EmZzOecaNXh/yhvDOJW1k?= =?us-ascii?Q?UD9b+xvbZo7snut/2Jfd8/8wGHn4Yk8zyD6Om1aCsLH+bieyiIDfceU6QBaO?= =?us-ascii?Q?a8dYfgvAr5TSql+0y2787ltsdaGfo8CrWYa0LaYXVb5y2VXdq/bMsX9NUrOT?= =?us-ascii?Q?JS7LL5INsDhcTzp3lbllMxyBOmml7Zj0kL9FHVdBUG4fDJ8wQfyy6u4RjuGn?= =?us-ascii?Q?Lq9ju9fNiEy9jmryO638JpD/3Qb/BINBmM8sH+9RETdQAY/PRtELRSyAT+V/?= =?us-ascii?Q?S3gwdEOEk+O/yuNDBcvDnAY20USrNgQM48tdNHnQfW5p/6aORgObM5bzK9m4?= =?us-ascii?Q?vQ/JRYyfhlkzNtgxhB7ctzqSF6f9QfmoGHZsfKix/c0Hl5JSIklg2gDq/86r?= =?us-ascii?Q?9Q/viZQrLD/f6R38Gdwp9UwyX4oqDWCRM2EBgleOideRS4EFBIQJKQBBeTgG?= =?us-ascii?Q?CUSkak6scmBsAAYUt9nTccLj2Kg4fKaaap9p1d2NOu43SpHkpv+lF++GBwpM?= =?us-ascii?Q?o8soBcJ/qYF1SJn9KmOGjZ6oQoNyFokckm3W3+0AGogGD/oiA8LotH7ARufO?= =?us-ascii?Q?y2ESPvyIQ5rFi+hSUy7kkBT8NM8YOSWAj90s/0LTOnfjSo7qDN9b5MT7/Q8V?= =?us-ascii?Q?lQpeb+KGpbMuO2can/OC6LNWG+xq7nrTd6rf0qA5ft844RHPMcXjNoIbAO+e?= =?us-ascii?Q?R0rR7P4FDbBsITwJyvXKwE1O19Ln3QJlqbrKRgUsTbMTE0mZ2LNoOhQ+O1BI?= =?us-ascii?Q?qULzPHMC0tq+O0B0HiJKcHMNEsqka7/WEv0r9ATePX1MH0Vt4FMbRBdE0orA?= =?us-ascii?Q?JvBKVP3GIwYNAOoW2wE/W9IJbgfevKCBnwmzv0LpVVgPQ4DstWdyNcm2HcWF?= =?us-ascii?Q?4fwIC8fn1RxAnjlE2yZg+EUNPZHIjs4EY4njD/Q2y3g=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b48b447b-8494-4010-dd06-08d8b4262530
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jan 2021 22:38:39.8351 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: VUzVLw4qP/1cOYc9io38HnTNzNlX/XP2gl9z68qG+9nhUq61fLfoZoMZetQ2O5tbUsp/vtyuo+r+62QyvLwSXfRF2EU7QduIxJSkLbX2zMU=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4563
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/iwkZathomZe9VACWuw8g3i9P8TY>
Subject: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 22:38:44 -0000

Hi Russ,

TL;DR: it would be great if this draft included a PBKDF2-based MAC (we sugg=
est PBMAC1 defined in RFC 8018). We also have a few general nit-picks about=
 the draft.


PBKDF2-based MAC
---------------
In draft-ietf-lamps-crmf-update-algs you are updating the underlying primit=
ives inside 4211's id-PasswordBasedMac, but we note that the overall algori=
thm is still PBKDF1-like, so in effect your draft is encouraging use of PBK=
DF1-SHA256-MAC or PBKDF1-AES-GMAC. This came up for us while going through =
a government crypto audit and having a FIPS-compliant PBKDF2-MAC in CMP wou=
ld have made the audit easier.

For backwards compatibility reasons you probably need to leave the PBKDF1-b=
ased 4211 id-PasswordBasedMac algorithm but with updated internal algs as y=
ou've done, but can you also offer as an alternative the PBKDF2-based RFC 8=
018 PBMAC1? I think we're asking that in the ASN.1:

```
PKMACValue ::=3D SEQUENCE {
algId  AlgorithmIdentifier,
-- algorithm value shall be PasswordBasedMac {1 2 840 113533 7 66 13}
-- parameter value is PBMParameter
```
the comment "-- algorithm value shall be PasswordBasedMac {1 2 840 113533 7=
 66 13}" also allow PBMAC1, as well as the corresponding parameter value ty=
pe.


The text in section 4.1 is already more tolerant, but explicitly mentioning=
 (as a MAY) PBMAC1 as an alternative might make sense too:

```
algId identifies the algorithm used to compute the MAC value.  All
implementations MUST support id-PasswordBasedMAC.  The details on
this algorithm are presented in section 4.4.
```

We're working with Hendrik on draft-ietf-lamps-cmp-algorithms and it would =
be clean if we could reference PBMAC1 in your draft.




Other general comments
----------------------
1. Section 3.2 - The change is "All implementations MUST support SHA-256 [S=
HS].", which used to require SHA-1.  I don't know how this is typically don=
e, but should your draft provide guidance on whether SHA-1 MAC is still saf=
e to be used in backwards compatibility scenarios?


2. Section 3.3 - "A lower iteration count can be used, if automated generat=
ion produces shared secrets with high entropy".  We find the wording slight=
ly confusing; after several re-reads we think you mean "lower than 10,000",=
 but someone doing a quick read might interpret "lower than 100". What is y=
our intent here?

3. Section 3.4 - There is a typo in "When this The algorithm identifier is =
used" ("The" should be removed)

4. Section 5 - "Therefore, the entropy of the password is crucial for the s=
ecurity of password-based MAC function." should be "of the password-based M=
AC function." ("the" missing)

5. You're copying the GMACParameters ASN.1 from your draft-ietf-lamps-cms-a=
es-gmac-alg, including the recommendation to use 12 bytes as default GMAC t=
ag length. If at some point the recommendation changes to a larger value th=
at would mean both documents need to be updated. Maybe better to leave the =
recommendation out of this draft and only reference the aes-gmac-alg draft?=
=20

5a. Which brings us to a question about draft-ietf-lamps-cms-aes-gmac-alg; =
where did the recommendation for a 12 byte GMAC tag come from? Is that supp=
orted by the referenced standards (NIST) or by an IRTF recommendation?

---
Mike Ounsworth
Software Security Architect, Entrust


From nobody Sat Jan  9 09:33:17 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFE623A13C1 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 09:33:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 82GKjHTPcbLq for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 09:33:12 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45A6B3A10DC for <spasm@ietf.org>; Sat,  9 Jan 2021 09:33:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 9AC17300BC5 for <spasm@ietf.org>; Sat,  9 Jan 2021 12:33:09 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 8cCiyWb0ggCR for <spasm@ietf.org>; Sat,  9 Jan 2021 12:33:07 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 9965C300ADB; Sat,  9 Jan 2021 12:33:07 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com>
Date: Sat, 9 Jan 2021 12:33:08 -0500
Cc: LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com>
To: "Mike Ounsworth (Mike.Ounsworth@entrustdatacard.com)" <Mike.Ounsworth@entrustdatacard.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/TlK2664Px4ZsySxTergvHWL5N2M>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 17:33:16 -0000

Mike:

Thanks for the review and thoughtful comments.

> TL;DR: it would be great if this draft included a PBKDF2-based MAC (we =
suggest PBMAC1 defined in RFC 8018). We also have a few general =
nit-picks about the draft.

I think this is a good idea.  Before I add it, I would like to know =
whether others agree or disagree.  More below.

> PBKDF2-based MAC
> ---------------
> In draft-ietf-lamps-crmf-update-algs you are updating the underlying =
primitives inside 4211's id-PasswordBasedMac, but we note that the =
overall algorithm is still PBKDF1-like, so in effect your draft is =
encouraging use of PBKDF1-SHA256-MAC or PBKDF1-AES-GMAC. This came up =
for us while going through a government crypto audit and having a =
FIPS-compliant PBKDF2-MAC in CMP would have made the audit easier.
>=20
> For backwards compatibility reasons you probably need to leave the =
PBKDF1-based 4211 id-PasswordBasedMac algorithm but with updated =
internal algs as you've done, but can you also offer as an alternative =
the PBKDF2-based RFC 8018 PBMAC1? I think we're asking that in the =
ASN.1:
>=20
> ```
> PKMACValue ::=3D SEQUENCE {
> algId  AlgorithmIdentifier,
> -- algorithm value shall be PasswordBasedMac {1 2 840 113533 7 66 13}
> -- parameter value is PBMParameter
> ```
> the comment "-- algorithm value shall be PasswordBasedMac {1 2 840 =
113533 7 66 13}" also allow PBMAC1, as well as the corresponding =
parameter value type.
>=20
>=20
> The text in section 4.1 is already more tolerant, but explicitly =
mentioning (as a MAY) PBMAC1 as an alternative might make sense too:
>=20
> ```
> algId identifies the algorithm used to compute the MAC value.  All
> implementations MUST support id-PasswordBasedMAC.  The details on
> this algorithm are presented in section 4.4.
> ```
>=20
> We're working with Hendrik on draft-ietf-lamps-cmp-algorithms and it =
would be clean if we could reference PBMAC1 in your draft.

If the LAMPS WG agree with this approach, I would suggest an update to =
section 4.1:

OLD

      algId identifies the algorithm used to compute the MAC value.  All
      implementations MUST support id-PasswordBasedMAC.  The details on
      this algorithm are presented in section 4.4

NEW

      algId identifies the algorithm used to compute the MAC value.  All
      implementations MUST support id-PasswordBasedMAC as
      presented in section 4.4.  All implementations MAY also support
      PBMAC1 presented in Section 7.1 of [RFC8018].


> Other general comments
> ----------------------
> 1. Section 3.2 - The change is "All implementations MUST support =
SHA-256 [SHS].", which used to require SHA-1.  I don't know how this is =
typically done, but should your draft provide guidance on whether SHA-1 =
MAC is still safe to be used in backwards compatibility scenarios?

I'd rather not see anything about SHA-1.  The situation for Certificate =
Request Message Format (CRMF) is not like S/MIME.  By that I mean, one =
will not need to process a CRMF message many years later from an archive =
folder.  A CRMF message should not need to be validated after the =
requested certificate is issued.

> 2. Section 3.3 - "A lower iteration count can be used, if automated =
generation produces shared secrets with high entropy".  We find the =
wording slightly confusing; after several re-reads we think you mean =
"lower than 10,000", but someone doing a quick read might interpret =
"lower than 100". What is your intent here?

I suggest:  As part of that tradeoff, an iteration count smaller than =
10,000 can be used when automated generation produces shared secrets =
with high entropy.

> 3. Section 3.4 - There is a typo in "When this The algorithm =
identifier is used" ("The" should be removed)

Thanks.  I'll fix it.

> 4. Section 5 - "Therefore, the entropy of the password is crucial for =
the security of password-based MAC function." should be "of the =
password-based MAC function." ("the" missing)

Thanks.  I'll fix it.

> 5. You're copying the GMACParameters ASN.1 from your =
draft-ietf-lamps-cms-aes-gmac-alg, including the recommendation to use =
12 bytes as default GMAC tag length. If at some point the recommendation =
changes to a larger value that would mean both documents need to be =
updated. Maybe better to leave the recommendation out of this draft and =
only reference the aes-gmac-alg draft?=20

Okay.

> 5a. Which brings us to a question about =
draft-ietf-lamps-cms-aes-gmac-alg; where did the recommendation for a 12 =
byte GMAC tag come from? Is that supported by the referenced standards =
(NIST) or by an IRTF recommendation?

This is for alignment with RFC 5084.  I was asked this so often that I =
added this information to the Implementation Considerations section of =
draft-ietf-lamps-cms-aes-gmac-alg.

Russ


From nobody Sat Jan  9 10:23:37 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0533A13F3 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 10:23:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3rBJXb-5OVp for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 10:23:34 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A25CF3A1190 for <spasm@ietf.org>; Sat,  9 Jan 2021 10:23:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 0E822300BC5 for <spasm@ietf.org>; Sat,  9 Jan 2021 13:23:32 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ijySTvIesCW9 for <spasm@ietf.org>; Sat,  9 Jan 2021 13:23:30 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 865E7300AA3 for <spasm@ietf.org>; Sat,  9 Jan 2021 13:23:30 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Message-Id: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com>
Date: Sat, 9 Jan 2021 13:23:31 -0500
To: LAMPS <spasm@ietf.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/iqrppVhu2XzIvf8dXN_5W6yNrqw>
Subject: [lamps] DRAFT Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 18:23:36 -0000

I assume that everyone saw the note from the IAB Chair, Mirja =
K=C3=BChlewind.  I suggest that the LAMPS WG ask the IAB to send the =
following liaison statement.  We're asking the IAB to do this because =
the IETF does not have a liaison relationship with ISO/TC 154.  Please =
review and comment.

Russ

=3D =3D =3D =3D =3D =3D =3D =3D =3D

FROM: IAB
TO: ISO/TC 154

The Internet Architecture Board would like to make sure that you are =
aware of the recent work by the at IETF LAMPS Working group =
(https://tools.ietf.org/wg/lamps/) that lead to RFC 8954 =
(https://www.rfc-editor..org/rfc/rfc8954.txt) that updates RFC 6960 =
(https://www.rfc-editor.org/rfc/rfc6960.txt). RFC 8954 limits the size =
of the OCSP Nonce extension to 32 octets to make the OCSP transactions =
more secure.=20

We understand that RFC 8954 may have a conflict with the way OCSP Nonce =
extension is proposed to be used in ISO 14533-4 and perhaps some other =
work which we are not aware of. =20

We had a discussion about the use case in the LAMPS working group =
recently.  Based on how the OCSP nonce extension is used in the =
industry, it was recommended that a new OCSP extension should be used =
for the purpose of capturing OCSP response for long term validation of =
the signed documents.

We recognize that the IETF does not have a liaison relationship with =
ISO/TC 154; however, the IETF LAMPS working group is willing to work =
with you to resolve this conflict in the best possible way.=


From nobody Sat Jan  9 10:26:15 2021
Return-Path: <rsalz@akamai.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A21723A11A2 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 10:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4_aFm96LDFO4 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 10:26:12 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0943A11A0 for <spasm@ietf.org>; Sat,  9 Jan 2021 10:26:12 -0800 (PST)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 109IEM8T007517; Sat, 9 Jan 2021 18:26:11 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=eFRXSNG14xJ9eRLgPEv4SplUxG0+PoqR9mrnIQ3gMao=; b=YhsTk69MIbGFVGG+P+w8pheMw9sryoeyHvdMIUcIKCPwPjt63Gz/WaPLK+A5PdCDOu9n Lb4fFMBdyK8E6NTE6EhLH7DKVrulTUY5TgH1thktYGgIegPcxhVsV8d8LXlR7ojB6R9Z KV0nIlXSbPzDi6V4z2buvGmhtuVh/47LlxoCfLwjRsn51jwKoQKOAvA+sEr258YQjkou 1wKtZbbIRGG3urPqrqzKUVosomex5ojWA1xYtFWRq4jDlNaBVzZcHxukNO8nLBmlJWMG xX9kW2dxxNjJn/+9KN+F18mKEH9JhsIWDueFs0fUqjONsJCwQW7bmEWFj3ZlolYH+RmT Zg== 
Received: from prod-mail-ppoint3 (a72-247-45-31.deploy.static.akamaitechnologies.com [72.247.45.31] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 35y5h5qj28-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 18:26:11 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 109IIwNS031591; Sat, 9 Jan 2021 13:26:10 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.30]) by prod-mail-ppoint3.akamai.com with ESMTP id 35y8q2jqv5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 13:26:10 -0500
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag3mb5.msg.corp.akamai.com (172.27.123.55) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 9 Jan 2021 13:26:09 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 9 Jan 2021 13:26:09 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Sat, 9 Jan 2021 13:26:09 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Russ Housley <housley@vigilsec.com>, LAMPS <spasm@ietf.org>
Thread-Topic: [lamps] DRAFT Liaison Statement to ISO/TC 154
Thread-Index: AQHW5rSQaG6NdpzoO0a8tF2eD7DtGqofnGIA
Date: Sat, 9 Jan 2021 18:26:08 +0000
Message-ID: <708A50BB-75E1-47A0-A4B4-F213719CCC0A@akamai.com>
References: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com>
In-Reply-To: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21010502
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <192F28442717F34CBAE10E5EBFAF0951@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_11:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 mlxscore=0 bulkscore=0 suspectscore=0 mlxlogscore=713 spamscore=0 phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101090122
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_11:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=628 adultscore=0 phishscore=0 suspectscore=0 impostorscore=0 spamscore=0 lowpriorityscore=0 bulkscore=0 priorityscore=1501 mlxscore=0 malwarescore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101090122
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.31) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint3
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/J60qAsnGxZkDePWiXP8Q-XP6xSQ>
Subject: Re: [lamps] DRAFT Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 18:26:14 -0000

PiAgICBJIGFzc3VtZSB0aGF0IGV2ZXJ5b25lIHNhdyB0aGUgbm90ZSBmcm9tIHRoZSBJQUIgQ2hh
aXIsIE1pcmphIEvDvGhsZXdpbmQuICBJIHN1Z2dlc3QgdGhhdCB0aGUgTEFNUFMgV0cgYXNrIHRo
ZSBJQUIgdG8gc2VuZCB0aGUgZm9sbG93aW5nIGxpYWlzb24gc3RhdGVtZW50LiAgV2UncmUgYXNr
aW5nIHRoZSBJQUIgdG8gZG8gdGhpcyBiZWNhdXNlIHRoZSBJRVRGIGRvZXMgbm90IGhhdmUgYSBs
aWFpc29uIHJlbGF0aW9uc2hpcCB3aXRoIElTTy9UQyAxNTQuICBQbGVhc2UgcmV2aWV3IGFuZCBj
b21tZW50Lg0KDQpMb29rcyBnb29kLCBzaGlwIGl0Lg0KIA0KDQo=


From nobody Sat Jan  9 10:51:43 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A453E3A1408 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 10:51:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XR7gXfMTuyyl for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 10:51:40 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58F1E3A13C3 for <spasm@ietf.org>; Sat,  9 Jan 2021 10:51:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 038B3300BC5 for <spasm@ietf.org>; Sat,  9 Jan 2021 13:51:38 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rU4IeWalN8j7 for <spasm@ietf.org>; Sat,  9 Jan 2021 13:51:36 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 5C2A5300AA3 for <spasm@ietf.org>; Sat,  9 Jan 2021 13:51:36 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Sat, 9 Jan 2021 13:51:37 -0500
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com>
Message-Id: <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/c7vZdwXImkdn7XXi3fDbOlUxPRY>
Subject: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 18:51:42 -0000

I gave this presentation at the NIST NCCoE Virtual Workshop on =
Considerations in Migrating to Post-Quantum Cryptographic Algorithms: =
https://www.nccoe.nist.gov/sites/default/files/10-Housley-NCCoE-Workshop-T=
ransition-to-PQC-Certificates.pdf

This short presentation still captures my view.  Are there people with a =
different view that would like time on the agenda at the LAMPS Interim =
on 28 Jan?  I would like to make sure that all point of view are heard.

Russ


From nobody Sat Jan  9 10:57:30 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB91C3A1414 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 10:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aIGddrVyQFhv for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 10:57:25 -0800 (PST)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2114.outbound.protection.outlook.com [40.107.243.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9900A3A1413 for <spasm@ietf.org>; Sat,  9 Jan 2021 10:57:25 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Pnn0Qdvoolume2oeQGjyLNljyFs4bciF63eqT8j/YQt4bIPviopeJKLsltERfHmEpzsG+UaFTsd6xcl6cc4+i4U0gy5OfoUPcNg4e2Spo1j39br+vQK7VwYr7moAFYie1/lplm6Hb2KrfsPGYP1PCQT85qiQrQdhqFXcjbVJ1uFvoQhoqRdF7awXBMET/CnGiEkH48AGowU2nEfhOJXAYInEuGTWav796TxKIlY359AB4tgEjFIVH2IE9Suo+8bwpe5PSV6F0t8ZuHDcM8eUDD1pZ6YARehSU0uWUdrvw+0fPDpeR/wkQWoiEXgxL4Hhy+TnI2WLAqKKDh2wqLb4OA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rtRWLVwlvudq2YxOw/rhJO7R0fyCYIkdE3Uc/eOSnQA=; b=WGpA+HaS3FPgv1Xlrm/zxUNI0Ad+GsfD+R4fG8nDznkXtQRrJjVrigN3FJe0IILJkC94ZgjJK6CLFYtI41pgD4dcZECYAD70u2OYApOfoFm3RWCY+6rNuYvCwrjasNm6T/ZCGvjFgqQcN1X77Don6R7E0wiZQHtBFs85ffssPygtCDBKhTOpjW9RFqIihaSQoN/jYPgj5lcliNEa3iNIqr7L/NQKnTFQXACh0q0ozP/dxo/P/8ueiZkfo100Wr008nttFsHUDXz7Z3EeGuzJNS64wktE8xMRBFmVSwRXzQuoPfTa8Kq6ZnS3wMr1lIUM2wXJ+gh5Rp4BG9pXMVe8Jw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rtRWLVwlvudq2YxOw/rhJO7R0fyCYIkdE3Uc/eOSnQA=; b=cSaXb/D9m6/jhReBUpOs1GGPk5uERkqMWfT0Zrw57Yrjho0vqV16Rq8Iz5leSr/e+Sl2aIA95iwrkW3+azBFQtBZcYH7fM5iCclNY08n7sdOeffRbA4B0sw67jXJWcGAYqCZYUMHwigCUTb49ylzNg11ZYwqnBHbmE6tH7hIvC/ER7pmYpLXVx3qGC76L1Oc34EIZXaKYQjyrVFUwdWWEs3egqRf6y98wDxlI0XusfhIVSFjLGWJVZ/sl7uu9EzFoWu1G/ln8V9FB/79+kFQN460q4ABpvnYQlkmIJWI6uSbl6h99UNxhsRFw8WPD7YIQP30vA84cpmM8X/1ddIYIQ==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB2780.namprd11.prod.outlook.com (2603:10b6:5:c8::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Sat, 9 Jan 2021 18:57:21 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.006; Sat, 9 Jan 2021 18:57:20 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Russ Housley <housley@vigilsec.com>
CC: LAMPS <spasm@ietf.org>
Thread-Topic: [EXTERNAL]Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
Thread-Index: AdbmDrJ8XClSyQZRTI2kM/VC377vqgAnswAAAALKW/A=
Date: Sat, 9 Jan 2021 18:57:20 +0000
Message-ID: <DM6PR11MB43802F7D66D0FB3EB4156AD29FAD0@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com>
In-Reply-To: <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [72.139.201.94]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0bcb7c74-c8a8-45de-88b6-08d8b4d064b8
x-ms-traffictypediagnostic: DM6PR11MB2780:
x-microsoft-antispam-prvs: <DM6PR11MB2780FAC23CF4035D2DADAAAC9FAD0@DM6PR11MB2780.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5kP9BeEoj09LJIZ02S0juErpUz57opvh1ZsAmF1X6wmwpEoT7+/7eWDJdY2fPwJveAb4p1E0A8CCDNQQXtGbObOxstimlcWVXnMv+BpcKLydXKXFlaoJnVdx2tc+neFCLOw+WQf4Qt6jBFuKRKzWl2pjaMb2JbzYaCqQiByJuQkaFCqf/RANt0lWK1k3k2o1ROP6gmOdO3Np2UTV9UVcVtwB9waPOwoJHD8sqWn5xCJ3i5qAFwEM5/7AIsXPxXLcg8ryTFHfFYo+jx5fzHZW2ShE4HD27IXyq0mgbiSP+AbFnyfolGm+zZAxoZV0eUD+yoJO46a989cm9n4Sf6SaACNR0gyfZJKDPiRfyVzZTFLgIVFIPeCRnodlNKe4JeT4wtWcBPA75RfWOMzk5IVyqdkmnFo5Jh1WAH62As4FWrFVWJZJidXZ8TTC5x/Y2tgmA/PFEAyOje9WWvHgETd9Kg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(346002)(39850400004)(376002)(396003)(366004)(2906002)(66476007)(316002)(8676002)(15650500001)(8936002)(83380400001)(6506007)(4326008)(6916009)(186003)(966005)(53546011)(478600001)(33656002)(26005)(86362001)(71200400001)(7696005)(55016002)(5660300002)(9686003)(66946007)(66556008)(64756008)(66446008)(52536014)(76116006); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?YoqjXNQjFCQG3upn8DsxqyV0+VeJ2lAXfk2cyX/mmmrlnkZcJ0KprL+MNkr/?= =?us-ascii?Q?NSRANDfZ/x58DaMMfxrnrs4ha39UM9RGbvQZnbJMe0IdKOTywt8ZPN1gmtRU?= =?us-ascii?Q?EhDItAUKdmnXXOk4e8Co5z8J3y2er1xarEjU05/cF4rlY5mcMOqT44RoRvb5?= =?us-ascii?Q?vxAD4osxlJctdSG/CVJqYOm15NQodYj5wfA/X5y7iAk351E1tyXPwH3OFuYg?= =?us-ascii?Q?iTbwdTk2uDzBAEBwev6oG2vQsAG6ThHRIOLPhOUP3dzjFQOwX8rXrg98fyUE?= =?us-ascii?Q?N+kbRr8kYp7Mz7sztsST/zk3Yw2cSY+0lV7oixeWFDb8FkllnoOGIjNbLcD1?= =?us-ascii?Q?QNCLO80a8hRvLwIKLlRkO5aplBhH3PoU4c2Zpr+TkANxDStEfDcOLc676pG3?= =?us-ascii?Q?sEu0AqqdWsyRoI5FOuPTh0YykjBheTk230JVvCs6OSolNtA7dcjd7Iy5+Z3l?= =?us-ascii?Q?VwZqwt6D5GT8ehcm3+SnlyS5HYRIqs1GmB0n8C1nQiu++8lUfp5ZsIqjVnS0?= =?us-ascii?Q?WyHFYwvPpySt+aO/rLLEbn9hut9tF7Epgw7IdYuqHGC6Fu1JzatUbKeP6Hck?= =?us-ascii?Q?XLXK/HMDQFuh8g0+P6+uxnX9v8Usu1K/w8k4/RidLY1zoYt/1tDgdq4UBQLW?= =?us-ascii?Q?rDI5jz4Y/srWsJpEWd0eimosmChmvQhvMa38XRKMC/ASG3Y+UDnDfSIhlxf6?= =?us-ascii?Q?mQEfpXUiIp3yxjtrKLsKuZLl23R09KWeylqCJIV6NQvsiJM4ruALg8jqqdg8?= =?us-ascii?Q?wBVGJ1Z9SvEeOwpKO82lXBOzIeGtL2G/7OEtRIYmG2fL1tZeCbpfNqQ8mNvX?= =?us-ascii?Q?MhR9Okb1NafeedgGAvwVgI2Al05AftZPqjC4inFDegUFmflL5Ifr0a8gLKes?= =?us-ascii?Q?fv9mO6PYtmQWjQH5OCLzIR9Oe6sCJ07xbeWFnNxKiwsMg3H7Lk7XChynvnpH?= =?us-ascii?Q?ok2pzfkueaen7n213F/60eJRh1IJq0RBYduSIpxHF7Q=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0bcb7c74-c8a8-45de-88b6-08d8b4d064b8
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2021 18:57:20.6648 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: eL4D6bCxTJzLsDjxagF+3va6uIkedw8rmlIGoZ8/S9KMJG0RnlitUElwx+QlkzQytpSIoxk61EF3hXZWZGIC7xryDxIziQtf61cQ0/WCxNg=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB2780
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/oOo6Kq1DETtGOZHV44ei-khcdvY>
Subject: Re: [lamps] [EXTERNAL]Re: Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 18:57:28 -0000

Thanks Russ!

I think those changes fully address our concerns.


One response:

>> 5a. Which brings us to a question about draft-ietf-lamps-cms-aes-gmac-al=
g; where did the recommendation for a 12 byte GMAC tag come from? Is that s=
upported by the referenced standards (NIST) or by an IRTF recommendation?

>This is for alignment with RFC 5084.  I was asked this so often that I add=
ed this information to the Implementation Considerations section of draft-i=
etf-lamps-cms-aes-gmac-alg.

Gotcha, thanks. Could you add that to your cms-aes-gmac draft just for the =
sake of an easy-to-follow citation chain? (I think 5084 is not currently in=
 the references list)

---
Mike Ounsworth

-----Original Message-----
From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
Sent: January 9, 2021 11:33 AM
To: Mike Ounsworth <Mike.Ounsworth@entrust.com>
Cc: LAMPS <spasm@ietf.org>
Subject: [EXTERNAL]Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-=
algs-02

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the =
content is safe.

Mike:

Thanks for the review and thoughtful comments.

> TL;DR: it would be great if this draft included a PBKDF2-based MAC (we su=
ggest PBMAC1 defined in RFC 8018). We also have a few general nit-picks abo=
ut the draft.

I think this is a good idea.  Before I add it, I would like to know whether=
 others agree or disagree.  More below.

> PBKDF2-based MAC
> ---------------
> In draft-ietf-lamps-crmf-update-algs you are updating the underlying prim=
itives inside 4211's id-PasswordBasedMac, but we note that the overall algo=
rithm is still PBKDF1-like, so in effect your draft is encouraging use of P=
BKDF1-SHA256-MAC or PBKDF1-AES-GMAC. This came up for us while going throug=
h a government crypto audit and having a FIPS-compliant PBKDF2-MAC in CMP w=
ould have made the audit easier.
>=20
> For backwards compatibility reasons you probably need to leave the PBKDF1=
-based 4211 id-PasswordBasedMac algorithm but with updated internal algs as=
 you've done, but can you also offer as an alternative the PBKDF2-based RFC=
 8018 PBMAC1? I think we're asking that in the ASN.1:
>=20
> ```
> PKMACValue ::=3D SEQUENCE {
> algId  AlgorithmIdentifier,
> -- algorithm value shall be PasswordBasedMac {1 2 840 113533 7 66 13}
> -- parameter value is PBMParameter
> ```
> the comment "-- algorithm value shall be PasswordBasedMac {1 2 840 113533=
 7 66 13}" also allow PBMAC1, as well as the corresponding parameter value =
type.
>=20
>=20
> The text in section 4.1 is already more tolerant, but explicitly mentioni=
ng (as a MAY) PBMAC1 as an alternative might make sense too:
>=20
> ```
> algId identifies the algorithm used to compute the MAC value.  All=20
> implementations MUST support id-PasswordBasedMAC.  The details on this=20
> algorithm are presented in section 4.4.
> ```
>=20
> We're working with Hendrik on draft-ietf-lamps-cmp-algorithms and it woul=
d be clean if we could reference PBMAC1 in your draft.

If the LAMPS WG agree with this approach, I would suggest an update to sect=
ion 4.1:

OLD

      algId identifies the algorithm used to compute the MAC value.  All
      implementations MUST support id-PasswordBasedMAC.  The details on
      this algorithm are presented in section 4.4

NEW

      algId identifies the algorithm used to compute the MAC value.  All
      implementations MUST support id-PasswordBasedMAC as
      presented in section 4.4.  All implementations MAY also support
      PBMAC1 presented in Section 7.1 of [RFC8018].


> Other general comments
> ----------------------
> 1. Section 3.2 - The change is "All implementations MUST support SHA-256 =
[SHS].", which used to require SHA-1.  I don't know how this is typically d=
one, but should your draft provide guidance on whether SHA-1 MAC is still s=
afe to be used in backwards compatibility scenarios?

I'd rather not see anything about SHA-1.  The situation for Certificate Req=
uest Message Format (CRMF) is not like S/MIME.  By that I mean, one will no=
t need to process a CRMF message many years later from an archive folder.  =
A CRMF message should not need to be validated after the requested certific=
ate is issued.

> 2. Section 3.3 - "A lower iteration count can be used, if automated gener=
ation produces shared secrets with high entropy".  We find the wording slig=
htly confusing; after several re-reads we think you mean "lower than 10,000=
", but someone doing a quick read might interpret "lower than 100". What is=
 your intent here?

I suggest:  As part of that tradeoff, an iteration count smaller than 10,00=
0 can be used when automated generation produces shared secrets with high e=
ntropy.

> 3. Section 3.4 - There is a typo in "When this The algorithm=20
> identifier is used" ("The" should be removed)

Thanks.  I'll fix it.

> 4. Section 5 - "Therefore, the entropy of the password is crucial for=20
> the security of password-based MAC function." should be "of the=20
> password-based MAC function." ("the" missing)

Thanks.  I'll fix it.

> 5. You're copying the GMACParameters ASN.1 from your draft-ietf-lamps-cms=
-aes-gmac-alg, including the recommendation to use 12 bytes as default GMAC=
 tag length. If at some point the recommendation changes to a larger value =
that would mean both documents need to be updated. Maybe better to leave th=
e recommendation out of this draft and only reference the aes-gmac-alg draf=
t?=20

Okay.

> 5a. Which brings us to a question about draft-ietf-lamps-cms-aes-gmac-alg=
; where did the recommendation for a 12 byte GMAC tag come from? Is that su=
pported by the referenced standards (NIST) or by an IRTF recommendation?

This is for alignment with RFC 5084.  I was asked this so often that I adde=
d this information to the Implementation Considerations section of draft-ie=
tf-lamps-cms-aes-gmac-alg.

Russ

_______________________________________________
Spasm mailing list
Spasm@ietf.org
https://www.ietf.org/mailman/listinfo/spasm


From nobody Sat Jan  9 14:03:25 2021
Return-Path: <rsalz@akamai.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC7533A0365 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 14:03:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53G06lYFRulY for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 14:03:22 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C75F73A033F for <spasm@ietf.org>; Sat,  9 Jan 2021 14:03:22 -0800 (PST)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 109M0QEr028173; Sat, 9 Jan 2021 22:03:14 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=OlaqS5lXKW4EI7rRBYnk0OemDJguJIbQ4cHFWAYKMAU=; b=MctkYSpUPLpgQpDc3aD//ueypRdLOdKTeWxNygQSNWBe0fGxgAtQMfnkOg8rZ2p6I3GY OGdi8HsCnW/X4DO0EoRmhaNDwlaQmxxj+XTEHmKFzgvHBfFuyzxSsWOLVjkklitqYCux amnhZxdcrna32OxozexLih8oSvfaZgKHCG+i2WALvl8y4OePBsXIwgCH95GA5bluoXkK F4Bbi3EddbvHjoYJWUNTAWcWvWyvuio31igBiS0LiqZVCt7NH8Tg9Re8WW1I2k8RqucX yWW0itDZ6N7SJGvAVzIyBRWdTnnL5ZATs99hTmTzZUQf0Yip4ImAjCxxLMG036KykVwD pg== 
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 35y5h5wwg4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 22:03:14 +0000
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 109LZ71p014109; Sat, 9 Jan 2021 14:03:13 -0800
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint5.akamai.com with ESMTP id 35ybbe0uex-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 14:03:13 -0800
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 9 Jan 2021 17:03:11 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 9 Jan 2021 17:03:11 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Sat, 9 Jan 2021 17:03:11 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Russ Housley <housley@vigilsec.com>, "Mike Ounsworth (Mike.Ounsworth@entrustdatacard.com)" <Mike.Ounsworth@entrustdatacard.com>
CC: LAMPS <spasm@ietf.org>
Thread-Topic: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
Thread-Index: AdbmDrJ8XClSyQZRTI2kM/VC377vqgAyLTYA///3oAA=
Date: Sat, 9 Jan 2021 22:03:10 +0000
Message-ID: <AC40C703-8619-40D1-9076-C26404645409@akamai.com>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com>
In-Reply-To: <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21010502
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <24128C797A8CE4439CBA859D5C9D55C3@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_13:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 malwarescore=0 mlxscore=0 mlxlogscore=814 suspectscore=0 spamscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101090143
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_13:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=736 adultscore=0 phishscore=0 suspectscore=0 impostorscore=0 spamscore=0 lowpriorityscore=0 bulkscore=0 priorityscore=1501 mlxscore=0 malwarescore=0 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101090145
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.60) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint5
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/nWPv0yEt_M9YVmHPyvlIJEUz-28>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 22:03:24 -0000

PiAgICBJIHRoaW5rIHRoaXMgaXMgYSBnb29kIGlkZWEuICBCZWZvcmUgSSBhZGQgaXQsIEkgd291
bGQgbGlrZSB0byBrbm93IHdoZXRoZXIgb3RoZXJzIGFncmVlIG9yIGRpc2FncmVlLiAgTW9yZSBi
ZWxvdy4NCg0KSSBhZ3JlZSB3aXRoIHlvdXIgY2hhbmdlcy4NCg0KPiAgICBJJ2QgcmF0aGVyIG5v
dCBzZWUgYW55dGhpbmcgYWJvdXQgU0hBLTEuICBUaGUgc2l0dWF0aW9uIGZvciBDZXJ0aWZpY2F0
ZSBSZXF1ZXN0IE1lc3NhZ2UgRm9ybWF0IChDUk1GKSBpcyBub3QgbGlrZSBTL01JTUUuICBCeSB0
aGF0IEkgbWVhbiwgb25lIHdpbGwgbm90IG5lZWQgdG8gcHJvY2VzcyBhIENSTUYgbWVzc2FnZSBt
YW55IHllYXJzIGxhdGVyIGZyb20gYW4gYXJjaGl2ZSBmb2xkZXIuICBBIENSTUYgbWVzc2FnZSBz
aG91bGQgbm90IG5lZWQgdG8gYmUgdmFsaWRhdGVkIGFmdGVyIHRoZSByZXF1ZXN0ZWQgY2VydGlm
aWNhdGUgaXMgaXNzdWVkLg0KDQpTdHJvbmdseSBhZ3JlZS4gIA0KIA0KDQo=


From nobody Sat Jan  9 15:37:51 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6323A0AD3 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 15:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M99hraylYobd for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 15:37:49 -0800 (PST)
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10on2100.outbound.protection.outlook.com [40.107.93.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C4C83A0AD5 for <spasm@ietf.org>; Sat,  9 Jan 2021 15:37:49 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=g17f+FQTuAKhQ+qIE9VU8MnWnDm3KheAMMVY/CS8O2oH5IjA/EZ2H1luAhUb8BdJ6LUrpuYORaAeLDO4Kj5+sI8P0q3oFVAdlDO15stZJUzeeTHvQL8sD3Tuhs/Uj15HXSyImtQNnkgWsAHDnaoPtluqEjUiFSJW10NNgMqcCKUeuVLe2vfg1YNYBynmxNCIfKMFw4uv38o657zEgZZdxBCFFhshaaXQBQqwIBP2NfnVQg3SOGaI14AGX14m9yIJ/cNy07rYdB1jbi3XcWTUHGhuQGMUSoHnmfsJk++6nKtSXARtFcXGmow1MFNL26Mgi1yIxqckQYYT/oRMsoHYuQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WivNPuRhhthq79R2QDRpn3i0+a9dFyv1CZ79d9ywijs=; b=fbS2Tsj6mmHCAElN65SyDuCu5uRKy1Vsq850BeGXspUy6vHt74S3NcAhrTpsbcL5d3L1V9nhv0fy16mF6zMtRIa94+H3AhdOcw92vWokIW0R6dC4d/QOnmJPCKBVUEPFsuzv+plWTY5siXgusAq3VO6BlqdN6oYsqKL83e66OQeudNVgW1zm0fW018wdIpG+6VuzZ36uARevcltw99kn5NRju2eLbMx83+N2eR1vaHhKOa9XeMDcbrrjSi6HP9YiBHGtmevXHEA7ZCnPVBj6zwAmv2bAoyIvYaRl90dBLCuWg/gCCy8woJeA6B929EW5dvNy36d+KLoIVAzrcC5MMw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WivNPuRhhthq79R2QDRpn3i0+a9dFyv1CZ79d9ywijs=; b=QB42Cr15OJFbDtvOrC3rj+Vw5dn+d+aRKopG5uzdQSnhGGniLHZss1kmj7DOyOUuAOaknb0Q/EDiX+tLyKO/knnvDWCYdSO8S+vPnqKUDR9I2v73kYfAzv6rOg7iO2hPj2+8Pw53F5toLoWBpjNIVxNR5+Ws+C2Gf396vb+eaRE1BRFjMgd+dnxeeV/zQC0mCwEyWnBNfdo8NuPTyK9+vLqOYVD8Hwmq6pNYO3lkmwvcXwNLn5/9v1AL92iVbmtYOcSvB5/L5RH7Ea2Mc32U7KuZdXwcT38/gedRCUW3DL7YMgm6Ad5CVM29/OATrHPv94KUlu2vXEjs5EzlwGsG/w==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB4284.namprd11.prod.outlook.com (2603:10b6:5:205::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Sat, 9 Jan 2021 23:37:46 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.006; Sat, 9 Jan 2021 23:37:46 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: "Salz, Rich" <rsalz@akamai.com>, Russ Housley <housley@vigilsec.com>
CC: LAMPS <spasm@ietf.org>
Thread-Topic: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
Thread-Index: AQHW5tNDoItPwZNbNkyEum8gmM3u0aof8ULg
Date: Sat, 9 Jan 2021 23:37:46 +0000
Message-ID: <DM6PR11MB43800A6F529075C037D62A939FAD0@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com> <AC40C703-8619-40D1-9076-C26404645409@akamai.com>
In-Reply-To: <AC40C703-8619-40D1-9076-C26404645409@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: akamai.com; dkim=none (message not signed) header.d=none;akamai.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [72.139.202.228]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f5806d8c-c634-44e6-12b1-08d8b4f79166
x-ms-traffictypediagnostic: DM6PR11MB4284:
x-microsoft-antispam-prvs: <DM6PR11MB42842295A9D9B16FC8DC46849FAD0@DM6PR11MB4284.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: xRYur+kjjoRwTCP5842B8OJqoZrZ41FJiQd1sTXIhgoBjpI7a48Ybcws6Tsu1gpWfz93vudP6YaHtRb3IO8KGthJq80kZvbtwNwawjKwhScxHBAUFBXkgN6ERLZv3htPKkJVzRGC+SshPB1rA7Jf7UXBFEMaDrnJogm8GYEMmpWUmDQ+H8+Fy/Q+BtEHAWLYWP57QnB39u8z7QvHOVMJ9nrQ4AMLSoLYrMsms7BCVl52LD82b14CFOcC4QstRALFwKLkBjNJ8DB7bEOGJlpjnctBq0DSnjusDUxUgdHG8/T3IB2QhQOFsPg/5awkBulD8h77HR6dQ1YJJn+R9P2wMtabK0kX7laQ0fc7pCDwYlLJERwUku7ei2SSo1147XyqUagtvwPPgCh19BHb5CWY+Q==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(39840400004)(346002)(396003)(376002)(366004)(86362001)(33656002)(7696005)(76116006)(5660300002)(66446008)(64756008)(66556008)(66476007)(66946007)(83380400001)(53546011)(6506007)(186003)(26005)(52536014)(2906002)(316002)(478600001)(110136005)(8676002)(9686003)(15650500001)(8936002)(4326008)(55016002)(71200400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?K2FSazFsMHcySFVINSs5SllzYk55N2hkcUVncnBzUjkrZ3B3VHJpWHdUTUNV?= =?utf-8?B?ZW5IZFdaMnErajNCTytMcnJINHFXek1vUFRPeFJzRjdmTmJReG1Fb2hWZGYx?= =?utf-8?B?YlBDb1ZnWUh3NXhMTit5Vk9kZm1NdlJWY1RLZUpjZGpIejRHZnFGUnZuRk5M?= =?utf-8?B?MWtacUlzbVZvb3JsNXBIcWJ5TlpKMU84L0JMZmpoWG9PSDRvNDJEczZtNzhh?= =?utf-8?B?cXlrNkJEMXhQS212cHFNa1lDYWdweStBU2FZM2crMTJlUDZJQk1wNm5IUmN0?= =?utf-8?B?V3Zjd01MTjE0OHR1NjN3L054SHB4VWYxaVFQR1VMNXRnM3lEdy94cDFFNU03?= =?utf-8?B?bkNKenA0Ync3dTAvcm91QWJobWhHRzZuZ2lyakhySHRQMEtFV29nUHVZMlkr?= =?utf-8?B?VklTT0JBbWg2WnczNllZeVJSL2dHSHlLelJhYWwzUHgxb3RMU1poNUhNYWNK?= =?utf-8?B?VDJ2ZVhlVUJKazBTNWFaYnVaNXhKbUtnNWtpVk1SN3JGamRTQytMTDNRVWly?= =?utf-8?B?ZUw2dTJUNnFQRzdqaUdrV25PL2FRckdMaUpKOEkvM3RJS2pCaU5VdU1SWGZ6?= =?utf-8?B?UFJoODJNNi9ucldxTUlSUS9xbFZjMVJrUlFqTDZnZFMxVGt4V0YzZFpTZjda?= =?utf-8?B?SU5NT2E1aWJsYzRvT09FRm9wdWhZWXRpbVJON2hVWmcvblQrNzB0V1VnaEdL?= =?utf-8?B?NjZsMThKTTJsR21aNldRb240M2l0bWpqcVg2dUN0V2NnOVVDNldRVmNUZW15?= =?utf-8?B?TDBEZitET2x3K0k0NXk5U0pxbUhwN3lIaVczZWZZNkMyY0k3akNDLzgvRVVW?= =?utf-8?B?Q1JXcXZzVHR6N2wveE12VzN5Q0xjNGZqdXcrZHVsL3p3NUNUQS9CSlZKZHY2?= =?utf-8?B?V3RSaTZlTElaTTFnYTdETDFtTmlZdk9ma01md0p1QU5GTGs4K3dHend1VzJq?= =?utf-8?B?Z3dSY3R3eC9GUG1IY1oxcEovWEc4VVNucmNlUTU5dFhENTc3SzBTT1lYaEtz?= =?utf-8?B?VzIyenpKdThDSkhnWmdYWE96SlR5amVoV2lScHIvUjNLRE83NFZKQ25lMS81?= =?utf-8?B?Tjd5VnRVU3NyMVNkNVo4SVAveXNkYXpCc2R6dk81UkJ2YzYwcDU3NzNBcVdo?= =?utf-8?B?SS9FU2txdXBPY2ZuZlA2VjlJVXpnQlBDOFQ1WEJpSjZ2bUlRc2tEV1VKSjZn?= =?utf-8?B?SlgyU0RacnZhaEtjTmVQcFNrVFpDV1oxZ0dkTGJRbkF1Nk1Vak1tWWwrbzdh?= =?utf-8?B?M3B5bmtUNVdlZWI2ZDNxUnhMZjB6M1JOc2RYWDcwa3RLT3RLTnVhUWJMMCtG?= =?utf-8?Q?LjJ/qYMsCWqSE=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f5806d8c-c634-44e6-12b1-08d8b4f79166
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2021 23:37:46.1763 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: EydFXPGYPigHrt1+ZNSYUfQN9+Jd1ELCrdHOTjyQByrAfuCxDLSsUkiIOuYnezpMMZtRVADcLneiAWSSRgmp2Uge+2cwOX/dSGb/kbTesac=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4284
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/HLLDzVjCj8IyaM8FYDf-OeWDR7g>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 23:37:51 -0000

Pj4gICAgSSdkIHJhdGhlciBub3Qgc2VlIGFueXRoaW5nIGFib3V0IFNIQS0xLiAgVGhlIHNpdHVh
dGlvbiBmb3IgQ2VydGlmaWNhdGUgUmVxdWVzdCBNZXNzYWdlIEZvcm1hdCAoQ1JNRikgaXMgbm90
IGxpa2UgUy9NSU1FLiAgQnkgdGhhdCBJIG1lYW4sIG9uZSB3aWxsIG5vdCBuZWVkIHRvIHByb2Nl
c3MgYSBDUk1GIG1lc3NhZ2UgbWFueSB5ZWFycyBsYXRlciBmcm9tIGFuIGFyY2hpdmUgZm9sZGVy
LiAgQSBDUk1GIG1lc3NhZ2Ugc2hvdWxkIG5vdCBuZWVkIHRvIGJlIHZhbGlkYXRlZCBhZnRlciB0
aGUgcmVxdWVzdGVkIGNlcnRpZmljYXRlIGlzIGlzc3VlZC4NCg0KPiBTdHJvbmdseSBhZ3JlZS4g
IA0KDQpXaGF0IGFib3V0IHNjZW5hcmlvcyB3aGVyZSB0aGUgQ0EgaXMgcmVjZWl2aW5nIGNlcnQg
cmVxcyBmcm9tIGxlZ2FjeSBjbGllbnRzIHRoYXQgYXJlIHN0aWxsIHVzaW5nIFNIQTE/IC4uLiBJ
IHN1cHBvc2UgeW91J3JlIG9wdGluZyB0byBzYXkgb3V0IG9mIHRoYXQgZGViYXRlIGFuZCBsZWF2
ZSB0aGUgZGVjaXNpb24gb2Ygd2hldGhlciBvciBub3QgdG8gcmVqZWN0IHVwIHRvIHRoZSBpbXBs
ZW1lbnRhdGlvbiAvIGNvbmZpZ3VyYXRpb24/DQoNCi0tLQ0KTWlrZSBPdW5zd29ydGgNCg0KLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFNhbHosIFJpY2ggPHJzYWx6QGFrYW1haS5j
b20+IA0KU2VudDogSmFudWFyeSA5LCAyMDIxIDQ6MDMgUE0NClRvOiBSdXNzIEhvdXNsZXkgPGhv
dXNsZXlAdmlnaWxzZWMuY29tPjsgTWlrZSBPdW5zd29ydGggPE1pa2UuT3Vuc3dvcnRoQGVudHJ1
c3QuY29tPg0KQ2M6IExBTVBTIDxzcGFzbUBpZXRmLm9yZz4NClN1YmplY3Q6IFtFWFRFUk5BTF1S
ZTogW2xhbXBzXSBNYWlsIHJlZ2FyZGluZyBkcmFmdC1pZXRmLWxhbXBzLWNybWYtdXBkYXRlLWFs
Z3MtMDINCg0KV0FSTklORzogVGhpcyBlbWFpbCBvcmlnaW5hdGVkIG91dHNpZGUgb2YgRW50cnVz
dC4NCkRPIE5PVCBDTElDSyBsaW5rcyBvciBhdHRhY2htZW50cyB1bmxlc3MgeW91IHRydXN0IHRo
ZSBzZW5kZXIgYW5kIGtub3cgdGhlIGNvbnRlbnQgaXMgc2FmZS4NCg0KPiAgICBJIHRoaW5rIHRo
aXMgaXMgYSBnb29kIGlkZWEuICBCZWZvcmUgSSBhZGQgaXQsIEkgd291bGQgbGlrZSB0byBrbm93
IHdoZXRoZXIgb3RoZXJzIGFncmVlIG9yIGRpc2FncmVlLiAgTW9yZSBiZWxvdy4NCg0KSSBhZ3Jl
ZSB3aXRoIHlvdXIgY2hhbmdlcy4NCg0KPiAgICBJJ2QgcmF0aGVyIG5vdCBzZWUgYW55dGhpbmcg
YWJvdXQgU0hBLTEuICBUaGUgc2l0dWF0aW9uIGZvciBDZXJ0aWZpY2F0ZSBSZXF1ZXN0IE1lc3Nh
Z2UgRm9ybWF0IChDUk1GKSBpcyBub3QgbGlrZSBTL01JTUUuICBCeSB0aGF0IEkgbWVhbiwgb25l
IHdpbGwgbm90IG5lZWQgdG8gcHJvY2VzcyBhIENSTUYgbWVzc2FnZSBtYW55IHllYXJzIGxhdGVy
IGZyb20gYW4gYXJjaGl2ZSBmb2xkZXIuICBBIENSTUYgbWVzc2FnZSBzaG91bGQgbm90IG5lZWQg
dG8gYmUgdmFsaWRhdGVkIGFmdGVyIHRoZSByZXF1ZXN0ZWQgY2VydGlmaWNhdGUgaXMgaXNzdWVk
Lg0KDQpTdHJvbmdseSBhZ3JlZS4gIA0KIA0KDQo=


From nobody Sat Jan  9 19:44:40 2021
Return-Path: <rsalz@akamai.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2363A0BDB for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 19:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQaENekiivLx for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 19:44:37 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CBD23A0BDA for <spasm@ietf.org>; Sat,  9 Jan 2021 19:44:37 -0800 (PST)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10A3ZlIg032738; Sun, 10 Jan 2021 03:44:34 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=hNjQ6i4g3QRF0TjhdNL/MOcJ1DW/dZVLxl5VOluPvjc=; b=NiiuqDiKPptvHUMAHBA0NNohZdMCLvwlov1uyRuLFFWAK3baL6OsA6yJ/1RpqbJc7MjQ FP1Y/HH6jZBsoZRoCrvTZkjNXjCqnnrHMlfHJI5UkZQcku+s9dsQR+8eUhoMFcjBOOez OKbsliHOyQ33sXyORYRqWrE7Ls21bF8Pe6m6b88xU5p0maRi69pczcy5x9xwjjP1OxE0 yfFViJGc0QRW1Xh6WJc9yIn/hotchTVpINF0TC86ngy6M747reBY1zYw2I3/YNONpULV hcqs3k4FFkn55WuvReN6rPykFCRwabCBL9rG4n7Xgr4m9RSf1UIq0/c+m+zctZidLuD4 aw== 
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 35y5egr3ju-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 10 Jan 2021 03:44:34 +0000
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 10A3ZDYG025421; Sat, 9 Jan 2021 22:44:34 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint1.akamai.com with ESMTP id 35y8q2shuc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 22:44:34 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 9 Jan 2021 22:44:33 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Sat, 9 Jan 2021 22:44:33 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Mike Ounsworth <Mike.Ounsworth@entrust.com>, Russ Housley <housley@vigilsec.com>
CC: LAMPS <spasm@ietf.org>
Thread-Topic: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
Thread-Index: AdbmDrJ8XClSyQZRTI2kM/VC377vqgAyLTYA///3oACAAG5AAP//8R4A
Date: Sun, 10 Jan 2021 03:44:32 +0000
Message-ID: <4BE67EDC-FBDC-4145-B81E-0BA396C48CDE@akamai.com>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com> <AC40C703-8619-40D1-9076-C26404645409@akamai.com> <DM6PR11MB43800A6F529075C037D62A939FAD0@DM6PR11MB4380.namprd11.prod.outlook.com>
In-Reply-To: <DM6PR11MB43800A6F529075C037D62A939FAD0@DM6PR11MB4380.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21010502
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E5B14C45E125304BB2FBE824253030CD@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_13:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 malwarescore=0 mlxscore=0 bulkscore=0 adultscore=0 phishscore=0 suspectscore=0 mlxlogscore=871 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101100021
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_13:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 spamscore=0 impostorscore=0 mlxscore=0 suspectscore=0 mlxlogscore=786 bulkscore=0 malwarescore=0 clxscore=1011 lowpriorityscore=0 priorityscore=1501 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101100021
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.18) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint1
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/CKL0dV-hwXuap9_-bzkEyJ-deEI>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jan 2021 03:44:38 -0000

PiAgICBXaGF0IGFib3V0IHNjZW5hcmlvcyB3aGVyZSB0aGUgQ0EgaXMgcmVjZWl2aW5nIGNlcnQg
cmVxcyBmcm9tIGxlZ2FjeSBjbGllbnRzIHRoYXQgYXJlIHN0aWxsIHVzaW5nIFNIQTE/DQpUaGVy
ZSBhcmUgemlsbGlvbnMgb2YgaW5zdGFuY2VzIHdoZXJlIGJ1c2luZXNzZXMgZG9uJ3QgZm9sbG93
IFJGQydzLiAgVGhpcyB3aWxsIGJlIGFub3RoZXIgb25lLiAgTm8gYmlnIGRlYWwuDQoNCj4gLi4u
IEkgc3VwcG9zZSB5b3UncmUgb3B0aW5nIHRvIHNheSBvdXQgb2YgdGhhdCBkZWJhdGUgYW5kIGxl
YXZlIHRoZSBkZWNpc2lvbiBvZiB3aGV0aGVyIG9yIG5vdCB0byByZWplY3QgdXAgdG8gdGhlIGlt
cGxlbWVudGF0aW9uIC8gY29uZmlndXJhdGlvbj8NCg0KVW5oIHllYWguICBJcyB0aGF0IGEgcHJv
YmxlbT8NCg0K


From nobody Sat Jan  9 20:41:13 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A61D43A08F4 for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 20:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dwCCKMA0TxBN for <spasm@ietfa.amsl.com>; Sat,  9 Jan 2021 20:41:09 -0800 (PST)
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10on2102.outbound.protection.outlook.com [40.107.93.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67E9F3A08C5 for <spasm@ietf.org>; Sat,  9 Jan 2021 20:41:09 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TRkvl69zHwBbhXGp21vjiidSaVdkVYD1VU2wxK5NItuHhjG8nf3ge5ryF1VkgzmkrxZTizCvv5Z4JPLArEEpipPT4MP0iGgDvp++f7EX7UMzjLMGo5ox3+GU0blKURv7bnAB63rJ8C9SKLlhP5RK4Irro9RAzo6AheG9Ss8IhAcwcmUwdROi7VhiirSa4HJ+pV/824SDjWggYbF4dh8R7SHCIBMBW7eo4S78EU7UODwL1Pk7VA0n1XTQ6DHmdHptKj3wDsbUNvuMZsrq/hxZE9dOLn24mBUsnyRFl8XdLBm8gc0TwmVCxXxZeN1unJ/cpIhyP6zhexi27uGg9taqng==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9VX1jqYUBppt7KjYt15f2ukI1OnWAC+MMwHoMz5siak=; b=QgflEVXvMuTZPPZZdq4f92xOxnbmGjtZa6M9ktf4psyUWQmAfvkgNJzWXQluyMh8Rkm13IvcMoL0O3BQLnI+G2kEJxgUF7C2tKXVACraoHZMaRRdEwv0PwQ+0bRI0oM3/KaCQVvXNapH2+pyyEwV8CX/G9oPZSsEIXsm4icgG+5+imjmCAl0f3HUL2SzKcurqMjUqkcnQwTlAAleZxQOgJs210SJ0OYkUYuAdA+v9jgeoHPc+w/Ocrok8BjzJtIRGLfjFMdzslIXxjbA18Zhtq5M72076lm8l+od/KUD+lh1Ud7WJ1N0BAtLq9c6dQOF0wJdO4hTm+cINwzXZoVbew==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9VX1jqYUBppt7KjYt15f2ukI1OnWAC+MMwHoMz5siak=; b=T5cl4EmDTlTqGGinUPNP59ZqK0Sw1Nul8U52NjZtGpXcYnoKgqw2ZF+xBxBoOZBm5dUrjA3d3mhbdl5ZP9w3L175zI4St1Wtzfdv9VY8d4iY0BENL+36I3T2RRVoWGq/Lu/I0H5kXv+hV4z7EEBcuSmegAxoLHXCEY3z0MMoLGa2rzHckoAvqATJymH82uF4N4/eCcR5QrnW17CxuR9Rm49zZ/yUHTmhSbUfWLtzNhcJQopUx8HI58vZdRU9T16rBQsWiZU1X3t2YB7XadU86vY5Ls8e2LUNFvcyVn8HJ7p/dK596I1e/fM/o33NMwz7xFKNSMhOkpfYABD7iiH4YQ==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM5PR11MB1258.namprd11.prod.outlook.com (2603:10b6:3:14::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Sun, 10 Jan 2021 04:41:05 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.006; Sun, 10 Jan 2021 04:41:05 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Russ Housley <housley@vigilsec.com>, "Salz, Rich" <rsalz@akamai.com>
CC: LAMPS <spasm@ietf.org>
Thread-Topic: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
Thread-Index: AQHW5tNDoItPwZNbNkyEum8gmM3u0aof8ULggABG5wCAAA+ilQ==
Date: Sun, 10 Jan 2021 04:41:05 +0000
Message-ID: <DM6PR11MB4380A74F7A3AB1DDC9B8E6D49FAC0@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com> <AC40C703-8619-40D1-9076-C26404645409@akamai.com> <DM6PR11MB43800A6F529075C037D62A939FAD0@DM6PR11MB4380.namprd11.prod.outlook.com>, <4BE67EDC-FBDC-4145-B81E-0BA396C48CDE@akamai.com>
In-Reply-To: <4BE67EDC-FBDC-4145-B81E-0BA396C48CDE@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [76.71.20.125]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: de49dd85-32d6-400b-8dc1-08d8b521f0c8
x-ms-traffictypediagnostic: DM5PR11MB1258:
x-microsoft-antispam-prvs: <DM5PR11MB1258F0F7D4324FF10FE47E249FAC0@DM5PR11MB1258.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5236;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jLEicjIEPVMuwXBoMeLPtpQjwrxuFD17FMuT3J8PZcnR+vTTg7kupZam/1Sg+Vfd8gLutOxbAUzLtZnukMx8MlrU4BkQ0f1J+uYQAT8Vz+kJIvunp5jnecyqrRDa4lBlrD7ZA5lXQ27hdhijGhI2D7fQ6DvbVXCsKUMbDEN8AuJyQlybh27lZZGi6Fcl0mLHY+VbDo5XsG6tMlCC2oxzAfu0s0FaxlXChAMrP6qfufYdmtm/nM6FGuEAePnaEoEH+tIrv6Z1gwcM/3vq5PspYAMwmEmf+QyY4oSMIkgkFG5xXcJxZgtbo++29ML0n3Dy3EcuF/zyMlqKSlnQ/Ox0qNN/cFmxEGZwRVVLpJEHNcUdTEafWDUQogzTLieWm0iPzWHNaEiJLVBsNBQELNOZjQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39840400004)(396003)(366004)(346002)(136003)(376002)(26005)(478600001)(53546011)(33656002)(186003)(9686003)(64756008)(55016002)(5660300002)(66446008)(76116006)(66946007)(91956017)(66556008)(71200400001)(86362001)(4744005)(110136005)(7696005)(52536014)(6506007)(4326008)(316002)(2906002)(83380400001)(8936002)(15650500001)(8676002)(66476007); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?WXN1vYzCl1LbO1KmD+mr/6DGv65T+HMVe9iqEi7qcmDMWJdw7VtfJS7Z1AJd?= =?us-ascii?Q?Gkgn22btRrE++l41bvvaWRY2DqaYavQuVtOskm76edZ307l5UU3HRgtz7w3K?= =?us-ascii?Q?+837hnQ950xV9OeeL7rZIQWE2pKX5jS/RTNIaHJ1pugmj7+hBIbVzPS4wdqp?= =?us-ascii?Q?KKasuUVvvTxhYiIB373apE6hPIR1GPfdI/mTBIsqf+ELfAyoC7NZaVkdTTrl?= =?us-ascii?Q?/UZcq6ZcJEDjgn3PXEZwDVV6Wia60D4grjKpVk7t7E21YWVIysTdJOCtwJGQ?= =?us-ascii?Q?+OeHWZbsuFGnW7pdcsoQbVB7jaiioXf2GukD1BLYBnpUJ9LOZ2wB6Ay2vAr5?= =?us-ascii?Q?tLwTP6xRXJFrBC9N6pSmZlyoDRqU+zGG08VItpg+vShLKBWqwD+iko6gkvjl?= =?us-ascii?Q?tdZ2Jrj9SYhW/orrZuLgBTMrUWtZ0Z1Llhpn7RFL5t+9d3L8NcZS8srhabIH?= =?us-ascii?Q?YWZ87Dq8jFP9p4K/ODRzm0+/QskI/5JqaEkijn3p4z3OVcj8L1MXrXPQDjjp?= =?us-ascii?Q?zZ/bMEaAaofER/MTpFHbB6T1hRgUvUTiPbUy1cd4t6qP6fuOLfqzrMeIx3L2?= =?us-ascii?Q?/zipqR7XVUPcLU7tpKrBCvRyo2lv3Ue7JZ++C3g3nY0+n8AQXAWzmrLwjlCt?= =?us-ascii?Q?ZU5DZBPZGaCCFa3ZU5wx4Am5DRKkRL1yCHLXQcLJQN2S4jqaNssfNaLF+X5g?= =?us-ascii?Q?NAYM6Jr0/X/nnPB0FUmJkrcZKdPUwasVJ+n13KBJOdg7xXLYCjnNVeROgyY7?= =?us-ascii?Q?6NMtBpzY+sKGkRNbZ1ZQEksuUEXi5OZaWtQt6mZLpfNCryojFVK7Ba/58463?= =?us-ascii?Q?yiAxOZnYUvfufpqeoSuGaScqyQa7JMWFe8AfhhHcJLo0CD0kw4R9rtI7JW48?= =?us-ascii?Q?oQKc8hx5wTo+3TCod5nkuxXVEEo/oCxmz94NRFWq3apCXYuxTkHp8n+KS5BH?= =?us-ascii?Q?5nzKeBL5fgK3RtdjhGuBy1WLgMhLNFe1EOkRrbrJPXH5OF9ap+uo5KVuADpA?= =?us-ascii?Q?h6Cm?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR11MB4380A74F7A3AB1DDC9B8E6D49FAC0DM6PR11MB4380namp_"
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: de49dd85-32d6-400b-8dc1-08d8b521f0c8
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2021 04:41:05.0689 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 1qE1lupLGhJOF7UjaoxfCK/EnG8Wg/mc6iTuDFLXvqUmhKEVBR9xMA2jcWBiqLArqhsqmYINyHpXx25hoPFsQPpKMr8LETvlZ8dcaEDXR5g=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1258
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/tT2RJkC2-3AD2kQhHmJoMU3kifs>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jan 2021 04:41:12 -0000

--_000_DM6PR11MB4380A74F7A3AB1DDC9B8E6D49FAC0DM6PR11MB4380namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Nope, no problem, just clarifying.
________________________________
From: Salz, Rich <rsalz@akamai.com>
Sent: Saturday, January 9, 2021 9:44:32 PM
To: Mike Ounsworth <Mike.Ounsworth@entrust.com>; Russ Housley <housley@vigi=
lsec.com>
Cc: LAMPS <spasm@ietf.org>
Subject: [EXTERNAL]Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-=
algs-02

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the =
content is safe.

>    What about scenarios where the CA is receiving cert reqs from legacy c=
lients that are still using SHA1?
There are zillions of instances where businesses don't follow RFC's.  This =
will be another one.  No big deal.

> ... I suppose you're opting to say out of that debate and leave the decis=
ion of whether or not to reject up to the implementation / configuration?

Unh yeah.  Is that a problem?


--_000_DM6PR11MB4380A74F7A3AB1DDC9B8E6D49FAC0DM6PR11MB4380namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
Nope, no problem, just clarifying.<span id=3D"ms-outlook-android-cursor"></=
span></div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Salz, Rich &lt;rsalz@=
akamai.com&gt;<br>
<b>Sent:</b> Saturday, January 9, 2021 9:44:32 PM<br>
<b>To:</b> Mike Ounsworth &lt;Mike.Ounsworth@entrust.com&gt;; Russ Housley =
&lt;housley@vigilsec.com&gt;<br>
<b>Cc:</b> LAMPS &lt;spasm@ietf.org&gt;<br>
<b>Subject:</b> [EXTERNAL]Re: [lamps] Mail regarding draft-ietf-lamps-crmf-=
update-algs-02</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText">WARNING: This email originated outside of Entrust.=
<br>
DO NOT CLICK links or attachments unless you trust the sender and know the =
content is safe.<br>
<br>
&gt;&nbsp;&nbsp;&nbsp; What about scenarios where the CA is receiving cert =
reqs from legacy clients that are still using SHA1?<br>
There are zillions of instances where businesses don't follow RFC's.&nbsp; =
This will be another one.&nbsp; No big deal.<br>
<br>
&gt; ... I suppose you're opting to say out of that debate and leave the de=
cision of whether or not to reject up to the implementation / configuration=
?<br>
<br>
Unh yeah.&nbsp; Is that a problem?<br>
<br>
</div>
</span></font></div>
</body>
</html>

--_000_DM6PR11MB4380A74F7A3AB1DDC9B8E6D49FAC0DM6PR11MB4380namp_--


From nobody Sun Jan 10 12:07:00 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12CB73A124D for <spasm@ietfa.amsl.com>; Sun, 10 Jan 2021 12:06:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMkdKaTDoCVD for <spasm@ietfa.amsl.com>; Sun, 10 Jan 2021 12:06:56 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59C1F3A124E for <spasm@ietf.org>; Sun, 10 Jan 2021 12:06:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A8115300BA5 for <spasm@ietf.org>; Sun, 10 Jan 2021 15:06:53 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 4KEv36kt09ID for <spasm@ietf.org>; Sun, 10 Jan 2021 15:06:52 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 510B7300A01; Sun, 10 Jan 2021 15:06:52 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DM6PR11MB43800A6F529075C037D62A939FAD0@DM6PR11MB4380.namprd11.prod.outlook.com>
Date: Sun, 10 Jan 2021 15:06:53 -0500
Cc: Rich Salz <rsalz@akamai.com>, LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5445DCD-66AA-4E9C-BEF7-6B6F7128C6CB@vigilsec.com>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com> <AC40C703-8619-40D1-9076-C26404645409@akamai.com> <DM6PR11MB43800A6F529075C037D62A939FAD0@DM6PR11MB4380.namprd11.prod.outlook.com>
To: "Mike Ounsworth (Mike.Ounsworth@entrustdatacard.com)" <Mike.Ounsworth@entrustdatacard.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/T4y3A1r04Mpxj1B6tmbhjqaI7-I>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jan 2021 20:06:58 -0000

> On Jan 9, 2021, at 6:37 PM, Mike Ounsworth =
<Mike.Ounsworth=3D40entrust.com@dmarc.ietf.org> wrote:
>=20
>>>   I'd rather not see anything about SHA-1.  The situation for =
Certificate Request Message Format (CRMF) is not like S/MIME.  By that I =
mean, one will not need to process a CRMF message many years later from =
an archive folder.  A CRMF message should not need to be validated after =
the requested certificate is issued.
>=20
>> Strongly agree. =20
>=20
> What about scenarios where the CA is receiving cert reqs from legacy =
clients that are still using SHA1? ... I suppose you're opting to say =
out of that debate and leave the decision of whether or not to reject up =
to the implementation / configuration?

In that case, the clients conform to RFC 4211, but they do not conform =
to the update.

The CA will have to decide if it is willing to support SHA1.  I'd =
actually be surprised is any still do so now.

Russ


From nobody Sun Jan 10 14:15:20 2021
Return-Path: <jfhamme.cccs@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D9D3A1342 for <spasm@ietfa.amsl.com>; Sun, 10 Jan 2021 14:15:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hg-e-oJdjQIX for <spasm@ietfa.amsl.com>; Sun, 10 Jan 2021 14:15:17 -0800 (PST)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E1313A1341 for <spasm@ietf.org>; Sun, 10 Jan 2021 14:15:17 -0800 (PST)
Received: by mail-oi1-x22c.google.com with SMTP id q25so18213609oij.10 for <spasm@ietf.org>; Sun, 10 Jan 2021 14:15:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=QByaF9SVC7/66V3rYjq7UaaSvtxLjdlC2xOD3d+HoTQ=; b=c+LfgUsCUyYzqoPA7EcfJBhLodw0bVcVdUbzOOfXSXQhS0jOqPcNWbjxqR26jwFQmq vD5ICrRKi3vbZWuPG0oqTsnLAn1w49vQPiDfRuSFrjBsVbDW1JpuInmhhHQvDwuh88zq vAiNCu41TXq1CfeE/fEmI9YCyWrxekmveiG41KrLZWhkHIIgbzku9lJCHdc038O4CEA9 N2bOZlfrpcBJeUTP3avgz35gYDCL9zsQiyGekyRLDILeP8Von3vV5lG0j5h0CKt+3s8H jS77vdu28mKEHl4k3E2PZdSkNyq8OiPTz7Eh1stLB1MBhnd1RQlEdH31M+kDMme+wQPh c05A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=QByaF9SVC7/66V3rYjq7UaaSvtxLjdlC2xOD3d+HoTQ=; b=KfMfjVR6DBTGajcI1PenXmWsOnIb0hlXawvaliFA3jw3khsJ4AT3mNniH+t/3C1nXZ yWUfcGRftC0KOOBnwo3i9aVH8UWhRIUuithNwh9RPWPIVs8rQraRV92xL0ybFVRUgEFJ R7IYG8FVALvaU+80wfv/nH+hvlUfHULPBCyR0DCaKmTdBU7wGcxlwWyZ9g+dsg5H9XrV O8Fb9r6sdX46X4STaRMZgv4aR0cBVENnkJlryXCvLc3VhsbTeNFLd832uI/E6QukHaTA nefPEJHxHJIa+gUexAnOcNO2M2fBlvbYurtJbav9uvYsltT6ULaIe5aKJwFhU+K7N8hr fY0Q==
X-Gm-Message-State: AOAM531vxMRpluGtWZXlbGy12vNz6WKLYnAGViD3qy0+IJmWum0DN7x6 y6vPQtT3Vnbg5ExmdbZZ5uJVOHt30dFUcXmbeNAtm/U5ZAg=
X-Google-Smtp-Source: ABdhPJxZp9LuIP2BG0XukdNDF85MHMONIZTd6pLATmiHXjq0E37aOlZHT825g/akYuwHs1JLHM49R94AZfZwioimM/Q=
X-Received: by 2002:aca:3094:: with SMTP id w142mr8558140oiw.101.1610316916347;  Sun, 10 Jan 2021 14:15:16 -0800 (PST)
MIME-Version: 1.0
References: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com>
In-Reply-To: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com>
From: Jonathan Hammell <jfhamme.cccs@gmail.com>
Date: Sun, 10 Jan 2021 17:15:05 -0500
Message-ID: <CALhKWghnCZx+OK4LEbt=nSJkX6VJBL7XNT7_0m6BBX57jNwczQ@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: LAMPS <spasm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/EUOb4vbSo3AtoNIL2TX6tRqVV9U>
Subject: Re: [lamps] DRAFT Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jan 2021 22:15:19 -0000

I support this constructive approach.

Jonathan

On Sat, Jan 9, 2021 at 1:23 PM Russ Housley <housley@vigilsec.com> wrote:
>
> I assume that everyone saw the note from the IAB Chair, Mirja K=C3=BChlew=
ind.  I suggest that the LAMPS WG ask the IAB to send the following liaison=
 statement.  We're asking the IAB to do this because the IETF does not have=
 a liaison relationship with ISO/TC 154.  Please review and comment.
>
> Russ
>
> =3D =3D =3D =3D =3D =3D =3D =3D =3D
>
> FROM: IAB
> TO: ISO/TC 154
>
> The Internet Architecture Board would like to make sure that you are awar=
e of the recent work by the at IETF LAMPS Working group (https://tools.ietf=
.org/wg/lamps/) that lead to RFC 8954 (https://www.rfc-editor..org/rfc/rfc8=
954.txt) that updates RFC 6960 (https://www.rfc-editor.org/rfc/rfc6960.txt)=
. RFC 8954 limits the size of the OCSP Nonce extension to 32 octets to make=
 the OCSP transactions more secure.
>
> We understand that RFC 8954 may have a conflict with the way OCSP Nonce e=
xtension is proposed to be used in ISO 14533-4 and perhaps some other work =
which we are not aware of.
>
> We had a discussion about the use case in the LAMPS working group recentl=
y.  Based on how the OCSP nonce extension is used in the industry, it was r=
ecommended that a new OCSP extension should be used for the purpose of capt=
uring OCSP response for long term validation of the signed documents.
>
> We recognize that the IETF does not have a liaison relationship with ISO/=
TC 154; however, the IETF LAMPS working group is willing to work with you t=
o resolve this conflict in the best possible way.
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Sun Jan 10 23:21:01 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE90A3A167C for <spasm@ietfa.amsl.com>; Sun, 10 Jan 2021 23:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XXOpMEeft2O for <spasm@ietfa.amsl.com>; Sun, 10 Jan 2021 23:20:58 -0800 (PST)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80073.outbound.protection.outlook.com [40.107.8.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94EF23A167B for <spasm@ietf.org>; Sun, 10 Jan 2021 23:20:58 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jHz0P96sGuhVAiijFN8SAnGy0Nap8RVBdxeZl36MWpV0XgFvvOsDgiWwYysItYkAa6h97lHXtSpAtYyKti1E8eHir13QWEDLF/FkLCZytIZelWGAjfEfn5zTvLhN8vbDOG3K8/RIQ18bCOPN0k8NUsOVmx0LtQVrpXG10Wt6++XW7shVjbjB2AswfKxJJ1GggWPqjDDKKcPLBtlm748LGeadixRfU5k8wS4HmEW6xFY9NY5Iyum4cpu3i/KVszosg3B+VbvSCE751E7SQjbhsapRxpTdI5tKUezYe4T/58ff2nm4MvdPSynZIwbbSVVhJbMNqFWOn8VP3HrQEfWbhA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Z2ivHDAtD2Bp+x/sMTdMm8UUQtMtD+tdDUumN0Eznio=; b=Rfu4UEbhyIVnssaCWWZZAgFkmk21QJx1PPgKPM0bW6XXIDgrHcmj4iWkMEfyL4kWQmXv/SR78i0bTLLPayd5oe7bUu0iA8eO70DhIv+RO8gLu70+XCwiCEiZ1pX1tgWuIS/y6NQ6lCJVOV4OyMFwWNAAJmGfsbLfX05kTtOFUhYdYaf0qS27ImoCROe9ZZBeBftcH+jsHj8OVJxvF4g6HzR3Am5KxShrbxYOSgmu2TvKQ7T6LlhB0UzXUYrdaeOs7k0vGUmujPd1giZZmpmba7msVDwsehsrXfwNoIO7ebTv9v98kx+XHgOF/uSgttaMFcJ27h6gL201FYFjFIwv/w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Z2ivHDAtD2Bp+x/sMTdMm8UUQtMtD+tdDUumN0Eznio=; b=WCiIY9Q/7JQ4+dvSnokPDCC9u5QdV6dg9DiRdRVvJXrjh0d3Hp10TNAiV+gmVKR0ehgGU8ipdXHYzVIhceeZztRtmFv3gnmf4KMiIDyD3E3cSEm1RHfH4OwYxgOSMji+33nY8YBeIIbyWgsJsAuZSf1IIQ5KlygLVoQLBYilG3U=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM0PR10MB3569.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:20b:15a::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Mon, 11 Jan 2021 07:20:56 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::a5a7:8af9:1e22:1d69]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::a5a7:8af9:1e22:1d69%6]) with mapi id 15.20.3721.026; Mon, 11 Jan 2021 07:20:55 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Russ Housley <housley@vigilsec.com>, "Mike Ounsworth (Mike.Ounsworth@entrustdatacard.com)" <Mike.Ounsworth@entrustdatacard.com>
CC: LAMPS <spasm@ietf.org>, "hans.aschauer@siemens.com" <hans.aschauer@siemens.com>
Thread-Topic: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
Thread-Index: AdbmDrJ8XClSyQZRTI2kM/VC377vqgAnswAAAE7zvNA=
Date: Mon, 11 Jan 2021 07:20:55 +0000
Message-ID: <AM0PR10MB2418710F80A2F8CDB58CE88CFEAB0@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com>
In-Reply-To: <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2021-01-11T07:20:54Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=55ee603a-c614-4e2d-a52c-cd8d4d53bd78; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.183]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: efaa847d-5cd0-4c71-a4ab-08d8b6016f9a
x-ms-traffictypediagnostic: AM0PR10MB3569:
x-ld-processed: 38ae3bcd-9579-4fd4-adda-b42e1495d55a,ExtAddr
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM0PR10MB356944DF3ECA2647C0CDF729FEAB0@AM0PR10MB3569.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 3Co8cWR2jYtz0y+0jrXoXyj9fjGFCV6WvTXEycERZss/KrX2kbAxddjZFo5CswcqGBZnCELlkeV7k12ORWFkbwdG8KWGGApSEJhxXHeUobUH1mEhdJnlicT5BJoVMZHlUfnsccHcfVQAMcQLSvfRyuM2UXaDVOZPyoouMUoM6L3XJuJO5B7dAts8dQORtzZcQeOVAowO61heLMUGUv3tiC8uTKBxzpwmhMFLCDwkmZvAqcMaD8CzcgJzhe1YONFS1FYs5GPxSidogGKiX94rTEnGTtVpy7SDkMJMmSwTm7a0iMrFIGvu191Vom79N3sk9mBTg3dmNfYEsWg/jKGuGTCFa+vH+9SRCqmy7NklDVco7AalX/A32yMvl2iwTe+vfWVlr1HiSxwzh/OKcHWzNg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(396003)(136003)(366004)(376002)(39860400002)(346002)(54906003)(107886003)(33656002)(110136005)(55016002)(15650500001)(316002)(8676002)(8936002)(71200400001)(7696005)(86362001)(52536014)(478600001)(64756008)(66946007)(66446008)(4744005)(55236004)(6506007)(186003)(9686003)(4326008)(66476007)(66556008)(2906002)(5660300002)(83380400001)(76116006)(26005); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?JCYaTUFw3KT1Cl0xKIkzPdrK3Ni3QZgr3kG/OYkIdPXde7QY6AQhFp6O0dmd?= =?us-ascii?Q?5yqGg/xYnokWGyA1et8qqbdICwdjsWv76y2OU1iphrCPsld7s3KvkROui0De?= =?us-ascii?Q?ZK0WS/alQvw6DY0ey9Wj1GoHMF7UU9MxnSsEO7q4HOATpRe42q8tpl9UM/z0?= =?us-ascii?Q?qWw6IFr9/Ro1ELrrx0YFyNcxUXkQdgEHH3iU89RdlgwdYl/aw6JD2eWa0ZaE?= =?us-ascii?Q?I+Qk3VpPT+LaPe0+x1yhVQU9BbpWj4hIpb29VI82l5VplxDYJvL6wIvRxQUQ?= =?us-ascii?Q?IjOAl4Roo5dPeTJC8TEHT3XwJfCzqxVaBX0Du+ecy0R+SNxZRmNanp009HBE?= =?us-ascii?Q?kDORj6llYZWsfl4yL9hocWihYAf/Cg0MFXEuTJkoGb1S3LThgla+k4g51q7H?= =?us-ascii?Q?fgJ5Cwn8mbXY7UAEfSRvov1JMSTcdcnfx8TsGTtSQ4bBqFhv+vPx0pXAS4U+?= =?us-ascii?Q?+1aAIMBAX5S9OXhNaeSGwSjrK7T9E8lv1ld6oA0RmP/CcJsEUOxuOpXV/739?= =?us-ascii?Q?fu6+2GXbG9pDNCiMw5gHBbajfyjHXcGTBYC3PSXU7pDNkwpUsiF9xF0PQF93?= =?us-ascii?Q?mdSeKnbujv/qYGBSaZt0FjTleSoFHxSH7ahXBIlKxs9Nl3WlFHbQSN8yF3EY?= =?us-ascii?Q?Xaqv5icxKEszw1c3MCYmiL/JZpeYliSY99cGSzaVaTav2bFcx1+0J+o+4SwW?= =?us-ascii?Q?GzJQ+BBD7YCvnn+YxYyXm8cRUXtIsYwVnAToG0yghC0RzKvwu23jpYWk3ZOh?= =?us-ascii?Q?ZqtiEvWRcRlLaV3OLcr6yolnt7WF3ivqCjnm4xpYCxqDSACWZTb5EYNGrhR9?= =?us-ascii?Q?Tggjr7kF7m2KcQYU/Luq6qA2uqrUf4SFWlyjJnXaPz6wdoXosKOrkXHmoOcc?= =?us-ascii?Q?3zsrQII/t4Tlx4467dAiGR5Ofyx/I6v4SlK7qecrG9f297PZSogJonjOPvsF?= =?us-ascii?Q?4PBGAQhnTR/aQ2wKYnIe5FpFmOKRiEcmsnBsWVpNuQc=3D?=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: efaa847d-5cd0-4c71-a4ab-08d8b6016f9a
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jan 2021 07:20:55.5244 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 0DhZzoeqWlMU45yi7MjtZgFQ1WBmKxd7I88uVvXuscyYZixH+295SX5epwxCoKg1aPFfpA3Bdm8SPIGuH4UelJXxA5lBcG/eP6P9Hhl4DJw=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR10MB3569
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/h--fRZykUaUfoo2TcWyQ7s8kCK4>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 07:21:00 -0000

Thanks Mike and Russ for your proposal.

> > TL;DR: it would be great if this draft included a PBKDF2-based MAC (we
> suggest PBMAC1 defined in RFC 8018). We also have a few general nit-picks
> about the draft.
>=20
> I think this is a good idea.  Before I add it, I would like to know wheth=
er
> others agree or disagree.  More below.

I support this approach.=20
After discussing this with Mike, I also plan to add PBMAC1 to CMP Algorithm=
s.
May be I should also add this to CMP Updates to explicitly open RFC 4210 Se=
ction 5.1.3.1 to also support PBMAC1 next to id-PasswordBasedMAC.

Hendrik


From nobody Mon Jan 11 00:56:02 2021
Return-Path: <tomas.gustavsson@primekey.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D271B3A1710 for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 00:56:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=primekey.com header.b=bL92Ec45; dkim=pass (1024-bit key) header.d=primekey.com header.b=bL92Ec45
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ROTUCoYYCuQ for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 00:55:58 -0800 (PST)
Received: from mail.primekey.com (mail.primekey.com [84.55.121.163]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAFF03A1711 for <spasm@ietf.org>; Mon, 11 Jan 2021 00:55:56 -0800 (PST)
Received: from mail.primekey.com (localhost [127.0.0.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.primekey.com (Postfix) with ESMTPS id EAAEC6AA00D5 for <spasm@ietf.org>; Mon, 11 Jan 2021 09:55:53 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=primekey.com; s=mail; t=1610355353; bh=BkNSP8brxDke76QRjG2Ku4toROkQvYJd7q85sSOI+cA=; h=Subject:To:References:From:Date:In-Reply-To:From; b=bL92Ec45HHQOav+T0SB01l2YvvwIASDk8w0rM28IBsdc87IwH0wXsl//lzrTaKiLK Dy3JeyvqO7HS6Au69/WlSmRgI84Aca6Klpym6qW6YfVBsUqXY2/8C8xxgsrjJaZ0ck oGH9pniVkvzDrDa5uRYVm++5GsZUx0ug/ZB2Jm0I=
Received: from [10.11.0.26] (unknown [10.11.0.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.primekey.com (Postfix) with ESMTPSA id BF8146AA00D4 for <spasm@ietf.org>; Mon, 11 Jan 2021 09:55:53 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=primekey.com; s=mail; t=1610355353; bh=BkNSP8brxDke76QRjG2Ku4toROkQvYJd7q85sSOI+cA=; h=Subject:To:References:From:Date:In-Reply-To:From; b=bL92Ec45HHQOav+T0SB01l2YvvwIASDk8w0rM28IBsdc87IwH0wXsl//lzrTaKiLK Dy3JeyvqO7HS6Au69/WlSmRgI84Aca6Klpym6qW6YfVBsUqXY2/8C8xxgsrjJaZ0ck oGH9pniVkvzDrDa5uRYVm++5GsZUx0ug/ZB2Jm0I=
To: spasm@ietf.org
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com> <AC40C703-8619-40D1-9076-C26404645409@akamai.com> <DM6PR11MB43800A6F529075C037D62A939FAD0@DM6PR11MB4380.namprd11.prod.outlook.com> <B5445DCD-66AA-4E9C-BEF7-6B6F7128C6CB@vigilsec.com>
From: Tomas Gustavsson <tomas.gustavsson@primekey.com>
Autocrypt: addr=tomas.gustavsson@primekey.com; prefer-encrypt=mutual; keydata= mQENBEyuwwYBCAD31Jsxn1lf7rnFc7y3Ol+TE7pU7ohO78kMdoVrZdAMnU9W0P33GedbU+kF 8/RFq7HlXV8a91RkgtdcMAK8tSdtBKDGZCOJZm5qOZ/EHikY8k/7s1wgSQSF4hYSG/IABCCA W139joDFl4L3buWyk2lsYX1HDBpuXGDL5HFyu165T0ZVlt23T04xmAwpIHUViKUWw1QYnlRz s66Desn2WeP+X8/QlqF1zOTUXbgrThB1X/Oh2+wzP08HVoTQCzlrEMeb9x2k+oa8PtVdnflh nZKBtyyBkZxRoHG3tNKcaf7JLoadSXcSKSKvfApcsxpP2JpkQgIhLi3JWik/Z+RR2WD1ABEB AAG0MFRvbWFzIEd1c3RhdnNzb24gPHRvbWFzLmd1c3RhdnNzb25AcHJpbWVrZXkuY29tPokB NwQTAQgAIQUCWX8yTAIbIwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBibcSbAEP+QGAU CAC82dn8XCQ8Ei7gxQAdRSc2imaP/388i/ObDMYhNhg5j4gXs3tkfxuCvhwkzskUFgOtmaEy uz/gIiVjQIsjQrHh5tl9M0q2tqbDHJpWfE6/SkXPUmTqQ0VGyq1MmZ3/zg2jSoll74qBSfdH V7sWugRXeCBxfaPeYo8DdPCGi27yrdL8zb3xkJ3BxPcDGNdkLm+Yza+qAOrssCD7MSLN+6Sd ML5Xcmw6pgRPlQ0aCsM7scrwgBNb7KrwxaqBxqwcuqF0NMgNjeiEHi2Oj3HOZdYU4Blk2GFq 9zHuCzTWumgNOlfksZ9K3ZMJBn6KLPot5bVXIKdnHwWRzoKMDxkSZjM5uQENBEyuwwYBCADZ 98eCFQ64zKo1OKkUgEJHO1JdsiqRO1znu6KyaTcd2vXfOCGkFFVBL+vjzzyyYV7Sg1/AaG4r l9TKJCwvx8mUmTJkKQspTfOj6AY33bmfMB/8LBYj2BjtxXyMucPjNTJqbL2r1HeGPV2nwyof MAyo2qcYuiLs20Ob7U8vooOV3GDDKEkXtJYZzTEU6qabGsepGIvMu770OZwvm4akQiCGe5sQ 4+/UH1pMZQNi+/fGbONFx+TUVMM8EkXD6dQ5WoL+xPabPjqiUmR7EBvg0uocr70Ag93tWk1d 4RgFcicjwMFcPg4TZ8Y/3Y7Nmbyo14+4SMNfNPFLgQMawL+cLLkdABEBAAGJAR8EGAECAAkC GwwFAlYXhXUACgkQYm3EmwBD/kA2igf/QNpPe7sLt3KdRD3x4cStxGjLCWyj7x1YLVnV4Nnu TvaNhC+KHx3uG39y1x3PJQwslpeSQ6JipOUmxeQjjGJGQZLV41L1PCJVhCL98Dinr6dJkYB7 cAVhfmW8PI51jiANExLZu8U5gnthj5CGv4428ODQgSoRI0demG3HmVCNrKdap+orhT8zRkq8 DuHTO01U7PKsfvQ2k8AqSAC/JjMOs1mpFe032IApXxlZkE+33Q3dE5BiJmICYg8hsRXvpKTm ZMCdNZJUQLq+XNpg6RtAPQIPMmCepXrE9M/KuH+jFS2G5+Hx5VBSM644E1G2i+HOPCVdHjof iaNi3V/ItEG3jw==
Message-ID: <5d499876-d416-4806-adee-d2def86aff52@primekey.com>
Date: Mon, 11 Jan 2021 09:55:53 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <B5445DCD-66AA-4E9C-BEF7-6B6F7128C6CB@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/6y_fi2OTEa6CbL9beIFNccvfCEw>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 08:56:01 -0000

On 2021-01-10 21:06, Russ Housley wrote:
> 
> 
>> On Jan 9, 2021, at 6:37 PM, Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org> wrote:
>>
>>>>   I'd rather not see anything about SHA-1.  The situation for Certificate Request Message Format (CRMF) is not like S/MIME.  By that I mean, one will not need to process a CRMF message many years later from an archive folder.  A CRMF message should not need to be validated after the requested certificate is issued.
>>
>>> Strongly agree.  
>>
>> What about scenarios where the CA is receiving cert reqs from legacy clients that are still using SHA1? ... I suppose you're opting to say out of that debate and leave the decision of whether or not to reject up to the implementation / configuration?
> 
> In that case, the clients conform to RFC 4211, but they do not conform to the update.
> 
> The CA will have to decide if it is willing to support SHA1.  I'd actually be surprised is any still do so now.

>From the product side, it's easier to support legacy algorithms than to
forbid them, as SHA-1 is yet long from being removed from cryptographic
libraries. We made a survey last year with customers, if we could remove
SHA-1 support completely, and it's still a few years out before it's
possible to generically completely forbid in products it seems.

Configuration for a specific CA is a different thing of course. Internal
legacy CAs still support SHA-1 in many organizations.

> 
> Russ
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
> 


From nobody Mon Jan 11 07:39:45 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8543A0F3D for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 07:39:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ppVPl2YjOkWe for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 07:39:41 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 348DB3A0F2E for <spasm@ietf.org>; Mon, 11 Jan 2021 07:39:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A3941300BBD for <spasm@ietf.org>; Mon, 11 Jan 2021 10:39:38 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id h4g6fUnqdtub for <spasm@ietf.org>; Mon, 11 Jan 2021 10:39:37 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 7899B300512; Mon, 11 Jan 2021 10:39:37 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <AM0PR10MB2418710F80A2F8CDB58CE88CFEAB0@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
Date: Mon, 11 Jan 2021 10:39:38 -0500
Cc: LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1D88C55-4F56-47C0-AA39-0E816DEF0346@vigilsec.com>
References: <DM6PR11MB43802618370EC97567869A7B9FAE0@DM6PR11MB4380.namprd11.prod.outlook.com> <3C017176-22E5-4092-BBE3-0F4505BE5BF2@vigilsec.com> <AM0PR10MB2418710F80A2F8CDB58CE88CFEAB0@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/3H_nHQT-9NAOx97297VJvY-uWm0>
Subject: Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-algs-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 15:39:43 -0000

> On Jan 11, 2021, at 2:20 AM, Brockhaus, Hendrik =
<hendrik.brockhaus@siemens.com> wrote:
>=20
> Thanks Mike and Russ for your proposal.
>=20
>>> TL;DR: it would be great if this draft included a PBKDF2-based MAC =
(we
>> suggest PBMAC1 defined in RFC 8018). We also have a few general =
nit-picks
>> about the draft.
>>=20
>> I think this is a good idea.  Before I add it, I would like to know =
whether
>> others agree or disagree.  More below.
>=20
> I support this approach.=20
> After discussing this with Mike, I also plan to add PBMAC1 to CMP =
Algorithms.
> May be I should also add this to CMP Updates to explicitly open RFC =
4210 Section 5.1.3.1 to also support PBMAC1 next to id-PasswordBasedMAC.

Yes, it makes sense to include PBMAC1 as an alternative algorithm in the =
update to RFC 4210 section 5.1.3.1.

Russ=


From nobody Mon Jan 11 10:21:09 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C74683A1184 for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 10:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gnu35I6TOzV4 for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 10:20:58 -0800 (PST)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-eopbgr680108.outbound.protection.outlook.com [40.107.68.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90CD43A11A2 for <spasm@ietf.org>; Mon, 11 Jan 2021 10:20:54 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ERISwBqI/A5j/WxiEmwNrnoeAL2iodJ5vPlwXd8hEjRu5hbjTAsdK9LNu+WEqWIYe/WVisM+Kr7N5HpVeJLJog6qz4qEENbOtIsBQb+VMQcPsc0zL+4e0GR1FpdRaCYzMzS62k1nUqdcwanp8vfywg+VZtk9hCTuXryEDGRMYDiV2sdb2Z+vC0avCwZyofB+S5KRIChKJg4bUEsImXnNvu2t/ZnF9Tj+MkyxOgU6HFJ5qPhtH/vW24cSE8vVHcEYyqJJTJMf6AMpFGM5fC2MA1t/jVAnwElKbWRlCqHHHpSHoUHm6zK3CN1m8eoCXlBrfe5I+//A2s15739KqZT2tg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kiAs4NiE0MvrpfA9x6CykC88SMFMkpNsE9tBhk3FCi4=; b=jZ69ed3GpVMmjgj+f9emvdWeg9VJjeJ0d2tw+onyZM8frgycES24NUu+o3Xi1kU2urE3tcgdF8fr0fu+DZf2F8oAzCDwRIIci/h5Z4xAiDzq3EJ1+Fp7LQQ5hm+pcOtcI9jm5ob5I4cN9qP5Vm0MEHtkYGibDfI+vFt9g/1lcAlWrswn9+9Xo4GuDT2xEMvNZT3u9nOp7Dx9VwFhS+8q6aFZmwbGamLAekWEVdsojxFesVv+KqN38M7onI30wjIrFFJK4ZnGTgCGsCDNYXf6b+k51N30dvNIbL1JSLnkoEjVEQhDwNYY7GiK3CbsRIUqJyXpQ6zXJqF7GhMLrvffgQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kiAs4NiE0MvrpfA9x6CykC88SMFMkpNsE9tBhk3FCi4=; b=ijAWlsdxLVnOR533msARU38WwWQTu3LIn866AmHhvTxNxd3BTLxGbtXenI53dcu4OZX3s0mjYryqJW83rq/3Is6u0KhjRWPfsTXrXONebICTPCfys9UvE2kXnMgOwZQjW2wyu32L4NWM3PwaX2Hms18cMShh6pHVqBDIAZ+lh0aR5gVGX1kGsFOZrjnHSZKK/+vQS6ABtzKPToBGMEeVi6EWNpMpjUNOkZQDVY9p75E9fBTBc3LpCpy7AM5WFzsc9C1yJ5UtRW3Et6FcjMsRDZ+61yjKrKPkKs8Dmcx9EJapwuVs2XyjB8vtadIgtyilnpk5naN9RsH/FsVbJIFDjg==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB3243.namprd11.prod.outlook.com (2603:10b6:5:e::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.12; Mon, 11 Jan 2021 18:20:53 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.012; Mon, 11 Jan 2021 18:20:53 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Russ Housley <housley@vigilsec.com>
CC: LAMPS <spasm@ietf.org>
Thread-Topic: [EXTERNAL]Re: [lamps] Mail regarding draft-ietf-lamps-cms-aes-gmac-alg-02
Thread-Index: AdboRnrZTj5Ayo0VS9qQ5eKZPj+u5w==
Date: Mon, 11 Jan 2021 18:20:52 +0000
Message-ID: <DM6PR11MB43802E75B2A922D1B7BC71DC9FAB0@DM6PR11MB4380.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [72.139.202.228]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 637d8040-e7ae-4ed9-ff60-08d8b65da17a
x-ms-traffictypediagnostic: DM6PR11MB3243:
x-microsoft-antispam-prvs: <DM6PR11MB3243C5EF876AFCE541FCC5C49FAB0@DM6PR11MB3243.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: S+o3vrtZneX8ESat7hruIA/JXqqg++gc/BnpB20uhU6WU8xb0zV/7Fs7/23y8J2wGGsfQJLHbm0SJ8hHtvgqaNF3u3Yr2RJD9StG7EX/toGh9Dkx/vE+mv3wX1QGZdnB/hfNrDmudxaYqrxJCnHayjsIqI5X51GtIBSlk8ejrY9kzbDGLR6hreTwvtHa4JFArmn+kJBLa61IC0KaaFeDn8Y6s84sRZAx9YTr0A15xdlBzNCz8THNgwFE45cDjYRHv+ED9Gr3vEsOWhmH2xNb+RMpy/JeLw8U52OtvRHf5cW9WldaY6v/7lNTHB3JP478Fn+ptKklie7xwOAPB0MC6Off8GtpxnzLRVmlbNjQYyCukgwfhwyCfQIlp7faICKHUBjGlde8jHBCvhUebW6UVGNyFx0JkwxXa3KbVAxwCl3WG1x1dnE9hvEXVG1WV+sLcV6yJDKBxh8HZQkxRKOFZw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(346002)(396003)(39850400004)(136003)(376002)(9686003)(53546011)(6916009)(52536014)(83380400001)(5660300002)(86362001)(4326008)(8936002)(55016002)(64756008)(6506007)(966005)(71200400001)(478600001)(66946007)(66476007)(186003)(8676002)(26005)(7696005)(76116006)(66556008)(66446008)(33656002)(2906002)(316002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?Q4C41Z8MWwYEUDg5O03Z1xJc3us5QgWptwAyupB0T9iZymowDReI3ijwcaIK?= =?us-ascii?Q?okks6p17Xxy19b9lATiFl7CNkFXOIDRaN7mAhA8g8pNjEMSX+0k+H95iqSg+?= =?us-ascii?Q?fzNgLRyAHl97sK+KG68ORkTKb2AokOkENHXepqYBfxwKu2TCw9XL74snKZuO?= =?us-ascii?Q?tiaNIUu0gA119nkrRI21cUDaMp3j/3LGpoO7Aol9a2+USJeCB+I+6NTMx+dQ?= =?us-ascii?Q?Qjn7UE9cyQyvXraaWh7BPX9dnJYhDSVmEYj5N2adAaBIjrrZLddHZSydjabH?= =?us-ascii?Q?wCYqDM/1H32/8Gk/Y8T12sk0MiQJZA4ugN7E03sNZzYnHJLs+TQhWCBsbwcx?= =?us-ascii?Q?ictlUm91wY1X3cVR6rz1vsPAH+Llib0vWBHRPbsi7ZGFaBJhuDZkOWVwr2Sb?= =?us-ascii?Q?GWcreZ1dWbUPwxj4itB2R86YoDhMry4XlKIgt0+iTvbEBp9z/nc1jmGdwg4P?= =?us-ascii?Q?VndgeJBArIZS87WInRA9y4Vp3TocFmnJH4eLCT2vHRBVwDUlOthKnljopsLs?= =?us-ascii?Q?g845tEuUPetzWw5IIv4NMO5e+Ks9HkJ/bZM82hLoRkAMIpct9FPH9XDCJqzz?= =?us-ascii?Q?eMI4NBrAPEKoB7LNz7U3votTknm+RYqYeT+S9mIwqAxSyQ8VbfpGmLkswFCi?= =?us-ascii?Q?GJ5MpjHTlVX4NllGVzNYas03ATeldamEnGI9HHoNOLO4ZXN7AvYyLRhUmPVL?= =?us-ascii?Q?f1KPXSZL00uN+jlRsQ3VswN2Tct/lpdZe7M59l3gCI3SbsEpvc+hBYL8nKuU?= =?us-ascii?Q?KKaijYcHZMY+RZE3u9j8GtIDz/WIkTzvaQLGvYx7LZMmAw/Eg2W7/spQZFYe?= =?us-ascii?Q?I2/7CTb7ybgwBJCTGDX9hqtda6TIRCCRGDfmuzbeCVKQI6whQYtEsjJaYXL8?= =?us-ascii?Q?uXHhgFv8PKxkEGfd7jmR3IsLOq4yu7q97dVESu4usa9FDku22+SgQbm45lt2?= =?us-ascii?Q?+DiyDohERlXPUH15Ut86ovfOIsnllhmrsKqHRgmI5uE=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 637d8040-e7ae-4ed9-ff60-08d8b65da17a
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jan 2021 18:20:52.9841 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: eK7iwI58Wdy+GydITAuuwnfAE05FuaiLihVOiHb6zTyODRK6VZfhDsE4xGF8TcBC/IuAC/XJhUnUGfvDNJHfuPrHRGDAPTRIsBjLJP4pz3A=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3243
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/pNyH0OehA9-qVisXBpTTphkPMe0>
Subject: Re: [lamps] [EXTERNAL]Re: Mail regarding draft-ietf-lamps-cms-aes-gmac-alg-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 18:21:08 -0000

Hi Russ,

(changing the subject line as this is now feedback on the recommended tag l=
ength in draft-ietf-lamps-cms-aes-gmac-alg-02)

Happy Monday! With a bit more reading, we're still not convinced 12 octets =
(96 bits) is the right recommendation for AES-GCM's authentication tag leng=
th in 2021. You reference RFC 5084 (published 2007) which does indeed recom=
mend 12 octets in section 3.2. More recent IETF standards suggest using a 1=
6 byte ICV, for example IPSec (specifically RFC 5282, published 2008) secti=
on 3.2 says:

   The AES GCM ICV consists solely of the AES GCM Authentication Tag.
   Implementations MUST support a full-length 16 octet ICV, MAY support
   8 or 12 octet ICVs, and MUST NOT support other ICV lengths.

As another reference, we're looking at NIST SP800-131Ar2 (published 2019). =
Section 10 (MACs) does not provide any guidance for GCM tag length. Section=
 3 (Digital Signatures) requires 112 bits of security for signatures. Since=
 CRMF is using AES-GMAC, amongst other things, as a POP for obtaining certi=
ficates, we think it's reasonable to follow the digital signature strength =
requirements.=20

Therefore we think for the GMAC tag length, a better RECOMMENDED value woul=
d be 16 octets (to match RFC 5282).  A value of 14 octets would also meet t=
he digital signature recommendation in SP800-131Ar2 but may be a less commo=
n choice of GCM tag length. Is this a thing that CFRG could weigh in on?

---
Mike Ounsworth

-----Original Message-----
From: Mike Ounsworth=20
Sent: January 9, 2021 12:57 PM
To: Russ Housley <housley@vigilsec.com>
Cc: LAMPS <spasm@ietf.org>
Subject: RE: [EXTERNAL]Re: [lamps] Mail regarding draft-ietf-lamps-crmf-upd=
ate-algs-02

Thanks Russ!

I think those changes fully address our concerns.


One response:

>> 5a. Which brings us to a question about draft-ietf-lamps-cms-aes-gmac-al=
g; where did the recommendation for a 12 byte GMAC tag come from? Is that s=
upported by the referenced standards (NIST) or by an IRTF recommendation?

>This is for alignment with RFC 5084.  I was asked this so often that I add=
ed this information to the Implementation Considerations section of draft-i=
etf-lamps-cms-aes-gmac-alg.

Gotcha, thanks. Could you add that to your cms-aes-gmac draft just for the =
sake of an easy-to-follow citation chain? (I think 5084 is not currently in=
 the references list)

---
Mike Ounsworth

-----Original Message-----
From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
Sent: January 9, 2021 11:33 AM
To: Mike Ounsworth <Mike.Ounsworth@entrust.com>
Cc: LAMPS <spasm@ietf.org>
Subject: [EXTERNAL]Re: [lamps] Mail regarding draft-ietf-lamps-crmf-update-=
algs-02

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the =
content is safe.

Mike:

Thanks for the review and thoughtful comments.

> TL;DR: it would be great if this draft included a PBKDF2-based MAC (we su=
ggest PBMAC1 defined in RFC 8018). We also have a few general nit-picks abo=
ut the draft.

I think this is a good idea.  Before I add it, I would like to know whether=
 others agree or disagree.  More below.

> PBKDF2-based MAC
> ---------------
> In draft-ietf-lamps-crmf-update-algs you are updating the underlying prim=
itives inside 4211's id-PasswordBasedMac, but we note that the overall algo=
rithm is still PBKDF1-like, so in effect your draft is encouraging use of P=
BKDF1-SHA256-MAC or PBKDF1-AES-GMAC. This came up for us while going throug=
h a government crypto audit and having a FIPS-compliant PBKDF2-MAC in CMP w=
ould have made the audit easier.
>=20
> For backwards compatibility reasons you probably need to leave the PBKDF1=
-based 4211 id-PasswordBasedMac algorithm but with updated internal algs as=
 you've done, but can you also offer as an alternative the PBKDF2-based RFC=
 8018 PBMAC1? I think we're asking that in the ASN.1:
>=20
> ```
> PKMACValue ::=3D SEQUENCE {
> algId  AlgorithmIdentifier,
> -- algorithm value shall be PasswordBasedMac {1 2 840 113533 7 66 13}
> -- parameter value is PBMParameter
> ```
> the comment "-- algorithm value shall be PasswordBasedMac {1 2 840 113533=
 7 66 13}" also allow PBMAC1, as well as the corresponding parameter value =
type.
>=20
>=20
> The text in section 4.1 is already more tolerant, but explicitly mentioni=
ng (as a MAY) PBMAC1 as an alternative might make sense too:
>=20
> ```
> algId identifies the algorithm used to compute the MAC value.  All=20
> implementations MUST support id-PasswordBasedMAC.  The details on this=20
> algorithm are presented in section 4.4.
> ```
>=20
> We're working with Hendrik on draft-ietf-lamps-cmp-algorithms and it woul=
d be clean if we could reference PBMAC1 in your draft.

If the LAMPS WG agree with this approach, I would suggest an update to sect=
ion 4.1:

OLD

      algId identifies the algorithm used to compute the MAC value.  All
      implementations MUST support id-PasswordBasedMAC.  The details on
      this algorithm are presented in section 4.4

NEW

      algId identifies the algorithm used to compute the MAC value.  All
      implementations MUST support id-PasswordBasedMAC as
      presented in section 4.4.  All implementations MAY also support
      PBMAC1 presented in Section 7.1 of [RFC8018].


> Other general comments
> ----------------------
> 1. Section 3.2 - The change is "All implementations MUST support SHA-256 =
[SHS].", which used to require SHA-1.  I don't know how this is typically d=
one, but should your draft provide guidance on whether SHA-1 MAC is still s=
afe to be used in backwards compatibility scenarios?

I'd rather not see anything about SHA-1.  The situation for Certificate Req=
uest Message Format (CRMF) is not like S/MIME.  By that I mean, one will no=
t need to process a CRMF message many years later from an archive folder.  =
A CRMF message should not need to be validated after the requested certific=
ate is issued.

> 2. Section 3.3 - "A lower iteration count can be used, if automated gener=
ation produces shared secrets with high entropy".  We find the wording slig=
htly confusing; after several re-reads we think you mean "lower than 10,000=
", but someone doing a quick read might interpret "lower than 100". What is=
 your intent here?

I suggest:  As part of that tradeoff, an iteration count smaller than 10,00=
0 can be used when automated generation produces shared secrets with high e=
ntropy.

> 3. Section 3.4 - There is a typo in "When this The algorithm=20
> identifier is used" ("The" should be removed)

Thanks.  I'll fix it.

> 4. Section 5 - "Therefore, the entropy of the password is crucial for=20
> the security of password-based MAC function." should be "of the=20
> password-based MAC function." ("the" missing)

Thanks.  I'll fix it.

> 5. You're copying the GMACParameters ASN.1 from your draft-ietf-lamps-cms=
-aes-gmac-alg, including the recommendation to use 12 bytes as default GMAC=
 tag length. If at some point the recommendation changes to a larger value =
that would mean both documents need to be updated. Maybe better to leave th=
e recommendation out of this draft and only reference the aes-gmac-alg draf=
t?=20

Okay.

> 5a. Which brings us to a question about draft-ietf-lamps-cms-aes-gmac-alg=
; where did the recommendation for a 12 byte GMAC tag come from? Is that su=
pported by the referenced standards (NIST) or by an IRTF recommendation?

This is for alignment with RFC 5084.  I was asked this so often that I adde=
d this information to the Implementation Considerations section of draft-ie=
tf-lamps-cms-aes-gmac-alg.

Russ

_______________________________________________
Spasm mailing list
Spasm@ietf.org
https://www.ietf.org/mailman/listinfo/spasm


From nobody Mon Jan 11 15:33:07 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82ED23A141B for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 15:33:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X3_s-pgFG0Ot for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 15:33:04 -0800 (PST)
Received: from NAM04-BN8-obe.outbound.protection.outlook.com (mail-bn8nam08on2090.outbound.protection.outlook.com [40.107.100.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8AE53A1413 for <spasm@ietf.org>; Mon, 11 Jan 2021 15:33:04 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UAFK3sXp0BTvMrjqCayxuomrNyw8/ezT/nXI1a91os3/UaAjk1bHAWX0RUFiRUQjbApi8FvIc4oevNvEkeIVDBAvfX8cqmYIqN4IDQmhiVRZi4XOsejxV9UlVTzL3G/CrMKCV4Tdaxq/tK4WYp43msMz0mX5ydGd4Llg2GOdq2q4ma8KXjuyjXB/+grLV00y3jjoKQgAEpNOyeuZ9fFVSztC4d4gHtAVqG5uOoC3HH2AEqYezem/pxYSo4TLPknAnvegCa3q7RTM6pDWG7PbRjMwRInQCPrPoivRUaeEg+lGsXyZVYKJbIqrKDW7f5K6BbV6JeD5iyjnSH2fYFGV6w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BvdMEsfZDeAvsIe9TuRgH3FBeHcdLZ0jMkrBbanhSsA=; b=klI90Azw4yv+OQ5a5JdVsCqF+l7KcVrv6KvD1ScgeWz3tg+oNuztb2lzk8/GuhjjaZcu42QXl+xP6/NBVFXOe+mGo9lUtXclEX+9Nl7O1+XVB5hvfKumuhc3e2jMzZ2nbb5/6+ZzMaUijL8CszJC9nVZWj6mDKEeI7yEgCD8wveHo6P5HPgXKIv+2EObd8e6Ps/iJxyf7VZfSQj0xRk6bNU8F8VXFtTmxHtKT7hfriND/zXrkY0Tb7kayypa3Zl0rNlzKJm4bROGSLUTKrtvCrzhm2EMDG9ghomLwYlx5D8+0Wy/rMcDALDV8Joo6qsE39ayIdpyCHcRnAIezG512Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BvdMEsfZDeAvsIe9TuRgH3FBeHcdLZ0jMkrBbanhSsA=; b=QQJx4mNe7kM6N7pslPqFmJ6WtAz9hd4FIgN1F799BvY+We11Wc2YvcY9hFbRhzhsxGuKukiK4N9ZZ0AFcxG4QSLSicgQq0/nhbvAqYwMt+2QJlL8usbMDS5jBVG547Enq5XPV3W/7mlCU1miLu2nKpoEs9KZYPQemUWSryGvPjosglmKO9pYZZPnsn/osmVMapmVadcvn/XOcxufWB0fndWt6GwkOg3/gH7BZ6f+bIEbYOSzsowoUhDBfKvVGHHP5xwL28wgq1tf/BuROg6yk5qN+9DpMixKyoTvtZK71yiI45YdQNRXvL/vHBrZb/O8fRIs4MAH9NJUt7BWpzaPGA==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB3660.namprd11.prod.outlook.com (2603:10b6:5:13c::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Mon, 11 Jan 2021 23:33:03 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.012; Mon, 11 Jan 2021 23:33:03 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Russ Housley <housley@vigilsec.com>, LAMPS <spasm@ietf.org>
Thread-Topic: [EXTERNAL][lamps] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
Thread-Index: AQHW5riHlQyD8EZZlECnX0UCU/+wHqojD0aw
Date: Mon, 11 Jan 2021 23:33:02 +0000
Message-ID: <DM6PR11MB43804A64358FB9D3684FD8129FAB0@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com>
In-Reply-To: <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [204.124.81.16]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 86eee0d8-5682-4a90-1703-08d8b6893d6b
x-ms-traffictypediagnostic: DM6PR11MB3660:
x-microsoft-antispam-prvs: <DM6PR11MB366061ECDD9BB495AF80337A9FAB0@DM6PR11MB3660.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 340v6Aodqw3TdxDXMNgpkodgjQr1lM20L5Qvqjwy/NOVk3DaSkx8EhMbCvfL92mfAd63DD5nvqZhzZ34GO/5sHn71Ds4iQvp3mEjcEzf7Hv33DY/rvjG/9Wp2tqL2ipGMjU/ognXc4rRx+I1f5WhjXVMretbDOtobnY3T8ut47yLtweN9A8kl1SLnPczuP7HL8e2SMD3/wDwoe/eqoTPn4oDudzm6C/FXekeRhcWFswUfZ7bfWiYr9pVviIMhBlbp+Y90eC9FaG3IECNFaLGR8SeN0z0djgu7Bi8tW8BS6pZibcb4dr6bK7mSB2J0AFONf8mwDiO036gm93kGs6wBfI90mBpVbX5+2CVJyZU1DtH+9wXagRcgeFHk8z7VhjyrRi/vFroKrjtnKuk7sKGPsBWCaNo0a8JkQeGg0+aa2OmDwG42LLKu5ZUxekVUM0Q01OcSAbDVPLB/5qcdq4gVUhjsHtb4xgzMZQ5oM72XH6Vi5l4ISRG1XyYlMJjLzEHLX1GPkstB3VMNUg81ZPIMQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(346002)(136003)(366004)(396003)(39860400002)(316002)(66446008)(6506007)(8936002)(966005)(71200400001)(64756008)(53546011)(66476007)(86362001)(83380400001)(66556008)(186003)(52536014)(5660300002)(8676002)(33656002)(83080400002)(2906002)(55016002)(9686003)(7696005)(26005)(478600001)(110136005)(76116006)(66946007); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?UBld5hktBmc8NCe8vRibeXGgTzb/UbpOedZ36sFXwN/YQXg7FdP0DxoRVOod?= =?us-ascii?Q?jFg1h+8lwMKc7oSXoOqzp4a6a+h26VY+kYzJ1ght6Tfr6+7eOCyq9p5QJD7l?= =?us-ascii?Q?BiQ9DMxfPpLMh5E243+byElu8pIljcNk7V3sVwoXDjwIoKGhF+WEHJcuF/4J?= =?us-ascii?Q?l01KedTo2tioDpP/OdUkNem1dpqKeYLnmf3FDT2QGdVpUJvSbHUvKk6YpU4m?= =?us-ascii?Q?wd4DYOlqAA+MRaI3oOTgD2g95mAjDwnBIrKzYXtdbH6LRCUQlnSPhOoGN4r2?= =?us-ascii?Q?6JCQWUDr2tKfTWi3juFeXNT60xzcVFrsppeKidTsQKt1xIUvcPbzUZf7aDX9?= =?us-ascii?Q?bonLW71I3ClLvcOAXEUo09SolKGqRlg4h6PZtAUWZ1ZQyQfi7gD9Ejac8ceD?= =?us-ascii?Q?BTjPXOCSdNacA+o/S0Qwic5OVUsI+LxW65XFVbnJQZirpCUpfslYMj9cT8hN?= =?us-ascii?Q?KXdGKBAXMgcdEqxbbBTxh2azRwAA5UcPMbPe7Okit7pGPiV7v1gCayQDZWB/?= =?us-ascii?Q?SPsgeLw82/f5m+I2PfnWAIJ5muOjQpBaYg5T7Nf/GsErN+mNoz6Hng++wV+P?= =?us-ascii?Q?irqADwjIDkd4wbB6So7PvrnffVOxemfee6Lt5LzEXLZwu9HQ9wLG7ss+XLAJ?= =?us-ascii?Q?T50koqUAO5Rt4VQ4JQgbn5Ncw+hbKbDZEvbGaM821UhwDADHCnRbJM8oYwIg?= =?us-ascii?Q?E0vL2UscgS44aRqn2SS4fdk6aIkcMpa0Vs0+SGz4ZZ2ccgFOdXgKEpnMLjhY?= =?us-ascii?Q?bvUdIPQii0rmpHxtupGG9R5Ym/uhUeTm7UBMSUBhrfSB1Nl0qsXRGo6esxi2?= =?us-ascii?Q?fUGw9txeX8j3KoIL80btmRnrrOC9u38dx+ZYs2Hy2vvhXLuyw+QCzuos7CES?= =?us-ascii?Q?tiPsjSwMpyCkezOHM3Z5/pE/ksmZYEu5R6Rcor8zgYscYkbklh0tKJZQx7Fh?= =?us-ascii?Q?9FRN6gLs/E55yuLbPl5Zi/pBwVMM8/zggNG/bJB2NoE=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 86eee0d8-5682-4a90-1703-08d8b6893d6b
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jan 2021 23:33:02.9158 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tWE9XGK6/a1whvJMN9GWfiF5xeXY0DhBakYmb6yZ2c/Em2OY/rdRDPZNtQ6EOSmiSXuzGwth9PV0YYabu6RwSjFFiEacyNdofzwHDcdFbuA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3660
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/XK_1mo9QV46QQ7g2lFsvOrlySLQ>
Subject: Re: [lamps] [EXTERNAL] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 23:33:07 -0000

Hi Russ,

Your slides refer to

Has known pitfalls of the "jumbo" certificate, which carried a key agreemen=
t public key and a signature public key for the same user"=20


Was that from the 1997 PKIX mail list thread titled "Combo DSS/ElGamal keys=
" ? If so, the objections I'm seeing were mostly to do with mixing key usag=
es -- ex.: nonrepudiation and key transport keys potentially having differe=
nt key policies like validity period or private key escrow. Or the argument=
 that revoking the keyex key due to, for example, bungling the backup copy =
would have the side-effect of invalidating any signatures produced by the s=
igning key which would not have been part of the backup.

You may need to expand a bit on which arguments from that thread apply to C=
omposite where all component keys must have the same keyusage and are inten=
ded to be used as an atomic object for producing composite signatures.

---
Mike Ounsworth

-----Original Message-----
From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
Sent: January 9, 2021 12:52 PM
To: LAMPS <spasm@ietf.org>
Subject: [EXTERNAL][lamps] Call for Presentations at the LAMPS Interim Meet=
ing on 28 Jan 2021

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the =
content is safe.

I gave this presentation at the NIST NCCoE Virtual Workshop on Consideratio=
ns in Migrating to Post-Quantum Cryptographic Algorithms: https://www.nccoe=
.nist.gov/sites/default/files/10-Housley-NCCoE-Workshop-Transition-to-PQC-C=
ertificates.pdf

This short presentation still captures my view.  Are there people with a di=
fferent view that would like time on the agenda at the LAMPS Interim on 28 =
Jan?  I would like to make sure that all point of view are heard.

Russ

_______________________________________________
Spasm mailing list
Spasm@ietf.org
https://www.ietf.org/mailman/listinfo/spasm


From nobody Mon Jan 11 22:26:42 2021
Return-Path: <tadahiko.ito.public@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87E443A10FF for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 22:26:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTXYKS_rbCwv for <spasm@ietfa.amsl.com>; Mon, 11 Jan 2021 22:26:39 -0800 (PST)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AAE83A10DC for <spasm@ietf.org>; Mon, 11 Jan 2021 22:26:38 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id u17so1821494iow.1 for <spasm@ietf.org>; Mon, 11 Jan 2021 22:26:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=sJmramdRH2NrCDvCJ2a/4YYdGIoIeZ4NQGCEjVERfPI=; b=i8ziEf0kKdlMl4t/JczlX3OEdXc7EA5m3zPkJuvfWOjllGRnhD3CDJDUgQAjFZdULQ TtHl3ykNtuc+S4Tl9NNY1ju1a4Is+USdHA3nYqQtYz2Y7AlNKwPLoAxfaCvjs3Y5Ee7Y ydwzuKLM349adFWRBIvUVibK7xNdq/TdvtmEFv9EHJXiKK7BA8Hx2tlAxLTUPYrwbeGp WF9TaQ1Zn8jefdcxaIiz9Qmh9Fs5ZDT93F5uLK+bjbqnS0V5ykGXeRGXjv1Ti6f11tQS JQrPNAsagM7tcyp0uuvYxh29yGxAshWP9pZunsHpDC2BE2EZuBsSBIfzCkzTrPpsS3JH vM3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=sJmramdRH2NrCDvCJ2a/4YYdGIoIeZ4NQGCEjVERfPI=; b=uQFtcnNm1FCxgHPhIvBkEBESlKJNuUkGuhV6eOfaBp2opFNRUQibDfDN4rsYgbhb0O O7zNN66aRR1ukyhhzI4C/KZkKeV6TLvcVOijGDg4PxiehVU9nV01YdXyUsV0ko4tdG/b n7Hmk+JBUpU2hY7r/i2xEppYUtBe7xQpNPzGxwncxxW52VDHLI2QXCrWbWAkF4x86tSH BC+O+mw+svRON6+F484aJU+LHgQRvXp1Se+nSZXHzo/d7WZzQHO7qrAlUF3ESEVQMBqm okLSDbfhXQA+MBaNGxg3AjOsuHHSSA+3ikC9zuo7x30p63A0rpAZvoNRYMh2VnolQ306 Vynw==
X-Gm-Message-State: AOAM5335yMJm/2W58ufVB5Qv6b/981wke83/Opy03FMPHwj5M4UX0Fu7 q2sdP9qtwOTg4Rl5qjz1AU8QrLitZL4QHLQtaHKpZbMJ93U=
X-Google-Smtp-Source: ABdhPJyL2AQOlR0WPePsG5IYKuaX83yr+tYG5B1JLdL/J/hNhnIjXBF6huwu+ut9jWXlk6hjcQICiV5gWIjEH0n7PL8=
X-Received: by 2002:a92:ce92:: with SMTP id r18mr487711ilo.60.1610432797915; Mon, 11 Jan 2021 22:26:37 -0800 (PST)
MIME-Version: 1.0
From: Tadahiko Ito <tadahiko.ito.public@gmail.com>
Date: Tue, 12 Jan 2021 15:26:26 +0900
Message-ID: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: LAMPS WG <spasm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dac0ee05b8ae1ae4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/WcXW8jYE6f8p-2VxJpRmtduK8Bc>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 06:26:41 -0000

--000000000000dac0ee05b8ae1ae4
Content-Type: text/plain; charset="UTF-8"

Hi Russ



I also want to talk a bit about separation of hash and asymmetric function.

It seems we cannot separate those functions in some PQC algorithms.

In current RSA or ECC, we use data control service to calculate hash
function part, and use key management service to calculate asymmetric
function part for large file.


For instance, we (our company) currently have a usecase of signing 10GB PDF
file (with HSM). Separation of those functions is necessary for such a
usecases according to limitation in HSM resource.



It would be OK if we introduce one more hash function to signing data, but
I believe it may damage interoperability. I would like to ask what we
should do in such a usecase.



My draft paper is following (it is a draft, we are not sure if we can
revise before the meeting)

<https://eprint.iacr.org/2020/990>



Regards Tadahiko Ito

--000000000000dac0ee05b8ae1ae4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><p class=3D"MsoNormal" style=3D"margin:0m=
m;text-align:justify;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=
=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US">Hi Russ<span></span></span=
></p><p class=3D"MsoNormal" style=3D"margin:0mm;text-align:justify;font-siz=
e:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><s=
pan lang=3D"EN-US"><span>=C2=A0</span></span></p><p class=3D"MsoNormal" sty=
le=3D"margin:0mm;text-align:justify;font-size:10.5pt;font-family:=E6=B8=B8=
=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US">I also want=
 to talk a bit about separation of hash and asymmetric function.<span></spa=
n></span></p><p class=3D"MsoNormal" style=3D"margin:0mm;text-align:justify;=
font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,=
0,0)"><span lang=3D"EN-US">It seems we cannot separate those functions in s=
ome PQC algorithms.<span></span></span></p><p class=3D"MsoNormal" style=3D"=
margin:0mm;text-align:justify;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=
=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US">In current RSA or=
 ECC, we use data control service to calculate hash function part, and use =
key management service to calculate asymmetric function part for large file=
.<span></span></span></p><p class=3D"MsoNormal" style=3D"margin:0mm;text-al=
ign:justify;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;=
color:rgb(0,0,0)"><span lang=3D"EN-US"><br></span></p><p class=3D"MsoNormal=
" style=3D"margin:0mm;text-align:justify;font-size:10.5pt;font-family:=E6=
=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US">For i=
nstance, we (our company) currently have a usecase of signing 10GB PDF file=
 (with HSM). Separation of those functions is necessary for such a usecases=
 according to limitation in HSM resource.<span></span></span></p><p class=
=3D"MsoNormal" style=3D"margin:0mm;text-align:justify;font-size:10.5pt;font=
-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"E=
N-US"><span>=C2=A0</span></span></p><p class=3D"MsoNormal" style=3D"margin:=
0mm;text-align:justify;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=
=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US">It would be OK if we in=
troduce one more hash function to signing data, but I believe it may damage=
 interoperability. I would like to ask what we should do in such a usecase.=
<span></span></span></p><p class=3D"MsoNormal" style=3D"margin:0mm;text-ali=
gn:justify;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;c=
olor:rgb(0,0,0)"><span lang=3D"EN-US"><span>=C2=A0</span></span></p><p clas=
s=3D"MsoNormal" style=3D"margin:0mm;text-align:justify;font-size:10.5pt;fon=
t-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"=
EN-US">My draft paper is following (it is a draft, we are not sure if we ca=
n revise before the meeting)<span></span></span></p><p class=3D"MsoNormal" =
style=3D"margin:0mm;text-align:justify;font-size:10.5pt;font-family:=E6=B8=
=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US">&lt;<a h=
ref=3D"https://eprint.iacr.org/2020/990">https://eprint.iacr.org/2020/990</=
a>&gt;<span></span></span></p><p class=3D"MsoNormal" style=3D"margin:0mm;te=
xt-align:justify;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,s=
erif;color:rgb(0,0,0)"><span lang=3D"EN-US"><span>=C2=A0</span></span></p><=
p class=3D"MsoNormal" style=3D"margin:0mm;text-align:justify;font-size:10.5=
pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span la=
ng=3D"EN-US">Regards Tadahiko Ito<span></span></span></p></div></div>

--000000000000dac0ee05b8ae1ae4--


From nobody Tue Jan 12 07:23:32 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A152E3A00C4 for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 07:23:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WCpww0uuRkl2 for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 07:23:29 -0800 (PST)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760110.outbound.protection.outlook.com [40.107.76.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 748AC3A00D2 for <spasm@ietf.org>; Tue, 12 Jan 2021 07:23:07 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DJqgPw3p7uEVjx32U0elJ6V6cgO6/NT1RKFYSNNlAxg2Y3R6PflOKFTFNUPHgWEnyDkICJd51pElMiKsVrlSdkt0/BzK4L74VZaVYhKCQR/dQtm7Fqd3PeAcONEJkcnZqINWxcvEkSfShcWKRPltaiEYWPJSaFWyvsXpcNYBYlHoM8iOwKOdqhHRnP2PdBFTNQPhrCwEfVnscqEOgxBRY0YEeStgG8Jqejsm2mDmJuXBCuMJKcQ+g821CVni/gKJfmv6mFA568B1YHDmRBMKr5LkJvkA5ZoW4i4JPni04LC16OS7mI01qpvhVEEgU7oq0UN3KDb2l23JD8qvFUeeBg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BhXAoRHWyzJrwY9rg5Mva4jDmxbV6PHVRclnM4sZFMg=; b=c/g+FnMpA7FvZ2kkIpzMAqPNH97fCxQH5X99iNt6xDwziC3WL+bCnS3NGJHhLx377OM4nZu0BTrHnYxJMbyC2RxqWCfr/bfLf7FK9/Zrf0WXs8xVt7gpYUTH5Sy03NAUx/CfCbAOT9jMV0/vJaKDoITC9KJLNKO/rClroLr95AILWCmV7x3RlGGG2D7aMdAgKBQaR7lKRiuCD2LdXgkyPlfVgwqyREBFfLcZo8YnHW8Dy4BSCywq3knH1FC4P6IBhmGVsto8U8WemVnFmNxLStOxo8JIZXKjHMRz107Y5Efwm2HSE6I0Y0nyQZiDYtXwe+vTmhI9CIpNkmZwxXXSxQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BhXAoRHWyzJrwY9rg5Mva4jDmxbV6PHVRclnM4sZFMg=; b=t5aHt3oksRWL51EgsFahd9PJzkzI6QLu29kxx8E1cYjkTEA0EigLAl9Kz6GxlguX1LN3k6Jh/v0sDHPeVcB6H1ulJTdAseQg1cP2BRwI4ZQOUzPxIPyUJByM7gkusPF7UMFbXB2GhgJk4+s2LyXBFDcYbIybBAMIopSrp0X7oX5ZBZb7U2Sg7QV6/3XUGYgvX6F179iMyHbKLTzzNorl7QfO6CYU69KXlIcYc/EdArSbpxb5rOnoU+ZqBN1VCkaC7QRT2jpTH2EHxtLH00roJD6o3jLL5qmkRD/HOW1+pf3sCSqThttQDxuDdMsxgotYlp7BXfg803e1y6ajQyI1ng==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB3722.namprd11.prod.outlook.com (2603:10b6:5:13b::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Tue, 12 Jan 2021 15:23:02 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.012; Tue, 12 Jan 2021 15:23:02 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Tadahiko Ito <tadahiko.ito.public@gmail.com>, Russ Housley <housley@vigilsec.com>
CC: LAMPS WG <spasm@ietf.org>
Thread-Topic: [EXTERNAL]Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
Thread-Index: AQHW6Kvt9c0igidFKU6Q1BVUJlGHjaokF64A
Date: Tue, 12 Jan 2021 15:23:02 +0000
Message-ID: <DM6PR11MB4380102AE9E9FD8B1D6BC5BB9FAA0@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com>
In-Reply-To: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [72.139.200.247]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d77d4b2a-c758-4d5e-0d3f-08d8b70df3ea
x-ms-traffictypediagnostic: DM6PR11MB3722:
x-microsoft-antispam-prvs: <DM6PR11MB3722987C5B25FBB499EB39A39FAA0@DM6PR11MB3722.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +gxOS1ZpMuQrLWPLLzSNwzoXoaJ9pW+xx+Fw3XoJgd2q8qMIwsuE7F1229cXYzflO5nQR0jls4g8UaL0GxxpSm7KnPGcyXYuod+Fewx8qpoexPXNjfYv6ZltxIeoX1H1bLnihe9grFVwv1dDrfXA1Kzr21mBJZkHkdCrgCxq0liQ+PnC9ohXxRQeReaJU0dYIzHbd2HoJsG5EnwTKgFLABnyXvkODuAi91e81E+K1T5GTCJTRI1Fqr7Pb5u4BMkjBswzFxPiwKA4j3/0YULcZyJjqQ9pTiYrO3uNhqu6mI2WG27SKsYTrmqS/eFC0cvRBltB1JOk7MldThrwpE4rwRhSjVvhAlIgaHsvD4y9mqoXJSv8s1XNZ9OESBVm3m+iZRxjgiGU6HOoa0kxzmJjGHyqa8HKN5kGsHZ7vdw6SR50gx1ZGcmZBazuOhXbiZZfaMIB1SGG9ZlsKWqE7qBqAA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(39860400002)(136003)(396003)(346002)(366004)(26005)(52536014)(55016002)(316002)(66476007)(9686003)(478600001)(6506007)(33656002)(66946007)(186003)(110136005)(5660300002)(71200400001)(4326008)(66556008)(76116006)(2906002)(8676002)(7696005)(66446008)(64756008)(8936002)(86362001)(53546011)(83380400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?bGJUYytZL1NpZlRHMDFQQnVKLzBndkJoZC9WUG1UQnp3TW91bS9aQmdIbVU0?= =?utf-8?B?OTNoUmgwSFovV25sNXpEenlOdHBvN0d2SFBScmtBWFJuVXhtVkpXY0dIVHJi?= =?utf-8?B?a05wVmlkWU1IRUxTOWhCOEdwWEhyRCtTaHdub05UMFJBYmZFODV4dW9MMWRz?= =?utf-8?B?VUhBZVE5eHFWVXFtYXV0RXVEQ2trOW9XbCtVOE1Xa2dmSTFWQXM5R3dSajFl?= =?utf-8?B?ekdCNllvYU8vN20wZnlhSnZXbmpRU3JST1VZZmpCZEJFcVJNV0c5YXRQU0tW?= =?utf-8?B?MTN0bGtxMVIzbUxCTVN3UlVmMmliWi9TTzAzK1hBYjNUSDVsZXdZRUtRZy9C?= =?utf-8?B?NVdaYjdod0dpRzhSOFNieGFDeW5rek1tR0hiYmRDU1RmNHRtUXh3Qk1abk1T?= =?utf-8?B?cUlYREUyUi94ME5aU1RpNlRBTzJva0FjSUxTK2sxaDYvTXQyVFc4UHNjbjhM?= =?utf-8?B?RmdMZnBCMHE0b0dncHVhTW5ncWV0Zmk3cTFrMUQyZWJpeGdxRWtQajJHZFpn?= =?utf-8?B?MC9qZ2VrSlQxOVArbkdGbEZ4RkxTR3JYTElWMVFadmdvaGlEUUQ4M1g4RlBQ?= =?utf-8?B?ZEhneGRMR2hUWnNXSWFxY01qK0l4dlNYMjJSWmJ2QTlvZ0U2STdrTFk0Ryta?= =?utf-8?B?SDNsTmZ3THZYaUVZRmcvSUFoa01wUituK3pHQ3ZDWUhqQWYvT1Y4cFB3YU1R?= =?utf-8?B?YzhaTFFZWlUwczkwc2FRd282WFFzaHYrMGZyNDZldDFDNmJzYnpzcDVPZU5I?= =?utf-8?B?UTNvUFF0UWFkYXp2TnlndUEwQVlqdTlrRk96cUdIZVdzcUh2cVBlbGs1THJH?= =?utf-8?B?WXRGQXhtcTRDWTRtK2N6aEcyL2paNm4xVkIzdXptbHk3VzRuK25wbXZKVWNt?= =?utf-8?B?L3B6SXpwbXBCSGJzeXRBK0xvdUFOS1RsUDNOSm13QXBIb3ZjTGVIVnMrL2Y1?= =?utf-8?B?VkFaL2g4SUxjNlhFb29TeXR4R2pVVTZVNUUveGl1WmZPRFFEdTVRVkp1WEJZ?= =?utf-8?B?emJKRC9zNEFSRWZQTEJBZEZTYlRkUE5MbXM5eGxsSlVrc3Nod2pKQ2l2Z1BE?= =?utf-8?B?dFpJL1RWeUpVWWdLMDkzNENhWDA1QjE4TTY4MS92R241ZTR6UjUzejl0cEJt?= =?utf-8?B?MnpVRlVmaDFDY1J6U0I4aWRiOE9mdzdualFHakcwekxCdElWUU1lbU9VZ1RK?= =?utf-8?B?RXRHYy9RTDgyMmhYT1phOVBhWlAxR2hKV05ZWEJuamNlc0h4ZGRLY0V4S3Br?= =?utf-8?B?VjhNdzF2aUNwcTNtTjVSRm9wUGQramFVMUlreFhZaWh4L1RQbkhQanl5SEdD?= =?utf-8?Q?/8gFlTfs5Ps+A=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d77d4b2a-c758-4d5e-0d3f-08d8b70df3ea
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2021 15:23:02.6845 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /5BIHbcliNwK6NDV+Yf/RB3suBy/tiCalnZrk92Y6bcfNXG0pYv7ebQmKtmPDQSlNriZcyiKTw9tkUcFn8iAXG4fWPWR+sb3Zsh5EulAXow=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3722
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/WwPNerstnYTAbIeqTgsCxb5Yd-M>
Subject: Re: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 15:23:31 -0000

SGVsbG8sDQoNCkkgd2FudCB0byBoaWdobGlnaHQgdHdvIGV4Y2VsbGVudCBwb2ludHMgdGhhdCB5
b3UgbWFrZSBpbiB5b3VyIHBhcGVyOg0KDQoxLiBVc2luZyBhIGZpeGVkLWxlbmd0aCBoYXNoIHZh
bHVlIGluIHBsYWNlIG9mIHRoZSBtZXNzYWdlIG1heSBhZmZlY3QgdGhlIHNlY3VyaXR5IHByb29m
IG9mIHRoZSBhc3ltbWV0cmljIGFsZ29yaXRobSwgc28gdGhpcyBwcm9iYWJseSBuZWVkcyB0byBi
ZSB2YWxpZGF0ZWQgYnkgY3J5cHRvZ3JhcGhlcnMgZm9yIGVhY2ggUFFDIGFsZ29yaXRobS4gSXQg
c2VlbXMgZnJvbSB5b3VyIHBhcGVyIHRoYXQgcVRFU0xBIGlzIGFscmVhZHkgY29tcGF0aWJsZSB3
aXRoIHRoaXMgbW9kZS4gSSBpbWFnaW5lIGhhc2gtYmFzZWQgc2lnbmF0dXJlcyB3b3VsZCBhbHNv
IGJlIG9rIHdpdGggcHJlLWhhc2hpbmcuIERvIGFueSBvdGhlciBQUUMgc2lnbmF0dXJlIGNhbmRp
ZGF0ZXMgaGF2ZSBwcm9vZnMgdGhhdCBwcmUtaGFzaGluZyBkb2VzIG5vdCBhZmZlY3Qgc2VjdXJp
dHk/IEkgaW1hZ2luZSB0aGF0IGRpZmZlcmVudCBwYXJhbWV0ZXIgc2V0cyAvIHNlY3VyaXR5IGxl
dmVscyBvZiBhIGdpdmVuIFBRQyBhbGdvcml0aG0gbWF5IG5lZWQgZGlmZmVyZW50IGxlbmd0aHMg
b2YgcHJlLWhhc2ggaW4gb3JkZXIgdG8gcHJlc2VydmUgc2VjdXJpdHkgbGV2ZWwuDQoNCjIuICJJ
biBhZGRpdGlvbiwgaXQgaXMgaGFyZCB0byBzYXkgdGhhdCB0aGVyZSBpcyBubyBwb3NzaWJpbGl0
eSB0aGF0IGEgbmV3IHBhdGVudCByaXNrIHdpbGwgb2NjdXIgZHVlIHRvIGNoYW5nZXMgb24gdGhl
IHVzZSBvZiBoYXNoZXMuIg0KDQoNCkkgd291bGQgc3VwcG9ydCBMQU1QUyBsb29raW5nIGF0IHRo
aXMsIHRob3VnaCBpdCBwcm9iYWJseSBuZWVkcyBpbnZvbHZlbWVudCBmcm9tIG90aGVyIGdyb3Vw
cywgZXNwZWNpYWxseSBvbiB0aGUgc2VjdXJpdHkgcHJvb2Ygc2lkZS4NCg0KLS0tDQpNaWtlIE91
bnN3b3J0aA0KDQpGcm9tOiBTcGFzbSA8c3Bhc20tYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxm
IE9mIFRhZGFoaWtvIEl0bw0KU2VudDogSmFudWFyeSAxMiwgMjAyMSAxMjoyNiBBTQ0KVG86IFJ1
c3MgSG91c2xleSA8aG91c2xleUB2aWdpbHNlYy5jb20+DQpDYzogTEFNUFMgV0cgPHNwYXNtQGll
dGYub3JnPg0KU3ViamVjdDogW0VYVEVSTkFMXVJlOiBbbGFtcHNdIENhbGwgZm9yIFByZXNlbnRh
dGlvbnMgYXQgdGhlIExBTVBTIEludGVyaW0gTWVldGluZyBvbiAyOA0KDQpXQVJOSU5HOiBUaGlz
IGVtYWlsIG9yaWdpbmF0ZWQgb3V0c2lkZSBvZiBFbnRydXN0Lg0KRE8gTk9UIENMSUNLIGxpbmtz
IG9yIGF0dGFjaG1lbnRzIHVubGVzcyB5b3UgdHJ1c3QgdGhlIHNlbmRlciBhbmQga25vdyB0aGUg
Y29udGVudCBpcyBzYWZlLg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KSGkgUnVzcw0KwqANCkkgYWxzbyB3YW50IHRvIHRhbGsgYSBiaXQgYWJvdXQgc2VwYXJhdGlv
biBvZiBoYXNoIGFuZCBhc3ltbWV0cmljIGZ1bmN0aW9uLg0KSXQgc2VlbXMgd2UgY2Fubm90IHNl
cGFyYXRlIHRob3NlIGZ1bmN0aW9ucyBpbiBzb21lIFBRQyBhbGdvcml0aG1zLg0KSW4gY3VycmVu
dCBSU0Egb3IgRUNDLCB3ZSB1c2UgZGF0YSBjb250cm9sIHNlcnZpY2UgdG8gY2FsY3VsYXRlIGhh
c2ggZnVuY3Rpb24gcGFydCwgYW5kIHVzZSBrZXkgbWFuYWdlbWVudCBzZXJ2aWNlIHRvIGNhbGN1
bGF0ZSBhc3ltbWV0cmljIGZ1bmN0aW9uIHBhcnQgZm9yIGxhcmdlIGZpbGUuDQoNCkZvciBpbnN0
YW5jZSwgd2UgKG91ciBjb21wYW55KSBjdXJyZW50bHkgaGF2ZSBhIHVzZWNhc2Ugb2Ygc2lnbmlu
ZyAxMEdCIFBERiBmaWxlICh3aXRoIEhTTSkuIFNlcGFyYXRpb24gb2YgdGhvc2UgZnVuY3Rpb25z
IGlzIG5lY2Vzc2FyeSBmb3Igc3VjaCBhIHVzZWNhc2VzIGFjY29yZGluZyB0byBsaW1pdGF0aW9u
IGluIEhTTSByZXNvdXJjZS4NCsKgDQpJdCB3b3VsZCBiZSBPSyBpZiB3ZSBpbnRyb2R1Y2Ugb25l
IG1vcmUgaGFzaCBmdW5jdGlvbiB0byBzaWduaW5nIGRhdGEsIGJ1dCBJIGJlbGlldmUgaXQgbWF5
IGRhbWFnZSBpbnRlcm9wZXJhYmlsaXR5LiBJIHdvdWxkIGxpa2UgdG8gYXNrIHdoYXQgd2Ugc2hv
dWxkIGRvIGluIHN1Y2ggYSB1c2VjYXNlLg0KwqANCk15IGRyYWZ0IHBhcGVyIGlzIGZvbGxvd2lu
ZyAoaXQgaXMgYSBkcmFmdCwgd2UgYXJlIG5vdCBzdXJlIGlmIHdlIGNhbiByZXZpc2UgYmVmb3Jl
IHRoZSBtZWV0aW5nKQ0KPGh0dHBzOi8vZXByaW50LmlhY3Iub3JnLzIwMjAvOTkwPg0KwqANClJl
Z2FyZHMgVGFkYWhpa28gSXRvDQo=


From nobody Tue Jan 12 07:42:47 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 003133A0965 for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 07:42:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OMXt1cDmRWUg for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 07:42:43 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23C6A3A0964 for <spasm@ietf.org>; Tue, 12 Jan 2021 07:42:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 80084300BA8 for <spasm@ietf.org>; Tue, 12 Jan 2021 10:42:40 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id iaauNzf64qkc for <spasm@ietf.org>; Tue, 12 Jan 2021 10:42:39 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 0139D300AE5; Tue, 12 Jan 2021 10:42:38 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DM6PR11MB43802E75B2A922D1B7BC71DC9FAB0@DM6PR11MB4380.namprd11.prod.outlook.com>
Date: Tue, 12 Jan 2021 10:42:40 -0500
Cc: LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <26EF8FB4-EA0F-4B4E-AC5A-D8B31110936A@vigilsec.com>
References: <DM6PR11MB43802E75B2A922D1B7BC71DC9FAB0@DM6PR11MB4380.namprd11.prod.outlook.com>
To: Mike Ounsworth <Mike.Ounsworth@entrust.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/g1-09MkwebIO3kI0T2sY5nBF2JM>
Subject: Re: [lamps] [EXTERNAL]Re: Mail regarding draft-ietf-lamps-cms-aes-gmac-alg-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 15:42:45 -0000

Mike:

This document is with the IESG.  IETF Last Call has not started yet, but =
I'll treat this as a Last Call comment when it does start.

My opinion is that we should not prevent anyone from using all of the =
Tag size choices.  CMS is used in many different contexts.  I would be =
supportive of requiring an implementation to support tags of 12 and 16 =
octets.

Russ


> On Jan 11, 2021, at 1:20 PM, Mike Ounsworth =
<Mike.Ounsworth@entrust.com> wrote:
>=20
> Hi Russ,
>=20
> (changing the subject line as this is now feedback on the recommended =
tag length in draft-ietf-lamps-cms-aes-gmac-alg-02)
>=20
> Happy Monday! With a bit more reading, we're still not convinced 12 =
octets (96 bits) is the right recommendation for AES-GCM's =
authentication tag length in 2021. You reference RFC 5084 (published =
2007) which does indeed recommend 12 octets in section 3.2. More recent =
IETF standards suggest using a 16 byte ICV, for example IPSec =
(specifically RFC 5282, published 2008) section 3.2 says:
>=20
>   The AES GCM ICV consists solely of the AES GCM Authentication Tag.
>   Implementations MUST support a full-length 16 octet ICV, MAY support
>   8 or 12 octet ICVs, and MUST NOT support other ICV lengths.
>=20
> As another reference, we're looking at NIST SP800-131Ar2 (published =
2019). Section 10 (MACs) does not provide any guidance for GCM tag =
length. Section 3 (Digital Signatures) requires 112 bits of security for =
signatures. Since CRMF is using AES-GMAC, amongst other things, as a POP =
for obtaining certificates, we think it's reasonable to follow the =
digital signature strength requirements.=20
>=20
> Therefore we think for the GMAC tag length, a better RECOMMENDED value =
would be 16 octets (to match RFC 5282).  A value of 14 octets would also =
meet the digital signature recommendation in SP800-131Ar2 but may be a =
less common choice of GCM tag length. Is this a thing that CFRG could =
weigh in on?
>=20
> ---
> Mike Ounsworth
> nks.  I'll fix it.
>=20
>> 5. You're copying the GMACParameters ASN.1 from your =
draft-ietf-lamps-cms-aes-gmac-alg, including the recommendation to use =
12 bytes as default GMAC tag length. If at some point the recommendation =
changes to a larger value that would mean both documents need to be =
updated. Maybe better to leave the recommendation out of this draft and =
only reference the aes-gmac-alg draft?=20
>=20
> Okay.
>=20
>> 5a. Which brings us to a question about =
draft-ietf-lamps-cms-aes-gmac-alg; where did the recommendation for a 12 =
byte GMAC tag come from? Is that supported by the referenced standards =
(NIST) or by an IRTF recommendation?
>=20
> This is for alignment with RFC 5084.  I was asked this so often that I =
added this information to the Implementation Considerations section of =
draft-ietf-lamps-cms-aes-gmac-alg.
>=20
> Russ


From nobody Tue Jan 12 07:48:41 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E53D3A09D6 for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 07:48:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LdRym5roXp1D for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 07:48:37 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79B373A09C9 for <spasm@ietf.org>; Tue, 12 Jan 2021 07:48:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 184C7300BBD for <spasm@ietf.org>; Tue, 12 Jan 2021 10:48:35 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yzP0TIsUsZj8 for <spasm@ietf.org>; Tue, 12 Jan 2021 10:48:32 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id DB70A300BC0; Tue, 12 Jan 2021 10:48:32 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <B70D9258-DB2E-4E13-9510-CA004EC9E9E1@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C1AFC18B-F467-42D5-9646-2DA5AFA1EF6D"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Tue, 12 Jan 2021 10:48:34 -0500
In-Reply-To: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com>
Cc: LAMPS WG <spasm@ietf.org>
To: Tadahiko Ito <tadahiko.ito.public@gmail.com>
References: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/U6tiYXQEba1fUHleYpPhtqSrnCc>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 15:48:39 -0000

--Apple-Mail=_C1AFC18B-F467-42D5-9646-2DA5AFA1EF6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Tadahiko:

It seems you are talking about PQC signatures in CMS.  PDF signatures =
employ an early version on CMS.  Would you be able to make a =
presentation at the interim meeting? =20

Russ


> On Jan 12, 2021, at 1:26 AM, Tadahiko Ito =
<tadahiko.ito.public@gmail.com> wrote:
>=20
> Hi Russ
> =20
> I also want to talk a bit about separation of hash and asymmetric =
function.
> It seems we cannot separate those functions in some PQC algorithms.
> In current RSA or ECC, we use data control service to calculate hash =
function part, and use key management service to calculate asymmetric =
function part for large file.
>=20
> For instance, we (our company) currently have a usecase of signing =
10GB PDF file (with HSM). Separation of those functions is necessary for =
such a usecases according to limitation in HSM resource.
> =20
> It would be OK if we introduce one more hash function to signing data, =
but I believe it may damage interoperability. I would like to ask what =
we should do in such a usecase.
> =20
> My draft paper is following (it is a draft, we are not sure if we can =
revise before the meeting)
> <https://eprint.iacr.org/2020/990 <https://eprint.iacr.org/2020/990>>
> =20
> Regards Tadahiko Ito


--Apple-Mail=_C1AFC18B-F467-42D5-9646-2DA5AFA1EF6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Tadahiko:<div class=3D""><br class=3D""></div><div =
class=3D"">It seems you are talking about PQC signatures in CMS. =
&nbsp;PDF signatures employ an early version on CMS. &nbsp;Would you be =
able to make a presentation at the interim meeting? &nbsp;<div =
class=3D""><br class=3D""></div><div class=3D"">Russ</div><div =
class=3D""><br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Jan 12, 2021, at 1:26 AM, Tadahiko Ito =
&lt;<a href=3D"mailto:tadahiko.ito.public@gmail.com" =
class=3D"">tadahiko.ito.public@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div dir=3D"ltr" class=3D""><div style=3D"margin: 0mm; =
text-align: justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=E6=
=9C=9D, serif;" class=3D""><span lang=3D"EN-US" class=3D"">Hi Russ<span =
class=3D""></span></span></div><p class=3D"MsoNormal" style=3D"margin: =
0mm; text-align: justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=
=E6=9C=9D, serif;"><span lang=3D"EN-US" class=3D""><span =
class=3D"">&nbsp;</span></span></p><div style=3D"margin: 0mm; =
text-align: justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=E6=
=9C=9D, serif;" class=3D""><span lang=3D"EN-US" class=3D"">I also want =
to talk a bit about separation of hash and asymmetric function.<span =
class=3D""></span></span></div><div style=3D"margin: 0mm; text-align: =
justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=E6=9C=9D, =
serif;" class=3D""><span lang=3D"EN-US" class=3D"">It seems we cannot =
separate those functions in some PQC algorithms.<span =
class=3D""></span></span></div><div style=3D"margin: 0mm; text-align: =
justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=E6=9C=9D, =
serif;" class=3D""><span lang=3D"EN-US" class=3D"">In current RSA or =
ECC, we use data control service to calculate hash function part, and =
use key management service to calculate asymmetric function part for =
large file.<span class=3D""></span></span></div><div style=3D"margin: =
0mm; text-align: justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=
=E6=9C=9D, serif;" class=3D""><span lang=3D"EN-US" class=3D""><br =
class=3D""></span></div><div style=3D"margin: 0mm; text-align: justify; =
font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=E6=9C=9D, serif;" =
class=3D""><span lang=3D"EN-US" class=3D"">For instance, we (our =
company) currently have a usecase of signing 10GB PDF file (with HSM). =
Separation of those functions is necessary for such a usecases according =
to limitation in HSM resource.<span class=3D""></span></span></div><p =
class=3D"MsoNormal" style=3D"margin: 0mm; text-align: justify; =
font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=E6=9C=9D, =
serif;"><span lang=3D"EN-US" class=3D""><span =
class=3D"">&nbsp;</span></span></p><div style=3D"margin: 0mm; =
text-align: justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=E6=
=9C=9D, serif;" class=3D""><span lang=3D"EN-US" class=3D"">It would be =
OK if we introduce one more hash function to signing data, but I believe =
it may damage interoperability. I would like to ask what we should do in =
such a usecase.<span class=3D""></span></span></div><p class=3D"MsoNormal"=
 style=3D"margin: 0mm; text-align: justify; font-size: 10.5pt; =
font-family: =E6=B8=B8=E6=98=8E=E6=9C=9D, serif;"><span lang=3D"EN-US" =
class=3D""><span class=3D"">&nbsp;</span></span></p><div style=3D"margin: =
0mm; text-align: justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=
=E6=9C=9D, serif;" class=3D""><span lang=3D"EN-US" class=3D"">My draft =
paper is following (it is a draft, we are not sure if we can revise =
before the meeting)<span class=3D""></span></span></div><div =
style=3D"margin: 0mm; text-align: justify; font-size: 10.5pt; =
font-family: =E6=B8=B8=E6=98=8E=E6=9C=9D, serif;" class=3D""><span =
lang=3D"EN-US" class=3D"">&lt;<a href=3D"https://eprint.iacr.org/2020/990"=
 class=3D"">https://eprint.iacr.org/2020/990</a>&gt;<span =
class=3D""></span></span></div><p class=3D"MsoNormal" style=3D"margin: =
0mm; text-align: justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=
=E6=9C=9D, serif;"><span lang=3D"EN-US" class=3D""><span =
class=3D"">&nbsp;</span></span></p><div style=3D"margin: 0mm; =
text-align: justify; font-size: 10.5pt; font-family: =E6=B8=B8=E6=98=8E=E6=
=9C=9D, serif;" class=3D""><span lang=3D"EN-US" class=3D"">Regards =
Tadahiko Ito<span =
class=3D""></span></span></div></div></div></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_C1AFC18B-F467-42D5-9646-2DA5AFA1EF6D--


From nobody Tue Jan 12 08:14:20 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2FAE3A0AD5 for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 08:14:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRIv05E0s1cZ for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 08:14:16 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90D1F3A0AC4 for <spasm@ietf.org>; Tue, 12 Jan 2021 08:14:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 21BFE300BBB for <spasm@ietf.org>; Tue, 12 Jan 2021 11:14:14 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id V5bzzL182Q3f for <spasm@ietf.org>; Tue, 12 Jan 2021 11:14:12 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id D004A300231 for <spasm@ietf.org>; Tue, 12 Jan 2021 11:14:12 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Message-Id: <859BA170-BA6D-471B-AD74-EB465C47103A@vigilsec.com>
Date: Tue, 12 Jan 2021 11:14:14 -0500
To: LAMPS WG <spasm@ietf.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/tYKKpNsJe0A9r8TduCvxnAhxDPM>
Subject: [lamps] RFC 6019
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 16:14:19 -0000

RFC 6019 is:

     BinaryTime: An Alternate Format for Representing Date and Time in
     ASN.1. R. Housley. September 2010. (Format: TXT, HTML) (Obsoletes
     RFC4049) (Status: PROPOSED STANDARD) (DOI: 10.17487/RFC6019)=20

Is appears that several people are finding this useful:

    https://datatracker.ietf.org/doc/rfc6019/referencedby/

I would like to know if people have implemented it.  If so, should we =
progress the document to Internet Standard?

Russ


From nobody Tue Jan 12 14:49:34 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47FB43A133A for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 14:49:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mRipYfFplgwX for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 14:49:31 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 612C23A1329 for <spasm@ietf.org>; Tue, 12 Jan 2021 14:49:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id D04C9300B9D for <spasm@ietf.org>; Tue, 12 Jan 2021 17:49:28 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 1qaU9jZlJor3 for <spasm@ietf.org>; Tue, 12 Jan 2021 17:49:26 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id CAD6C300512; Tue, 12 Jan 2021 17:49:26 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DM6PR11MB43804A64358FB9D3684FD8129FAB0@DM6PR11MB4380.namprd11.prod.outlook.com>
Date: Tue, 12 Jan 2021 17:49:28 -0500
Cc: LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AFF7174-A5AB-475F-8DFB-E3152FC18C43@vigilsec.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <DM6PR11MB43804A64358FB9D3684FD8129FAB0@DM6PR11MB4380.namprd11.prod.outlook.com>
To: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Gmm6frwFktKydAaXpEpHvyg6h0Y>
Subject: Re: [lamps] [EXTERNAL] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 22:49:34 -0000

Mike:

These were the Jumbo Certificates that were used in the early days of =
the UD Defense Message System development.  They were abandoned before =
production, and they included a DSS and KEA public keys.  IN that =
system, the DSS private key was not escrowed, but the KEA private key =
was escrowed.  The mis-match with the key usage extension was just one =
problem.

The DSS key and the KEA key had the same lifetime, so some of the =
concerns that you reference were avoided.

There were many issues with revocation.  Revoking the certificate made =
both the DSS key and the KEA key unusable, even in situations where one =
of them was still workable.

Russ


> On Jan 11, 2021, at 6:33 PM, Mike Ounsworth =
<Mike.Ounsworth=3D40entrust.com@dmarc.ietf.org> wrote:
>=20
> Hi Russ,
>=20
> Your slides refer to
>=20
> Has known pitfalls of the "jumbo" certificate, which carried a key =
agreement public key and a signature public key for the same user"=20
>=20
>=20
> Was that from the 1997 PKIX mail list thread titled "Combo DSS/ElGamal =
keys" ? If so, the objections I'm seeing were mostly to do with mixing =
key usages -- ex.: nonrepudiation and key transport keys potentially =
having different key policies like validity period or private key =
escrow. Or the argument that revoking the keyex key due to, for example, =
bungling the backup copy would have the side-effect of invalidating any =
signatures produced by the signing key which would not have been part of =
the backup.
>=20
> You may need to expand a bit on which arguments from that thread apply =
to Composite where all component keys must have the same keyusage and =
are intended to be used as an atomic object for producing composite =
signatures.
>=20
> ---
> Mike Ounsworth
>=20
> -----Original Message-----
> From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
> Sent: January 9, 2021 12:52 PM
> To: LAMPS <spasm@ietf.org>
> Subject: [EXTERNAL][lamps] Call for Presentations at the LAMPS Interim =
Meeting on 28 Jan 2021
>=20
> WARNING: This email originated outside of Entrust.
> DO NOT CLICK links or attachments unless you trust the sender and know =
the content is safe.
>=20
> I gave this presentation at the NIST NCCoE Virtual Workshop on =
Considerations in Migrating to Post-Quantum Cryptographic Algorithms: =
https://www.nccoe.nist.gov/sites/default/files/10-Housley-NCCoE-Workshop-T=
ransition-to-PQC-Certificates.pdf
>=20
> This short presentation still captures my view.  Are there people with =
a different view that would like time on the agenda at the LAMPS Interim =
on 28 Jan?  I would like to make sure that all point of view are heard.
>=20
> Russ
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Tue Jan 12 15:41:53 2021
Return-Path: <csmiley@amsl.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A622E3A145A for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 15:41:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3IpkGYlYeK9 for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 15:41:47 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C1D03A1456 for <spasm@ietf.org>; Tue, 12 Jan 2021 15:41:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 9AB6438B368; Tue, 12 Jan 2021 15:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQ21XRpwW6JB; Tue, 12 Jan 2021 15:41:46 -0800 (PST)
Received: from [192.168.1.3] (cpe-76-95-228-63.socal.res.rr.com [76.95.228.63]) by c8a.amsl.com (Postfix) with ESMTPSA id 5998F38B35C; Tue, 12 Jan 2021 15:41:46 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Chris Smiley <csmiley@amsl.com>
In-Reply-To: <20201230211854.823E9F4073F@rfc-editor.org>
Date: Tue, 12 Jan 2021 15:41:46 -0800
Cc: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0BED4425-F1CF-4C83-8321-2985280C0FFC@amsl.com>
References: <20201230211854.823E9F4073F@rfc-editor.org>
To: Russ Housley <housley@vigilsec.com>, Roman Danyliw <rdd@cert.org>, Benjamin Kaduk <kaduk@mit.edu>, tim.hollebeek@digicert.com, spasm@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/P3zUolQDsRfH2h2xyJA4wy5n7Ig>
Subject: Re: [lamps] [Technical Errata Reported] RFC8649 (6376)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 23:41:51 -0000

Greetings,

This report has been deleted as junk.

Thank you.

RFC Editor/cs

> On Dec 30, 2020, at 1:18 PM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC8649,
> "Hash Of Root Key Certificate Extension".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6376
>=20
> --------------------------------------
> Type: Technical
> Reported by: Mahmud andreansyah <amtzandre43@gmail.com>
>=20
> 1297992261
>=20
> Original Text
> -------------
> Privasi account
>=20
> Corrected Text
> --------------
> Privasi account saya
>=20
> Notes
> -----
> Privasi account
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC8649 (draft-ietf-lamps-hash-of-root-key-cert-extn-07)
> --------------------------------------
> Title               : Hash Of Root Key Certificate Extension
> Publication Date    : August 2019
> Author(s)           : R. Housley
> Category            : INFORMATIONAL
> Source              : Limited Additional Mechanisms for PKIX and SMIME
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
>=20


From nobody Tue Jan 12 19:29:09 2021
Return-Path: <pkampana@cisco.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CE23A0AFA for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 19:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.993
X-Spam-Level: 
X-Spam-Status: No, score=-9.993 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=knDvr9g6; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.onmicrosoft.com header.b=Nwa/zprR
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MipQFaMDEXcD for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 19:29:06 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D34703A0AF9 for <spasm@ietf.org>; Tue, 12 Jan 2021 19:29:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7643; q=dns/txt; s=iport; t=1610508545; x=1611718145; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=fP6JYv+JKkS6U1RWbpeH/Yx3CUo858UXovWGkBIVhVQ=; b=knDvr9g6/tROr5KzCE+XsFwOKbaxzKDEB3ziuA9N91UqwA/W0eWYaDvC hSv+KkzG19Lh6WGlqu2a8VHCHx+hWKedC9FHPAqUjTsQFH7mfzjDuF6ZI owewYOR8QfPsWD0K57KNMvSWss82uYCbooP6xv3oZydxzv+1SutojRHqH Q=;
X-Files: smime.p7s : 4024
X-IPAS-Result: =?us-ascii?q?A0DEAgChaP5fmIsNJK1iHQEBAQEJARIBBQUBQIFPgVNRf?= =?us-ascii?q?S0uLy4Kh30DjXUDmRKCUwNUBAcBAQEKAwEBGA0IAgQBAYRKAoFxAiU4EwIDA?= =?us-ascii?q?QEBAwIDAQEBAQUBAQECAQYEFAEBAQEBAQEBhjYMhXMBAQEEAQEbIwEBLAwLB?= =?us-ascii?q?AIBCBEEAQEvAiULHQgCBAESCAaDGAGBflcDHw8BDqQVAooldIE0gwQBAQaBR?= =?us-ascii?q?gI7BAGDGhiCCQcDBoE4gVOBIoZKg3ImG4FBP4ERQ4IoLj6BBIFZAQGBYYNKg?= =?us-ascii?q?iyDVCtbCwoLHBsNgSKPLYxHnCoKgneEXoJolDuiYJQSoUACBAIEBQIOAQEGg?= =?us-ascii?q?W0hgVlwFTuCaVAXAg2OIRqDV4F/gxWFRHQCNQIGCgEBAwl8i04BgRABAQ?=
IronPort-PHdr: =?us-ascii?q?9a23=3A3ND2mRBiY7ShZUmsK6wFUyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qw31A3XXIra7+lJgKzdtKWzEWAD4JPUtncEfdQMUh?= =?us-ascii?q?IekswZkkQmB9LNEkz0KvPmLklYVMRPXVNo5Te3ZE5SHsuteVzdo3mp4DVUER?= =?us-ascii?q?L6ZkJ5I+3vEdvUiMK6n+m555zUZVBOgzywKbN/JRm7t0PfrM4T1IBjMa02jB?= =?us-ascii?q?DOpyhF?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,343,1602547200";  d="p7s'?scan'208";a="643685265"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Jan 2021 03:29:04 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 10D3T4t0014020 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Jan 2021 03:29:04 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 Jan 2021 21:29:04 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 Jan 2021 21:29:04 -0600
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 12 Jan 2021 21:29:04 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SatEZVAymk18R2Q1YHCLnlfkQnDXnPUW3f1/Waq7lA5jFkaaXeHSgLeRvS9gAW3bzfpJTiq7QWb3KFdSPsmtgtyNi93SnaZ/eNukTYYrw65ALybDiotKDDvZusdy8Lg0yZJfD+SS07+1zAevuj8czZc51/uNFGRNRVo98Ozz7l9JXxUdcpqKuyrO8HHx+5OJVLiiCZUQT5Wm13WW3JDWtFkgOdH4E4GPkiv9ivKp+YU7D25CgKbD2nABO7nkj5MfywKjZzrJPYFGnMlkQhw9gIHGM/W318u0eUoTU/o5hk1eQhkrsh9udt6JbfzRMQoa9hQ7G0BON9I+GR0JAeErCw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=t6N1pU/KFZTpo6o2TpiwIuIxDsHmgIOux8n3M7e2jK4=; b=KmSusS6p+V/RTXU+DOt5ZWzCflv1x/wDGiP5P/W+Yych+gy21ypJd5XhFsOXve1wjsskHQariHKYE20vNTU1cqsB8Y3030vXSnFhU6xkLp1wWbd0RqFMH3f8Y2Uq1iINItUfPqF6jJZauTD8cbYHehP0NowzETteDH2rWO7GV8+7Lmt3Ec47P87BVvxyra45H5eaFpVP7jnzAewIuBSFgZPWmFZKQI1qGD1E55lMbuWHy73qoWxCRePhplh8f20TWB9/STwHF+BwtvxzxS2SwIH3YUrhFqCDLM1L5abaRymN6y3KcjxGBdX6qEIF0dJCu+449g3NbnBiRFIMu0PEtQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=t6N1pU/KFZTpo6o2TpiwIuIxDsHmgIOux8n3M7e2jK4=; b=Nwa/zprR5fhcPkKdrxpqrbNJGQHeWHtnjkTyAJTcI0MITalpk0FaXlvQkb5/l1xqqAX1PbzHkpZzukzrsFnrohhHV99x+zcmOfuStqY2AIRh/sFCwrqvdDpkX+21x3qeg3vIYOKuqrmGfBNWs8nbdM/ayffw+unKlLce++iNBf8=
Received: from BN7PR11MB2547.namprd11.prod.outlook.com (2603:10b6:406:af::18) by BN6PR11MB1986.namprd11.prod.outlook.com (2603:10b6:404:3c::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.9; Wed, 13 Jan 2021 03:29:02 +0000
Received: from BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::9195:40a8:5888:b23d]) by BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::9195:40a8:5888:b23d%4]) with mapi id 15.20.3742.012; Wed, 13 Jan 2021 03:29:02 +0000
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Russ Housley <housley@vigilsec.com>, LAMPS <spasm@ietf.org>
Thread-Topic: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
Thread-Index: AQHW5riBmy+cI8nzfkirOXSHgYVFNaok5YWg
Date: Wed, 13 Jan 2021 03:29:02 +0000
Message-ID: <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com>
In-Reply-To: <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [68.93.142.48]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e242f9dc-0135-40f6-23ee-08d8b7735f9a
x-ms-traffictypediagnostic: BN6PR11MB1986:
x-microsoft-antispam-prvs: <BN6PR11MB1986BD8BB1F47BFB7CC68980C9A90@BN6PR11MB1986.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: E2vGAtOOVKuU6dewWOiGGGiczkYrZ3bnFtUyTzkltNpgDSJDJdImksK23A3H2VWhhWm3rgYbjN8owWhqB+79njpjFHSHja6g+8Y0ZMqZpjnggCSllAGtAfuyWxC6pPO5nd/FuE/DeiReDKldGML7c3IDsywz7v1MaDq8CtH1b0FuGR/fcDSzNQDsv0KdEK3ijwap4KQaEt1bTVCkEDJ0y1KTu9iCt0Khqj6MuIX9bggs8K2uBD8zxzAWgNXR2gOEVa+PcBTz+r/gSj6aw3Bu6+VXk2919N1VjTdDvzZV/CcnMuUlcve0wNW8MjDa/XEu32LK+SsPRhCl3yR9KQtLa5sBrjdFPYrDsj3lpgydKqXzdHlUH0jl2IEdf7wUrT1br1mNupoGpnuvKrmZZTT2fQwxF2tsW83NvbwlHUl3c2qnWllbIUFCNzGWqgPovPGtXOgYO9q50ZynzYsaA/NgVN2kZzTa5IS2iRJ2KhDuzWniKsLsKL4KZtcH6OnQUygpanHKBCm/wrpS6FXgKM3KGw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BN7PR11MB2547.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(346002)(366004)(39860400002)(376002)(396003)(136003)(316002)(71200400001)(966005)(5660300002)(7696005)(86362001)(55016002)(99936003)(66946007)(66446008)(186003)(76116006)(2906002)(9686003)(110136005)(83080400002)(83380400001)(33656002)(53546011)(8936002)(52536014)(8676002)(6506007)(66476007)(26005)(478600001)(66556008)(64756008)(66616009); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?LYv9gVD/W7jRtGVpxEXmTlyyogJTYoUo75SWKMmDBh2+0dxQwZfrM5teRZwr?= =?us-ascii?Q?JaQWRT0CTu0szVU2xuGC7BbRBCujutsbu92WnYdvnBV8cKTRLA3od2yfSsIu?= =?us-ascii?Q?owWsowWaVcJ/tnNB/KbdzarHvxQrvJPag5QghQ/wJl3s3oMHB+YuGzimPwMU?= =?us-ascii?Q?P89QPgwJDZ+DV8JG0ddilkTmK8mqcPM6Cq7aew6yLscaHjw13Ewn+JnV9ERc?= =?us-ascii?Q?MBKO4owChMq2QH1aasWD3Tqh9ybH3rf4cbj11IkptDXRZVru/hEbJPC3cY65?= =?us-ascii?Q?plJ6Eh+qoX3th/j8Biw3OsoL6ghG8tX9ZlECyd5F234UgE2jslssyMTkBEEy?= =?us-ascii?Q?O6JDiQRfBnbKwnvly61As/FKTXemYs05y8tE9hDC5ymLUHf1gy2MclqGN0ql?= =?us-ascii?Q?K9BcQjnJW9tj2BG65+/gVR42q1eIIGd6Z8rTEEkwn/Ka2qrLYZEgbzuF0uji?= =?us-ascii?Q?w4926CVBwcFwRtWFg/QaGw/HVivItOqQ3EfRSq7I/NkGc2DsdjCdcArPpe3W?= =?us-ascii?Q?2D2FuQ9kMood3/V8IETulk9NMOqIFHH/4kOZ0oc2X9vxtb9F3fwEP4i2sphY?= =?us-ascii?Q?OaxaWY9zivM3vHm4FhblWIb/EPgB/9xusjJG4n/7U17AwPewTy8S4XpDnU2p?= =?us-ascii?Q?wHL8q+5hJR0EpQe05K+4fz63mMi1hGPjaN0QzLQx7iWthijxlOaTP4NOeHAf?= =?us-ascii?Q?+7ce8M9ToPPac3OlpWO8lP7UYPsi1spMU2LHCfV7mhdyHfP8S3cY/7JhH2Zq?= =?us-ascii?Q?YzpDdlYzMwF1xJTa2xgL/6E9AXPQeNjtLvxBmnsHgcXtKptOOmgFNYokhnQf?= =?us-ascii?Q?duspM6zel/NYDiTzYSowFYM5dgym/CaC3VvwFDKpOYpxgEolGrdqY1mH+y2D?= =?us-ascii?Q?J197tbFWIoPHsX8VlXnfre4fO5K+mPmPPbq3k0zEPCwXtvLoUxjC22Ts8vjc?= =?us-ascii?Q?LY+x93LSbzRS2PXKQa4VDHdwSDpDH8OKXK0Rh/wCVxk=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=2.16.840.1.101.3.4.2.1; boundary="----=_NextPart_000_0021_01D6E932.537EBDE0"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN7PR11MB2547.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e242f9dc-0135-40f6-23ee-08d8b7735f9a
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2021 03:29:02.4665 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: +3K/gZvRW9QP+dnn116z0sA45DsHHKR8inCdXuVZ2mfdPaiHtuRG/Zk6F6GAzwAzddjmNQNQAGgT9q08vWVfQQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1986
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ch7VGgo6t9UXEItfYuiXNvBBSsQ>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 03:29:08 -0000

------=_NextPart_000_0021_01D6E932.537EBDE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

I have been on both sides of the argument, Classical+PQ signatures or
parallel (classical, PQ). Recently I have been thinking that we probably
can't avoid keeping classical PKI for backwards compatibility which probably
makes the Classical+PQ sigs less appealing. Especially for live protocols
like TLS, this argument is even more relevant especially since the big cert
would be penalizing the classical peer with unnecessary PQ sig data. 

But I have heard some arguments for classical+PQ for non-TLS usecases. An
example could be SW Signing. I would argue that PKCS#7/CMS can include
multiple sigs (in SignerInfo) in the SignedData as clarified in RFC4853, so
even for SW Signing we may not need Composite or Hybrid Classical+PQ
Signatures. 

So, in summary, I am curious about the usecases where classical and PQ
signatures need to exist together. 

Thx,
Panos


-----Original Message-----
From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
Sent: Saturday, January 09, 2021 1:52 PM
To: LAMPS <spasm@ietf.org>
Subject: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
Jan 2021

I gave this presentation at the NIST NCCoE Virtual Workshop on
Considerations in Migrating to Post-Quantum Cryptographic Algorithms:
https://www.nccoe.nist.gov/sites/default/files/10-Housley-NCCoE-Workshop-Tra
nsition-to-PQC-Certificates.pdf

This short presentation still captures my view.  Are there people with a
different view that would like time on the agenda at the LAMPS Interim on 28
Jan?  I would like to make sure that all point of view are heard.

Russ

_______________________________________________
Spasm mailing list
Spasm@ietf.org
https://www.ietf.org/mailman/listinfo/spasm

------=_NextPart_000_0021_01D6E932.537EBDE0
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCDGkw
ggNDMIICK6ADAgECAhBf+HsoK1TcjUKjFbVoya3/MA0GCSqGSIb3DQEBBQUAMDUxFjAUBgNVBAoT
DUNpc2NvIFN5c3RlbXMxGzAZBgNVBAMTEkNpc2NvIFJvb3QgQ0EgMjA0ODAeFw0wNDA1MTQyMDE3
MTJaFw0yOTA1MTQyMDI1NDJaMDUxFjAUBgNVBAoTDUNpc2NvIFN5c3RlbXMxGzAZBgNVBAMTEkNp
c2NvIFJvb3QgQ0EgMjA0ODCCASAwDQYJKoZIhvcNAQEBBQADggENADCCAQgCggEBALCauaunrwp3
p+JxtrRmYpR4iEfGYlWEQDK/wKsupRxx1rxue6iqum7SFYhIRZ2i/IPQzLmM4CZocEp43yEXnvRh
BckVyM8W2jVhiZRDqISoMZh4m7lObyxTEmzNHa0rJLsxxCv/g0Rvtj0kdwnqvyqoH2pW9iAPEVSX
gXWnJc5ZaoJl77fq5+KNdYtu8t1Ppl5inM8QCmTQTm3OK8xb9WClJ0eNafR/zhtw3nAbINZuzaYB
qDwS0qk/oGteu44gi3qR47Vo7qDnxAF0qFMLK0qaD2USDoJNjmP97+ubGttTphNgr8J918dsFyXU
c/tHZFCBgJRM4b+uSxzfku0uBd8CAQOjUTBPMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/
MB0GA1UdDgQWBBQn88gVHm6aAgkWrSugiWBf2nsvqjAQBgkrBgEEAYI3FQEEAwIBADANBgkqhkiG
9w0BAQUFAAOCAQEAnZ2EhKNBqXx3DLdTyk5EUGLvVHzTdRcc6ODGSEu2/kw6GYFWsFbuGZZiqlqj
ZMH2TlQzxnf+xRy65V0lyvXwk5qDES7my/h0Rf7nBbir59/LS+E3hNq5i5dwHvDii9ew2A6dsWnW
KpF7qUlPfuaOldiDJzzVaEkO1J32LuunvuswpKwfRPyVqzMG+31gCt60imOwnKnypLlTAYfQaKQn
f6v/6frJQDiIZ7Q5xoRvV8lT27qO7sBDsvgJg27/Zs8+7xezWBglCTRe48vWFLbs8pJvdOQvgSrV
kpHg4Jc8MmgFhUvR91fiUh2TGlSfBXDASnFgHkMLYB7+o86BGeELNTCCBG4wggNWoAMCAQICCmEQ
gG0AAAAAAA4wDQYJKoZIhvcNAQEFBQAwNTEWMBQGA1UEChMNQ2lzY28gU3lzdGVtczEbMBkGA1UE
AxMSQ2lzY28gUm9vdCBDQSAyMDQ4MB4XDTE0MDQwNDIwMjQxOFoXDTI5MDUxNDIwMjU0MlowLDEO
MAwGA1UEChMFQ2lzY28xGjAYBgNVBAMTEUNpc2NvIEVtcGxveWVlIENBMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAyt9+FkxTFfsjVs3GuWUKBJXl3kxFZ4wMxwbgqx9tXzcqe+fto62A
fxHI84Lr7p9Q2cm/PaEvuzwRBzXvuKXZUU7ZsPdToJSALCySZa0Qb6GGa19ACpmlUEQakE3P5kz7
RgaNSOMH1+GtY9fV6CcAFb9uB7JDu2UGL332WV2bEsUsfb3rRLBS4cL8Hu2dWfcdk6erMaZCQjkn
04FixlQsJozbPRTQqI4V6iikG/69rDyeTdbVTK+My/9LnwVsD3GBMiRh7RmrvupxtGiMu8j05Is/
d1OifhWecwvjV3Reg9Lok8bMNJEMAped1weTdVS0X4MsAheosJBld9lS5O4idwIDAQABo4IBhzCC
AYMwEAYJKwYBBAGCNxUBBAMCAQAwHQYDVR0OBBYEFJ+VNrSOXdVLwwrBpymTQ1EG/YlRMBkGCSsG
AQQBgjcUAgQMHgoAUwB1AGIAQwBBMAsGA1UdDwQEAwIBhjASBgNVHRMBAf8ECDAGAQH/AgEAMB8G
A1UdIwQYMBaAFCfzyBUebpoCCRatK6CJYF/aey+qMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly93
d3cuY2lzY28uY29tL3NlY3VyaXR5L3BraS9jcmwvY3JjYTIwNDguY3JsMFAGCCsGAQUFBwEBBEQw
QjBABggrBgEFBQcwAoY0aHR0cDovL3d3dy5jaXNjby5jb20vc2VjdXJpdHkvcGtpL2NlcnRzL2Ny
Y2EyMDQ4LmNlcjBcBgNVHSAEVTBTMFEGCisGAQQBCRUBFQAwQzBBBggrBgEFBQcCARY1aHR0cDov
L3d3dy5jaXNjby5jb20vc2VjdXJpdHkvcGtpL3BvbGljaWVzL2luZGV4Lmh0bWwwDQYJKoZIhvcN
AQEFBQADggEBAD5OviMaRgKNXmvbigI0C2Ob5QE8Jl2McLIk62Be7IqEZC4bWRWjZxrhFuP94E19
RJojKNLttveiH+dEze1t6oYhVCisbGG8+8hlUARAiiqL/J9uGJ71xT6loqkcAK5xphe7STJLSlgT
k0w26fcvDeiA6zhdVHnKhVKkpOJWd9MNByFOnCQyDOK+pcNxLU6IN9TwL1ZoRkdFa11QiCX3Oimk
8YhBrVN+VzGGKtbgZ4fYU6uBo3V3vtshyDpHtGkn1e7f9/TWcY26etFzL33dzaZ4lChlw4l3XkLq
6AfCEDF5djpBdiCRjwpBUIIbCSmyESBvA+sL4j8i1vo/uEartrAwggSsMIIDlKADAgECAgoBhhEi
QTzquitVMA0GCSqGSIb3DQEBCwUAMCwxDjAMBgNVBAoTBUNpc2NvMRowGAYDVQQDExFDaXNjbyBF
bXBsb3llZSBDQTAeFw0xOTEyMjAxOTQ5MDJaFw0yMTEyMTkxOTU5MDJaMIGfMSQwIgYDVQQDExtQ
YW5vcyBLYW1wYW5ha2lzIChwa2FtcGFuYSkxFDASBgNVBAsTC0Npc2NvIFVzZXJzMRIwEAYDVQQL
EwlFbXBsb3llZXMxEzARBgoJkiaJk/IsZAEZEwNjb20xFTATBgoJkiaJk/IsZAEZEwVjaXNjbzEh
MB8GCSqGSIb3DQEJAQwScGthbXBhbmFAY2lzY28uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAmIHTLIzoAnuMUiHMx8V+PF9JpAcB7zrNHOY1Vj1R1Vx7ty7m9yo9G991T2n7zHo4
UzF6tnB9NxzQOKCY54oqP5KjVGYOPPo+qZ+2rx1GABzdKUF4LwUUKOTf9uXAtvsvIRUc5J/csShT
jcUIvtVmiAzWXWRfMYShjBYBVtx/h8fDqAqfFAzd6HG0TcdsN/BRb9k6QEW1afHjPKlRUaDRELyj
nFGJZd2OsUJ7/aKMdFmQFd2CAJYzsuwLYjeqJsuGNzBc/k6mzQPf6FW17nz17G41KReU0UdZf2yZ
jvimkwCQ/yW8SVTOcGBP+Zk+Lq5EYEGQMu1qtNK/97bXMc5kuwIDAQABo4IBWjCCAVYwDgYDVR0P
AQH/BAQDAgTwMAwGA1UdEwEB/wQCMAAwegYIKwYBBQUHAQEEbjBsMDwGCCsGAQUFBzAChjBodHRw
Oi8vd3d3LmNpc2NvLmNvbS9zZWN1cml0eS9wa2kvY2VydHMvY2VjYS5jZXIwLAYIKwYBBQUHMAGG
IGh0dHA6Ly9wa2ljdnMuY2lzY28uY29tL3BraS9vY3NwMB8GA1UdIwQYMBaAFJ+VNrSOXdVLwwrB
pymTQ1EG/YlRMDoGA1UdHwQzMDEwL6AtoCuGKWh0dHA6Ly9jaXNjb2NlcnRzLmNpc2NvLmNvbS9m
aWxlL2NlY2EuY3JsMB0GA1UdEQQWMBSBEnBrYW1wYW5hQGNpc2NvLmNvbTAdBgNVHQ4EFgQUjrl7
6Mrrdw3ZYFiTpZBdtrUm5P4wHwYDVR0lBBgwFgYKKwYBBAGCNwoDDAYIKwYBBQUHAwQwDQYJKoZI
hvcNAQELBQADggEBAMhR6xCTygu68lppjWebXTXYznix5961hcmwiJRkPtUIGQ5JQwXyCwq/Juuq
yc5ebeq9cQEO5iqyxik/UAQ35BlmKb7SNLi75RtFE/AIZrRsEjTUoO2EtCMQOEMcenWa2XE8fEID
BkwzreKeaOchCbDd4L9PvKFht6nDDFtb6VZdWs4ort+J3iFeilVf3oI5MSVi+qroWaFLnLYTQGTn
qEjWANfKw3RRBAMdoPCZ+N4eftAk1TWVS08nOsPoKWXtIqX6y0ZPs/EZjBSk57v1TPLpYhEqYGXI
oGJlIvzIAfYNoUg8yP8toG5T7x+7hRz0MMUGWcCDsS9PMFxH6SnrUSMxggMNMIIDCQIBATA6MCwx
DjAMBgNVBAoTBUNpc2NvMRowGAYDVQQDExFDaXNjbyBFbXBsb3llZSBDQQIKAYYRIkE86rorVTAN
BglghkgBZQMEAgEFAKCCAaQwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMjEwMTEzMDMyOTAxWjAvBgkqhkiG9w0BCQQxIgQgPGP/t9ksoQcf476tCxNjPxobQs4W2yui
sCpllNKuhyEwSQYJKwYBBAGCNxAEMTwwOjAsMQ4wDAYDVQQKEwVDaXNjbzEaMBgGA1UEAxMRQ2lz
Y28gRW1wbG95ZWUgQ0ECCgGGESJBPOq6K1UwSwYLKoZIhvcNAQkQAgsxPKA6MCwxDjAMBgNVBAoT
BUNpc2NvMRowGAYDVQQDExFDaXNjbyBFbXBsb3llZSBDQQIKAYYRIkE86rorVTCBoAYJKoZIhvcN
AQkPMYGSMIGPMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCgYIKoZIhvcNAwcwCwYJYIZIAWUD
BAECMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDALBglghkgBZQMEAgEwCwYJKoZIhvcN
AQEKMAsGCWCGSAFlAwQCAzALBglghkgBZQMEAgIwBwYFKw4DAhowDQYJKoZIhvcNAQEBBQAEggEA
XC9ynX/OT8M0U6L1x3bsIOLVvlQyccvYTJ/ZZAgOfDlkQyMEWGtOOSWGrmrp7AceWU2CYVoAeogc
0V2xII1LmX4jkIHMrQgW17nTLV0SC5q4lFMBYu+eAHDgt5GH6YTu25qvskW5HxH9KDl9AEwfp5Vo
9wby2soc05rO84nhkk9V9Sn+wg0LAm7c2xzZ4Lrc7sHNZJey5Ie/D5TsufFvB26Y5iL9cMTlNAdX
h1RP1ilH3YltdWQ4WHZZXeCTVjZu4hSKde62q0SF/eZY0fc2ZjX+ClsyJvlbt36dDYogNAxpLues
B/k6rNvw+Q3wjmE3+g/YXWVaU0PbLkOG8dHwKwAAAAAAAA==

------=_NextPart_000_0021_01D6E932.537EBDE0--


From nobody Tue Jan 12 20:36:42 2021
Return-Path: <pkampana@cisco.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5B583A03EC for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 20:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.992
X-Spam-Level: 
X-Spam-Status: No, score=-9.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=E6SVkbXK; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.onmicrosoft.com header.b=iBohFXqP
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M8sYG3-CWP0m for <spasm@ietfa.amsl.com>; Tue, 12 Jan 2021 20:36:38 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC9CA3A0332 for <spasm@ietf.org>; Tue, 12 Jan 2021 20:36:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15188; q=dns/txt; s=iport; t=1610512598; x=1611722198; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ai/sw6uH7ki0LCF3R3q20QGFutAXovqvWxNdli1v0uw=; b=E6SVkbXKLoR+oUySBX225poVAeHIYihc/GLLHu3McpdqHsEpB+cJQgNH 9xB8v7xK7OpzPxwyLZ42cG2TPPHacPJsXcmRePnWRazkCLjZCi5/XY4E1 J5IMVxIOgpYlYfF1wAg0/1K99BOpInnDqXcJYXMPUJjTu3xi+6E28X2yb U=;
X-Files: smime.p7s : 4024
IronPort-PHdr: =?us-ascii?q?9a23=3ADQs4HhN5AtsZJ7AG7TUl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEvKwx3lDMVITfrflDjrmev6PhXDkG5pCM+DAHfYdXXh?= =?us-ascii?q?AIwcMRg0Q7AcGDBEG6SZyibyEzEMlYElMw+Xa9PBtaHc//YxvZpXjhpTIXEw?= =?us-ascii?q?/0YAxyIOm9E4XOjsOxgua1/ZCbYwhBiDenJ71oKxDjpgTKvc5Qioxneas=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DACQAkeP5f/51dJa1ig3swUQd2LS4?= =?us-ascii?q?vLgqENYNIA411A4dtjDKEc4JTA1QEBwEBAQoDAQEfDgIEAQGESgKBcQIlOBM?= =?us-ascii?q?CAwEBCwEBBQEBAQIBBgRxhWEMhXMBAQEEHQYKEwEBNwEPAgEIEQQBASsCAgI?= =?us-ascii?q?wHQgCBA4FCAaDGYF+VwMfDwGkIAKKJXaBMoMEAQEGgTMBg3QYggkHAwaBOIF?= =?us-ascii?q?TgSKDfQGGPiYbgUE/gVSCKC4+hEArgms0giyDLCcsIC0ZNgMgao9sJIMliHe?= =?us-ascii?q?bGYERCoJ3hF6CaIFlj0WDEaJgnyiWKgIEAgQFAg4BAQaBbSOBV3AVgyRQFwI?= =?us-ascii?q?NjiwYg06FFIVEdDcCBgoBAQMJfItOAYEQAQE?=
X-IronPort-AV: E=Sophos;i="5.79,343,1602547200";  d="p7s'?scan'208,217";a="850010472"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Jan 2021 04:36:37 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 10D4abd9008669 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Jan 2021 04:36:37 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 Jan 2021 22:36:36 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 Jan 2021 23:36:35 -0500
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 12 Jan 2021 22:36:35 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JC/1W2lVwEJvOHUbAKvxEiySOZ263exmGHQITy8MtivyX2QlCkVbaUx1H+4zSuGrol+9tiMkmNqhD+sc1ZBQI3LfyB5Y2ipOzHuK/NhFQGZuWQ8p80J2YqlklygqlAhDjaAWuDNmMVk/H2q+JUv7XvJA7uYFj092KMtHS+dy+J4cwo/KZpTj6f/NMCEpP0m6CkeQjcRiWuQHgYv/ZH6TyO830ZgSZqV/4UW815wNzRRS/63SLA8soo+xPZBnwB7mDxiF0yckNaqcheTVJWllCSs1njFFIgV5SnKGV1q4Q5mKZm9oS9JZT8zqT+Zls+ozJLDDk/7uFgVv0bhuJ5zYJg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VLaOuo3pRf7kATLL8WlFNlRKsaZOWYuB6xWZ8aPKXm0=; b=Os3yVT+KQgHwLGrGlw5WH2/KbTnlBXmw8bt3lRZEeHQeAWvviG9w1XNwRai/Mkea2I/o6OF5TkGalKrFwg3i+Ga4G9ZlB9aWOBo3QSOcdud0maTz3rcTeOUWAqeSzcBBZT+98ID2hkmxPRm33bPRWmaDEY5bgitZFesfBLevMayKTpBH7yb6GDUUthWJWQlJzUz4iIkNCHfVxKsqxCgOpnQ6qHr8/HXJWkRKq4k3ZkeZ/lsZKmF2/KB3gai/95DnT5gNz5FJrvGy+6x7AS9ncFQEOdviInjO+jNxkDmBSfcZlt2qTyEVNtqZWWfTwXOY2swoG2AEGaWakCde27ZH5g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VLaOuo3pRf7kATLL8WlFNlRKsaZOWYuB6xWZ8aPKXm0=; b=iBohFXqPN7xQP5hwF11tKKpGG43RYGBhQcEzLeo2dibJv7+7wqnV4MdFV6ZBFUIwIT5xTEhAB1EkjObbYnmhrTOBz9EVQetjhSwazhZarRYpd8sWg6kteEkAQCav+orPCUR9TwwaNuLF5h+lSRGNrq02qJn0sVRHmHZs+neFmVs=
Received: from BN7PR11MB2547.namprd11.prod.outlook.com (2603:10b6:406:af::18) by BN6PR11MB4163.namprd11.prod.outlook.com (2603:10b6:405:7f::37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Wed, 13 Jan 2021 04:36:34 +0000
Received: from BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::9195:40a8:5888:b23d]) by BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::9195:40a8:5888:b23d%4]) with mapi id 15.20.3742.012; Wed, 13 Jan 2021 04:36:34 +0000
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Tadahiko Ito <tadahiko.ito.public@gmail.com>
CC: LAMPS WG <spasm@ietf.org>
Thread-Topic: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
Thread-Index: AQHW6Kv3aM0rHe5fHkSwnlXF0ftpA6ok6jLA
Date: Wed, 13 Jan 2021 04:36:33 +0000
Message-ID: <BN7PR11MB25477FEB059BB4ACA3545B7AC9A90@BN7PR11MB2547.namprd11.prod.outlook.com>
References: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com>
In-Reply-To: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [68.93.142.48]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 170a3c80-b0ff-418e-b532-08d8b77cceb0
x-ms-traffictypediagnostic: BN6PR11MB4163:
x-microsoft-antispam-prvs: <BN6PR11MB41634C7B3CCA2CC2CB4E7320C9A90@BN6PR11MB4163.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: EfH0MepsiSg6y1gp4tRHxWLHQ3t5rE6lkj59W1U31qhUXRVHYf4hPiizhDPPbx/OgSzTYCvWVUMnDlXuZOxp/qHkC020K/I6v4xeP3XUZ8iY5fwkwLbZoTAjQhx1B7qf9HGZextC5pjcMYZ8vm8uacyKQdpzMlqr+rra6ZXthK9C7shJJUAoZ58Sw0GaDPT4XqjoIzJEW0rB9PVMA2KPaoodY8IQ7DbPAdnE/rFj69fej0ERK6XLASTMUHHK3Wqch6UxFVKC281BzVSse+2qZRnfDIUy5Biz4kO+YHsyyFNsFAhLQPajb7BgUoDV679ZMwu8lqyPmlIe9vnnsY8Ob1+6aXoG+OdztyabY6r3BHQdhxMYOflclONxbbwcjHb0TriZFDfBPe1JXm6+VDo/qpenYHx/uLr1b8gA7sxnQ+Xt+ODQFxfx0lzOWrHaM50cChqNrUlI+k5qOYNHps6vIw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BN7PR11MB2547.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(136003)(376002)(366004)(346002)(39860400002)(186003)(66556008)(76116006)(166002)(66476007)(6506007)(83380400001)(66616009)(66946007)(2906002)(64756008)(6916009)(66446008)(4326008)(478600001)(8936002)(71200400001)(86362001)(8676002)(52536014)(33656002)(99936003)(53546011)(5660300002)(26005)(55016002)(7696005)(316002)(9686003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?bWFmMzhjWFAzZ05OMndiTFhHQVRkUzJxUTNTWFIrODBYNE05aXhUdmRHSURv?= =?utf-8?B?WC8ycllpbHZ5NjdHNlNBcW5WSFVhSXZpRGwyNkc0ZG9UTEpQeGs0d291R2NW?= =?utf-8?B?bDFnVEFvVURqYlROT1Y4TUxldXVOR1hhNDNPcm0rbXpIV2FBQmw5UlVkbzdJ?= =?utf-8?B?cDRJb3VkbUZmQ01FL01xWmh1bm1udVZNSzkwTnFEdFBlUWVGeUtMdjJUOXRD?= =?utf-8?B?b1grQUJIQ1lSN1BpT3QwNEZwT1NpZjlHZXRUcTBReGlhNzZucHhyM3liK0w1?= =?utf-8?B?SDVBMlU0bGk5NVNlZ1M5cWxiLzVPd2xqVDhzT2MzdFp4dURmYTBUMkp4R2E0?= =?utf-8?B?aVlzTkVUMFdWTnExQjZMWFA2UytCNzJtZCtJUnloL2w0V3JnUkJTRTRvazNu?= =?utf-8?B?MDF4TTFqUGU4eUptZDVQRHZLU2Q3UUN2YnNac0RsVThFWm44cEdNaXRjQjhy?= =?utf-8?B?dzhqVzhJMzN2N0c4K0lONWNJNytmbjZNYnhKS3k5K0ZLZDhUMXlxMTBwa2tY?= =?utf-8?B?RXNkWnlTd1h6TnJ4K2hQMHZGRjhxSHkyMlRBMEp0dzdWaDJHeldjVVpWMkxG?= =?utf-8?B?Um9aM3JBbW5HeGI3akpaNGx0NnZYT1lUMkZTTERRelUzSzIrcE5hTTJkWm1r?= =?utf-8?B?S3Azb0JQM3JVN0wzRm9FUXVXLzduUE5iTFMxb3MvbUFWamJ3VUtXeWtvWndk?= =?utf-8?B?MkE3OVBneExuZVBPcTdXNmdncFZlQ3loVjMwalI0ZXRRUEE1WURrdkpwZ3Q3?= =?utf-8?B?U0NENnVOdkhYZ3QyT3dBcVM2MVg2SFhvbS9UWTQvMTFVSDRMSE5LQ1F5cEFr?= =?utf-8?B?YjFXekhWbUFYSUQrMm55OVByMXo0d0pzUjF2RDZ0MUFmWU91c2tqWHJPNGNU?= =?utf-8?B?Y1diWWJMTlF1a0RIZTJsall2VzlLQTN3VytnKzVJNkdkYkloSkFzSW5lQnRO?= =?utf-8?B?N1kvbXp4eFNjelBETmdIV2JDbmxQWitrSVpxRmk5U3F0WFh6Y0tiN3RtMkpR?= =?utf-8?B?bG9sd3VKRUo2SXN3Zm11S3k0VXdLcDNlU3JZd0NWT2llZklBMmhHejVna0hz?= =?utf-8?B?UTRLa2lwd1Rsakt2ei9mN3Z1WUo5WVNvRzFlY01QUDFLekFQejM2ZVgyUWFh?= =?utf-8?B?L2NJVUs2NXZ3VkxCR0NvUm0vRzNGUkY0OHgrWWc3eXNXdzVZb0lXUTVMN1pm?= =?utf-8?B?YlNWSnJQQmZBV2F0cm40WnZON2k3ZmdMSk43eDFWRGhCQXh1Z2c5UHJzY3dl?= =?utf-8?B?d3pPQXRBcnhlbTg4R1VXT0ZpblFsdi9PdjVLM0VaVGNSREtkVFdaUHU3UTRu?= =?utf-8?Q?/LZeYidOhjZE4=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=2.16.840.1.101.3.4.2.1; boundary="----=_NextPart_000_002D_01D6E93B.C1AB2750"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN7PR11MB2547.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 170a3c80-b0ff-418e-b532-08d8b77cceb0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2021 04:36:34.3820 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 6dej8cmdg8R81ywzcJLLarnT8mRDNFVetPLTbocCglrlIbmWQXhrJq0OgVNrKfg0Fqag1Su/5h/RuyjNhFnwgg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB4163
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/bDi3GeBwCcECBRWU8Y4U64niDw8>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 04:36:41 -0000

------=_NextPart_000_002D_01D6E93B.C1AB2750
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_002E_01D6E93B.C1AB4E60"


------=_NextPart_001_002E_01D6E93B.C1AB4E60
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit

Hi Tadahiko-san,



We dealt with a similar issue when trying to introduce HBS signatures in CMS 
implementations with an API which demanded the message digest function.



I think for such usecases someone could do the same as in Ed25519ph and 
Ed448ph. You pre-hash/digest the message and pass that to the PQ signature 
API. Not ideal because of collisions, but as long as the hash/digest function 
is collision resistant and offers at least as many classical and PQ bits of 
security as the PQ signature scheme, you are OK.



For example you could define a DilithiumIII identifier and a DilithiumIIIph 
identifier. The latter can hardcode SHA2-512(M) as the digest, or 
SHAKE256(M,64) similar to what RFC8032 does.



Rgs,

Panos





From: Spasm <spasm-bounces@ietf.org> On Behalf Of Tadahiko Ito
Sent: Tuesday, January 12, 2021 1:26 AM
To: Russ Housley <housley@vigilsec.com>
Cc: LAMPS WG <spasm@ietf.org>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28



Hi Russ



I also want to talk a bit about separation of hash and asymmetric function.

It seems we cannot separate those functions in some PQC algorithms.

In current RSA or ECC, we use data control service to calculate hash function 
part, and use key management service to calculate asymmetric function part for 
large file.



For instance, we (our company) currently have a usecase of signing 10GB PDF 
file (with HSM). Separation of those functions is necessary for such a 
usecases according to limitation in HSM resource.



It would be OK if we introduce one more hash function to signing data, but I 
believe it may damage interoperability. I would like to ask what we should do 
in such a usecase.



My draft paper is following (it is a draft, we are not sure if we can revise 
before the meeting)

<https://eprint.iacr.org/2020/990>



Regards Tadahiko Ito


------=_NextPart_001_002E_01D6E93B.C1AB4E60
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Yu Mincho";}
@font-face
	{font-family:"\@Yu Mincho";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap:break-word'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Tadahiko-san, <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>We dealt with a similar =
issue when trying to introduce HBS signatures in CMS implementations =
with an API which demanded the message digest function. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I think for such =
usecases someone could do the same as in Ed25519ph and Ed448ph. You =
pre-hash/digest the message and pass that to the PQ signature API. Not =
ideal because of collisions, but as long as the hash/digest function is =
collision resistant and offers at least as many classical and PQ bits of =
security as the PQ signature scheme, you are OK. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>For example you could =
define a DilithiumIII identifier and a DilithiumIIIph identifier. The =
latter can hardcode SHA2-512(M) as the digest, or SHAKE256(M,64) similar =
to what RFC8032 does.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Rgs, =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Panos<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b>From:</b> Spasm =
&lt;spasm-bounces@ietf.org&gt; <b>On Behalf Of </b>Tadahiko =
Ito<br><b>Sent:</b> Tuesday, January 12, 2021 1:26 AM<br><b>To:</b> Russ =
Housley &lt;housley@vigilsec.com&gt;<br><b>Cc:</b> LAMPS WG =
&lt;spasm@ietf.org&gt;<br><b>Subject:</b> Re: [lamps] Call for =
Presentations at the LAMPS Interim Meeting on 28<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu Mincho",serif;color:black'>Hi =
Russ<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu =
Mincho",serif;color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu Mincho",serif;color:black'>I =
also want to talk a bit about separation of hash and asymmetric =
function.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu Mincho",serif;color:black'>It =
seems we cannot separate those functions in some PQC =
algorithms.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu Mincho",serif;color:black'>In =
current RSA or ECC, we use data control service to calculate hash =
function part, and use key management service to calculate asymmetric =
function part for large file.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu =
Mincho",serif;color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu Mincho",serif;color:black'>For =
instance, we (our company) currently have a usecase of signing 10GB PDF =
file (with HSM). Separation of those functions is necessary for such a =
usecases according to limitation in HSM =
resource.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu =
Mincho",serif;color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu Mincho",serif;color:black'>It =
would be OK if we introduce one more hash function to signing data, but =
I believe it may damage interoperability. I would like to ask what we =
should do in such a usecase.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu =
Mincho",serif;color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu Mincho",serif;color:black'>My =
draft paper is following (it is a draft, we are not sure if we can =
revise before the meeting)<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu =
Mincho",serif;color:black'>&lt;<a =
href=3D"https://eprint.iacr.org/2020/990">https://eprint.iacr.org/2020/99=
0</a>&gt;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu =
Mincho",serif;color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:10.5pt;font-family:"Yu =
Mincho",serif;color:black'>Regards Tadahiko =
Ito<o:p></o:p></span></p></div></div></div></body></html>
------=_NextPart_001_002E_01D6E93B.C1AB4E60--

------=_NextPart_000_002D_01D6E93B.C1AB2750
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCDGkw
ggNDMIICK6ADAgECAhBf+HsoK1TcjUKjFbVoya3/MA0GCSqGSIb3DQEBBQUAMDUxFjAUBgNVBAoT
DUNpc2NvIFN5c3RlbXMxGzAZBgNVBAMTEkNpc2NvIFJvb3QgQ0EgMjA0ODAeFw0wNDA1MTQyMDE3
MTJaFw0yOTA1MTQyMDI1NDJaMDUxFjAUBgNVBAoTDUNpc2NvIFN5c3RlbXMxGzAZBgNVBAMTEkNp
c2NvIFJvb3QgQ0EgMjA0ODCCASAwDQYJKoZIhvcNAQEBBQADggENADCCAQgCggEBALCauaunrwp3
p+JxtrRmYpR4iEfGYlWEQDK/wKsupRxx1rxue6iqum7SFYhIRZ2i/IPQzLmM4CZocEp43yEXnvRh
BckVyM8W2jVhiZRDqISoMZh4m7lObyxTEmzNHa0rJLsxxCv/g0Rvtj0kdwnqvyqoH2pW9iAPEVSX
gXWnJc5ZaoJl77fq5+KNdYtu8t1Ppl5inM8QCmTQTm3OK8xb9WClJ0eNafR/zhtw3nAbINZuzaYB
qDwS0qk/oGteu44gi3qR47Vo7qDnxAF0qFMLK0qaD2USDoJNjmP97+ubGttTphNgr8J918dsFyXU
c/tHZFCBgJRM4b+uSxzfku0uBd8CAQOjUTBPMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/
MB0GA1UdDgQWBBQn88gVHm6aAgkWrSugiWBf2nsvqjAQBgkrBgEEAYI3FQEEAwIBADANBgkqhkiG
9w0BAQUFAAOCAQEAnZ2EhKNBqXx3DLdTyk5EUGLvVHzTdRcc6ODGSEu2/kw6GYFWsFbuGZZiqlqj
ZMH2TlQzxnf+xRy65V0lyvXwk5qDES7my/h0Rf7nBbir59/LS+E3hNq5i5dwHvDii9ew2A6dsWnW
KpF7qUlPfuaOldiDJzzVaEkO1J32LuunvuswpKwfRPyVqzMG+31gCt60imOwnKnypLlTAYfQaKQn
f6v/6frJQDiIZ7Q5xoRvV8lT27qO7sBDsvgJg27/Zs8+7xezWBglCTRe48vWFLbs8pJvdOQvgSrV
kpHg4Jc8MmgFhUvR91fiUh2TGlSfBXDASnFgHkMLYB7+o86BGeELNTCCBG4wggNWoAMCAQICCmEQ
gG0AAAAAAA4wDQYJKoZIhvcNAQEFBQAwNTEWMBQGA1UEChMNQ2lzY28gU3lzdGVtczEbMBkGA1UE
AxMSQ2lzY28gUm9vdCBDQSAyMDQ4MB4XDTE0MDQwNDIwMjQxOFoXDTI5MDUxNDIwMjU0MlowLDEO
MAwGA1UEChMFQ2lzY28xGjAYBgNVBAMTEUNpc2NvIEVtcGxveWVlIENBMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAyt9+FkxTFfsjVs3GuWUKBJXl3kxFZ4wMxwbgqx9tXzcqe+fto62A
fxHI84Lr7p9Q2cm/PaEvuzwRBzXvuKXZUU7ZsPdToJSALCySZa0Qb6GGa19ACpmlUEQakE3P5kz7
RgaNSOMH1+GtY9fV6CcAFb9uB7JDu2UGL332WV2bEsUsfb3rRLBS4cL8Hu2dWfcdk6erMaZCQjkn
04FixlQsJozbPRTQqI4V6iikG/69rDyeTdbVTK+My/9LnwVsD3GBMiRh7RmrvupxtGiMu8j05Is/
d1OifhWecwvjV3Reg9Lok8bMNJEMAped1weTdVS0X4MsAheosJBld9lS5O4idwIDAQABo4IBhzCC
AYMwEAYJKwYBBAGCNxUBBAMCAQAwHQYDVR0OBBYEFJ+VNrSOXdVLwwrBpymTQ1EG/YlRMBkGCSsG
AQQBgjcUAgQMHgoAUwB1AGIAQwBBMAsGA1UdDwQEAwIBhjASBgNVHRMBAf8ECDAGAQH/AgEAMB8G
A1UdIwQYMBaAFCfzyBUebpoCCRatK6CJYF/aey+qMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly93
d3cuY2lzY28uY29tL3NlY3VyaXR5L3BraS9jcmwvY3JjYTIwNDguY3JsMFAGCCsGAQUFBwEBBEQw
QjBABggrBgEFBQcwAoY0aHR0cDovL3d3dy5jaXNjby5jb20vc2VjdXJpdHkvcGtpL2NlcnRzL2Ny
Y2EyMDQ4LmNlcjBcBgNVHSAEVTBTMFEGCisGAQQBCRUBFQAwQzBBBggrBgEFBQcCARY1aHR0cDov
L3d3dy5jaXNjby5jb20vc2VjdXJpdHkvcGtpL3BvbGljaWVzL2luZGV4Lmh0bWwwDQYJKoZIhvcN
AQEFBQADggEBAD5OviMaRgKNXmvbigI0C2Ob5QE8Jl2McLIk62Be7IqEZC4bWRWjZxrhFuP94E19
RJojKNLttveiH+dEze1t6oYhVCisbGG8+8hlUARAiiqL/J9uGJ71xT6loqkcAK5xphe7STJLSlgT
k0w26fcvDeiA6zhdVHnKhVKkpOJWd9MNByFOnCQyDOK+pcNxLU6IN9TwL1ZoRkdFa11QiCX3Oimk
8YhBrVN+VzGGKtbgZ4fYU6uBo3V3vtshyDpHtGkn1e7f9/TWcY26etFzL33dzaZ4lChlw4l3XkLq
6AfCEDF5djpBdiCRjwpBUIIbCSmyESBvA+sL4j8i1vo/uEartrAwggSsMIIDlKADAgECAgoBhhEi
QTzquitVMA0GCSqGSIb3DQEBCwUAMCwxDjAMBgNVBAoTBUNpc2NvMRowGAYDVQQDExFDaXNjbyBF
bXBsb3llZSBDQTAeFw0xOTEyMjAxOTQ5MDJaFw0yMTEyMTkxOTU5MDJaMIGfMSQwIgYDVQQDExtQ
YW5vcyBLYW1wYW5ha2lzIChwa2FtcGFuYSkxFDASBgNVBAsTC0Npc2NvIFVzZXJzMRIwEAYDVQQL
EwlFbXBsb3llZXMxEzARBgoJkiaJk/IsZAEZEwNjb20xFTATBgoJkiaJk/IsZAEZEwVjaXNjbzEh
MB8GCSqGSIb3DQEJAQwScGthbXBhbmFAY2lzY28uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAmIHTLIzoAnuMUiHMx8V+PF9JpAcB7zrNHOY1Vj1R1Vx7ty7m9yo9G991T2n7zHo4
UzF6tnB9NxzQOKCY54oqP5KjVGYOPPo+qZ+2rx1GABzdKUF4LwUUKOTf9uXAtvsvIRUc5J/csShT
jcUIvtVmiAzWXWRfMYShjBYBVtx/h8fDqAqfFAzd6HG0TcdsN/BRb9k6QEW1afHjPKlRUaDRELyj
nFGJZd2OsUJ7/aKMdFmQFd2CAJYzsuwLYjeqJsuGNzBc/k6mzQPf6FW17nz17G41KReU0UdZf2yZ
jvimkwCQ/yW8SVTOcGBP+Zk+Lq5EYEGQMu1qtNK/97bXMc5kuwIDAQABo4IBWjCCAVYwDgYDVR0P
AQH/BAQDAgTwMAwGA1UdEwEB/wQCMAAwegYIKwYBBQUHAQEEbjBsMDwGCCsGAQUFBzAChjBodHRw
Oi8vd3d3LmNpc2NvLmNvbS9zZWN1cml0eS9wa2kvY2VydHMvY2VjYS5jZXIwLAYIKwYBBQUHMAGG
IGh0dHA6Ly9wa2ljdnMuY2lzY28uY29tL3BraS9vY3NwMB8GA1UdIwQYMBaAFJ+VNrSOXdVLwwrB
pymTQ1EG/YlRMDoGA1UdHwQzMDEwL6AtoCuGKWh0dHA6Ly9jaXNjb2NlcnRzLmNpc2NvLmNvbS9m
aWxlL2NlY2EuY3JsMB0GA1UdEQQWMBSBEnBrYW1wYW5hQGNpc2NvLmNvbTAdBgNVHQ4EFgQUjrl7
6Mrrdw3ZYFiTpZBdtrUm5P4wHwYDVR0lBBgwFgYKKwYBBAGCNwoDDAYIKwYBBQUHAwQwDQYJKoZI
hvcNAQELBQADggEBAMhR6xCTygu68lppjWebXTXYznix5961hcmwiJRkPtUIGQ5JQwXyCwq/Juuq
yc5ebeq9cQEO5iqyxik/UAQ35BlmKb7SNLi75RtFE/AIZrRsEjTUoO2EtCMQOEMcenWa2XE8fEID
BkwzreKeaOchCbDd4L9PvKFht6nDDFtb6VZdWs4ort+J3iFeilVf3oI5MSVi+qroWaFLnLYTQGTn
qEjWANfKw3RRBAMdoPCZ+N4eftAk1TWVS08nOsPoKWXtIqX6y0ZPs/EZjBSk57v1TPLpYhEqYGXI
oGJlIvzIAfYNoUg8yP8toG5T7x+7hRz0MMUGWcCDsS9PMFxH6SnrUSMxggMNMIIDCQIBATA6MCwx
DjAMBgNVBAoTBUNpc2NvMRowGAYDVQQDExFDaXNjbyBFbXBsb3llZSBDQQIKAYYRIkE86rorVTAN
BglghkgBZQMEAgEFAKCCAaQwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMjEwMTEzMDQzNjMxWjAvBgkqhkiG9w0BCQQxIgQg1T+OPUBEQ4teaMcBchdcPlfsP0r3NQTJ
4GVrsKEANWwwSQYJKwYBBAGCNxAEMTwwOjAsMQ4wDAYDVQQKEwVDaXNjbzEaMBgGA1UEAxMRQ2lz
Y28gRW1wbG95ZWUgQ0ECCgGGESJBPOq6K1UwSwYLKoZIhvcNAQkQAgsxPKA6MCwxDjAMBgNVBAoT
BUNpc2NvMRowGAYDVQQDExFDaXNjbyBFbXBsb3llZSBDQQIKAYYRIkE86rorVTCBoAYJKoZIhvcN
AQkPMYGSMIGPMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCgYIKoZIhvcNAwcwCwYJYIZIAWUD
BAECMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDALBglghkgBZQMEAgEwCwYJKoZIhvcN
AQEKMAsGCWCGSAFlAwQCAzALBglghkgBZQMEAgIwBwYFKw4DAhowDQYJKoZIhvcNAQEBBQAEggEA
SaLzYBuGLbYyEaEnI5JhMxoI3asSRuNGGOor1rOsMLBWP5ghwEmC8cuHmRH56C4x9BbfRF8jD2SL
Y6gtdQp8UHyplI5r38VEguvlZg09e7Fr2xeicofJPy2oJ5kXeO4ivuZADAR096biVCBZlOBeitFx
0I5ti9vaP/1XtQdJdxJFRd/dh8y1TW9o8SloCY60hg8e5Vebq8AwUWMTCX86phf9wlDOALgmbLWG
dY7Q9xg6no9xwRS7VA+eEnFlgVDcLbh1Talg6yJUBxT5j1/r6wl8X1wcv0E/hw8ZESviY/PlnXsZ
y5AZd7+slPZuPl3DlGB5hkmfZ1RI1g72l7WfAgAAAAAAAA==

------=_NextPart_000_002D_01D6E93B.C1AB2750--


From nobody Wed Jan 13 02:57:26 2021
Return-Path: <tadahiko.ito.public@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 486B13A0147 for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 02:57:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J13GI6M9sTAG for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 02:57:23 -0800 (PST)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBA873A0100 for <spasm@ietf.org>; Wed, 13 Jan 2021 02:57:22 -0800 (PST)
Received: by mail-io1-xd31.google.com with SMTP id u17so3222446iow.1 for <spasm@ietf.org>; Wed, 13 Jan 2021 02:57:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=pf4J2PRxpzWCjpYLxT7KS9qHg7I83RX0Rc1ND4mwFP8=; b=S3nh39drLycMUlrbDB+MwQ5kG8+TLnnxOJPKGKITH4vzVyGMYbjbtNIz8Gd7sF5vkZ 3CHYTTAsRkOdtrJQPLHv0iCPA+aVCN15doJiViWau+M23xz0MR+AsgV5jWH6NQLW2PlZ 9mn8IgymbDPoSmOseK47aSswsHLEOuRwJ6yAmaHTgNYpAftbX6XAiV/6FXUvKgVCuECC b/cR5zqm0SinBrSAzeJLd0xQIdMdPPN0SS9C1kYEQYB1OsjQuLpLRRB9Kr5Dga1+5PXr R8zdcAGUAGpqzyn8BNVzeBMFJIfXKKv9xt1PLJqpAwKF1YQY2l+qG1Yp4LkH6tOb7WhO 90jA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pf4J2PRxpzWCjpYLxT7KS9qHg7I83RX0Rc1ND4mwFP8=; b=AbfK9ya9YKRQnYCzRMNa6/AXXnEFOukOvrn2riUt5iPjdcaH2mG1JqP0B+mkTqjJvv 2hDXo/CIK6GoKEbtVUPkLSiaxPt8C02QOJCDFVmwsQp1PuRh5sGQYWsxb6PV6UpC6vsD ggnLYWe3393nTt1SZtMBV05KBceXsgb63LhZvef3elgEUih0oGfqRax3NM53MTCdmmuu mlZKXm/H1q+BdG/uFq9ET2gPHvQHcujDnJFZZC9abiXvGJcXonphTRTo0ZgVgKrw1K0q 1hKDqA8iRhRjBTw+1ldzhNrzKhc10hxzB/RczwN/zQfYAv+/QCs3ellGjyk4JOZoIFlv xzIw==
X-Gm-Message-State: AOAM531XvzC+vIJRrHiKY7EOfDfublbEE+uNJEKMTa7Gh3Hb/4jzggD5 JorcYKfeyaIWjFRHQVpidtII3nhnan6j+COkXPQ=
X-Google-Smtp-Source: ABdhPJwjYUQKnu8cTTQxb0dLE++gqstX9EAb3xol0oWQDDDghxGGilXXcy5lsg3VW2S0jV/88kw+V8lBaa7KI+e0AFk=
X-Received: by 2002:a92:cd81:: with SMTP id r1mr1738739ilb.252.1610535442114;  Wed, 13 Jan 2021 02:57:22 -0800 (PST)
MIME-Version: 1.0
From: Tadahiko Ito <tadahiko.ito.public@gmail.com>
Date: Wed, 13 Jan 2021 19:57:11 +0900
Message-ID: <CAFTXyYC_+yyYFt15tnrzr-Nc0RFxrz9S4FEePYcE0_VUMRhRSg@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>, Mike.Ounsworth@entrust.com, pkampana@cisco.com, LAMPS WG <spasm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ececb305b8c600f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/bEI_m9gor6ATuvN_UqRAAwMqSAE>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 10:57:24 -0000

--000000000000ececb305b8c600f2
Content-Type: text/plain; charset="UTF-8"

Hi Russ

>> It seems you are talking about PQC signatures in CMS.  PDF signatures
employ an early version on CMS.  Would you be able to make a presentation
at the interim meeting?

Sure.
I would explain CMS part of the PDF signature also. They use CMS with only
one SignatureValue. It is just my opinion, but a separate signature seems
more suitable for PDF signing.


Hi Mike

>> I would support LAMPS looking at this, though it probably needs
involvement from other groups, especially on the security proof side.

Thank you very much.
Proof may not be that difficult for those people, but I believe we should
at least discuss that topic.


Hi Panos

>> For example, you could define a DilithiumIII identifier and a
DilithiumIIIph identifier. The latter can hardcode SHA2-512(M) as the
digest, or SHAKE256(M,64) similar to what RFC8032 does.

I totally agree, but I feel like we should have some consensus on which and
how to use digest function.
(It should be easier for the crypto library to process. I dislike the
situation where each company ends up using different use of hash
algorithms.)

Regards Tadahiko Ito

--000000000000ececb305b8c600f2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Russ</div><div><br></div><div>&gt=
;&gt; It seems you are talking about PQC signatures in CMS.=C2=A0 PDF signa=
tures employ an early version on CMS.=C2=A0 Would you be able to make a pre=
sentation at the interim meeting? =C2=A0</div><div><br></div><div>Sure.</di=
v><div>I would explain CMS part of the PDF signature also. They use CMS wit=
h only one SignatureValue. It is just my opinion, but a separate signature =
seems more suitable for PDF signing.</div><div><br></div><div><br></div><di=
v>Hi Mike</div><div><br></div><div>&gt;&gt; I would support LAMPS looking a=
t this, though it probably needs involvement from other groups, especially =
on the security proof side.</div><div><br></div><div>Thank you very much.=
=C2=A0</div><div>Proof may not be that difficult for those people, but I be=
lieve we should at least discuss that topic.</div><div><br></div><div><br><=
/div><div>Hi Panos</div><div><br></div><div>&gt;&gt; For example, you could=
 define a DilithiumIII identifier and a DilithiumIIIph identifier. The latt=
er can hardcode SHA2-512(M) as the digest, or SHAKE256(M,64) similar to wha=
t RFC8032 does.</div><div><br></div><div>I totally agree, but I feel like w=
e should have some consensus on which and how to use digest function.</div>=
<div>(It should be easier for the crypto library to process. I dislike the =
situation where each company ends up using different use of hash algorithms=
.)</div><div><br></div><div>Regards Tadahiko Ito</div></div></div>

--000000000000ececb305b8c600f2--


From nobody Wed Jan 13 06:52:43 2021
Return-Path: <quynh.dang@nist.gov>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23F1B3A10CF for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 06:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.247
X-Spam-Level: 
X-Spam-Status: No, score=-3.247 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FROM_GOV_DKIM_AU=-0.998, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nist.gov
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vixZWrLRb15M for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 06:52:38 -0800 (PST)
Received: from GCC02-DM3-obe.outbound.protection.outlook.com (mail-dm3gcc02on2092.outbound.protection.outlook.com [40.107.91.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01CFC3A10C1 for <spasm@ietf.org>; Wed, 13 Jan 2021 06:52:37 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Dpk858A8DJkCALOoKoOUjv76k6b2zmyBLSDge5ZLl60zovVRy31Iq/hvdEXeeNq78GBZhp7CYyt2YozrP6AfCN/DTf6r8TjJ/gpe0VJpTcqQ6TEFApWEK8ePtyETPg4nYp5vkApmsH81DoRV4TLGF4SVA4M9Ut79/6ShkDde22OzbVTbDhIsXRELp3FFaP5Aiwosp2ZAUFm3ExUg7XAVVrv7iPF0YkYX63+zTkx7xNywPM5SVnGdFHjP9PuEGgpaDPN8RbOHzRwT0JyN3UvLTJ9MBwAVken96m2DbTARm8WWTcwwwOCGcc46UhTkN+yawUNhVMldbXWfk4+PKOCJ9A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FY0NXiGwnjSxKvLQcBJ9x1BzzaPMClTqoPhNKot4Uw8=; b=W5T0h+ls0k3GWvjQu54hNmkJbopIVfKp3RU2d9YDTDgPN1k6cytAbko9FU/Xc3j7UW4KbV9M4DunY8c3TrowLFxwTtG72fXxbdFJm+wHroAErkXhPWib+EJbDFoIkRX8PDSRPqsN95c61SXntI+KdNwPHylhrp4sl1qFT9Uv4bSE1kp+Fl9xZovpyIDKzEnOYmysRHl7KIdv/06bkhmgHcUEYVyiYr53huXYzjk8u6K4/t319uLDLqsD9YaknQZj1We/R6OwbCBCYCl7+iimr30UCKVGeJ16PEgG2XGqjhMywJqM9YWLGVVDEw6TigfYvKL4+NQiEAazTfWpYrwDQQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nist.gov; dmarc=pass action=none header.from=nist.gov; dkim=pass header.d=nist.gov; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nist.gov; s=selector2;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FY0NXiGwnjSxKvLQcBJ9x1BzzaPMClTqoPhNKot4Uw8=; b=N1HCQD2vtfEnhL+ulvh6y1rczyxcKwJpJJuTeyOCkQAJtZbFJtL1B8DDHCnEYxaAHrvy7M+KNtK2ebiRrcWgfFIKKv4o0JqI5jBlxKL4+ALVcHMoqHGxMcNW2pGkL2HN4xwf+2kq0r3jLmmQT/R28zWwmrZ2Uo5q748NKk7m5YI=
Received: from DM8PR09MB7238.namprd09.prod.outlook.com (2603:10b6:5:2ea::16) by DM6PR09MB5670.namprd09.prod.outlook.com (2603:10b6:5:264::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10; Wed, 13 Jan 2021 14:52:34 +0000
Received: from DM8PR09MB7238.namprd09.prod.outlook.com ([fe80::2183:9eeb:c223:750a]) by DM8PR09MB7238.namprd09.prod.outlook.com ([fe80::2183:9eeb:c223:750a%6]) with mapi id 15.20.3763.010; Wed, 13 Jan 2021 14:52:33 +0000
From: "Dang, Quynh H. (Fed)" <quynh.dang@nist.gov>
To: "Panos Kampanakis (pkampana)" <pkampana=40cisco.com@dmarc.ietf.org>, Tadahiko Ito <tadahiko.ito.public@gmail.com>
CC: LAMPS WG <spasm@ietf.org>
Thread-Topic: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
Thread-Index: AQHW6Kvv/nE2HrPZ7EiI2EU0kI2Lbaok+f6AgACn3ck=
Date: Wed, 13 Jan 2021 14:52:33 +0000
Message-ID: <DM8PR09MB7238566FA3B17DBCE19A67F1F3A90@DM8PR09MB7238.namprd09.prod.outlook.com>
References: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com>,  <BN7PR11MB25477FEB059BB4ACA3545B7AC9A90@BN7PR11MB2547.namprd11.prod.outlook.com>
In-Reply-To: <BN7PR11MB25477FEB059BB4ACA3545B7AC9A90@BN7PR11MB2547.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=nist.gov;
x-originating-ip: [2610:20:6005:223::12]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 9f621fcd-6825-4138-3c49-08d8b7d2dc48
x-ms-traffictypediagnostic: DM6PR09MB5670:
x-microsoft-antispam-prvs: <DM6PR09MB5670A95CCE53C4B303F2BE02F3A90@DM6PR09MB5670.namprd09.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: EClJe7pNmdughx/o3T6bqUTrsNo7AvBS4H8jakMVcP20qGoOGMoZvYUmbLSJkQaVjaSx2x6eAhYjdkRUFuo7ZINmNPPZEW7TkaViZAyjo+ygmUdDi7y5s0vqcgI8QZ2MlOiLP6vgNjtkJRvwZWzA6CTz8Rw+PTMYsrsJMSpU2XJaxPyKpNKRXap6PxHx2uyZ4Qj9zJ4XMhJKpckN+7Gh/B5oqg+J6lv2wH8HxwRq+UZOquhF2cG2kWcmD5dtuNETwQ1t+E7D8N6hLO1/Qjl49xbnjykh1/5VneMKq9liHC+M2IED8ZQtWbd9xutEuVcF1mdQ42xj1Fl5NxbBtmm2dxnpEVh/2ptnF28eWDm3jMLZWqCx+5358DC0k1GfAFQsfaKXXp4et0K64y++qRmkOy+zyP9SV5Ueus1YpZEDYXai+ENZN6SdBw40wT2f/fNKkNneBW0s0YoF+Zh3AY9qdA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM8PR09MB7238.namprd09.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(366004)(346002)(396003)(376002)(39860400002)(166002)(52536014)(9686003)(8676002)(86362001)(55016002)(33656002)(66476007)(66946007)(64756008)(83380400001)(8936002)(316002)(2906002)(66556008)(66446008)(5660300002)(53546011)(91956017)(76116006)(6506007)(7696005)(186003)(19627405001)(71200400001)(4326008)(110136005)(478600001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?uVV4CbjYxq9iZCVXHqKSj0ykpVA1qgqt6DM1NgJJnHOqVATFsqI3yi9+Ub?= =?iso-8859-1?Q?bg618dGMpvzU0s24oQdIZY7jQt/Fzx9pa5cgqiPXh1eyULImohxLhfV4uT?= =?iso-8859-1?Q?dJmMpw2dFq19ww2E1Lc1kTojMi+9ef88+XDWh1UF1Ic4u7odIaIxQOcpnW?= =?iso-8859-1?Q?DD15/2X2Ibwk9ocE481i7LsUigUbc5xGN1kEpJouFiPmFf6mVna6ZIozcX?= =?iso-8859-1?Q?V6lKh89sMm0dGJyZdjdhxjp2ldI9CU94hpAQEiNheORERY2extqZ1NJIPD?= =?iso-8859-1?Q?jFZ9ptbGnpIIt+WE+674Dz2YCDEqh1JrSbWpcAG4a157GuB7NddAOE+wOK?= =?iso-8859-1?Q?L++OktAUrNoYdiCbKcLeiHJ85FEORMUnljHhrksc+DTzkLLwSBiR8unOGO?= =?iso-8859-1?Q?9KvrNXkbdMMwQIijp05zR4BZpe/1/GxKO4Gl0QkarpRDmhdqPKsZXCiTCs?= =?iso-8859-1?Q?qpHchsPRpMBsTsjzOX+kcFBGFh5amKiO5GOmZNdlOjw+4R+IFYyZITBF6D?= =?iso-8859-1?Q?giUzfVfH1jHZdxzqAI/2QwLBRHRDgXzy0UHwNRjCPe2Zb0rylCmEmP9tRU?= =?iso-8859-1?Q?SzhoP3nLFh41Kwj3G5j4i85R0wTPYyMd+qOhwhYSGs+2Oop+SxUoMMLFbY?= =?iso-8859-1?Q?bCRyEQ5uQtNsNeAI4rmIVmKZ7WOLZ6g5c4BrxzT3le1jTv0Auwl1WZS8kk?= =?iso-8859-1?Q?1+rBJygM+6doP1PB7gd5MnXbi9O3ft42AJrwHSLoHFFqh+clXe61caMROr?= =?iso-8859-1?Q?2NB6ohQLs/g6JjDyPfo44URfBmweIqmdAvGutyaIrXnkF58vL2CV1qiyjd?= =?iso-8859-1?Q?PFovkz3B4Y+hSbe1ocaDlO7rUekVmzh1syAAACyttgn+PQ6EbtxqrfEcxX?= =?iso-8859-1?Q?tZM1EIgGJcb/uOB0uOJVzUMthnIAOFq60gAV53Cmp+gYZAAKEcQpxRE17Z?= =?iso-8859-1?Q?ytsvCeFeicWjm79kVUnm6c2FtLSugJXrQWZsebsYigEUUAIKzK0Vg/w4g1?= =?iso-8859-1?Q?WhPBEjnLO6uIrb6KlGFUO/5+mvdsriJ3Qt6sRb?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM8PR09MB7238566FA3B17DBCE19A67F1F3A90DM8PR09MB7238namp_"
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM8PR09MB7238.namprd09.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9f621fcd-6825-4138-3c49-08d8b7d2dc48
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2021 14:52:33.8626 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 8QDS98K16/mSPeJGDzphZ3Bu8xnz/e0OxfwNPlUV7r3VMuEnMCVuvSXIsaNdLsR5
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR09MB5670
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/UKrGy3J_NN8r_ZCVu6oj02lMw44>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 14:52:41 -0000

--_000_DM8PR09MB7238566FA3B17DBCE19A67F1F3A90DM8PR09MB7238namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Tadahiko and Panos,

If we have pre-hash and non-prehash versions, then the asymmetric operation=
 must be domain-separated between the 2.  Otherwise, obtaining a signature =
from a pre-hash version is an attack on the non-prehash version.

For example, step 10 in Dilithium's signing operation:
hash(tr || M) would become hash(0|| tr || M) and
hash(1|| tr || M) for the pre-hash and non-prehash options, for example.

Regards,
Quynh.

________________________________
From: Spasm <spasm-bounces@ietf.org> on behalf of Panos Kampanakis (pkampan=
a) <pkampana=3D40cisco.com@dmarc.ietf.org>
Sent: Tuesday, January 12, 2021 11:36 PM
To: Tadahiko Ito <tadahiko.ito.public@gmail.com>
Cc: LAMPS WG <spasm@ietf.org>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on=
 28


Hi Tadahiko-san,



We dealt with a similar issue when trying to introduce HBS signatures in CM=
S implementations with an API which demanded the message digest function.



I think for such usecases someone could do the same as in Ed25519ph and Ed4=
48ph. You pre-hash/digest the message and pass that to the PQ signature API=
. Not ideal because of collisions, but as long as the hash/digest function =
is collision resistant and offers at least as many classical and PQ bits of=
 security as the PQ signature scheme, you are OK.



For example you could define a DilithiumIII identifier and a DilithiumIIIph=
 identifier. The latter can hardcode SHA2-512(M) as the digest, or SHAKE256=
(M,64) similar to what RFC8032 does.



Rgs,

Panos





From: Spasm <spasm-bounces@ietf.org> On Behalf Of Tadahiko Ito
Sent: Tuesday, January 12, 2021 1:26 AM
To: Russ Housley <housley@vigilsec.com>
Cc: LAMPS WG <spasm@ietf.org>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on=
 28



Hi Russ



I also want to talk a bit about separation of hash and asymmetric function.

It seems we cannot separate those functions in some PQC algorithms.

In current RSA or ECC, we use data control service to calculate hash functi=
on part, and use key management service to calculate asymmetric function pa=
rt for large file.



For instance, we (our company) currently have a usecase of signing 10GB PDF=
 file (with HSM). Separation of those functions is necessary for such a use=
cases according to limitation in HSM resource.



It would be OK if we introduce one more hash function to signing data, but =
I believe it may damage interoperability. I would like to ask what we shoul=
d do in such a usecase.



My draft paper is following (it is a draft, we are not sure if we can revis=
e before the meeting)

<https://eprint.iacr.org/2020/990<https://gcc02.safelinks.protection.outloo=
k.com/?url=3Dhttps%3A%2F%2Feprint.iacr.org%2F2020%2F990&data=3D04%7C01%7Cqu=
ynh.dang%40nist.gov%7Ca5a2bf18b7a64ce675c808d8b77cdd6d%7C2ab5d82fd8fa4797a9=
3e054655c61dec%7C1%7C0%7C637461094229173904%7CUnknown%7CTWFpbGZsb3d8eyJWIjo=
iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=3D=
4b2EJXVMkBxHH0MYOzjn7bpHzP4CkBFY9BxBKi2yuZE%3D&reserved=3D0>>



Regards Tadahiko Ito

--_000_DM8PR09MB7238566FA3B17DBCE19A67F1F3A90DM8PR09MB7238namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<span style=3D"font-family: Candara, Optima, sans-serif;">Hi Tadahiko and P=
anos,&nbsp;</span></div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<span style=3D"font-family: Candara, Optima, sans-serif;">If we have pre-ha=
sh and non-prehash versions, then the asymmetric operation must be domain-s=
eparated between the 2.&nbsp; Otherwise, obtaining a signature from a pre-h=
ash version is an attack on the non-prehash
 version.&nbsp;</span></div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<span style=3D"font-family: Candara, Optima, sans-serif;">For example, step=
 10 in Dilithium's signing operation:&nbsp;</span></div>
<div><span style=3D"font-family: Candara, Optima, sans-serif;">hash(tr || M=
) would become&nbsp;</span><span style=3D"color: rgb(0, 0, 0); font-size: 1=
4px; font-family: Candara, Optima, sans-serif;">hash(0|| tr || M)</span><sp=
an style=3D"color: rgb(0, 0, 0); font-size: 14px; font-family: Candara, Opt=
ima, sans-serif;">&nbsp;and&nbsp;</span></div>
<span style=3D"background-color: rgb(255, 255, 255); display: inline !impor=
tant; font-family: Candara, Optima, sans-serif;">hash(1|| tr || M)</span><s=
pan style=3D"background-color:rgb(255, 255, 255);display:inline !important"=
><span style=3D"font-family: Candara, Optima, sans-serif;">&nbsp;for
 the pre-hash and non-prehash options, for example.&nbsp;</span></span>
<div><br>
</div>
<div><span style=3D"font-family: Candara, Optima, sans-serif;">Regards,</sp=
an></div>
<div><span style=3D"font-family: Candara, Optima, sans-serif;">Quynh.&nbsp;=
</span><br>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Spasm &lt;spasm-bounc=
es@ietf.org&gt; on behalf of Panos Kampanakis (pkampana) &lt;pkampana=3D40c=
isco.com@dmarc.ietf.org&gt;<br>
<b>Sent:</b> Tuesday, January 12, 2021 11:36 PM<br>
<b>To:</b> Tadahiko Ito &lt;tadahiko.ito.public@gmail.com&gt;<br>
<b>Cc:</b> LAMPS WG &lt;spasm@ietf.org&gt;<br>
<b>Subject:</b> Re: [lamps] Call for Presentations at the LAMPS Interim Mee=
ting on 28</font>
<div>&nbsp;</div>
</div>
<div lang=3D"EN-US" style=3D"word-wrap:break-word">
<div class=3D"x_WordSection1">
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">Hi Tadahiko-san, </span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">We dealt with a similar issue when trying to =
introduce HBS signatures in CMS implementations with an API which demanded =
the message digest function.
</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">I think for such usecases someone could do th=
e same as in Ed25519ph and Ed448ph. You pre-hash/digest the message and pas=
s that to the PQ signature API. Not ideal because of collisions, but as lon=
g as the hash/digest function is collision
 resistant and offers at least as many classical and PQ bits of security as=
 the PQ signature scheme, you are OK.
</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">For example you could define a DilithiumIII i=
dentifier and a DilithiumIIIph identifier. The latter can hardcode SHA2-512=
(M) as the digest, or SHAKE256(M,64) similar to what RFC8032 does.</span></=
p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">Rgs, </span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">Panos</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<span style=3D"color:#1F497D">&nbsp;</span></p>
<div style=3D"border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
<b>From:</b> Spasm &lt;spasm-bounces@ietf.org&gt; <b>On Behalf Of </b>Tadah=
iko Ito<br>
<b>Sent:</b> Tuesday, January 12, 2021 1:26 AM<br>
<b>To:</b> Russ Housley &lt;housley@vigilsec.com&gt;<br>
<b>Cc:</b> LAMPS WG &lt;spasm@ietf.org&gt;<br>
<b>Subject:</b> Re: [lamps] Call for Presentations at the LAMPS Interim Mee=
ting on 28</p>
</div>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;">
&nbsp;</p>
<div>
<div>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">Hi Russ</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">I also want to talk a bit about separation of hash and asymmetr=
ic function.</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">It seems we cannot separate those functions in some PQC algorit=
hms.</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">In current RSA or ECC, we use data control service to calculate=
 hash function part, and use key management service to calculate asymmetric=
 function part for large file.</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">For instance, we (our company) currently have a usecase of sign=
ing 10GB PDF file (with HSM). Separation of those functions is necessary fo=
r such a usecases according to limitation in
 HSM resource.</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">It would be OK if we introduce one more hash function to signin=
g data, but I believe it may damage interoperability. I would like to ask w=
hat we should do in such a usecase.</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">My draft paper is following (it is a draft, we are not sure if =
we can revise before the meeting)</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">&lt;<a href=3D"https://gcc02.safelinks.protection.outlook.com/?=
url=3Dhttps%3A%2F%2Feprint.iacr.org%2F2020%2F990&amp;data=3D04%7C01%7Cquynh=
.dang%40nist.gov%7Ca5a2bf18b7a64ce675c808d8b77cdd6d%7C2ab5d82fd8fa4797a93e0=
54655c61dec%7C1%7C0%7C637461094229173904%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC=
4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=
=3D4b2EJXVMkBxHH0MYOzjn7bpHzP4CkBFY9BxBKi2yuZE%3D&amp;reserved=3D0" origina=
lsrc=3D"https://eprint.iacr.org/2020/990" shash=3D"tnsx6UmfIZzaiNs/hNefQyVo=
rSCJ5pOaPy6NFuzGEVbW6s88IMqnZYfoG01Vtj27k+aZpAx+KK5fjVYrks+Lvivdk6w7CWXdSuA=
unl67By2c3RDjrJlYVpVkYv16LT6Nk3PZou3vOuPSXvl/Fw5pWEKsRjMjyO/i/lmdYwOpZCE=3D=
">https://eprint.iacr.org/2020/990</a>&gt;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">&nbsp;</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0in; font-size: 11pt; font-family=
: Calibri, sans-serif;text-align:justify">
<span style=3D"font-size:10.5pt; font-family:&quot;Yu Mincho&quot;,serif; c=
olor:black">Regards Tadahiko Ito</span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_DM8PR09MB7238566FA3B17DBCE19A67F1F3A90DM8PR09MB7238namp_--


From nobody Wed Jan 13 09:55:12 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 236EF3A1246 for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 09:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FqNBxkxqv1i6 for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 09:55:08 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F3EA3A0BC2 for <spasm@ietf.org>; Wed, 13 Jan 2021 09:55:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 0F5F7389B3 for <spasm@ietf.org>; Wed, 13 Jan 2021 12:56:39 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id caPlYOlegYb2 for <spasm@ietf.org>; Wed, 13 Jan 2021 12:56:35 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 74190389A6 for <spasm@ietf.org>; Wed, 13 Jan 2021 12:56:35 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6C199AFD for <spasm@ietf.org>; Wed, 13 Jan 2021 12:55:02 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 13 Jan 2021 12:55:02 -0500
Message-ID: <6452.1610560502@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/NPoRxsaEkDBdE_vxdjjBqQFVJfs>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 17:55:11 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Panos Kampanakis \(pkampana\) <pkampana=3D40cisco.com@dmarc.ietf.org> wrote:
    > I have been on both sides of the argument, Classical+PQ signatures or
    > parallel (classical, PQ). Recently I have been thinking that we proba=
bly
    > can't avoid keeping classical PKI for backwards compatibility which p=
robably
    > makes the Classical+PQ sigs less appealing.

First, I think that we need better terms to explain the two options.
Russ has used "One Certificate" and "Two Certificate".

I think that in the "One Certificate" case, that the PQC and traditional
(He said "traditional", and Panos said "classical", btw) CA signers would s=
ign
both BQC and traditional keys.  Right?


    > Especially for live protocols
    > like TLS, this argument is even more relevant especially since the bi=
g cert
    > would be penalizing the classical peer with unnecessary PQ sig data.

It seems that for live protocols we can negotiate, and the server can send
only what is needed, so there are really no byte-size issues.

    > But I have heard some arguments for classical+PQ for non-TLS usecases=
. An
    > example could be SW Signing. I would argue that PKCS#7/CMS can include
    > multiple sigs (in SignerInfo) in the SignedData as clarified in RFC48=
53, so
    > even for SW Signing we may not need Composite or Hybrid Classical+PQ
    > Signatures.

That seems to be the parallel case, isn't it?

I have a different concern to ask as well:
  Are hash-based signatures in the classical or PQC category?

    > I gave this presentation at the NIST NCCoE Virtual Workshop on
    > Considerations in Migrating to Post-Quantum Cryptographic Algorithms:
    > https://www.nccoe.nist.gov/sites/default/files/10-Housley-NCCoE-Works=
hop-Tra
    > nsition-to-PQC-Certificates.pdf

    > This short presentation still captures my view.  Are there people wit=
h a
    > different view that would like time on the agenda at the LAMPS Interi=
m on 28
    > Jan?  I would like to make sure that all point of view are heard.

Russ' preference is for "Two Certificate" case.
I think that it is equivalent to having RSA and ECDSA ecosystems alive, whi=
ch
I think we have managed reasonably well.
So I don't think that I have a diverging view.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl//M/YACgkQgItw+93Q
3WVFqwf8DDEkQ6i96R6XY3j1OeqwoTgfgdQtY3/JV7TyYhLkE8heR/aP/k2weIjX
x6NV5W/llkM0wLQNQEfEUJ1Ie+IyL0Y1MoF1Si2B7mk1ozFdQo8/i9rBjQ8OIFkP
QHI1DtGjzeXoCceBTy0g88HBcwi5TOH5edRCEhp81nx0hzUU0ypKvvByHPHSk71j
1CjNwJjT4Up5caxXi/t5zZ26+fkDsJUv+pLgQHHEEUMI0cDpHOvzMnRi9nLKMajH
s1oWxTOi2Y4z5H6tD8JbhRaJfpfFvjUyD0jh+83dExQCH0FCrOlDYc3ucwU31k8h
uhml9CqNUdEltdu1fFAJOTLSKSz37A==
=5rLG
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan 13 09:59:06 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DEBD3A0EC4 for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 09:59:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOPyVNnUBESc for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 09:59:02 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBA6F3A0E4B for <spasm@ietf.org>; Wed, 13 Jan 2021 09:59:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8D6D0389BA for <spasm@ietf.org>; Wed, 13 Jan 2021 13:00:34 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HxQjlKXZUqIl for <spasm@ietf.org>; Wed, 13 Jan 2021 13:00:33 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7FADC389B3 for <spasm@ietf.org>; Wed, 13 Jan 2021 13:00:33 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7533AAFD for <spasm@ietf.org>; Wed, 13 Jan 2021 12:59:00 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: LAMPS <spasm@ietf.org>
In-Reply-To: <6452.1610560502@localhost>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com> <6452.1610560502@localhost>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 13 Jan 2021 12:59:00 -0500
Message-ID: <7435.1610560740@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/PttvRxct1rthhTSABB8Hjbqaae8>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 17:59:05 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > First, I think that we need better terms to explain the two options.
    > Russ has used "One Certificate" and "Two Certificate".

    > I think that in the "One Certificate" case, that the PQC and traditio=
nal
    > (He said "traditional", and Panos said "classical", btw) CA signers w=
ould sign
    > both BQC and traditional keys.  Right?

...
    >> This short presentation still captures my view.  Are there people wi=
th a
    >> different view that would like time on the agenda at the LAMPS Inter=
im on 28
    >> Jan?  I would like to make sure that all point of view are heard.

It occurs to me that what I'd like is to have the two options clearly
explained in a document, and for the two methods to be given clear names,
and then for the IETF to express a preference for what direction we will go
for each relevant protocol (TLS, IKE, PGP, CMS, COSE, ...).
In this case, the document really would be a Request for *Comments*

(maybe this belongs in SAAG)

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl//NOQACgkQgItw+93Q
3WXZfwf/eS4wZX+yx7CwnK6Iv++tWZzyiullfbmt3vurxZ3vJoH0b4KWEOTafWYN
aJ9r6Qag9dEJefbkdj+kIATOpz1BF+0/5b57KEdP/naM/lJZdE54y8qdG3zgOgLa
4a4C2iJ3/7dmqMD7mwXreo1JeYFne8psHKMUgixE+mC4IViDHluPGhmyvVhYxZec
NrbgPs6SJiE5dZk/oYxLZQeMOIGUFWLPY5uNukNsvSVx4HV/04IRJAdLpwiOYCun
dVS316XBB8M0mDRUWrzwt/25tbirblqXep2k3TEzJDXKJbGneeYDRcOyNd6twqpr
8lyCZ+zWKWkuzxZ73z2ZEYZMXg/jxg==
=+Q2d
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan 13 11:04:34 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 969323A129A for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 11:04:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ba2O_RzIR7Vm for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 11:04:29 -0800 (PST)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2113.outbound.protection.outlook.com [40.107.243.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B58043A1298 for <spasm@ietf.org>; Wed, 13 Jan 2021 11:04:29 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MpAwDW2Wk6CPSHPbuuUtzslIlENgZnnmrcYzDp7KFfOIxL11y+wqdEk4YVXeI+SUXKWNqCjsmzuvXaWruz7iuTj7xrCUBpOE0xVHer9Fd6C/sY/OgkTEksfA+Jlb5Ye2cU6Qe1t+p6JG0BLYWR1aWACkUMOBu67TC9LocBDQ1A0+TKrQS5C79plIkPTdy1k9oP1qdGS8tAkHhQF2e3Pna/4PMc781ip1y7sn2BnRX7CMs4yBmY/uRTkEmu//VJlzPcnVFVSeup39EfQCreM5XYDXKBLBxhRq74Z+AuieqVeAfR18pHajHC+gMlzMXL0lXdYkSUMo1bG2yh33O9HCGg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=y2ty0hVhHmVn0qCBZ7/iprEzUJ25zDoJzja3BYHSOuY=; b=ZoFG5lyLXZMkmUqw6ZCl77oLjNWupAFnaXKOPYPvPon/9tMwG3Y1LhLd1kMlx2KD9AaIMOy5RxW+6lm/CGj5irb8k9psRpcJ+5rCqp+8kgGeuQhIX0W9owPO04GtWUB9O2mU7xJLML3wqG9QSHzhaHytP3hzNRiqGwngUXqt0mcQ16gu+Qx/XkMKwhsh5xuXnJ77Ny50Hts+Bh9h12pM0izGw8Nom2NLUMwuBgcL3Rv5lgx7dfq9KnSLcEXlf4SOW1JLboD7fmQpR3/ceLADbcFLLnFPFcmUAvDvoRK5aGMhDaaaUx9mJYVWspsf02InQAk0UMECjmzp43Se8GzuEw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=y2ty0hVhHmVn0qCBZ7/iprEzUJ25zDoJzja3BYHSOuY=; b=PAVzp/e4oA020EPRVYyE63fjHZ1NM+vqsNTRzp+j+uYcgF1XMZ2s2fAKnqaPLEuh0OXd5li7p3UZS/6EVN9CgBxt7eOYHO0rdTs9b674E2wJuEhnGy7qgSRuAPkB7gKzTCuJvMFCLpdrbgtgH3phmQXntvsPF0a57kVNI2i9I7Vw07Gl9IOsbOItaUu3CypyLyGUW0/AYMuWfS76DazUD+BgO00DYzRqfDAGbFMpEqxw/fIgkw+l/AXm8nXaPAK97fbvBWVlQ9XABEcqd1cYUWGbeYA/nIYjGhAtWhHkHl55kUbQT04quwG53G/A7Zkj9e9eQxUQaPSuRJ4OsY1hQg==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB4394.namprd11.prod.outlook.com (2603:10b6:5:202::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10; Wed, 13 Jan 2021 19:04:28 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.012; Wed, 13 Jan 2021 19:04:28 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, LAMPS <spasm@ietf.org>
Thread-Topic: [EXTERNAL]Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
Thread-Index: AQHW6VxU2VU/0CQXxkeOjfCPsxBhR6ol17YAgAAPeDA=
Date: Wed, 13 Jan 2021 19:04:28 +0000
Message-ID: <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com> <6452.1610560502@localhost>
In-Reply-To: <6452.1610560502@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: sandelman.ca; dkim=none (message not signed) header.d=none;sandelman.ca; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [72.139.200.247]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4ae5d1f1-c9b4-4239-c65d-08d8b7f60d12
x-ms-traffictypediagnostic: DM6PR11MB4394:
x-microsoft-antispam-prvs: <DM6PR11MB439415569635B05CB89FEEC89FA90@DM6PR11MB4394.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: DHm6ENAiTm0pTk83JoH++EX9zrVtH2p7+vkTWmGW4siQaPxM8qVTwUvlFlNko9F3I+1K/KVmf4QehYa8cuo6IlHCiv4Fmh55adhGOrYTXmMv26BprVIjYqwvdcKqfj5dPQYhvz2TLk7PlNkj+yh+wKrXWTibKSS3oWAcbCxuRJA/cAZK6e7jRLfKBxGzxe4unfthOkPCJ4n93y8z+jak9pdVLPqqEs5klOKumr4+LAuXMtjQrLIDh+PlZKPqfQ7mpNaw7e/1VsI1VWc4ffYltq2xwHvHxMjO+fk8IAy09+A14kL6v08wGnnJwh9g8+bMVsiTiTVLKeHWvfUDQ4qFmCCo6pQqWlCsXGD/X6jcFvcml7A3hLgAb3fMjCI7InqnDsEhOaLymIgwYowudull3YI+9C+2ZDFITgDO/BAsiDn+bNmEC5K6otqvbnWxDjSP/S0DXTW6fsutT3aKcca6BcDCpgslSq2TozHD2C8DzuXe3cKAezPJdbg2XrhLH8vKl/dVIYnDa7QYYpzc+s7ehw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(376002)(366004)(39860400002)(136003)(346002)(8936002)(6506007)(53546011)(76116006)(26005)(83080400002)(316002)(2906002)(186003)(52536014)(8676002)(33656002)(66476007)(66946007)(64756008)(86362001)(66556008)(66446008)(66574015)(7696005)(966005)(9686003)(55016002)(478600001)(5660300002)(83380400001)(110136005)(71200400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?blV0NCtsZXN2d0tyanBpVHQ0OGNFY0J5eG1EaG1UVHBiTGlUSXZpQW4ySVU1?= =?utf-8?B?aFlaTkFKaTFzVTZCL1ZPaEJKV2lZMSthNW5sODQ1L3k1VkZpejI1UlpTNUpW?= =?utf-8?B?cklQTUN4OEQrdWRFLzJQRk5SbVYxYjR4akE3WUdrbWtVT2ZtcXNLTVkvd3Zp?= =?utf-8?B?WFFGRXgrZmt0cXhPMy9vWjh3UmJoV25oM0tqL0JZQ012RTA2Y3lzWlBQNDd6?= =?utf-8?B?N1pPK1FBMmpTL2x3bG94V0tJaUpoeEhRdDdtbHZlWFhYYXlvalRvQmhZK0E4?= =?utf-8?B?OGdoWjNXZ0VrVE9CdE9kRmx5Yk5KVStiVk12VjRSbVB6cVZtMFlRWGYxV1JD?= =?utf-8?B?M3Fscll1MWorUEo5b1FML2N3am5rYXhEQlgwTUtqakxaZVp0N0txaXNKUndw?= =?utf-8?B?QUMwTkNNRUhRNkxldWFtNmFsZGtvUGh5ME1WbHFXLzlTczJSaFI5MzU2Zjk2?= =?utf-8?B?bDdTek5PNHJ0VzdnTHVsbjZKVVRueDBXMkRuZG9pY2tIUlB2ZUNCYjROSGpx?= =?utf-8?B?SVJBSUVhbHlkNDQzRzVGdXRqbUo1UlltOFNJUkVvTlpEOVZEYUxiK29LaWpt?= =?utf-8?B?RTlTNXNkSzlBUTdaR1ZSR0tNSDFaTjRrckFBdGo4U3dzZEhhUldxWVJHMGcy?= =?utf-8?B?RGd4NVcybTkxVURud3RtT0NvU3l3YkR4M1pKdjBsTUZJN2NjYWc2QytRVnJL?= =?utf-8?B?amsvNUxycXp5VGJuQWRsUGthRDV1RGFXUHg2YkY4OVYrTlVlMVpLVmVZVUZC?= =?utf-8?B?WnZUQ0ppYjBITVAwSk5wVk8xekMxd3BsOEx0RDV1SVVEUCtBVFplRGgrbGho?= =?utf-8?B?dTlVKzRjNlJNVHBmRFlqdnRZYWVrT3l2OUNLRU5xUVlkQWtDYWx4QkJFSDZJ?= =?utf-8?B?Q1pkQytEQXNEUGVRaUR1OG5adzAwanV6UHR1YWVDU1FXakR6Vzg3SFBRVWp6?= =?utf-8?B?K3o3aHdZUktlZWc2TloraUc5K28xL2FzQW9FTVYwdlliRjBuUEt0YlVqdFBx?= =?utf-8?B?bWpBMm5kdkpOMXFSK1luVzh5N0U5WEtMeFJvZTZTOFF3bHJCL05udTJVUGk0?= =?utf-8?B?RS9CVzRSTmFMNlBkNGVuOFhmRDBwbWVXZVc1eFg4ZHA4bHhTRGhNN3kzT2x5?= =?utf-8?B?bTVkbzRNRW1INGVWQk12SWdNeUhjR3lJdHIxc2o2MUJwSE9PNm1zcVFCemhP?= =?utf-8?B?NlB5NysxaHQvKytZMXN3eGpFM3htVUlheXNOTDFUelF3NWtqMFgvL21DbXFx?= =?utf-8?B?NEFlRGlJY2NpVmpFZUdqVCtxNXdNL2JTTzRUSjkvSmp0MWpsMkNkQzhlb1pF?= =?utf-8?Q?ru8vL9iS3vBNE=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4ae5d1f1-c9b4-4239-c65d-08d8b7f60d12
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2021 19:04:28.1537 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: FpOIOEs/5jk17PLwUL3Coz7M9u0IzVgUeiKcN2rwd4u4reliooZjOJVm6s2T+fL277SpXtDZ/9nXD7+BlkckvSHvEjGnUJCJUuF8sicP1d0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4394
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/MN_2YZA6ba20UdbWI2vmrJlwmYs>
Subject: Re: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 19:04:33 -0000

QXQgdGhlIHJpc2sgb2Ygb3Zlci1jb21wbGljYXRpbmcgZXZlcnl0aGluZywgd2Ugc2VlIHRoZSBP
bmUtQ2VydCB2cyBUd28tQ2VydCBkaXNjdXNzaW9uIGFzIGluIHNvbWUgc2Vuc2VzIG9ydGhvZ29u
YWwgdG8gb3VyIGNvbXBvc2l0ZSBrZXlzIGFuZCBzaWduYXR1cmVzIGRyYWZ0IChkcmFmdC1vdW5z
d29ydGgtcHEtY29tcG9zaXRlLXNpZ3MpLg0KDQpJIHRoaW5rIHRoYXQgc2hvZWhvcm5pbmcgdGhp
cyBpbnRvIGEgIm9uZS1jZXJ0IHZzIHR3by1jZXJ0IiBkaXNjdXNzaW9uIGlzIG1pc3Npbmcgc29t
ZSBvZiB0aGUgcG90ZW50aWFsIHZhbHVlIG9mIHRoZSBDb21wb3NpdGUgcHJvcG9zYWwuDQoNCklu
IHdyaXRpbmcgdGhlIGNvbXBvc2l0ZSBkcmFmdCwgd2Ugd2VyZSBjYXJlZnVsIHRvIG5vdCBtYWtl
IGl0IGEgY2VydGlmaWNhdGVzIGRyYWZ0LCBhbmQgaW5zdGVhZCBzdGljayBzdHJpY3RseSB0byBw
dWJsaWMga2V5LCBwcml2YXRlIGtleSwgYW5kIHNpZ25hdHVyZSBPSURzIGFuZCBBU04uMSBlbmNv
ZGluZ3MuIEF0IHByZXNlbnQsIHdlIGFyZSBqdXN0IGxvb2tpbmcgYXQgY29tcG9zaXRlIGtleSBh
bmQgc2lnbmF0dXJlIGZvcm1hdHMgc28gdGhhdCB0aGVyZSBpcyBhbiBvYnZpb3VzIGFuZCBzdGFu
ZGFyZGl6ZWQgd2F5IHRvIG1lZXQgdGhlIE5JU1QgY2FsbCBmb3IgcHV0dGluZyBkdWFsIHNpZ25h
dHVyZXMgb24gPHRoaW5nPjsgd2hhdGV2ZXIgPHRoaW5nPiBpcy4NCg0KRm9yIGV4YW1wbGUsIHNv
bWVvbmUgd2F5IHdhbnQgdG8gY29tYmluZSBib3RoIGFwcHJvYWNoZXMgYW5kIGhhdmUgYSBUd28t
Q2VydCBlY29zeXN0ZW0gd2hlcmUgb25lIG9mIHRoZSBjZXJ0cyBpcyBDb21wb3NpdGU6DQoNCkNl
cnQxOiB7UlNBfQ0KQ2VydDI6IHtSU0EsIFBRfQ0KDQoNCkFub3RoZXIgZXhhbXBsZSBvZiB0aGVt
IGJlaW5nIG9ydGhvZ29uYWwgaXMgYSBjYXNlIHdoZXJlIHlvdSBoYXZlIHNlcGFyYXRlIGNlcnRp
ZmljYXRlcyB7UlNBfSwge1BRfSwgYnV0IGZvciBwcm90b2NvbCBzaW1wbGljaXR5IHlvdSB3YW50
IHRvIHVzZSB0aGUgY29tcG9zaXRlIHNpZ25hdHVyZSBzdHJ1Y3R1cmUge1JTQSxQUX0gb24gdGhl
IHdpcmUuDQoNCk91ciBkcmFmdCAoZHJhZnQtb3Vuc3dvcnRoLXBxLWNvbXBvc2l0ZS1zaWdzKSBp
cyByZWFsbHkgdHJ5aW5nIHRvIGJlIG9ydGhvZ29uYWwgZnJvbSB0aGUgT25lLUNlcnQgdnMgVHdv
LUNlcnQgcXVlc3Rpb24uDQoNCi0tLQ0KTWlrZSBPdW5zd29ydGgNCg0KLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCkZyb206IFNwYXNtIDxzcGFzbS1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhh
bGYgT2YgTWljaGFlbCBSaWNoYXJkc29uDQpTZW50OiBKYW51YXJ5IDEzLCAyMDIxIDExOjU1IEFN
DQpUbzogTEFNUFMgPHNwYXNtQGlldGYub3JnPg0KU3ViamVjdDogW0VYVEVSTkFMXVJlOiBbbGFt
cHNdIENhbGwgZm9yIFByZXNlbnRhdGlvbnMgYXQgdGhlIExBTVBTIEludGVyaW0gTWVldGluZyBv
biAyOCBKYW4gMjAyMQ0KDQoNClBhbm9zIEthbXBhbmFraXMgXChwa2FtcGFuYVwpIDxwa2FtcGFu
YT00MGNpc2NvLmNvbUBkbWFyYy5pZXRmLm9yZz4gd3JvdGU6DQogICAgPiBJIGhhdmUgYmVlbiBv
biBib3RoIHNpZGVzIG9mIHRoZSBhcmd1bWVudCwgQ2xhc3NpY2FsK1BRIHNpZ25hdHVyZXMgb3IN
CiAgICA+IHBhcmFsbGVsIChjbGFzc2ljYWwsIFBRKS4gUmVjZW50bHkgSSBoYXZlIGJlZW4gdGhp
bmtpbmcgdGhhdCB3ZSBwcm9iYWJseQ0KICAgID4gY2FuJ3QgYXZvaWQga2VlcGluZyBjbGFzc2lj
YWwgUEtJIGZvciBiYWNrd2FyZHMgY29tcGF0aWJpbGl0eSB3aGljaCBwcm9iYWJseQ0KICAgID4g
bWFrZXMgdGhlIENsYXNzaWNhbCtQUSBzaWdzIGxlc3MgYXBwZWFsaW5nLg0KDQpGaXJzdCwgSSB0
aGluayB0aGF0IHdlIG5lZWQgYmV0dGVyIHRlcm1zIHRvIGV4cGxhaW4gdGhlIHR3byBvcHRpb25z
Lg0KUnVzcyBoYXMgdXNlZCAiT25lIENlcnRpZmljYXRlIiBhbmQgIlR3byBDZXJ0aWZpY2F0ZSIu
DQoNCkkgdGhpbmsgdGhhdCBpbiB0aGUgIk9uZSBDZXJ0aWZpY2F0ZSIgY2FzZSwgdGhhdCB0aGUg
UFFDIGFuZCB0cmFkaXRpb25hbCAoSGUgc2FpZCAidHJhZGl0aW9uYWwiLCBhbmQgUGFub3Mgc2Fp
ZCAiY2xhc3NpY2FsIiwgYnR3KSBDQSBzaWduZXJzIHdvdWxkIHNpZ24gYm90aCBCUUMgYW5kIHRy
YWRpdGlvbmFsIGtleXMuICBSaWdodD8NCg0KDQogICAgPiBFc3BlY2lhbGx5IGZvciBsaXZlIHBy
b3RvY29scw0KICAgID4gbGlrZSBUTFMsIHRoaXMgYXJndW1lbnQgaXMgZXZlbiBtb3JlIHJlbGV2
YW50IGVzcGVjaWFsbHkgc2luY2UgdGhlIGJpZyBjZXJ0DQogICAgPiB3b3VsZCBiZSBwZW5hbGl6
aW5nIHRoZSBjbGFzc2ljYWwgcGVlciB3aXRoIHVubmVjZXNzYXJ5IFBRIHNpZyBkYXRhLg0KDQpJ
dCBzZWVtcyB0aGF0IGZvciBsaXZlIHByb3RvY29scyB3ZSBjYW4gbmVnb3RpYXRlLCBhbmQgdGhl
IHNlcnZlciBjYW4gc2VuZCBvbmx5IHdoYXQgaXMgbmVlZGVkLCBzbyB0aGVyZSBhcmUgcmVhbGx5
IG5vIGJ5dGUtc2l6ZSBpc3N1ZXMuDQoNCiAgICA+IEJ1dCBJIGhhdmUgaGVhcmQgc29tZSBhcmd1
bWVudHMgZm9yIGNsYXNzaWNhbCtQUSBmb3Igbm9uLVRMUyB1c2VjYXNlcy4gQW4NCiAgICA+IGV4
YW1wbGUgY291bGQgYmUgU1cgU2lnbmluZy4gSSB3b3VsZCBhcmd1ZSB0aGF0IFBLQ1MjNy9DTVMg
Y2FuIGluY2x1ZGUNCiAgICA+IG11bHRpcGxlIHNpZ3MgKGluIFNpZ25lckluZm8pIGluIHRoZSBT
aWduZWREYXRhIGFzIGNsYXJpZmllZCBpbiBSRkM0ODUzLCBzbw0KICAgID4gZXZlbiBmb3IgU1cg
U2lnbmluZyB3ZSBtYXkgbm90IG5lZWQgQ29tcG9zaXRlIG9yIEh5YnJpZCBDbGFzc2ljYWwrUFEN
CiAgICA+IFNpZ25hdHVyZXMuDQoNClRoYXQgc2VlbXMgdG8gYmUgdGhlIHBhcmFsbGVsIGNhc2Us
IGlzbid0IGl0Pw0KDQpJIGhhdmUgYSBkaWZmZXJlbnQgY29uY2VybiB0byBhc2sgYXMgd2VsbDoN
CiAgQXJlIGhhc2gtYmFzZWQgc2lnbmF0dXJlcyBpbiB0aGUgY2xhc3NpY2FsIG9yIFBRQyBjYXRl
Z29yeT8NCg0KICAgID4gSSBnYXZlIHRoaXMgcHJlc2VudGF0aW9uIGF0IHRoZSBOSVNUIE5DQ29F
IFZpcnR1YWwgV29ya3Nob3Agb24NCiAgICA+IENvbnNpZGVyYXRpb25zIGluIE1pZ3JhdGluZyB0
byBQb3N0LVF1YW50dW0gQ3J5cHRvZ3JhcGhpYyBBbGdvcml0aG1zOg0KICAgID4gaHR0cHM6Ly93
d3cubmNjb2UubmlzdC5nb3Yvc2l0ZXMvZGVmYXVsdC9maWxlcy8xMC1Ib3VzbGV5LU5DQ29FLVdv
cmtzaG9wLVRyYQ0KICAgID4gbnNpdGlvbi10by1QUUMtQ2VydGlmaWNhdGVzLnBkZg0KDQogICAg
PiBUaGlzIHNob3J0IHByZXNlbnRhdGlvbiBzdGlsbCBjYXB0dXJlcyBteSB2aWV3LiAgQXJlIHRo
ZXJlIHBlb3BsZSB3aXRoIGENCiAgICA+IGRpZmZlcmVudCB2aWV3IHRoYXQgd291bGQgbGlrZSB0
aW1lIG9uIHRoZSBhZ2VuZGEgYXQgdGhlIExBTVBTIEludGVyaW0gb24gMjgNCiAgICA+IEphbj8g
IEkgd291bGQgbGlrZSB0byBtYWtlIHN1cmUgdGhhdCBhbGwgcG9pbnQgb2YgdmlldyBhcmUgaGVh
cmQuDQoNClJ1c3MnIHByZWZlcmVuY2UgaXMgZm9yICJUd28gQ2VydGlmaWNhdGUiIGNhc2UuDQpJ
IHRoaW5rIHRoYXQgaXQgaXMgZXF1aXZhbGVudCB0byBoYXZpbmcgUlNBIGFuZCBFQ0RTQSBlY29z
eXN0ZW1zIGFsaXZlLCB3aGljaCBJIHRoaW5rIHdlIGhhdmUgbWFuYWdlZCByZWFzb25hYmx5IHdl
bGwuDQpTbyBJIGRvbid0IHRoaW5rIHRoYXQgSSBoYXZlIGEgZGl2ZXJnaW5nIHZpZXcuDQoNCi0t
DQpNaWNoYWVsIFJpY2hhcmRzb24gPG1jcitJRVRGQHNhbmRlbG1hbi5jYT4gICAuIG8gTyAoIElQ
djYgScO4VCBjb25zdWx0aW5nICkNCiAgICAgICAgICAgU2FuZGVsbWFuIFNvZnR3YXJlIFdvcmtz
IEluYywgT3R0YXdhIGFuZCBXb3JsZHdpZGUNCg==


From nobody Wed Jan 13 12:02:15 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9B33A12EA for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 12:02:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T1B_pUFnUQ46 for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 12:02:12 -0800 (PST)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2096.outbound.protection.outlook.com [40.107.92.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71E1F3A1396 for <spasm@ietf.org>; Wed, 13 Jan 2021 12:01:23 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YkMXKGnBBe453YQ7B0xvTCBQelLtr41iM02/+6E/IPliRYl8FAAbl4UJ/+DlsQF7q+zk0Addxa49boZKbMKSntnvTztm7LcLap7+C9XJ/qJUmPaQPOcHsC6fTLwAgRlKz/obM0yoYyY1DvQiMCSfhbYBvkCsHr0C63IOTdXq+UAYr5OSlQrb9OPW0yIDsIKoCyiXzKM45OSLbysrGcfc2qh3W+2Kttlpp8XV6OytFFW3vlMZSfXwk7y4sOE6koWvjmztoiBnroRe4GBUaJsp2uXjc8MP+mDaQeCdBxeCOxjubuiyG2TCCWVCZVIYDS89GgE5CNDuI8DqQxQ92A2OGg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Qtyb5BbaxgQ9+LBMu8L1FY6Rjbfy7Qdcib1cHRVe9J0=; b=oTxUSGX3FVELsRkr8C+zIs6XysHHYd0Lk7YH8x9jIvamfXI8bpec1LIBggj1o/ewwDVbYdkXrLONzHAtG+yHgNpK+RdZ3GGaez2+QJOaD7zvwC7Eizgfn2bZUxCq3i9yArYhqoKMHHroZl7pcXOmo4074jkgBj84+Iu/0P3jX/VigqdCUyZ6MjwZECLivo8xvqagDyI1vYPVb8h1fvaRe/C6xZyW+T9wzObNzhZhvTTuVgCNJVqTNLxyW815fDlYYUp7iDj4t0FMjEUnjihnuk+ahKSVQH+9ssfspUqiWpTv0nhW3SmBl5gRiKdvniF3LUxmdUKVk6yxBHIF5yrZ0w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Qtyb5BbaxgQ9+LBMu8L1FY6Rjbfy7Qdcib1cHRVe9J0=; b=K2JpW5+T4ZKWTCTffd3FGyfoKQRFwhUsMc+hwde35nSsdy7EF0pn0JZVCTrjrRBnkCfas7B45TOA39Y4KPlPUdpxT1kyQFedOg1Eih1olDMssdQ9ZidIapd5BQzyqdq2yTGRUWAi6Wa3Mm2OpKF1j7hdWIIyKHCGtGuc946URSgVHXhjc+8FmV9HuCG7CYDVxGBgH/yqJzTsP98GKeXTs+nsp7MA34K+6c/cU+xd9v4KeOotq3troOOriSe5MRkcAonjY1VKIgmMIhGW3BADOdx1CtlNzd4AO40hy8fZ2u08BKIPIAUZ20xgCN4gh01NFOb0aouzNdiED6Zu15ykDg==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB4409.namprd11.prod.outlook.com (2603:10b6:5:1df::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Wed, 13 Jan 2021 20:01:21 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.012; Wed, 13 Jan 2021 20:01:21 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>, LAMPS <spasm@ietf.org>
Thread-Topic: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
Thread-Index: AQHW6ebclr6lpPDytEOcWe8MTZ0juw==
Date: Wed, 13 Jan 2021 20:01:21 +0000
Message-ID: <DM6PR11MB4380B9B6B39A98DF192720B59FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com> <6452.1610560502@localhost> <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
In-Reply-To: <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none; dmarc.ietf.org; dmarc=none action=none header.from=entrust.com; 
x-originating-ip: [72.139.200.247]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 48ff28ad-ef9d-410f-2842-08d8b7fdff6b
x-ms-traffictypediagnostic: DM6PR11MB4409:
x-microsoft-antispam-prvs: <DM6PR11MB4409533325513C61B66159639FA90@DM6PR11MB4409.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: H12JbY1j7VMVBr01iVMKvvffFcNMnvjcpzulTdsD9AdkeA1Dys38bOT9YrwhMkHRw+V7RNcxhtVmqYhSiAqQsCF2yJIzhCdq61WGHA6LHAhDOOfySRtU5XBkpo2KdcqpNohVjYxsNKk8ele1scO8umDJzTi+wz0YBA16MojDpnXhsvH8R82jPfcGFKaGqcyhYNzC86nTgjHXsxKxgKqyzrh7q/QRlyCIyEeJRsqPAwdImF5dldftnT2Nm05TnZLIDxF3S6VDu6tp8Yhsug6HvdnUmC139wpi10UxPVFhS50IYj9hbQFy/0ZQVxYiTBnrXdEq8jD5b/svsOeiJs053qIPcKi5aa6Vd8y2lFZb6M+6Mnf8fKOJc5k3X7r4VcQA0Qii6HuS6xQx7e5WrW2b388D65Mal+JdXi0L3z6u54iUWzuD2av9nSuYyXg/iZab3UH3wNJMy5RaBeIKA5zLvfXdpun8fV1QgbjNZz5EZ5r6AG4JrLq72p9nw6ZTWSQYCw0vHs6L4HNyQovL/nZL0A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(376002)(39860400002)(346002)(366004)(136003)(26005)(316002)(186003)(6506007)(52536014)(55016002)(110136005)(2906002)(966005)(53546011)(83080400002)(86362001)(66476007)(66574015)(66446008)(478600001)(2940100002)(33656002)(5660300002)(66946007)(83380400001)(9686003)(7696005)(8676002)(66556008)(8936002)(71200400001)(64756008)(76116006); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?VlJtbXZ0cUdGSWZDUmdqRkhGbm10d3ZFdHFGbE1wTzI2d256ekRYYmw2TEUr?= =?utf-8?B?Sm5DbS9hekRMSVdETjd6UjBqaTZrMWE1TE1KRUJGWnZvSERES2tsV0VKWDJu?= =?utf-8?B?a3ZiK3Y4RWJLZnM1bUd3cUk1aEovdmpxMmY3b2pHWjhyd0w2TjYxb09ZQ0Fv?= =?utf-8?B?OW05U1dFU0dIU2J4dkhaaTRZbGtKSDY1eFFXbVQ2ckNzN2ZGYjh0Q3VYOXds?= =?utf-8?B?NjhjMVVtVENkWmE2dXIzV0tSZnVXb011dVhEMzhRWUJxYWdiZGdESUZieFBh?= =?utf-8?B?UThKYzNsRzJsMlgyVVBzM2xKMHdidE9YeHdmZzFRdTJ1eUNsSlUxUHc2MlBw?= =?utf-8?B?eFlEZEF3SWsrMjNXTlpzY3RRZDZOaTJXUDR0ODRVOURtck9PdWE3TmhHblAx?= =?utf-8?B?a3JJVGd1M1hTNEJZc2RldklWYkE5MUp6UnlDUWxHaFRYdStIOGdNdFhPZWJ2?= =?utf-8?B?RVJFYzNnL2Y2U3FZdElGR1FDd0RhTlFORXpqbmI4SWhoSDFaaWpyVkZWRFc5?= =?utf-8?B?cTIvUndLWVk5dVBJRFB1Q3Z4dm1Ybjh5bWhoWFd1dVcrdzR2ampBdW52dHIy?= =?utf-8?B?QmlCT0tReHozcXB3L2pIWTdUZlpBRXdLdFVPb25iZXJEVkljNVJNNVJIeUpv?= =?utf-8?B?SEFRZUR5MkQwaklQVXpmSzFaeStWd3BmdTNaMjVBQ256RW9zMkV2aGxwZmtj?= =?utf-8?B?RnVnSEpsMmVlcXhqbCtmQW5XdTlqYVZ6OHE0VTB5YUQySmlteCt5RUdReWpT?= =?utf-8?B?V0VQdHBBbWpBU1RvOUZERXBsMTF4Ym91UDVKQW1Cc1hFRW9hUkc4Q2cxZnFK?= =?utf-8?B?K0ZsRU9zS0IxdWQrZEh3LzRJM2tXNHBZeDZZM0hsOE4vbTh3cmVyclcrekFh?= =?utf-8?B?OTFGNHByVjJZNlZhK1R4WTNEU3lwRHBkYjZ0cUNKd2lGWUxxT29LekxRZmlO?= =?utf-8?B?TU1hNU9VK3pSOUVzOGo3RWJ6azUxYTBQaGFiaVFoTUhxN2RnTmZzTk9GTkVI?= =?utf-8?B?SDJsZlNvbk5EcHBRWW9maWJqNmdvNDJtZm10ajkzbVE0MFk3bCs2b09vcGNR?= =?utf-8?B?ZS9DRFpNb3lpRVJoRzVZTmJ0ckg3RElQN2ljbGdiSlpWWVZSWExYN0E2S3dl?= =?utf-8?B?dzRRTXlFL3JMNlZKRXhnc1RMWkkxTmw5SzBaR083QVkrSkRvcXNaTEw4T3lX?= =?utf-8?B?MjRobVFJZ1VDZGdlK1Q2ZGt3TjVGN0IxRDJjdkV1dnBOc0dqRmkweDVYOEk4?= =?utf-8?B?N2gzaU9EQTZ6dkcycVdTU1Z0dGZBdlhXaUZKUEVKaTd3dDVBSVJrNTQrblFH?= =?utf-8?Q?kPuSyvn6wk9kQ=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 48ff28ad-ef9d-410f-2842-08d8b7fdff6b
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2021 20:01:21.1327 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: j1jqtiJq+yZ4gQ3NQGJpyK+Mhr8HR22WsdmQfwExYu44gqBio3dG3ifl8enXN7mdLygTT/dZJlnsvztsywK55BaWXs5qWgBIaO55VUfY1Y8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4409
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/uRm7I6_j7szLdcuZCZaBeJYtKDo>
Subject: Re: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 20:02:14 -0000

QW5vdGhlciBub3RlOiBJIGFtIGF3YXJlIHRoYXQgTEFNUFMgaXMgYSBiaXQgb2YgYW4gb2RkIHBs
YWNlIGZvciBhIGRyYWZ0IHRoYXQgZG9lcyBub3QgYWN0dWFsbHkgdXBkYXRlIGFueSBQS0lYIHN0
YW5kYXJkcywgYnV0IHRoaXMgaGFzIGJvdW5jZWQgYSBmZXcgdGltZXMgYmV0d2VlbiBMQU1QUyBh
bmQgU2VjRGlzcGF0Y2ggKHNlZSB0aHJlYWQgIltTZWNkaXNwYXRjaF0gQ2FuIENvbXBvc2l0ZSBz
aWdzIG1vdmUgYmFjayB0byBMQU1QUz8iKS4gVGhlcmUgc2VlbXMgdG8gYmUgc3VwcG9ydCBmb3Ig
YWR2YW5jaW5nIHRoaXMgZHJhZnQsIGFuZCBMQU1QUyBpcyBhcyBnb29kIGEgaG9tZSBhcyBhbnku
DQoNClRoZXJlZm9yZSwgSSBzdWJtaXQgdGhhdCBMQU1QUyBzaG91bGQgbG9vayBhdCBzdGFuZGFy
ZGl6aW5nIG1lY2hhbmlzbXMgdG8gbWVldCB0aGUgTklTVCBjYWxsIG9mIGNhcnJ5aW5nIGR1YWwg
c2lnbmF0dXJlcyBpbiBQS0lYLWxpa2UgcHJvdG9jb2xzLiBJIHdvdWxkIHN1Ym1pdCBkcmFmdC1v
dW5zd29ydGgtcHEtY29tcG9zaXRlLXNpZ3MgYXMgb25lIHN1Y2ggbWVjaGFuaXNtLCBidXQgbGlr
ZWx5IG5vdCB0aGUgb25seSBvbmUuIEkgdGhpbmsgdGhpbmdzIHdpbGwgbmVlZCB0byBjYXJyeSB0
d28gc2lnbmF0dXJlcyBhbmQgTEFNUFMgaXMgaW4gdGhlIHJpZ2h0IHBsYWNlIHRvIHN0YW5kYXJk
aXplIGFuIGVuY29kaW5nLiBJIGJlbGlldmUgc3RhbmRhcmRpemluZyAiZHVhbCBzaWduYXR1cmVz
IiBpbiBnZW5lcmFsIGlzIGluZGVwZW5kZW50IGZyb20gd2hldGhlciBpdCdzIGFwcHJvcHJpYXRl
IHRvIHVzZSB0aGVtIG9uIFguNTA5IGNlcnRpZmljYXRlcy4NCg0KLS0tDQpNaWtlIE91bnN3b3J0
aA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogU3Bhc20gPHNwYXNtLWJvdW5j
ZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBNaWtlIE91bnN3b3J0aA0KU2VudDogSmFudWFyeSAx
MywgMjAyMSAxOjA0IFBNDQpUbzogTWljaGFlbCBSaWNoYXJkc29uIDxtY3IraWV0ZkBzYW5kZWxt
YW4uY2E+OyBMQU1QUyA8c3Bhc21AaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW2xhbXBzXSBbRVhU
RVJOQUxdUmU6IENhbGwgZm9yIFByZXNlbnRhdGlvbnMgYXQgdGhlIExBTVBTIEludGVyaW0gTWVl
dGluZyBvbiAyOCBKYW4gMjAyMQ0KDQpBdCB0aGUgcmlzayBvZiBvdmVyLWNvbXBsaWNhdGluZyBl
dmVyeXRoaW5nLCB3ZSBzZWUgdGhlIE9uZS1DZXJ0IHZzIFR3by1DZXJ0IGRpc2N1c3Npb24gYXMg
aW4gc29tZSBzZW5zZXMgb3J0aG9nb25hbCB0byBvdXIgY29tcG9zaXRlIGtleXMgYW5kIHNpZ25h
dHVyZXMgZHJhZnQgKGRyYWZ0LW91bnN3b3J0aC1wcS1jb21wb3NpdGUtc2lncykuDQoNCkkgdGhp
bmsgdGhhdCBzaG9laG9ybmluZyB0aGlzIGludG8gYSAib25lLWNlcnQgdnMgdHdvLWNlcnQiIGRp
c2N1c3Npb24gaXMgbWlzc2luZyBzb21lIG9mIHRoZSBwb3RlbnRpYWwgdmFsdWUgb2YgdGhlIENv
bXBvc2l0ZSBwcm9wb3NhbC4NCg0KSW4gd3JpdGluZyB0aGUgY29tcG9zaXRlIGRyYWZ0LCB3ZSB3
ZXJlIGNhcmVmdWwgdG8gbm90IG1ha2UgaXQgYSBjZXJ0aWZpY2F0ZXMgZHJhZnQsIGFuZCBpbnN0
ZWFkIHN0aWNrIHN0cmljdGx5IHRvIHB1YmxpYyBrZXksIHByaXZhdGUga2V5LCBhbmQgc2lnbmF0
dXJlIE9JRHMgYW5kIEFTTi4xIGVuY29kaW5ncy4gQXQgcHJlc2VudCwgd2UgYXJlIGp1c3QgbG9v
a2luZyBhdCBjb21wb3NpdGUga2V5IGFuZCBzaWduYXR1cmUgZm9ybWF0cyBzbyB0aGF0IHRoZXJl
IGlzIGFuIG9idmlvdXMgYW5kIHN0YW5kYXJkaXplZCB3YXkgdG8gbWVldCB0aGUgTklTVCBjYWxs
IGZvciBwdXR0aW5nIGR1YWwgc2lnbmF0dXJlcyBvbiA8dGhpbmc+OyB3aGF0ZXZlciA8dGhpbmc+
IGlzLg0KDQpGb3IgZXhhbXBsZSwgc29tZW9uZSB3YXkgd2FudCB0byBjb21iaW5lIGJvdGggYXBw
cm9hY2hlcyBhbmQgaGF2ZSBhIFR3by1DZXJ0IGVjb3N5c3RlbSB3aGVyZSBvbmUgb2YgdGhlIGNl
cnRzIGlzIENvbXBvc2l0ZToNCg0KQ2VydDE6IHtSU0F9DQpDZXJ0Mjoge1JTQSwgUFF9DQoNCg0K
QW5vdGhlciBleGFtcGxlIG9mIHRoZW0gYmVpbmcgb3J0aG9nb25hbCBpcyBhIGNhc2Ugd2hlcmUg
eW91IGhhdmUgc2VwYXJhdGUgY2VydGlmaWNhdGVzIHtSU0F9LCB7UFF9LCBidXQgZm9yIHByb3Rv
Y29sIHNpbXBsaWNpdHkgeW91IHdhbnQgdG8gdXNlIHRoZSBjb21wb3NpdGUgc2lnbmF0dXJlIHN0
cnVjdHVyZSB7UlNBLFBRfSBvbiB0aGUgd2lyZS4NCg0KT3VyIGRyYWZ0IChkcmFmdC1vdW5zd29y
dGgtcHEtY29tcG9zaXRlLXNpZ3MpIGlzIHJlYWxseSB0cnlpbmcgdG8gYmUgb3J0aG9nb25hbCBm
cm9tIHRoZSBPbmUtQ2VydCB2cyBUd28tQ2VydCBxdWVzdGlvbi4NCg0KLS0tDQpNaWtlIE91bnN3
b3J0aA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogU3Bhc20gPHNwYXNtLWJv
dW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBNaWNoYWVsIFJpY2hhcmRzb24NClNlbnQ6IEph
bnVhcnkgMTMsIDIwMjEgMTE6NTUgQU0NClRvOiBMQU1QUyA8c3Bhc21AaWV0Zi5vcmc+DQpTdWJq
ZWN0OiBbRVhURVJOQUxdUmU6IFtsYW1wc10gQ2FsbCBmb3IgUHJlc2VudGF0aW9ucyBhdCB0aGUg
TEFNUFMgSW50ZXJpbSBNZWV0aW5nIG9uIDI4IEphbiAyMDIxDQoNCg0KUGFub3MgS2FtcGFuYWtp
cyBcKHBrYW1wYW5hXCkgPHBrYW1wYW5hPTQwY2lzY28uY29tQGRtYXJjLmlldGYub3JnPiB3cm90
ZToNCiAgICA+IEkgaGF2ZSBiZWVuIG9uIGJvdGggc2lkZXMgb2YgdGhlIGFyZ3VtZW50LCBDbGFz
c2ljYWwrUFEgc2lnbmF0dXJlcyBvcg0KICAgID4gcGFyYWxsZWwgKGNsYXNzaWNhbCwgUFEpLiBS
ZWNlbnRseSBJIGhhdmUgYmVlbiB0aGlua2luZyB0aGF0IHdlIHByb2JhYmx5DQogICAgPiBjYW4n
dCBhdm9pZCBrZWVwaW5nIGNsYXNzaWNhbCBQS0kgZm9yIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5
IHdoaWNoIHByb2JhYmx5DQogICAgPiBtYWtlcyB0aGUgQ2xhc3NpY2FsK1BRIHNpZ3MgbGVzcyBh
cHBlYWxpbmcuDQoNCkZpcnN0LCBJIHRoaW5rIHRoYXQgd2UgbmVlZCBiZXR0ZXIgdGVybXMgdG8g
ZXhwbGFpbiB0aGUgdHdvIG9wdGlvbnMuDQpSdXNzIGhhcyB1c2VkICJPbmUgQ2VydGlmaWNhdGUi
IGFuZCAiVHdvIENlcnRpZmljYXRlIi4NCg0KSSB0aGluayB0aGF0IGluIHRoZSAiT25lIENlcnRp
ZmljYXRlIiBjYXNlLCB0aGF0IHRoZSBQUUMgYW5kIHRyYWRpdGlvbmFsIChIZSBzYWlkICJ0cmFk
aXRpb25hbCIsIGFuZCBQYW5vcyBzYWlkICJjbGFzc2ljYWwiLCBidHcpIENBIHNpZ25lcnMgd291
bGQgc2lnbiBib3RoIEJRQyBhbmQgdHJhZGl0aW9uYWwga2V5cy4gIFJpZ2h0Pw0KDQoNCiAgICA+
IEVzcGVjaWFsbHkgZm9yIGxpdmUgcHJvdG9jb2xzDQogICAgPiBsaWtlIFRMUywgdGhpcyBhcmd1
bWVudCBpcyBldmVuIG1vcmUgcmVsZXZhbnQgZXNwZWNpYWxseSBzaW5jZSB0aGUgYmlnIGNlcnQN
CiAgICA+IHdvdWxkIGJlIHBlbmFsaXppbmcgdGhlIGNsYXNzaWNhbCBwZWVyIHdpdGggdW5uZWNl
c3NhcnkgUFEgc2lnIGRhdGEuDQoNCkl0IHNlZW1zIHRoYXQgZm9yIGxpdmUgcHJvdG9jb2xzIHdl
IGNhbiBuZWdvdGlhdGUsIGFuZCB0aGUgc2VydmVyIGNhbiBzZW5kIG9ubHkgd2hhdCBpcyBuZWVk
ZWQsIHNvIHRoZXJlIGFyZSByZWFsbHkgbm8gYnl0ZS1zaXplIGlzc3Vlcy4NCg0KICAgID4gQnV0
IEkgaGF2ZSBoZWFyZCBzb21lIGFyZ3VtZW50cyBmb3IgY2xhc3NpY2FsK1BRIGZvciBub24tVExT
IHVzZWNhc2VzLiBBbg0KICAgID4gZXhhbXBsZSBjb3VsZCBiZSBTVyBTaWduaW5nLiBJIHdvdWxk
IGFyZ3VlIHRoYXQgUEtDUyM3L0NNUyBjYW4gaW5jbHVkZQ0KICAgID4gbXVsdGlwbGUgc2lncyAo
aW4gU2lnbmVySW5mbykgaW4gdGhlIFNpZ25lZERhdGEgYXMgY2xhcmlmaWVkIGluIFJGQzQ4NTMs
IHNvDQogICAgPiBldmVuIGZvciBTVyBTaWduaW5nIHdlIG1heSBub3QgbmVlZCBDb21wb3NpdGUg
b3IgSHlicmlkIENsYXNzaWNhbCtQUQ0KICAgID4gU2lnbmF0dXJlcy4NCg0KVGhhdCBzZWVtcyB0
byBiZSB0aGUgcGFyYWxsZWwgY2FzZSwgaXNuJ3QgaXQ/DQoNCkkgaGF2ZSBhIGRpZmZlcmVudCBj
b25jZXJuIHRvIGFzayBhcyB3ZWxsOg0KICBBcmUgaGFzaC1iYXNlZCBzaWduYXR1cmVzIGluIHRo
ZSBjbGFzc2ljYWwgb3IgUFFDIGNhdGVnb3J5Pw0KDQogICAgPiBJIGdhdmUgdGhpcyBwcmVzZW50
YXRpb24gYXQgdGhlIE5JU1QgTkNDb0UgVmlydHVhbCBXb3Jrc2hvcCBvbg0KICAgID4gQ29uc2lk
ZXJhdGlvbnMgaW4gTWlncmF0aW5nIHRvIFBvc3QtUXVhbnR1bSBDcnlwdG9ncmFwaGljIEFsZ29y
aXRobXM6DQogICAgPiBodHRwczovL3d3dy5uY2NvZS5uaXN0Lmdvdi9zaXRlcy9kZWZhdWx0L2Zp
bGVzLzEwLUhvdXNsZXktTkNDb0UtV29ya3Nob3AtVHJhDQogICAgPiBuc2l0aW9uLXRvLVBRQy1D
ZXJ0aWZpY2F0ZXMucGRmDQoNCiAgICA+IFRoaXMgc2hvcnQgcHJlc2VudGF0aW9uIHN0aWxsIGNh
cHR1cmVzIG15IHZpZXcuICBBcmUgdGhlcmUgcGVvcGxlIHdpdGggYQ0KICAgID4gZGlmZmVyZW50
IHZpZXcgdGhhdCB3b3VsZCBsaWtlIHRpbWUgb24gdGhlIGFnZW5kYSBhdCB0aGUgTEFNUFMgSW50
ZXJpbSBvbiAyOA0KICAgID4gSmFuPyAgSSB3b3VsZCBsaWtlIHRvIG1ha2Ugc3VyZSB0aGF0IGFs
bCBwb2ludCBvZiB2aWV3IGFyZSBoZWFyZC4NCg0KUnVzcycgcHJlZmVyZW5jZSBpcyBmb3IgIlR3
byBDZXJ0aWZpY2F0ZSIgY2FzZS4NCkkgdGhpbmsgdGhhdCBpdCBpcyBlcXVpdmFsZW50IHRvIGhh
dmluZyBSU0EgYW5kIEVDRFNBIGVjb3N5c3RlbXMgYWxpdmUsIHdoaWNoIEkgdGhpbmsgd2UgaGF2
ZSBtYW5hZ2VkIHJlYXNvbmFibHkgd2VsbC4NClNvIEkgZG9uJ3QgdGhpbmsgdGhhdCBJIGhhdmUg
YSBkaXZlcmdpbmcgdmlldy4NCg0KLS0NCk1pY2hhZWwgUmljaGFyZHNvbiA8bWNyK0lFVEZAc2Fu
ZGVsbWFuLmNhPiAgIC4gbyBPICggSVB2NiBJw7hUIGNvbnN1bHRpbmcgKQ0KICAgICAgICAgICBT
YW5kZWxtYW4gU29mdHdhcmUgV29ya3MgSW5jLCBPdHRhd2EgYW5kIFdvcmxkd2lkZSBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KU3Bhc20gbWFpbGluZyBs
aXN0DQpTcGFzbUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9zcGFzbQ0K


From nobody Wed Jan 13 14:29:46 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 296033A1468 for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 14:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t8EHpif_Kqgb for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 14:29:41 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C091B3A1463 for <spasm@ietf.org>; Wed, 13 Jan 2021 14:29:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 30538300BC4 for <spasm@ietf.org>; Wed, 13 Jan 2021 17:29:39 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id fng7WPbJH9wR for <spasm@ietf.org>; Wed, 13 Jan 2021 17:29:37 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 12B44300AFC; Wed, 13 Jan 2021 17:29:36 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
Date: Wed, 13 Jan 2021 17:29:38 -0500
Cc: LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9CE4E955-97C8-49C2-8FE2-375C576930B8@vigilsec.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com> <6452.1610560502@localhost> <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
To: "Mike Ounsworth (Mike.Ounsworth@entrustdatacard.com)" <Mike.Ounsworth@entrustdatacard.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/CcXYiDm3tFh4f5v74s9t9faH_eI>
Subject: Re: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 22:29:45 -0000

Mike:

I do not see them as orthogonal.  If one uses the composite signature =
structure {RSA,PQ} on the wire, and the public keys are in separate =
certificates, I cannot see how the validation works out.  Maybe I am =
missing something.  Can you put together some sides for the Interim =
meeting on the 28th to explain more fully?

Russ


> On Jan 13, 2021, at 2:04 PM, Mike Ounsworth =
<Mike.Ounsworth=3D40entrust.com@dmarc.ietf.org> wrote:
>=20
> At the risk of over-complicating everything, we see the One-Cert vs =
Two-Cert discussion as in some senses orthogonal to our composite keys =
and signatures draft (draft-ounsworth-pq-composite-sigs).
>=20
> I think that shoehorning this into a "one-cert vs two-cert" discussion =
is missing some of the potential value of the Composite proposal.
>=20
> In writing the composite draft, we were careful to not make it a =
certificates draft, and instead stick strictly to public key, private =
key, and signature OIDs and ASN.1 encodings. At present, we are just =
looking at composite key and signature formats so that there is an =
obvious and standardized way to meet the NIST call for putting dual =
signatures on <thing>; whatever <thing> is.
>=20
> For example, someone way want to combine both approaches and have a =
Two-Cert ecosystem where one of the certs is Composite:
>=20
> Cert1: {RSA}
> Cert2: {RSA, PQ}
>=20
>=20
> Another example of them being orthogonal is a case where you have =
separate certificates {RSA}, {PQ}, but for protocol simplicity you want =
to use the composite signature structure {RSA,PQ} on the wire.
>=20
> Our draft (draft-ounsworth-pq-composite-sigs) is really trying to be =
orthogonal from the One-Cert vs Two-Cert question.
>=20
> ---
> Mike Ounsworth
>=20
> -----Original Message-----
> From: Spasm <spasm-bounces@ietf.org> On Behalf Of Michael Richardson
> Sent: January 13, 2021 11:55 AM
> To: LAMPS <spasm@ietf.org>
> Subject: [EXTERNAL]Re: [lamps] Call for Presentations at the LAMPS =
Interim Meeting on 28 Jan 2021
>=20
>=20
> Panos Kampanakis \(pkampana\) <pkampana=3D40cisco.com@dmarc.ietf.org> =
wrote:
>> I have been on both sides of the argument, Classical+PQ signatures or
>> parallel (classical, PQ). Recently I have been thinking that we =
probably
>> can't avoid keeping classical PKI for backwards compatibility which =
probably
>> makes the Classical+PQ sigs less appealing.
>=20
> First, I think that we need better terms to explain the two options.
> Russ has used "One Certificate" and "Two Certificate".
>=20
> I think that in the "One Certificate" case, that the PQC and =
traditional (He said "traditional", and Panos said "classical", btw) CA =
signers would sign both BQC and traditional keys.  Right?
>=20
>=20
>> Especially for live protocols
>> like TLS, this argument is even more relevant especially since the =
big cert
>> would be penalizing the classical peer with unnecessary PQ sig data.
>=20
> It seems that for live protocols we can negotiate, and the server can =
send only what is needed, so there are really no byte-size issues.
>=20
>> But I have heard some arguments for classical+PQ for non-TLS =
usecases. An
>> example could be SW Signing. I would argue that PKCS#7/CMS can =
include
>> multiple sigs (in SignerInfo) in the SignedData as clarified in =
RFC4853, so
>> even for SW Signing we may not need Composite or Hybrid Classical+PQ
>> Signatures.
>=20
> That seems to be the parallel case, isn't it?
>=20
> I have a different concern to ask as well:
>  Are hash-based signatures in the classical or PQC category?
>=20
>> I gave this presentation at the NIST NCCoE Virtual Workshop on
>> Considerations in Migrating to Post-Quantum Cryptographic Algorithms:
>> =
https://www.nccoe.nist.gov/sites/default/files/10-Housley-NCCoE-Workshop-T=
ra
>> nsition-to-PQC-Certificates.pdf
>=20
>> This short presentation still captures my view.  Are there people =
with a
>> different view that would like time on the agenda at the LAMPS =
Interim on 28
>> Jan?  I would like to make sure that all point of view are heard.
>=20
> Russ' preference is for "Two Certificate" case.
> I think that it is equivalent to having RSA and ECDSA ecosystems =
alive, which I think we have managed reasonably well.
> So I don't think that I have a diverging view.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T =
consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Wed Jan 13 14:45:33 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA2C3A1486 for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 14:45:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bQGDf_tPFZ8O for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 14:45:29 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0E643A13B4 for <spasm@ietf.org>; Wed, 13 Jan 2021 14:45:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 669D6389C6; Wed, 13 Jan 2021 17:47:01 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9UX0TBtoeEUl; Wed, 13 Jan 2021 17:47:00 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 3E625389C5; Wed, 13 Jan 2021 17:47:00 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7180FB3E; Wed, 13 Jan 2021 17:45:26 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: LAMPS <spasm@ietf.org>, Mike Ounsworth <Mike.Ounsworth@entrust.com>
In-Reply-To: <DM6PR11MB4380B9B6B39A98DF192720B59FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com> <6452.1610560502@localhost> <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com> <DM6PR11MB4380B9B6B39A98DF192720B59FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 13 Jan 2021 17:45:26 -0500
Message-ID: <22798.1610577926@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/PA6ScjlyvVAynlwNW9FkLEBdoy8>
Subject: Re: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 22:45:32 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Mike Ounsworth <Mike.Ounsworth=3D40entrust.com@dmarc.ietf.org> wrote:
    > Therefore, I submit that LAMPS should look at standardizing mechanisms
    > to meet the NIST call of carrying dual signatures in PKIX-like
    > protocols. I would submit draft-ounsworth-pq-composite-sigs as one su=
ch
    > mechanism, but likely not the only one. I think things will need to
    > carry two signatures and LAMPS is in the right place to standardize an
    > encoding. I believe standardizing "dual signatures" in general is
    > independent from whether it's appropriate to use them on X.509
    > certificates.

I agree that the technical details of how to do this for CMS and PKIX
certificates belongs in LAMPS.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl//eAUACgkQgItw+93Q
3WX9/gf+Mvy6THxtUUjjmNVkZe877+VMInuQ2auMMjBsigl/vQ4zUjHB8d8/pAXx
uuYZG76jCK0ibxYP4wMVzX2uO+tIVJOXOmzTQQ8C03CmQ0yyixI4vwfo7K76eRvT
kUBMLRjRc60oO68ucDckK1Z8sSVOLe6gAnsjnLrNoudP/AGqH36kpYw8MlVkpUvB
bsKOvyLG4st+hbtIFWcsogelYtt4xwQri96PQnFWn2DI+g6ekmBOJKbBt9kokHWj
Mzc0l+0fPcvmfd5nlp12fu9hnDlCSUdPgVXRRj6XxofR+oIbvxd+nT+8vLQIxdte
ySTJFbE6E9yp+aT8uHaK1uSl7f7vkg==
=F9GH
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan 13 14:49:42 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D08953A1488 for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 14:49:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qR2HhpbCC3ib for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 14:49:38 -0800 (PST)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760110.outbound.protection.outlook.com [40.107.76.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B34CD3A1486 for <spasm@ietf.org>; Wed, 13 Jan 2021 14:49:38 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=j1OA7629bKeaUZem6PIaRmXq0bI9OzXqySq7V3QV/YJmcgWwkyi30iYohd4LsluOUAsl4VD2fg4unfaoQN3kgvrtjPv3F84+Byyi7j3XulGGBlU9HXqDzshwIK6q+szORJmGHGrlNb3gdjM5Ym9ns8WcLkFvOOuYMXDHFSIePK4npf1KVz8pGzLmYQP1KaGoo8nOELqW+HQrMgE5MNOVvfzDhfub5T70OYAV1c8qHELEX4OlL+dAsOFOx31mz4L4gS5pDExyk38zHwGH2zcksRILdm1gZWiuu8weJv2ysq4/iPe0/O7NLKk+AQxja1dsmWeL48RonP96KHsqsiHCPQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZNHQPmx+a2vWPi+VktBkq4nSDlgGLR0qlXv4vXNMUQ4=; b=LVTcqmYmuPYlEvdb3xyniSf29gw289889csvnI+JAMEXU2Zmc1LO94jL9Mj0n4VIjwk5FakyZ5spPC+6EQPyhxh/cj24HVd4NlIuJYVYbu6ztzvSyIltB3b4rfkuvl5GsVso2nwZtB3+8YCtrxU+Nd1BhO+E1zm2t2Ze+afDpKFiI3A+JX+W7x+jbc3juZMX6fMPcYEkGtsfSRaaODe3EqwQzD51tPkSQfMnQsiAReD7osnQ5Y5FcSrmsYRBMEsF/9Ez2CehuB/GtM5RL9+oXAO6kfJkykNIKlz9nlsZ1tVrG3AJLAUSpQ8+kSULVCC7DgW16poWmPVMvDIiEI8ufg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZNHQPmx+a2vWPi+VktBkq4nSDlgGLR0qlXv4vXNMUQ4=; b=CbEaCHzcVfY9gBP3kzZxjfVE9M1SkMLLOTKHo06fNGqR2V9UFp7STrMJas86z2meHly0H4LvB7c7+nWT/2LZlKWSDN0ijt2kEEucR5gU7q8ymbi7qR/eiMJKl223Nj7OxNzNdsXfXY0zeGmu3cWT3XISN2L63m1rQ0g/x3W4ejUVb8qMVeP7onSJhbyp7rDe/V4gz/9SQo9bjxTPJckVKVdgU8/wrKLmtMQ1/ua3+ozgvZrcwiPKa/upe8EJlKnf7KhES4j5c67eYoc37esk2BLn0Tey7gAM/rHsSeTXB8Ioi4TthiblbwB3rGIV4TJvo1EHC6HKI2lN48ghH5gndQ==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM5PR11MB1417.namprd11.prod.outlook.com (2603:10b6:3:a::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.12; Wed, 13 Jan 2021 22:49:37 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::15ab:1cac:c06:c1f8%7]) with mapi id 15.20.3742.012; Wed, 13 Jan 2021 22:49:37 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Russ Housley <housley@vigilsec.com>
CC: LAMPS <spasm@ietf.org>
Thread-Topic: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
Thread-Index: AQHW6fuhRgkZZS9UCkmrJePvPeP61aomJPfw
Date: Wed, 13 Jan 2021 22:49:37 +0000
Message-ID: <DM6PR11MB43800BF75B25756CBC241C539FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com> <6452.1610560502@localhost> <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com> <9CE4E955-97C8-49C2-8FE2-375C576930B8@vigilsec.com>
In-Reply-To: <9CE4E955-97C8-49C2-8FE2-375C576930B8@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [72.139.200.247]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f8918cd8-d1f0-40ba-2dde-08d8b815812f
x-ms-traffictypediagnostic: DM5PR11MB1417:
x-microsoft-antispam-prvs: <DM5PR11MB14172FCE17F6C0BF23D8CFEE9FA90@DM5PR11MB1417.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: /eebnnyUamE3GNgciYJFMaxh6pfGjA2K/NaT5gqiurmHyykrBXbMgk4JloM6qKXDbNXr+bJMjCoaTsN8nosE1NYgdS6Wwn5ELaF57dVxxP+VgU9VA0DdSdHu6ARavkSbl/t8z1C6kNqAZbFzPs+C9XALJnF3ZipSDZgnM/jZ93/nmWWtMMbqs1DiHfmn4Kf44YlyrdtjiCcF1CSsYjBjrRb9CRoHaHSp+PtHu8NrpLApqYcTYliYSHT3g6RH9AjpthIPm2ePqAmedS5C3Ty+R3B8mmUO2Zv/8TqtDa8sCxOzr31fD8SPOsCeT6ytsEBGvJl/1jODlD227uw9u/o4my9SkF55mMn2jo32vc6cQHB+pkAYMUHLL1s/hwXa7srTXYLlezzxxlZ2iFh4LSP5mWH1rD+k4JhLGxiuggC9PyS3FcKwsMi0OK3CIZEp4CgEjDLkdDBs18KcVGrelnQ/Cem8bMLr9qYDFPNPR/j/qJnd+kGHlYlXdyhQxzZ9CKlSOhSnUeqPFrgmqyYFOgkSfg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(366004)(346002)(136003)(39860400002)(396003)(53546011)(6506007)(64756008)(52536014)(5660300002)(8676002)(8936002)(83080400002)(4326008)(66476007)(9686003)(7696005)(66946007)(316002)(76116006)(478600001)(83380400001)(66556008)(186003)(66574015)(2906002)(26005)(71200400001)(86362001)(966005)(66446008)(6916009)(33656002)(55016002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?VmZiaFJTMzlFRlZxQTQ5bGdidnVVVGh6RWZVSjZYRmJFTEFtR01kSHZTL1or?= =?utf-8?B?MXZFS2hRc2xmNkJacVZpQ2pNVmlnN2FPNzZYTGNhMjBxa2ViVWJ6TklPVkhO?= =?utf-8?B?bjhIbGxPclNnTFNaTWl5Vm9jOTVlaSs1QkhSd1NzZEtYOGtROHQ1ODBZRTVs?= =?utf-8?B?QjlEVm54cGJlbmNXeWdqUmR0MGdZNnFwT2cyODJjU1FaWW1IZjhpUGRUZXAy?= =?utf-8?B?UnpaVWZVb2dCTFlReU5hNWFuc25kbWwxMVU3b0RKQ3k2YkVYeS9KVGNaVTJH?= =?utf-8?B?STluT3kvMGljcWtjR3ozZGsyOENSQ2xwdzNwUHVDNjcrc1kwRHc1Slo5ZXZa?= =?utf-8?B?dHJaNmRhVEd2VTZXWjRNQkNsQSttWjhzSXVPaG5naWV5aU5Md1FObytTSDhC?= =?utf-8?B?NEpjL3plV09RTjVZckRmRGhmYkwxeldlNjM1eHFKeG5zRy95NG5QSnd1eGEv?= =?utf-8?B?Z0E2TDFCT05UZHlBLzBscFhjNTF5ZS9OOVN0emd1YmtIYWxlZDMxUlFqR0hz?= =?utf-8?B?UnkrM1FBbFV0ZnRsQjA4WmxxSyszdnZ5OEFHcnp4VE9lNHcyMHc0VEZ1L3Nh?= =?utf-8?B?SzE1c3Zsd2tZMnNWVkJ6UCtDUUc2TTUrdGhIV3NHMDl4Q0NoTlhKOENDcDF5?= =?utf-8?B?dGNEQ0IwVVk0NWgwbjV0VmNTZndpZFdzK3dZMDNLQWVZMi95aS8vOVlTK05j?= =?utf-8?B?WUFOSmFiVjB3SG1Lc1RRTElnV1pWckU3RlZZSXJZdzBTaW5XUUpZM1VsTUdq?= =?utf-8?B?WnRBVXFnSW5QSTkzYXZ1ZitYa2lxc3cxakd0enBzNi9FVW1XYlM0ZUl5bHd3?= =?utf-8?B?Y0pONlRYN2JiMFY1OEd3YVNlaEFyTTlJMkRxSjBEbXZIU1ZndDRBOWRsei9w?= =?utf-8?B?TUJ1ZGxYcGd0blR0RVIwbkpnM2gyaC9WTnByU3FVT1d2bEpMb2FuWktyd243?= =?utf-8?B?NWtyUDNBK0JacVVNYjVUcXhjQlorQmp6ZjdtZytSbE1IY0pxS293azNDbW5Z?= =?utf-8?B?MzA2ZDFibTNHNldPVnhFSlVrUlpKK01mRWgzcy9MT3VpVVRiMHBnRnJuSFl0?= =?utf-8?B?bXFoamNxUzNOL1BKOFppVU1NcndxVGkyUDY4M09WS0lVeFppd2NLWWlFMnFX?= =?utf-8?B?bzI3dnozOFFXSVBvYnVLVHJ4bUtSQkhTN1FWZWlVTG04d0o4d0dTSy83cXhC?= =?utf-8?B?eDVkZXdxZEViWnNROVAzNWpKbDRQazRUU2hpUVZ5TEJRWDF2V3VGbXdBZk95?= =?utf-8?B?K3ZJc3Y4UjQvUXBYYWhwT1ZiS2lBREFsWDd5Mmw1NDR1L1BoOWFMc0lHRHI0?= =?utf-8?Q?vvtRzzmL8rTKk=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f8918cd8-d1f0-40ba-2dde-08d8b815812f
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2021 22:49:37.3752 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ive87LeKZyBdrwJ0nl3k7w6mHFL3M48+FXdlngv7+ZvUjotNXPidsHE237r1kh/eOpgabPmA116vyGmHTDffNkjBhYviKOzDplrTQAE99dI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1417
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/CSae7UELuDC9mX6BfGizF9l51q4>
Subject: Re: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 22:49:41 -0000

SGkgUnVzcywNCg0KWWVzLCBJJ20gaGFwcHkgdG8gcHJlc2VudCBvbiB0aGUgMjh0aC4NCg0KSSB3
YW50IHRvIG1ha2Ugc3VyZSBJJ3ZlIGdvdCB0aGUgcmlnaHQgbGlzdCBvZiB0b3BpY3MgdGhhdCBw
ZW9wbGUgYXJlIGludGVyZXN0ZWQgaW4ga25vd2luZy4gU28gZmFyIGl0IHNvdW5kcyBsaWtlIG15
IHByZXNlbnRhdGlvbiBzaG91bGQgYmU6DQoNCi0gVGhlIGdlbmVyYWwgc3VnZ2VzdGlvbiB0aGF0
IExBTVBTIHJlLWNoYXJ0ZXIgdG8gd29yayBvbiBoeWJyaWQga2V5IGV4Y2hhbmdlIGFuZCBkdWFs
IHNpZ25hdHVyZSBtZWNoYW5pc21zIGZvciBDTVMgYW5kIFBLSVggcHJvdG9jb2xzLCBpZSBmdWxm
aWxsIE5JU1QncyBjYWxsIGZvciBzdWNoIG1lY2hhbmlzbXMuDQotIE92ZXJ2aWV3IG9mIHRoZSBj
b21wb3NpdGUga2V5cyBhbmQgc2lnbmF0dXJlcyBkcmFmdC4NCi0gVXNlLWNhc2VzIGZvciBjb21w
b3NpdGUgY2VydGlmaWNhdGVzLg0KLSBVc2UtY2FzZXMgZm9yIGNvbXBvc2l0ZSBrZXlzIGFuZCAv
IG9yIHNpZ25hdHVyZXMgaW5kZXBlbmRlbnRseSBvZiBjZXJ0aWZpY2F0ZXMuDQoNCkFyZSB0aGVy
ZSBvdGhlciB0b3BpY3MgdGhhdCBJJ20gdGhlIHJpZ2h0IHBvc2l0aW9uIHRvIHByZXNlbnQgb24/
DQoNCi0tLQ0KTWlrZSBPdW5zd29ydGgNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IFNwYXNtIDxzcGFzbS1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2YgUnVzcyBIb3Vz
bGV5DQpTZW50OiBKYW51YXJ5IDEzLCAyMDIxIDQ6MzAgUE0NClRvOiBNaWtlIE91bnN3b3J0aCA8
TWlrZS5PdW5zd29ydGhAZW50cnVzdC5jb20+DQpDYzogTEFNUFMgPHNwYXNtQGlldGYub3JnPg0K
U3ViamVjdDogUmU6IFtsYW1wc10gW0VYVEVSTkFMXVJlOiBDYWxsIGZvciBQcmVzZW50YXRpb25z
IGF0IHRoZSBMQU1QUyBJbnRlcmltIE1lZXRpbmcgb24gMjggSmFuIDIwMjENCg0KTWlrZToNCg0K
SSBkbyBub3Qgc2VlIHRoZW0gYXMgb3J0aG9nb25hbC4gIElmIG9uZSB1c2VzIHRoZSBjb21wb3Np
dGUgc2lnbmF0dXJlIHN0cnVjdHVyZSB7UlNBLFBRfSBvbiB0aGUgd2lyZSwgYW5kIHRoZSBwdWJs
aWMga2V5cyBhcmUgaW4gc2VwYXJhdGUgY2VydGlmaWNhdGVzLCBJIGNhbm5vdCBzZWUgaG93IHRo
ZSB2YWxpZGF0aW9uIHdvcmtzIG91dC4gIE1heWJlIEkgYW0gbWlzc2luZyBzb21ldGhpbmcuICBD
YW4geW91IHB1dCB0b2dldGhlciBzb21lIHNpZGVzIGZvciB0aGUgSW50ZXJpbSBtZWV0aW5nIG9u
IHRoZSAyOHRoIHRvIGV4cGxhaW4gbW9yZSBmdWxseT8NCg0KUnVzcw0KDQoNCj4gT24gSmFuIDEz
LCAyMDIxLCBhdCAyOjA0IFBNLCBNaWtlIE91bnN3b3J0aCA8TWlrZS5PdW5zd29ydGg9NDBlbnRy
dXN0LmNvbUBkbWFyYy5pZXRmLm9yZz4gd3JvdGU6DQo+IA0KPiBBdCB0aGUgcmlzayBvZiBvdmVy
LWNvbXBsaWNhdGluZyBldmVyeXRoaW5nLCB3ZSBzZWUgdGhlIE9uZS1DZXJ0IHZzIFR3by1DZXJ0
IGRpc2N1c3Npb24gYXMgaW4gc29tZSBzZW5zZXMgb3J0aG9nb25hbCB0byBvdXIgY29tcG9zaXRl
IGtleXMgYW5kIHNpZ25hdHVyZXMgZHJhZnQgKGRyYWZ0LW91bnN3b3J0aC1wcS1jb21wb3NpdGUt
c2lncykuDQo+IA0KPiBJIHRoaW5rIHRoYXQgc2hvZWhvcm5pbmcgdGhpcyBpbnRvIGEgIm9uZS1j
ZXJ0IHZzIHR3by1jZXJ0IiBkaXNjdXNzaW9uIGlzIG1pc3Npbmcgc29tZSBvZiB0aGUgcG90ZW50
aWFsIHZhbHVlIG9mIHRoZSBDb21wb3NpdGUgcHJvcG9zYWwuDQo+IA0KPiBJbiB3cml0aW5nIHRo
ZSBjb21wb3NpdGUgZHJhZnQsIHdlIHdlcmUgY2FyZWZ1bCB0byBub3QgbWFrZSBpdCBhIGNlcnRp
ZmljYXRlcyBkcmFmdCwgYW5kIGluc3RlYWQgc3RpY2sgc3RyaWN0bHkgdG8gcHVibGljIGtleSwg
cHJpdmF0ZSBrZXksIGFuZCBzaWduYXR1cmUgT0lEcyBhbmQgQVNOLjEgZW5jb2RpbmdzLiBBdCBw
cmVzZW50LCB3ZSBhcmUganVzdCBsb29raW5nIGF0IGNvbXBvc2l0ZSBrZXkgYW5kIHNpZ25hdHVy
ZSBmb3JtYXRzIHNvIHRoYXQgdGhlcmUgaXMgYW4gb2J2aW91cyBhbmQgc3RhbmRhcmRpemVkIHdh
eSB0byBtZWV0IHRoZSBOSVNUIGNhbGwgZm9yIHB1dHRpbmcgZHVhbCBzaWduYXR1cmVzIG9uIDx0
aGluZz47IHdoYXRldmVyIDx0aGluZz4gaXMuDQo+IA0KPiBGb3IgZXhhbXBsZSwgc29tZW9uZSB3
YXkgd2FudCB0byBjb21iaW5lIGJvdGggYXBwcm9hY2hlcyBhbmQgaGF2ZSBhIFR3by1DZXJ0IGVj
b3N5c3RlbSB3aGVyZSBvbmUgb2YgdGhlIGNlcnRzIGlzIENvbXBvc2l0ZToNCj4gDQo+IENlcnQx
OiB7UlNBfQ0KPiBDZXJ0Mjoge1JTQSwgUFF9DQo+IA0KPiANCj4gQW5vdGhlciBleGFtcGxlIG9m
IHRoZW0gYmVpbmcgb3J0aG9nb25hbCBpcyBhIGNhc2Ugd2hlcmUgeW91IGhhdmUgc2VwYXJhdGUg
Y2VydGlmaWNhdGVzIHtSU0F9LCB7UFF9LCBidXQgZm9yIHByb3RvY29sIHNpbXBsaWNpdHkgeW91
IHdhbnQgdG8gdXNlIHRoZSBjb21wb3NpdGUgc2lnbmF0dXJlIHN0cnVjdHVyZSB7UlNBLFBRfSBv
biB0aGUgd2lyZS4NCj4gDQo+IE91ciBkcmFmdCAoZHJhZnQtb3Vuc3dvcnRoLXBxLWNvbXBvc2l0
ZS1zaWdzKSBpcyByZWFsbHkgdHJ5aW5nIHRvIGJlIG9ydGhvZ29uYWwgZnJvbSB0aGUgT25lLUNl
cnQgdnMgVHdvLUNlcnQgcXVlc3Rpb24uDQo+IA0KPiAtLS0NCj4gTWlrZSBPdW5zd29ydGgNCj4g
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IFNwYXNtIDxzcGFzbS1ib3Vu
Y2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2YgTWljaGFlbCBSaWNoYXJkc29uDQo+IFNlbnQ6IEph
bnVhcnkgMTMsIDIwMjEgMTE6NTUgQU0NCj4gVG86IExBTVBTIDxzcGFzbUBpZXRmLm9yZz4NCj4g
U3ViamVjdDogW0VYVEVSTkFMXVJlOiBbbGFtcHNdIENhbGwgZm9yIFByZXNlbnRhdGlvbnMgYXQg
dGhlIExBTVBTIA0KPiBJbnRlcmltIE1lZXRpbmcgb24gMjggSmFuIDIwMjENCj4gDQo+IA0KPiBQ
YW5vcyBLYW1wYW5ha2lzIFwocGthbXBhbmFcKSA8cGthbXBhbmE9NDBjaXNjby5jb21AZG1hcmMu
aWV0Zi5vcmc+IHdyb3RlOg0KPj4gSSBoYXZlIGJlZW4gb24gYm90aCBzaWRlcyBvZiB0aGUgYXJn
dW1lbnQsIENsYXNzaWNhbCtQUSBzaWduYXR1cmVzIG9yIA0KPj4gcGFyYWxsZWwgKGNsYXNzaWNh
bCwgUFEpLiBSZWNlbnRseSBJIGhhdmUgYmVlbiB0aGlua2luZyB0aGF0IHdlIA0KPj4gcHJvYmFi
bHkgY2FuJ3QgYXZvaWQga2VlcGluZyBjbGFzc2ljYWwgUEtJIGZvciBiYWNrd2FyZHMgDQo+PiBj
b21wYXRpYmlsaXR5IHdoaWNoIHByb2JhYmx5IG1ha2VzIHRoZSBDbGFzc2ljYWwrUFEgc2lncyBs
ZXNzIGFwcGVhbGluZy4NCj4gDQo+IEZpcnN0LCBJIHRoaW5rIHRoYXQgd2UgbmVlZCBiZXR0ZXIg
dGVybXMgdG8gZXhwbGFpbiB0aGUgdHdvIG9wdGlvbnMuDQo+IFJ1c3MgaGFzIHVzZWQgIk9uZSBD
ZXJ0aWZpY2F0ZSIgYW5kICJUd28gQ2VydGlmaWNhdGUiLg0KPiANCj4gSSB0aGluayB0aGF0IGlu
IHRoZSAiT25lIENlcnRpZmljYXRlIiBjYXNlLCB0aGF0IHRoZSBQUUMgYW5kIHRyYWRpdGlvbmFs
IChIZSBzYWlkICJ0cmFkaXRpb25hbCIsIGFuZCBQYW5vcyBzYWlkICJjbGFzc2ljYWwiLCBidHcp
IENBIHNpZ25lcnMgd291bGQgc2lnbiBib3RoIEJRQyBhbmQgdHJhZGl0aW9uYWwga2V5cy4gIFJp
Z2h0Pw0KPiANCj4gDQo+PiBFc3BlY2lhbGx5IGZvciBsaXZlIHByb3RvY29scw0KPj4gbGlrZSBU
TFMsIHRoaXMgYXJndW1lbnQgaXMgZXZlbiBtb3JlIHJlbGV2YW50IGVzcGVjaWFsbHkgc2luY2Ug
dGhlIA0KPj4gYmlnIGNlcnQgd291bGQgYmUgcGVuYWxpemluZyB0aGUgY2xhc3NpY2FsIHBlZXIg
d2l0aCB1bm5lY2Vzc2FyeSBQUSBzaWcgZGF0YS4NCj4gDQo+IEl0IHNlZW1zIHRoYXQgZm9yIGxp
dmUgcHJvdG9jb2xzIHdlIGNhbiBuZWdvdGlhdGUsIGFuZCB0aGUgc2VydmVyIGNhbiBzZW5kIG9u
bHkgd2hhdCBpcyBuZWVkZWQsIHNvIHRoZXJlIGFyZSByZWFsbHkgbm8gYnl0ZS1zaXplIGlzc3Vl
cy4NCj4gDQo+PiBCdXQgSSBoYXZlIGhlYXJkIHNvbWUgYXJndW1lbnRzIGZvciBjbGFzc2ljYWwr
UFEgZm9yIG5vbi1UTFMgDQo+PiB1c2VjYXNlcy4gQW4gZXhhbXBsZSBjb3VsZCBiZSBTVyBTaWdu
aW5nLiBJIHdvdWxkIGFyZ3VlIHRoYXQgDQo+PiBQS0NTIzcvQ01TIGNhbiBpbmNsdWRlIG11bHRp
cGxlIHNpZ3MgKGluIFNpZ25lckluZm8pIGluIHRoZSANCj4+IFNpZ25lZERhdGEgYXMgY2xhcmlm
aWVkIGluIFJGQzQ4NTMsIHNvIGV2ZW4gZm9yIFNXIFNpZ25pbmcgd2UgbWF5IG5vdCANCj4+IG5l
ZWQgQ29tcG9zaXRlIG9yIEh5YnJpZCBDbGFzc2ljYWwrUFEgU2lnbmF0dXJlcy4NCj4gDQo+IFRo
YXQgc2VlbXMgdG8gYmUgdGhlIHBhcmFsbGVsIGNhc2UsIGlzbid0IGl0Pw0KPiANCj4gSSBoYXZl
IGEgZGlmZmVyZW50IGNvbmNlcm4gdG8gYXNrIGFzIHdlbGw6DQo+ICBBcmUgaGFzaC1iYXNlZCBz
aWduYXR1cmVzIGluIHRoZSBjbGFzc2ljYWwgb3IgUFFDIGNhdGVnb3J5Pw0KPiANCj4+IEkgZ2F2
ZSB0aGlzIHByZXNlbnRhdGlvbiBhdCB0aGUgTklTVCBOQ0NvRSBWaXJ0dWFsIFdvcmtzaG9wIG9u
IA0KPj4gQ29uc2lkZXJhdGlvbnMgaW4gTWlncmF0aW5nIHRvIFBvc3QtUXVhbnR1bSBDcnlwdG9n
cmFwaGljIEFsZ29yaXRobXM6DQo+PiBodHRwczovL3d3dy5uY2NvZS5uaXN0Lmdvdi9zaXRlcy9k
ZWZhdWx0L2ZpbGVzLzEwLUhvdXNsZXktTkNDb0UtV29ya3MNCj4+IGhvcC1UcmENCj4+IG5zaXRp
b24tdG8tUFFDLUNlcnRpZmljYXRlcy5wZGYNCj4gDQo+PiBUaGlzIHNob3J0IHByZXNlbnRhdGlv
biBzdGlsbCBjYXB0dXJlcyBteSB2aWV3LiAgQXJlIHRoZXJlIHBlb3BsZSANCj4+IHdpdGggYSBk
aWZmZXJlbnQgdmlldyB0aGF0IHdvdWxkIGxpa2UgdGltZSBvbiB0aGUgYWdlbmRhIGF0IHRoZSBM
QU1QUyANCj4+IEludGVyaW0gb24gMjggSmFuPyAgSSB3b3VsZCBsaWtlIHRvIG1ha2Ugc3VyZSB0
aGF0IGFsbCBwb2ludCBvZiB2aWV3IGFyZSBoZWFyZC4NCj4gDQo+IFJ1c3MnIHByZWZlcmVuY2Ug
aXMgZm9yICJUd28gQ2VydGlmaWNhdGUiIGNhc2UuDQo+IEkgdGhpbmsgdGhhdCBpdCBpcyBlcXVp
dmFsZW50IHRvIGhhdmluZyBSU0EgYW5kIEVDRFNBIGVjb3N5c3RlbXMgYWxpdmUsIHdoaWNoIEkg
dGhpbmsgd2UgaGF2ZSBtYW5hZ2VkIHJlYXNvbmFibHkgd2VsbC4NCj4gU28gSSBkb24ndCB0aGlu
ayB0aGF0IEkgaGF2ZSBhIGRpdmVyZ2luZyB2aWV3Lg0KPiANCj4gLS0NCj4gTWljaGFlbCBSaWNo
YXJkc29uIDxtY3IrSUVURkBzYW5kZWxtYW4uY2E+ICAgLiBvIE8gKCBJUHY2IEnDuFQgY29uc3Vs
dGluZyApDQo+ICAgICAgICAgICBTYW5kZWxtYW4gU29mdHdhcmUgV29ya3MgSW5jLCBPdHRhd2Eg
YW5kIFdvcmxkd2lkZSANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4gU3Bhc20gbWFpbGluZyBsaXN0DQo+IFNwYXNtQGlldGYub3JnDQo+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc3Bhc20NCg0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClNwYXNtIG1haWxpbmcgbGlzdA0KU3Bh
c21AaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc3Bhc20N
Cg==


From nobody Wed Jan 13 23:56:16 2021
Return-Path: <tadahiko.ito.public@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 146BC3A121E for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 23:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fO_s0wHADPxh for <spasm@ietfa.amsl.com>; Wed, 13 Jan 2021 23:56:13 -0800 (PST)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD5783A121D for <spasm@ietf.org>; Wed, 13 Jan 2021 23:56:13 -0800 (PST)
Received: by mail-io1-xd2a.google.com with SMTP id d9so9455968iob.6 for <spasm@ietf.org>; Wed, 13 Jan 2021 23:56:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=gSxhNCtPG3ttwqaUMLv6mqi7l4Rrg/y8R8O8b0lG2ts=; b=XLjAr9ppeBEuTGVoiCoJ+/vlIMrDcS+a+6ABn9LFcWqybyCboQR0CbtdmVQK4F6XVm 87RkIlgorfeCwLmiclDQYgUSEPCAqtVag50hxQbABdDy7+KYVCnc6q3bXPMFz7xSmDC3 mYtLlnd6lawpdPTsUkm9zAC2VUdEaWWcpoZm4dV59fyJN/d1Lux/mk5VwMj2VqCl6ljr V/6NwqOAQHweFRT41o9EZr+ST7p/NTOTte6Kc6Izco/qdV2WYZ3EQrMHtbWUF81Yx+FL hB0vLAUwIhnoTU8LUnni2ktzAkxPQ2xLDLSMq3bCmJQsgUo1a+QYzvr6Y5DCndvFiQEf Kg6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=gSxhNCtPG3ttwqaUMLv6mqi7l4Rrg/y8R8O8b0lG2ts=; b=LnkYciBXkLuvh1JbdnFtTfZ0cbxRIMg8omhAtH/ELXWjBAyY+UFQf9GRevkvDPBDJT wynDNsXMlwtJBK9Pb7+eh9a26YV3eCmmzKs4nvcLrUT//7Bx/7mszF2lyfBoUn7d++KT mXnNo/ND0hCzCu/7j9fKN2FVs6D8OkfKiR+tPDQD5f3icsT43XEuvKTDEjzYukYz/e+w yIyyP/7y6MuOaz1yJxlsyxdmjzGTJJjx7oytM/0COEzWojTx3lPoJNoznNhfPycj4mE7 0GwX7UGDnMRTkSIEhMmmIIe/7lVy16QOTa5VqDRdFsIjbE+1PCH552tZLxPRamw/0hsE 2yvQ==
X-Gm-Message-State: AOAM531yg/qwJZcmQqKbWGuPMcah5ft+9V1z6ZjWGosN3yfy43YWLgLb XeoK3ftLVPpdLXVXKZfWYvI89HcDLKoFgAg5iW8=
X-Google-Smtp-Source: ABdhPJyLULbhD2DMfi2YACs74CnIDerTAocq0SU/AlZOUgOeNyBp1F1WPfxsxniiXEhXZziYpEQXR3Noszo80UJGdt8=
X-Received: by 2002:a02:ca54:: with SMTP id i20mr5509373jal.111.1610610972393;  Wed, 13 Jan 2021 23:56:12 -0800 (PST)
MIME-Version: 1.0
From: Tadahiko Ito <tadahiko.ito.public@gmail.com>
Date: Thu, 14 Jan 2021 16:56:01 +0900
Message-ID: <CAFTXyYCC3uLW7H3rKmjvFabRWkUWXjPWsond2qPCcCQktRgeEA@mail.gmail.com>
To: quynh.dang@nist.gov, pkampana@cisco.com
Cc: LAMPS WG <spasm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e1859405b8d79627"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/BtDZQiDQGh3zuGIGv8LRECQGHWo>
Subject: Re: [lamps] Call for Presentations at the LAMPS Interim Meeting on 28
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 07:56:15 -0000

--000000000000e1859405b8d79627
Content-Type: text/plain; charset="UTF-8"

Hi Quynh.



>>If we have pre-hash and non-prehash versions, then the asymmetric
operation must be domain-separated between the 2.

>>Otherwise, obtaining a signature from a pre-hash version is an attack on
the non-prehash version.



It is a very good point.

I am not sure about the difficulty of domain-separation, but apart from
that, there would be difficulty here.



>>hash(tr || M) would become hash(0|| tr || M) and hash(1|| tr || M) for
the pre-hash and non-prehash options, for example.



I believe that tr should be secret, so that fix will be inside of
asymmetric function (and inside of the HSM in my case).
I feel like I should not simply introduce a pre-hash.

It also seems it would increase implementation complexity. In addition,
necessity of choosing mode may be confusing.



Regards Tadahiko Ito

--000000000000e1859405b8d79627
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><p class=3D"MsoNormal" a=
lign=3D"left" style=3D"margin:0mm;font-size:10.5pt;font-family:=E6=B8=B8=E6=
=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US" style=3D"font-=
size:9pt;font-family:Candara,sans-serif;color:rgb(34,34,34)">Hi Quynh.=C2=
=A0=C2=A0<span></span></span></p><p class=3D"MsoNormal" align=3D"left" styl=
e=3D"margin:0mm;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,se=
rif;color:rgb(0,0,0)"><span lang=3D"EN-US" style=3D"font-size:9pt;font-fami=
ly:Candara,sans-serif;color:rgb(34,34,34)"><span>=C2=A0</span></span></p><p=
 class=3D"MsoNormal" align=3D"left" style=3D"margin:0mm;font-size:10.5pt;fo=
nt-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D=
"EN-US" style=3D"font-size:9pt;font-family:Candara,sans-serif;color:rgb(34,=
34,34)">&gt;&gt;If we have pre-hash and non-prehash versions, then the asym=
metric operation must be domain-separated between the 2.=C2=A0=C2=A0<span><=
/span></span></p><p class=3D"MsoNormal" align=3D"left" style=3D"margin:0mm;=
font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,=
0,0)"><span lang=3D"EN-US" style=3D"font-size:9pt;font-family:Candara,sans-=
serif;color:rgb(34,34,34)">&gt;&gt;Otherwise, obtaining a signature from a =
pre-hash version is an attack on the non-prehash version.=C2=A0=C2=A0<span>=
</span></span></p><p class=3D"MsoNormal" align=3D"left" style=3D"margin:0mm=
;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0=
,0,0)"><span lang=3D"EN-US" style=3D"font-size:9pt;font-family:Candara,sans=
-serif;color:rgb(34,34,34)"><span>=C2=A0</span></span></p><p class=3D"MsoNo=
rmal" align=3D"left" style=3D"margin:0mm;font-size:10.5pt;font-family:=E6=
=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US" style=
=3D"font-size:9pt;font-family:Candara,sans-serif;color:rgb(34,34,34)">It is=
 a very good point.</span></p><p class=3D"MsoNormal" align=3D"left" style=
=3D"margin:0mm;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,ser=
if;color:rgb(0,0,0)"><span lang=3D"EN-US" style=3D"font-size:9pt;font-famil=
y:Candara,sans-serif;color:rgb(34,34,34)">I am not sure about the difficult=
y of domain-separation, but apart from that, there would be difficulty here=
.=C2=A0<span></span></span></p><p class=3D"MsoNormal" align=3D"left" style=
=3D"margin:0mm;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,ser=
if;color:rgb(0,0,0)"><span lang=3D"EN-US" style=3D"font-size:9pt;font-famil=
y:Candara,sans-serif;color:rgb(34,34,34)"><span>=C2=A0</span></span></p><p =
class=3D"MsoNormal" align=3D"left" style=3D"margin:0mm;font-size:10.5pt;fon=
t-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"=
EN-US" style=3D"font-size:9pt;font-family:Candara,sans-serif;color:rgb(34,3=
4,34)">&gt;&gt;hash(tr || M) would become hash(0|| tr || M) and hash(1|| tr=
 || M) for the pre-hash and non-prehash options, for example.<span></span><=
/span></p><p class=3D"MsoNormal" align=3D"left" style=3D"margin:0mm;font-si=
ze:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><=
span lang=3D"EN-US" style=3D"font-size:9pt;font-family:Candara,sans-serif;c=
olor:rgb(34,34,34)"><span>=C2=A0</span></span></p><p class=3D"MsoNormal" al=
ign=3D"left" style=3D"margin:0mm;font-size:10.5pt;font-family:=E6=B8=B8=E6=
=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US" style=3D"font-=
size:9pt;font-family:Candara,sans-serif;color:rgb(34,34,34)">I believe that=
 tr should be secret, so that fix will be inside of asymmetric function (an=
d inside of the HSM in my case).=C2=A0<br>I feel like I should not simply i=
ntroduce a pre-hash.<span></span></span></p><p class=3D"MsoNormal" align=3D=
"left" style=3D"margin:0mm;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=
=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US" style=3D"font-size:9=
pt;font-family:Candara,sans-serif;color:rgb(34,34,34)">It also seems it wou=
ld increase implementation complexity. In addition, necessity of choosing m=
ode may be confusing.<span></span></span></p><p class=3D"MsoNormal" align=
=3D"left" style=3D"margin:0mm;font-size:10.5pt;font-family:=E6=B8=B8=E6=98=
=8E=E6=9C=9D,serif;color:rgb(0,0,0)"><span lang=3D"EN-US" style=3D"font-siz=
e:9pt;font-family:Candara,sans-serif;color:rgb(34,34,34)"><span>=C2=A0</spa=
n></span></p><p class=3D"MsoNormal" align=3D"left" style=3D"margin:0mm;font=
-size:10.5pt;font-family:=E6=B8=B8=E6=98=8E=E6=9C=9D,serif;color:rgb(0,0,0)=
"><span lang=3D"EN-US" style=3D"font-size:9pt;font-family:Candara,sans-seri=
f;color:rgb(34,34,34)">Regards Tadahiko Ito</span><span lang=3D"EN-US" styl=
e=3D"font-size:8pt;font-family:-webkit-standard,serif"><span></span></span>=
</p></div></div></div>

--000000000000e1859405b8d79627--


From nobody Thu Jan 14 04:10:24 2021
Return-Path: <ilariliusvaara@welho.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B39E3A1444 for <spasm@ietfa.amsl.com>; Thu, 14 Jan 2021 04:10:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.009, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X86uc4U82YgR for <spasm@ietfa.amsl.com>; Thu, 14 Jan 2021 04:10:22 -0800 (PST)
Received: from welho-filter2.welho.com (welho-filter2b.welho.com [83.102.41.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA1DD3A13DE for <spasm@ietf.org>; Thu, 14 Jan 2021 04:10:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by welho-filter2.welho.com (Postfix) with ESMTP id A5972CFF46 for <spasm@ietf.org>; Thu, 14 Jan 2021 14:10:18 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp1.welho.com ([IPv6:::ffff:83.102.41.84]) by localhost (welho-filter2.welho.com [::ffff:83.102.41.24]) (amavisd-new, port 10024) with ESMTP id aQ2cbr6StO7i for <spasm@ietf.org>; Thu, 14 Jan 2021 14:10:18 +0200 (EET)
Received: from LK-Perkele-VII (78-27-99-170.bb.dnainternet.fi [78.27.99.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp1.welho.com (Postfix) with ESMTPSA id 64D1B7A for <spasm@ietf.org>; Thu, 14 Jan 2021 14:10:17 +0200 (EET)
Date: Thu, 14 Jan 2021 14:10:16 +0200
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: LAMPS WG <spasm@ietf.org>
Message-ID: <YAA0qP7K+BVJcSMB@LK-Perkele-VII>
References: <CAFTXyYAme9N9BweLALU=ueu1BXH20v72bJCi35vNMWHiinBVhg@mail.gmail.com> <DM6PR11MB4380102AE9E9FD8B1D6BC5BB9FAA0@DM6PR11MB4380.namprd11.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <DM6PR11MB4380102AE9E9FD8B1D6BC5BB9FAA0@DM6PR11MB4380.namprd11.prod.outlook.com>
Sender: ilariliusvaara@welho.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/djt44KHSvhh6V-Z4n0ulf0EfZW4>
Subject: Re: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 12:10:23 -0000

On Tue, Jan 12, 2021 at 03:23:02PM +0000, Mike Ounsworth wrote:
> Hello,
> 
> I want to highlight two excellent points that you make in your paper:
> 
> 1. Using a fixed-length hash value in place of the message may affect
> the security proof of the asymmetric algorithm, so this probably
> needs to be validated by cryptographers for each PQC algorithm. It
> seems from your paper that qTESLA is already compatible with this
> mode. I imagine hash-based signatures would also be ok with
> pre-hashing. Do any other PQC signature candidates have proofs that
> pre-hashing does not affect security? 

There are at least two ways pre-hashing can cause security proofs
to break, with concrete attacks:

Firstly (this was already brought up), if signature fails to
contextualize on presence of prehash, then pre-hashed message would
validate as signature of another plain message.

And without support from the signature algorithm itself, this impiles
pre-encoding even in the plain message case.


Secondly, if signature is salted, using unsalted prehash will weaken
the signature.

FALCON, SPHINCS+ and Dilithium all seem to be salted. Thus to not weaken
security, one needs to first hash random nonce or public key _before_
the message (random nonce is stronger). 


Note that the tr in Dilithium that is a part of the private key is
actually just hash of the public key (it is part of secret key, as it
is needed for signing).



-Ilari


From nobody Thu Jan 14 04:20:49 2021
Return-Path: <ilariliusvaara@welho.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7362F3A1491 for <spasm@ietfa.amsl.com>; Thu, 14 Jan 2021 04:20:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.009, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CloLdOTTRkM0 for <spasm@ietfa.amsl.com>; Thu, 14 Jan 2021 04:20:46 -0800 (PST)
Received: from welho-filter4.welho.com (welho-filter4b.welho.com [83.102.41.30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A39C3A1490 for <spasm@ietf.org>; Thu, 14 Jan 2021 04:20:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by welho-filter4.welho.com (Postfix) with ESMTP id 7ABE967DBB for <spasm@ietf.org>; Thu, 14 Jan 2021 14:20:44 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp3.welho.com ([IPv6:::ffff:83.102.41.86]) by localhost (welho-filter4.welho.com [::ffff:83.102.41.26]) (amavisd-new, port 10024) with ESMTP id mgJAPFISgtFZ for <spasm@ietf.org>; Thu, 14 Jan 2021 14:20:44 +0200 (EET)
Received: from LK-Perkele-VII (78-27-99-170.bb.dnainternet.fi [78.27.99.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp3.welho.com (Postfix) with ESMTPSA id 371872315 for <spasm@ietf.org>; Thu, 14 Jan 2021 14:20:43 +0200 (EET)
Date: Thu, 14 Jan 2021 14:20:42 +0200
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: LAMPS <spasm@ietf.org>
Message-ID: <YAA3GqG0fDf92o3m@LK-Perkele-VII>
References: <2C7FE71D-D3DA-49CF-B133-EAC979309951@vigilsec.com> <D95BD95A-ED8C-4275-AE4F-463A41A6C85C@vigilsec.com> <BN7PR11MB254730455D173EB9769B6632C9A90@BN7PR11MB2547.namprd11.prod.outlook.com> <6452.1610560502@localhost> <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <DM6PR11MB4380C66B31D31C4B13912D859FA90@DM6PR11MB4380.namprd11.prod.outlook.com>
Sender: ilariliusvaara@welho.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/KF8WqBiQIHfA3dnejZ8utrW_JOI>
Subject: Re: [lamps] [EXTERNAL]Re: Call for Presentations at the LAMPS Interim Meeting on 28 Jan 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 12:20:48 -0000

On Wed, Jan 13, 2021 at 07:04:28PM +0000, Mike Ounsworth wrote:
> At the risk of over-complicating everything, we see the One-Cert vs
> Two-Cert discussion as in some senses orthogonal to our composite
> keys and signatures draft (draft-ounsworth-pq-composite-sigs).

I do not think these are orthogonal.

For "one-cert" to make sense, the composite certificates must be
compatible with legacy software due to very slow transition times
(at least before things turn into hot mess). The certificates from
draft-ounsworth-pq-composite-sigs are not compatible in this way,
hence only really make sense in context of two-cert system.


But depending on the protocol, it might make sense to:

1) Negotiate supported algorithms and send only the legacy or composite
   certificate.

This seems to be the only viable way for TLS 1.3, as:

a) TLS is formally capable of negotiating certificate signing
   algorithms (even if in reality this does not work all that well due
   to missing server end implementation).
b) TLS can only transmit one end-entity certificate. And in reality,
   transmitting multiple certificate chains at once might not actually
   work in interoperable way.

2) Send both at once. This is necressary for protocols that are not
   interactive.

3) Decide that the protocol is lost cause due to being insufficiently
   crypto-agile. I am sure there are at least a few of those around
   (besides TLS version 1.2, TLS 1.3 fixes those flaws).


As to very slow transition times, consider that SHA-1 to SHA-2
transition in WebPKI took about a decade. And I am not fully sure that
things will move quickly after turning out into hot mess, as IIRC MD5 to
SHA-1 transition took like 3 years after that point.

And making hybrid certificates compatible with legacy software needs
some very ugly hacks, and there might be IPR issues too.



-Ilari


From nobody Tue Jan 19 15:29:04 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 361F53A190B for <spasm@ietfa.amsl.com>; Tue, 19 Jan 2021 15:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1fs8EXsjbgzD for <spasm@ietfa.amsl.com>; Tue, 19 Jan 2021 15:28:57 -0800 (PST)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-eopbgr680090.outbound.protection.outlook.com [40.107.68.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9712F3A18FB for <spasm@ietf.org>; Tue, 19 Jan 2021 15:28:54 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=G+bTHlc/MkUKfDocLEqJZSh+MzudkD2r4S6o9B0CTVb9JVYeyGnni6hGfO+qqEa15v42zGnaAgyLkbWIETAZ/Z9w+Z1w7lge0szVBzN5h5qSxVk34RQjPbikCu4bopQyfCrLUoRhqI9j8Q6fXFE3afo1Gva39ekxWr9uaZl6ypdZ9cl8nD3JgDAOIsXePOVSJ58S562skcBNqCb5dGIgeRDdBV7MBpW/pFJ0nIF7c0ryTHSVLVYzHBQOK4SBhlTZ0cJrDS35F//fBLulw6EeQTQyG9EspzYgEuC36kqlVLeXNYhQjq7wyZRx7oI8Mg7cXC4fH+UdzPTeUjhpg/DHgg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NIplghSKksIDQx3OQ5ejT/+Q7FrwBJqB7JOigigdUyk=; b=a9WFg32VMFkmZrjFidD+Ty6b60cz1GTczlMzV59WSuLK25VXQDL1OONiwZ/8i9AmLO5WJUffQ0yfXWLWKfWJdqwFm1jVC7ydRPNpEiUaVztX0La+eqjn75LSMrVK6bJzca6RV1pMULn5PddrjSQHgL7kyrtfgS7ozq1avR7LmrIiAZuzo2Fr84+MHKqg25Qr+vrafOZLyDq+m1luRiuwxG6gLej+MfZOSxnIkZM8KMIC2c4OKxmEpbwixMCkoydrdAAQMXy6lFzXR+6nCZQOZ10PrxLBaqRkFpnPEMGLWvdxMwDa7//SBlO+gn0kmnjxhKKEtYFw0+Jrtq9H8FXfDw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NIplghSKksIDQx3OQ5ejT/+Q7FrwBJqB7JOigigdUyk=; b=IX6UGL+xjLmK3cD3U30XXU7BcqfbTF91Lgj5pE0pywYx+wMr+XIKhTzJp6L4XbTrVftD4e+2TeeLKqzKnEougHwT3P4tqytd5ILeXIfsdsugd8w+u5mY9pb116qf7iF7w/k4Vg9IR8qlQcALY1slniUJrpQ8gu3OHl2OVFK12zHYf6pd12vnCLToFKNMK0XI2AVuhKDk7xwqyKxWB2lk3G7bIP8iCm+LFTG2ZHXV3eQ6M3REofCQ6ejci4bFSyG4zv69F0jWU2QIl+Yyx+AI3pIMLA+kDp9wlVs9gEyjMGqnPHMR2xDivicMAEvGX9k5cwZwE9GlqOhEaLbqpL+oTw==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM5PR11MB1612.namprd11.prod.outlook.com (2603:10b6:4:b::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.9; Tue, 19 Jan 2021 23:28:52 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::a816:b4fb:846e:9417]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::a816:b4fb:846e:9417%6]) with mapi id 15.20.3763.014; Tue, 19 Jan 2021 23:28:52 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Russ Housley <housley@vigilsec.com>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
CC: "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [EXTERNAL]Re: [lamps] [CMP Algorithms] Use Key-Wrap with or without padding in Section 4.3 and Section 5
Thread-Index: Adaruf01J5o8GQNXSnKFZnSnQvB7NgAD0msAELvSkzA=
Date: Tue, 19 Jan 2021 23:28:52 +0000
Message-ID: <DM6PR11MB4380CB89F71A459DF133E7BC9FA30@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <AM0PR10MB2418EE8CF8A2A721861B64F5FE190@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <C02DCAC5-2B4B-4FBD-88A6-AD60A4610757@vigilsec.com>
In-Reply-To: <C02DCAC5-2B4B-4FBD-88A6-AD60A4610757@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [2605:8d80:6a1:c927:c852:ea95:add:40ba]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 812710f3-ba65-4daa-e3e9-08d8bcd1fb78
x-ms-traffictypediagnostic: DM5PR11MB1612:
x-microsoft-antispam-prvs: <DM5PR11MB16129CA9082853036F979E279FA30@DM5PR11MB1612.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Affl0eWlUPT4XXyYIKYIPsqP6tlIf95goSJzJf016bY8pm3OCAJ3Sa1doPiYBw+fycrmaDp6Ep+QxjT/Axi4FPnVYcIDb5NiRDWLL9XoIOufHkFSHurdI8O+bvv4wCx78g594IXzyyVLM4DgqcjL2JTewdEcZuaAt8a+JV/oc7ZTg3FvcLncJS0h7QYKSz7Ppsxtz1LovkfXhLWpu+fYHfdDoz+1sZgXX4cKfPk/zUHnSyYre+rrHgUCx6nGNB/qzifIN1M/Sy0v6b1Qdp1FG/vi/4z9biNDrJIfxfTwkS03M+vQtAvxCsN43v9toV9eUjYWyqPpXbZMTzUzt+J2Ek5rcloS0kKKnBQPWwtOLDGZPn8iC8n//i6a0OfTDNtTV6DHSMxHyEkdkt/MunIYCR3kRKYbmkW76l0gBsy8HNjWIZp6asUnlsbpBIV6+Mc4lUmu3BvlIgg55vhS+duUCQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(396003)(136003)(366004)(39860400002)(376002)(8936002)(966005)(478600001)(186003)(53546011)(6506007)(8676002)(66476007)(33656002)(55016002)(4326008)(5660300002)(110136005)(9686003)(66556008)(66946007)(71200400001)(2906002)(76116006)(7696005)(83380400001)(64756008)(86362001)(316002)(52536014)(66446008); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?0UNeB1mi6u+/ojWM5cN3jxdVEogI7nb0cW/IHxH2BoS189IxOkVl/THFQAgn?= =?us-ascii?Q?3/XxpVJeh72W/TqUxvovBxnKP5OuqEjvyf3NNDqFlJ4C7FSgVIV7aRz2hQpo?= =?us-ascii?Q?5N3LxxWugqdc1jF2Nra+qD1kZ6xsINXwafevyIlQiIPo1V+wYwlEaj/k0BGt?= =?us-ascii?Q?ewrbAYSStvcI9eNOTwVV1eeZa0BvR9yzcKuzxYnXVgJN2lvZBB6QZsm+Trqn?= =?us-ascii?Q?sUsSZD+5bctpvnaGPcmdFjmWETKMj3OTMJbQNM/ipDxfeu4qt/8w8neD6lhb?= =?us-ascii?Q?XRe9ODhi6vXAxFHuta+JYsYBNe0y+NUhJcwFCkI+3v7xJgjuLCNL9gCeidhX?= =?us-ascii?Q?2UAZyGiXdDJ+lJ0yGq7SrLolRFiHErBrd9l6JvMXylXwhZCzGOSv0fKacKaU?= =?us-ascii?Q?NdPp8kCNY4CQ4+gz1h3Ye7uIrfsgJ8DUX9UDJpFWwRLbP7WrRCGXC9Qd18Yy?= =?us-ascii?Q?TgrNH+/n0Kz56qNpFzPeG0DLL75WypC+szm0HNZgwfzPbzAvXh1gpFyPYDKc?= =?us-ascii?Q?QbeN1+nF1WGaEvVavQnp4obi8Yhzvhpzf4/mYg1Gy0NR3vlBCml5UzbP1qmi?= =?us-ascii?Q?ECYnPATVKwkKPYyD3vFvfAis5JuubrPpkU6C0sXJtHgIuHeWt1BIqSWjUjqQ?= =?us-ascii?Q?YgUIOsNUK+QA+dw/eooOG9Ihxw9j2/N4TdInlW6YLeZp/kwAfpdfksUowK3h?= =?us-ascii?Q?PjJVMqELtPS+3uH/DaZ4DeF7Tgfv28fn2rpAvaBD6r/8Ak9wKKH7pImw7r1F?= =?us-ascii?Q?0Fy/z4Y6R/oyBPwIUz2WXOqyp3WCNnOkj5ew9zrOK2eMFa2hVe+s4fFgGW1g?= =?us-ascii?Q?7rO3xxmJxwZjSeb9k3xSqINaeI5zCepHRD3pfnyHdSFO+CSw6xf6tkI4eLOB?= =?us-ascii?Q?H4WhYfLhuEzc8495tHzHCtKW5DWsf1wesrDmvOyawj0/YwEeyNrWu4QU3seh?= =?us-ascii?Q?zL0+wsZkjw7w+YpfL5qDa/vxeonNn09BDSm2e2lge+y9/JL4Ir/SAOx2OdqR?= =?us-ascii?Q?jDhvebIkzpE+lxWrWL0F6ZfFeCPLc+QtyWP65uUxeCVdgbA=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 812710f3-ba65-4daa-e3e9-08d8bcd1fb78
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jan 2021 23:28:52.5416 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: zq61Dr7BZSSw0d8ilYKVK+pt16R7UXWrMsx4mDXOqfVoRu1wKDEUtWdYTJ0J73RwQxbKf+ojgOqM5l3YDzw45AEzGqqtKZuLKwEGUR6FZxY=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1612
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ZGki2LtncwTQ_ko1bdL0AwNG-kQ>
Subject: Re: [lamps] [EXTERNAL]Re: [CMP Algorithms] Use Key-Wrap with or without padding in Section 4.3 and Section 5
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 23:29:03 -0000

Hello Russ,

We would like to confirm our understanding of your comment below.

There are two encryption operations at play here:

- Content encryption; this key is encrypted with the keyWrap algorithm and =
included in the message.
- KeyWrap encryption; this key is established using one of the listed key e=
stablishment mechanisms.

Your suggestion (matching 8551) is that both encryptions MUST use the same =
algorithm and key size.

Therefore, the key to be wrapped, and the AESKeyWrap's block size will alwa=
ys be the same. Therefore, there is no reason to support a padded AES schem=
e.

Can you confirm that this is the correct understanding?

---
Mike Ounsworth
Hendrix Brockhaus
John Gray

-----Original Message-----
From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
Sent: October 26, 2020 1:53 PM
To: Brockhaus, Hendrik <hendrik.brockhaus@siemens.com>
Cc: spasm@ietf.org
Subject: [EXTERNAL]Re: [lamps] [CMP Algorithms] Use Key-Wrap with or withou=
t padding in Section 4.3 and Section 5

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the =
content is safe.


> On Oct 26, 2020, at 1:12 PM, Brockhaus, Hendrik <hendrik.brockhaus@siemen=
s.com> wrote:
>=20
> I am looking for some guidance regarding encryption algorithms required f=
or CMP, especially when using EnvelopedData.
>=20
> Encryption is needed for encryption of the content-encryption key and for=
 encryption of the content itself.=20
> In case of CMP the content is a Signed Data wrapped AsymmetricKeyPackage,=
 a Certificates or a Password.
>=20
> I am uncertain whether to use AES key wrapping with or without padding?
> I am also uncertain if I can uses the same algorithm for CEK and content =
encryption?
>=20
> Any guidance is welcome.
>=20
> Hendrik

It seems that alignment with RFC 8551 would be a reasonable way forward, wh=
ich would use different algorithms for key wrap and content encryption:

   The underlying encryption functions for the key wrap and content-
   encryption algorithms [RFC3370] [RFC3565] and the key sizes for the
   two algorithms MUST be the same (e.g., AES-128 key wrap algorithm
   with AES-128 content-encryption algorithm).  As both 128-bit and
   256-bit AES modes are mandatory to implement as content-encryption
   algorithms (Section 2.7), both the AES-128 and AES-256 key wrap
   algorithms MUST be supported.

Russ
_______________________________________________
Spasm mailing list
Spasm@ietf.org
https://www.ietf.org/mailman/listinfo/spasm


From nobody Tue Jan 19 15:32:24 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C8173A1885 for <spasm@ietfa.amsl.com>; Tue, 19 Jan 2021 15:32:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8O_5CX2Uskft for <spasm@ietfa.amsl.com>; Tue, 19 Jan 2021 15:32:19 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A91713A1882 for <spasm@ietf.org>; Tue, 19 Jan 2021 15:32:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 084DC300BC5 for <spasm@ietf.org>; Tue, 19 Jan 2021 18:32:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 06Xt4GVJpHzt for <spasm@ietf.org>; Tue, 19 Jan 2021 18:32:15 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 394D2300AB0; Tue, 19 Jan 2021 18:32:15 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DM6PR11MB4380CB89F71A459DF133E7BC9FA30@DM6PR11MB4380.namprd11.prod.outlook.com>
Date: Tue, 19 Jan 2021 18:32:16 -0500
Cc: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, "spasm@ietf.org" <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3944B8B0-A6BD-430E-A9FF-8F9213914A82@vigilsec.com>
References: <AM0PR10MB2418EE8CF8A2A721861B64F5FE190@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <C02DCAC5-2B4B-4FBD-88A6-AD60A4610757@vigilsec.com> <DM6PR11MB4380CB89F71A459DF133E7BC9FA30@DM6PR11MB4380.namprd11.prod.outlook.com>
To: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/GMF7O1sQcvNyqLBM_C7_qEmlYDg>
Subject: Re: [lamps] [EXTERNAL]Re: [CMP Algorithms] Use Key-Wrap with or without padding in Section 4.3 and Section 5
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 23:32:22 -0000

Yes, that is my suggestion.

Russ



> On Jan 19, 2021, at 6:28 PM, Mike Ounsworth =
<Mike.Ounsworth=3D40entrust.com@dmarc.ietf.org> wrote:
>=20
> Hello Russ,
>=20
> We would like to confirm our understanding of your comment below.
>=20
> There are two encryption operations at play here:
>=20
> - Content encryption; this key is encrypted with the keyWrap algorithm =
and included in the message.
> - KeyWrap encryption; this key is established using one of the listed =
key establishment mechanisms.
>=20
> Your suggestion (matching 8551) is that both encryptions MUST use the =
same algorithm and key size.
>=20
> Therefore, the key to be wrapped, and the AESKeyWrap's block size will =
always be the same. Therefore, there is no reason to support a padded =
AES scheme.
>=20
> Can you confirm that this is the correct understanding?
>=20
> ---
> Mike Ounsworth
> Hendrix Brockhaus
> John Gray
>=20
> -----Original Message-----
> From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
> Sent: October 26, 2020 1:53 PM
> To: Brockhaus, Hendrik <hendrik.brockhaus@siemens.com>
> Cc: spasm@ietf.org
> Subject: [EXTERNAL]Re: [lamps] [CMP Algorithms] Use Key-Wrap with or =
without padding in Section 4.3 and Section 5
>=20
> WARNING: This email originated outside of Entrust.
> DO NOT CLICK links or attachments unless you trust the sender and know =
the content is safe.
>=20
>=20
>> On Oct 26, 2020, at 1:12 PM, Brockhaus, Hendrik =
<hendrik.brockhaus@siemens.com> wrote:
>>=20
>> I am looking for some guidance regarding encryption algorithms =
required for CMP, especially when using EnvelopedData.
>>=20
>> Encryption is needed for encryption of the content-encryption key and =
for encryption of the content itself.=20
>> In case of CMP the content is a Signed Data wrapped =
AsymmetricKeyPackage, a Certificates or a Password.
>>=20
>> I am uncertain whether to use AES key wrapping with or without =
padding?
>> I am also uncertain if I can uses the same algorithm for CEK and =
content encryption?
>>=20
>> Any guidance is welcome.
>>=20
>> Hendrik
>=20
> It seems that alignment with RFC 8551 would be a reasonable way =
forward, which would use different algorithms for key wrap and content =
encryption:
>=20
>   The underlying encryption functions for the key wrap and content-
>   encryption algorithms [RFC3370] [RFC3565] and the key sizes for the
>   two algorithms MUST be the same (e.g., AES-128 key wrap algorithm
>   with AES-128 content-encryption algorithm).  As both 128-bit and
>   256-bit AES modes are mandatory to implement as content-encryption
>   algorithms (Section 2.7), both the AES-128 and AES-256 key wrap
>   algorithms MUST be supported.
>=20
> Russ
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Wed Jan 20 08:10:38 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 456D43A14BD; Wed, 20 Jan 2021 08:10:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: spasm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: spasm@ietf.org
Message-ID: <161115903621.21831.6292824907492428494@ietfa.amsl.com>
Date: Wed, 20 Jan 2021 08:10:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/2jDqgiWcTj-Oveygc4sEjNEa7eU>
Subject: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2021 16:10:36 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Limited Additional Mechanisms for PKIX and SMIME WG of the IETF.

        Title           : CMP Algorithms
        Authors         : Hendrik Brockhaus
                          Hans Aschauer
                          Mike Ounsworth
                          Serge Mister
	Filename        : draft-ietf-lamps-cmp-algorithms-02.txt
	Pages           : 27
	Date            : 2021-01-20

Abstract:
   This document describes the conventions for using concrete
   cryptographic algorithms with the Certificate Management Protocol
   (CMP).  CMP is used to enroll and further manage the lifecycle of
   X.509 certificates.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lamps-cmp-algorithms/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-lamps-cmp-algorithms-02.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lamps-cmp-algorithms-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Jan 20 08:23:23 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 850DA3A14D4 for <spasm@ietfa.amsl.com>; Wed, 20 Jan 2021 08:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3eT3L0BmI0A for <spasm@ietfa.amsl.com>; Wed, 20 Jan 2021 08:23:19 -0800 (PST)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2074.outbound.protection.outlook.com [40.107.20.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62C683A14D3 for <spasm@ietf.org>; Wed, 20 Jan 2021 08:23:18 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=E5v9dxmpR5KSl1CIE7uomj3Z6Fx3yvPBJ+XziOVAF3yKVTntN/2QUwjpuvG0vo3ijMrocdg2et/9E0tfymaoOie+KBj31NNtEIwEWsvaQhGGAn27YLr8UUZYK8BKN+BN6Zj/+1TcBWMZZglwCusYGXL6ex4Er1kAySmD2xVceEXlnlj1stnVvx1s6z4GMC/kcbcswuzu61LUu/pn84mCUEqMYzXRqUtDnezFzm0DBGjNYbZ8bg2bJRmhBIp21mJ669ky7BzCqfKGoWKsQASN1hGL7hYgQWuN9YwSpv2nMX1qTELCu7ZfELt02MenJN9OuUkJB0OiehO6DrkkbkBCrA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5kehUavgG0YGJlspJXmiQWxTbsSKgrZdJj6zvsDVnNk=; b=Mzk+TDOPcUR2MsdHaD5BjzLWNGInnVebUy80AJmLSeiAduCKthAbSW85Sm4Wgdp9FGWqV+fSwG3Fox2/KNG3V1XIC8NIfhknmxElg9G1c8bmlTZCF0J4aPMYPoOEYWYpDpAmx6NyzEI+OdRailJLJLWMWAdjgynmBIGftgD64smOzgsneW2L2mTD6ZrPBeKbGOfddnsgux8nmf/4RR2sFgUy0RU9uGBavRjdaMnxt89aZmtIGSAE1ZUn/eO92pV9i6J9Gise05EEWl7semeF6J1pEXUhS26hmXc02mwkxIpvROPBFo6h5obufFo2YOVa4nfS+v5g31WgFkJ5d7BXNQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5kehUavgG0YGJlspJXmiQWxTbsSKgrZdJj6zvsDVnNk=; b=Khzduk0GRPbb095cD7E6ApxMOse+OXJoYaz9COTiSoxKrEOlX0xXdpVAG+H4BPk9RZUcOeTmzMqsPMIDoGKfkWSf3YZLfRk+Em1Nezj1FlaEj4VwY+W9vb1Oxc9Y7lWfYEATSKbhAsf5Ee5OG1zoS+TdJkmC8DSP5l/1Ce/G+/I=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM9PR10MB4216.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:20b:1fa::5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.9; Wed, 20 Jan 2021 16:23:16 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::a5a7:8af9:1e22:1d69]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::a5a7:8af9:1e22:1d69%6]) with mapi id 15.20.3763.014; Wed, 20 Jan 2021 16:23:16 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: "spasm@ietf.org" <spasm@ietf.org>
CC: "hans.aschauer@siemens.com" <hans.aschauer@siemens.com>, Mike Ounsworth <Mike.Ounsworth@entrust.com>, Serge Mister <Serge.Mister@entrust.com>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bT5wngqywmbE6XWcKJbZgLXqowsA+g
Date: Wed, 20 Jan 2021 16:23:16 +0000
Message-ID: <AM0PR10MB2418DF03776AD23DBE323E43FEA20@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com>
In-Reply-To: <161115903621.21831.6292824907492428494@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2021-01-20T16:23:15Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=729a2018-173a-499a-a704-3b59168ae6aa; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.183]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 99ae2d1e-2cbf-4849-d159-08d8bd5fb160
x-ms-traffictypediagnostic: AM9PR10MB4216:
x-ld-processed: 38ae3bcd-9579-4fd4-adda-b42e1495d55a,ExtAddr
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM9PR10MB4216E0C39957743E4F6A814CFEA20@AM9PR10MB4216.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bIhuVfmYNf6I6gb4Tfbt3d4cNqp9arAHxjKavle4O9Yh3X+DJa/t2h9sURA6rtrOlLc6KT0Gx0vflWLkq2CH6571zNTomAmo5+baepHf3xqbV4eo/yheoPClAW0KdeCAGNMCUZiybVFZycFAi0EALP3GYsy5UqXgAa1jMOAB3/AsLyBdpfYIGBOTqMPY79nbCsPKyJ5hXtf9kSCspfof7C9/n9imnY9CjSoK6ldCgH7K9HSrUTNuQRemCQO4V22VZbulhmlc4c2pxNwI5ED+G5rOzB7RZESf5HTdEehhdlkRd3ClMWvhvMpamS88M5UFaBBFocVSWowiWIkRRUuYqi1NTmKh+WOpd15rxyWMYe7J9RMMeq8vt5FYQhG6qZDDBynSz2nV7gShmwBOgz7ECG6DJwTYge03dcM6bQ0EPNYY8BYgl6tn+49JoM6qiaeeYLc1vDCPa+0ZAt2LqAjrQzeKdtrGlhfnRpVv194g1uvZ3HpOlJUufvIgTEgnCX3Nhaw9/NbCGghLfeeE1dHjP6jDgfacCVv2mLaXt1JQ7za3lfWcmZSBorv/puKhMc/jWT0VuKPjMswqr8KKETAu0sQf3RadkO9iOMv5bnQHrQQ=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(346002)(396003)(366004)(376002)(136003)(39860400002)(2906002)(8936002)(4326008)(76116006)(5660300002)(478600001)(83380400001)(66946007)(6916009)(66574015)(71200400001)(186003)(86362001)(6506007)(9686003)(966005)(55236004)(54906003)(52536014)(45080400002)(8676002)(66556008)(55016002)(64756008)(33656002)(66446008)(7696005)(26005)(66476007)(316002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?svfeSnNU8a/G4rlOjZ2MTOz4GttymLUTQB6u/ucC3Lz8gF1n4Xw84uONnean?= =?us-ascii?Q?omY2uCHoPdVXx3223pDiwZaOkNjvy/zgw8vR2iVyqIkUpA09uovSGfkQPHMQ?= =?us-ascii?Q?AMT9KdDdFKxvKTWncKoouFvGe/Kz00ZqMhnzHPM22LHEv0ZXMsi1FsjJuF3S?= =?us-ascii?Q?L34LbK6NRUTltoHEy9RCoLnnaTdFOFn2b83PHsVcNODvA7E8PdhmCE1/VJHu?= =?us-ascii?Q?0ungAlVbKNhgJ67bPVH6oNK4TZ74UkCxTNV2RJAOvlENVXnWeifxoKsJtsJH?= =?us-ascii?Q?nAdoaLsgHxTc++voo/zbJ2M99WCYRmqwNGo3RVUSNhGEH7+tFTmweeux+Tlm?= =?us-ascii?Q?CFBVy32zgz64Qu3SJril5YfoEMZwzijFmW1Zan4XItqDXyGKDHESMDWj7hTe?= =?us-ascii?Q?tlt1DqtpO84fJpt1ErvIh0VfhT2WWCqd87rkAyFOzyx95AXgU2y2qBmP59MO?= =?us-ascii?Q?plS3RT+IIVjDSokov68dSuvDJcp23J+9N5QmIPnGSXAB1KZTzwg70lwrnImD?= =?us-ascii?Q?qCN6EsUJeAHDmOB4GyxfBXKR5ZN1hh6AAYsci3VJRlIjyHm/MW16zL8ehDYu?= =?us-ascii?Q?p5dR8LpTiDjYQtX846ruN+H9rua+yT63KZWFVzDgOgLEaKV2O0xL1p5KPKFV?= =?us-ascii?Q?MBlqvqWrzTeMDQzxXDF4hHfVZuMoMVTz1QQ7Ayz8jvCEdwKEuqQrurJsbKHJ?= =?us-ascii?Q?tZiMavSE0+Gxlc41YDqfhPtG+POPvfmTNHsShU6E8rYLHOegnu8vqJ9Lk1Ya?= =?us-ascii?Q?+DWDvhQx/MHcJbZqzUyEVEVmKvyaYxpIVj82ukhgo7QfXAT3WS02NWG4RQ6O?= =?us-ascii?Q?HjudxxCFlFVgt7qzFdh/4Z+aYQjbfhGYk+jkBtYz5/Uqw1qnhYKirAl4lpFS?= =?us-ascii?Q?DUyergEWqJR+mmpEkIynr4ZIPCUllm+1+MfhEcXq3szrV2Z7JQ3IXx/4zywv?= =?us-ascii?Q?umdW3pDfsNuzYHh6c7cI2PM6Hd188gg+xFB6qAGhQuJsVOif9UpU5WWbyT41?= =?us-ascii?Q?eqlB?=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 99ae2d1e-2cbf-4849-d159-08d8bd5fb160
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jan 2021 16:23:16.7360 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: XZHkfagvQWyAvaRL93LuWfYG7rROq48GCv/MT6Ag0+Td1JV2KWDMmvBrZ1ALbJfzxZvCwaEp/6uY9UFu6IgcY/DR2wwaCVegDxZz6N+RmiA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM9PR10MB4216
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/00Ts-n_KIUd2aS76l3n-YQB0FlY>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2021 16:23:22 -0000

The new version of CMP Algorithms cover the following changes.=20
Thanks to the co-authors for their engagement and support.
Any feedback and comments are welcome.
Hendrik

   Changes from version 01 -> 02:
   *  Added Hans Aschauer, Mike Ounsworth, and Serge Mister as co-author
   *  Changed to XML V3
   *  Added SHAKE digest algorithm to Section 2 as discussed at IETF 109
   *  Deleted DSA from Section 3 as discussed at IETF 109
   *  Added RSASSA-PSS with SHAKE to Section 3
   *  Added SECP curves the section on ECDSA with SHA2, ECDSA with
      SHAKE, and EdDSA to Section 3 as discussed at IETF 109
   *  Deleted static-static D-H and ECDH from Section 4.1 based on the
      discussion on the mailing list (see thread "[CMP Algorithms]
      Section 4.1.1 and 4.1.2 drop static-static (EC)DH key agreement
      algorithms for use in CMP")
   *  Added ECDH OIDs and SECP curves, as well as ECDH with curve25519
      and curve448 to Section 4.1 as discussed at IETF 109
   *  Deleted RSA-OAEP from Section 4.2 first as discussed at IETF 109,
      but re-added it after discussion on the mailing list (see thread
      "Mail regarding draft-ietf-lamps-cmp-algorithms")
   *  Added a paragraph to Section 4.3.1 to explain that the algorithms
      and key length for content encryption and key wrapping must be
      aligned as discussed on the mailing list (see thread "[CMP
      Algorithms] Use Key-Wrap with or without padding in Section 4.3
      and Section 5")
   *  Deleted AES-CCM and AES-GMC from and added AES-CBC to Section 5 as
      discussed at IETF 109
   *  Added Section 6.1.2 to offer PBMAC1 as discusses on the mailing
      list (see thread "Mail regarding draft-ietf-lamps-crmf-update-
      algs-02") and restructured text in Section 6 to be easier to
      differentiate between password- and shared-key-based MAC
   *  Deleted Diffie-Hellmann based MAC from Section 6 as is only
      relevant when using enrolling Diffie-Hellmann certificates
   *  Added AES-GMAC and SHAKE-based KMAC to Section 6 as discussed at
      IETF 109
   *  Extended Section 9 to mention Russ supporting with two additional
      I-Ds and name further supporters of the draft
   *  Added a first draft of a generic algorithm selection guideline to
      Appendix A
   *  Added a first proposal for mandatory algorithms for the
      Lightweight CMP Profile to Appendix A
   *  Minor changes in wording

> Von: Spasm <spasm-bounces@ietf.org> Im Auftrag von internet-
> drafts@ietf.org
> Gesendet: Mittwoch, 20. Januar 2021 17:11
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Limited Additional Mechanisms for PKIX a=
nd
> SMIME WG of the IETF.
>=20
>         Title           : CMP Algorithms
>         Authors         : Hendrik Brockhaus
>                           Hans Aschauer
>                           Mike Ounsworth
>                           Serge Mister
> 	Filename        : draft-ietf-lamps-cmp-algorithms-02.txt
> 	Pages           : 27
> 	Date            : 2021-01-20
>=20
> Abstract:
>    This document describes the conventions for using concrete
>    cryptographic algorithms with the Certificate Management Protocol
>    (CMP).  CMP is used to enroll and further manage the lifecycle of
>    X.509 certificates.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdatat=
r
> acker.ietf.org%2Fdoc%2Fdraft-ietf-lamps-cmp-
> algorithms%2F&amp;data=3D04%7C01%7Chendrik.brockhaus%40siemens.com
> %7C33f72021ce2446610b6a08d8bd5df512%7C38ae3bcd95794fd4addab42e1
> 495d55a%7C1%7C0%7C637467558529016092%7CUnknown%7CTWFpbGZsb3
> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
> 3D%7C1000&amp;sdata=3DiCDVg2iRbQL8lyHhCLgFyMC%2Bq5clHP66SNNLLjJ4J
> Qg%3D&amp;reserved=3D0
>=20
> There is also an HTML version available at:
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.
> ietf.org%2Farchive%2Fid%2Fdraft-ietf-lamps-cmp-algorithms-
> 02.html&amp;data=3D04%7C01%7Chendrik.brockhaus%40siemens.com%7C33f
> 72021ce2446610b6a08d8bd5df512%7C38ae3bcd95794fd4addab42e1495d55
> a%7C1%7C0%7C637467558529016092%7CUnknown%7CTWFpbGZsb3d8eyJ
> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C1000&amp;sdata=3DaPFIhgAI0QsNrZd0WixSIKgzbsvaD%2F1P0VySbeYoCf4%3
> D&amp;reserved=3D0
>=20
> A diff from the previous version is available at:
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.
> ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-lamps-cmp-algorithms-
> 02&amp;data=3D04%7C01%7Chendrik.brockhaus%40siemens.com%7C33f7202
> 1ce2446610b6a08d8bd5df512%7C38ae3bcd95794fd4addab42e1495d55a%7C
> 1%7C0%7C637467558529016092%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM
> C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000
> &amp;sdata=3DAIMc2rvOMFDZTsnbuIQ5aYCKzTK%2Boq6qDpTAguR2cu8%3D&
> amp;reserved=3D0
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> https://eur01.safelinks.protection.outlook.com/?url=3Dftp%3A%2F%2Fftp.iet=
f.
> org%2Finternet-
> drafts%2F&amp;data=3D04%7C01%7Chendrik.brockhaus%40siemens.com%7C
> 33f72021ce2446610b6a08d8bd5df512%7C38ae3bcd95794fd4addab42e1495
> d55a%7C1%7C0%7C637467558529026085%7CUnknown%7CTWFpbGZsb3d8e
> yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %7C1000&amp;sdata=3DKpiHghtdehyWTEpEaehk%2Bus0y7cRKQxADq7xBKPMx
> 9E%3D&amp;reserved=3D0
>=20
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fspasm&amp;data=3D04%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C33f72021ce2446610b6a08d8bd5df512%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637467558529026085%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> iI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3D62sdFOf4HxlerYX%2BDl
> O7ibsG3EEDxfA27mkCGoWrc78%3D&amp;reserved=3D0


From nobody Thu Jan 21 08:58:56 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2533A12D6 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 08:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wr935Xwvde4h for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 08:58:53 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF2243A12D4 for <spasm@ietf.org>; Thu, 21 Jan 2021 08:58:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 326D9300B44 for <spasm@ietf.org>; Thu, 21 Jan 2021 11:58:51 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id knELuZVXH-hL for <spasm@ietf.org>; Thu, 21 Jan 2021 11:58:50 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 2F3CB300512 for <spasm@ietf.org>; Thu, 21 Jan 2021 11:58:50 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Thu, 21 Jan 2021 11:58:51 -0500
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com>
To: spasm@ietf.org
In-Reply-To: <161115903621.21831.6292824907492428494@ietfa.amsl.com>
Message-Id: <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/KUxXaRr-s395iEzylHY3rmObqHg>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 16:58:55 -0000

Hendrik:

Wow, that is a lot of key agreement algorithm alternatives. Do we really =
need all of them?  Can we drop any?

Russ


> On Jan 20, 2021, at 11:10 AM, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Limited Additional Mechanisms for =
PKIX and SMIME WG of the IETF.
>=20
>        Title           : CMP Algorithms
>        Authors         : Hendrik Brockhaus
>                          Hans Aschauer
>                          Mike Ounsworth
>                          Serge Mister
> 	Filename        : draft-ietf-lamps-cmp-algorithms-02.txt
> 	Pages           : 27
> 	Date            : 2021-01-20
>=20
> Abstract:
>   This document describes the conventions for using concrete
>   cryptographic algorithms with the Certificate Management Protocol
>   (CMP).  CMP is used to enroll and further manage the lifecycle of
>   X.509 certificates.
>=20


From nobody Thu Jan 21 10:23:49 2021
Return-Path: <rsalz@akamai.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 100963A03F8 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 10:23:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xheZdgztko8k for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 10:23:47 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2140D3A03F2 for <spasm@ietf.org>; Thu, 21 Jan 2021 10:23:47 -0800 (PST)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10LIDo7O005283; Thu, 21 Jan 2021 18:23:46 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=go38T3cQ0NbatzuM6ShHgRWGJ+hpvqu/jCgTQZj8d14=; b=JuDVafVFd7XH3s49/Ez2nx9sw48nXFaA/v9iRQrvUKrqVvu7HWeZdF+IcYjvymgDtdsB rVYtTXPucw+XmuaRthu0ntrI0i+PcMNGA6VfVZThrntLVMXe2xJkUGSwv+O7jO3WdnGk f06FWU48Aa8tNrxNTHyhLAfIl4s0IOis20OREdNQIEabAA7QvvlnZEZH6laF64cCM8hb hefXAOgPPV+wgtQUk4z6b2DCd5vNpkcPFhUjJWU408DhwJ6BW9Fpw+h2KFMSKja5yimF oLwiDf1SLanBjj2U6WuSHh6WqIOMUo2rGd9gF1Ryg7tvJLted+Ef4RcCuPssJ/KZYmXF ww== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 3668rjugm8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Jan 2021 18:23:46 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 10LIKJZ1012740; Thu, 21 Jan 2021 13:23:45 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint2.akamai.com with ESMTP id 3669kwnh8y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 21 Jan 2021 13:23:45 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 21 Jan 2021 13:23:44 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Thu, 21 Jan 2021 13:23:44 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bOuRd8Wg6qTUuzRaLVMhTx16oyoqaA///D5gA=
Date: Thu, 21 Jan 2021 18:23:44 +0000
Message-ID: <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com>
In-Reply-To: <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21011103
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <740CC7EDDD64F5438255CF1A653295A8@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-21_09:2021-01-21, 2021-01-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 spamscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 mlxlogscore=699 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101210094
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-21_09:2021-01-21, 2021-01-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 spamscore=0 malwarescore=0 phishscore=0 mlxlogscore=604 suspectscore=0 adultscore=0 mlxscore=0 clxscore=1015 lowpriorityscore=0 priorityscore=1501 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101210094
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.19) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint2
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/GKmx5EC03MUVOrZhRM5tg8YPzSA>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 18:23:48 -0000

PiAgICBXb3csIHRoYXQgaXMgYSBsb3Qgb2Yga2V5IGFncmVlbWVudCBhbGdvcml0aG0gYWx0ZXJu
YXRpdmVzLiBEbyB3ZSByZWFsbHkgbmVlZCBhbGwgb2YgdGhlbT8gIENhbiB3ZSBkcm9wIGFueT8N
Cg0KSXQncyBhIGxvdCBvZiAqZXZlcnl0aGluZyogIFdpdGggbm8gZ3VpZGFuY2Ugb24gd2hhdCdz
IGltcG9ydGFudC4NCg0KDQo=


From nobody Thu Jan 21 10:53:10 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 670D03A0977 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 10:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KVqzgpQwTtLh for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 10:53:07 -0800 (PST)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80050.outbound.protection.outlook.com [40.107.8.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53EF83A094E for <spasm@ietf.org>; Thu, 21 Jan 2021 10:53:06 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=juGfaYFMKjWJ0XvtX3uGyJh+eRQyJ+LMxdQihQkHtblbd//VBgCvseutk4Jv1u21fh/qEkV5bUJgO0HLSHbkIVb41B62eJep/4SHi1i3OgRGX5CZLSM0frsHf05n43obmSr+PjlpxBbswo+Ur9/vjYplBxpUNaT9KwZ8N6lM48fUSRFj/4Kkr59nLkQgqNpTL52J4nCsfr1AkEkGgfcvi1QGEb2oFlBEiIecmd+XQhFSkoVTntZkF/LSmDpCrW72iquDYweZ5yE9lEmo3Cvm1TceGPxGqkOIM7MoI/qjvUySHuRHJGh8HJ9O6tDSkSEvdhJuVEdC5lNVgJpHsgJROw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XqxRwpyEDJY0YmCYDSRHcXQkIkyKo4Bj4VRlMb5w2OU=; b=ha9eEzID6Fqrcjule0CxvPPZUs/00EEVGnBYN7BOz8sjzw5F7ph3KCX0j+JZhKz3peeE8sSrhV8U+R31zL7d93R4NzRph69VlhULuHd2fy/CdA+p/ucm+4y+WTUsI4jpXklsP0e4NtGDbUFFyIXARkyLhHUM5KvpdI9Lpf4zuuEPuAaIw5cFdvzbp44wOEjvuTvFsJ6ay2x1DF/13zxTtjdnFWBCI7ut87sQ2Fh2uR9UqYc0yJ7NUfk7o58TIo0fgTFFVTb1Ub54j9Teg8lLR1q+YaXhBhoj0I92solbdT4vL8cNX0LaBAPBZSzNLcnSvkJd+O7ZTTENfe3jwE7H8w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XqxRwpyEDJY0YmCYDSRHcXQkIkyKo4Bj4VRlMb5w2OU=; b=M15ZS17dfMK9uzBeEqB0Epj9Xbro7Er7BKQC+kNRYk/fq5QUz9zUz88amMd0NNAjeaZWB+i8B2hoySRW4NOaEC57ASE2YTGEn8N36/ryzplPrVgRMBPN5EZYXlMToVEgYkPZ9Pc9UsXKweIfpmIW7KGr2BLlJ3FBrB1bRRijkPw=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM9PR10MB4371.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:20b:273::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10; Thu, 21 Jan 2021 18:53:04 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1%3]) with mapi id 15.20.3784.013; Thu, 21 Jan 2021 18:53:04 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bT5wngqywmbE6XWcKJbZgLXqoyTtWAgAAXtwCAAAga0A==
Date: Thu, 21 Jan 2021 18:53:04 +0000
Message-ID: <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com>
In-Reply-To: <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none; dmarc.ietf.org; dmarc=none action=none header.from=siemens.com; 
x-originating-ip: [165.225.200.151]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: e27a017e-0a44-4776-3cdd-08d8be3dc8e5
x-ms-traffictypediagnostic: AM9PR10MB4371:
x-microsoft-antispam-prvs: <AM9PR10MB43717321DF7B329D802F2CD9FEA10@AM9PR10MB4371.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:3173;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: p4Trwoa/CjHPYrUdCGLa5naX6kQ4xhKJ3LOAVKBGY7n6BSMufHO4z/NNjhZJqFLAsbyJswqwoKGFDJCr3YsbSfWCVKCDbFqEDcqCy37xVFj2HB+TlZqovLDN5UqaZi1t9Vg1g0ndObkefkG9AAwgInjPYhyJGMdEQ2i1nZkSJL9Tle+BwPJpoys42n5Iw6N1CElbtjjf37QrJSRqDkUvKKylfKARGDdUhClefIyO6uw9Dz9ypA4IXc8wf3Buqy6emmo9LQqBh9Wrl0XfNPFk57nEQ2sQSJsSmhWSokusQRG7POVo0X7Y6fFjZM12WX9hJ5ERdAN2R5Up/CGRpuah4SOHiNqhfc/L7+hSENGdp4oN7DLHVBsZ+KxE6LpP28IB06YYZkRdvyYUpcLbfu2HutWa/7WZUJLBjaJGyKLP5P/1q1fosYnod7lJAoHbNwERJ7VdAk7i+HideSG51ZMo+w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(396003)(136003)(376002)(39850400004)(346002)(366004)(52536014)(76116006)(66574015)(4744005)(26005)(7696005)(55016002)(6506007)(966005)(110136005)(55236004)(186003)(33656002)(86362001)(9686003)(66556008)(66446008)(8936002)(5660300002)(64756008)(66946007)(2906002)(71200400001)(316002)(478600001)(45080400002)(66476007)(8676002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?CwJ1/Up01jLCGZQEuVTleDM9ZjyPUXT+IK6EBJf4j6703lFsq7THH6ndm/?= =?iso-8859-1?Q?q27IrU8/dXKUwSPoTqTuJhFTneNSjFZ3dPwhDgnlNmJrUPv2mNTtw/P7Xl?= =?iso-8859-1?Q?85FagDtcV3f46ECHolhkEUz07Q75QJqEDQprIUiisc2CR9Qfrq6efeOtJR?= =?iso-8859-1?Q?iQ92UIg0x5otJxaM8GajTBA51bVik6DBPDvkUn+BGR+qRvYlKz9l3G3/GG?= =?iso-8859-1?Q?UbRpOsGd5rw/KbLDj8hNUCYr5eIsQBV2qThL5ZK0uHovaROgSVWVEG7Ab1?= =?iso-8859-1?Q?p0R8a/sZlwkQAi77SRPOiZfLmxUEXbB5hw0CdlQQn85byU+jtkHQ60OiZf?= =?iso-8859-1?Q?AS05iEB4V9R6HE/bpF2UVm/No+aYggSQ7egwZTNHfauRUrb8BPHC5alvI5?= =?iso-8859-1?Q?qY9QwCVX1kOf04foUfwuWh7/zHQ3Po+XvE/RhFYbWWOS1+mJ1ET6NpzcXP?= =?iso-8859-1?Q?SGRMy8adVS1HVR1psuSUtR/L9ytYOlZXIJ+eOO9cr9Q+X9lZV20ejVc7vv?= =?iso-8859-1?Q?UXUYoSZ2zqrldBP8rD+mS04GmERBQMtq137EGxwEqY2tiRKOjXMIHt9JIN?= =?iso-8859-1?Q?uut3tKdYn3IZqpwyAAQGCELzCBbahshv4K+iXtiPxlGgHCXAEmOMMSUAMI?= =?iso-8859-1?Q?SMi2GkgqIQpu+XCsMroQ4CceUtJTU9+r6bFTpfDIbGbXMTY8pTzKSXbSLv?= =?iso-8859-1?Q?Kx/r4BwYenLNEkx8Tsq4tZ5lay4/kRB91mN4NzetVIqThNQq5ZoFFuqNCl?= =?iso-8859-1?Q?mDAbfPw1K9NmQ1XavlTBISus2sY9cG4znpaxkYjewgDdOvuX0jIILqVeJ6?= =?iso-8859-1?Q?Lb/CCyTnhIvu2IPVNiAj8uZjw67mY6MmbkgzoiUDIE5LsBLZRzr7khxbfU?= =?iso-8859-1?Q?Kd7iHVt+sy71IzmBu1j0bgYC7frSEnBCgxotuiqLZUobnZS3bej6kB017y?= =?iso-8859-1?Q?Z9SkbLpsDBaRXH/E1KW+TJ7KlkJ+JePQaoOf6FMGi4zhN54jAfjd8KobL2?= =?iso-8859-1?Q?8dODr1vqEyFr9Ah+fzRjN1zhBkwv/FU8Do1Udp?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: e27a017e-0a44-4776-3cdd-08d8be3dc8e5
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jan 2021 18:53:04.5154 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vUyY9Z8X9OE1rVKR6TlkEYvCS+yEIibUtiuKqnwhjhL9u8sRvJZs6AaFBOQR5y254jNA1zTYnYgO+t4sEdwJWM56i6ddN/sfNWam/6+9ztM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM9PR10MB4371
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/t2dHkoY7BXd9KzFgivk1dEU9hzk>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 18:53:09 -0000

The guidance is to come in the Appendix A

Hendrik

> -----Urspr=FCngliche Nachricht-----
> Von: Spasm <spasm-bounces@ietf.org> Im Auftrag von Salz, Rich
>=20
> >    Wow, that is a lot of key agreement algorithm alternatives. Do we re=
ally
> need all of them?  Can we drop any?
>=20
> It's a lot of *everything*  With no guidance on what's important.
>=20
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww
> .ietf.org%2Fmailman%2Flistinfo%2Fspasm&amp;data=3D04%7C01%7Chendrik.
> brockhaus%40siemens.com%7C31191d8b952c416a5e1508d8be39b7dd%7C38
> ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637468502413902057%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DWqHe0VxkVbuuLyd6mck
> OpkKKTnq%2BrSr9uymRkiJ3TFc%3D&amp;reserved=3D0


From nobody Thu Jan 21 10:54:13 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 969643A097E for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 10:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id InYMmrRWicm5 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 10:54:11 -0800 (PST)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20084.outbound.protection.outlook.com [40.107.2.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B72343A093D for <spasm@ietf.org>; Thu, 21 Jan 2021 10:54:10 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PSOpMFA4kKhNt/HNfHZndlBEbFegcPcFe6NzaQKHywoGO1PnKdS8ckeomVpYZhbRp2s1s9TQsgalvzxcmyQ74H952JnKgN7OHIPfXhOc1E2xsJRYPJSawPrm5bLdKAoaA3UufAxn3oAkEX9X+FxxU+1KDSIwM2A03k8ncP+YKp8kO/Dee3ZIQVp4ltjSgBS2BKC1AkxHNmMVl/EC7ZUUkYyErV7O6ZtzpOsvqx9LCDW+bDJnsLZHG5Vt6XwAGGfKJgQH0L5AVTm0ptQG+k9sm6gEkeg12d+8/u/O2kVuYqj/REtSHVZALqouaVz2HZNST4jGMH6z+oUmE2PxPK1Ahg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=08K4jN/HKT6gBTrpln3j6mKvp04ktZULlPXikmm3ueI=; b=jBBnd4BLfbaEayv2OQ9eEX5sj5cdDVLgRKUVxv6FW5mzXeqaQgfdSHRhGyh977Jo80dMaH0iu5KrcCzsMa5kF3shUal0KCajnrl6Jof9qkzR08p2Y0wzmTvCklHKaj16QXlYyRLUakX2DwoffUmW2s9gPqm5cTx9cTEhMYOR9feVQaaBZuEEOAd96qnmhSWiiaqDXs1OSCgcDQKPGsGoXVKAr9rQoUSREqBiByYW4NYVemIx8VMx9JZ2SLnzVxmFQ1JkwyCPxWLkBJkApH6ThLCJVEiVPkrBO9JjN78eEhyAxFW5LeMheUE/A+6q4QxFamJWbqJn2bT/iBZ9WnK1Tg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=08K4jN/HKT6gBTrpln3j6mKvp04ktZULlPXikmm3ueI=; b=Rtg1IgrY9DFQbXcpkCh60j7NmHzIy1W8CC6x94Ofd//Re82x+X9KnUt5NONmX/tRB59Jmt7CogCDgkPop8rhkVqUAqB87lz4bc4yjo/dCPbm31TJAuzhnazcgqnjK8ooEO0Z2aMXoaCR3gdtTyi8BXagoZRfuzA8asabBjVk3vs=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM0PR10MB2737.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:124::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.12; Thu, 21 Jan 2021 18:54:07 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1%3]) with mapi id 15.20.3784.013; Thu, 21 Jan 2021 18:54:07 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bT5wngqywmbE6XWcKJbZgLXqoyTtWAgAAf+qA=
Date: Thu, 21 Jan 2021 18:54:07 +0000
Message-ID: <AM0PR10MB2418352793349C0C5C6A850CFEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com>
In-Reply-To: <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.151]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 5cbb6814-c75f-480b-8bb6-08d8be3dee9c
x-ms-traffictypediagnostic: AM0PR10MB2737:
x-microsoft-antispam-prvs: <AM0PR10MB2737008C4F6574BD8BCD182CFEA10@AM0PR10MB2737.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:2582;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: wXs1Ot0kNtucSs+K9/T2ApQRdmf12mW1JhZz7P/3LWmr4noZ13W4wWqWx+sNw7fKL0WoMDviLZaxwdk50BykQ27BE2Tkw05OZveY6PBIc0JJOwSTAAwP3W3EDaGwZ0EGL6BUYnzlJdgzWqhklH735BEJTIyhNaiyZUobDcToFR9CoDZwnpA4PV514OGWCepcLs0IrjU9H4SVA3tXEqa+nrpNvOvH/LwTQkc7kPImOIq+f9vwtNtnzHRfy6prJVw+pgMLMgvT7GvxdrwQRiNPIHhIosuVTLV03asalIiZDbIOi8ueVwYNl9juXAxq1Q6jq36HsOX3rF3Ya4UFbvfR51NGb+qxv/szWBfPRne4hNiKWGj+PSMqbt/iesib9InUmK9X21MBrY1vmdggJnLlc3b/PB4xEup4wOez2gIXPIuj39ONEmQQC4XvuSr4PDAPU5zOaP4ut0OYIYjzLYw6fw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(396003)(136003)(376002)(366004)(39850400004)(346002)(33656002)(66476007)(66446008)(83380400001)(8936002)(66946007)(66556008)(8676002)(64756008)(316002)(55236004)(55016002)(110136005)(66574015)(53546011)(86362001)(76116006)(52536014)(6506007)(26005)(71200400001)(9686003)(2906002)(7696005)(478600001)(186003)(5660300002)(966005)(45080400002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?XMwWatuHUuG/mn4tRZKkOfSE/e5H65aM+kxn+fA06bGBqIMr2jWbRmWAAc?= =?iso-8859-1?Q?uHFLYrR+VaFIP0qIQvARUuwFHQkAt8ZVzANPdtaselZ2LbTK58GI+Q/mCZ?= =?iso-8859-1?Q?d7XgvvyQ7HH+XhXyT5WJGY7hBn8pUX/8p8YLqWNMujWQVrxq02J/zxDzO0?= =?iso-8859-1?Q?3Vifj2FpNn8021ii4BAVOWZQJ8P2qkQW6kiVIvUSAVHtD5poFC20kY5+Gu?= =?iso-8859-1?Q?5ULGNIa6Il/JTGE4JTEnkd9nJkvLWGRfIGfYWkeeY9c0XHUN9+3zo0+58i?= =?iso-8859-1?Q?VkqH2VMwB+uM2QGm7YZ2qNtFUs0I4odTjI/O2MrGDyEOCRAsOnCEQ41BoU?= =?iso-8859-1?Q?J2Ap36y3eaERYiADr/H23ADvdLnM0eQA2ZEmlY/8xCUwVsZv93TFtReSgw?= =?iso-8859-1?Q?LHRCafD/dNwhxqOLnJWtGWel0M63zg5Bjg/nv/90nFa9Ramgv6aSxCP+8p?= =?iso-8859-1?Q?zdwvaZewW2v6/MyT/nlHMMHFvrYpfgCMjuTWzikxRy4lCRNgf+Ma2uwE8r?= =?iso-8859-1?Q?gw3Ib8cW7awH0w9fK8BrEssZBSkM6GEEwoGt3MQKz589KuKRU6e/KA8YzG?= =?iso-8859-1?Q?2J7NTYORsIMgz/Jkx/FTFQmSSKmR1cwyL2ZLCD+4DnLpEHek0vkMZWBfmi?= =?iso-8859-1?Q?HRjw9kZCgWUfKrLi2Fl6HoUBHN4r12PI7g07s4uAuxumWFMpKMKYOkdHkk?= =?iso-8859-1?Q?mUM5gVq0yPcV1y4RdsFRB8DmH4GxyaZ/A8w8anBU1w9B4bY3Y05IhyaQfa?= =?iso-8859-1?Q?dAfr6qCAu+0NuBaFIj65ZSK22qq7T+lYJXmVdKy6C/+yrQiv/HPbIVn/lT?= =?iso-8859-1?Q?vAcHrFGEi9hkugJAtDY81keBxdPzyKhdtQmY3M6BJtjpz0PDu3yu85qQgN?= =?iso-8859-1?Q?HCWpySnt7D9RsZdt8itojP2Q4Aj/zFY3pwwRYGDaWVfGZwoB+5Rnx16E/E?= =?iso-8859-1?Q?GZZFHKQe/I4J+A5gEJT9KK6YEpwKTsphBV3bVvAMY3hS9beA+NLFgH+r+r?= =?iso-8859-1?Q?bD39Le/iqTPNr8/lPAZiFNbfrPtMc+Og1B2SRd?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 5cbb6814-c75f-480b-8bb6-08d8be3dee9c
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jan 2021 18:54:07.7425 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: IxtAi+6I3SKRPDfZQz+ZnXwwa6uHg50Sz2mUvrNDARnrfPDnKP/+Fob9Dmdp7uOHicL5lCUe6uymUKbP1SzxE31BS10WlCRvSOd2/RQzIu4=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR10MB2737
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/8fP-cK2VBEY0T41K4nBmB2hz2TI>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 18:54:13 -0000

What would you suggest to drop?

Hendrik

> -----Urspr=FCngliche Nachricht-----
> Von: Spasm <spasm-bounces@ietf.org> Im Auftrag von Russ Housley
>=20
> Hendrik:
>=20
> Wow, that is a lot of key agreement algorithm alternatives. Do we really =
need
> all of them?  Can we drop any?
>=20
> Russ
>=20
>=20
> > On Jan 20, 2021, at 11:10 AM, internet-drafts@ietf.org wrote:
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Limited Additional Mechanisms for PKIX=
 and
> SMIME WG of the IETF.
> >
> >        Title           : CMP Algorithms
> >        Authors         : Hendrik Brockhaus
> >                          Hans Aschauer
> >                          Mike Ounsworth
> >                          Serge Mister
> > 	Filename        : draft-ietf-lamps-cmp-algorithms-02.txt
> > 	Pages           : 27
> > 	Date            : 2021-01-20
> >
> > Abstract:
> >   This document describes the conventions for using concrete
> >   cryptographic algorithms with the Certificate Management Protocol
> >   (CMP).  CMP is used to enroll and further manage the lifecycle of
> >   X.509 certificates.
> >
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww
> .ietf.org%2Fmailman%2Flistinfo%2Fspasm&amp;data=3D04%7C01%7Chendrik.
> brockhaus%40siemens.com%7Ceb613e47461a441631f208d8be2ddc95%7C38
> ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637468451471439269%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=3DWgDQTSsFwQKsqwA1Cs
> BDegLvXHV1Py1xwyCPFOwt1ME%3D&amp;reserved=3D0


From nobody Thu Jan 21 10:59:04 2021
Return-Path: <rsalz@akamai.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74F9A3A09A8 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 10:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HOaLQaTp67sI for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 10:59:00 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B06753A0990 for <spasm@ietf.org>; Thu, 21 Jan 2021 10:58:55 -0800 (PST)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10LIwfGQ016503; Thu, 21 Jan 2021 18:58:54 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=Ch0B0zcueJgRA8s9wom5Dt0jUWTgYNupeOwkBk4NjrI=; b=WHLa7gss9+DDvACb30oLkmnaicsXE5uK1ftwRP4ZY/hRggFL1cQf8pD/R2Pjf/4N6oCO d6CqzV34qkljTBL+vxT0x5W1fMxYVANSvhV2mqDgPz61C16Vj+yyrjRNHXiKCpcPve92 pJCGrvkphnTI+/FqyuFnDU45hlOskbzqw3FK5XiGPlS5MLEeBKk28BzYazid+OCzpGxj x8q7FMTCQ+4P+ltu+82RwKKUG/abEmF1s4q6BucdP1Vr5uW8StaJ9yOjgrvw7Wnsq3Q7 uI3mbXs0WdSfZXYUtO3VycjcIYVpEe810TolkgWEjAbJbEXqAgLMVcyo3ih93/DYccpr UQ== 
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 3668s0k17h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Jan 2021 18:58:54 +0000
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 10LIfhiN031792; Thu, 21 Jan 2021 13:58:54 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint6.akamai.com with ESMTP id 3669dydqf8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 21 Jan 2021 13:58:53 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 21 Jan 2021 13:58:53 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Thu, 21 Jan 2021 13:58:53 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bOuRd8Wg6qTUuzRaLVMhTx16oyoqaA///D5gCAAFwEAP//rX+A
Date: Thu, 21 Jan 2021 18:58:52 +0000
Message-ID: <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com> <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21011103
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D59DF5B44EBAE74AB9394E581B0DCECE@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-21_09:2021-01-21, 2021-01-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 adultscore=0 malwarescore=0 spamscore=0 mlxlogscore=727 phishscore=0 suspectscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101210095
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-21_10:2021-01-21, 2021-01-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 priorityscore=1501 mlxscore=0 malwarescore=0 mlxlogscore=642 lowpriorityscore=0 bulkscore=0 suspectscore=0 adultscore=0 phishscore=0 clxscore=1011 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101210096
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.61) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint6
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/mU3IN0oO9wbBTyoLGZShkcOo-14>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 18:59:03 -0000

PiAgICBUaGUgZ3VpZGFuY2UgaXMgdG8gY29tZSBpbiB0aGUgQXBwZW5kaXggQQ0KDQpPa2F5LiAg
TWF5YmUgbmV4dCBkcmFmdCBjb3VsZCBoYXZlIGEgc2tlbGV0b24gQXBwZW5kaXggdGhhdCBqdXN0
IHNhaWQgd2hhdCBpdCB3aWxsIGJlIHdoZW4gZG9uZS4NCg0KSSBhbnRpY2lwYXRlIG11Y2ggYmlr
ZXNoZWRkaW5nIHRoZXJlLg0KDQpDTVAgaXMgd2hhdCBJIGNvbnNpZGVyICJvbGQgc2Nob29sIiB3
aGVyZSBldmVyeSBhbGdvcml0aG0gaXMgYWxsb3dlZC4gIEtpbmRhIGxpa2UgVExTIGVzcGVjaWFs
bHkgZm9yIDEuMSwgYnV0IGNlcnRhaW5seSBiZWZvcmUgMS4zDQoNCk1heWJlIHdlIGNhbiBtYWtl
IGl0ICJuZXcgc2Nob29sIiBhbmQganVzdCBwaWNrIGEgZmV3PyAgRm9yIGV4YW1wbGUsIHdoYXQn
cyBpbiBUTFMgMS4zIHBsdXMgb25lIG9yIHR3by4NCg0KDQo=


From nobody Thu Jan 21 11:10:33 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 364A33A0A21 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 11:10:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6rmfkdHXG_l3 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 11:10:26 -0800 (PST)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80043.outbound.protection.outlook.com [40.107.8.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83F2F3A0A0B for <spasm@ietf.org>; Thu, 21 Jan 2021 11:10:25 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YBRHYHJkzNhi/gr+jj8WXfAOxusZRGsUI1rIOMcZc50HAGHuccxEecNxuJ5n3zB5ShHuV6fnKfEkFgnxKTi/Frw304rwXZYW063mcf7mX4pGKQmise1XBvMWsleUIHLJ2enxM0lnb1SVhM/UYmsZtQCr72VuPYFr3+nKxZsruuNZNUc/51AFEg3QQal11d69lE+EJcBiWwN0M4O80HeX/vzEoXpFxjq7KmoL1vMbMM7btB7BUNUKdhnHq6iFrw8/5BtDx7deDPSd57VoCddeMSZOHa9bFpWEYztSS1wJeob1eR5SuACbjnUFrPf39wdAiv/TlRtoDbz+LkzyV6Kapw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MbhEeuJXNsezZodl3aPzYLn6TdNGD60+e76kXhpQhq4=; b=iDuQU/n1Bktlr2MMbRIhoRGq7KvwrF2b3jSpjQ1ZOUoqh9LtlVqg3oXU6mLvxtIxd3Yz8H/cLAYLUJjcti7qKPv5uOJuASCuZQaxquJDt3qhdfEdIo2hESVOFmGHa+cPsurQqt/PtSO+oNukGB9vDz/sX6tkEbYcv00DKlsESckQCkYtxe1cdfetpAnxFFqPkFLk019FPImwHMJe1/jzxgo7lOwuFjMy0OmIraLjMtyFle5+h9Wx8wfv/+cAvXyP4q0K6mXinZ7rXI+XVB5tm3wrsU+8B7WCW91gVR10MTJ0ZpqjPdz5EOJMgQIBQwhBp+kwl3L67bVWsRV9/cAi7w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MbhEeuJXNsezZodl3aPzYLn6TdNGD60+e76kXhpQhq4=; b=ODHK7AhZeHznXlctzeB5g7T/kqEKsTWy0h7XjfUGffojaqu7iV4fjjS2ITLYc2ZYqOZj+A2icdXwlYwg3m3NU7zJS16X9MFvvaQT2OprIFc2SMtxEpQxDNBpIXC5LbKIoc1R+DqCEHXkPU1eBJuZed+iHluCMySbvkgzs53LBj8=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM8PR10MB4290.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:20b:1e4::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.12; Thu, 21 Jan 2021 19:10:23 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1%3]) with mapi id 15.20.3784.013; Thu, 21 Jan 2021 19:10:23 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: "Salz, Rich" <rsalz@akamai.com>, Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bT5wngqywmbE6XWcKJbZgLXqoyTtWAgAAXtwCAAAga0IAAAbcAgAAA80A=
Date: Thu, 21 Jan 2021 19:10:23 +0000
Message-ID: <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com> <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com>
In-Reply-To: <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: akamai.com; dkim=none (message not signed) header.d=none;akamai.com; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.151]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: c4a21b7c-b654-4c21-87c3-08d8be40345e
x-ms-traffictypediagnostic: AM8PR10MB4290:
x-microsoft-antispam-prvs: <AM8PR10MB42909F28FAE00FAC5A14A8E8FEA10@AM8PR10MB4290.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: oZy8bOXgmRVyFq7wBp7Veao/Rtt5i/YDBe3GRl8NaQ7wzfTnzNf+8Dvx0Ig2ofaCeXnGxhSck9zM/SxWu59QaMd2yUETZ6Ftss0XOM26+zCH93t9QXlEI4EpvGZAgjZjookxn9CZWAlNLnyWhs7oU+r+4ws8Sf4gElFoLeiLH1TOMUnQb+48Bgv/J8KH7w974bh+FUdhTnH2mr+LLWrcng69gDqjbIUmt6emuuApYCEZXnEAiWzCE07+TQ8FycVr4AFmwnZ7R8q1KVJYslAZixFql3dJ2hR+rsoh6cHnUtAmOEXTIjQ/GZa140ML+hi8/arHkJCgz8HM84UCubDmPIjkK60tRV0VBMdF4ErDEta2rnWCVfYMJlKNsGorxdEnnSptLqKNZw9K32AcAQV/bQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(376002)(136003)(39860400002)(366004)(346002)(396003)(5660300002)(186003)(66446008)(316002)(52536014)(7696005)(66946007)(71200400001)(83380400001)(76116006)(66556008)(64756008)(66476007)(55236004)(26005)(6506007)(110136005)(2906002)(9686003)(66574015)(33656002)(8936002)(55016002)(8676002)(478600001)(86362001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?c3hxeGsyYndQSzlOcWhUOEVoWTMvKzdpb3YwSFFTNUdDS1NjUzVCa1JyemFT?= =?utf-8?B?cEJrYlJnNXJrbkg0b0tvWTFOclJhOEV4cUtRaWZCTU5zK0NWU1RQa2xlWnRQ?= =?utf-8?B?R1FieFNxUjhVUE9VLzc1dGxuME5oOHpLb3FGSDA1YUJvLzAyM2h2Y0R1b2tC?= =?utf-8?B?VzAzdDhiYU1EY1pmZkV5MlB1WFJHRzltRHB1NHF3TUluMncxSzY3UmFGR3Jw?= =?utf-8?B?Lyt0Q2ZSUGFuOFNVZGNDcExHZzFDY1ZSc1U5d2d1aHBPTlZVS3htbDdQSGNX?= =?utf-8?B?Y0hTWWRrVHJ6UnlRUUdHenAvdWN4VEJ1eWZvL2UvZ1h3UmwzQ1B4dUZ3UGVI?= =?utf-8?B?Q1hNSWhicnRvdkJuR1p6dU8yQ1JGc0pjOWdsNkhOWFFYcHliYmRlTlQ2bEQx?= =?utf-8?B?cFhsYUNHM25PdHVJSTFuNExIWUp4NUZHRVFUL1JudVFkSmd4RDREUDlxRGtq?= =?utf-8?B?UDBrVkpOQWtwdzZKNUtNNzJuRm9QenE0aU05R0EvNTg3QjlKejlkTmdrZmVy?= =?utf-8?B?N09NZWhSUkxjT1BxRUtLNmtNRjgxZXBxQ0kxQXIvd3BtWkhnZHI1enJvSTI0?= =?utf-8?B?ZEw2aHkvZHdTQ1FUeXFQYS8yMythTGZKeVBMWTN1NU9aYmZGNTk5MW05WFhC?= =?utf-8?B?NlZOQVZkZWNhNzRra3RtWlJLMGlHL1VxcVJkS3NiMXk2aGw3RFd0Q2VLWS9O?= =?utf-8?B?L2s2NTdZRzM1T2ZseFpzenR2OWwyUFdKQ05URDJXak1DcXFySVM0MWtkejQ0?= =?utf-8?B?eFExY0xTYTBmZVpOenhlWkdsNHZrU1kvTmI3THRCbjN5UUlIK2w3RnQyYTNs?= =?utf-8?B?bm5OeE04VUVDSW8rVzY3NXZ5OGhCeDdUSzlVcGh2dWpYeHg0MFVTUDlJbzg3?= =?utf-8?B?WU1Fbk5Jamo2dytEc0szbkx1RWJTYmFBYUVEam1WVjdoMXJCbFp1ejhnd1VP?= =?utf-8?B?NHE0L0xjNGp4eW9nTmN3eC9kN3BUcVRoOWdxaHRkNlY4WjF4YkdPSnlvOFAr?= =?utf-8?B?ZlJwTElUL1lMbkdjZllXTnBxU2pKY1dIU1FMYjZuY2V2UklqSGtjYTMzQVZL?= =?utf-8?B?UmV4YjI5QWI3akx4STlPM1RhZmdpQnNScmZWL2pxL01OU1MyWHBUOFlqSUk4?= =?utf-8?B?TGpHdW1ZTHdDU1pWZGNLNHhtTWJBZFFNRmx5TkQ5bjl3c3U3d09XdlBiK1Ro?= =?utf-8?B?UkY4dXhOK1Nkck5Nc2hCZWZaWXpVUG1OdkhXSHlWVE5pbmNIbnlYRE9HTWU0?= =?utf-8?B?cDVyRlVlOEtpZVF2ZFdNbVNQT1o2emZDSzR5ZUxkWkNyeVk4cUthNG1zWEEz?= =?utf-8?Q?TFlMHMGHmO6O35nOFQ13LNFJd3An/4jQ1s?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: c4a21b7c-b654-4c21-87c3-08d8be40345e
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jan 2021 19:10:23.8210 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qAcPeXA0DWg6Y0GZD+cbsTU0quoS9dYYHyBUNqfyL55k2UObQR+RM7Y3FQThtjYxt5VhVX2v+LjboMNV+HYlNHyiDTBkP/vto+2DAuG1HtU=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR10MB4290
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/AsJ07adhyjHBMogoLMWNL88HLQk>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 19:10:28 -0000

U29ycnksIEkgd2FudGVkIHRvIHNheSwgdGhhdCB0aGVyZSBpcyBhbHJlYWR5IGd1aWRhbmNlIGlu
IEFwcGVuZGl4IEEuIFRoZXJlIGlzIGFsc28gYW4gVXBkYXRlIHRvIFJGQzQyMTAgQXBwZW5kaXgg
RC4yIGFuZCBhbiBBbGdvcml0aG0gUHJvZmlsZSBmb3IgdGhlIExpZ2h0d2VpZ2h0IENNUC4NCkFu
eSBmZWVkYmFjayBhbmQgY29uY3JldGUgc3VnZ2VzdGlvbnMgdG8gdGhlc2VzIGFsZ29yaXRobSBw
cm9maWxlcyBpcyB2ZXJ5IHdlbGNvbWUuIEkgbGlrZSB0aGUgaWRlYSB0byBhbGlnbiB0byBhbGdv
cml0aG1zIHN1cHBvcnRlZCBieSBUTFMgMS4zLg0KDQpCdXQgeW91IGFyZSByaWdodCwgd2hlbiBz
dXBwb3J0aW5nIEVudmVsb3BlZERhdGEsIGUuZy4sIGZvciBjZW50cmFsIGtleSBnZW5lcmF0aW9u
LCBpdCByZWFsbHkgZ2V0cyBjb21wbGV4LiBCdXQgdGhpcyBpcyBub3QgZHVlIHRvIENNUCBidXQg
dG8gdGhlIGNvbXBsZXhpdHkgb2Yga2V5IHRyYW5zcG9ydCBpbiBFbnZlbG9wZWREYXRhLg0KRm9y
IHRoZSBMaWdodHdlaWdodCBDTVAgUHJvZmlsZSB0aGUgY2VudHJhbCBrZXkgZ2VuZXJhdGlvbiBp
cyBvcHRpb25hbCBhbmQgb25lIGNvdWxkIHNraXAgU2VjdGlvbiA0IChhcGFydCBmcm9tIFBCS0RG
MiwgdGhhdCBpcyBuZWVkZWQgZm9yIFBCTUFDMSBpbiBTZWN0aW9uIDYpIGFuZCA1IGNvbXBsZXRl
bHkuDQoNCkhlbmRyaWsNCg0KPiAtLS0tLVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tDQo+
IFZvbjogU2FseiwgUmljaCA8cnNhbHpAYWthbWFpLmNvbT4NCj4gR2VzZW5kZXQ6IERvbm5lcnN0
YWcsIDIxLiBKYW51YXIgMjAyMSAxOTo1OQ0KPiBBbjogQnJvY2toYXVzLCBIZW5kcmlrIChUIFJE
QSBDU1QgU0VBLURFKQ0KPiA8aGVuZHJpay5icm9ja2hhdXNAc2llbWVucy5jb20+OyBSdXNzIEhv
dXNsZXkgPGhvdXNsZXlAdmlnaWxzZWMuY29tPjsNCj4gc3Bhc21AaWV0Zi5vcmcNCj4gQmV0cmVm
ZjogUmU6IFtsYW1wc10gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1sYW1wcy1jbXAtYWxnb3JpdGht
cy0wMi50eHQNCj4gDQo+ID4gICAgVGhlIGd1aWRhbmNlIGlzIHRvIGNvbWUgaW4gdGhlIEFwcGVu
ZGl4IEENCj4gDQo+IE9rYXkuICBNYXliZSBuZXh0IGRyYWZ0IGNvdWxkIGhhdmUgYSBza2VsZXRv
biBBcHBlbmRpeCB0aGF0IGp1c3Qgc2FpZCB3aGF0DQo+IGl0IHdpbGwgYmUgd2hlbiBkb25lLg0K
PiANCj4gSSBhbnRpY2lwYXRlIG11Y2ggYmlrZXNoZWRkaW5nIHRoZXJlLg0KPiANCj4gQ01QIGlz
IHdoYXQgSSBjb25zaWRlciAib2xkIHNjaG9vbCIgd2hlcmUgZXZlcnkgYWxnb3JpdGhtIGlzIGFs
bG93ZWQuICBLaW5kYQ0KPiBsaWtlIFRMUyBlc3BlY2lhbGx5IGZvciAxLjEsIGJ1dCBjZXJ0YWlu
bHkgYmVmb3JlIDEuMw0KPiANCj4gTWF5YmUgd2UgY2FuIG1ha2UgaXQgIm5ldyBzY2hvb2wiIGFu
ZCBqdXN0IHBpY2sgYSBmZXc/ICBGb3IgZXhhbXBsZSwNCj4gd2hhdCdzIGluIFRMUyAxLjMgcGx1
cyBvbmUgb3IgdHdvLg0KPiANCg0K


From nobody Thu Jan 21 11:27:33 2021
Return-Path: <sean@sn3rd.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CCB33A0ADE for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 11:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jzDebeDlp951 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 11:27:29 -0800 (PST)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 772753A0ADB for <spasm@ietf.org>; Thu, 21 Jan 2021 11:27:29 -0800 (PST)
Received: by mail-qk1-x732.google.com with SMTP id c7so2843969qke.1 for <spasm@ietf.org>; Thu, 21 Jan 2021 11:27:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=tnWNY/T9eTwwy0NdQcEJvHvCuCDhH38dFc26k+o04fI=; b=e3igt2sTFBGQxwaYrQvFkITvVW2b6f3/dvZiH2FkIIkqA9VSiYTRQ2IEOK8g1mE/Me n/L9qs2aPnmvGKahfOgtsK26tUhsV4BVfp8gSo0s63+4lcvjwXI6nUpjdvO69RygoeMR uBAEtsgVOP7D78CK5zXbDA1EkcV3RCvy6WjDo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=tnWNY/T9eTwwy0NdQcEJvHvCuCDhH38dFc26k+o04fI=; b=SujSNTGROG73C00r21cJECs19LJuXRxgKV5LH/ESCJ0r4Wcs9LRXLr1E7wRdRtcjLd dReZuolDU0lLif+GPmAZu4ApByIUdncfH+Rp5f5cVTQhk2NmTWr93I0KCyGlsAfq+j5u 5laG5I2iLqAqDsRoh9IJxiv0tq2VD1yEFeyputO6T8jYoSs/kZpemV8bwwjniPVFH2Qo E5gbeE8BJI1zakzA7LbWWkonNQQfp2fhM1cOitn/artyimd5SkBwsPRza56ApqWmAKBD VfltOgUHKKymoZgLx6SPWAZP8bP1k3eGTRdgT2Vmd/w2PsJ2TKWo8f6sMY0+8WtHwF+m NE6Q==
X-Gm-Message-State: AOAM530addxerdIqURnyIFAXTIogTSjurWVv3HpvNLvye08kCKXUtqOz 8nG1JY040WBInKOOyOlQ7f48ew==
X-Google-Smtp-Source: ABdhPJyH/EFJYo+XLJE/P/2SDspB6zNDRZuyJ118QdEKZ26dqe4HSyqQW7Wu9qdsVhByczuiv39Fwg==
X-Received: by 2002:ae9:f507:: with SMTP id o7mr1314474qkg.420.1611257248372;  Thu, 21 Jan 2021 11:27:28 -0800 (PST)
Received: from [192.168.1.152] (pool-108-31-39-252.washdc.fios.verizon.net. [108.31.39.252]) by smtp.gmail.com with ESMTPSA id l24sm4589399qkl.46.2021.01.21.11.27.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Jan 2021 11:27:27 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
Date: Thu, 21 Jan 2021 14:27:26 -0500
Cc: Rich Salz <rsalz@akamai.com>, Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C69D92DB-E066-4049-9C78-A868C98A846D@sn3rd.com>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com> <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com> <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/fjNjxey2araJCN5z-zhsHTEdCrY>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 19:27:31 -0000

Ah this helps.

Can you correct me if I am wrong, but it seems like Sections 2-6 list =
the OIDs and associated parameters for the various places where =
AlgorithmIdentifer appears in CMP. And, there=E2=80=99s nothing new; =
this is okay, it=E2=80=99s just that there are no new OIDs and there are =
no parameters for the OIDs.

Appendix A is the part of the draft that Appendix D of RFC 4210?

spt

> On Jan 21, 2021, at 14:10, Brockhaus, Hendrik =
<hendrik.brockhaus@siemens.com> wrote:
>=20
> Sorry, I wanted to say, that there is already guidance in Appendix A. =
There is also an Update to RFC4210 Appendix D.2 and an Algorithm Profile =
for the Lightweight CMP.
> Any feedback and concrete suggestions to theses algorithm profiles is =
very welcome. I like the idea to align to algorithms supported by TLS =
1.3.
>=20
> But you are right, when supporting EnvelopedData, e.g., for central =
key generation, it really gets complex. But this is not due to CMP but =
to the complexity of key transport in EnvelopedData.
> For the Lightweight CMP Profile the central key generation is optional =
and one could skip Section 4 (apart from PBKDF2, that is needed for =
PBMAC1 in Section 6) and 5 completely.
>=20
> Hendrik
>=20
>> -----Urspr=C3=BCngliche Nachricht-----
>> Von: Salz, Rich <rsalz@akamai.com>
>> Gesendet: Donnerstag, 21. Januar 2021 19:59
>> An: Brockhaus, Hendrik (T RDA CST SEA-DE)
>> <hendrik.brockhaus@siemens.com>; Russ Housley <housley@vigilsec.com>;
>> spasm@ietf.org
>> Betreff: Re: [lamps] I-D Action: =
draft-ietf-lamps-cmp-algorithms-02.txt
>>=20
>>>   The guidance is to come in the Appendix A
>>=20
>> Okay.  Maybe next draft could have a skeleton Appendix that just said =
what
>> it will be when done.
>>=20
>> I anticipate much bikeshedding there.
>>=20
>> CMP is what I consider "old school" where every algorithm is allowed. =
 Kinda
>> like TLS especially for 1.1, but certainly before 1.3
>>=20
>> Maybe we can make it "new school" and just pick a few?  For example,
>> what's in TLS 1.3 plus one or two.
>>=20
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Thu Jan 21 12:48:00 2021
Return-Path: <rsalz@akamai.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 627713A0C70 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 12:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id waIUZDA3hGLF for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 12:47:58 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41FD03A0C5D for <spasm@ietf.org>; Thu, 21 Jan 2021 12:47:58 -0800 (PST)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 10LKeI64016259; Thu, 21 Jan 2021 20:47:57 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=sUXxN61OExQ27J/ESYvW4c4mZTTqeB3D6iCieBgbVKg=; b=c40rgMMcPMjPZA57Jn8YOpNrSSqB4us9pd+Vh9HACcPN8z22kyMI4Q64uHZO+lxY+7o+ JC/QKGuLeDuuvhYri7Z4ET8PPRaHEPh+dOK1cqpOmbbuw65UH6uxwcxYADWwxfp5I/9P Q1QKxzwoJcrZiTIiBidPS3YHqJSSwRatnr6KAh6cO943IDtloqnnXbLKn1sk3bi4vYL1 h1bWj9i8BDISolN8DQgwQrfHRk+EfKpJ/N85OR6cykdRfbAHQpRb2xH24w6j+N6boow9 gBXh515RbRa5G9nN5OMJ/IkyH1kHmZBPGNkepaFVNchNJofopbGiGnk+F6waiv11SnZF ow== 
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 3668rsm63q-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Jan 2021 20:47:57 +0000
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 10LKYSJK022169; Thu, 21 Jan 2021 12:47:56 -0800
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint5.akamai.com with ESMTP id 3668smwxh4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 21 Jan 2021 12:47:56 -0800
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 21 Jan 2021 15:47:56 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Thu, 21 Jan 2021 15:47:56 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bOuRd8Wg6qTUuzRaLVMhTx16oyoqaA///D5gCAAFwEAP//rX+AgABXV4D//8dvgA==
Date: Thu, 21 Jan 2021 20:47:55 +0000
Message-ID: <44CD89E1-F529-4F52-8702-E20BADD933F1@akamai.com>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com> <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com> <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21011103
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <32816B3AD5430E47BD2951EA94D3F0AC@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-21_10:2021-01-21, 2021-01-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=702 phishscore=0 mlxscore=0 spamscore=0 malwarescore=0 bulkscore=0 adultscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101210105
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-21_10:2021-01-21, 2021-01-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 phishscore=0 priorityscore=1501 adultscore=0 impostorscore=0 suspectscore=0 bulkscore=0 malwarescore=0 spamscore=0 clxscore=1015 mlxlogscore=611 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101210106
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.60) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint5
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/JLxNOHRQG9KdhxOPTbjieKc2ycY>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 20:47:59 -0000

DQoNCu+7v09uIDEvMjEvMjEsIDI6MTAgUE0sICJCcm9ja2hhdXMsIEhlbmRyaWsiIDxoZW5kcmlr
LmJyb2NraGF1c0BzaWVtZW5zLmNvbT4gd3JvdGU6DQoNCiAgICBTb3JyeSwgSSB3YW50ZWQgdG8g
c2F5LCB0aGF0IHRoZXJlIGlzIGFscmVhZHkgZ3VpZGFuY2UgaW4gQXBwZW5kaXggQS4NCg0KVGhh
bmtzIGZvciB0aGUgaW5mby4NCiANCg0KDQo=


From nobody Thu Jan 21 13:37:55 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BEBC3A0CEB for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 13:37:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eoq-34DCoEAu for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 13:37:52 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B1F23A0CE7 for <spasm@ietf.org>; Thu, 21 Jan 2021 13:37:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id D7118300BA6 for <spasm@ietf.org>; Thu, 21 Jan 2021 16:37:49 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id KrucI8WPg9oN for <spasm@ietf.org>; Thu, 21 Jan 2021 16:37:48 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 70A94300ADB; Thu, 21 Jan 2021 16:37:48 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <AM0PR10MB2418352793349C0C5C6A850CFEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
Date: Thu, 21 Jan 2021 16:37:49 -0500
Cc: "spasm@ietf.org" <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6EDF5C4-B886-4C02-A978-BA3F72779F15@vigilsec.com>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <AM0PR10MB2418352793349C0C5C6A850CFEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/aT-WE0TM85TH6Ib2qIa83MxTAgw>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 21:37:54 -0000

If all of the algorithms are actually used, I would not mink keeping =
them, but I wonder about a few that are on the list.  I guess this is a =
call for people to propose ones to drop.

Russ

> On Jan 21, 2021, at 1:54 PM, Brockhaus, Hendrik =
<hendrik.brockhaus@siemens.com> wrote:
>=20
> What would you suggest to drop?
>=20
> Hendrik
>=20
>> -----Urspr=C3=BCngliche Nachricht-----
>> Von: Spasm <spasm-bounces@ietf.org> Im Auftrag von Russ Housley
>>=20
>> Hendrik:
>>=20
>> Wow, that is a lot of key agreement algorithm alternatives. Do we =
really need
>> all of them?  Can we drop any?
>>=20
>> Russ
>>=20
>>=20
>>> On Jan 20, 2021, at 11:10 AM, internet-drafts@ietf.org wrote:
>>>=20
>>>=20
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>> This draft is a work item of the Limited Additional Mechanisms for =
PKIX and
>> SMIME WG of the IETF.
>>>=20
>>>       Title           : CMP Algorithms
>>>       Authors         : Hendrik Brockhaus
>>>                         Hans Aschauer
>>>                         Mike Ounsworth
>>>                         Serge Mister
>>> 	Filename        : draft-ietf-lamps-cmp-algorithms-02.txt
>>> 	Pages           : 27
>>> 	Date            : 2021-01-20
>>>=20
>>> Abstract:
>>>  This document describes the conventions for using concrete
>>>  cryptographic algorithms with the Certificate Management Protocol
>>>  (CMP).  CMP is used to enroll and further manage the lifecycle of
>>>  X.509 certificates.
>>>=20
>>=20
>> _______________________________________________
>> Spasm mailing list
>> Spasm@ietf.org
>> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=

>> .ietf.org%2Fmailman%2Flistinfo%2Fspasm&amp;data=3D04%7C01%7Chendrik.
>> brockhaus%40siemens.com%7Ceb613e47461a441631f208d8be2ddc95%7C38
>> ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637468451471439269%7CU
>> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
>> 6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=3DWgDQTSsFwQKsqwA1Cs
>> BDegLvXHV1Py1xwyCPFOwt1ME%3D&amp;reserved=3D0


From nobody Thu Jan 21 23:00:55 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF5C63A1179 for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 23:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dTPiWY8f0WfX for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 23:00:48 -0800 (PST)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-he1eur04on0608.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0d::608]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 426F63A0906 for <spasm@ietf.org>; Thu, 21 Jan 2021 23:00:48 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DbYeDNHaBy1LMAriDcU31kZJSe7AtkPChGHBZcwRWTf7ooZIOJDA/Y73Zs47U9G3JENkttvwYdRy4IPSSBqEskkAScQHpjXY25ZxuZ+e+ztThAAaZbWqt0jSYr6Zi7TXg/N8wzDlVeX9jdqNCImSgpgXZrBoWUB9yHrHg0Be7HLJDZGzHN6A/t5qpn52Qk6nJbppJdG0bBnCuCgb7XsJcq0LvzWxtpSCFH9E57anwg90+k/1eRcg5WUZNXfaB/xrou8CNik+X3U5DBAO5vrKaUwQXmohhHsKvCn+JeJdGjmUEL+V5JwK4vnb21HgbJInAKcOvuYJPBb2rHaDArsxKw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KIVkRkoIFNAdyGOQCuaVLkt2HaOhU7DWiWVzibLljnA=; b=XYhtZ9zBEl9eogc3wstR4QrjMvOU652L0iHkb0dXBQLf7vGajBCcf50OILhjP9qO5FCmKHx6RcTNUqIvcV3nGPQm8mrBP2j7LCPH/ow5W4IhYwTHHbEYatPIh3sr8YVu7opZLJ9vp6YxI2iOPs6lXKZpkFyDZFtoSJdCw7DcT4oM7v0XheRkDPFDlAXAtA/En5CDGW3VG/xwqm3AWuO/15Ev7ZwJ4yyWqpGNHapV9P5elweDO3QEsIEQ2WzTBWC2ZqP8zbIyAMOPUp8rOEI6/IXgW4gMJLPP8ZgDq/ztaLhjlfX2g59OzoDOgbr8kYpvsxyRdqvbn22u+I0UIjGSbQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KIVkRkoIFNAdyGOQCuaVLkt2HaOhU7DWiWVzibLljnA=; b=IQWTCp/xhQ0N3p+F+7mdkQuvax/pLMpWFzp+snfC1zs+b6jiBZ6pQvbEx/j0vMbY3xl2/lsYIpLLjCh9K6FgSODpZowelJfYBbhbUux86zK0Xo9nSsdThI+Y2QbP5ZzQNlaxUb5xGb6n/4AnAfxa9QQH0u/Cqys1mmu9MHPOcDs=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM0PR10MB2931.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:160::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.13; Fri, 22 Jan 2021 07:00:31 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1%3]) with mapi id 15.20.3784.013; Fri, 22 Jan 2021 07:00:31 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Sean Turner <sean@sn3rd.com>
CC: Rich Salz <rsalz@akamai.com>, Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bT5wngqywmbE6XWcKJbZgLXqoyTtWAgAAXtwCAAAga0IAAAbcAgAAA80CAAAcIAIAAwMSA
Date: Fri, 22 Jan 2021 07:00:31 +0000
Message-ID: <AM0PR10MB2418CF25FD1157481A3EDE07FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com> <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com> <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <C69D92DB-E066-4049-9C78-A868C98A846D@sn3rd.com>
In-Reply-To: <C69D92DB-E066-4049-9C78-A868C98A846D@sn3rd.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2021-01-22T07:00:29Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=aa748999-158d-4add-8970-f2a2af3be08e; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
authentication-results: sn3rd.com; dkim=none (message not signed) header.d=none;sn3rd.com; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.179]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 08041742-c6dd-40d4-4179-08d8bea368b8
x-ms-traffictypediagnostic: AM0PR10MB2931:
x-microsoft-antispam-prvs: <AM0PR10MB293191C5805986561B88ECC3FEA00@AM0PR10MB2931.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: nlfitir9SgjyVbUrFmBOkBurUnjeYY8dtCwW4dUqwoHD3RSDHWfNzCzGZgI6MQe5tmOp5p0cEcRgLsUvs7OFRG61X+vIJrqKTL1HYVerfHyd/OqJ9EWZV/8pqiQA5i/am8Ywt0KNSHfjs9g3rNDJH2wNx7os2wEAaOGF/V9n7UggVx2beaZsF80SossxlMc6ybjxspU7SFckNr/ugyIKbPWc8ZsGaQujWyxNcRC3xmW8sa+rTL4fGcOfHFq9dtnUaAGTjtSKwLEj4Va5E+HXwaLqf/hEi9q92TQ1HfiY0F/dSRivpV2B4KINxCgVHQeXEJlB4PGh5VKcQ5Su89BfbPoLayYsGl9cR15+i7+styVp755TqDPMpfVweWRdViGgECcCMHv3I4Jizi/zz42eSR5H//HvtIXMVMNAMJhlWAgaQ7gdZIGStyN4rdoYFXYIT6+dHHIRuo7DpWpfF8mnHA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(396003)(136003)(39860400002)(346002)(376002)(366004)(478600001)(5660300002)(45080400002)(83380400001)(55016002)(4326008)(316002)(71200400001)(86362001)(54906003)(52536014)(76116006)(966005)(66574015)(64756008)(2906002)(9686003)(26005)(66946007)(7696005)(66556008)(33656002)(66446008)(66476007)(55236004)(6506007)(6916009)(53546011)(8936002)(8676002)(186003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?BGvKC2dbfPcP+xUF4jV1Aaw6awXuwAu5uN/9Bg5oZbWmz+t6zpAMQigy9A?= =?iso-8859-1?Q?S9IaJBevISlop44eT0JwAZiqE4CRlCWKD3ziflRsP/gOtj4H4/ifoE2JUi?= =?iso-8859-1?Q?LHPprUqU2rpUQgXzRkcwva2pQM4DQ4YGxnnjQW7TfSaTH/0I0sGLeJQSz8?= =?iso-8859-1?Q?77xRwvzkz3jKAIEFAHUM7zA4ti21tb/fnongAYzEY+5PpF58bO2Ev9RyVN?= =?iso-8859-1?Q?XBHEHLx7MeAOu4JUcjgIwIQmyqwnyGBn8Bi/ut94xroxMUNQ540axuQKnj?= =?iso-8859-1?Q?0EjROMA+wqw8Sv6yj321BjnbZHh+CYRDTvApYCbrnJE/53JOjs6/4vWYIN?= =?iso-8859-1?Q?doIU4uGeeIv1iuKMSIosQdDxeNgNTRLYBjFrEW59jhDvfURMMzvCPWtzOM?= =?iso-8859-1?Q?MF+fJtXtcGpGAsYkDr7vJSE9Cc1OsPJzxWN8C3STkcerzNFs6XtzMU/uzi?= =?iso-8859-1?Q?EZHK6b2x4yTrqeqmL5hVBqik9GZrQkZzmpmhTKEf/26bTU9XE+Hu53QCLi?= =?iso-8859-1?Q?+62qZeJn7k44b2OI8TGQXEgjV8euS7Me37aBhvuuv48W8HmJ61h+V+u8oK?= =?iso-8859-1?Q?L/v2BF6mWEGj1hZe6rq29IASm0Up06ljt97LSePsOxRKcC1UcDHkZw4urx?= =?iso-8859-1?Q?oVzzKR0qtDFhBOPM/GRyIGOnK+0xIRP1xlxKfW9m+B7cVnji1lGVMvb3Sb?= =?iso-8859-1?Q?YZLniF5f8xBA5xIlvjUv4wK1SM63GADIHsu94JE/i7dzdPNKKnWJWDVgl9?= =?iso-8859-1?Q?Z86iCylEqX+CDowZkGhDxQErG+AY95d36Ki2uO3V48EoryI5BuZJqBadNE?= =?iso-8859-1?Q?vdwCC9zvPTxb25B+3BXnIK+FTBwLXdbUEFMXkH3W/EuWzfRgXuw92TOWLd?= =?iso-8859-1?Q?ZtNamxr1kWq5LqKD+Qs7YZxFJtF/n98TYRwkCYsCp8xbSmugtfTrQ7YKeq?= =?iso-8859-1?Q?HQDZQasP89RKN33hEHNZvvQsEsyMJ1+uhdhjrQaqu9qYs9KHys1p+9+asW?= =?iso-8859-1?Q?kI9us+j7TV0ohBKiWk2wjkjAgL1vRFs3fgC6be?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 08041742-c6dd-40d4-4179-08d8bea368b8
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2021 07:00:31.7248 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: h3lOyQxxgo8X/eUhjtmZsOVXbGpsv34Q5aJUPTtTwld1Kx1xkP/sX1Ce9bPDLfggBJA7U8sntG0ObnhpI5eYF6e0/hUYHfBONzO/yVsxiYQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR10MB2931
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/7tsKXhPplKRnPjK07qSVm0Zs3-c>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 07:00:53 -0000

Thanks Sean for the summary. That is exactly what I intended to do.
I wanted to enlist the OIDs and where to find the details on relevant algor=
ithms in Sections 2-6.
The specific guidance and profiles is located in Appendix A.

Hendrik=20

> -----Urspr=FCngliche Nachricht-----
> Von: Sean Turner <sean@sn3rd.com>
> Gesendet: Donnerstag, 21. Januar 2021 20:27
> An: Brockhaus, Hendrik (T RDA CST SEA-DE)
> <hendrik.brockhaus@siemens.com>
> Cc: Rich Salz <rsalz@akamai.com>; Russ Housley <housley@vigilsec.com>;
> spasm@ietf.org
> Betreff: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
>=20
> Ah this helps.
>=20
> Can you correct me if I am wrong, but it seems like Sections 2-6 list the=
 OIDs
> and associated parameters for the various places where AlgorithmIdentifer
> appears in CMP. And, there's nothing new; this is okay, it's just that th=
ere are
> no new OIDs and there are no parameters for the OIDs.
>=20
> Appendix A is the part of the draft that Appendix D of RFC 4210?
>=20
> spt
>=20
> > On Jan 21, 2021, at 14:10, Brockhaus, Hendrik
> <hendrik.brockhaus@siemens.com> wrote:
> >
> > Sorry, I wanted to say, that there is already guidance in Appendix A. T=
here
> is also an Update to RFC4210 Appendix D.2 and an Algorithm Profile for th=
e
> Lightweight CMP.
> > Any feedback and concrete suggestions to theses algorithm profiles is v=
ery
> welcome. I like the idea to align to algorithms supported by TLS 1.3.
> >
> > But you are right, when supporting EnvelopedData, e.g., for central key
> generation, it really gets complex. But this is not due to CMP but to the
> complexity of key transport in EnvelopedData.
> > For the Lightweight CMP Profile the central key generation is optional =
and
> one could skip Section 4 (apart from PBKDF2, that is needed for PBMAC1 in
> Section 6) and 5 completely.
> >
> > Hendrik
> >
> >> -----Urspr=FCngliche Nachricht-----
> >> Von: Salz, Rich <rsalz@akamai.com>
> >> Gesendet: Donnerstag, 21. Januar 2021 19:59
> >> An: Brockhaus, Hendrik (T RDA CST SEA-DE)
> >> <hendrik.brockhaus@siemens.com>; Russ Housley
> <housley@vigilsec.com>;
> >> spasm@ietf.org
> >> Betreff: Re: [lamps] I-D Action:
> >> draft-ietf-lamps-cmp-algorithms-02.txt
> >>
> >>>   The guidance is to come in the Appendix A
> >>
> >> Okay.  Maybe next draft could have a skeleton Appendix that just said
> >> what it will be when done.
> >>
> >> I anticipate much bikeshedding there.
> >>
> >> CMP is what I consider "old school" where every algorithm is allowed.
> >> Kinda like TLS especially for 1.1, but certainly before 1.3
> >>
> >> Maybe we can make it "new school" and just pick a few?  For example,
> >> what's in TLS 1.3 plus one or two.
> >>
> >
> > _______________________________________________
> > Spasm mailing list
> > Spasm@ietf.org
> >
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.
> >
> ietf.org%2Fmailman%2Flistinfo%2Fspasm&amp;data=3D04%7C01%7Chendrik.b
> rock
> >
> haus%40siemens.com%7Caf2a533f39304bd8101d08d8be4298c1%7C38ae3bc
> d95794f
> >
> d4addab42e1495d55a%7C1%7C0%7C637468540520523618%7CUnknown%7
> CTWFpbGZsb3
> >
> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
> 3D%7
> >
> C1000&amp;sdata=3DGHOXtxAVGOzowtF23f7XQ9LP2UnYs%2FpLdrdMtvmYxP8
> %3D&amp;r
> > eserved=3D0


From nobody Thu Jan 21 23:04:01 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 606753A117B for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 23:03:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KKoCPzUs-B3X for <spasm@ietfa.amsl.com>; Thu, 21 Jan 2021 23:03:57 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60053.outbound.protection.outlook.com [40.107.6.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DE7B3A0906 for <spasm@ietf.org>; Thu, 21 Jan 2021 23:03:57 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FLeD/BXpZB7lPfwCoDZPJrdbUHM9lkLltu7nUGNoSleoUaNnmothl6Awb99RDQFRIiU5qXdKZWGMdxEO5TytnG4yNw60JL0mwA/42NMj8Vr2IKxVftt9rAgqNE7Pj0hj/rqupHcViFXhBH/m1alj/LfNz89G1MzpK2DT01r3URMjrQzJeaPZxOXmI/3LfHFoTmPRx8LnTQraOwfIw2PkibCImWVidzYrh9zJy7WhYWIpeIJ5wOg4+6zU42ZshABRRUlimLnFCf732DrOB9SlCCxU29isbZ1MX8KSpLVu0ySpjDfwnzwGqyG7TYFwHanwlnUsyZpZBy+THBJMQoNu2g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Zr/EU1jcNQF89zKXc+7qEZaj1/NGwduEh5kpFMiThbI=; b=iMAOSZ8X+hP11MBz64ebvQnQcj4lu75Sc6QWUqyGOp6k6E/fxKmK99S4d/phSPDWPt9Rg1Q5mXnaLgDM83N5O61zTLIKj+jIvZk0lryzP5KEAVohcGkMhg/0H5wehR1QRZnO/JCenu250vob1RGzIWVZW5OUkAHX/tnozr85nGYkkdy3L+or+1WwJVbR8wWHjtUKI+UPrdP8Ks/ztMMXrWtyxqYU7L/2oIL2xQ9Ly7QQS0upTdwqdqDgShJvJsNk8XiCrSmPXch+cBHTmzlS6W/lET6fdk0JzV4dw9ZQiFf66hp1KmrFZPHrn8YJ81M1jtF44ROjVH1ge0RNY9ZwEg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Zr/EU1jcNQF89zKXc+7qEZaj1/NGwduEh5kpFMiThbI=; b=LjYEXkk/k6jUrdNjCZfgOSaPOGcQSUtbGDPH0+z5DYXrx6SmZM7my04AsSwOi0JW1q06htFdYc36FCXk/aYA0q/2U5Q8ntkGCkZ7DT2TC8Sgr7DlBHHDXQq0iPYww0QDcIiohizEdpiBkY9U69j+6R4hSprsBm4PMzS0q4RBmyg=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM9PR10MB4339.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:20b:26c::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.13; Fri, 22 Jan 2021 07:03:55 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1%3]) with mapi id 15.20.3784.013; Fri, 22 Jan 2021 07:03:55 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Russ Housley <housley@vigilsec.com>
CC: "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bT5wngqywmbE6XWcKJbZgLXqoyTtWAgAAf+qCAAC33gIAAnXFg
Date: Fri, 22 Jan 2021 07:03:54 +0000
Message-ID: <AM0PR10MB2418821D45528EDC986A7559FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <AM0PR10MB2418352793349C0C5C6A850CFEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <F6EDF5C4-B886-4C02-A978-BA3F72779F15@vigilsec.com>
In-Reply-To: <F6EDF5C4-B886-4C02-A978-BA3F72779F15@vigilsec.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2021-01-22T07:03:53Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=a7a338c2-8c31-407d-b59c-5d27dfee8b15; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
authentication-results: vigilsec.com; dkim=none (message not signed) header.d=none;vigilsec.com; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.179]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: b84490c6-2f66-4cb9-83fd-08d8bea3e1d1
x-ms-traffictypediagnostic: AM9PR10MB4339:
x-microsoft-antispam-prvs: <AM9PR10MB43394DD3C98BCBF0080A5B56FEA00@AM9PR10MB4339.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:2958;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: o0pQnx8zG9rJyy3gyRzbcP1LEBCK9jcI93PjSuV2qRfXJK4cXGQaIngyzvYFYVjwQ3Hb/+GhDeaDOG+R+GpzIZcmEsqS1FALAbixTDC+ckVjypc+T5fVfFzuSX8irUNAdbFyaxmo/ATz+zRwt4nF+N317JMNB3vjKtpBRJ/KHy4wZGJtfpn+Zi3Vk8RafoUW5ZUAnt01qiHy1PYjLa3Ond+AFwJEC6pbhk4Gk0k02t9B4LVFjRBTz3W4omeen73XUVrcAz5DDTm92oCX1lrH/gF77gpCgCT854THFWLW7wdHA9gXik2pbnBzcuDfAJCPmS9zdV/TM4SJE4DdAkVw8uRZlobbXT8pIOimuuZWSt9VNWrcNpfRUKxte/iETD9S6+p6NC/iyvCUZHUryqXaMyBRGTE/4sQ4qjEevndfemyDTdML+ygcJ59OHJ4OffPgPv7N1DlFn3arl6Yw7vzaZA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(346002)(396003)(136003)(39860400002)(376002)(366004)(45080400002)(86362001)(71200400001)(5660300002)(83380400001)(4326008)(316002)(26005)(966005)(76116006)(52536014)(66446008)(66946007)(55016002)(2906002)(9686003)(66476007)(66574015)(478600001)(7696005)(33656002)(64756008)(66556008)(6506007)(53546011)(55236004)(6916009)(8936002)(8676002)(186003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?8mGpcZiST7BzA5QZktnlTa8/2v5Ui6vOVg/Ro3QD5gQNlfDhUgMLt9dp3t?= =?iso-8859-1?Q?wiC0NafDk8OnKP30Gym3u8757iULuieGIayDWTyPZT9fAY4EgjNhUX5jyf?= =?iso-8859-1?Q?HL8ZP0wSNfIgibrRHbHn3EEU+gw5LdEyE5M1gA7NDcj+6XlkZQMfBfkRSm?= =?iso-8859-1?Q?rGGVdK82m2LL8B5y7HjIVBjhYP2wq+DI9bZEWVujbxjU36yKuAhWOm68c3?= =?iso-8859-1?Q?LrYQ3F04Qyk6NLdW8C7JaaUwTWwUhgm9ayrTIRvSvkOgxpZmC3OfYUTM2P?= =?iso-8859-1?Q?4BOECZN77crKhjWJd6IzeATkZ2m0/hvJPZ/WkaxNjnYb3mnbjwi6r5rEPN?= =?iso-8859-1?Q?nEulk3Abk9aUXNFs1mctNG8L4z3c+nLIFbFxwqCLjH4s1ppP9bmLvVAKrL?= =?iso-8859-1?Q?RpSSQHh56ERKg/SZL9ETAHqj20xSJctbTpIz/9750d//Xp2MAGuwQD9elL?= =?iso-8859-1?Q?wEobonNsBlQCUSZNiuUpLzucAvoYexPAPH2X6SIWa84Q+N0jn3UIb0mYed?= =?iso-8859-1?Q?AYK6N+lgYZAuyGQFvZnihKPcShazZS5UjKZtkXF7eJnjPJXKNNr7n9Zlfb?= =?iso-8859-1?Q?lQSwekI9AsN+cWLK2tBFRMdYtipOfAGqUBojyUwDt4QH1lwB5QXpBBsAqZ?= =?iso-8859-1?Q?bV/6i0LYKwpBH4PRpy/sgusaUy4JqdkhW10e5KEGywuXXN7ZmE/IM5nQji?= =?iso-8859-1?Q?Dta767W6IGSHLbP+g6i37EP0Ub8EL0eAJc/WZkbw5OO5PZgT1JJ0EowJ+I?= =?iso-8859-1?Q?65THtFTkM5PsGNAenEl9ZFAFbpCeCSCURrnlfMut9dEFWhOvCbBtXgLn1r?= =?iso-8859-1?Q?nyNed2ed6z28dxfXW0q6EhB7VWTqpVU+V2vAAMOG/43GJuybLW18+QQPHw?= =?iso-8859-1?Q?+Uo5Kiv2D0c9EqB6tREtt96GfLmZpKErtK/1eB56vWNItOXyebB9DS/j3O?= =?iso-8859-1?Q?bkgsJ4FSQsZO8ogLhrTIYNsXzJtddKPMcqgoDmFdvzZn04URxQXcfFFfV5?= =?iso-8859-1?Q?fAHfxRa2MLOnsNSkYRQcKsY62dpiPwxVmXlsBY?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: b84490c6-2f66-4cb9-83fd-08d8bea3e1d1
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2021 07:03:54.9866 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 0jgYfnpEMurZMiOmUvYksIgEhIP00iHoNt/71Zk6/pHB3dzcRwQ7TLtqfWgWzAgPUhhUR/3F26EXnEPNDcfsQB6djd9zJvVvQpE8HhyOaPg=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM9PR10MB4339
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/OuchT2F2Ax1zzh59unbmpB8j92U>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 07:03:59 -0000

Yes, if people think, we should drop some of the listed algorithms, we shou=
ld discuss and align on the mailing list.
I would also like to get input to Appendix A. Any suggestions on how to enh=
ance the Appendix are welcome.

Hendrik

> -----Urspr=FCngliche Nachricht-----
> Von: Russ Housley <housley@vigilsec.com>
>=20
> If all of the algorithms are actually used, I would not mink keeping them=
, but
> I wonder about a few that are on the list.  I guess this is a call for pe=
ople to
> propose ones to drop.
>=20
> Russ
>=20
> > On Jan 21, 2021, at 1:54 PM, Brockhaus, Hendrik
> <hendrik.brockhaus@siemens.com> wrote:
> >
> > What would you suggest to drop?
> >
> > Hendrik
> >
> >> -----Urspr=FCngliche Nachricht-----
> >> Von: Spasm <spasm-bounces@ietf.org> Im Auftrag von Russ Housley
> >>
> >> Hendrik:
> >>
> >> Wow, that is a lot of key agreement algorithm alternatives. Do we
> >> really need all of them?  Can we drop any?
> >>
> >> Russ
> >>
> >>
> >>> On Jan 20, 2021, at 11:10 AM, internet-drafts@ietf.org wrote:
> >>>
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >>> This draft is a work item of the Limited Additional Mechanisms for
> >>> PKIX and
> >> SMIME WG of the IETF.
> >>>
> >>>       Title           : CMP Algorithms
> >>>       Authors         : Hendrik Brockhaus
> >>>                         Hans Aschauer
> >>>                         Mike Ounsworth
> >>>                         Serge Mister
> >>> 	Filename        : draft-ietf-lamps-cmp-algorithms-02.txt
> >>> 	Pages           : 27
> >>> 	Date            : 2021-01-20
> >>>
> >>> Abstract:
> >>>  This document describes the conventions for using concrete
> >>> cryptographic algorithms with the Certificate Management Protocol
> >>> (CMP).  CMP is used to enroll and further manage the lifecycle of
> >>>  X.509 certificates.
> >>>
> >>
> >> _______________________________________________
> >> Spasm mailing list
> >> Spasm@ietf.org
> >>
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww
> >>
> .ietf.org%2Fmailman%2Flistinfo%2Fspasm&amp;data=3D04%7C01%7Chendrik.
> >>
> brockhaus%40siemens.com%7Ceb613e47461a441631f208d8be2ddc95%7C38
> >>
> ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637468451471439269%7
> CU
> >>
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> >>
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=3DWgDQTSsFwQKsqwA1Cs
> >> BDegLvXHV1Py1xwyCPFOwt1ME%3D&amp;reserved=3D0


From nobody Fri Jan 22 05:30:33 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C8CED3A0C60; Fri, 22 Jan 2021 05:30:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: spasm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: spasm@ietf.org
Message-ID: <161132223078.24135.4147323963754983842@ietfa.amsl.com>
Date: Fri, 22 Jan 2021 05:30:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/SP5xYCtCrWdBsrQDcA59_aTdA6k>
Subject: [lamps] I-D Action: draft-ietf-lamps-cmp-updates-07.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 13:30:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Limited Additional Mechanisms for PKIX and SMIME WG of the IETF.

        Title           : Certificate Management Protocol (CMP) Updates
        Authors         : Hendrik Brockhaus
                          David von Oheimb
	Filename        : draft-ietf-lamps-cmp-updates-07.txt
	Pages           : 53
	Date            : 2021-01-22

Abstract:
   This document contains a set of updates to the syntax and transport
   of Certificate Management Protocol (CMP) version 2.  This document
   updates RFC 4210 and RFC 6712.

   The aspects of CMP updated in this document are using EnvelopedData
   instead of EncryptedValue, adding new general message types, defining
   extended key usages to identify certificates of CMP endpoints on
   certification and registration authorities, and adding an HTTP URI
   discovery mechanism and extending the URI structure.

   To properly differentiate the support of EnvelopedData instead of
   EncryptedValue, the CMP version 3 is introduced in case a transaction
   is supposed to use EnvelopedData.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lamps-cmp-updates/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-lamps-cmp-updates-07.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lamps-cmp-updates-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Fri Jan 22 05:33:40 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BA9C3A12A6 for <spasm@ietfa.amsl.com>; Fri, 22 Jan 2021 05:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfMDD8yJrWNw for <spasm@ietfa.amsl.com>; Fri, 22 Jan 2021 05:33:37 -0800 (PST)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2054.outbound.protection.outlook.com [40.107.20.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9B1C3A12A7 for <spasm@ietf.org>; Fri, 22 Jan 2021 05:33:36 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nZE2Y6cH0/XxzC8p4Z5ptKa18CCZvZJJ8jWVINGLKGdPedJAJvb5yOy6LlwhX5mUFcnRET2JdnzDPjCYkm8xw6/hsAGEfK4nytkIlO9BaalmBYYVG+8I7SzfcN7XaPW0rDeq7CLP/HVGsL58fEVVhqtITFK3rIbxPM40GRMbbIyjNcJO8M4/uZJrUD5bg29fV72aiRoL2L4TfeMq3Qk7LgBhXfgRy2UlsZud5RU2mbje+AYNARYAiy6X+eff6xoiwfzu2iLNf89XX8n1Z+Sysd2KQkRW/j61jn7eBhMDZlaACRO1AsCm51kGfJIJO0G1/lMA5yvdjrQCMmBVrsIoog==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RqKm+L+eWGJFNIQTTFKz/uKmvwKXB4/IVhiSB+pMYbI=; b=XqGXJbJgYsaFaoQHewNBUz5vn9s1YiIkz7P4pS0/RvZKBLLk/ZzywmNixUHFjkiXYXKmfREKGlcWXGtp8oabapM5tlByRA51QbKUO+rHZqzivfTqD4WiPMPugLpsBQyhqKsBxjD177svHrAWP0awFjqpgc0qW2rQOAMjNYvkKhOoUdpLQ/VFfVkj+gLLeCGo6fuyO/EbjunWj9Aybl4jh80lzPELBktP4KG/PuXmrckxKKLI/TFKgc7yseM8VzXztEgihlKdexIun6tlYMAPe+WwxbtZQkjGO2g1B9bRklCraSvEBZxY0usijx5vACSZNMECddhm2LIQY8LDlzqB7w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RqKm+L+eWGJFNIQTTFKz/uKmvwKXB4/IVhiSB+pMYbI=; b=oYESCZcwrVcZLSFWY4SRtaeK5fHmvfYa6VPhyTXSpqaYkHumDiPuWFb3QAqwocv6xkvdQKsJcjj2VvniUbsUcRE0nLdaowK/WL1XXU3hhz4JLRTqB+AnvHC0P+zvBpk1griBiET8AuV3Ftr4M64UunnpTpE950e6vfvHM16pyVw=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM0PR10MB2370.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:d7::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.12; Fri, 22 Jan 2021 13:33:32 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1%3]) with mapi id 15.20.3784.013; Fri, 22 Jan 2021 13:33:32 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-updates-07.txt
Thread-Index: AQHW8MLLNSoOBsjxg0S3+7bntz/UaKozpD4A
Date: Fri, 22 Jan 2021 13:33:32 +0000
Message-ID: <AM0PR10MB2418D86079541DBFAF75EF5BFEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <161132223078.24135.4147323963754983842@ietfa.amsl.com>
In-Reply-To: <161132223078.24135.4147323963754983842@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2021-01-22T13:33:30Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=7a15cc61-38a4-4d98-9475-8e82200cdb00; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.179]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 8e5d00e8-07c4-4878-0e95-08d8beda4faa
x-ms-traffictypediagnostic: AM0PR10MB2370:
x-microsoft-antispam-prvs: <AM0PR10MB2370BD0D857E76D1E09BBCCBFEA00@AM0PR10MB2370.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vBKzn2kVMlFQAM0fc1LRA66x6lQchd6CXDmMNau0u6GoEAt6gVSOeXeIKF19AzxBy6W/L6jQMDLv51RDo+Jr+W1T/e+7rMxWiECK86AfHh5o5unN7vTblcLJdLYuT53Lq1nMTu2nVAMFUuMECpy9NeTGK013dH4fFQkQhoG7fioaiDbaWHy0kx5c5TB2FI4yFRRGxsaKGPbH4Ty3NW0tD3FWO1/SQX9WgPxRhmxHeKxfcHPG5SVyG325+MyMFlI+eyiAQofEjTXMHK+gxdcQoqvbvK6ZCBYXFDbexY2iLqbSpVK0gLofHVeRJiWH5Tv+JPNHSJiHiOirZS4g1u/vQdmGBr1XuZu+A3A4S7LnsbHhweXynYcsVH8ZhrdQr3Y0RUI//zU6GdRliY5jPnX2q5RCfKDG453Vb+TZnM/r5kZF6sbFsdD60ivWZBrK40gFijtm6rN06cN83NjDEEU0PA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(366004)(8936002)(6916009)(55236004)(6506007)(8676002)(186003)(55016002)(76116006)(52536014)(26005)(71200400001)(86362001)(5660300002)(45080400002)(83380400001)(66476007)(498600001)(9686003)(66574015)(2906002)(33656002)(66556008)(7696005)(64756008)(66946007)(966005)(15650500001)(66446008); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?On1cBaLjY9EYM+hv+UYJkvpH7NDYx3DxcO2IsslwQq3sL9njF3i5W/RAuk?= =?iso-8859-1?Q?FV6NtjnIk3cAP2NUaYRryovq07bAwgBxJIxaz3uDOMR+fqjStKZkSKRNOR?= =?iso-8859-1?Q?RRGMt0fZr9eN4lMFKGaZ0orO2xJAxtFfszBb1EPl6x5dDCjBpd7kw+CFYx?= =?iso-8859-1?Q?nT7EM/FSVf+VW+/SUwwd+0IRwOxnr9kNavwBosKw8tqRYcbPLl43IZ+TwT?= =?iso-8859-1?Q?xzbsXqKiIxx3V9uGxv89QhfMzykW0mw+O5hdi4A6ySdSLbY3bXAxg6sRRx?= =?iso-8859-1?Q?zbRREFVc8kSj9iWRrwlLEhsVWyQ2U1RPEKTukdYDZSuB+GBlQB7Dx+fkdi?= =?iso-8859-1?Q?3xIepgTLRcRzJw6UxIKth4KOQsu0HFhYPf2xkG28xSDelHKR4AYTbpDvdL?= =?iso-8859-1?Q?ZUEyLwVTuEG92KgMM3C+b2dueMR8lEt5aCKYxZlrJCXWVo2pv2JSkeL/l1?= =?iso-8859-1?Q?b7cIsA8mpPkTViujFEBlCHOTcbBAfCSc3h0EDU3RJcGo7xAPOopkOTVQdM?= =?iso-8859-1?Q?1cmivJbDW2pphnjk8cV/aHcQIchAJ4Ez0+joY9DbD2ROFLuWSEHEd0XsVc?= =?iso-8859-1?Q?Lk+e4b/i35zmbX4kthbSL6j0pXGhqKtf8ecVLAFGi9Ewfj2W7HncNHxtRA?= =?iso-8859-1?Q?fJBXX+OV7GsbgKb4XrZdpgrBEm0z2pEpu+8XZQEXgvPkNBzFFKGKJEfs5y?= =?iso-8859-1?Q?EFztVybykZ5ayzmrgnbGM4NiMqplB9fOhgsR97JZAT5csbkiYB9YECnQPr?= =?iso-8859-1?Q?DkcGbHHlbZfGJ/yBP2ZFjEaLOW1w1zSbZgnbu1VWhUEJ5U1Ou1d3V/H7y7?= =?iso-8859-1?Q?W+HnPXYpAJppkUplys7Fr0rjl0BEl3BwaQXaTAGuXT1Yyb4wWhNSZrfv7/?= =?iso-8859-1?Q?vYtY0H8B4XyqcWBCCnR2udo+Ad9dxQd/AuMLuKAtHOlgncTFGdsHa6yOUW?= =?iso-8859-1?Q?YpfxSnuUitQtwj09x7lehfo2SdcHLjTJF1bIVCfGU5Gy2Zywy1UO1BNcYI?= =?iso-8859-1?Q?GpZ2BKqo4sCwPPkicGxKjfFRecb0Sfsuc9uYWm?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 8e5d00e8-07c4-4878-0e95-08d8beda4faa
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2021 13:33:32.0928 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: zAzwI5slo3WF6oKs+HAkkn/uJFLq0V4ZAtB0zgRuiBYf5qpBusmYnk39HAVL2/8Y1gki3fn2FScPIH6XihJt84SZJHU4GjRuRfzYZraxycU=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR10MB2370
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/1Qmy6snt8_9byTaGdCR21kXXMEs>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-updates-07.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 13:33:39 -0000

I just uploaded a new version of CMP Updates. I covers the results from IET=
F109 and discussion on the mailing list.
Any Feedback and improvements are welcome.

Hendrik

Theses are the thing that I changed:
   *  Added David von Oheimb as co-author
   *  Changed to XML V3
   *  Added Section 2.3 to enable a CMP protocol version number 3 in the
      PKIHeader for cases where EnvelopedData is to be used (see thread
      "Mail regarding draft-ietf-lamps-cmp-updates").
   *  Added Section 2.4 to refer to [I-D.ietf-lamps-crmf-update-algs]
      for the update of id-PasswordBasedMac for PKI message protection
      using passwords or shared secrets.
   *  Updated Section 2.6 to introduce the protocol version number 3 to
      properly indicate support of EnvelopedData instead of
      EncryptedValue in case a transaction requires use of EnvelopedData
      (see thread "Mail regarding draft-ietf-lamps-cmp-updates").
   *  Update Section 2.14 to make the minimal changes to the respective
      section in CMP more explicit.
   *  Added Sections 2.15 and 2.16 to address the new cmp2021 protocol
      version in Section 7 Version Negotiation.
   *  Updated Section 2.17 to add new OIDs for id-regCtrl-algId and id-
      regCtrl-rsaKeyLen for registration at IANA.
   *  Added Section 2.20 to update the general rules of interpretation
      in Appendix D.1 regarding the new cmp2021 version.
   *  Added Section 2.21 to update the Algorithm Use Profile in
      Appendix D.2 with the reference to the new CMP Algorithms document
      as decided at IETF 108.
   *  Updates Section 3.1 to delete the description of a discovery
      mechanism as decided at IETF 108.
   *  Various changes and corrections in wording.

> -----Urspr=FCngliche Nachricht-----
> Von: Spasm <spasm-bounces@ietf.org> Im Auftrag von internet-
> drafts@ietf.org
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Limited Additional Mechanisms for PKIX a=
nd
> SMIME WG of the IETF.
>=20
>         Title           : Certificate Management Protocol (CMP) Updates
>         Authors         : Hendrik Brockhaus
>                           David von Oheimb
> 	Filename        : draft-ietf-lamps-cmp-updates-07.txt
> 	Pages           : 53
> 	Date            : 2021-01-22
>=20
> Abstract:
>    This document contains a set of updates to the syntax and transport
>    of Certificate Management Protocol (CMP) version 2.  This document
>    updates RFC 4210 and RFC 6712.
>=20
>    The aspects of CMP updated in this document are using EnvelopedData
>    instead of EncryptedValue, adding new general message types, defining
>    extended key usages to identify certificates of CMP endpoints on
>    certification and registration authorities, and adding an HTTP URI
>    discovery mechanism and extending the URI structure.
>=20
>    To properly differentiate the support of EnvelopedData instead of
>    EncryptedValue, the CMP version 3 is introduced in case a transaction
>    is supposed to use EnvelopedData.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdatat
> racker.ietf.org%2Fdoc%2Fdraft-ietf-lamps-cmp-
> updates%2F&amp;data=3D04%7C01%7Chendrik.brockhaus%40siemens.com%7
> C48dfc91868d84ea9d8ab08d8bed9ebc1%7C38ae3bcd95794fd4addab42e1495
> d55a%7C1%7C0%7C637469190483645264%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C1000&amp;sdata=3DHnDyIpStC56FJ3Eab2LLjCgCk%2BSlJrL7a2WP6oE87n0%3D
> &amp;reserved=3D0
>=20
> There is also an HTML version available at:
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww
> .ietf.org%2Farchive%2Fid%2Fdraft-ietf-lamps-cmp-updates-
> 07.html&amp;data=3D04%7C01%7Chendrik.brockhaus%40siemens.com%7C48d
> fc91868d84ea9d8ab08d8bed9ebc1%7C38ae3bcd95794fd4addab42e1495d55a
> %7C1%7C0%7C637469190483645264%7CUnknown%7CTWFpbGZsb3d8eyJWIj
> oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1
> 000&amp;sdata=3DYMgnV8wNnwSu5yfoxz4RKlndZmw%2BJ9BpTBiEY0Z1Bjk%3
> D&amp;reserved=3D0
>=20
> A diff from the previous version is available at:
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww
> .ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-lamps-cmp-updates-
> 07&amp;data=3D04%7C01%7Chendrik.brockhaus%40siemens.com%7C48dfc918
> 68d84ea9d8ab08d8bed9ebc1%7C38ae3bcd95794fd4addab42e1495d55a%7C1
> %7C0%7C637469190483645264%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC
> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&
> amp;sdata=3DraUCTzwJ%2Fh2aM0dM9oAjvA2vIsbIhFpgg6AiOExzbtI%3D&amp;
> reserved=3D0
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> https://eur01.safelinks.protection.outlook.com/?url=3Dftp%3A%2F%2Fftp.iet=
f.
> org%2Finternet-
> drafts%2F&amp;data=3D04%7C01%7Chendrik.brockhaus%40siemens.com%7C4
> 8dfc91868d84ea9d8ab08d8bed9ebc1%7C38ae3bcd95794fd4addab42e1495d5
> 5a%7C1%7C0%7C637469190483645264%7CUnknown%7CTWFpbGZsb3d8eyJ
> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C1000&amp;sdata=3DJgDjsJPjO0iusca5dzgyd8pvbnu8mHuIobyuYdEATls%3D&
> amp;reserved=3D0
>=20
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww
> .ietf.org%2Fmailman%2Flistinfo%2Fspasm&amp;data=3D04%7C01%7Chendrik.
> brockhaus%40siemens.com%7C48dfc91868d84ea9d8ab08d8bed9ebc1%7C38
> ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637469190483645264%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DvKzfebQmwrM1yNNtSdP
> Qzuu1mTOpeDLqjzqGmEg3teA%3D&amp;reserved=3D0


From nobody Fri Jan 22 06:38:52 2021
Return-Path: <rsalz@akamai.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BA663A121E for <spasm@ietfa.amsl.com>; Fri, 22 Jan 2021 06:38:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iTjPLh3tXTQg for <spasm@ietfa.amsl.com>; Fri, 22 Jan 2021 06:38:48 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AD5B3A1213 for <spasm@ietf.org>; Fri, 22 Jan 2021 06:38:48 -0800 (PST)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10METtRm000385; Fri, 22 Jan 2021 14:38:48 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=o4EktbeOHyYi0cCew+web4UYmUWa+4ALpN3WLMuQUDM=; b=as/ybYT/PDzmftGFo/K+gjF/M1ScGn0C5IBEUjf+mfLBsKPuTrMg2DG11Z0JIEAwbP5g 7wpctRmAN7lgx8qGTsqzkeFi/35OPRf0PjQ54MHL81R5e+dPpYMc0gz7xe7cZJuYHBai d8FRqZV1SakbBOlsGzT5FzoX/LEFNovTvLrRIvUqQf7YlB3ePcev+OCZZQc96VKMj5gq BdgbuHy6iE3uOpBwbdR+yb+iJppnYlzQhHjsMIrbQ5LCNW2PxMDz2O5dLBDLAsEFXnbt 6BxraAV4SvajoS3S/bjiGNZIVovsqcG2ivI1TMVEmP+NCiXf3JE3rFeAHkQkmfMmYWEQ Pw== 
Received: from prod-mail-ppoint4 (a72-247-45-32.deploy.static.akamaitechnologies.com [72.247.45.32] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 3668rm1rxc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 Jan 2021 14:38:47 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 10MEcE2C028815; Fri, 22 Jan 2021 09:38:47 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.53]) by prod-mail-ppoint4.akamai.com with ESMTP id 36690500ju-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 22 Jan 2021 09:38:46 -0500
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag3mb2.msg.corp.akamai.com (172.27.123.59) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 22 Jan 2021 09:38:45 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 22 Jan 2021 09:38:45 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Fri, 22 Jan 2021 09:38:45 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, Sean Turner <sean@sn3rd.com>
CC: Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bOuRd8Wg6qTUuzRaLVMhTx16oyoqaA///D5gCAAFwEAP//rX+AgABXV4CAAATEAIAAwaWAgAAsNQA=
Date: Fri, 22 Jan 2021 14:38:45 +0000
Message-ID: <ADF72E6E-E542-41AC-993C-27DD11AFF2A7@akamai.com>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com> <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com> <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <C69D92DB-E066-4049-9C78-A868C98A846D@sn3rd.com> <AM0PR10MB2418CF25FD1157481A3EDE07FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <AM0PR10MB2418CF25FD1157481A3EDE07FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21011103
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <30CE1E816133B24DB771D08C79915222@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-22_11:2021-01-21, 2021-01-22 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 bulkscore=0 spamscore=0 phishscore=0 adultscore=0 suspectscore=0 mlxlogscore=841 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101220082
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-22_09:2021-01-21, 2021-01-22 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 spamscore=0 malwarescore=0 phishscore=0 mlxlogscore=759 suspectscore=0 adultscore=0 mlxscore=0 clxscore=1015 lowpriorityscore=0 priorityscore=1501 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101220081
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.32) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint4
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Rij-n32U5R-TRBnTwltrA9NseNM>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 14:38:50 -0000

PiAgICBJIHdhbnRlZCB0byBlbmxpc3QgdGhlIE9JRHMgYW5kIHdoZXJlIHRvIGZpbmQgdGhlIGRl
dGFpbHMgb24gcmVsZXZhbnQgYWxnb3JpdGhtcyBpbiBTZWN0aW9ucyAyLTYuDQogICAgVGhlIHNw
ZWNpZmljIGd1aWRhbmNlIGFuZCBwcm9maWxlcyBpcyBsb2NhdGVkIGluIEFwcGVuZGl4IEEuDQoN
Ckkgc3VnZ2VzdCB5b3UgY2hhbmdlIEFwcGVuZGl4IEEgdG8gYmUgYSBuZXcgc2VjdGlvbiA3LiAg
SSB0aGluayBpdCB3aWxsIGNhdXNlIG11Y2ggbGVzcyBjb25mdXNpb247IG5vcm1hdGl2ZSBhcHBl
bmRpY2VzIGFyZSBub3QgY29tbW9uLCBlc3BlY2lhbGx5IHNvbWV0aGluZyBzbyBpbXBvcnRhbnQg
YXMgdGhlIGd1aWRhbmNlLg0KDQo=


From nobody Fri Jan 22 09:33:42 2021
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6B483A133B for <spasm@ietfa.amsl.com>; Fri, 22 Jan 2021 09:33:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N1-2C5HpLlP0 for <spasm@ietfa.amsl.com>; Fri, 22 Jan 2021 09:33:40 -0800 (PST)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70081.outbound.protection.outlook.com [40.107.7.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8C593A1311 for <spasm@ietf.org>; Fri, 22 Jan 2021 09:33:39 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=arH7kt8IHZRQ3X3mDyE585mIFHZawkM8molvr6+oxGnU6rhVjQWwui2ioz3XhBhRNXSKHwZQWR0pTZ3DCYgWIK0o2tJ1jdvJddDeSJOWKzs0BrQmI+gY5n3paO1xV1Mb6LQOvD5xEO37bvXvZZCHdug0Tajbinxf4sf5w8Q6sJb/l0Ax5ma3punbkRpioEznLtva3ajZpfk74UpOnNCsvtd8Co45DZ+7jajBXAHv4A3EYUuYCdlxLGzRGuOf18D7VvZVp1QN+jAvnZkLmHMb42SR87gAjQ/weqiYPTm1BbgqUHhHeMH+fnUVEyobisgRMQIjsOE7cWQlAojD9+Ff5g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SEIooXVUfKr28Pw4UNr1rlib7HygUj2JSIZX5XVbOs0=; b=j/dgOViaE8D7/aTtyMiN+UEEmEjMN9HMJiXALSJMghnrH0VgLUI5xVdwcZZjPkbQxfKkwwS6/nB1nTTTSHRZ7tjZEYeQ+SeL6Cn6iuVMwww/8T9BuTNs5N3fjgG8TCBAI5zUSJV3HUzqqOC9QF1ffvm63hASk4OxypsFcZS66mcVuOyhuUxXM2Bf2+bzaXBPsSG3/R+0Bm7D9oihjpoNtIZGGHlEs7bSlqATF56lhHBrOImXO4CghjwPxA/zWARWmId7/dYwJv5kOVR4MDli8DjSlkAyVsFkwCz1TWtudi6Oy1rbPbJJWY1/q6WmeTRZjUV/ZMvGURogTFMr6H/zZw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SEIooXVUfKr28Pw4UNr1rlib7HygUj2JSIZX5XVbOs0=; b=Lv7sXnBQuGeI8XaHtvLbHqp2f2klNM5uLx4pF69yMEhMuhXxWADKFyLKj1XmR/cWeB1RmJP9kPE69274BDTJxAGbD6gl/32B0YAuVYs51/vVSo9qHqIL7B4y0R2e6/u6CPTLBj3y2I/hFrcEuTMUrK2VB81GEkl4lIZrSQlworQ=
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:dd::17) by AM0PR10MB2738.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:131::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.12; Fri, 22 Jan 2021 17:33:36 +0000
Received: from AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1]) by AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM ([fe80::d199:e33a:ff08:75b1%3]) with mapi id 15.20.3784.013; Fri, 22 Jan 2021 17:33:36 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: "Salz, Rich" <rsalz@akamai.com>, Sean Turner <sean@sn3rd.com>
CC: Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
Thread-Index: AQHW70bT5wngqywmbE6XWcKJbZgLXqoyTtWAgAAXtwCAAAga0IAAAbcAgAAA80CAAAcIAIAAwMSAgACA6YCAACrPYA==
Date: Fri, 22 Jan 2021 17:33:36 +0000
Message-ID: <AM0PR10MB24188A9844583BC094B4B479FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com> <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com> <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <C69D92DB-E066-4049-9C78-A868C98A846D@sn3rd.com> <AM0PR10MB2418CF25FD1157481A3EDE07FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <ADF72E6E-E542-41AC-993C-27DD11AFF2A7@akamai.com>
In-Reply-To: <ADF72E6E-E542-41AC-993C-27DD11AFF2A7@akamai.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2021-01-22T17:33:34Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=e690497d-0aab-40f2-929b-4ffcf9770bac; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
authentication-results: akamai.com; dkim=none (message not signed) header.d=none;akamai.com; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.179]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: f2e47aac-9fab-45f2-f66b-08d8befbd956
x-ms-traffictypediagnostic: AM0PR10MB2738:
x-microsoft-antispam-prvs: <AM0PR10MB2738A3FDE4A146825CEB3977FEA00@AM0PR10MB2738.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: lPvEpPLR8iMN4kvLt8whqgr50avo/iTC68j1SzrkCuuJYRIrSSI7gYqLl0mnsjoQgCIluZk6PiYs6ZcQn3lnVs5ShdHpKiDh+BREdojwQFozahgSLsNkWf0WMDMMMwYGkHzALbssy5m8pEdQFmZ3dIFhDthuZQkfAL6tPgzHmmwKBWt3Ywi5hozpGLGzxtbcIeYfWrHRFzi40hiVI2KSmN16kVAUcUXJe172t3bGdl3+MORdZXDOZmXT2GVsWtDv/RKUbndre2JV3/V4jsGS/MPsXzbx+t4ENWKqJg4bNvzDJh8TmwitqqTnjCxMbHh4Z/1x6GYFgTyswaiBlRmjSlfo0gkNd4nUALPNwZswVP19HLPXysJfgYM+yj/P7To0pMIPZ8aPpIoihRfr+3TwCj/gnV/SXTZ4cwGU7gvJeIQZ4XXeDay0J3HwMasuTo4sNppleY4FzP1m/tEeL8jcXW1an7A9GGWNy+gXNbBnc/QFjA4GoU4km1mQrUrJJ70i+TR9iOiRELwRajTkOUBOYg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(396003)(136003)(346002)(376002)(366004)(316002)(55236004)(110136005)(54906003)(8936002)(7696005)(55016002)(66446008)(66556008)(64756008)(66574015)(66476007)(5660300002)(71200400001)(26005)(66946007)(6506007)(478600001)(33656002)(76116006)(4744005)(186003)(2906002)(86362001)(4326008)(9686003)(52536014)(8676002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?bytwckVQZW16MnRCQmROdFkxMG1aMzNHK1I1ckFBVTR5d1dUTVNFdVJ3VVNN?= =?utf-8?B?UGZKOWdZWDhRZEgveEpLOGJHdURhS1FZbGVwQ2RBM1BvK3BWd2FqdDYzSXVG?= =?utf-8?B?S2paejh1TG9vdzVhcWUxSEdhYjNyMWh3VXRQREZPbEl3RlVNaDZCUmQ1ZG9i?= =?utf-8?B?am5zblR0aVczeVhLQnlNTkp1eVFmQ0lWTlQ1UDloWWZZaUovWk50c2ZWRXk1?= =?utf-8?B?YWdTTFNrNUwrUGgxTGdiWHF3MlFsMzducjg2YTNYQytQdG9Qb3dLYTM0RmY1?= =?utf-8?B?WkVhWTh1a0dVazY0UlpQTlhQc2oxeGZBSmc1cEZOQ2NHZjRKS2V0d0w3alhE?= =?utf-8?B?UFdISDV6bDExS1FVNis5clVsVS9LUjdWd3BtSWZFb0VQWnVHU1cyMS85dlh2?= =?utf-8?B?RysvOWowSFowaDVaY2ZZekM5RUxnejI2b2JvaHhELzZJN3UrdmU2UlBsb2pR?= =?utf-8?B?TWZXNWRtSTJaWjZhZHFYUjlWdFNSSnNQcTdEMW4wYVNOZFkxb1p1SVBLYk5m?= =?utf-8?B?MDhWQXJwWEJLV2xPdFhXWGFNMVF1OFIwQWFKQldyU2F5ZmJnZXJpL2p3VDhY?= =?utf-8?B?MXZkTnZ4NXh1OGdINjN2am9Vdy9YbVRPUVdNUmM3bGhpWHROR2FwOEtJeG9D?= =?utf-8?B?OTJTZGUxNmMxQ05tdmd3REVHcFZENmVjc244Rk9zd0VpRUk3ZUhDVmMvYlla?= =?utf-8?B?c2xXU2I0MmN5RXprZnZGWFU5dEN6WVdyajBuTUhiZ1pPQUpKK2Y3UEJ4Qnhm?= =?utf-8?B?WU1WNStTdHJxZkNhakdwT0l0V2lhRSthSTRBSHRWdUpvcUtFZDQvczhCdE4r?= =?utf-8?B?WFl5c0Z0TXIzejl6dDJhUzV2YzAreDdkeFFuSE1ZQ1NiN0krVmxaSW03dTFH?= =?utf-8?B?YnJRZHR5MU56c2tyU1BiWGdBS1VGWGdGaXRZQXJhdk52eEFNcnoxNWxMYkND?= =?utf-8?B?UThuVXlydWhkVnpRZUFQbVl4TXZENmhGN2xKRmZJRFlaRElxdVNTbFY5TDJt?= =?utf-8?B?VFBkRm5aYzlMYXZISzZla1B2YkwwOTVGSmtjZjVVSUljd1lkV3JMVnkvYnQ0?= =?utf-8?B?a2tIZTA3dXd4ek5wRlREKzZ3RmFydXdmNXhZdHdtMHIxbVRvek1mVWpKNXlC?= =?utf-8?B?V24wcjI1ZEEyTkpNTUZtQkVjS0dKcmV3N2hpc1c3REI2d29oQTVEcHN2Qk9p?= =?utf-8?B?MVF0V21DVHBDWHVlWmR4VzIrcGRMWjd3UDRiNHJONzZwUjIyZXRpelFIaCtZ?= =?utf-8?B?aldzS3NIQnoySzNzNGVDTDN0UWF6Zjl0aUR0WVFKa2ZKYzZVbnVRZ3NRM3Za?= =?utf-8?Q?2sfxXfmgcOMcBFGzejskCSS3R6edWGQr+V?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: f2e47aac-9fab-45f2-f66b-08d8befbd956
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2021 17:33:36.3999 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tGhR8TXWxjjZKfgtzPLqHWv6yektSjgN1iG2LRaWrNzQ9GeX2sNNJjmFsznDHgwjx3lQd0xBf2z4a2K55PBoZVL3vzLTLgevWu3Ahj0TJW8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR10MB2738
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/dzSkukevQhihLJHraFHwVD1CWaM>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 17:33:42 -0000

PiAtLS0tLVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tDQo+IFZvbjogU2FseiwgUmljaCA8
cnNhbHpAYWthbWFpLmNvbT4NCj4gDQo+ID4gICAgSSB3YW50ZWQgdG8gZW5saXN0IHRoZSBPSURz
IGFuZCB3aGVyZSB0byBmaW5kIHRoZSBkZXRhaWxzIG9uIHJlbGV2YW50DQo+IGFsZ29yaXRobXMg
aW4gU2VjdGlvbnMgMi02Lg0KPiAgICAgVGhlIHNwZWNpZmljIGd1aWRhbmNlIGFuZCBwcm9maWxl
cyBpcyBsb2NhdGVkIGluIEFwcGVuZGl4IEEuDQo+IA0KPiBJIHN1Z2dlc3QgeW91IGNoYW5nZSBB
cHBlbmRpeCBBIHRvIGJlIGEgbmV3IHNlY3Rpb24gNy4gIEkgdGhpbmsgaXQgd2lsbCBjYXVzZQ0K
PiBtdWNoIGxlc3MgY29uZnVzaW9uOyBub3JtYXRpdmUgYXBwZW5kaWNlcyBhcmUgbm90IGNvbW1v
biwgZXNwZWNpYWxseQ0KPiBzb21ldGhpbmcgc28gaW1wb3J0YW50IGFzIHRoZSBndWlkYW5jZS4N
Cg0KR29vZCBwb2ludC4gSWYgdGhlcmUgaXMgY29uc2Vuc3VzLCBJIHdpbGwgZG8gdGhhdC4NCg0K
SGVuZHJpaw0K


From nobody Fri Jan 22 10:31:38 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 321753A13DE for <spasm@ietfa.amsl.com>; Fri, 22 Jan 2021 10:31:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id el_8Rbe4MrTx for <spasm@ietfa.amsl.com>; Fri, 22 Jan 2021 10:31:35 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9221B3A13DF for <spasm@ietf.org>; Fri, 22 Jan 2021 10:31:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id EAC7A300BA5 for <spasm@ietf.org>; Fri, 22 Jan 2021 13:31:12 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id s-d501XUVN_R for <spasm@ietf.org>; Fri, 22 Jan 2021 13:31:11 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id B5A4D300B08; Fri, 22 Jan 2021 13:31:11 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <AM0PR10MB24188A9844583BC094B4B479FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
Date: Fri, 22 Jan 2021 13:31:12 -0500
Cc: "spasm@ietf.org" <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A0D61B4-1E5E-404D-948A-AF7CD60B99E9@vigilsec.com>
References: <161115903621.21831.6292824907492428494@ietfa.amsl.com> <2668BA25-2897-4735-948E-56D04375F924@vigilsec.com> <49CFFEC2-6340-406C-BF7F-50B1418461A1@akamai.com> <AM0PR10MB24187FBF28EF16487F9C0970FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <833900E8-11F3-4654-B2B8-DD51D1B97758@akamai.com> <AM0PR10MB241880324E91D01555A04A99FEA10@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <C69D92DB-E066-4049-9C78-A868C98A846D@sn3rd.com> <AM0PR10MB2418CF25FD1157481A3EDE07FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM> <ADF72E6E-E542-41AC-993C-27DD11AFF2A7@akamai.com> <AM0PR10MB24188A9844583BC094B4B479FEA00@AM0PR10MB2418.EURPRD10.PROD.OUTLOOK.COM>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/5aZPs6UtjWB2t_FZImKu6shzWXg>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cmp-algorithms-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 18:31:37 -0000

Hendrik:

>>>   I wanted to enlist the OIDs and where to find the details on =
relevant
>> algorithms in Sections 2-6.
>>    The specific guidance and profiles is located in Appendix A.
>>=20
>> I suggest you change Appendix A to be a new section 7.  I think it =
will cause
>> much less confusion; normative appendices are not common, especially
>> something so important as the guidance.
>=20
> Good point. If there is consensus, I will do that.

I think moving the MUST and SHOULD statements about the algorithms into =
a numbered section is a good idea.

Russ


From nobody Mon Jan 25 18:10:33 2021
Return-Path: <rdd@cert.org>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDB23A1AC9 for <spasm@ietfa.amsl.com>; Mon, 25 Jan 2021 18:10:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2C1G1jyMWi-d for <spasm@ietfa.amsl.com>; Mon, 25 Jan 2021 18:10:29 -0800 (PST)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 769403A1AC7 for <spasm@ietf.org>; Mon, 25 Jan 2021 18:10:29 -0800 (PST)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 10Q2AR10044916 for <spasm@ietf.org>; Mon, 25 Jan 2021 21:10:28 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 10Q2AR10044916
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1611627028; bh=hugGZbmsASTsDQX/jUvpA1dbd1xhrRJRiLp47318ppU=; h=From:To:Subject:Date:From; b=la56H3FXwNM9Gyut7eSE35toe0xa1JaSuIwMVWSGgHgiZ5NgXhzQ3jSSjaERB+aZ1 4Y0sDMRNlE9hhn+RqDJLvp5F0+Mq2wOdD7kCe5yA7xzgpTnOw7Q8I0MYvCVsCkdjAt D+72415+gwPQZYorn9euGAlmIHFefMEiGBqoUY1g=
Received: from MURIEL.ad.sei.cmu.edu (muriel.ad.sei.cmu.edu [147.72.252.47]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 10Q2ARrE029887 for <spasm@ietf.org>; Mon, 25 Jan 2021 21:10:27 -0500
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MURIEL.ad.sei.cmu.edu (147.72.252.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 25 Jan 2021 21:10:26 -0500
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Mon, 25 Jan 2021 21:10:26 -0500
From: Roman Danyliw <rdd@cert.org>
To: LAMPS WG <spasm@ietf.org>
Thread-Topic: AD Review: draft-ietf-lamps-cms-aes-gmac-alg-02
Thread-Index: AdbzfN5BmWxXMmZ4QHOOCC27Bji/LA==
Date: Tue, 26 Jan 2021 02:10:25 +0000
Message-ID: <0653df8b1e474cd98cc6e3f06ab69d6a@cert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.203.54]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/grCBD6XVl2P1gyBCKeTb5a4yE6s>
Subject: [lamps] AD Review: draft-ietf-lamps-cms-aes-gmac-alg-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 02:10:31 -0000

Hi!

I conducted an AD review draft-ietf-lamps-cms-aes-gmac-alg-02.  Thanks for =
the work to bring AES-GMAC to CMS.  Here is my feedback:

** Questions about the recommendation in Section 3.1 for a 12 octet tag has=
 come up a few times [1][2][3].  Thanks for adding the text in -02 to expla=
in the origin as being from RFC5084 per [1]. If we decide to go that way, [=
2] makes a good suggestion to also add it to the comments.  [3] acknowledge=
s the alignment with RFC5084 but speculates whether 13-year old guidance si=
nce applies. Like [3] I couldn't find any relevant NIST or RFCs to meaningf=
ully cite.  In addition to RFC5282, there is also RFC4543 which also recomm=
end 16-bytes for the nonce.  However, I'm sensitive to those requirements p=
otentially being protocol specific and CMS has a wider set of applications.=
  As an aside, this variability in application should be explicitly stated.=
 =20

Is the thinking with [4] to make support for 12 and 16 octets a MUST, with =
the 12 there for parity with RFC5084 and the 16 because we think that's the=
 right balance in 2021?

[1] https://mailarchive.ietf.org/arch/msg/spasm/KrmkF6kkbg8-pU4MpjgpTVmxzik=
/
[2] https://mailarchive.ietf.org/arch/msg/spasm/T9UhA9T9j85o6VYjT-9D2JnTEic=
/
[3] https://mailarchive.ietf.org/arch/msg/spasm/7qqXzNFuA1YDFnfHw8oL9OVK_Dc=
/
[4] https://mailarchive.ietf.org/arch/msg/spasm/g1-09MkwebIO3kI0T2sY5nBF2JM=
/

** Section 3.1.  Editorial. Clarifying text adding the specific CMS field n=
ame that carries the algorithm identifier.

OLD
   The AES-GMAC [AES][GCM] Message Authentication Code (MAC) algorithm
   uses one of the following algorithm identifiers;=20
NEW
   The AES-GMAC [AES][GCM] Message Authentication Code (MAC) algorithm
   uses one of the following algorithm identifiers in the AuthenticatedData=
 macAlgorithm field;

** Section 3.1.  Per "The nonce may have any number of bits between 8 and 2=
^64 ...", should this read 2^64 - 1?  Page 8 of [GCM]  (https://nvlpubs.nis=
t.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf) says "The bit l=
engths of the input strings to the authenticated encryption function shall =
meet the following requirements: ... 1 <=3D len(IV) <=3D 2^64-1"

** Section 3.1.  Typo.  s/field field/field/

Regards,
Roman


From nobody Tue Jan 26 14:52:11 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2F133A0B55 for <spasm@ietfa.amsl.com>; Tue, 26 Jan 2021 14:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVjQbx4vnqAR for <spasm@ietfa.amsl.com>; Tue, 26 Jan 2021 14:52:06 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEF3A3A0B53 for <spasm@ietf.org>; Tue, 26 Jan 2021 14:52:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 62690300B78 for <spasm@ietf.org>; Tue, 26 Jan 2021 17:52:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rDnkFy1Jkxqq for <spasm@ietf.org>; Tue, 26 Jan 2021 17:52:03 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 206B4300AEC for <spasm@ietf.org>; Tue, 26 Jan 2021 17:52:03 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Message-Id: <51C0C78E-CD70-4476-B6B1-FDC78C272F18@vigilsec.com>
Date: Tue, 26 Jan 2021 17:52:04 -0500
To: LAMPS <spasm@ietf.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Y-WpNJn38HGtHyONQJB0szWiHFM>
Subject: [lamps] LAMPS WG Virtual Interim on 28 January 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 22:52:10 -0000

LAMPS WG Virtual Interim on 28 January 2021

Since the LAMPS WG needs to re-charter to take on
draft-dkg-lamps-e2e-mail-guidance, this seems like a
good time to ask what other topics the group might
want to tackle.  Some have expressed interest in topics
related to the transition to PQ cryptographic algorithms.
This virtual interim on that will help determine what, if
anything, should be included in the LAMPS WG re-charter.


AGENDA

0)  Minute Taker, Jabber Scribe, Bluesheets

1)  Agenda Bash

2)  Position Presentations=20
    a)  Russ Housley
    b)  Max Pala
    c)  Mike Ounsworth
    d)  Antonio Vaira

3)  Open Discussion

4)  Wrap Up


=3D =3D =3D =3D =3D =3D =3D =3D =3D

WebEx:  =
https://ietf.webex.com/ietf/j.php?MTID=3Dmb6639fe2c67ce9a639fcb8701fa85e3c=

Notes:  https://codimd.ietf.org/notes-ietf-interim-2021-lamps-01-lamps#
Slides: =
https://datatracker.ietf.org/meeting/interim-2021-lamps-01/session/lamps
Jabber: xmpp:lamps@jabber.ietf.org


From nobody Tue Jan 26 14:56:07 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B191E3A0BCC for <spasm@ietfa.amsl.com>; Tue, 26 Jan 2021 14:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_rC0gbqLNAX for <spasm@ietfa.amsl.com>; Tue, 26 Jan 2021 14:56:03 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79ED43A0BBC for <spasm@ietf.org>; Tue, 26 Jan 2021 14:56:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 25774300B78 for <spasm@ietf.org>; Tue, 26 Jan 2021 17:56:01 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id N3PdUoCCN2E6 for <spasm@ietf.org>; Tue, 26 Jan 2021 17:55:59 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id CF731300AEC for <spasm@ietf.org>; Tue, 26 Jan 2021 17:55:59 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Tue, 26 Jan 2021 17:56:01 -0500
References: <51C0C78E-CD70-4476-B6B1-FDC78C272F18@vigilsec.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <51C0C78E-CD70-4476-B6B1-FDC78C272F18@vigilsec.com>
Message-Id: <AAB0C594-12EE-4455-9E6A-3A9574CD92D5@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/3iU8Fi_IaEv5K5w3VWu-qsxKNsU>
Subject: [lamps] Minute taker for LAMPS WG Virtual Interim on 28 January 2021?
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 22:56:06 -0000

If we can get a volunteer to the minutes now, we will not have to waste =
meeting time on that activity.  Anyone willing?

Russ


> On Jan 26, 2021, at 5:52 PM, Russ Housley <housley@vigilsec.com> =
wrote:
>=20
> LAMPS WG Virtual Interim on 28 January 2021
>=20
> Since the LAMPS WG needs to re-charter to take on
> draft-dkg-lamps-e2e-mail-guidance, this seems like a
> good time to ask what other topics the group might
> want to tackle.  Some have expressed interest in topics
> related to the transition to PQ cryptographic algorithms.
> This virtual interim on that will help determine what, if
> anything, should be included in the LAMPS WG re-charter.
>=20
>=20
> AGENDA
>=20
> 0)  Minute Taker, Jabber Scribe, Bluesheets
>=20
> 1)  Agenda Bash
>=20
> 2)  Position Presentations=20
>    a)  Russ Housley
>    b)  Max Pala
>    c)  Mike Ounsworth
>    d)  Antonio Vaira
>=20
> 3)  Open Discussion
>=20
> 4)  Wrap Up
>=20
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> WebEx:  =
https://ietf.webex.com/ietf/j.php?MTID=3Dmb6639fe2c67ce9a639fcb8701fa85e3c=

> Notes:  =
https://codimd.ietf.org/notes-ietf-interim-2021-lamps-01-lamps#
> Slides: =
https://datatracker.ietf.org/meeting/interim-2021-lamps-01/session/lamps
> Jabber: xmpp:lamps@jabber.ietf.org
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Tue Jan 26 15:49:01 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12AEC3A0DC0 for <spasm@ietfa.amsl.com>; Tue, 26 Jan 2021 15:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JAx0iY0cIroM for <spasm@ietfa.amsl.com>; Tue, 26 Jan 2021 15:48:59 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01A313A0C5B for <spasm@ietf.org>; Tue, 26 Jan 2021 15:48:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 5C51B300B93 for <spasm@ietf.org>; Tue, 26 Jan 2021 18:48:56 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id R1XX83YSWq7a for <spasm@ietf.org>; Tue, 26 Jan 2021 18:48:54 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 79D30300B6A; Tue, 26 Jan 2021 18:48:54 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <0653df8b1e474cd98cc6e3f06ab69d6a@cert.org>
Date: Tue, 26 Jan 2021 18:48:55 -0500
Cc: LAMPS WG <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <00A2D070-671B-4DCB-8716-E099B7A4CA3A@vigilsec.com>
References: <0653df8b1e474cd98cc6e3f06ab69d6a@cert.org>
To: "Roman D. Danyliw" <rdd@cert.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/zAWW6FkDRSDDB-Xv6TW0CyLTjy4>
Subject: Re: [lamps] AD Review: draft-ietf-lamps-cms-aes-gmac-alg-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 23:49:01 -0000

Roman:

On 23 Dec 2020, Quynh Dang from NIST said: "12 octets are fine for many =
use cases. "  Given this, keeping some compatibility with RFC 5084 seems =
wise.

I will make the other three changes.

Russ


> On Jan 25, 2021, at 9:10 PM, Roman Danyliw <rdd@cert.org> wrote:
>=20
> Hi!
>=20
> I conducted an AD review draft-ietf-lamps-cms-aes-gmac-alg-02.  Thanks =
for the work to bring AES-GMAC to CMS.  Here is my feedback:
>=20
> ** Questions about the recommendation in Section 3.1 for a 12 octet =
tag has come up a few times [1][2][3].  Thanks for adding the text in =
-02 to explain the origin as being from RFC5084 per [1]. If we decide to =
go that way, [2] makes a good suggestion to also add it to the comments. =
 [3] acknowledges the alignment with RFC5084 but speculates whether =
13-year old guidance since applies. Like [3] I couldn't find any =
relevant NIST or RFCs to meaningfully cite.  In addition to RFC5282, =
there is also RFC4543 which also recommend 16-bytes for the nonce.  =
However, I'm sensitive to those requirements potentially being protocol =
specific and CMS has a wider set of applications.  As an aside, this =
variability in application should be explicitly stated. =20
>=20
> Is the thinking with [4] to make support for 12 and 16 octets a MUST, =
with the 12 there for parity with RFC5084 and the 16 because we think =
that's the right balance in 2021?
>=20
> [1] =
https://mailarchive.ietf.org/arch/msg/spasm/KrmkF6kkbg8-pU4MpjgpTVmxzik/
> [2] =
https://mailarchive.ietf.org/arch/msg/spasm/T9UhA9T9j85o6VYjT-9D2JnTEic/
> [3] =
https://mailarchive.ietf.org/arch/msg/spasm/7qqXzNFuA1YDFnfHw8oL9OVK_Dc/
> [4] =
https://mailarchive.ietf.org/arch/msg/spasm/g1-09MkwebIO3kI0T2sY5nBF2JM/
>=20
> ** Section 3.1.  Editorial. Clarifying text adding the specific CMS =
field name that carries the algorithm identifier.
>=20
> OLD
>   The AES-GMAC [AES][GCM] Message Authentication Code (MAC) algorithm
>   uses one of the following algorithm identifiers;=20
> NEW
>   The AES-GMAC [AES][GCM] Message Authentication Code (MAC) algorithm
>   uses one of the following algorithm identifiers in the =
AuthenticatedData macAlgorithm field;
>=20
> ** Section 3.1.  Per "The nonce may have any number of bits between 8 =
and 2^64 ...", should this read 2^64 - 1?  Page 8 of [GCM]  =
(https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d=
.pdf) says "The bit lengths of the input strings to the authenticated =
encryption function shall meet the following requirements: ... 1 <=3D =
len(IV) <=3D 2^64-1"
>=20
> ** Section 3.1.  Typo.  s/field field/field/
>=20
> Regards,
> Roman
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Wed Jan 27 07:45:46 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 705763A09F6 for <spasm@ietfa.amsl.com>; Wed, 27 Jan 2021 07:45:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id od7h0dABap2w for <spasm@ietfa.amsl.com>; Wed, 27 Jan 2021 07:45:42 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8995E3A0A0B for <spasm@ietf.org>; Wed, 27 Jan 2021 07:45:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 00766300B9D for <spasm@ietf.org>; Wed, 27 Jan 2021 10:45:39 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 1aVm3v-qJ9pD for <spasm@ietf.org>; Wed, 27 Jan 2021 10:45:38 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 85BEE300AEC; Wed, 27 Jan 2021 10:45:38 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com>
Date: Wed, 27 Jan 2021 10:45:39 -0500
Cc: LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8E2C72E-A6FE-4E01-A79A-454DAC328367@vigilsec.com>
References: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com>
To: IAB <iab@iab.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/jbS0ZEm0PSM0XpnZTT83LKKd0qs>
Subject: [lamps] Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 15:45:44 -0000

Dear IAB:

The LAMPS WG has been discussing the incompatibility between ISO 14533-4 =
and OCSP with the update in RFC 8954.  We would like to make sure that =
ISO/TC 154, the technical committee that produced ISO 14533-4, is aware =
of the incompatibility.  To that end, we ask the IAB to send the =
attacked Liaison Statement.  We think that the IAB should send it =
because the IETF doe not have a liaison relationship with ISO/TC 154.

On behalf of the LAMPS WG,
 Russ

=3D=3D =3D=3D =3D=3D =3D=3D =3D=3D


FROM: IAB
TO: ISO/TC 154

The Internet Architecture Board would like to make sure that you are =
aware of the recent work by the at IETF LAMPS Working group =
(https://tools.ietf.org/wg/lamps/) that lead to RFC 8954 =
(https://www.rfc-editor..org/rfc/rfc8954.txt) that updates RFC 6960 =
(https://www.rfc-editor.org/rfc/rfc6960.txt). RFC 8954 limits the size =
of the OCSP Nonce extension to 32 octets to make the OCSP transactions =
more secure.

We understand that RFC 8954 may have a conflict with the way OCSP Nonce =
extension is proposed to be used in ISO 14533-4 and perhaps some other =
work which we are not aware of.

We had a discussion about the use case in the LAMPS working group =
recently. Based on how the OCSP nonce extension is used in the industry, =
it was recommended that a new OCSP extension should be used for the =
purpose of capturing OCSP response for long term validation of the =
signed documents.

We recognize that the IETF does not have a liaison relationship with =
ISO/TC 154; however, the IETF LAMPS working group would like to work =
with you to resolve this conflict in the best possible way.


From nobody Wed Jan 27 10:41:16 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D19D3A0CFA; Wed, 27 Jan 2021 10:41:15 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: spasm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: spasm@ietf.org
Message-ID: <161177287509.30770.12760522983722441560@ietfa.amsl.com>
Date: Wed, 27 Jan 2021 10:41:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ZrsEMYbi1brTJ5EhSyjuT67it0c>
Subject: [lamps] I-D Action: draft-ietf-lamps-cms-aes-gmac-alg-03.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 18:41:15 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Limited Additional Mechanisms for PKIX and SMIME WG of the IETF.

        Title           : Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS)
        Author          : Russ Housley
	Filename        : draft-ietf-lamps-cms-aes-gmac-alg-03.txt
	Pages           : 7
	Date            : 2021-01-27

Abstract:
   This document specifies the conventions for using the AES-GMAC
   Message Authentication Code algorithms with the Cryptographic Message
   Syntax (CMS) as specified in RFC 5652.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-aes-gmac-alg/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-lamps-cms-aes-gmac-alg-03
https://datatracker.ietf.org/doc/html/draft-ietf-lamps-cms-aes-gmac-alg-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lamps-cms-aes-gmac-alg-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Jan 27 10:42:39 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 523293A0CF4 for <spasm@ietfa.amsl.com>; Wed, 27 Jan 2021 10:42:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6SVEgjkOWqjs for <spasm@ietfa.amsl.com>; Wed, 27 Jan 2021 10:42:36 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D3A23A0CAC for <spasm@ietf.org>; Wed, 27 Jan 2021 10:42:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id B92E8300B98 for <spasm@ietf.org>; Wed, 27 Jan 2021 13:42:33 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id H4yXoSRTici3 for <spasm@ietf.org>; Wed, 27 Jan 2021 13:42:32 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 705C7300AE5 for <spasm@ietf.org>; Wed, 27 Jan 2021 13:42:32 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Wed, 27 Jan 2021 13:42:33 -0500
References: <161177287509.30770.12760522983722441560@ietfa.amsl.com>
To: LAMPS WG <spasm@ietf.org>
In-Reply-To: <161177287509.30770.12760522983722441560@ietfa.amsl.com>
Message-Id: <2F3D4CB3-C13E-4EAB-A0EE-6EED2AD57729@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/liGPcgxCcFuz0IApVoOlM7e6sPs>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cms-aes-gmac-alg-03.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 18:42:38 -0000

This revision resolves the comments from Roman.

Russ


> On Jan 27, 2021, at 1:41 PM, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Limited Additional Mechanisms for =
PKIX and SMIME WG of the IETF.
>=20
>        Title           : Using the AES-GMAC Algorithm with the =
Cryptographic Message Syntax (CMS)
>        Author          : Russ Housley
> 	Filename        : draft-ietf-lamps-cms-aes-gmac-alg-03.txt
> 	Pages           : 7
> 	Date            : 2021-01-27
>=20
> Abstract:
>   This document specifies the conventions for using the AES-GMAC
>   Message Authentication Code algorithms with the Cryptographic =
Message
>   Syntax (CMS) as specified in RFC 5652.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-aes-gmac-alg/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-lamps-cms-aes-gmac-alg-03
> =
https://datatracker.ietf.org/doc/html/draft-ietf-lamps-cms-aes-gmac-alg-03=

>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-lamps-cms-aes-gmac-alg-03=

>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jan 28 06:51:44 2021
Return-Path: <ietf@kuehlewind.net>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5455D3A156D; Thu, 28 Jan 2021 06:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBT0o7jYaDi2; Thu, 28 Jan 2021 06:51:40 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5DBF3A156B; Thu, 28 Jan 2021 06:51:40 -0800 (PST)
Received: from p200300dee71fe6009943a274f8257e41.dip0.t-ipconnect.de ([2003:de:e71f:e600:9943:a274:f825:7e41]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1l58dj-0006WW-Pd; Thu, 28 Jan 2021 15:51:19 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <F8E2C72E-A6FE-4E01-A79A-454DAC328367@vigilsec.com>
Date: Thu, 28 Jan 2021 15:51:18 +0100
Cc: IAB <iab@iab.org>, LAMPS <spasm@ietf.org>, Roman Danyliw <rdd@cert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0647E22E-22F8-473D-A351-C29CCF5D5285@kuehlewind.net>
References: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com> <F8E2C72E-A6FE-4E01-A79A-454DAC328367@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1611845500;95517c58;
X-HE-SMSGID: 1l58dj-0006WW-Pd
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/xnYr0LX_OUPFoURMqfbzN4eOITc>
Subject: Re: [lamps] [IAB] Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 14:51:42 -0000

Hi Russ, hi all,

The IAB would be ready to send this out.

There was one wording proposal by one of the IAB members:

OLD:

We understand that RFC 8954 may have a conflict with the way OCSP Nonce =
extension is proposed to be used in ISO 14533-4 and perhaps some other =
work which we are not aware of.

NEW:

We understand that the way OCSP Nonce extension is proposed to be used =
in ISO 14533-4 may conflict with RFC 8954. This may perhaps be true for =
other work that we are unaware of.

Please let me know if this editorial change is okay for you/the lamps =
group!

Do you already know who would be the right contact point at ISO/TC154? =
Is there a group list we should send this to? Or who would otherwise be =
the responsible contract person for TC 154?

Best,
Mirja



> On 27. Jan 2021, at 16:45, Russ Housley <housley@vigilsec.com> wrote:
>=20
> Dear IAB:
>=20
> The LAMPS WG has been discussing the incompatibility between ISO =
14533-4 and OCSP with the update in RFC 8954.  We would like to make =
sure that ISO/TC 154, the technical committee that produced ISO 14533-4, =
is aware of the incompatibility.  To that end, we ask the IAB to send =
the attacked Liaison Statement.  We think that the IAB should send it =
because the IETF doe not have a liaison relationship with ISO/TC 154.
>=20
> On behalf of the LAMPS WG,
> Russ
>=20
> =3D=3D =3D=3D =3D=3D =3D=3D =3D=3D
>=20
>=20
> FROM: IAB
> TO: ISO/TC 154
>=20
> The Internet Architecture Board would like to make sure that you are =
aware of the recent work by the at IETF LAMPS Working group =
(https://tools.ietf.org/wg/lamps/) that lead to RFC 8954 =
(https://www.rfc-editor..org/rfc/rfc8954.txt) that updates RFC 6960 =
(https://www.rfc-editor.org/rfc/rfc6960.txt). RFC 8954 limits the size =
of the OCSP Nonce extension to 32 octets to make the OCSP transactions =
more secure.
>=20
> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>=20
> We had a discussion about the use case in the LAMPS working group =
recently. Based on how the OCSP nonce extension is used in the industry, =
it was recommended that a new OCSP extension should be used for the =
purpose of capturing OCSP response for long term validation of the =
signed documents.
>=20
> We recognize that the IETF does not have a liaison relationship with =
ISO/TC 154; however, the IETF LAMPS working group would like to work =
with you to resolve this conflict in the best possible way.
>=20
>=20


From nobody Thu Jan 28 08:17:17 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EFDA3A15FE for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 08:17:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L78sgwz_dyoj for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 08:17:11 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C4553A15FA for <spasm@ietf.org>; Thu, 28 Jan 2021 08:17:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 1A387300B89 for <spasm@ietf.org>; Thu, 28 Jan 2021 11:17:09 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 2kW702WkWQYH for <spasm@ietf.org>; Thu, 28 Jan 2021 11:17:06 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 891E1300B86; Thu, 28 Jan 2021 11:17:06 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <0647E22E-22F8-473D-A351-C29CCF5D5285@kuehlewind.net>
Date: Thu, 28 Jan 2021 11:17:07 -0500
Cc: IAB <iab@iab.org>, LAMPS <spasm@ietf.org>, "Roman D. Danyliw" <rdd@cert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0601395-5B08-4B72-A247-409198B728C1@vigilsec.com>
References: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com> <F8E2C72E-A6FE-4E01-A79A-454DAC328367@vigilsec.com> <0647E22E-22F8-473D-A351-C29CCF5D5285@kuehlewind.net>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/k14zr4QLG0I20VezqcwiKsuDaIA>
Subject: Re: [lamps] [IAB] Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 16:17:15 -0000

Mirja:

I do not agree.  ISO 14533-4 is not a draft; it has already been =
approved.  So, "proposed" is not the right word.

Russ


> On Jan 28, 2021, at 9:51 AM, Mirja Kuehlewind <ietf@kuehlewind.net> =
wrote:
>=20
> Hi Russ, hi all,
>=20
> The IAB would be ready to send this out.
>=20
> There was one wording proposal by one of the IAB members:
>=20
> OLD:
>=20
> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>=20
> NEW:
>=20
> We understand that the way OCSP Nonce extension is proposed to be used =
in ISO 14533-4 may conflict with RFC 8954. This may perhaps be true for =
other work that we are unaware of.
>=20
> Please let me know if this editorial change is okay for you/the lamps =
group!
>=20
> Do you already know who would be the right contact point at ISO/TC154? =
Is there a group list we should send this to? Or who would otherwise be =
the responsible contract person for TC 154?
>=20
> Best,
> Mirja
>=20
>=20
>=20
>> On 27. Jan 2021, at 16:45, Russ Housley <housley@vigilsec.com> wrote:
>>=20
>> Dear IAB:
>>=20
>> The LAMPS WG has been discussing the incompatibility between ISO =
14533-4 and OCSP with the update in RFC 8954.  We would like to make =
sure that ISO/TC 154, the technical committee that produced ISO 14533-4, =
is aware of the incompatibility.  To that end, we ask the IAB to send =
the attacked Liaison Statement.  We think that the IAB should send it =
because the IETF doe not have a liaison relationship with ISO/TC 154.
>>=20
>> On behalf of the LAMPS WG,
>> Russ
>>=20
>> =3D=3D =3D=3D =3D=3D =3D=3D =3D=3D
>>=20
>>=20
>> FROM: IAB
>> TO: ISO/TC 154
>>=20
>> The Internet Architecture Board would like to make sure that you are =
aware of the recent work by the at IETF LAMPS Working group =
(https://tools.ietf.org/wg/lamps/) that lead to RFC 8954 =
(https://www.rfc-editor..org/rfc/rfc8954.txt) that updates RFC 6960 =
(https://www.rfc-editor.org/rfc/rfc6960.txt). RFC 8954 limits the size =
of the OCSP Nonce extension to 32 octets to make the OCSP transactions =
more secure.
>>=20
>> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>>=20
>> We had a discussion about the use case in the LAMPS working group =
recently. Based on how the OCSP nonce extension is used in the industry, =
it was recommended that a new OCSP extension should be used for the =
purpose of capturing OCSP response for long term validation of the =
signed documents.
>>=20
>> We recognize that the IETF does not have a liaison relationship with =
ISO/TC 154; however, the IETF LAMPS working group would like to work =
with you to resolve this conflict in the best possible way.
>>=20
>>=20
>=20


From nobody Thu Jan 28 08:28:15 2021
Return-Path: <ben@nostrum.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F17FB3A1621; Thu, 28 Jan 2021 08:28:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.279
X-Spam-Level: 
X-Spam-Status: No, score=-1.279 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, MAY_BE_FORGED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vD3jCYViz61S; Thu, 28 Jan 2021 08:28:10 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50E403A1614; Thu, 28 Jan 2021 08:28:10 -0800 (PST)
Received: from macbook-pro.localdomain (mta-70-120-133-87.satx.rr.com [70.120.133.87] (may be forged)) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 10SGRvvm016705 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 28 Jan 2021 10:27:59 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1611851282; bh=+AB0g4kC4922Zy9/7Lj9SJh6VU+FLd6UlECp0a6mSXY=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=COqbWIJefeJwRMrunAeWwyIxY8bnsyyFQv7+jNvZvPYrqJYKxLRmWa2tnxzP+I9dt uEHolpXdDH3NzTQ99zHEkr1qtteYGxyzZSf0rPwP2MuvQiPNa16tainbGQ+0jd9c+L 0S/Gt8vGOXdi7UY/W/clDeJeX0D2TCm2e+TQFZb8=
X-Authentication-Warning: raven.nostrum.com: Host mta-70-120-133-87.satx.rr.com [70.120.133.87] (may be forged) claimed to be macbook-pro.localdomain
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <B0601395-5B08-4B72-A247-409198B728C1@vigilsec.com>
Date: Thu, 28 Jan 2021 10:27:51 -0600
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, LAMPS <spasm@ietf.org>, "Roman D. Danyliw" <rdd@cert.org>, IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C318FB23-86E5-43CC-BEC6-57A3CF5D4945@nostrum.com>
References: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com> <F8E2C72E-A6FE-4E01-A79A-454DAC328367@vigilsec.com> <0647E22E-22F8-473D-A351-C29CCF5D5285@kuehlewind.net> <B0601395-5B08-4B72-A247-409198B728C1@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/nF3BXQZflgj085b-arz6MGaV3r4>
Subject: Re: [lamps] [IAB] Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 16:28:13 -0000

Hi Russ,

The phrase =E2=80=9Cis proposed to be used=E2=80=9D was from the =
original language. That being said, should that just change to =E2=80=9Cis=
 used=E2=80=9D?

Thanks!

Ben.

> On Jan 28, 2021, at 10:17 AM, Russ Housley <housley@vigilsec.com> =
wrote:
>=20
> Mirja:
>=20
> I do not agree.  ISO 14533-4 is not a draft; it has already been =
approved.  So, "proposed" is not the right word.
>=20
> Russ
>=20
>=20
>> On Jan 28, 2021, at 9:51 AM, Mirja Kuehlewind <ietf@kuehlewind.net> =
wrote:
>>=20
>> Hi Russ, hi all,
>>=20
>> The IAB would be ready to send this out.
>>=20
>> There was one wording proposal by one of the IAB members:
>>=20
>> OLD:
>>=20
>> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>>=20
>> NEW:
>>=20
>> We understand that the way OCSP Nonce extension is proposed to be =
used in ISO 14533-4 may conflict with RFC 8954. This may perhaps be true =
for other work that we are unaware of.
>>=20
>> Please let me know if this editorial change is okay for you/the lamps =
group!
>>=20
>> Do you already know who would be the right contact point at =
ISO/TC154? Is there a group list we should send this to? Or who would =
otherwise be the responsible contract person for TC 154?
>>=20
>> Best,
>> Mirja
>>=20
>>=20
>>=20
>>> On 27. Jan 2021, at 16:45, Russ Housley <housley@vigilsec.com> =
wrote:
>>>=20
>>> Dear IAB:
>>>=20
>>> The LAMPS WG has been discussing the incompatibility between ISO =
14533-4 and OCSP with the update in RFC 8954.  We would like to make =
sure that ISO/TC 154, the technical committee that produced ISO 14533-4, =
is aware of the incompatibility.  To that end, we ask the IAB to send =
the attacked Liaison Statement.  We think that the IAB should send it =
because the IETF doe not have a liaison relationship with ISO/TC 154.
>>>=20
>>> On behalf of the LAMPS WG,
>>> Russ
>>>=20
>>> =3D=3D =3D=3D =3D=3D =3D=3D =3D=3D
>>>=20
>>>=20
>>> FROM: IAB
>>> TO: ISO/TC 154
>>>=20
>>> The Internet Architecture Board would like to make sure that you are =
aware of the recent work by the at IETF LAMPS Working group =
(https://tools.ietf.org/wg/lamps/) that lead to RFC 8954 =
(https://www.rfc-editor..org/rfc/rfc8954.txt) that updates RFC 6960 =
(https://www.rfc-editor.org/rfc/rfc6960.txt). RFC 8954 limits the size =
of the OCSP Nonce extension to 32 octets to make the OCSP transactions =
more secure.
>>>=20
>>> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>>>=20
>>> We had a discussion about the use case in the LAMPS working group =
recently. Based on how the OCSP nonce extension is used in the industry, =
it was recommended that a new OCSP extension should be used for the =
purpose of capturing OCSP response for long term validation of the =
signed documents.
>>>=20
>>> We recognize that the IETF does not have a liaison relationship with =
ISO/TC 154; however, the IETF LAMPS working group would like to work =
with you to resolve this conflict in the best possible way.
>>>=20
>>>=20
>>=20
>=20


From nobody Thu Jan 28 08:44:55 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 908883A0AA1 for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 08:44:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZDI7zdTUD0LM for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 08:44:51 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C7563A0A93 for <spasm@ietf.org>; Thu, 28 Jan 2021 08:44:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 06040300BD0 for <spasm@ietf.org>; Thu, 28 Jan 2021 11:44:49 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ujXD_qtzWEG4 for <spasm@ietf.org>; Thu, 28 Jan 2021 11:44:45 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 84DA0300B86; Thu, 28 Jan 2021 11:44:45 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <C318FB23-86E5-43CC-BEC6-57A3CF5D4945@nostrum.com>
Date: Thu, 28 Jan 2021 11:44:46 -0500
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, LAMPS <spasm@ietf.org>, "Roman D. Danyliw" <rdd@cert.org>, IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <371E8BA0-8F33-4708-AB84-2ABABDDF4207@vigilsec.com>
References: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com> <F8E2C72E-A6FE-4E01-A79A-454DAC328367@vigilsec.com> <0647E22E-22F8-473D-A351-C29CCF5D5285@kuehlewind.net> <B0601395-5B08-4B72-A247-409198B728C1@vigilsec.com> <C318FB23-86E5-43CC-BEC6-57A3CF5D4945@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/CPy3EUeZmAS4G2mEkeXd2UUG8Es>
Subject: Re: [lamps] [IAB] Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 16:44:54 -0000

Ben:

Yes, that is better.  However, it is in conflict because the use exceeds =
32 octets, so I suggest:

> We understand that the way OCSP Nonce extension is used in ISO 14533-4 =
conflicts with RFC 8954. This may perhaps be true for other work that we =
are unaware of.


Russ


> On Jan 28, 2021, at 11:27 AM, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Hi Russ,
>=20
> The phrase =E2=80=9Cis proposed to be used=E2=80=9D was from the =
original language. That being said, should that just change to =E2=80=9Cis=
 used=E2=80=9D?
>=20
> Thanks!
>=20
> Ben.
>=20
>> On Jan 28, 2021, at 10:17 AM, Russ Housley <housley@vigilsec.com> =
wrote:
>>=20
>> Mirja:
>>=20
>> I do not agree.  ISO 14533-4 is not a draft; it has already been =
approved.  So, "proposed" is not the right word.
>>=20
>> Russ
>>=20
>>=20
>>> On Jan 28, 2021, at 9:51 AM, Mirja Kuehlewind <ietf@kuehlewind.net> =
wrote:
>>>=20
>>> Hi Russ, hi all,
>>>=20
>>> The IAB would be ready to send this out.
>>>=20
>>> There was one wording proposal by one of the IAB members:
>>>=20
>>> OLD:
>>>=20
>>> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>>>=20
>>> NEW:
>>>=20
>>> We understand that the way OCSP Nonce extension is proposed to be =
used in ISO 14533-4 may conflict with RFC 8954. This may perhaps be true =
for other work that we are unaware of.
>>>=20
>>> Please let me know if this editorial change is okay for you/the =
lamps group!
>>>=20
>>> Do you already know who would be the right contact point at =
ISO/TC154? Is there a group list we should send this to? Or who would =
otherwise be the responsible contract person for TC 154?
>>>=20
>>> Best,
>>> Mirja
>>>=20
>>>=20
>>>=20
>>>> On 27. Jan 2021, at 16:45, Russ Housley <housley@vigilsec.com> =
wrote:
>>>>=20
>>>> Dear IAB:
>>>>=20
>>>> The LAMPS WG has been discussing the incompatibility between ISO =
14533-4 and OCSP with the update in RFC 8954.  We would like to make =
sure that ISO/TC 154, the technical committee that produced ISO 14533-4, =
is aware of the incompatibility.  To that end, we ask the IAB to send =
the attacked Liaison Statement.  We think that the IAB should send it =
because the IETF doe not have a liaison relationship with ISO/TC 154.
>>>>=20
>>>> On behalf of the LAMPS WG,
>>>> Russ
>>>>=20
>>>> =3D=3D =3D=3D =3D=3D =3D=3D =3D=3D
>>>>=20
>>>>=20
>>>> FROM: IAB
>>>> TO: ISO/TC 154
>>>>=20
>>>> The Internet Architecture Board would like to make sure that you =
are aware of the recent work by the at IETF LAMPS Working group =
(https://tools.ietf.org/wg/lamps/) that lead to RFC 8954 =
(https://www.rfc-editor..org/rfc/rfc8954.txt) that updates RFC 6960 =
(https://www.rfc-editor.org/rfc/rfc6960.txt). RFC 8954 limits the size =
of the OCSP Nonce extension to 32 octets to make the OCSP transactions =
more secure.
>>>>=20
>>>> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>>>>=20
>>>> We had a discussion about the use case in the LAMPS working group =
recently. Based on how the OCSP nonce extension is used in the industry, =
it was recommended that a new OCSP extension should be used for the =
purpose of capturing OCSP response for long term validation of the =
signed documents.
>>>>=20
>>>> We recognize that the IETF does not have a liaison relationship =
with ISO/TC 154; however, the IETF LAMPS working group would like to =
work with you to resolve this conflict in the best possible way.
>>>>=20
>>>>=20
>>>=20
>>=20
>=20


From nobody Thu Jan 28 08:59:24 2021
Return-Path: <kaduk@mit.edu>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCCBC3A0B20 for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 08:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TJ8lnRvM8DkF for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 08:59:21 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0856F3A0B29 for <spasm@ietf.org>; Thu, 28 Jan 2021 08:59:20 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 10SGxEf9009104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <spasm@ietf.org>; Thu, 28 Jan 2021 11:59:19 -0500
Date: Thu, 28 Jan 2021 08:59:14 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: LAMPS WG <spasm@ietf.org>
Message-ID: <20210128165914.GY21@kduck.mit.edu>
References: <20210128154420.4B40EF40715@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210128154420.4B40EF40715@rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/q50aoWUlkTOMBdW50sD8ea5c1iU>
Subject: [lamps] Fwd: [Technical Errata Reported] RFC5280 (6414)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 16:59:23 -0000

FYI there's some ongoing discussion about this report on the pkix@ list:
https://mailarchive.ietf.org/arch/browse/pkix/

-Ben

On Thu, Jan 28, 2021 at 07:44:20AM -0800, RFC Errata System wrote:
> The following errata report has been submitted for RFC5280,
> "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6414
> 
> --------------------------------------
> Type: Technical
> Reported by: Rob Stradling <rob@sectigo.com>
> 
> Section: 4.2.1.12
> 
> Original Text
> -------------
>    id-kp-serverAuth             OBJECT IDENTIFIER ::= { id-kp 1 }
>    -- TLS WWW server authentication
>    -- Key usage bits that may be consistent: digitalSignature,
>    -- keyEncipherment or keyAgreement
> 
> Corrected Text
> --------------
>    id-kp-serverAuth             OBJECT IDENTIFIER ::= { id-kp 1 }
>    -- TLS WWW server authentication
>    -- Key usage bits that may be consistent: digitalSignature
>    -- and/or (keyEncipherment or keyAgreement)
> 
> Notes
> -----
> In https://github.com/zmap/zlint/issues/553 there's been some disagreement and confusion about how to correctly interpret the "or" in the Original Text.  "You can only set one of these three bits" is one interpretation, and it's hard to argue that this interpretation is inconsistent with the Original Text.
> 
> However, digitalSignature+keyEncipherment makes sense for an RSA leaf certificate, and digitalSignature+keyAgreement makes sense for an ECC leaf certificate.  Both are widely used, to enable ephemeral and non-ephemeral TLS ciphersuites in conjunction with a single server certificate.
> 
> Given that RFC5480 section 3 explicitly permits digitalSignature+keyAgreement in an ECC leaf certificate, I think it's likely that my proposed Corrected Text conveys the RFC5280 authors' intended meaning.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC5280 (draft-ietf-pkix-rfc3280bis-11)
> --------------------------------------
> Title               : Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
> Publication Date    : May 2008
> Author(s)           : D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R. Housley, W. Polk
> Category            : PROPOSED STANDARD
> Source              : Public-Key Infrastructure (X.509)
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG


From nobody Thu Jan 28 09:01:00 2021
Return-Path: <ben@nostrum.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFF713A0C55; Thu, 28 Jan 2021 09:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.279
X-Spam-Level: 
X-Spam-Status: No, score=-1.279 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, MAY_BE_FORGED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9S4KUGwegvp; Thu, 28 Jan 2021 09:00:57 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CF113A0B20; Thu, 28 Jan 2021 09:00:57 -0800 (PST)
Received: from macbook-pro.localdomain (mta-70-120-133-87.satx.rr.com [70.120.133.87] (may be forged)) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 10SH0nvu028497 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 28 Jan 2021 11:00:50 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1611853252; bh=Z+/9k4EIeGnToDeBAVLc6kbW6D75lxvvpL4jNuVqfQw=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Szg7Ap/J24cTEaZ4E6mD0UhZZttQLcqBRBm1FL8PQMw7o5TqyYDxOHwngnPuthi6L h9vXijm7RZEwfBTbyFC/pgWU3KsAW9p6P68grygINeaXKomyiyqv6NqlRCjZmnRWL0 vMBNOAwpHvLY066ZCYI/sgg8MPmM2SneZU+9P2JM=
X-Authentication-Warning: raven.nostrum.com: Host mta-70-120-133-87.satx.rr.com [70.120.133.87] (may be forged) claimed to be macbook-pro.localdomain
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <371E8BA0-8F33-4708-AB84-2ABABDDF4207@vigilsec.com>
Date: Thu, 28 Jan 2021 11:00:43 -0600
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, LAMPS <spasm@ietf.org>, "Roman D. Danyliw" <rdd@cert.org>, IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BE0FA11-DEAE-45A3-925D-2C9A353B0F91@nostrum.com>
References: <14DC502F-8418-4DF4-B866-B6B8F162CB9D@vigilsec.com> <F8E2C72E-A6FE-4E01-A79A-454DAC328367@vigilsec.com> <0647E22E-22F8-473D-A351-C29CCF5D5285@kuehlewind.net> <B0601395-5B08-4B72-A247-409198B728C1@vigilsec.com> <C318FB23-86E5-43CC-BEC6-57A3CF5D4945@nostrum.com> <371E8BA0-8F33-4708-AB84-2ABABDDF4207@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/OMzh8WMJbxp4z883jhAnKi0gPt8>
Subject: Re: [lamps] [IAB] Liaison Statement to ISO/TC 154
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 17:00:59 -0000

Works for me.

Ben.

> On Jan 28, 2021, at 10:44 AM, Russ Housley <housley@vigilsec.com> =
wrote:
>=20
> Ben:
>=20
> Yes, that is better.  However, it is in conflict because the use =
exceeds 32 octets, so I suggest:
>=20
>> We understand that the way OCSP Nonce extension is used in ISO =
14533-4 conflicts with RFC 8954. This may perhaps be true for other work =
that we are unaware of.
>=20
>=20
> Russ
>=20
>=20
>> On Jan 28, 2021, at 11:27 AM, Ben Campbell <ben@nostrum.com> wrote:
>>=20
>> Hi Russ,
>>=20
>> The phrase =E2=80=9Cis proposed to be used=E2=80=9D was from the =
original language. That being said, should that just change to =E2=80=9Cis=
 used=E2=80=9D?
>>=20
>> Thanks!
>>=20
>> Ben.
>>=20
>>> On Jan 28, 2021, at 10:17 AM, Russ Housley <housley@vigilsec.com> =
wrote:
>>>=20
>>> Mirja:
>>>=20
>>> I do not agree.  ISO 14533-4 is not a draft; it has already been =
approved.  So, "proposed" is not the right word.
>>>=20
>>> Russ
>>>=20
>>>=20
>>>> On Jan 28, 2021, at 9:51 AM, Mirja Kuehlewind <ietf@kuehlewind.net> =
wrote:
>>>>=20
>>>> Hi Russ, hi all,
>>>>=20
>>>> The IAB would be ready to send this out.
>>>>=20
>>>> There was one wording proposal by one of the IAB members:
>>>>=20
>>>> OLD:
>>>>=20
>>>> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>>>>=20
>>>> NEW:
>>>>=20
>>>> We understand that the way OCSP Nonce extension is proposed to be =
used in ISO 14533-4 may conflict with RFC 8954. This may perhaps be true =
for other work that we are unaware of.
>>>>=20
>>>> Please let me know if this editorial change is okay for you/the =
lamps group!
>>>>=20
>>>> Do you already know who would be the right contact point at =
ISO/TC154? Is there a group list we should send this to? Or who would =
otherwise be the responsible contract person for TC 154?
>>>>=20
>>>> Best,
>>>> Mirja
>>>>=20
>>>>=20
>>>>=20
>>>>> On 27. Jan 2021, at 16:45, Russ Housley <housley@vigilsec.com> =
wrote:
>>>>>=20
>>>>> Dear IAB:
>>>>>=20
>>>>> The LAMPS WG has been discussing the incompatibility between ISO =
14533-4 and OCSP with the update in RFC 8954.  We would like to make =
sure that ISO/TC 154, the technical committee that produced ISO 14533-4, =
is aware of the incompatibility.  To that end, we ask the IAB to send =
the attacked Liaison Statement.  We think that the IAB should send it =
because the IETF doe not have a liaison relationship with ISO/TC 154.
>>>>>=20
>>>>> On behalf of the LAMPS WG,
>>>>> Russ
>>>>>=20
>>>>> =3D=3D =3D=3D =3D=3D =3D=3D =3D=3D
>>>>>=20
>>>>>=20
>>>>> FROM: IAB
>>>>> TO: ISO/TC 154
>>>>>=20
>>>>> The Internet Architecture Board would like to make sure that you =
are aware of the recent work by the at IETF LAMPS Working group =
(https://tools.ietf.org/wg/lamps/) that lead to RFC 8954 =
(https://www.rfc-editor..org/rfc/rfc8954.txt) that updates RFC 6960 =
(https://www.rfc-editor.org/rfc/rfc6960.txt). RFC 8954 limits the size =
of the OCSP Nonce extension to 32 octets to make the OCSP transactions =
more secure.
>>>>>=20
>>>>> We understand that RFC 8954 may have a conflict with the way OCSP =
Nonce extension is proposed to be used in ISO 14533-4 and perhaps some =
other work which we are not aware of.
>>>>>=20
>>>>> We had a discussion about the use case in the LAMPS working group =
recently. Based on how the OCSP nonce extension is used in the industry, =
it was recommended that a new OCSP extension should be used for the =
purpose of capturing OCSP response for long term validation of the =
signed documents.
>>>>>=20
>>>>> We recognize that the IETF does not have a liaison relationship =
with ISO/TC 154; however, the IETF LAMPS working group would like to =
work with you to resolve this conflict in the best possible way.
>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20


From nobody Thu Jan 28 11:27:41 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11E0F3A16AF for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 11:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkN_Q7XY72-r for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 11:27:39 -0800 (PST)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2098.outbound.protection.outlook.com [40.107.220.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8D393A1623 for <spasm@ietf.org>; Thu, 28 Jan 2021 11:27:38 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QdJAR0H36wBFSV0WFujIjL1FTjESLRtWJaD5RKmzDIzhwBqrAcz/iyqEcDtwK8XEwLBHhFJOj1eQOEzWaCrTTZWHRHuxgvsUhrYKXBkqG8/pMKnd0CM3JjH6n+j/EVpfAAarNnmNt7FKKWSJ6HttyTtp1CJZ3vEZ1XnYSNbKQc9SiUkdXt4RXYFLGq1Vf1xwYZrFB+JuRW70fX9/lsuluBpkCfcPCYpuctS6GE5dBNrp/Bc2g8uiPW2JJVeY9QSHiwnKYKpB3W8YQzzABYJaqu3KC7mAflDsnI5nnskH6oI7bmi0PpNTEovQx0UFtlY7Gx1Em/Yg50KhmPIB2zL9gg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NZBRuJHPnUCwLwf7+MNTD2/0pGNSvDrowMyo5aWsAus=; b=G5vqgjg5AXge5yCj+LPD+WhYwuUf6z5/v51pb68EIoKm7lS+m9D+bwlogi0L7+7BxXDChTYyvTJRnDnqt9StEkX0eNXozP0KMJuzo6ClvD9IDccB1FVx6oEuQnKFAHZKsKg2A7EaQS8uubwP4fztOb+DkHq5tg/ivogiBi8WITyEvcLEYbKHznmBAH1B6jGeBQ2ct1d7ushT9IJyhdrLR+xlrvXmD0+WdDT4Yu+chxWKn0g52V2CjTv8up343gCR5xj1A/N7ZV5lpgdfczh6RLBLEdt8aubU6H9k7WzUwLVZweIZcsGcyOJyTdfWAsDK1YKQdjvFSGC3twECAIUNTg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NZBRuJHPnUCwLwf7+MNTD2/0pGNSvDrowMyo5aWsAus=; b=NpXtPmjxqYTwJSMYcA+B/PBQPgz4VTSebm+09gPp1QFdG0QCqcMaMOdvhcflPkqlKIGLOCRsqtCPMecIDaoVNpigEnyR+5059+ciJc6cTaD7YVUWVOApPSKopFEViqcqwPwYdKooQaVNJucTXv0IYdjf0/ZWGyqtdugPslIC+fz2IEPgcPyUxHbAIcl69Nxki7ESKIau5KI/S+PNYqxR3p1RZNj2FOpGNLrC+zusbpFHWhWdaMJBBMjIeWB2gPJDw69q647fg1Us/tKuGiovTH4KzKqXJFNtoiW+/3LlM3IEiQ8EFHXdI1+PjXYnzG3GZS7OzzMJEtBRLq6gdRcIMQ==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB3546.namprd11.prod.outlook.com (2603:10b6:5:13e::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.16; Thu, 28 Jan 2021 19:27:37 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::a816:b4fb:846e:9417]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::a816:b4fb:846e:9417%6]) with mapi id 15.20.3784.019; Thu, 28 Jan 2021 19:27:37 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: 'LAMPS' <spasm@ietf.org>
Thread-Topic: Proposed re-charter text for hybrid and dual crypto modes
Thread-Index: Adb1q3GYntimtkHXQaOdOOEUbm7smw==
Date: Thu, 28 Jan 2021 19:27:36 +0000
Message-ID: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [4.19.72.62]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 406e6934-31fd-432f-0180-08d8c3c2c511
x-ms-traffictypediagnostic: DM6PR11MB3546:
x-microsoft-antispam-prvs: <DM6PR11MB3546573123075698861C37479FBA9@DM6PR11MB3546.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: r66fz+AJJzNaf2mQkFr49eDM3uAi8kUXN74rTyGERc+39d/fM0UGdxUhEQHkfbKidH5nTj3fi9ShFVquyqUDAmfclRkz8TGFjuFA1tJy/MYOPLUjVcD3nV3HmiqVKjoJJiYh1DpzhbbP//06ncYsHUOiBwBO65T2EW4Ie1ultTp4Q1ufwdosB3cQs0GdO9jTo3DUZrUN3Z4lQ5IEiyngleQrW/8DUF1aemR+IwSSy7m0Qim6qLBKaEA5xts/TJU0NYQcarVGbvpmCJJFz8QMd7G2kO6mbcPMKVVu8Aa5obzK2i/0UCyr5AOsb9B+YM8RIw2EfstuLkX2BobOJxaPVB0LG+Gv1xkaX8fDFNw4HtLwsh8RcmtFUHU0rjW5YmV6+ee9BUTkuZtr8d1AwrFR3OZhrb+O9oLmqZQjoSMvGSDl/tuG21QZk6FtbC4qi1yNSDigKqn4meWsgITcR5Bnnb6LIM73Ir/rrByawtbOwPXAWfGo4Fi+CPmDRgoO7KFuQ6YHgfZz7nqM/wAwWRV/3A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(376002)(366004)(396003)(346002)(136003)(83380400001)(478600001)(7696005)(71200400001)(9686003)(86362001)(316002)(76116006)(66556008)(55016002)(26005)(2906002)(66446008)(186003)(66476007)(64756008)(8936002)(6506007)(33656002)(52536014)(8676002)(4744005)(5660300002)(66946007)(6916009); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?86qq/D3+cUcXBjA6ilUwnyXDxUk740C2szNycUvCE3dotG2RN9sa6DiAor?= =?iso-8859-1?Q?TGZuTxaFFJf8rhk+x4scl7uWvAsX/HUnTEuU2FAgZX/8WiP3oahl7VZ8ks?= =?iso-8859-1?Q?bkx+lIkG6Bx/UC3ic6ZkUBLv0RW6mdOcIwJ+3UJPzGA5imkCFqoSXokiLM?= =?iso-8859-1?Q?YjUwPlrD7opHx2HKpR0/GfXTVFRGN9STqAahoH02y3SXwFuA0ACpeme+R/?= =?iso-8859-1?Q?Eb4bpbKoNxlQ06hfH4M2nOaoYD+Cf4M/53dO5zJ4IHnlaTb521UMiEYsnH?= =?iso-8859-1?Q?qG/ZUnl42xfFCoisRN0pcAMeF6g8QwGfbMx+AlkdvsXEFwHlbsMlDgTNOp?= =?iso-8859-1?Q?RRQRPTiOBmLCaszF8Hr5S2V8XksD2q4JkyQf2XT/HfLgyCZQ22/zn1oLOz?= =?iso-8859-1?Q?hNJIOuPkqjE8eu5lmUYKfjsMKk79HGCY/kLpE2gY9ANwhzidfIiLHdQVpJ?= =?iso-8859-1?Q?xIY4FiPcCnRd6LmBAiwKf1bBOrJMPxT7RKLwsWPjaSHqrIOJWWuJw2bvH7?= =?iso-8859-1?Q?7Z1jvn7gteqY7SsH0Tp7GTwNUdl36GEKIWnjRcaXe6ZlAkW4cemLHog89i?= =?iso-8859-1?Q?/HGK8ynTA9+3k6n8YhaSnbaUS2p9rnl1HHuLIcXML5M/nR7iXDfP52GfW7?= =?iso-8859-1?Q?Vvd50zPl1qkCJU8PehqRr/Gl1poFUq1UgzWF8VJk/pS93Z1SY4SoORwomA?= =?iso-8859-1?Q?UM+OR8iyHGQQmN14wzw6NliAXSeaa9GUwuBTkIXnoHSkpTbALx+/N70vel?= =?iso-8859-1?Q?wMs5iWy3IjwNy5YoyKtKFphA1Axhq5K1dniTf1Pm9Y+nCncnDq0i1W0r0c?= =?iso-8859-1?Q?S1Q6OsTMQVWh2d3dlOVR05UufpJB6vDF6+/bxo5o1IkXhxM/b2CjGX3Sgq?= =?iso-8859-1?Q?NxuTXLoLZPN0tZgB4ngbuZXCqJGa5p+gsrf2CJSfw5jnTA8wZ2kHsm0WKL?= =?iso-8859-1?Q?9vwLOVFp07t6dExD44D9SDBbCk1/Sdu0/w5Dd++7hcNTPgcnHADN9YM/SM?= =?iso-8859-1?Q?85NpCCC76f3vnOFScEWv6NoIxJ0gCGz7P82BwdvYHZn2YAYp3r9DSImWpo?= =?iso-8859-1?Q?+HHIV/AwEk2wvaqh1Zbo6UE=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 406e6934-31fd-432f-0180-08d8c3c2c511
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jan 2021 19:27:36.9463 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: GKFtwAbdUYb3QIFjH4AfAwfF+6p/7BMDpS499nMYFeV0o2YE0GYhSECaC3gs7LZ3uPZDe4QpEyy66yzperV3Mu1R2ULrBXvq2qXNCY9nbi0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3546
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/-NmenDdia5hHlZyldHs_JENpv_Y>
Subject: [lamps] Proposed re-charter text for hybrid and dual crypto modes
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 19:27:40 -0000

Proposed charter text:

Post-quantum cryptography (PQC) will require a transition period in some wa=
ys similar to previous crypto migrations, but unique in that timelines requ=
ire deployment of PQC before cryptographers have full confidence in the rep=
lacement algorithms. NIST has called for transition mechanisms that "layer"=
 traditional and PQ crypto together, referred to as "hybrid key establishme=
nt" and "dual signatures". The LAMPS working group will update documents pr=
oduced by the=A0PKIX and S/MIME WG=A0to support hybrid key establishment, e=
ncryption, and dual signature mechanisms.

---
Mike Ounsworth
Software Security Architect, Entrust


From nobody Thu Jan 28 12:04:52 2021
Return-Path: <sean@sn3rd.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B6A3A16D0 for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 12:04:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u_CYycXn3gaj for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 12:04:49 -0800 (PST)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03BA33A16CD for <spasm@ietf.org>; Thu, 28 Jan 2021 12:04:48 -0800 (PST)
Received: by mail-qk1-x72a.google.com with SMTP id t63so6577806qkc.1 for <spasm@ietf.org>; Thu, 28 Jan 2021 12:04:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kch8vPYRvvUUh7R6YgjvL9852BmaIPlY96mGO3cKEZI=; b=HvqjBfEks0q/TBbjhVOObbSJrKaA5ZQ7McRs10dDqW7H7ZalF0/7+z4BHNQw4CR8BD EffAf5/jP2lEbsB13xqxmgGrdG1Zf5fWdxtiUygIzsQ2SNqDa3x5nmLbQeZKN/RS0PZH CatAretnBnDq00Mixth8JET2UPtgDHaoKQt0s=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kch8vPYRvvUUh7R6YgjvL9852BmaIPlY96mGO3cKEZI=; b=Sj3HgOvidqSEKLETb1lRsNkcVl9XySpfnwAq3XhkT2Kh+bi1k9xPcL39uWgkt5b9/8 IDYb4TMDjliI5sN7s6ibDSAIKTy0Aq74bRhAVQhw9622ckzxPBfRx+YGEZ0XJBe3beS9 EosgoQrKDi6xpL/1aIdgxX0fyucL5lRq03lz6oBHSYiJxSV4eVXW51bb2PEN/QqQIFY+ FoOEyheb6A1M5drUj66NFnxVRv3smfKZCWdpPhpTnjt8afsnfhHTERlU+lPAz8SkzyWV Yh+CP+E+PGzVQAL080CB2i3RhjcK0Dy3KrOz/zIWAj7B6ncuyNdJR1JCJBMPAHNH6oLv meFQ==
X-Gm-Message-State: AOAM533qfBVzyUQc4v9QiMRXyh8P/hfpaSlGyPpT888UDkLhsVy2D6H9 DL8DxaHf2yvaW6F2NdoLPZgy1EtwAf9b9A==
X-Google-Smtp-Source: ABdhPJzpntuRpNdUPi4Ia4C6XC/EP6X7sD32NoaxOW+UZadVe1SSS12dHs9E9Lq/7KvF2I+Noj6LTg==
X-Received: by 2002:a37:9bca:: with SMTP id d193mr931730qke.369.1611864287933;  Thu, 28 Jan 2021 12:04:47 -0800 (PST)
Received: from [192.168.1.152] (pool-108-31-39-252.washdc.fios.verizon.net. [108.31.39.252]) by smtp.gmail.com with ESMTPSA id p11sm4114175qtb.62.2021.01.28.12.04.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jan 2021 12:04:46 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
Date: Thu, 28 Jan 2021 15:04:44 -0500
Cc: LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1BE0BD5D-BD11-40E7-87F5-61EE49AAF1FD@sn3rd.com>
References: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
To: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/SaK2PvBydYFF9rd372rMcxf6TEM>
Subject: Re: [lamps] Proposed re-charter text for hybrid and dual crypto modes
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 20:04:51 -0000

I think if we are going to do this then I think these are the words =
I=E2=80=99d use.

Get ready to explain the quoted text to the IESG :)

spt

> On Jan 28, 2021, at 14:27, Mike Ounsworth =
<Mike.Ounsworth=3D40entrust.com@dmarc.ietf.org> wrote:
>=20
> Proposed charter text:
>=20
> Post-quantum cryptography (PQC) will require a transition period in =
some ways similar to previous crypto migrations, but unique in that =
timelines require deployment of PQC before cryptographers have full =
confidence in the replacement algorithms. NIST has called for transition =
mechanisms that "layer" traditional and PQ crypto together, referred to =
as "hybrid key establishment" and "dual signatures". The LAMPS working =
group will update documents produced by the PKIX and S/MIME WG to =
support hybrid key establishment, encryption, and dual signature =
mechanisms.
>=20
> ---
> Mike Ounsworth
> Software Security Architect, Entrust
>=20
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Thu Jan 28 12:05:02 2021
Return-Path: <sfluhrer@cisco.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8318C3A16CD for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 12:05:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level: 
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=RF7nL786; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=03Ds5U4S
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NcxuOyVa3oBz for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 12:04:58 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BF733A16F4 for <spasm@ietf.org>; Thu, 28 Jan 2021 12:04:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22441; q=dns/txt; s=iport; t=1611864298; x=1613073898; h=from:to:subject:date:message-id:mime-version; bh=mt1nG2tosWdq/FOpI6IFIjoQnSeTUqbA20Hp808uImw=; b=RF7nL786QE1AbXgI8f5k7O/zPsQuaQjYG0fZcwbFUG/iIxD97rw3DhBM 0y4pr5MCvFmy/7ZgEEn5zjXbR1E0CwrE4WOOEuW5jkQyFhYU4E+8t1J+v Zw2aIXgLx+aH0H5rNWT7T2yzHAd9yHfqMNinV6ybMmUmh0ov5DQYrSf+5 k=;
X-IPAS-Result: =?us-ascii?q?A0B0BgBMFxNgmIsNJK1iHQEBPAEFBQECAQkBFYFRgSEwI?= =?us-ascii?q?y59WjIvCgGHfQOLcIIXgQiYFIJTA1QLAQEBDQEBJQgCBAEBhEoCgXgCJTgTA?= =?us-ascii?q?gMBAQEDAgMBAQEBBQEBAQIBBgQUAQEBAQEBAQGGNgEMhicTAQEvCREBQAc5F?= =?us-ascii?q?BIBBBMIE4MLAYF+VwMuAQ6qIAKKJXSBNIMFAQEGgTMBE0GDBBiCEgMGgTgBg?= =?us-ascii?q?naGU4N0JhuBQT+BEUOCIQeDSQICF4EQOCuDIIIsgmEnGgoCMyQCLTEBBSsjG?= =?us-ascii?q?A0qDxQFSYpwhDogimidfwqCdgSJLodHhGWGOaMElCiLI5Jrg1MCBAIEBQIOA?= =?us-ascii?q?QEGgW0hOYENDAdwFTuCaVAXAg2OLQ4Jg06KWHQ3AgYKAQEDCXyKCAEwYAEB?=
IronPort-PHdr: =?us-ascii?q?9a23=3AKjOraRxVDd1e80HXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5ZRWFt/RgkFGPWp/UuLpIiOvT5qbnX2FIoZOMq2sLf5EEUR?= =?us-ascii?q?gZwd4XkAotDI/gawX7IffmYjZ8EJFEU1lorHC2LUYTH9zxNBXep3So5msUHR?= =?us-ascii?q?PyfQN+OuXyHNvUiMK6n+C/8pHeeUNGnj24NLhzNx6x6w7Ws5ob?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,383,1602547200";  d="scan'208,217";a="636130791"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Jan 2021 20:04:56 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 10SK4uRb019834 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <spasm@ietf.org>; Thu, 28 Jan 2021 20:04:56 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 28 Jan 2021 14:04:56 -0600
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 28 Jan 2021 15:04:55 -0500
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 28 Jan 2021 14:04:54 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nprqqOYTFpY5hD0XFa5Zn88cdQe4FXVtNr28A2bi62iyRyZxqcyvUPXJYIy3Xc6gmbWJjev8FWy3T4uhMf4k6Oc0/H9l5spMypuJDIySkDHQMsLxphWhK4SwIOBXv0I4YFthdYlB5sgeheahr7iM+X0wgsdR42osioeFND9Hd9/gMWbwlbKsRupD3Vn4oN91gPGHzK5S5kiwyAdzqeXiHS5N4E0qpcefNT6+cB4Yo7xWdvGN3n48cYOFwHpQsmg6qKsjqcfrgzuoP+oo4/Qohhb7k7mUp9ypzqMU1+9dRsG2dUG4G7mvVA4pxfQdoUO7IDwPmQo5HcujoRkHRs97gg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Jhnhg/8YiMJ6bhy6WkExm0RgLwarTY0QR1nvNtVy1sg=; b=I9H2hLXkdCRiHA9toWxMO6eHGt7wC7vn6B395PnpnWfxNE5CcidEiRB796vOV+jSGvijSZY8voxk2zRq8T9YKZYLoFd2M4Hc1WnDl8gq4CPQmSRoPe1FtwZRYOzdoo3nkIZ7J1Mby32DoOeFFjDy6jsYAKJ4G90NeZ7jdp+3ixAxx+fRsnPej5tTASj5ahI5XLK+4n4o6sLvweIM5RMmaHHJEVPfoNV14VO5wabpNFC6B6mR2j91bqGcWTyjQB1/aJAu9UuJus9OhSz1KQmEwfWd4Zm1rr/NTHIG1DlrMjurtK+8lhdySsPiBjx6e4V5Zpm8AaMarAnZOCIjQmElIg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Jhnhg/8YiMJ6bhy6WkExm0RgLwarTY0QR1nvNtVy1sg=; b=03Ds5U4SRmnPphFnMPJymyVe+bbrNWUUXM46c19oUWBmxgYJjox0uDuu/GCFbQWBdlgN3dNc4NEqLol25Vu8BGrIbKVQ8gwOyupJACXFjgr1lb6VaSajTsHLFkNbzuctLJxX8SZ3pkHt4Qqn2Skg8i/3LOKgRD1IopfQX5A1P0k=
Received: from BN7PR11MB2641.namprd11.prod.outlook.com (2603:10b6:406:b1::25) by BN6PR1101MB2195.namprd11.prod.outlook.com (2603:10b6:405:5a::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.13; Thu, 28 Jan 2021 20:04:53 +0000
Received: from BN7PR11MB2641.namprd11.prod.outlook.com ([fe80::515e:9791:f22c:6c4f]) by BN7PR11MB2641.namprd11.prod.outlook.com ([fe80::515e:9791:f22c:6c4f%7]) with mapi id 15.20.3784.019; Thu, 28 Jan 2021 20:04:53 +0000
From: "Scott Fluhrer (sfluhrer)" <sfluhrer@cisco.com>
To: "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: Work done elsewhere to start defining OIDs for postquantum algorithms
Thread-Index: Adb1sBc/bObHVRcPSfq1cVvoJ5AXkA==
Date: Thu, 28 Jan 2021 20:04:53 +0000
Message-ID: <BN7PR11MB2641C7E80117EADEAEB04607C1BA9@BN7PR11MB2641.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [173.38.117.78]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1639f4c8-a90c-4b18-6106-08d8c3c7f9fb
x-ms-traffictypediagnostic: BN6PR1101MB2195:
x-microsoft-antispam-prvs: <BN6PR1101MB21954EBF05E97F3BAA2498E0C1BA9@BN6PR1101MB2195.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: o/4ddKtCoxQfPFfThgSNLz8KTOGYjff7DImL4MbLG0y43FmMc5KrTdfYIH+7KM6Tg4t22U3ebA6NcbBmRmnAHb90eyLbUzAX+UzEbUej22PEKhZNmI1MS40nMRHCBQJUwYLe3X/K+4DXscy4lftBkBUcp8tY4N78X2SGy66/3Hq/QCyGb8cZSyLCr0bpY0LSMPFppHX5wMDrWLnZ+aEmqbnZ6JSso0eAcUA4+e1gUhgEfR4ZVbUO2NZRRoHqmysJuACZq9wK6OpB+fLsoQvAxXIxS1IJlyMssEEs6GxeBX5kFpoj01ybyTBgz49ENAqR2FxLCaXHXFfIjeDAR7a6UktJ+esjoGPDVtdgoVxjH50sQx5qUVJE8r8pYWtGx/TgstmtwuDHzINkWlyPJyBdaFmURDIenbmk+Za/EWF7a4e77mCuDcRGzUe3R3MFX7Ow+aA7SwUYnoS4ZiIXQLezZotfs9bul1cpPNAnXVsIzo38nd2MaoXqo+BqvNxHHzPIea1bOF2q/c/Za/+by3RGZ9ngqgAKsZLLm9NRBUxwdZxZklk8IgPPx2l/rcfKXIPWGh7ZHaKoqnGZX4UmktB9C4DRmIQNbxpuOL5oY1YmJklgCjQR3/+CoClX6zAwwIW6YC9j7PPOhcm3YOdb//KAqg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BN7PR11MB2641.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(346002)(366004)(39860400002)(396003)(376002)(136003)(8676002)(76116006)(966005)(186003)(66556008)(52536014)(7696005)(2906002)(66946007)(66446008)(66476007)(6506007)(64756008)(26005)(316002)(478600001)(33656002)(55016002)(8936002)(9686003)(166002)(83380400001)(71200400001)(86362001)(5660300002)(6916009)(15940465004); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?ZhH+BxceJlzh2udmut3S4hnHK+e9L1nVTZXCrEL3PaKWzxCjsAGSFP7LORAy?= =?us-ascii?Q?cyRxEoa8MhW8O0E/MAWRmkzes3kDMQXacU0de0q9f9b+VUz+lOhJPl5kaPcH?= =?us-ascii?Q?o8Gk0NQBqYOuQD33UlILlh0JFOI+jDrRZrGuwAtf1lYYS9L5FzhKlwA8DzpU?= =?us-ascii?Q?Pnm4+EbpXfsrwX4ErlAYhMt37s6T4nAkI9tDACZwdVYotCXW40p9Vi+XOild?= =?us-ascii?Q?fDZLpjY12riV6o964sIMJiWfovn8C8gXFrgSh5bp7K02KrO9VR8pqhsY03IJ?= =?us-ascii?Q?HPPJxjg6cmtgp21oDY8whTyBvoPOOFeQc8TJ9k07yI0veGtaJz9hDdj0GJHH?= =?us-ascii?Q?AlkyzjvdW89ypJeUVwAzGQo/0bICN+wzYUQRc+/IPOvyh0njfBlKGKAOtrZX?= =?us-ascii?Q?6UeHxZVFmT+1W90F5pkJCqvUQKelTrAPd98wjfTk8ImYq4wfDUl5+ak8rnpq?= =?us-ascii?Q?SHCSYW19DUpyCZaKI5W3zrQb2S3OE56oYtX9MTpJYJhKUlYEO1z2h5Mrk/Yd?= =?us-ascii?Q?u1NGPIBntCrkO1gKdOBqc+1nRwagm/JyOVtnYGkNM5s2jLUVo97ernhbGBUI?= =?us-ascii?Q?s1wLygvR+fQ8Ph5jW2Je4wy9mttwoN6rr6yX0m0fRnCm+guPqatps8DxzNeo?= =?us-ascii?Q?L55kbzRu0KPjhcAc2tZ2bfYM+8mfEmTYt8iJeldBnZM5DUy0qP2nPOlaMcw+?= =?us-ascii?Q?3Xzto/SkorfPH3WA1O/LYP/LuRZT2bt4dkbnmtQLEYUMSZc/7CnRR6gwADGm?= =?us-ascii?Q?XwzhTYT8Dv1ymzFH5ZK9he4xembS+ZHgIamktLuc/CSiOaxNqWKwyIZOLs0x?= =?us-ascii?Q?/ajwcPnqLKz7ckhwAd9b2mey+wESngIfVucTdSUvwCm8FIPBslTLkQd+h3NK?= =?us-ascii?Q?J/0rcyp1PL95v+ElLTxB2oOV0EX1uMK4Dpydfcw7XeNqmDM1tnICMDMWFfx4?= =?us-ascii?Q?B25Z8KyhkaktDq5aJaMpw8jO99BC1xMZ2IOpoyzkU96Ipk4MHsNPBmCPbF+T?= =?us-ascii?Q?FVe0ggevr2OsobFW3PiM/8w1PnAM3Gpb8gIOMzBj2akp0CRkH/Q60lCI3sRd?= =?us-ascii?Q?+NFzbLWL?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN7PR11MB2641C7E80117EADEAEB04607C1BA9BN7PR11MB2641namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN7PR11MB2641.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1639f4c8-a90c-4b18-6106-08d8c3c7f9fb
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jan 2021 20:04:53.2404 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hK+jbkw5t9wFZS/9ZHP79EzDQ+D1S8sxsEdT8AwdRav7x8TdA64rpQ2+DXz/gZFshfa2zzBnFQvEVb/Q6zXgaA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1101MB2195
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/fWR4ElM0rga8PERq4dKbVEjwOas>
Subject: [lamps] Work done elsewhere to start defining OIDs for postquantum algorithms
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 20:05:01 -0000

--_000_BN7PR11MB2641C7E80117EADEAEB04607C1BA9BN7PR11MB2641namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

During the interim working group meeting, it was mentioned that we might wa=
nt to start assigning OIDs to various postquantum algorithms.

I came across some people already started working on this (I saw this on an=
 X9 list, however looking at it closer, it might not be the X9 doing it); i=
t might make sense to coordinate with them.  Note that they are not working=
 with composite or hybrid algorithms; they are just working with the postqu=
antum algorithms in isolation.

Here is the full text that I received:

I would like to draw everybody's attention to a piece of work focused on ke=
y identification and key serialization for post quantum algorithms. This wo=
rk was started by a small group of industrial partners who are already depl=
oying quantum safe algorithms in an attempt to parallelize efforts around t=
he standardization of quantum safe cryptographic algorithms, at the same ti=
me as the standardization required to manage the use of these algorithms. T=
his work is taking place in a completely open format under the following li=
nks, and we welcome any participation on this topic:

https://groups.google.com/g/rfc-quantum-safe-key-serialization-and-identifi=
cation---review

https://docs.google.com/document/d/19XfdzkVdHS69rqin-XV72Cn2FjrpEbiyERg7F1l=
KIVs/edit?usp=3Dsharing


This goal of this effort is to create an open and public set of initial spe=
cifications and formats, that allow a more controlled evolution of quantum =
safe algorithms. It is hoped that this can provide the technical basis for =
adoption of formats in other standards that need to evolve to become quantu=
m safe. The scope of the document is initially confined to algorithm identi=
fication and key serialization formats. We do not aim to compete with any s=
tandards activities, rather preemptively bootstrap a set of guidelines to s=
implify the adoption and interoperability post quantum algorithms.  Three o=
f the finalist NIST algorithms have been completed (DILITHIUM, FALCON, NTRU=
), the remaining algorithms together with the alternative list are under de=
velopment.


Background
New quantum safe key exchange and digital signature algorithms are being de=
veloped that are secure against future quantum adversaries. The US National=
 Institute of Science and Technology (NIST) is currently running a multi ye=
ar process to evaluate potential candidates and select a small set of algor=
ithms to standardize. This process started in 2016 and is expected to finis=
h in 2023. The NIST process thus far did not include any mechanisms to stan=
dardize algorithm identifiers and key serialization formats. Parallel to th=
e NIST standardization process, many of the proposed algorithms are being i=
mplemented. This is in part for testing and evaluation and in part as pre-s=
tandard hybrid solutions. Implementations necessarily need to evolve as the=
 algorithms themselves evolve through the standards process.

Early implementations and pre-standardization roll-outs have also shown tha=
t many platforms and protocols are constrained in the size of keys that the=
y are able to handle without significant modification. Post quantum keys ar=
e generally larger, in some cases much larger, than current RSA or ECC keys=
 where the concept of compressing parameter sets to reduce key size is alre=
ady commonly used. This is driven by the need in many application domains t=
o save every byte possible and trade-off key size against the overhead of k=
ey regeneration. Applying lessons learnt from the previous incremental stan=
dardization of compressed parameter sets, there is a clear benefit to defin=
ing this upfront.

The early definition of key identification and key serialization for post q=
uantum algorithms should avoid :
*         Difficulty in managing algorithm versions and the compatibility o=
f associated keys
*         Incompatibility between key compression formats
*         Difficulty in interoperability testing
*         Difficulty in evaluating the impact of integrating algorithms wit=
h higher level standards
*         Delays follow on activities for algorithm integration and adoptio=
n

By addressing these problems now rather than after waiting for the NIST sta=
ndards process to complete, it should reduce the time it will take for indu=
stry to adopt a new generation of quantum safe cryptography.


kind regards

Mike Osborne

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Michael Osborne
Manager Privacy and Security
Global Lead IBM Q Encryption
Zurich Research Laboratory,
Saeumerstrasse 4, CH 8803, Rueschlikon / Switzerland
Phone/FAX (41) ( 44 ) 724 8458 / (41) ( 44 ) 724 8953
Extern: osb@zurich.ibm.com<mailto:osb@zurich.ibm.com>





--_000_BN7PR11MB2641C7E80117EADEAEB04607C1BA9BN7PR11MB2641namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1986663185;
	mso-list-template-ids:712703020;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea=
k-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">During the interim working group meeting, it was men=
tioned that we might want to start assigning OIDs to various postquantum al=
gorithms.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I came across some people already started working on=
 this (I saw this on an X9 list, however looking at it closer, it might not=
 be the X9 doing it); it might make sense to coordinate with them.&nbsp; No=
te that they are not working with composite
 or hybrid algorithms; they are just working with the postquantum algorithm=
s in isolation.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here is the full text that I received:<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">I would like to draw everybody's attention to a piece=
 of work focused on<strong><span style=3D"font-family:&quot;Arial&quot;,san=
s-serif;color:black;font-weight:normal"> key identification
 and key serialization for post quantum algorithms. This work was started b=
y a small group of industrial partners who are already deploying quantum sa=
fe algorithms in an attempt to parallelize efforts around the standardizati=
on of quantum safe cryptographic
 algorithms, at the same time as the standardization required to manage </s=
pan></strong>the use of these algorithms. This work is taking place in a co=
mpletely open format under the following links, and we welcome any particip=
ation on this topic:</span><span style=3D"font-size:10.0pt;font-family:&quo=
t;Arial&quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif"><a href=3D"https://groups.google.com/g/rfc-quantum-sa=
fe-key-serialization-and-identification---review" target=3D"_blank">https:/=
/groups.google.com/g/rfc-quantum-safe-key-serialization-and-identification-=
--review</a></span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif"><a href=3D"https://docs.google.com/document/d/19Xfdzk=
VdHS69rqin-XV72Cn2FjrpEbiyERg7F1lKIVs/edit?usp=3Dsharing" target=3D"_blank"=
>https://docs.google.com/document/d/19XfdzkVdHS69rqin-XV72Cn2FjrpEbiyERg7F1=
lKIVs/edit?usp=3Dsharing</a>&nbsp;</span><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif;color:black">This goal of this effort is to create an =
open and public set of initial specifications and formats, that allow a mor=
e controlled evolution of quantum safe algorithms.
 It is hoped that this can provide the technical basis for adoption of form=
ats in other standards that need to evolve to become quantum safe. The scop=
e of the document is initially confined to algorithm identification&nbsp;an=
d key serialization formats. We do not
 aim to compete with any standards activities, rather preemptively bootstra=
p a set of guidelines to simplify the adoption and interoperability post qu=
antum algorithms.&nbsp; Three of the finalist NIST algorithms have been com=
pleted (DILITHIUM, FALCON, NTRU), the
 remaining algorithms together with the alternative list are under developm=
ent.</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,sa=
ns-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><strong><span style=3D"font-size:12.0pt;font-family:=
&quot;Arial&quot;,sans-serif">Background</span></strong><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif"><o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif;color:black">New quantum safe key exchange and digital=
 signature algorithms are being developed that are secure against future qu=
antum adversaries. The US National Institute of
 Science and Technology (NIST) is currently running a multi year process to=
 evaluate potential candidates and select a small set of algorithms to stan=
dardize. This process started in 2016 and is expected to finish in 2023. Th=
e NIST process thus far did not
 include any mechanisms to standardize algorithm identifiers and key serial=
ization formats. Parallel to the NIST standardization process, many of the =
proposed algorithms are being implemented. This is in part for testing and =
evaluation and in part as pre-standard
 hybrid solutions. Implementations necessarily need to evolve as the algori=
thms themselves evolve through the standards process.&nbsp;</span><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif"><o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif;color:black">Early implementations and pre-standardiza=
tion roll-outs have also shown that many platforms and protocols are constr=
ained in the size of keys that they are able to
 handle without significant modification. Post quantum keys are generally l=
arger, in some cases much larger, than current RSA or ECC keys where the co=
ncept of compressing parameter sets to reduce key size is already commonly =
used. This is driven by the need
 in many application domains to save every byte possible and trade-off key =
size against the overhead of key regeneration. Applying lessons learnt from=
 the previous incremental standardization of compressed parameter sets, the=
re is a clear benefit to defining
 this upfront.</span><span style=3D"font-size:10.0pt;font-family:&quot;Aria=
l&quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif;color:black">The early definition of key identificatio=
n and key serialization for post quantum algorithms should avoid :</span><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif"><o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-left:96.0pt;=
text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol"><s=
pan style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:12.0pt;font-family:=
&quot;Arial&quot;,sans-serif;color:black">Difficulty in managing algorithm =
versions and the compatibility of associated keys</span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif"><o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-left:96.0pt;=
text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol"><s=
pan style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:12.0pt;font-family:=
&quot;Arial&quot;,sans-serif;color:black">Incompatibility between key compr=
ession</span><span style=3D"font-size:12.0pt;font-family:&quot;Arial&quot;,=
sans-serif">
<span style=3D"color:black">formats</span></span><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-left:96.0pt;=
text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol"><s=
pan style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:12.0pt;font-family:=
&quot;Arial&quot;,sans-serif;color:black">Difficulty in interoperability</s=
pan><span style=3D"font-size:12.0pt;font-family:&quot;Arial&quot;,sans-seri=
f">
<span style=3D"color:black">testing</span></span><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-left:96.0pt;=
text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol"><s=
pan style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:12.0pt;font-family:=
&quot;Arial&quot;,sans-serif;color:black">Difficulty in evaluating the impa=
ct</span><span style=3D"font-size:12.0pt;font-family:&quot;Arial&quot;,sans=
-serif">
<span style=3D"color:black">of integrating algorithms with higher level sta=
ndards</span></span><span style=3D"font-size:10.0pt;font-family:&quot;Arial=
&quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-left:96.0pt;=
text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol"><s=
pan style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times=
 New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:12.0pt;font-family:=
&quot;Arial&quot;,sans-serif;color:black">Delays follow on activities for</=
span><span style=3D"font-size:12.0pt;font-family:&quot;Arial&quot;,sans-ser=
if">
<span style=3D"color:black">algorithm integration and adoption</span></span=
><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif;color:black">By addressing these problems now rather t=
han after waiting for the NIST standards process to complete, it should red=
uce the time it will take for industry to adopt
 a new generation of quantum safe cryptography. </span><span style=3D"font-=
size:10.0pt;font-family:&quot;Arial&quot;,sans-serif"><o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">kind regards</span><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">Mike Osborne</span><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,sans-serif"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif"><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<br>
Michael Osborne<br>
Manager Privacy and Security<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,sans-serif">Global Lead IBM Q Encryption<br>
Zurich Research Laboratory,<br>
Saeumerstrasse 4,&nbsp;CH 8803, Rueschlikon / Switzerland<br>
Phone/FAX (41) ( 44 ) 724 8458 / (41) ( 44 ) 724 8953<br>
Extern: <a href=3D"mailto:osb@zurich.ibm.com">osb@zurich.ibm.com</a><o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_BN7PR11MB2641C7E80117EADEAEB04607C1BA9BN7PR11MB2641namp_--


From nobody Thu Jan 28 12:22:16 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3EB3A1715 for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 12:22:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ljg7te74FhLF for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 12:22:05 -0800 (PST)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-eopbgr690118.outbound.protection.outlook.com [40.107.69.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAD9D3A1730 for <spasm@ietf.org>; Thu, 28 Jan 2021 12:22:03 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MlufNOPdv0rE9VKIzpNTA4BKqf9lLKcUhIt6qTl0wVcTw1eD+NuE10EI8HuIx2AoSvPwR83QFd8ZInbyDmIO0iF/xoQ3N5Z+viJNvCf8+/Vl+b4Wt9ww/hEkDpnm/3S+UiVma/liyNAXvgUdPnsr15E7lNYH5oA+PQxBzKMuIp9JPzAw5ayiPZsr70rt04LRJfeasYo6R+n1jfyBsmi1QLEvXNuBFGaU6fGnJ3Zf3OoEgnzJu4dvscvOJZzbLUhAO83ONTMdoC31yakvwIIZwYxAYaoUQzbNYFTND0sRcxgooWUkGVbu5HEpR3sot4yesL7d2DCAOmPSqDT/YM6omQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PpUWHhWl7T7WNqRsvOsvbkFkXexEyCV4hKgvr/mO7VE=; b=DUvEIFtLMpHL+IfAoJ1FBjSBMDq+aJ3ncOf9Q7Ti1iNksplcpcZxrPW9oqrUln4ePBaN/qeClyHP7xTKUOUXBU5sD09sHgaJ8Dnv5WZ3jLYzABrB9K/tM5utyzcMIlpfkjTeNAJVtQmDw4soAdQeJ1p46i1ClCNIWKNnfy2+iRFJluf0iqlUJFW9eVdaeOtx+uAn1P69sj8K+9e2i0jFp0S3uNmi4FGpt7C+wrOgkt5aO6I30z6knuysGF6lg2/33P/nIpcXYwhcgSeqaOK+E2ribx6RkB6bAQftLcyi7Mj+2epYdpElRR8VIePKEhNpgCEPZ9xRMZ22hZTbm7kIQA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PpUWHhWl7T7WNqRsvOsvbkFkXexEyCV4hKgvr/mO7VE=; b=DApALl6iaAhuwkdzfzjH4bNuw3EHIU5mbDaw6lptTSR40f/lnyV9WfZpHA8GnO9sHaG6g5epVXhp8x4D18Sk7M6tfH76XzjKMq7IIsE6X3C0M7/sX/NAvs7KzUWs9xX/v5SwhKaP77AMC8jGKSyiNvmg009R7XktVw+JmlueVI4Wppd3mC1LRJP0TQM2/ROySnIUmK9OUUSn3t7xKb/0atWpxe6DdJG0XF2qhmMF45cnqf1Kio7Z/C37UYR7fCZta4tV5fVsgjMY74gkncHLLtfvSJksL0JY1OOVgmdCV5wJbyxNAYhMm1w1fCoKYjGQb9E9zmazHz79Nv+eYILdPw==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB2571.namprd11.prod.outlook.com (2603:10b6:5:c7::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.17; Thu, 28 Jan 2021 20:22:01 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::a816:b4fb:846e:9417]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::a816:b4fb:846e:9417%6]) with mapi id 15.20.3784.019; Thu, 28 Jan 2021 20:22:01 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: Sean Turner <sean@sn3rd.com>
CC: LAMPS <spasm@ietf.org>
Thread-Topic: [EXTERNAL] Re: [lamps] Proposed re-charter text for hybrid and dual crypto modes
Thread-Index: Adb1q3GYntimtkHXQaOdOOEUbm7smwABWBgAAABqtFA=
Date: Thu, 28 Jan 2021 20:22:01 +0000
Message-ID: <DM6PR11MB43801C9A891C0DF843AE309C9FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
References: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com> <1BE0BD5D-BD11-40E7-87F5-61EE49AAF1FD@sn3rd.com>
In-Reply-To: <1BE0BD5D-BD11-40E7-87F5-61EE49AAF1FD@sn3rd.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: sn3rd.com; dkim=none (message not signed) header.d=none;sn3rd.com; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [4.19.72.62]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 627b8d17-6b1f-4b12-a2f3-08d8c3ca5edf
x-ms-traffictypediagnostic: DM6PR11MB2571:
x-microsoft-antispam-prvs: <DM6PR11MB25715A61BF5EE091EBBCF0209FBA9@DM6PR11MB2571.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: L/Xni5OpwKKfLP1vJ413s5Q6u2O1i2Iy0eBQNowu52Zml8Xk565gS+29WEhzNHrg18JHaATrFnLjI6VybkzlGrGHlWFHRhp+8BTL+B5wPR6I0bc1BvN1o33LnwpDUCngOxFQ4/EetBp4hnhJkmToAZll6c8R4/Y7c4zwiPEfGwzcZhtbwNCorq/cCzSwpzy+oXzcGunhEzPVGsQzZL99qhneUlVKVYQsfqa7S9yEl9QY32oPCdARZaEpoE+/LB4Xoh7il1ASUAKlvKVd7Ld52iFXZ5Idu9DASDpPGlsMAlSQ6jsniEsmDiXG+GmfVyy7Le33qMgG+wZ5azvsIwWA/S7WWgEj387hn/HVcRgV2pHJ+sb2aqfuwDTeVIGkAgwq/UGaOqNEpvvERebIhwwhubKaGeV0InKDFOwwALXIznJurxLJZTr6/UcNyaQziTENR/hFhh8ZOhAI27FtCqgl/VKfPXo0HAdkNdrcXQuPwZg44DHHBFP1BJM4+FG/5LHepRxLV5BVVFx9mXUIyTL0QcDrPHhOr0VWi41XSj7701UqcigP09evQWCG6SoRiBHXvaZlcnrpWK4yWjbsUdOegnc14gnu+yfXqS6/tqpKfVA=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(136003)(396003)(366004)(376002)(39850400004)(86362001)(64756008)(66556008)(66446008)(26005)(66476007)(66946007)(6506007)(53546011)(7696005)(52536014)(71200400001)(186003)(5660300002)(316002)(966005)(478600001)(76116006)(55016002)(83380400001)(4326008)(9686003)(33656002)(6916009)(8676002)(8936002)(2906002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?Y2g2ZmM0Y1N5NE5iTHphNituS2RJTFNlR0FaMloyK2VhUEtpTWs4cG84Z3NQ?= =?utf-8?B?NlpwL3MycDVpcDg5QjFxWFl3SUFKWVJ0Y0p3V2kwT0pwVXRLV0RURENWVHY3?= =?utf-8?B?SEVsWEU5U0hwejZKZVRpeFFUUkUyZEZkQm1YM0tTV0UrbzZ0VHV4RWJydTd5?= =?utf-8?B?Y1o5T1oxSVpGMlc1aWR4QlNRY1kvMmc5dWtIRjhKS3phMDRiNHNrdjh0RGRq?= =?utf-8?B?MWhsOUNaM2NLYkwvemttbUFCNWU3SDNvRDlLVlppc01FdGxFalMyVDRKVTlO?= =?utf-8?B?UFFDN0UxMDVFM3Q5L29MdWo5TXhpdG9uOHJBekhsQ2VLMVdWZ05QZ2FTOWVk?= =?utf-8?B?TitsV1J2ZU0vQkZzMnBabzJLa2gwV3BGVmUvT0N3cXBRcFBFSENHemUxVTI2?= =?utf-8?B?dVhzT2xqVzFWYTF6KzNLbzRaa0hiRUoxU0Q0R1duRXZ4UE5weHMvQWtWZUVF?= =?utf-8?B?T0FNbEVPTmc2blQ5b3lDRm5lVE1IUnpqUlUrZGFJWlQ3Mk9vcFpWOGdqcXcv?= =?utf-8?B?dFdHV1oxd2ZQTkE1aEF0NWpkNWdScXVqQnFDdVFFbzFvb0cvSGdFYnR1dURa?= =?utf-8?B?Zkt3WUw5YjIzdXlraUJpdmxhaXlnMTZvNzZHM3NpY052bC9nYXJsOEVWc05R?= =?utf-8?B?N29SNjRWSmZENzc1MUhSeWF6emd5OFpkamhsOXBHQUVRd3JJZ1hiNkVHc2Iz?= =?utf-8?B?dkgwZWt0UTNWYTFpMkZLdTR2Wk1HM1FoRlRRMCtMeFA3Ym1iWnV2TjBsSnRL?= =?utf-8?B?YVIxTHJjbEFIa1NxR0EyN0ZwWU5wNEE1cU5MQlovSmxCWno0V0lrRndpbk5y?= =?utf-8?B?NTRNbEtoN2ZGdThHR2Z2SmpUQXEvYnZmMitGZTNHR09pYm9rZ2NEeno0SlhI?= =?utf-8?B?L2wrcGYvamhuMzBMbXlWcjh6M2UzdnhHaEw0LzhoZ1ZNdURuUVc3ZzBxMlY5?= =?utf-8?B?QWMrbXZXQUN4UEJnTzZUdkcyOUNOUFAyc1pJZjlEcFlYZVVsSnpWRTNveG5Z?= =?utf-8?B?TWRweitKZVI5Um9PVVMzeDNoamxCN3cvV0I3T3JaRzR0UTRMdVQ3MFRjSGhO?= =?utf-8?B?cVlleGdYRFJCK0lBY08rMEh3SHVyQTE4THFnSVB2UVNRazY1Yk1UTGJFZ3Jh?= =?utf-8?B?WU42SzJlc0hTQ1ltSGVrK2tJaXBKenZyUWN2b0FFajNYL3pNbHVXeHBkRW01?= =?utf-8?B?Uit5NDBlNWNuNnBjLzhmaWUwSjMzcTBUUkpxSUdRNTVFZEN1TkVtODE5RGpn?= =?utf-8?B?UTBYakN6TDRFNVEvTy9jWWo3aTRNMHRyVUx4elhZMldpYXYwdUpUOGsxVzQ0?= =?utf-8?B?cDZkY2FWZm51cjVkT0xkeXo1ejI2SjNXaXlBWmZOeVJ1SnU2V1pycXZEN3Zx?= =?utf-8?Q?22XGhL30T9AsSoqI57Oy21eFirOBuFBo=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 627b8d17-6b1f-4b12-a2f3-08d8c3ca5edf
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jan 2021 20:22:01.4910 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: UqyiGy9QBQyPkMtNZJr2dMt+4AoOa1H3q+yeerztRzFo1UEvTqTWixjYJy+M98xXvMSRBX+CpdxpbnK0wtu5bqh/qgsFthI5K9RrIubZFCM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB2571
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ff3f61dHndyryai3ceO9_0_AhLU>
Subject: Re: [lamps] [EXTERNAL] Re: Proposed re-charter text for hybrid and dual crypto modes
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 20:22:16 -0000

RnJvbSBkaXNjdXNzaW9uIGF0IHRoZSBpbnRlcmltIG1lZXRpbmcsIHBlcmhhcHMgIi4uLiB3aWxs
IHVwZGF0ZSBkb2N1bWVudHMgcHJvZHVjZWQgYnkgdGhlIFBLSVggYW5kIFMvTUlNRSBXRy4uIiBt
YXliZSBpcyBub3QgYnJvYWQgZW5vdWdoIGFuZCBtYXliZSBuZWVkcyB0byBhbGxvdyBmb3IgbmV3
IGRvY3VtZW50cz8gVGhlIGlkZWEgaGVyZSBpcyB0byBtYWtlIHN1cmUgZXhpc3Rpbmcgc3RhbmRh
cmRzIGhhdmUgc3VmZmljaWVudCBoeWJyaWQgYW5kIGR1YWwgc3VwcG9ydCwgbm90IHRvIGdvIGlu
dmVudGluZyB0b3RhbGx5IG5ldyBwcm90b2NvbHMuIA0KDQouLi4gdGhhdCBzYWlkLCBJIHdvbmRl
ciB3aGV0aGVyIGRyYWZ0LW91bnN3b3J0aC1wcS1jb21wb3NpdGUtc2lncyBhY3R1YWxseSBmYWxs
cyBpbnNpZGUgdGhpcyB3b3JkaW5nIG9yIG5vdDsgYXMgYSBzdGFuZGFsb25lIGRlZmluaXRpb24g
b2YgYSBuZXcgc2lnbmF0dXJlIGFsZ29yaXRobSwgaXQncyBub3QgdGVjaG5pY2FsbHkgdXBkYXRp
bmcgYW55IGV4aXN0aW5nIGRvY3VtZW50cy4uLg0KDQotLS0NCk1pa2UgT3Vuc3dvcnRoDQoNCi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBTZWFuIFR1cm5lciA8c2VhbkBzbjNyZC5j
b20+IA0KU2VudDogSmFudWFyeSAyOCwgMjAyMSAyOjA1IFBNDQpUbzogTWlrZSBPdW5zd29ydGgg
PE1pa2UuT3Vuc3dvcnRoQGVudHJ1c3QuY29tPg0KQ2M6IExBTVBTIDxzcGFzbUBpZXRmLm9yZz4N
ClN1YmplY3Q6IFtFWFRFUk5BTF0gUmU6IFtsYW1wc10gUHJvcG9zZWQgcmUtY2hhcnRlciB0ZXh0
IGZvciBoeWJyaWQgYW5kIGR1YWwgY3J5cHRvIG1vZGVzDQoNCldBUk5JTkc6IFRoaXMgZW1haWwg
b3JpZ2luYXRlZCBvdXRzaWRlIG9mIEVudHJ1c3QuDQpETyBOT1QgQ0xJQ0sgbGlua3Mgb3IgYXR0
YWNobWVudHMgdW5sZXNzIHlvdSB0cnVzdCB0aGUgc2VuZGVyIGFuZCBrbm93IHRoZSBjb250ZW50
IGlzIHNhZmUuDQoNCkkgdGhpbmsgaWYgd2UgYXJlIGdvaW5nIHRvIGRvIHRoaXMgdGhlbiBJIHRo
aW5rIHRoZXNlIGFyZSB0aGUgd29yZHMgSeKAmWQgdXNlLg0KDQpHZXQgcmVhZHkgdG8gZXhwbGFp
biB0aGUgcXVvdGVkIHRleHQgdG8gdGhlIElFU0cgOikNCg0Kc3B0DQoNCj4gT24gSmFuIDI4LCAy
MDIxLCBhdCAxNDoyNywgTWlrZSBPdW5zd29ydGggPE1pa2UuT3Vuc3dvcnRoPTQwZW50cnVzdC5j
b21AZG1hcmMuaWV0Zi5vcmc+IHdyb3RlOg0KPiANCj4gUHJvcG9zZWQgY2hhcnRlciB0ZXh0Og0K
PiANCj4gUG9zdC1xdWFudHVtIGNyeXB0b2dyYXBoeSAoUFFDKSB3aWxsIHJlcXVpcmUgYSB0cmFu
c2l0aW9uIHBlcmlvZCBpbiBzb21lIHdheXMgc2ltaWxhciB0byBwcmV2aW91cyBjcnlwdG8gbWln
cmF0aW9ucywgYnV0IHVuaXF1ZSBpbiB0aGF0IHRpbWVsaW5lcyByZXF1aXJlIGRlcGxveW1lbnQg
b2YgUFFDIGJlZm9yZSBjcnlwdG9ncmFwaGVycyBoYXZlIGZ1bGwgY29uZmlkZW5jZSBpbiB0aGUg
cmVwbGFjZW1lbnQgYWxnb3JpdGhtcy4gTklTVCBoYXMgY2FsbGVkIGZvciB0cmFuc2l0aW9uIG1l
Y2hhbmlzbXMgdGhhdCAibGF5ZXIiIHRyYWRpdGlvbmFsIGFuZCBQUSBjcnlwdG8gdG9nZXRoZXIs
IHJlZmVycmVkIHRvIGFzICJoeWJyaWQga2V5IGVzdGFibGlzaG1lbnQiIGFuZCAiZHVhbCBzaWdu
YXR1cmVzIi4gVGhlIExBTVBTIHdvcmtpbmcgZ3JvdXAgd2lsbCB1cGRhdGUgZG9jdW1lbnRzIHBy
b2R1Y2VkIGJ5IHRoZSBQS0lYIGFuZCBTL01JTUUgV0cgdG8gc3VwcG9ydCBoeWJyaWQga2V5IGVz
dGFibGlzaG1lbnQsIGVuY3J5cHRpb24sIGFuZCBkdWFsIHNpZ25hdHVyZSBtZWNoYW5pc21zLg0K
PiANCj4gLS0tDQo+IE1pa2UgT3Vuc3dvcnRoDQo+IFNvZnR3YXJlIFNlY3VyaXR5IEFyY2hpdGVj
dCwgRW50cnVzdA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4gU3Bhc20gbWFpbGluZyBsaXN0DQo+IFNwYXNtQGlldGYub3JnDQo+IGh0dHBz
Oi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL3NwYXNtX187ISFGSi1ZOHFDcVhUajIhSm0xQy1qTTBPV3hlV0MycGZhVVB4VXJ0TklkdUdB
UjJEMmtpNThBenRWcU5pSHdXTXJuMWtmc3d4Ulo4R2FkSElRRUwkIA0KDQo=


From nobody Thu Jan 28 13:58:41 2021
Return-Path: <Mike.Ounsworth@entrust.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2D633A174D for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 13:58:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=entrust.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Lrz-LN3tQ0p for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 13:58:38 -0800 (PST)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-eopbgr680110.outbound.protection.outlook.com [40.107.68.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D689C3A0AF9 for <spasm@ietf.org>; Thu, 28 Jan 2021 13:58:37 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QKW3AY1UofZpQ21DBBMp4EklQM8quFqjWvL7svRkW04ynBy3WmjuWK873uWl1wZSH2Lnq/xPFgdGI7U3orRQHJXiEegJzVpN0mSfri7wP0wwoAPipO0YnU/2cKZ0HYTAJ/aZIfOmz47s++/yJGh4n1ebwxNkb66H1aJotZXRAF0TZ70LNFpdPAl4K64PhJRBMGYZ5jXr7Mt9naLx/jll9dBSJCeWIpGIvZx7/uEyjGc3XPYOEqSdLvr6z9ItdPN3teYls+k+xypdd9c1LVscao0waQVOZGvrhs7imcXibLxDZXH1DYkAFbDbCLh5SwBZ1C0v3GQYrw+fB74p4Mahbw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DdYhHxbTZPq1ygyPkivwPFDRE/atx1klDxyilbE88l0=; b=XMMbj9uJDZM/rctJvoDF9SoEJDwHUVuPr+32hB5GlzWsTmSrEcbwN7IK2Ca5FVRoPHSmEuQ2AiKdMhOyCfjXACXatZV9ceVlGyGpUoxEDt1CcS9RdQETGACX7xPnklBXEBVEWIk7lstFQmRw1kRe0mEIJ/mSfK2MlLywtY1t92bXD8UkGRaSVAD/QkGrCpZHMxnEjCprGlJ+e/AmfG5buWWVUM1yIAoWilge0UsOAcKu09lcSrTgUMeCcJ9Yl8uBmYw/6iVFl53fSXRN6xXJg/ciS/f+fs+M1jYUhWGa1SdL0Qc5bzCOHMEBsjtKku6HuBsEqGB77IJsvvlL1mVKuw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=entrust.com; dmarc=pass action=none header.from=entrust.com; dkim=pass header.d=entrust.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=entrust.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DdYhHxbTZPq1ygyPkivwPFDRE/atx1klDxyilbE88l0=; b=OSdLWCNF4wxaLUOItCiSQfM2bvzW7CXneRfTHvDHYbYHoIphcWNk+pRentPtmdAFknv+Xa6h5gMF4qPu/0Z2/BG6v3R/cbo8r/HIqCKeT9pHwLoeh2XWqpa42WcoiVX5duv2g7vxhB3IKw3StJ1UauVr1LYXiCersPEJme/KOohD+4afXAAgy4LzatsGiryU6IzML2AzWlw0Z/gVXCqW14X0fTfIFylhJORSqO0Ne6/X1T+FOj9bYeotVWeWEqbsTjEOwJRe/8FMVJuzJYBvAnBypSgAkugFNVH00hFpBQqmgrNaVaCpEnXIDB/yhZjGMJgqsCwmep6ECO2ivY929Q==
Received: from DM6PR11MB4380.namprd11.prod.outlook.com (2603:10b6:5:14e::20) by DM6PR11MB4284.namprd11.prod.outlook.com (2603:10b6:5:205::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.16; Thu, 28 Jan 2021 21:58:32 +0000
Received: from DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::a816:b4fb:846e:9417]) by DM6PR11MB4380.namprd11.prod.outlook.com ([fe80::a816:b4fb:846e:9417%6]) with mapi id 15.20.3784.019; Thu, 28 Jan 2021 21:58:32 +0000
From: Mike Ounsworth <Mike.Ounsworth@entrust.com>
To: LAMPS <spasm@ietf.org>
CC: Douglas Stebila <douglas@stebila.ca>
Thread-Topic: KEM-only certificates (KEMTLS)
Thread-Index: Adb1wLUGY43U9lzXQQWGT7DWXZJeOw==
Date: Thu, 28 Jan 2021 21:58:32 +0000
Message-ID: <DM6PR11MB43802D374E23EB20A62C7A179FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=entrust.com;
x-originating-ip: [4.19.72.62]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 53651349-3fc8-410b-9fbb-08d8c3d7dac2
x-ms-traffictypediagnostic: DM6PR11MB4284:
x-microsoft-antispam-prvs: <DM6PR11MB4284AEB97FFBF516E6CDEEAC9FBA9@DM6PR11MB4284.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: hNhfHHWvi6SnOwUmiRLfTA+DF9kdtYQHABgzTqyq1hphtazaG/7qz/HkHOj5YekmsnVhZzxqszPVeCaIp1hwSOPGLDraDc0tNNeKy67POLmXGsXXj0S0wR5tMxzM7uYGxiOpkIj5aADVALWQzWZX+PKKwtYQ1I7uPqjH6v8i9IdUcmFrlJfIqEye0y5pxEnNFArdUwNAHz2rLBI0zbPRHwM645AKto3Wou/9KF/mJ9O9UH9xL4bHZez08DeLL4sVfDRqPXVxoeAvht3VmGRKN/hfQVkNl4jEPQLBrBRG3WR+k/7aXmKXQPNu5yEltIHL3lzJNkdFgBwQ7oLFg0mGwpJc2oDAoFZi+rXXJIbSxdQvUerqJaV8P7gLSCi9kRap3HffPPxu32K5tGajhq3346qPxDFL7aDxEll3ZEUt1WdVrR6SP5ETWNhKfCIgxazDnFVyw3Ze21N0WpeUEtyEkO6nMRWj0GmaxkwvMfhnAOWetACOQRaxe2I8VJStbH4Ima8JVTvQ2dIoiMOBy6kjhcWr+FhZM83H6zewXTk9V7LvGOV37vWVR/dUHP5TwSQp4bY13bFvjcrQIA88UnLjF6rl9TAvbCYldY7y0+9mk78=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB4380.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(39860400002)(396003)(366004)(346002)(136003)(478600001)(966005)(6506007)(8676002)(76116006)(5660300002)(66556008)(66446008)(86362001)(2906002)(66476007)(64756008)(7696005)(8936002)(4326008)(186003)(71200400001)(66946007)(316002)(55016002)(83380400001)(9686003)(52536014)(6916009)(33656002)(26005); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?sub5xedVt93wzy0BM0Az1CT6ppgnwxLkn+cq2vsKQpHfLfAXBvdDSPLCsqjK?= =?us-ascii?Q?NpcUv0S5aWS6m6STXFa8KKtyiiv1KpIgYhI+oKx1iB4uzX5R/tPdyc79JeOQ?= =?us-ascii?Q?L/RRMVwtaAWd+aWPiBf2XnZZ0+EWAc/TJQjlZawJiVdqibSBphk3d3ZuW+oe?= =?us-ascii?Q?qAdaTR3AZmhS1wTdRuQx1r5iDuR7KqIGf8jJZVFy4U9ZSJ0siSR5c5YM6hZR?= =?us-ascii?Q?hDjK9XZSOSVfaAApjK+RuADsQmdhgf1FTHNoak5GrSJy5hPQppgBs5igd35L?= =?us-ascii?Q?Gxq1F1fchpURbneoJD9hn0z2RwrQ2EABUlTTHIRNUg1XGSLu2gZN2AkzJLHM?= =?us-ascii?Q?EXtwxmd39dJ+a4xHDr/t+WmAsmtwmhS9p+1HTuXaLDraY87P2DGjzpHWLVcE?= =?us-ascii?Q?XPCGOwo84RJOKqb9qCFs8vBJdeceDLyq+M61Gb2/aqawNRQQUzpsIQG8Du/z?= =?us-ascii?Q?1Gu2OFnU7ueqhxAGEUlwIp6Z1fEQooUZaBleS1cJpPKoc2Yb9ED/hgb182Qn?= =?us-ascii?Q?MpWhKxVfnBzNEV1u5M62FqPtoxh6e7+KcvUzgtqBUjCX5eRbf+WBKTu7N9N0?= =?us-ascii?Q?A5R6uKXmSgC50RZbjSGG0k7nENyHFU7qnm5gbz9K/j4aem+FW3HE8Q4X5sO6?= =?us-ascii?Q?Hb6kZvzGsW50/bJ+Tgxz4ixSQzPPFU111D35Hc2Igd91QXBJrCA3CP6lG6ZX?= =?us-ascii?Q?UlT10s3Q/ysZP1JnUKmDtw7e4qhXzkS+0tYS0ieOF0NpNcPHE/YIxMZSOIqd?= =?us-ascii?Q?kiGc9iSmOlUAaFEFkzjeItSx+c2BCutqeRTQ3Uwp3Tb682UxlDtPhyLd4R3L?= =?us-ascii?Q?K6JWPuUhb9iUYjb8h5KQWOfTOl1TIpF7k63dpuv81eTiAQliBPfPg7blbUWW?= =?us-ascii?Q?FlMI+RjuVUbOf5At4WVf6x8QNQTKzlAH7bNZQZSPaFKxOHisWZE9u5KST3cZ?= =?us-ascii?Q?w2pSiZfQHBN9EELxGSyMXWaUJ5ML5VXxBWA/WJQeZzkY83XeqYE77mUYrE2F?= =?us-ascii?Q?FBhSspD9Aplwcc5Lse1cAyPCfSfQMsYwpZxHhoJlK6zNHl0=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: entrust.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4380.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 53651349-3fc8-410b-9fbb-08d8c3d7dac2
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jan 2021 21:58:32.7628 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f46cf439-27ef-4acf-a800-15072bb7ddc1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: iM+2ATme8cK9avjzHV/pNk4OAfGImooa0XAKpAY1ALW0yNTkFtaX3k6ASYMLSzUdIP0VFhJDFWDmt5ErWAjo2bob3HwQC1NyX869BlJDeew=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4284
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/1TxkuvIasCffeABFHrzVb9mC92o>
Subject: [lamps] KEM-only certificates (KEMTLS)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 21:58:40 -0000

TL;DR: No immediate action, but something to keep an eye on.

I did not spend time on this during my talk today because I didn't want to =
distract from the Composite topic, but I want to draw attention to my "Bonu=
s topic" slide about KEM certificates. I don't know if anyone else is follo=
wing the KEMTLS discussions (references below), but that would require PKIs=
 to issue large amounts of Key Establishment Mechanism (KEM; aka keyUsage: =
keyEncipherment) TLS certificates. If TLS WG decides to adopt the KEMTLS dr=
aft, then LAMPS probably needs to take a look at PKIX to make sure we can h=
andle enrollment, update, revocation for clients that don't have signing ke=
ys. I took a (very) quick pass over CMP, Lightweight CMP, EST (both simple =
and full-CMC) and attempted to summarize findings in my "bonus topics" slid=
es.

1: My slides from today: https://datatracker.ietf.org/meeting/interim-2021-=
lamps-01/materials/slides-interim-2021-lamps-01-sessa-position-presentation=
-by-mike-ounsworth-00.pdf
2: "Post-quantum TLS without handshake signatures", Schwabe, Stebila, Wigge=
rs, https://eprint.iacr.org/2020/534
3: "KEMTLS: Post-quantum TLS without signatures", Celi, Wiggers, https://bl=
og.cloudflare.com/kemtls-post-quantum-tls-without-signatures/

---
Mike Ounsworth
Software Security Architect, Entrust


From nobody Thu Jan 28 19:53:02 2021
Return-Path: <pkampana@cisco.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE2B3A09BD for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 19:53:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.621
X-Spam-Level: 
X-Spam-Status: No, score=-9.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=EJzs7j3k; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.onmicrosoft.com header.b=uoaD0yGJ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D9mg4NcUMThZ for <spasm@ietfa.amsl.com>; Thu, 28 Jan 2021 19:52:57 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB6683A09B7 for <spasm@ietf.org>; Thu, 28 Jan 2021 19:52:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9170; q=dns/txt; s=iport; t=1611892376; x=1613101976; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=JzPINhNomWcWqkzaj+sVHUTXM+m5TQ5ehdLeUHbncvs=; b=EJzs7j3k6i/e0Jy0xjoiwk4SRswllcC97CrH561wFW97iOB2kIPelmUO VHp5VdS9v/eslacu6Pa9v1iFy0O64Km0wyBQE+OLyTCcjLeHleSc0O6bp GzCQvULw2XWH8Jo2nxFDFbaBGewU4lyEhr9DYoSBnUmwEO7K3/+v+YYS2 A=;
X-Files: smime.p7s : 4024
X-IPAS-Result: =?us-ascii?q?A0A7CwCRhBNg/4gNJK1iHgEBCxIMQIMiUQd2LC4yLwoBh?= =?us-ascii?q?30DjgcDmRmCUwNUBAcBAQEKAwEBGA0IAgQBAYFVgnUCgXgCJTgTAgMBAQEDA?= =?us-ascii?q?gMBAQEBBQEBAQIBBgRxhWENhXMBAQEEAQE+AQEsCwELBAIBCBEEAQEvAiULH?= =?us-ascii?q?QgBAQQBDQUIBoMZgX5XAx8PAQ6qFAKKJXSBNIMFAQEGgTMBAwKDSxiCCwcDB?= =?us-ascii?q?oE4gVOBJIpHCB4bgUE/gRFDglY+gl0BAQOBJh4ag0uCLIFPe2hRAiA3BAsyC?= =?us-ascii?q?BROKQYrGIpwhFoVIYt7nDYKgnaEYYJpgWiMLIY5gy6fVpQoggiJG5FvhE8CB?= =?us-ascii?q?AIEBQIOAQEGgW0jgVdwFTuCaVAXAg2OIQwXg06FFIVEdDcCBgoBAQMJfIoIA?= =?us-ascii?q?TBgAQE?=
IronPort-PHdr: =?us-ascii?q?9a23=3AglbDUBXzSTpCoRbDHLkfgjT2vQfV8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSBN+Huf5BgvDd9aHtRWJG5oyO4zgOc51JAh?= =?us-ascii?q?kCj8he3wktG9WMBkCzKvn2Jzc7E8JPWB4AnTm7PEFZFdy4awjUpXu/vjIXEw?= =?us-ascii?q?/0cwt4OuqzHZTd3Iy70umo8MjVZANFzDO2fbJ1KkCwqgPc/skbiIdvMOA/0B?= =?us-ascii?q?zM93BJYO9Rg2hvIAGe?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,384,1602547200";  d="p7s'?scan'208";a="635031968"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Jan 2021 03:52:55 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 10T3qtMj013929 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 29 Jan 2021 03:52:55 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 28 Jan 2021 21:52:55 -0600
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 28 Jan 2021 22:52:54 -0500
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 28 Jan 2021 22:52:54 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YDhltCSBUnYdX7LZfdB7pSRbdnRF5YqKg6o6QeyhOJiyjm7Vc/Rv1RjD40JfPtoHNdFBjBuLt+ux4TkWUjCOV86htIuG840NgXYNPDpjPcE+wqgZWGoGhJSYhgVaXWWm1I7zoMi6dQv2mH6Z2V8HlpFd02F0EPpConzWj/FGalpVbIFUJubqOjr08fkjw7oQMTSZf6/gWp7EABvok9oxMpTBJwdJUHphhA9F0cWlmlR4tV2AGMX7seQ9yvnzrGzi2R9Siew9Q4y9wmUB5KNa0ekbeOONPxYftJiL0CN/F8hSI4WSqY8qzkmz6UF4E41YZ4BSk6U1Djlx4IuxJIII7g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ysQHcjHLi+N0VoFzvVJAsEvMRdbN70RhClUE5EwhcDI=; b=QQwuC6i91ZDEKt4CHkHTQ9jnj9eGyZ83J50riGj7lTlDaZ/H0hOg+SffDK/Aamfh1sc/X+HQboDuyRW8YWW8hjhQ9oCJnHMdXK0s44HHdf+IWJL7ogeXeEFHw7T+IuC28Qvd8O+TBLdYz+PSshRtGuZFUalOvu7LrHoQ/+tZIM3WaTKuKIQZaQlA6EAlkZF5egCiNUIYEOjos4bnximmtDTv1TM4DgJeJn8jSI+xE9VzDwmjqXW492nfq1e9qHI1+S24kaZJB8amQkpY6D2L0e4Mm8oEnqwcyx1SdieHnoN391y4f4ZOCi6Acn5TKXfoAxRH69L8Os377wSDn2jJSQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ysQHcjHLi+N0VoFzvVJAsEvMRdbN70RhClUE5EwhcDI=; b=uoaD0yGJ6QuKmRy8s2ppFoH20evx4hOl/80zkifiozeWPkounlAqqOnzDHsnRv3ezIodpkL3quOEeeUfucrTMLBZQRVPfFpCQnLgGozleII51u84ope+2gWHBedaW2qlwIa5Xgvr8wYMRrjuRjZTLZxJZX9oHzhQ1lvcFrLwtPo=
Received: from BN7PR11MB2547.namprd11.prod.outlook.com (2603:10b6:406:af::18) by BN6PR11MB1810.namprd11.prod.outlook.com (2603:10b6:404:fc::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.17; Fri, 29 Jan 2021 03:52:53 +0000
Received: from BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::651c:70ca:fdc4:25eb]) by BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::651c:70ca:fdc4:25eb%3]) with mapi id 15.20.3784.019; Fri, 29 Jan 2021 03:52:52 +0000
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>, LAMPS <spasm@ietf.org>
CC: Douglas Stebila <douglas@stebila.ca>
Thread-Topic: KEM-only certificates (KEMTLS)
Thread-Index: Adb1wLUGY43U9lzXQQWGT7DWXZJeOwALd/gw
Date: Fri, 29 Jan 2021 03:52:51 +0000
Message-ID: <BN7PR11MB254768723D3C932F74A5BFACC9B99@BN7PR11MB2547.namprd11.prod.outlook.com>
References: <DM6PR11MB43802D374E23EB20A62C7A179FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
In-Reply-To: <DM6PR11MB43802D374E23EB20A62C7A179FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [68.93.142.48]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 30158ee4-30b7-41ec-4b34-08d8c4095aba
x-ms-traffictypediagnostic: BN6PR11MB1810:
x-microsoft-antispam-prvs: <BN6PR11MB18105DA8FA98A000D96AC49BC9B99@BN6PR11MB1810.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 1BwGxKKe81IXBQenRdvYrC397Ha5PuKzpJpA8OSJGjejB2jq60DTgpzqLr+/090SkxcUrGaFlx4IGbKDUXJcI7w0LwD/64+cr6Y7KmUv0bgCjcyYXF8av3hGWKNb1XBoJneMZ2Vvhj0VfIF2r3KI+BMlibpTHexN1vSN8A8ZJ8yTNjuRVKDwRVDkFD54JiCuw/aex89oHiNWaeqTTAGJ6IppmpA4f5XuyTP2kmjfQb5s3wVB0rLMdgN+CwFnCMX870HQe1nniz3dUQeY8k7zLQhS+HEKSknorbgR6CDJ7acbPk3tfY1OxxO6Ls8GggsA2Tm0cdmV3aFjftK1TQ9vU/m3qBS1KDOmSTn7BHw5nn6KhghlCNwYEVaGqGXWRrdLQz/znMCrBteokn0qeK5xQrQiYZVT02RVUUMpNq4XPeyngqM9jOq36VcaR/opW0jhwXrDjPG8LR0ewtOr1Xf8wycEOEVldObS1naZJ3tDwCuZMslA7CxqUzjq9ILMa/lU6MrUIddygY1x/bE6iuDY3BL80EbU9ZoevuRQXO3EGJZcmvkaeo+cjs7GsUGXZIKlvP4/6hLad97YLA7nK1jaP76Rd2US4u6eboalXWclYBc=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BN7PR11MB2547.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(376002)(366004)(396003)(39860400002)(136003)(346002)(478600001)(33656002)(86362001)(76116006)(5660300002)(66476007)(2906002)(66556008)(66946007)(53546011)(966005)(64756008)(66616009)(8676002)(7696005)(186003)(4326008)(83380400001)(66446008)(6506007)(316002)(52536014)(26005)(9686003)(8936002)(99936003)(110136005)(55016002)(71200400001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?3aUFPEtFiXLekax0qcQm2ZCcjwnGfDdHZV9NSiRaG3I8XOgaLW7mU8Z6P3/i?= =?us-ascii?Q?vELhOYdS2LP/QIg+B51VaabFmrkP1xOztF9OEVtgNWHx4WrGm4i7ZbDnLOxc?= =?us-ascii?Q?vvgXEHs5wolfy/2YKQRCwcqvczVFK+tl0jOFGSWBgr8XAn1TOR7i3iNq+DTZ?= =?us-ascii?Q?IR5RSTqFK4amS0fo1ye1XoF6etARnyzKxv2GHdC9NREfYQDZaytpUX6fF4qe?= =?us-ascii?Q?EuAW8ucR8NRS+/mg/82vU9k9/EAan4PJXhMta24Iwqrwq7AJl2Y7KQbHRw2S?= =?us-ascii?Q?rdc5s/fk//eYX0B41XNPhkDmu9iSlknNR59f+Ps8gKNfnRkgu1glaoU1TUe0?= =?us-ascii?Q?vKdYcN6VN6py//QMNhEaoyqtKLluikgehDOrBQxWqf/xkiNgj/bgGZp4pBCH?= =?us-ascii?Q?eW2plc22hN2qHFQZR75WiZekLHe7Yq5Sqxi1c+JtVP3lC223VO2SwPZGl9kw?= =?us-ascii?Q?yiZaeDmv9TngVCtR7TTx2iiKZcg8gYFN0n4YbuSsXk+t2Sebs0E0snvjbZta?= =?us-ascii?Q?dR+QJtj68Kv6Q6i7bHAQxZVluMp+UPp83Pl6U1eAjfKE6yrBnlQ11jS+4Ko3?= =?us-ascii?Q?7HcocEY0emBLeHCWmaBozjotKdY6ZCk4R2h8KJLDICMUNsugPLjjbBCzOwr/?= =?us-ascii?Q?gi4QJ/ExEIDlIQJPSvDRaTlF49sG7+KjZ0/2jaS1yOj7PbfaaJU85WWRv1Ua?= =?us-ascii?Q?DygnUiBVMKzAJlsQuYxEQT0F/D71rq96ftMSRSP6z3aQk9mR8NtNt8LRJYZL?= =?us-ascii?Q?LM0I4bKJQ5ZsvStIShA4VzEq/yqKIcNrtEJa6QL5XVjgK8lpST1TRQ1N9dA0?= =?us-ascii?Q?ZX9Pp8hPZOj5KBqEWNRZ+iB7Qn4gVfxliymPdZQ1/ZNirCB7J02PDwxTtgg6?= =?us-ascii?Q?4+d7XI7pqUdo8qpJGzlbdlzR0TjE36+nFDNB0RVAktx6nUSokyG4fs+SKFUL?= =?us-ascii?Q?qrqUsTTblo/eIKmo59kN0EjSeccZ0UBrYcm01WmASRHXXvCCCnWbBaDNXDFe?= =?us-ascii?Q?9oUaJBuG+78hh26h7uuerE4FQB/ece9YbIpVa7tqD//iEwtkEnTBU2BarT4D?= =?us-ascii?Q?76E6AqtE?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=2.16.840.1.101.3.4.2.1; boundary="----=_NextPart_000_0005_01D6F5C8.4D70C9F0"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN7PR11MB2547.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 30158ee4-30b7-41ec-4b34-08d8c4095aba
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jan 2021 03:52:52.7564 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: W5B2za+WszoamQNyn0mDzSZsHdJ3PY22hl/13ypOHVWuGvvGTdL6OV3sKnAjUrkmBehwva4mHx/AMHg2qhoV0g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1810
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/DVcwvIuoEodZlbTCSLb8Q97mLTc>
Subject: Re: [lamps] KEM-only certificates (KEMTLS)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 03:53:00 -0000

------=_NextPart_000_0005_01D6F5C8.4D70C9F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hopefully we will get to discuss KEMTLS if the Cloudflare folks bring this
to the TLS WG. 

KEM-TLS is a neat idea, but not as easy as swapping a Sig with a KEM in the
leaf cert. If it was swapping (EC)DSA with (EC)DH as a KEM, then it would be
trivial as proposed in
https://tools.ietf.org/html/draft-ietf-tls-semistatic-dh. But it doesn't
work like that with PQ KEMs. 

KEMTLS introduces drastic changes to the handshake like implicit and
explicit trust and the option to send encrypted data to the server that has
not been fully authenticated yet. These concepts have not existed in TLS so
far. We are talking about TLS 1.4 here and a new security proof. It is no
longer TLS 1.3 with minor changes. Nothing wrong with that, but it is not a
trivial change at all.

The advantages of KEMTLS are 
- In KEMTLS the KEM is only used at the leaf. The rest of the cert chain
still uses Signatures. Thus, the signer does not need to support a PQ
signature algorithm but the verifier still needs to support a PQ signature
algorithm.
- KEMTLS saves 1-2KB of data compared to PQ Signatures (assuming Dilithium,
Falcon) which is an improvement, but based on experiments so far, it would
not have significant impact on a real-world handshake. It may impact
constrained mediums with high loss probability, but it won't be noticeable
for the rest of the handshakes. 
- The PQ KEM may have better side-channel resistance than the PQ signature
scheme.
- KEMTLS may be slightly faster if we are assuming Falcon, but not for
Dilithium. 

Rgs,
Panos

-----Original Message-----
From: Spasm <spasm-bounces@ietf.org> On Behalf Of Mike Ounsworth
Sent: Thursday, January 28, 2021 4:59 PM
To: LAMPS <spasm@ietf.org>
Cc: Douglas Stebila <douglas@stebila.ca>
Subject: [lamps] KEM-only certificates (KEMTLS)

TL;DR: No immediate action, but something to keep an eye on.

I did not spend time on this during my talk today because I didn't want to
distract from the Composite topic, but I want to draw attention to my "Bonus
topic" slide about KEM certificates. I don't know if anyone else is
following the KEMTLS discussions (references below), but that would require
PKIs to issue large amounts of Key Establishment Mechanism (KEM; aka
keyUsage: keyEncipherment) TLS certificates. If TLS WG decides to adopt the
KEMTLS draft, then LAMPS probably needs to take a look at PKIX to make sure
we can handle enrollment, update, revocation for clients that don't have
signing keys. I took a (very) quick pass over CMP, Lightweight CMP, EST
(both simple and full-CMC) and attempted to summarize findings in my "bonus
topics" slides.

1: My slides from today:
https://datatracker.ietf.org/meeting/interim-2021-lamps-01/materials/slides-
interim-2021-lamps-01-sessa-position-presentation-by-mike-ounsworth-00.pdf
2: "Post-quantum TLS without handshake signatures", Schwabe, Stebila,
Wiggers, https://eprint.iacr.org/2020/534
3: "KEMTLS: Post-quantum TLS without signatures", Celi, Wiggers,
https://blog.cloudflare.com/kemtls-post-quantum-tls-without-signatures/

---
Mike Ounsworth
Software Security Architect, Entrust

_______________________________________________
Spasm mailing list
Spasm@ietf.org
https://www.ietf.org/mailman/listinfo/spasm

------=_NextPart_000_0005_01D6F5C8.4D70C9F0
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCDGkw
ggNDMIICK6ADAgECAhBf+HsoK1TcjUKjFbVoya3/MA0GCSqGSIb3DQEBBQUAMDUxFjAUBgNVBAoT
DUNpc2NvIFN5c3RlbXMxGzAZBgNVBAMTEkNpc2NvIFJvb3QgQ0EgMjA0ODAeFw0wNDA1MTQyMDE3
MTJaFw0yOTA1MTQyMDI1NDJaMDUxFjAUBgNVBAoTDUNpc2NvIFN5c3RlbXMxGzAZBgNVBAMTEkNp
c2NvIFJvb3QgQ0EgMjA0ODCCASAwDQYJKoZIhvcNAQEBBQADggENADCCAQgCggEBALCauaunrwp3
p+JxtrRmYpR4iEfGYlWEQDK/wKsupRxx1rxue6iqum7SFYhIRZ2i/IPQzLmM4CZocEp43yEXnvRh
BckVyM8W2jVhiZRDqISoMZh4m7lObyxTEmzNHa0rJLsxxCv/g0Rvtj0kdwnqvyqoH2pW9iAPEVSX
gXWnJc5ZaoJl77fq5+KNdYtu8t1Ppl5inM8QCmTQTm3OK8xb9WClJ0eNafR/zhtw3nAbINZuzaYB
qDwS0qk/oGteu44gi3qR47Vo7qDnxAF0qFMLK0qaD2USDoJNjmP97+ubGttTphNgr8J918dsFyXU
c/tHZFCBgJRM4b+uSxzfku0uBd8CAQOjUTBPMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/
MB0GA1UdDgQWBBQn88gVHm6aAgkWrSugiWBf2nsvqjAQBgkrBgEEAYI3FQEEAwIBADANBgkqhkiG
9w0BAQUFAAOCAQEAnZ2EhKNBqXx3DLdTyk5EUGLvVHzTdRcc6ODGSEu2/kw6GYFWsFbuGZZiqlqj
ZMH2TlQzxnf+xRy65V0lyvXwk5qDES7my/h0Rf7nBbir59/LS+E3hNq5i5dwHvDii9ew2A6dsWnW
KpF7qUlPfuaOldiDJzzVaEkO1J32LuunvuswpKwfRPyVqzMG+31gCt60imOwnKnypLlTAYfQaKQn
f6v/6frJQDiIZ7Q5xoRvV8lT27qO7sBDsvgJg27/Zs8+7xezWBglCTRe48vWFLbs8pJvdOQvgSrV
kpHg4Jc8MmgFhUvR91fiUh2TGlSfBXDASnFgHkMLYB7+o86BGeELNTCCBG4wggNWoAMCAQICCmEQ
gG0AAAAAAA4wDQYJKoZIhvcNAQEFBQAwNTEWMBQGA1UEChMNQ2lzY28gU3lzdGVtczEbMBkGA1UE
AxMSQ2lzY28gUm9vdCBDQSAyMDQ4MB4XDTE0MDQwNDIwMjQxOFoXDTI5MDUxNDIwMjU0MlowLDEO
MAwGA1UEChMFQ2lzY28xGjAYBgNVBAMTEUNpc2NvIEVtcGxveWVlIENBMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAyt9+FkxTFfsjVs3GuWUKBJXl3kxFZ4wMxwbgqx9tXzcqe+fto62A
fxHI84Lr7p9Q2cm/PaEvuzwRBzXvuKXZUU7ZsPdToJSALCySZa0Qb6GGa19ACpmlUEQakE3P5kz7
RgaNSOMH1+GtY9fV6CcAFb9uB7JDu2UGL332WV2bEsUsfb3rRLBS4cL8Hu2dWfcdk6erMaZCQjkn
04FixlQsJozbPRTQqI4V6iikG/69rDyeTdbVTK+My/9LnwVsD3GBMiRh7RmrvupxtGiMu8j05Is/
d1OifhWecwvjV3Reg9Lok8bMNJEMAped1weTdVS0X4MsAheosJBld9lS5O4idwIDAQABo4IBhzCC
AYMwEAYJKwYBBAGCNxUBBAMCAQAwHQYDVR0OBBYEFJ+VNrSOXdVLwwrBpymTQ1EG/YlRMBkGCSsG
AQQBgjcUAgQMHgoAUwB1AGIAQwBBMAsGA1UdDwQEAwIBhjASBgNVHRMBAf8ECDAGAQH/AgEAMB8G
A1UdIwQYMBaAFCfzyBUebpoCCRatK6CJYF/aey+qMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly93
d3cuY2lzY28uY29tL3NlY3VyaXR5L3BraS9jcmwvY3JjYTIwNDguY3JsMFAGCCsGAQUFBwEBBEQw
QjBABggrBgEFBQcwAoY0aHR0cDovL3d3dy5jaXNjby5jb20vc2VjdXJpdHkvcGtpL2NlcnRzL2Ny
Y2EyMDQ4LmNlcjBcBgNVHSAEVTBTMFEGCisGAQQBCRUBFQAwQzBBBggrBgEFBQcCARY1aHR0cDov
L3d3dy5jaXNjby5jb20vc2VjdXJpdHkvcGtpL3BvbGljaWVzL2luZGV4Lmh0bWwwDQYJKoZIhvcN
AQEFBQADggEBAD5OviMaRgKNXmvbigI0C2Ob5QE8Jl2McLIk62Be7IqEZC4bWRWjZxrhFuP94E19
RJojKNLttveiH+dEze1t6oYhVCisbGG8+8hlUARAiiqL/J9uGJ71xT6loqkcAK5xphe7STJLSlgT
k0w26fcvDeiA6zhdVHnKhVKkpOJWd9MNByFOnCQyDOK+pcNxLU6IN9TwL1ZoRkdFa11QiCX3Oimk
8YhBrVN+VzGGKtbgZ4fYU6uBo3V3vtshyDpHtGkn1e7f9/TWcY26etFzL33dzaZ4lChlw4l3XkLq
6AfCEDF5djpBdiCRjwpBUIIbCSmyESBvA+sL4j8i1vo/uEartrAwggSsMIIDlKADAgECAgoBhhEi
QTzquitVMA0GCSqGSIb3DQEBCwUAMCwxDjAMBgNVBAoTBUNpc2NvMRowGAYDVQQDExFDaXNjbyBF
bXBsb3llZSBDQTAeFw0xOTEyMjAxOTQ5MDJaFw0yMTEyMTkxOTU5MDJaMIGfMSQwIgYDVQQDExtQ
YW5vcyBLYW1wYW5ha2lzIChwa2FtcGFuYSkxFDASBgNVBAsTC0Npc2NvIFVzZXJzMRIwEAYDVQQL
EwlFbXBsb3llZXMxEzARBgoJkiaJk/IsZAEZEwNjb20xFTATBgoJkiaJk/IsZAEZEwVjaXNjbzEh
MB8GCSqGSIb3DQEJAQwScGthbXBhbmFAY2lzY28uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAmIHTLIzoAnuMUiHMx8V+PF9JpAcB7zrNHOY1Vj1R1Vx7ty7m9yo9G991T2n7zHo4
UzF6tnB9NxzQOKCY54oqP5KjVGYOPPo+qZ+2rx1GABzdKUF4LwUUKOTf9uXAtvsvIRUc5J/csShT
jcUIvtVmiAzWXWRfMYShjBYBVtx/h8fDqAqfFAzd6HG0TcdsN/BRb9k6QEW1afHjPKlRUaDRELyj
nFGJZd2OsUJ7/aKMdFmQFd2CAJYzsuwLYjeqJsuGNzBc/k6mzQPf6FW17nz17G41KReU0UdZf2yZ
jvimkwCQ/yW8SVTOcGBP+Zk+Lq5EYEGQMu1qtNK/97bXMc5kuwIDAQABo4IBWjCCAVYwDgYDVR0P
AQH/BAQDAgTwMAwGA1UdEwEB/wQCMAAwegYIKwYBBQUHAQEEbjBsMDwGCCsGAQUFBzAChjBodHRw
Oi8vd3d3LmNpc2NvLmNvbS9zZWN1cml0eS9wa2kvY2VydHMvY2VjYS5jZXIwLAYIKwYBBQUHMAGG
IGh0dHA6Ly9wa2ljdnMuY2lzY28uY29tL3BraS9vY3NwMB8GA1UdIwQYMBaAFJ+VNrSOXdVLwwrB
pymTQ1EG/YlRMDoGA1UdHwQzMDEwL6AtoCuGKWh0dHA6Ly9jaXNjb2NlcnRzLmNpc2NvLmNvbS9m
aWxlL2NlY2EuY3JsMB0GA1UdEQQWMBSBEnBrYW1wYW5hQGNpc2NvLmNvbTAdBgNVHQ4EFgQUjrl7
6Mrrdw3ZYFiTpZBdtrUm5P4wHwYDVR0lBBgwFgYKKwYBBAGCNwoDDAYIKwYBBQUHAwQwDQYJKoZI
hvcNAQELBQADggEBAMhR6xCTygu68lppjWebXTXYznix5961hcmwiJRkPtUIGQ5JQwXyCwq/Juuq
yc5ebeq9cQEO5iqyxik/UAQ35BlmKb7SNLi75RtFE/AIZrRsEjTUoO2EtCMQOEMcenWa2XE8fEID
BkwzreKeaOchCbDd4L9PvKFht6nDDFtb6VZdWs4ort+J3iFeilVf3oI5MSVi+qroWaFLnLYTQGTn
qEjWANfKw3RRBAMdoPCZ+N4eftAk1TWVS08nOsPoKWXtIqX6y0ZPs/EZjBSk57v1TPLpYhEqYGXI
oGJlIvzIAfYNoUg8yP8toG5T7x+7hRz0MMUGWcCDsS9PMFxH6SnrUSMxggMNMIIDCQIBATA6MCwx
DjAMBgNVBAoTBUNpc2NvMRowGAYDVQQDExFDaXNjbyBFbXBsb3llZSBDQQIKAYYRIkE86rorVTAN
BglghkgBZQMEAgEFAKCCAaQwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMjEwMTI5MDM1MjQ5WjAvBgkqhkiG9w0BCQQxIgQgmRfBPoKhA18apwPoUHgvw2dcPtTS9TiC
gqx9w/MFUfgwSQYJKwYBBAGCNxAEMTwwOjAsMQ4wDAYDVQQKEwVDaXNjbzEaMBgGA1UEAxMRQ2lz
Y28gRW1wbG95ZWUgQ0ECCgGGESJBPOq6K1UwSwYLKoZIhvcNAQkQAgsxPKA6MCwxDjAMBgNVBAoT
BUNpc2NvMRowGAYDVQQDExFDaXNjbyBFbXBsb3llZSBDQQIKAYYRIkE86rorVTCBoAYJKoZIhvcN
AQkPMYGSMIGPMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCgYIKoZIhvcNAwcwCwYJYIZIAWUD
BAECMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDALBglghkgBZQMEAgEwCwYJKoZIhvcN
AQEKMAsGCWCGSAFlAwQCAzALBglghkgBZQMEAgIwBwYFKw4DAhowDQYJKoZIhvcNAQEBBQAEggEA
bYWEWi2/Bw5dp5GoSaTWApeYKhwmnqsHYBOtsFO/98YaBP1tR2R+uJAl7hfDN075iLdeuGAnoupC
QYt62bVgmPuWaM7PxQz/kebSSslD41MH4UtuXryOmz8W4lD+WLyHrQetLpumQaS/H9ZBxtXprZgQ
rxeEKfU+LLIWfjh5VvIhhlQGvoNMMyBvyaVKDRKx93VGvJTEs2N86GB/J+HQgz/Q+7aqdz+/QLJk
GKKkZ0Uk82N2eJipacvbOgyEuVrY1PtQVm1cmWME50fmPHC9jxOFwPWtVyvV8bLcfgEkSt8Dn/J5
uX1fdAtlurXahIBTOq8GQdpI0GcT1eNvJcfP2AAAAAAAAA==

------=_NextPart_000_0005_01D6F5C8.4D70C9F0--


From nobody Fri Jan 29 09:16:10 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E51E23A1191; Fri, 29 Jan 2021 09:16:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: spasm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: spasm@ietf.org
Message-ID: <161194056487.11286.4506801369846006255@ietfa.amsl.com>
Date: Fri, 29 Jan 2021 09:16:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/RtRA42i18_oMQ4-Pg4J1sMUoqUQ>
Subject: [lamps] I-D Action: draft-ietf-lamps-crmf-update-algs-03.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 17:16:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Limited Additional Mechanisms for PKIX and SMIME WG of the IETF.

        Title           : Algorithm Requirements Update to the Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)
        Author          : Russ Housley
	Filename        : draft-ietf-lamps-crmf-update-algs-03.txt
	Pages           : 8
	Date            : 2021-01-29

Abstract:
   This document updates the cryptographic algorithm requirements for
   the Password-Based Message Authentication Code in the Internet X.509
   Public Key Infrastructure Certificate Request Message Format (CRMF)
   specified in RFC 4211.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lamps-crmf-update-algs/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-lamps-crmf-update-algs-03
https://datatracker.ietf.org/doc/html/draft-ietf-lamps-crmf-update-algs-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lamps-crmf-update-algs-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Fri Jan 29 09:27:34 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9B43A119D for <spasm@ietfa.amsl.com>; Fri, 29 Jan 2021 09:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRKsERjBV8Ig for <spasm@ietfa.amsl.com>; Fri, 29 Jan 2021 09:27:29 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 579D43A116F for <spasm@ietf.org>; Fri, 29 Jan 2021 09:27:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6D9DA300B93 for <spasm@ietf.org>; Fri, 29 Jan 2021 12:27:26 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id o5yg1WEu69A2 for <spasm@ietf.org>; Fri, 29 Jan 2021 12:27:24 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 971F5300B78 for <spasm@ietf.org>; Fri, 29 Jan 2021 12:27:24 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Fri, 29 Jan 2021 12:27:25 -0500
References: <161194056513.11286.8665929175142199665@ietfa.amsl.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <161194056513.11286.8665929175142199665@ietfa.amsl.com>
Message-Id: <CFDA135B-CD86-49AC-908D-F61389660B14@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/UNOEv6IG6tQQR18KpDyxOzeIgYQ>
Subject: Re: [lamps] New Version Notification for draft-ietf-lamps-crmf-update-algs-03.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 17:27:33 -0000

This revision addresses several recent comments:

Signature Key POP:

   algId identifies the algorithm used to compute the MAC value.  All
   implementations MUST support id-PasswordBasedMAC as presented in
   Section 4.4 of this document.  Implementations MAY also support
   PBMAC1 presented in Section 7.1 of [RFC8018].

Iteration Count:

   There is a trade off between protection of the password from
   attacks and the time spent by the server processing the
   iterations.  As part of that tradeoff, an iteration count smaller
   than 10,000 can be used when automated generation produces
   shared secrets with high entropy.

GMAC MAC Length:

   The GMACParameters length parameter field tells the size of the
   message authentication code in octets.  GMAC supports lengths
   between 12 and 16 octets, inclusive.  However, for use with CRMF,
   the maximum length of 16 octets MUST be used.

References:

   Point to draft-ietf-lamps-cms-aes-gmac-alg.

   Used a shorter anchor name for NISTSP800-63B.

With these changes, I believe that all open comments have been =
addressed.

Russ


> On Jan 29, 2021, at 12:16 PM, internet-drafts@ietf.org wrote:
>=20
>=20
> A new version of I-D, draft-ietf-lamps-crmf-update-algs-03.txt
> has been successfully submitted by Russ Housley and posted to the
> IETF repository.
>=20
> Name:		draft-ietf-lamps-crmf-update-algs
> Revision:	03
> Title:		Algorithm Requirements Update to the Internet =
X.509 Public Key Infrastructure Certificate Request Message Format =
(CRMF)
> Document date:	2021-01-29
> Group:		lamps
> Pages:		8
> URL:            =
https://www.ietf.org/archive/id/draft-ietf-lamps-crmf-update-algs-03.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-ietf-lamps-crmf-update-algs/
> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-ietf-lamps-crmf-update-algs
> Htmlized:       =
https://tools.ietf.org/html/draft-ietf-lamps-crmf-update-algs-03
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-lamps-crmf-update-algs-03
>=20
> Abstract:
>   This document updates the cryptographic algorithm requirements for
>   the Password-Based Message Authentication Code in the Internet X.509
>   Public Key Infrastructure Certificate Request Message Format (CRMF)
>   specified in RFC 4211.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
>=20


From nobody Fri Jan 29 17:01:42 2021
Return-Path: <Daniel.VanGeest@isara.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 561EC3A143D for <spasm@ietfa.amsl.com>; Fri, 29 Jan 2021 17:01:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2I5V50em_Zbq for <spasm@ietfa.amsl.com>; Fri, 29 Jan 2021 17:01:38 -0800 (PST)
Received: from esa1.isaracorp.com (esa1.isaracorp.com [207.107.152.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F0963A143C for <spasm@ietf.org>; Fri, 29 Jan 2021 17:01:37 -0800 (PST)
Authentication-Results: ip1.isaracorp.com; spf=Fail smtp.mailfrom=Daniel.VanGeest@isara.com; dkim=none (message not signed) header.i=none; dmarc=fail (p=none dis=none) d=isara.com
IronPort-SDR: aLosTlen4z1MhvHSfIEw0tnmSAqOV0weJsgEaao+5ZeZsj7mXjQ9RDAAqnx8uTdmDhQ0reS282 eggMwkdEsrE2odzWGq3lueIXXWejcwCqZtUyCPnUg7bH4GTRfOMENXqRTtbQ7W41jYuDrFc4ps rrp3p7xr1pE1+7jyzuIIscQ+UXQBtwZWCWOsK++hRp5ry5TvSzEVcvAUwhCTZ1jAOudcBn7sJU kmZOheMMVwhTsEEhxORw4N/bBaX4w0WiCfrmhy5dxBN2Pph7eHobb0vv/VPED3QupPl7A2+AAY tNE=
Received: from unknown (HELO V0501WEXGPR01.isaracorp.com) ([10.5.8.20]) by ip1.isaracorp.com with ESMTP; 30 Jan 2021 01:01:35 +0000
Received: from V0501WEXGPR01.isaracorp.com (10.5.8.20) by V0501WEXGPR01.isaracorp.com (10.5.8.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2106.2; Fri, 29 Jan 2021 20:01:35 -0500
Received: from V0501WEXGPR01.isaracorp.com ([fe80::d802:5aec:db34:beba]) by V0501WEXGPR01.isaracorp.com ([fe80::d802:5aec:db34:beba%6]) with mapi id 15.01.2106.002; Fri, 29 Jan 2021 20:01:35 -0500
From: Daniel Van Geest <Daniel.VanGeest@isara.com>
To: "Panos Kampanakis (pkampana)" <pkampana=40cisco.com@dmarc.ietf.org>, "Mike Ounsworth" <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>, LAMPS <spasm@ietf.org>
CC: Douglas Stebila <douglas@stebila.ca>
Thread-Topic: [External]Re: [lamps] KEM-only certificates (KEMTLS)
Thread-Index: AQHW9qN01Ku+vl8LsUecqhqxbbmMhQ==
Date: Sat, 30 Jan 2021 01:01:35 +0000
Message-ID: <04AA4363-33A4-4400-9A50-A30D24CA152D@isara.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.5.52]
Content-Type: multipart/alternative; boundary="_000_04AA436333A444009A50A30D24CA152Disaracom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/U0dR5zZudZDqk6sgZ-stESp-T2I>
Subject: Re: [lamps] KEM-only certificates (KEMTLS)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2021 01:01:41 -0000

--_000_04AA436333A444009A50A30D24CA152Disaracom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

V2hpbGUgYW4gYWRvcHRlZCBLRU1UTFMgd291bGQgcmVzdWx0IGluIGEgcHJvbGlmZXJhdGlvbiBv
ZiBLRU0gY2VydHMsIE5JU1Qgd2lsbCBiZSBzcGVjaWZ5aW5nIGhvdyB0byBjb252ZXJ0IEtFTXMg
dG8gcHVibGljIGtleSBlbmNyeXB0aW9uIHNjaGVtZXMgKGh0dHBzOi8vY3NyYy5uaXN0Lmdvdi9w
cm9qZWN0cy9wb3N0LXF1YW50dW0tY3J5cHRvZ3JhcGh5L2ZhcXMgb2xkIFExMyksIHNvIEtFTXMg
d291bGQgYWxzbyBiZSBuZWVkZWQgaW4gRUUgY2VydHMgaWYgdGhleSB3ZXJlIHRvIGJlIHVzZWQg
Zm9yIGtleSB0cmFuc3BvcnQgaW4gQ01TLg0KDQpEYW5pZWwgVmFuIEdlZXN0DQoNCk9uIDIwMjEt
MDEtMjgsIDEwOjUzIFBNLCAiU3Bhc20gb24gYmVoYWxmIG9mIFBhbm9zIEthbXBhbmFraXMgKHBr
YW1wYW5hKSIgPHNwYXNtLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOnNwYXNtLWJvdW5jZXNAaWV0
Zi5vcmc+IG9uIGJlaGFsZiBvZiBwa2FtcGFuYT00MGNpc2NvLmNvbUBkbWFyYy5pZXRmLm9yZzxt
YWlsdG86cGthbXBhbmE9NDBjaXNjby5jb21AZG1hcmMuaWV0Zi5vcmc+PiB3cm90ZToNCg0KSG9w
ZWZ1bGx5IHdlIHdpbGwgZ2V0IHRvIGRpc2N1c3MgS0VNVExTIGlmIHRoZSBDbG91ZGZsYXJlIGZv
bGtzIGJyaW5nIHRoaXMNCnRvIHRoZSBUTFMgV0cuDQoNCktFTS1UTFMgaXMgYSBuZWF0IGlkZWEs
IGJ1dCBub3QgYXMgZWFzeSBhcyBzd2FwcGluZyBhIFNpZyB3aXRoIGEgS0VNIGluIHRoZQ0KbGVh
ZiBjZXJ0LiBJZiBpdCB3YXMgc3dhcHBpbmcgKEVDKURTQSB3aXRoIChFQylESCBhcyBhIEtFTSwg
dGhlbiBpdCB3b3VsZCBiZQ0KdHJpdmlhbCBhcyBwcm9wb3NlZCBpbg0KaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtdGxzLXNlbWlzdGF0aWMtZGguIEJ1dCBpdCBkb2Vzbid0
DQp3b3JrIGxpa2UgdGhhdCB3aXRoIFBRIEtFTXMuDQoNCktFTVRMUyBpbnRyb2R1Y2VzIGRyYXN0
aWMgY2hhbmdlcyB0byB0aGUgaGFuZHNoYWtlIGxpa2UgaW1wbGljaXQgYW5kDQpleHBsaWNpdCB0
cnVzdCBhbmQgdGhlIG9wdGlvbiB0byBzZW5kIGVuY3J5cHRlZCBkYXRhIHRvIHRoZSBzZXJ2ZXIg
dGhhdCBoYXMNCm5vdCBiZWVuIGZ1bGx5IGF1dGhlbnRpY2F0ZWQgeWV0LiBUaGVzZSBjb25jZXB0
cyBoYXZlIG5vdCBleGlzdGVkIGluIFRMUyBzbw0KZmFyLiBXZSBhcmUgdGFsa2luZyBhYm91dCBU
TFMgMS40IGhlcmUgYW5kIGEgbmV3IHNlY3VyaXR5IHByb29mLiBJdCBpcyBubw0KbG9uZ2VyIFRM
UyAxLjMgd2l0aCBtaW5vciBjaGFuZ2VzLiBOb3RoaW5nIHdyb25nIHdpdGggdGhhdCwgYnV0IGl0
IGlzIG5vdCBhDQp0cml2aWFsIGNoYW5nZSBhdCBhbGwuDQoNClRoZSBhZHZhbnRhZ2VzIG9mIEtF
TVRMUyBhcmUNCi0gSW4gS0VNVExTIHRoZSBLRU0gaXMgb25seSB1c2VkIGF0IHRoZSBsZWFmLiBU
aGUgcmVzdCBvZiB0aGUgY2VydCBjaGFpbg0Kc3RpbGwgdXNlcyBTaWduYXR1cmVzLiBUaHVzLCB0
aGUgc2lnbmVyIGRvZXMgbm90IG5lZWQgdG8gc3VwcG9ydCBhIFBRDQpzaWduYXR1cmUgYWxnb3Jp
dGhtIGJ1dCB0aGUgdmVyaWZpZXIgc3RpbGwgbmVlZHMgdG8gc3VwcG9ydCBhIFBRIHNpZ25hdHVy
ZQ0KYWxnb3JpdGhtLg0KLSBLRU1UTFMgc2F2ZXMgMS0yS0Igb2YgZGF0YSBjb21wYXJlZCB0byBQ
USBTaWduYXR1cmVzIChhc3N1bWluZyBEaWxpdGhpdW0sDQpGYWxjb24pIHdoaWNoIGlzIGFuIGlt
cHJvdmVtZW50LCBidXQgYmFzZWQgb24gZXhwZXJpbWVudHMgc28gZmFyLCBpdCB3b3VsZA0Kbm90
IGhhdmUgc2lnbmlmaWNhbnQgaW1wYWN0IG9uIGEgcmVhbC13b3JsZCBoYW5kc2hha2UuIEl0IG1h
eSBpbXBhY3QNCmNvbnN0cmFpbmVkIG1lZGl1bXMgd2l0aCBoaWdoIGxvc3MgcHJvYmFiaWxpdHks
IGJ1dCBpdCB3b24ndCBiZSBub3RpY2VhYmxlDQpmb3IgdGhlIHJlc3Qgb2YgdGhlIGhhbmRzaGFr
ZXMuDQotIFRoZSBQUSBLRU0gbWF5IGhhdmUgYmV0dGVyIHNpZGUtY2hhbm5lbCByZXNpc3RhbmNl
IHRoYW4gdGhlIFBRIHNpZ25hdHVyZQ0Kc2NoZW1lLg0KLSBLRU1UTFMgbWF5IGJlIHNsaWdodGx5
IGZhc3RlciBpZiB3ZSBhcmUgYXNzdW1pbmcgRmFsY29uLCBidXQgbm90IGZvcg0KRGlsaXRoaXVt
Lg0KDQpSZ3MsDQpQYW5vcw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogU3Bh
c20gPHNwYXNtLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOnNwYXNtLWJvdW5jZXNAaWV0Zi5vcmc+
PiBPbiBCZWhhbGYgT2YgTWlrZSBPdW5zd29ydGgNClNlbnQ6IFRodXJzZGF5LCBKYW51YXJ5IDI4
LCAyMDIxIDQ6NTkgUE0NClRvOiBMQU1QUyA8c3Bhc21AaWV0Zi5vcmc8bWFpbHRvOnNwYXNtQGll
dGYub3JnPj4NCkNjOiBEb3VnbGFzIFN0ZWJpbGEgPGRvdWdsYXNAc3RlYmlsYS5jYTxtYWlsdG86
ZG91Z2xhc0BzdGViaWxhLmNhPj4NClN1YmplY3Q6IFtsYW1wc10gS0VNLW9ubHkgY2VydGlmaWNh
dGVzIChLRU1UTFMpDQoNClRMO0RSOiBObyBpbW1lZGlhdGUgYWN0aW9uLCBidXQgc29tZXRoaW5n
IHRvIGtlZXAgYW4gZXllIG9uLg0KDQpJIGRpZCBub3Qgc3BlbmQgdGltZSBvbiB0aGlzIGR1cmlu
ZyBteSB0YWxrIHRvZGF5IGJlY2F1c2UgSSBkaWRuJ3Qgd2FudCB0bw0KZGlzdHJhY3QgZnJvbSB0
aGUgQ29tcG9zaXRlIHRvcGljLCBidXQgSSB3YW50IHRvIGRyYXcgYXR0ZW50aW9uIHRvIG15ICJC
b251cw0KdG9waWMiIHNsaWRlIGFib3V0IEtFTSBjZXJ0aWZpY2F0ZXMuIEkgZG9uJ3Qga25vdyBp
ZiBhbnlvbmUgZWxzZSBpcw0KZm9sbG93aW5nIHRoZSBLRU1UTFMgZGlzY3Vzc2lvbnMgKHJlZmVy
ZW5jZXMgYmVsb3cpLCBidXQgdGhhdCB3b3VsZCByZXF1aXJlDQpQS0lzIHRvIGlzc3VlIGxhcmdl
IGFtb3VudHMgb2YgS2V5IEVzdGFibGlzaG1lbnQgTWVjaGFuaXNtIChLRU07IGFrYQ0Ka2V5VXNh
Z2U6IGtleUVuY2lwaGVybWVudCkgVExTIGNlcnRpZmljYXRlcy4gSWYgVExTIFdHIGRlY2lkZXMg
dG8gYWRvcHQgdGhlDQpLRU1UTFMgZHJhZnQsIHRoZW4gTEFNUFMgcHJvYmFibHkgbmVlZHMgdG8g
dGFrZSBhIGxvb2sgYXQgUEtJWCB0byBtYWtlIHN1cmUNCndlIGNhbiBoYW5kbGUgZW5yb2xsbWVu
dCwgdXBkYXRlLCByZXZvY2F0aW9uIGZvciBjbGllbnRzIHRoYXQgZG9uJ3QgaGF2ZQ0Kc2lnbmlu
ZyBrZXlzLiBJIHRvb2sgYSAodmVyeSkgcXVpY2sgcGFzcyBvdmVyIENNUCwgTGlnaHR3ZWlnaHQg
Q01QLCBFU1QNCihib3RoIHNpbXBsZSBhbmQgZnVsbC1DTUMpIGFuZCBhdHRlbXB0ZWQgdG8gc3Vt
bWFyaXplIGZpbmRpbmdzIGluIG15ICJib251cw0KdG9waWNzIiBzbGlkZXMuDQoNCjE6IE15IHNs
aWRlcyBmcm9tIHRvZGF5Og0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nL2lu
dGVyaW0tMjAyMS1sYW1wcy0wMS9tYXRlcmlhbHMvc2xpZGVzLQ0KaW50ZXJpbS0yMDIxLWxhbXBz
LTAxLXNlc3NhLXBvc2l0aW9uLXByZXNlbnRhdGlvbi1ieS1taWtlLW91bnN3b3J0aC0wMC5wZGYN
CjI6ICJQb3N0LXF1YW50dW0gVExTIHdpdGhvdXQgaGFuZHNoYWtlIHNpZ25hdHVyZXMiLCBTY2h3
YWJlLCBTdGViaWxhLA0KV2lnZ2VycywgaHR0cHM6Ly9lcHJpbnQuaWFjci5vcmcvMjAyMC81MzQN
CjM6ICJLRU1UTFM6IFBvc3QtcXVhbnR1bSBUTFMgd2l0aG91dCBzaWduYXR1cmVzIiwgQ2VsaSwg
V2lnZ2VycywNCmh0dHBzOi8vYmxvZy5jbG91ZGZsYXJlLmNvbS9rZW10bHMtcG9zdC1xdWFudHVt
LXRscy13aXRob3V0LXNpZ25hdHVyZXMvDQoNCi0tLQ0KTWlrZSBPdW5zd29ydGgNClNvZnR3YXJl
IFNlY3VyaXR5IEFyY2hpdGVjdCwgRW50cnVzdA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KU3Bhc20gbWFpbGluZyBsaXN0DQpTcGFzbUBpZXRmLm9y
ZzxtYWlsdG86U3Bhc21AaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3NwYXNtDQoNCg==

--_000_04AA436333A444009A50A30D24CA152Disaracom_
Content-Type: text/html; charset="utf-8"
Content-ID: <581E76F44B0A794EB32D28C23D4F16EE@isara.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCWZvbnQtc2l6
ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBz
cGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsN
Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcy
LjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1DQSIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBs
ZSIgc3R5bGU9IndvcmQtd3JhcDpicmVhay13b3JkIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9u
MSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaGlsZSBhbiBhZG9wdGVkIEtFTVRMUyB3b3VsZCBy
ZXN1bHQgaW4gYSBwcm9saWZlcmF0aW9uIG9mIEtFTSBjZXJ0cywgTklTVCB3aWxsIGJlIHNwZWNp
ZnlpbmcgaG93IHRvIGNvbnZlcnQgS0VNcyB0byBwdWJsaWMga2V5IGVuY3J5cHRpb24gc2NoZW1l
cyAoPGEgaHJlZj0iaHR0cHM6Ly9jc3JjLm5pc3QuZ292L3Byb2plY3RzL3Bvc3QtcXVhbnR1bS1j
cnlwdG9ncmFwaHkvZmFxcyI+aHR0cHM6Ly9jc3JjLm5pc3QuZ292L3Byb2plY3RzL3Bvc3QtcXVh
bnR1bS1jcnlwdG9ncmFwaHkvZmFxczwvYT4NCiBvbGQgUTEzKSwgc28gS0VNcyB3b3VsZCBhbHNv
IGJlIG5lZWRlZCBpbiBFRSBjZXJ0cyBpZiB0aGV5IHdlcmUgdG8gYmUgdXNlZCBmb3Iga2V5IHRy
YW5zcG9ydCBpbiBDTVMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRhbmllbCBWYW4gR2Vlc3Q8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MzYuMHB0Ij5PbiAyMDIxLTAxLTI4LCAxMDo1MyBQTSwgJnF1b3Q7U3Bhc20gb24gYmVoYWxmIG9m
IFBhbm9zIEthbXBhbmFraXMgKHBrYW1wYW5hKSZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnNw
YXNtLWJvdW5jZXNAaWV0Zi5vcmciPnNwYXNtLWJvdW5jZXNAaWV0Zi5vcmc8L2E+IG9uIGJlaGFs
ZiBvZg0KPGEgaHJlZj0ibWFpbHRvOnBrYW1wYW5hPTQwY2lzY28uY29tQGRtYXJjLmlldGYub3Jn
Ij5wa2FtcGFuYT00MGNpc2NvLmNvbUBkbWFyYy5pZXRmLm9yZzwvYT4mZ3Q7IHdyb3RlOjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPkhv
cGVmdWxseSB3ZSB3aWxsIGdldCB0byBkaXNjdXNzIEtFTVRMUyBpZiB0aGUgQ2xvdWRmbGFyZSBm
b2xrcyBicmluZyB0aGlzPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij50byB0aGUgVExTIFdHLiA8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
YXJnaW4tbGVmdDozNi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+S0VNLVRMUyBp
cyBhIG5lYXQgaWRlYSwgYnV0IG5vdCBhcyBlYXN5IGFzIHN3YXBwaW5nIGEgU2lnIHdpdGggYSBL
RU0gaW4gdGhlPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5sZWFmIGNlcnQuIElmIGl0IHdhcyBzd2Fw
cGluZyAoRUMpRFNBIHdpdGggKEVDKURIIGFzIGEgS0VNLCB0aGVuIGl0IHdvdWxkIGJlPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luLWxlZnQ6MzYuMHB0Ij50cml2aWFsIGFzIHByb3Bvc2VkIGluPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYu
MHB0Ij48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi10bHMt
c2VtaXN0YXRpYy1kaCI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtdGxz
LXNlbWlzdGF0aWMtZGg8L2E+LiBCdXQgaXQgZG9lc24ndDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+
d29yayBsaWtlIHRoYXQgd2l0aCBQUSBLRU1zLiA8bzpwPg0KPC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5LRU1UTFMgaW50cm9kdWNlcyBkcmFzdGljIGNoYW5n
ZXMgdG8gdGhlIGhhbmRzaGFrZSBsaWtlIGltcGxpY2l0IGFuZDxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBw
dCI+ZXhwbGljaXQgdHJ1c3QgYW5kIHRoZSBvcHRpb24gdG8gc2VuZCBlbmNyeXB0ZWQgZGF0YSB0
byB0aGUgc2VydmVyIHRoYXQgaGFzPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5ub3QgYmVlbiBmdWxs
eSBhdXRoZW50aWNhdGVkIHlldC4gVGhlc2UgY29uY2VwdHMgaGF2ZSBub3QgZXhpc3RlZCBpbiBU
TFMgc288bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPmZhci4gV2UgYXJlIHRhbGtpbmcgYWJvdXQgVExT
IDEuNCBoZXJlIGFuZCBhIG5ldyBzZWN1cml0eSBwcm9vZi4gSXQgaXMgbm88bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVm
dDozNi4wcHQiPmxvbmdlciBUTFMgMS4zIHdpdGggbWlub3IgY2hhbmdlcy4gTm90aGluZyB3cm9u
ZyB3aXRoIHRoYXQsIGJ1dCBpdCBpcyBub3QgYTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+dHJpdmlh
bCBjaGFuZ2UgYXQgYWxsLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6MzYuMHB0Ij5UaGUgYWR2YW50YWdlcyBvZiBLRU1UTFMgYXJlIDxvOnA+DQo8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MzYuMHB0Ij4tIEluIEtFTVRMUyB0aGUgS0VNIGlzIG9ubHkgdXNlZCBhdCB0aGUgbGVhZi4gVGhl
IHJlc3Qgb2YgdGhlIGNlcnQgY2hhaW48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPnN0aWxsIHVzZXMg
U2lnbmF0dXJlcy4gVGh1cywgdGhlIHNpZ25lciBkb2VzIG5vdCBuZWVkIHRvIHN1cHBvcnQgYSBQ
UTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+c2lnbmF0dXJlIGFsZ29yaXRobSBidXQgdGhlIHZlcmlm
aWVyIHN0aWxsIG5lZWRzIHRvIHN1cHBvcnQgYSBQUSBzaWduYXR1cmU8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoz
Ni4wcHQiPmFsZ29yaXRobS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPi0gS0VNVExTIHNhdmVzIDEt
MktCIG9mIGRhdGEgY29tcGFyZWQgdG8gUFEgU2lnbmF0dXJlcyAoYXNzdW1pbmcgRGlsaXRoaXVt
LDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+RmFsY29uKSB3aGljaCBpcyBhbiBpbXByb3ZlbWVudCwg
YnV0IGJhc2VkIG9uIGV4cGVyaW1lbnRzIHNvIGZhciwgaXQgd291bGQ8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoz
Ni4wcHQiPm5vdCBoYXZlIHNpZ25pZmljYW50IGltcGFjdCBvbiBhIHJlYWwtd29ybGQgaGFuZHNo
YWtlLiBJdCBtYXkgaW1wYWN0PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5jb25zdHJhaW5lZCBtZWRp
dW1zIHdpdGggaGlnaCBsb3NzIHByb2JhYmlsaXR5LCBidXQgaXQgd29uJ3QgYmUgbm90aWNlYWJs
ZTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+Zm9yIHRoZSByZXN0IG9mIHRoZSBoYW5kc2hha2VzLiA8
bzpwPg0KPC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+LSBUaGUgUFEgS0VNIG1heSBoYXZlIGJldHRlciBzaWRl
LWNoYW5uZWwgcmVzaXN0YW5jZSB0aGFuIHRoZSBQUSBzaWduYXR1cmU8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoz
Ni4wcHQiPnNjaGVtZS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPi0gS0VNVExTIG1heSBiZSBzbGln
aHRseSBmYXN0ZXIgaWYgd2UgYXJlIGFzc3VtaW5nIEZhbGNvbiwgYnV0IG5vdCBmb3I8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDozNi4wcHQiPkRpbGl0aGl1bS4gPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDozNi4wcHQiPlJncyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPlBhbm9zPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPi0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5Gcm9tOiBTcGFzbSAmbHQ7
PGEgaHJlZj0ibWFpbHRvOnNwYXNtLWJvdW5jZXNAaWV0Zi5vcmciPnNwYXNtLWJvdW5jZXNAaWV0
Zi5vcmc8L2E+Jmd0OyBPbiBCZWhhbGYgT2YgTWlrZSBPdW5zd29ydGg8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoz
Ni4wcHQiPlNlbnQ6IFRodXJzZGF5LCBKYW51YXJ5IDI4LCAyMDIxIDQ6NTkgUE08bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
bGVmdDozNi4wcHQiPlRvOiBMQU1QUyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnNwYXNtQGlldGYub3Jn
Ij5zcGFzbUBpZXRmLm9yZzwvYT4mZ3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5DYzogRG91Z2xh
cyBTdGViaWxhICZsdDs8YSBocmVmPSJtYWlsdG86ZG91Z2xhc0BzdGViaWxhLmNhIj5kb3VnbGFz
QHN0ZWJpbGEuY2E8L2E+Jmd0OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+U3ViamVjdDogW2xhbXBz
XSBLRU0tb25seSBjZXJ0aWZpY2F0ZXMgKEtFTVRMUyk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+VEw7RFI6IE5vIGltbWVkaWF0ZSBhY3Rpb24sIGJ1
dCBzb21ldGhpbmcgdG8ga2VlcCBhbiBleWUgb24uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPkkgZGlkIG5vdCBzcGVuZCB0aW1lIG9uIHRoaXMgZHVy
aW5nIG15IHRhbGsgdG9kYXkgYmVjYXVzZSBJIGRpZG4ndCB3YW50IHRvPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MzYuMHB0Ij5kaXN0cmFjdCBmcm9tIHRoZSBDb21wb3NpdGUgdG9waWMsIGJ1dCBJIHdhbnQgdG8g
ZHJhdyBhdHRlbnRpb24gdG8gbXkgJnF1b3Q7Qm9udXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPnRv
cGljJnF1b3Q7IHNsaWRlIGFib3V0IEtFTSBjZXJ0aWZpY2F0ZXMuIEkgZG9uJ3Qga25vdyBpZiBh
bnlvbmUgZWxzZSBpczxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+Zm9sbG93aW5nIHRoZSBLRU1UTFMg
ZGlzY3Vzc2lvbnMgKHJlZmVyZW5jZXMgYmVsb3cpLCBidXQgdGhhdCB3b3VsZCByZXF1aXJlPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bWFyZ2luLWxlZnQ6MzYuMHB0Ij5QS0lzIHRvIGlzc3VlIGxhcmdlIGFtb3VudHMgb2YgS2V5IEVz
dGFibGlzaG1lbnQgTWVjaGFuaXNtIChLRU07IGFrYTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+a2V5
VXNhZ2U6IGtleUVuY2lwaGVybWVudCkgVExTIGNlcnRpZmljYXRlcy4gSWYgVExTIFdHIGRlY2lk
ZXMgdG8gYWRvcHQgdGhlPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5LRU1UTFMgZHJhZnQsIHRoZW4g
TEFNUFMgcHJvYmFibHkgbmVlZHMgdG8gdGFrZSBhIGxvb2sgYXQgUEtJWCB0byBtYWtlIHN1cmU8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDozNi4wcHQiPndlIGNhbiBoYW5kbGUgZW5yb2xsbWVudCwgdXBkYXRlLCBy
ZXZvY2F0aW9uIGZvciBjbGllbnRzIHRoYXQgZG9uJ3QgaGF2ZTxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBw
dCI+c2lnbmluZyBrZXlzLiBJIHRvb2sgYSAodmVyeSkgcXVpY2sgcGFzcyBvdmVyIENNUCwgTGln
aHR3ZWlnaHQgQ01QLCBFU1Q8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPihib3RoIHNpbXBsZSBhbmQg
ZnVsbC1DTUMpIGFuZCBhdHRlbXB0ZWQgdG8gc3VtbWFyaXplIGZpbmRpbmdzIGluIG15ICZxdW90
O2JvbnVzPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij50b3BpY3MmcXVvdDsgc2xpZGVzLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1sZWZ0OjM2LjBwdCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij4xOiBNeSBzbGlkZXMg
ZnJvbSB0b2RheTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxhIGhyZWY9Imh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvbWVldGluZy9pbnRlcmltLTIwMjEtbGFtcHMtMDEvbWF0ZXJpYWxzL3Ns
aWRlcy0iPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvbWVldGluZy9pbnRlcmltLTIwMjEt
bGFtcHMtMDEvbWF0ZXJpYWxzL3NsaWRlcy08L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5pbnRl
cmltLTIwMjEtbGFtcHMtMDEtc2Vzc2EtcG9zaXRpb24tcHJlc2VudGF0aW9uLWJ5LW1pa2Utb3Vu
c3dvcnRoLTAwLnBkZjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+MjogJnF1b3Q7UG9zdC1xdWFudHVt
IFRMUyB3aXRob3V0IGhhbmRzaGFrZSBzaWduYXR1cmVzJnF1b3Q7LCBTY2h3YWJlLCBTdGViaWxh
LDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+V2lnZ2VycywgPGEgaHJlZj0iaHR0cHM6Ly9lcHJpbnQu
aWFjci5vcmcvMjAyMC81MzQiPg0KaHR0cHM6Ly9lcHJpbnQuaWFjci5vcmcvMjAyMC81MzQ8L2E+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij4zOiAmcXVvdDtLRU1UTFM6IFBvc3QtcXVhbnR1bSBUTFMg
d2l0aG91dCBzaWduYXR1cmVzJnF1b3Q7LCBDZWxpLCBXaWdnZXJzLDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2
LjBwdCI+PGEgaHJlZj0iaHR0cHM6Ly9ibG9nLmNsb3VkZmxhcmUuY29tL2tlbXRscy1wb3N0LXF1
YW50dW0tdGxzLXdpdGhvdXQtc2lnbmF0dXJlcy8iPmh0dHBzOi8vYmxvZy5jbG91ZGZsYXJlLmNv
bS9rZW10bHMtcG9zdC1xdWFudHVtLXRscy13aXRob3V0LXNpZ25hdHVyZXMvPC9hPjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1sZWZ0OjM2LjBwdCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij4tLS08bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
bGVmdDozNi4wcHQiPk1pa2UgT3Vuc3dvcnRoPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5Tb2Z0d2Fy
ZSBTZWN1cml0eSBBcmNoaXRlY3QsIEVudHJ1c3Q8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX188bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPlNwYXNtIG1haWxpbmcgbGlzdDxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1sZWZ0OjM2LjBwdCI+PGEgaHJlZj0ibWFpbHRvOlNwYXNtQGlldGYub3JnIj5TcGFz
bUBpZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxhIGhyZWY9Imh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc3Bhc20iPmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vc3Bhc208L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_04AA436333A444009A50A30D24CA152Disaracom_--


From nobody Fri Jan 29 17:12:36 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5763A1448 for <spasm@ietfa.amsl.com>; Fri, 29 Jan 2021 17:12:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DwFRywiXP-CR for <spasm@ietfa.amsl.com>; Fri, 29 Jan 2021 17:12:30 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B019E3A143E for <spasm@ietf.org>; Fri, 29 Jan 2021 17:12:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 1FA0C300B90 for <spasm@ietf.org>; Fri, 29 Jan 2021 20:12:28 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id p9wxB6hAAzds for <spasm@ietf.org>; Fri, 29 Jan 2021 20:12:26 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 87E5E300B03 for <spasm@ietf.org>; Fri, 29 Jan 2021 20:12:26 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_955D21E4-7BD8-4AA7-8081-FAF4FC19F08C"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Fri, 29 Jan 2021 20:12:28 -0500
References: <51C0C78E-CD70-4476-B6B1-FDC78C272F18@vigilsec.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <51C0C78E-CD70-4476-B6B1-FDC78C272F18@vigilsec.com>
Message-Id: <9C910CC4-65F1-472C-A152-F3D6E81946F5@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/s6JwDnPFIKImIUN8l5AAQ7-8JQk>
Subject: Re: [lamps] LAMPS WG Virtual Interim on 28 January 2021
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2021 01:12:34 -0000

--Apple-Mail=_955D21E4-7BD8-4AA7-8081-FAF4FC19F08C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

The recording of the meeting has been posted to YouTube: =
https://youtu.be/WH-q9FYLWh0 <https://youtu.be/WH-q9FYLWh0>

Russ

- - - - - - - - -

LAMPS WG Virtual Interim on 28 January 2021

Since the LAMPS WG needs to re-charter to take on
draft-dkg-lamps-e2e-mail-guidance, this seems like a
good time to ask what other topics the group might
want to tackle.  Some have expressed interest in topics
related to the transition to PQ cryptographic algorithms.
This virtual interim on that will help determine what, if
anything, should be included in the LAMPS WG re-charter.


AGENDA

0)  Minute Taker, Jabber Scribe, Bluesheets

1)  Agenda Bash

2)  Position Presentations=20
   a)  Russ Housley
   b)  Max Pala
   c)  Mike Ounsworth
   d)  Antonio Vaira
   e) Tadahiko Ito

3)  Open Discussion

4)  Wrap Up


=3D =3D =3D =3D =3D =3D =3D =3D =3D

WebEx:  =
https://ietf.webex.com/ietf/j.php?MTID=3Dmb6639fe2c67ce9a639fcb8701fa85e3c=

Notes:  https://codimd.ietf.org/notes-ietf-interim-2021-lamps-01-lamps#
Slides: =
https://datatracker.ietf.org/meeting/interim-2021-lamps-01/session/lamps
Jabber: xmpp:lamps@jabber.ietf.org



--Apple-Mail=_955D21E4-7BD8-4AA7-8081-FAF4FC19F08C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><div =
class=3D"">The recording of the meeting has been posted to =
YouTube:&nbsp;<a href=3D"https://youtu.be/WH-q9FYLWh0" =
class=3D"">https://youtu.be/WH-q9FYLWh0</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">Russ</div><div><br class=3D""><div =
class=3D"">- - - - - - - - -</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">LAMPS WG Virtual =
Interim on 28 January 2021<br class=3D""><br class=3D"">Since the LAMPS =
WG needs to re-charter to take on<br =
class=3D"">draft-dkg-lamps-e2e-mail-guidance, this seems like a<br =
class=3D"">good time to ask what other topics the group might<br =
class=3D"">want to tackle. &nbsp;Some have expressed interest in =
topics<br class=3D"">related to the transition to PQ cryptographic =
algorithms.<br class=3D"">This virtual interim on that will help =
determine what, if<br class=3D"">anything, should be included in the =
LAMPS WG re-charter.<br class=3D""><br class=3D""><br class=3D"">AGENDA<br=
 class=3D""><br class=3D"">0) &nbsp;Minute Taker, Jabber Scribe, =
Bluesheets<br class=3D""><br class=3D"">1) &nbsp;Agenda Bash<br =
class=3D""><br class=3D"">2) &nbsp;Position Presentations <br class=3D""> =
&nbsp;&nbsp;&nbsp;a) &nbsp;Russ Housley<br class=3D""> =
&nbsp;&nbsp;&nbsp;b) &nbsp;Max Pala<br class=3D""> &nbsp;&nbsp;&nbsp;c) =
&nbsp;Mike Ounsworth<br class=3D""> &nbsp;&nbsp;&nbsp;d) &nbsp;Antonio =
Vaira<br class=3D""></div></div>&nbsp; &nbsp;e) Tadahiko Ito<div =
class=3D""><div class=3D""><br class=3D"">3) &nbsp;Open Discussion<br =
class=3D""><br class=3D"">4) &nbsp;Wrap Up<br class=3D""><br =
class=3D""><br class=3D"">=3D =3D =3D =3D =3D =3D =3D =3D =3D<br =
class=3D""><br class=3D"">WebEx: &nbsp;<a =
href=3D"https://ietf.webex.com/ietf/j.php?MTID=3Dmb6639fe2c67ce9a639fcb870=
1fa85e3c" =
class=3D"">https://ietf.webex.com/ietf/j.php?MTID=3Dmb6639fe2c67ce9a639fcb=
8701fa85e3c</a><br class=3D"">Notes: &nbsp;<a =
href=3D"https://codimd.ietf.org/notes-ietf-interim-2021-lamps-01-lamps#" =
class=3D"">https://codimd.ietf.org/notes-ietf-interim-2021-lamps-01-lamps#=
</a><br class=3D"">Slides: <a =
href=3D"https://datatracker.ietf.org/meeting/interim-2021-lamps-01/session=
/lamps" =
class=3D"">https://datatracker.ietf.org/meeting/interim-2021-lamps-01/sess=
ion/lamps</a><br class=3D"">Jabber: <a href=3D"xmpp:lamps@jabber.ietf.org"=
 class=3D"">xmpp:lamps@jabber.ietf.org</a><br class=3D""><br =
class=3D""></div></div></div><br class=3D""></body></html>=

--Apple-Mail=_955D21E4-7BD8-4AA7-8081-FAF4FC19F08C--


From nobody Sat Jan 30 13:14:05 2021
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA8C3A1163 for <spasm@ietfa.amsl.com>; Sat, 30 Jan 2021 13:14:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tBInG_L59lr for <spasm@ietfa.amsl.com>; Sat, 30 Jan 2021 13:13:59 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAAE83A1164 for <spasm@ietf.org>; Sat, 30 Jan 2021 13:13:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 55F22300B89 for <spasm@ietf.org>; Sat, 30 Jan 2021 16:13:56 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id MJGucp40z58C for <spasm@ietf.org>; Sat, 30 Jan 2021 16:13:55 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id ED025300A4B for <spasm@ietf.org>; Sat, 30 Jan 2021 16:13:54 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Sat, 30 Jan 2021 16:13:56 -0500
References: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com>
Message-Id: <E64102E4-AA88-4B87-814A-6C79F6655102@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/REVYUwBci717m7zVfbSIYpv7VKA>
Subject: Re: [lamps] Proposed re-charter text for hybrid and dual crypto modes
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2021 21:14:03 -0000

Building on the text proposed by Mike, I want to address a point raised =
by Max and a point raised by Sean.

First, Max observed that PQC algorithms will be used in both the one =
certificate and the two certificate models.  So, I propose charter text =
that has a place for each of them.

Second, Sean observed that the charter will need some background text to =
explain what we are doing to the IESG.  So, I propose some charter text =
for additional context.

Third, the charter is structured as a list of deliverables for the LAMPS =
WG.  So, I structured the proposed charter text as a new numbered item =
"X".

~~~

X. Recent progress in the development of quantum computers pose a threat
to widely deployed public key algorithms.  As a result, there is a need
to prepare for a day when cryptosystems such as RSA, Diffie-Hellman,
ECDSA, ECDH, and EdDSA cannot be depended upon.  As a result, there are
efforts to develop standards for post-quantum cryptosystem (PQC)
algorithms that that will be secure if large-scale quantum computers
are ever developed.

a. Specify the use of PQC public key algorithms with the PKIX
certificates and the Cryptographic Message Syntax (CMS).

b. Develop specifications to facilitate a lengthy transition from
today's public key algorithms to PQC public key algorithms.  Unlike
previous algorithm transitions, time will be needed before there is
full confidence in the PQC public key algorithms.  Therefore,
transition mechanisms that combine traditional algorithms with PQC
algorithms will be needed for "hybrid key establishment" and "dual
signatures".  NIST defines "hybrid key establishment" as any key
establishment scheme that is a combination of two or more components
that are themselves cryptographic key-establishment schemes.  NIST
defines "dual signatures" as any signature scheme that consists of
two or more signatures on a common message.  The specifications
developed will enable PKIX and S/MIME protocols to support hybrid key
establishment and dual signature mechanisms.

~~~

Review and comments welcome.

Russ


> On Jan 28, 2021, at 2:27 PM, Mike Ounsworth =
<Mike.Ounsworth=3D40entrust.com@dmarc.ietf.org> wrote:
>=20
> Proposed charter text:
>=20
> Post-quantum cryptography (PQC) will require a transition period in =
some ways similar to previous crypto migrations, but unique in that =
timelines require deployment of PQC before cryptographers have full =
confidence in the replacement algorithms. NIST has called for transition =
mechanisms that "layer" traditional and PQ crypto together, referred to =
as "hybrid key establishment" and "dual signatures". The LAMPS working =
group will update documents produced by the PKIX and S/MIME WG to =
support hybrid key establishment, encryption, and dual signature =
mechanisms.
>=20
> ---
> Mike Ounsworth
> Software Security Architect, Entrust


From nobody Sat Jan 30 14:39:04 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5EC53A11FA for <spasm@ietfa.amsl.com>; Sat, 30 Jan 2021 14:39:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAtQ0hf4ar5k for <spasm@ietfa.amsl.com>; Sat, 30 Jan 2021 14:39:00 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64BBD3A11F9 for <spasm@ietf.org>; Sat, 30 Jan 2021 14:38:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C1C4A389A0; Sat, 30 Jan 2021 17:41:35 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wPDm0iT6rOy8; Sat, 30 Jan 2021 17:41:31 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D385B3899E; Sat, 30 Jan 2021 17:41:31 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D982C5E5; Sat, 30 Jan 2021 17:38:53 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Russ Housley <housley@vigilsec.com>, LAMPS <spasm@ietf.org>
In-Reply-To: <E64102E4-AA88-4B87-814A-6C79F6655102@vigilsec.com>
References: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com> <E64102E4-AA88-4B87-814A-6C79F6655102@vigilsec.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Sat, 30 Jan 2021 17:38:53 -0500
Message-ID: <6498.1612046333@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/U1W4HY0Iaa6b-lfBCsvEjHsZmUM>
Subject: Re: [lamps] Proposed re-charter text for hybrid and dual crypto modes
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2021 22:39:03 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Russ Housley <housley@vigilsec.com> wrote:
    > full confidence in the PQC public key algorithms.  Therefore,
    > transition mechanisms that combine traditional algorithms with PQC
    > algorithms will be needed for "hybrid key establishment" and "dual
    > signatures".

    > NIST defines "hybrid key establishment" as any key
    > establishment scheme that is a combination of two or more components
    > that are themselves cryptographic key-establishment schemes.

To be clear for me, such a system would get a unique algorithm OID,
and would count as a single signature outside of the crypto function.

    > NIST
    > defines "dual signatures" as any signature scheme that consists of two
    > or more signatures on a common message.  The specifications developed
    > will enable PKIX and S/MIME protocols to support hybrid key
    > establishment and dual signature mechanisms.

Such as system would be visible as having two algorithmOIDs, and this would
be visible outside of the crypt function.  The length discussion about
matching the two identities, etc. deals with this side of things.

My understanding is that we might have situations where we have dual
signatures, and the second signature might be a hybrid signature.

RFC5280 only provides for one algorithmIdentifier (signatureAlgorithm) at t=
he
top-level sequence, which is not contained under the signature.
We had some document a few years ago that dealt with coordinating this with
the section 4.1.2.3 Signature which *is* the signature. (I think Russ wrote=
 that)

I know that some of the proposals (maybe all) put the second algorithm into
various extensions, and that is really the only way to do the dual-signatur=
es
in a backwards compatible way.

I note that RFC5280 is only at Proposed Standard.
It was suggested it was more mature, but I can't find any evidence of that:
not in the DT nor on the rfc-editor page.

I believe that write a few "Updates" (Amends) RFC5280 documents is
appropriate, but I think that given that this is going to be a long
transition, that I think the charter should include text that would allow
RFC5280bis to be produced.  That might not be a near-term priority, but I
think that it needs to get done for a number of technical and marketing rea=
sons.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmAV3/0ACgkQgItw+93Q
3WXI3QgAmVKqFB90AstyYKuTrnCNefMe51k+pMWzc7znwJ6+1TkvAA3eAwnDxzeK
MccgCQ9ggnwOg6Obd0eVDzp5hcRVjWbMs47BYPKnTI+pNiTnT6LGx2CFwHDh/wMN
ZptUpxoF6pEHtVi/KyrxTJ+piwK17md3KMN8X23F9rTp5qimIO979z0aYmePQ+sI
0ci8NkW9IFicKeA+N5v5AHzSX13spuYeuJFrqb5LQ9GNSkFA8YnKNUEvr32X7tzk
+Di+U9DC3GU//zOJ5WkV/LGmfBw1M+zYpzdQXm+XLBeOvVYtdvxzyAKIoaHOFbj4
yhokZ44Co1zN+v/kp+/fsPACaaxSiQ==
=Z4XJ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Jan 31 08:20:16 2021
Return-Path: <m.jenkins.364706@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73A503A10B3 for <spasm@ietfa.amsl.com>; Sun, 31 Jan 2021 08:20:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZX-Ole8LTek5 for <spasm@ietfa.amsl.com>; Sun, 31 Jan 2021 08:20:12 -0800 (PST)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19A903A10B0 for <spasm@ietf.org>; Sun, 31 Jan 2021 08:20:11 -0800 (PST)
Received: by mail-io1-xd2e.google.com with SMTP id s24so3163415iob.6 for <spasm@ietf.org>; Sun, 31 Jan 2021 08:20:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XmjzXnoKLL1S7vQu8bd/RK4oXQKb/go5/nbawa3SWew=; b=EBqE6onveFgNKZI8wRhKQ0dtOe2mIqUd7lLcFr1ZfUF19lWOgvvIpI4SCIu1sp4ezw jTb3Y64W8Zw16p7GKJKl0wIxEoM5zAXJERVMQIgmAWMZ16+K+QCJfbPlvyayM71ZBf/A DA/JI4I9PUJ26BmqAeY+gAeYA6RidA8qcrkJK38q9I7Wdr9okOTDDUqYZfszNPRM2eoM oWfhInJBak5uuiNhVR4zq/y7+dO340JWfdneqG6OTYrdGfieeWz9LrgNOxpHML85+UlT 9YOZQcigxNOWLwU51YGGqFqq8HtQUAHvJGPEl3YMAgeJIShDL3/Dc0rw2FuYdOUvVhnW WlEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XmjzXnoKLL1S7vQu8bd/RK4oXQKb/go5/nbawa3SWew=; b=q1ARSAZ0r1tOU6fQujxBJf1WWUXYHCLZx01EjJ/W3xJseR1OI7O5W2KKUcH0O5GvSS r3MWF/p4uxnvnP0lTu9n+7vED13bu5/OWyfkIPfZjWR2mfgFi7NCcHrF/JhxmAS8Bd08 xwYciQ0a3ihBMltb90GfU9FAU/0Y9dvKfKOkc5AcHaICxW/SVqvbnRUWP4P9bFXmC0O4 tyoOkW5elSR+Ia3x3Zy+hrXmneTZ3FzUQjS9ekzjU71j9YAxK15DNoZoHJqAYf9W7pb1 hUfo/Gvv6kS88WgLJ1YZAUyWt7m0Tkl9pj98+7B6Yi228hJgrQPFEhdL1MXgIyy7sXdx Ed5Q==
X-Gm-Message-State: AOAM531V6Za3Miq6hz3iBLgovsPhIwiy18WI+cZPBq6HsdoAczpF8JdK a6wOjNdRF5x/NEMY9XFHdfOSAFll22dQte3i+R4ksj2U
X-Google-Smtp-Source: ABdhPJxRMNbaSF61DCx3cEM+c2ky6q51TS4rLrqTeRj6LEwvyRiK0uncvhcaQ8MnaSCCEnsXiF3CWBLSgembnUbUuB0=
X-Received: by 2002:a02:cd25:: with SMTP id h5mr5008519jaq.31.1612110011138; Sun, 31 Jan 2021 08:20:11 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com> <E64102E4-AA88-4B87-814A-6C79F6655102@vigilsec.com>
In-Reply-To: <E64102E4-AA88-4B87-814A-6C79F6655102@vigilsec.com>
From: Michael Jenkins <m.jenkins.364706@gmail.com>
Date: Sun, 31 Jan 2021 11:20:00 -0500
Message-ID: <CAC2=hneq2Lx5Ke1fpEjSgUPvP58MBEOD9LiB6rnNRQnirqAf9A@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: LAMPS <spasm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008d839d05ba349c96"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/g7EYb_jBR7-4OoyMWiLm2H8mmyw>
Subject: Re: [lamps] Proposed re-charter text for hybrid and dual crypto modes
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jan 2021 16:20:15 -0000

--0000000000008d839d05ba349c96
Content-Type: text/plain; charset="UTF-8"

Not that I object to any of the work being proposed, but we seem to have
put paid to the notion of "limited". This is looking like PKIXme.

On Sat, Jan 30, 2021 at 4:14 PM Russ Housley <housley@vigilsec.com> wrote:

> Building on the text proposed by Mike, I want to address a point raised by
> Max and a point raised by Sean.
>
> First, Max observed that PQC algorithms will be used in both the one
> certificate and the two certificate models.  So, I propose charter text
> that has a place for each of them.
>
> Second, Sean observed that the charter will need some background text to
> explain what we are doing to the IESG.  So, I propose some charter text for
> additional context.
>
> Third, the charter is structured as a list of deliverables for the LAMPS
> WG.  So, I structured the proposed charter text as a new numbered item "X".
>
> ~~~
>
> X. Recent progress in the development of quantum computers pose a threat
> to widely deployed public key algorithms.  As a result, there is a need
> to prepare for a day when cryptosystems such as RSA, Diffie-Hellman,
> ECDSA, ECDH, and EdDSA cannot be depended upon.  As a result, there are
> efforts to develop standards for post-quantum cryptosystem (PQC)
> algorithms that that will be secure if large-scale quantum computers
> are ever developed.
>
> a. Specify the use of PQC public key algorithms with the PKIX
> certificates and the Cryptographic Message Syntax (CMS).
>
> b. Develop specifications to facilitate a lengthy transition from
> today's public key algorithms to PQC public key algorithms.  Unlike
> previous algorithm transitions, time will be needed before there is
> full confidence in the PQC public key algorithms.  Therefore,
> transition mechanisms that combine traditional algorithms with PQC
> algorithms will be needed for "hybrid key establishment" and "dual
> signatures".  NIST defines "hybrid key establishment" as any key
> establishment scheme that is a combination of two or more components
> that are themselves cryptographic key-establishment schemes.  NIST
> defines "dual signatures" as any signature scheme that consists of
> two or more signatures on a common message.  The specifications
> developed will enable PKIX and S/MIME protocols to support hybrid key
> establishment and dual signature mechanisms.
>
> ~~~
>
> Review and comments welcome.
>
> Russ
>
>
> > On Jan 28, 2021, at 2:27 PM, Mike Ounsworth <Mike.Ounsworth=
> 40entrust.com@dmarc.ietf.org> wrote:
> >
> > Proposed charter text:
> >
> > Post-quantum cryptography (PQC) will require a transition period in some
> ways similar to previous crypto migrations, but unique in that timelines
> require deployment of PQC before cryptographers have full confidence in the
> replacement algorithms. NIST has called for transition mechanisms that
> "layer" traditional and PQ crypto together, referred to as "hybrid key
> establishment" and "dual signatures". The LAMPS working group will update
> documents produced by the PKIX and S/MIME WG to support hybrid key
> establishment, encryption, and dual signature mechanisms.
> >
> > ---
> > Mike Ounsworth
> > Software Security Architect, Entrust
>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>


-- 
Mike Jenkins
mjjenki@nsa.gov <mjjenki@tycho.ncsc.mil> - if you want me to read it only
at my desk
m.jenkins.364706@gmail.com - to read everywhere
443-634-3951

--0000000000008d839d05ba349c96
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Not that I object to any of the work being proposed, but w=
e seem to have put paid to the notion of &quot;limited&quot;. This is looki=
ng like PKIXme.<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Sat, Jan 30, 2021 at 4:14 PM Russ Housley &lt;<a href=
=3D"mailto:housley@vigilsec.com">housley@vigilsec.com</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">Building on the text p=
roposed by Mike, I want to address a point raised by Max and a point raised=
 by Sean.<br>
<br>
First, Max observed that PQC algorithms will be used in both the one certif=
icate and the two certificate models.=C2=A0 So, I propose charter text that=
 has a place for each of them.<br>
<br>
Second, Sean observed that the charter will need some background text to ex=
plain what we are doing to the IESG.=C2=A0 So, I propose some charter text =
for additional context.<br>
<br>
Third, the charter is structured as a list of deliverables for the LAMPS WG=
.=C2=A0 So, I structured the proposed charter text as a new numbered item &=
quot;X&quot;.<br>
<br>
~~~<br>
<br>
X. Recent progress in the development of quantum computers pose a threat<br=
>
to widely deployed public key algorithms.=C2=A0 As a result, there is a nee=
d<br>
to prepare for a day when cryptosystems such as RSA, Diffie-Hellman,<br>
ECDSA, ECDH, and EdDSA cannot be depended upon.=C2=A0 As a result, there ar=
e<br>
efforts to develop standards for post-quantum cryptosystem (PQC)<br>
algorithms that that will be secure if large-scale quantum computers<br>
are ever developed.<br>
<br>
a. Specify the use of PQC public key algorithms with the PKIX<br>
certificates and the Cryptographic Message Syntax (CMS).<br>
<br>
b. Develop specifications to facilitate a lengthy transition from<br>
today&#39;s public key algorithms to PQC public key algorithms.=C2=A0 Unlik=
e<br>
previous algorithm transitions, time will be needed before there is<br>
full confidence in the PQC public key algorithms.=C2=A0 Therefore,<br>
transition mechanisms that combine traditional algorithms with PQC<br>
algorithms will be needed for &quot;hybrid key establishment&quot; and &quo=
t;dual<br>
signatures&quot;.=C2=A0 NIST defines &quot;hybrid key establishment&quot; a=
s any key<br>
establishment scheme that is a combination of two or more components<br>
that are themselves cryptographic key-establishment schemes.=C2=A0 NIST<br>
defines &quot;dual signatures&quot; as any signature scheme that consists o=
f<br>
two or more signatures on a common message.=C2=A0 The specifications<br>
developed will enable PKIX and S/MIME protocols to support hybrid key<br>
establishment and dual signature mechanisms.<br>
<br>
~~~<br>
<br>
Review and comments welcome.<br>
<br>
Russ<br>
<br>
<br>
&gt; On Jan 28, 2021, at 2:27 PM, Mike Ounsworth &lt;Mike.Ounsworth=3D<a hr=
ef=3D"mailto:40entrust.com@dmarc.ietf.org" target=3D"_blank">40entrust.com@=
dmarc.ietf.org</a>&gt; wrote:<br>
&gt; <br>
&gt; Proposed charter text:<br>
&gt; <br>
&gt; Post-quantum cryptography (PQC) will require a transition period in so=
me ways similar to previous crypto migrations, but unique in that timelines=
 require deployment of PQC before cryptographers have full confidence in th=
e replacement algorithms. NIST has called for transition mechanisms that &q=
uot;layer&quot; traditional and PQ crypto together, referred to as &quot;hy=
brid key establishment&quot; and &quot;dual signatures&quot;. The LAMPS wor=
king group will update documents produced by the PKIX and S/MIME WG to supp=
ort hybrid key establishment, encryption, and dual signature mechanisms.<br=
>
&gt; <br>
&gt; ---<br>
&gt; Mike Ounsworth<br>
&gt; Software Security Architect, Entrust<br>
<br>
_______________________________________________<br>
Spasm mailing list<br>
<a href=3D"mailto:Spasm@ietf.org" target=3D"_blank">Spasm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/spasm" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/spasm</a><br>
</blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g=
mail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr=
"><div><div dir=3D"ltr">Mike Jenkins<br><div><a href=3D"mailto:mjjenki@tych=
o.ncsc.mil" target=3D"_blank">mjjenki@nsa.gov</a> - if you want me to read =
it only at my desk<br></div><a href=3D"mailto:m.jenkins.364706@gmail.com" t=
arget=3D"_blank">m.jenkins.364706@gmail.com</a> - to read everywhere<br>443=
-634-3951</div></div></div></div></div></div></div></div>

--0000000000008d839d05ba349c96--


From nobody Sun Jan 31 13:19:32 2021
Return-Path: <kaduk@mit.edu>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D793A1268; Sun, 31 Jan 2021 13:19:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zYJPqpdlJHNH; Sun, 31 Jan 2021 13:19:24 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1028C3A1262; Sun, 31 Jan 2021 13:19:23 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 10VLJBou023995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 31 Jan 2021 16:19:15 -0500
Date: Sun, 31 Jan 2021 13:19:11 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: david.cooper@nist.gov, sharon.boeyen@entrust.com, rdd@cert.org, pkix@ietf.org, spasm@ietf.org
Message-ID: <20210131211911.GQ21@kduck.mit.edu>
References: <20210128154420.4B40EF40715@rfc-editor.org> <20210128161318.GV21@kduck.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210128161318.GV21@kduck.mit.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/gdurlxehk0nmCcmB3Fl7lOBC1FI>
Subject: Re: [lamps] [Technical Errata Reported] RFC5280 (6414)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jan 2021 21:19:26 -0000

On Thu, Jan 28, 2021 at 08:13:25AM -0800, Benjamin Kaduk wrote:
> On Thu, Jan 28, 2021 at 07:44:20AM -0800, RFC Errata System wrote:
> > The following errata report has been submitted for RFC5280,
> > "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile".
> > 
> > --------------------------------------
> > You may review the report below and at:
> > https://www.rfc-editor.org/errata/eid6414
> > 
> > --------------------------------------
> > Type: Technical
> > Reported by: Rob Stradling <rob@sectigo.com>
> > 
> > Section: 4.2.1.12
> > 
> > Original Text
> > -------------
> >    id-kp-serverAuth             OBJECT IDENTIFIER ::= { id-kp 1 }
> >    -- TLS WWW server authentication
> >    -- Key usage bits that may be consistent: digitalSignature,
> >    -- keyEncipherment or keyAgreement
> > 
> > Corrected Text
> > --------------
> >    id-kp-serverAuth             OBJECT IDENTIFIER ::= { id-kp 1 }
> >    -- TLS WWW server authentication
> >    -- Key usage bits that may be consistent: digitalSignature
> >    -- and/or (keyEncipherment or keyAgreement)
> > 
> > Notes
> > -----
> > In https://github.com/zmap/zlint/issues/553 there's been some disagreement and confusion about how to correctly interpret the "or" in the Original Text.  "You can only set one of these three bits" is one interpretation, and it's hard to argue that this interpretation is inconsistent with the Original Text.
> > 
> > However, digitalSignature+keyEncipherment makes sense for an RSA leaf certificate, and digitalSignature+keyAgreement makes sense for an ECC leaf certificate.  Both are widely used, to enable ephemeral and non-ephemeral TLS ciphersuites in conjunction with a single server certificate.
> > 
> > Given that RFC5480 section 3 explicitly permits digitalSignature+keyAgreement in an ECC leaf certificate, I think it's likely that my proposed Corrected Text conveys the RFC5280 authors' intended meaning.
> 
> I would be inclined to mark this as "editorial" and "hold for document
> update".  Given that across the list of EKU values both "or" and "and/or"
> are used, it seems like there was probably some intent to distinguish
> between them, but I don't see that we will get clear agreement on what wa
> intended at the time of publication.

In light of the subsequent discussion, my new proposal is to adopt Paul
Hoffman's suggestion and use "editorial"+"rejected", with a verifier note
along the lines of:

  This errata report correctly notes that the description for other extended
  key usage values appear to differentiate between "or" and "and/or".
  However, the suggestion that the lists of "key usage bits that may be
  consistent" with a given extended key usage value are somehow restrictive
  with normative force on which key usage bits can appear seems to be based
  on a mistaken premise.  What key usage bits can appear are governed by the
  rules for the key usage extension, which are in practice (but not by
  protocol) limited by the capabilities of current cryptographic algorithms,
  and the descriptive text here seems to just be an attempt to reflect those
  algorithmic limitations.  It should not be interpreted as making a
  normative restriction on which key usage bits can appear with a given
  extended key usage value -- doing so would raise the prospect of
  conflicting restrictions imposed by different extended key usage values,
  and it is well-known that multiple extended key usage values are permitted
  in any given certificate.

Any other comments?

Thanks,

Ben


From nobody Sun Jan 31 13:36:24 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9CFB3A1286 for <spasm@ietfa.amsl.com>; Sun, 31 Jan 2021 13:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9NrcsL9upxd for <spasm@ietfa.amsl.com>; Sun, 31 Jan 2021 13:36:22 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B8CA3A1285 for <spasm@ietf.org>; Sun, 31 Jan 2021 13:36:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 93F8438994; Sun, 31 Jan 2021 16:39:01 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gQr9QITFUnrh; Sun, 31 Jan 2021 16:39:01 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1F05038980; Sun, 31 Jan 2021 16:39:01 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 83D0D65E; Sun, 31 Jan 2021 16:36:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Michael Jenkins <m.jenkins.364706@gmail.com>, LAMPS <spasm@ietf.org>
In-Reply-To: <CAC2=hneq2Lx5Ke1fpEjSgUPvP58MBEOD9LiB6rnNRQnirqAf9A@mail.gmail.com>
References: <DM6PR11MB43808FA7D74229A5997965649FBA9@DM6PR11MB4380.namprd11.prod.outlook.com> <E64102E4-AA88-4B87-814A-6C79F6655102@vigilsec.com> <CAC2=hneq2Lx5Ke1fpEjSgUPvP58MBEOD9LiB6rnNRQnirqAf9A@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Sun, 31 Jan 2021 16:36:19 -0500
Message-ID: <10212.1612128979@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/t_zcdU2MOnA6vnk3vTDQRRjjHLI>
Subject: Re: [lamps] Proposed re-charter text for hybrid and dual crypto modes
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jan 2021 21:36:24 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Michael Jenkins <m.jenkins.364706@gmail.com> wrote:
    > Not that I object to any of the work being proposed, but we seem to
    > have put paid to the notion of "limited". This is looking like PKIXme.

I hear what you are saying.
I think that things would be best if we assumed we have to open 5280.
This work is much needed PKIX-maintenance.
Spinning another WG won't change the effort involved, though.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmAXItMACgkQgItw+93Q
3WVOVQf6A7WgD5HLV3x/2Ce5wsQq4rZMA0TionTWBpF15cT+dJHM4UgPhdGJZSB2
WLR1E1Evzx75vAdHeQqSfWw9QASWJrxkJgnyLI1eizpCheTr16thdURA3mLi368d
z3H/bD+VfKKNjpIMxGUTPmTEKfN5DmVFjsOfcOiGSJijUr3U6mfptr6SjR+evspY
6cmQGCp2PYYWjAbK+xLPffTUeLWmhZwPx+EuzooXcmRPaBYrWB2wbuZs7BSLC4Wz
+NlOUdY/ipzEzuHxyZaqxF8I5pCJV+qs1I7gv01BnGsiZ0sizq7plc7GS3k/AzoX
yRR7rT+pnJ0GdS+mMZjgfHqj1Vx8PA==
=5ZGT
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Jan 31 14:32:34 2021
Return-Path: <ryan.sleevi@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0011E3A12D1; Sun, 31 Jan 2021 14:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.42
X-Spam-Level: 
X-Spam-Status: No, score=-1.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNf3NdZ0UqDn; Sun, 31 Jan 2021 14:32:27 -0800 (PST)
Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 409203A12D0; Sun, 31 Jan 2021 14:32:27 -0800 (PST)
Received: by mail-pg1-f182.google.com with SMTP id j2so9079956pgl.0; Sun, 31 Jan 2021 14:32:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Pv1Vdo8QNsBeLSh9gTitqp+3pPdGpkWSQQilU3kcBYM=; b=NNrnlVTQU74ySGFx01AyzbiCDDFeAOFXw0nr+hSo4IfDmKX1pJgK/t2X7kDv+Xjuc+ C9/E8dFh+W1ksHTAxkl+5tcDFC8mSJxIFt9eWSfG/nlJWII6aKTEHOqV5Ox4CqDxzlCf TlBpnYrFC5M+UuLzci+VfT1QSTXaXa3xrDIBCbi19+4IMLZdwW43BJh9vvoGfcG7/DHV KmftrxVZ7eU9cxcM7Uu/HTuor/UhfRpGGHKUSbbgnQPhhg5xP+nd1iWlaWNumgNuXQhS pXRMGMzjjMqoQDWi+Hv7wEZFtfx0jIIFRfFP8B7ESD++hYJnONyxCu8NujCXdnEjgC2S 49cA==
X-Gm-Message-State: AOAM533RId8fa4UvGLC4wJs/7Cr+XFoBYPAdxq74nlHZlGcNgxmISWE2 +ZVNBuCFARUcXZefgZh47sWS5qi+JbU=
X-Google-Smtp-Source: ABdhPJzNOMz1hOZJUt9DU6Qgg0Dy/QSd/LWZnx1DSB+eX7JMxH5A+sb0Mi6wOOieAXABPxgeTmJXew==
X-Received: by 2002:a05:6a00:16c7:b029:1b6:68a6:985a with SMTP id l7-20020a056a0016c7b02901b668a6985amr13472660pfc.44.1612132346367;  Sun, 31 Jan 2021 14:32:26 -0800 (PST)
Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com. [209.85.216.51]) by smtp.gmail.com with ESMTPSA id w67sm2782396pfb.79.2021.01.31.14.32.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 31 Jan 2021 14:32:26 -0800 (PST)
Received: by mail-pj1-f51.google.com with SMTP id z9so1248617pjl.5; Sun, 31 Jan 2021 14:32:26 -0800 (PST)
X-Received: by 2002:a17:90b:4d07:: with SMTP id mw7mr14607859pjb.172.1612132345978;  Sun, 31 Jan 2021 14:32:25 -0800 (PST)
MIME-Version: 1.0
References: <20210128154420.4B40EF40715@rfc-editor.org> <20210128161318.GV21@kduck.mit.edu> <20210131211911.GQ21@kduck.mit.edu>
In-Reply-To: <20210131211911.GQ21@kduck.mit.edu>
From: Ryan Sleevi <ryan-ietf@sleevi.com>
Date: Sun, 31 Jan 2021 17:32:16 -0500
X-Gmail-Original-Message-ID: <CAErg=HH5wNY=3HFaUTitAcak+yj+d85Q0QAVbFJ6J-i7dkP-BQ@mail.gmail.com>
Message-ID: <CAErg=HH5wNY=3HFaUTitAcak+yj+d85Q0QAVbFJ6J-i7dkP-BQ@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, sharon.boeyen@entrust.com,  "Roman D. Danyliw" <rdd@cert.org>, SPASM <spasm@ietf.org>, IETF PKIX <pkix@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d026ab05ba39cf5f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/rzvOIhFKvRX4iTKDT1_E42GH-Mg>
Subject: Re: [lamps] [pkix] [Technical Errata Reported] RFC5280 (6414)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jan 2021 22:32:29 -0000

--000000000000d026ab05ba39cf5f
Content-Type: text/plain; charset="UTF-8"

On Sun, Jan 31, 2021 at 4:19 PM Benjamin Kaduk <kaduk@mit.edu> wrote:.

> In light of the subsequent discussion, my new proposal is to adopt Paul
> Hoffman's suggestion and use "editorial"+"rejected", with a verifier note
> along the lines of:
>
>   This errata report correctly notes that the description for other
> extended
>   key usage values appear to differentiate between "or" and "and/or".
>   However, the suggestion that the lists of "key usage bits that may be
>   consistent" with a given extended key usage value are somehow restrictive
>   with normative force on which key usage bits can appear seems to be based
>   on a mistaken premise.  What key usage bits can appear are governed by
> the
>   rules for the key usage extension, which are in practice (but not by
>   protocol) limited by the capabilities of current cryptographic
> algorithms,
>   and the descriptive text here seems to just be an attempt to reflect
> those
>   algorithmic limitations.  It should not be interpreted as making a
>   normative restriction on which key usage bits can appear with a given
>   extended key usage value -- doing so would raise the prospect of
>   conflicting restrictions imposed by different extended key usage values,
>   and it is well-known that multiple extended key usage values are
> permitted
>   in any given certificate.
>
> Any other comments?
>

Hey Ben,

I think you were the only one that raised the concern about normative
force, but I think I'd disagree with you here, especially in light of the
work clarifying RFC 8813.

I think your proposed response would thus actually substantially change
things, by suggesting something that is presently treated as normative as
informative. While that's certainly one way to square things, I think that
probably moves too far in the opposite direction.

I think the same applies to your remark about "(but not by protocol)",
since the reflection of the keyUsage bits here within the textual comment
for EKU is actually a reflection of the TLS protocol when the PKIX work
first began (and continues to this day). Namely, the binding of keyUsage
bits to ciphersuite selection, and (both implicitly via spec and explicitly
via implementation) to the extendedKeyUsage.

So I don't think the premise of the response may be a bit mistaken: there
is a normative reason for both the restriction of both KU and EKU
(cross-protocol attacks, as we saw with QUIC / TLS 1.3), and the limitation
of the KU within an EKU (relevant to the how the given EKU makes use of the
key; in this case, the TLS ciphersuites associated with RSA and EC keys)

To that end, I'm perhaps missing what you mean by "doing so would raise the
prospect of conflicting restrictions imposed by different extend key usage
values". It's very intentional that, in "every major implementation", the
EKU is the primary means of preventing cross-protocol attacks enabled by
key reuse. If, for example, usage A required KU (1, 2) and usage B required
KU (3, 4), then it should be very much the fact that a single certificate
usable for both usage A and usage B (as distinct EKUs) would not be issued,
because it would enable the same set of cross-protocol/downgrade attacks
that we've seen plague SSL 2 -> SSL 3, SSL 3 -> TLS 1, and TLS <= 1.2 ->
TLS 1.3.

I do support the conclusion of this being "editorial that accidentally
became normative" (that is, that it "should" have been "and/or"), but I
think given the ramifications to key reuse, the rest of the text may swing
too far in overcorrecting in a way that would introduce security issues, or
at least require their careful discussion.

--000000000000d026ab05ba39cf5f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jan 31, 2021 at 4:19 PM Benja=
min Kaduk &lt;<a href=3D"mailto:kaduk@mit.edu">kaduk@mit.edu</a>&gt; wrote:=
.</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">
In light of the subsequent discussion, my new proposal is to adopt Paul<br>
Hoffman&#39;s suggestion and use &quot;editorial&quot;+&quot;rejected&quot;=
, with a verifier note<br>
along the lines of:<br>
<br>
=C2=A0 This errata report correctly notes that the description for other ex=
tended<br>
=C2=A0 key usage values appear to differentiate between &quot;or&quot; and =
&quot;and/or&quot;.<br>
=C2=A0 However, the suggestion that the lists of &quot;key usage bits that =
may be<br>
=C2=A0 consistent&quot; with a given extended key usage value are somehow r=
estrictive<br>
=C2=A0 with normative force on which key usage bits can appear seems to be =
based<br>
=C2=A0 on a mistaken premise.=C2=A0 What key usage bits can appear are gove=
rned by the<br>
=C2=A0 rules for the key usage extension, which are in practice (but not by=
<br>
=C2=A0 protocol) limited by the capabilities of current cryptographic algor=
ithms,<br>
=C2=A0 and the descriptive text here seems to just be an attempt to reflect=
 those<br>
=C2=A0 algorithmic limitations.=C2=A0 It should not be interpreted as makin=
g a<br>
=C2=A0 normative restriction on which key usage bits can appear with a give=
n<br>
=C2=A0 extended key usage value -- doing so would raise the prospect of<br>
=C2=A0 conflicting restrictions imposed by different extended key usage val=
ues,<br>
=C2=A0 and it is well-known that multiple extended key usage values are per=
mitted<br>
=C2=A0 in any given certificate.<br>
<br>
Any other comments?<br></blockquote><div><br></div><div>Hey Ben,</div><div>=
<br></div><div>I think you were the only one that raised the concern about =
normative force, but I think I&#39;d disagree with you here, especially in =
light of the work clarifying RFC 8813.</div><div><br></div><div>I think you=
r proposed response would thus actually substantially change things, by sug=
gesting something that is presently treated as normative as informative. Wh=
ile that&#39;s certainly one way to square things, I think that probably mo=
ves too far in the opposite direction.</div><div><br></div><div>I think the=
 same applies to your remark about &quot;(but not by protocol)&quot;, since=
 the reflection of the keyUsage bits here within the textual comment for EK=
U is actually a reflection of the TLS protocol when the PKIX work first beg=
an (and continues to this day). Namely, the binding of keyUsage bits to cip=
hersuite selection, and (both implicitly via spec and explicitly via implem=
entation) to the extendedKeyUsage.</div><div><br></div><div>So I don&#39;t =
think the premise of the response may be a bit mistaken: there is a normati=
ve reason for both the restriction of both KU and EKU (cross-protocol attac=
ks, as we saw with QUIC / TLS 1.3), and the limitation of the KU within an =
EKU (relevant to the how the given EKU makes use of the key; in this case, =
the TLS ciphersuites associated with RSA and EC keys)</div><div><br></div><=
div>To that end, I&#39;m perhaps missing what you mean by &quot;doing so wo=
uld raise the prospect of conflicting restrictions imposed by different ext=
end key usage values&quot;. It&#39;s very intentional that, in &quot;every =
major implementation&quot;, the EKU is the primary means of preventing cros=
s-protocol attacks enabled by key reuse. If, for example, usage A required =
KU (1, 2) and usage B required KU (3, 4), then it should be very much the f=
act that a single certificate usable for both usage A and usage B (as disti=
nct EKUs) would not be issued, because it would enable the same set of cros=
s-protocol/downgrade attacks that we&#39;ve seen plague SSL 2 -&gt; SSL 3, =
SSL 3 -&gt; TLS 1, and TLS &lt;=3D 1.2 -&gt; TLS 1.3.</div><div><br></div><=
div>I do support the conclusion of this being &quot;editorial that accident=
ally became normative&quot; (that is, that it &quot;should&quot; have been =
&quot;and/or&quot;), but I think given the ramifications to key reuse, the =
rest of the text may swing too far in overcorrecting in a way that would in=
troduce security issues, or at least require their careful discussion.</div=
></div></div>

--000000000000d026ab05ba39cf5f--

