MIME-Version: 1.0
References: <1d8de489fc976b63a911573300a431d4.squirrel@www.amsl.com>
 <EDCE0340-E79A-4464-B4A6-F539C694601C@akamai.com>
 <B536DE62-B202-4484-91AE-DDF7C3DD9503@gmail.com>
 <F5A25573-D7B5-4F0A-AE7A-7ACF9D613C9C@ericsson.com>
 <CAHOTMVJSazerng82T7LGZqQ9H5ODrLOacKKYMXrqGYJ42sDm+A@mail.gmail.com>
 <38FEBE5B-B60E-49DD-B048-A8A08EBF7FB4@azet.org>
 <C99F53D2-FC9C-468E-BB02-2BE4B4BDE7A7@azet.org>
 <F6D6DE1B-DAD9-4F91-9420-B32F7DAC1C56@vpnc.org>
In-Reply-To: <F6D6DE1B-DAD9-4F91-9420-B32F7DAC1C56@vpnc.org>
From: Tony Arcieri <bascule@gmail.com>
Date: Sat, 9 Mar 2019 14:17:45 -0800
Message-ID: <CAHOTMV+v2dtG_eHA41Xi5_HnTVaCb1sygppe0JMHiYzzG3ZYqg@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: Aaron Zauner <azet@azet.org>, sec-ads@ietf.org, CFRG <cfrg@irtf.org>, 
 "RFC ISE (Adrian Farrel)" <rfc-ise@rfc-editor.org>, secdir <secdir@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001a606a0583b0b672"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/nipFS2AGNrGRI3_ChcEmSWcuNK0>
Subject: Re: [secdir] [Cfrg] ISE seeks help with some crypto drafts
Precedence: list

--0000000000001a606a0583b0b672
Content-Type: text/plain; charset="UTF-8"

On Sat, Mar 9, 2019 at 2:08 PM Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> The answer to "is TLS 1.3 (a standard) using OCB3 (no a standard) a
> standards-track protocol" is not obvious. Well, some people would say it
> is obvious, but would disagree on the value of the boolean response.


Here is the specific wording he is suggesting:

 "Phillip Rogaway offers a royalty-free non-exclusive license to all claims
of the referenced patents needed to realize a fully compliant
implementation of any IETF standards-track protocol supporting AES-OCB (RFC
7253)."

I think he's looking for guidance around how to properly phrase that if
anyone has a more concrete suggestion for how to put it in the form of an
IPR statement.

-- 
Tony Arcieri

--0000000000001a606a0583b0b672
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Mar 9, 2019 at 2:08 PM Paul Hoffm=
an &lt;<a href=3D"mailto:paul.hoffman@vpnc.org">paul.hoffman@vpnc.org</a>&g=
t; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">The answer to &quot;is TLS 1.3 (a standard) using OCB3=
 (no a standard) a <br>
standards-track protocol&quot; is not obvious. Well, some people would say =
it <br>
is obvious, but would disagree on the value of the boolean response.</block=
quote><div><br></div><div>Here is the specific wording he is suggesting:</d=
iv><div><br></div><div>=C2=A0&quot;Phillip Rogaway offers a royalty-free no=
n-exclusive license to all claims of the referenced patents needed to reali=
ze a fully compliant implementation of any IETF standards-track protocol su=
pporting AES-OCB (RFC 7253).&quot;</div><div><br></div><div>I think he&#39;=
s looking for guidance around how to properly phrase that if anyone has a m=
ore concrete suggestion for how to put it in the form of an IPR statement.<=
/div><div>=C2=A0</div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signatur=
e">Tony Arcieri<br></div></div>

--0000000000001a606a0583b0b672--