Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <92c3be5c-4522-4072-d4ce-d7b41cdfebf0@akamai.com>
Date: Fri, 9 Mar 2018 19:35:09 -0500
Cc: "<tls@ietf.org>" <tls@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0DDF644-3C44-401F-8C13-46E9BE2ED9C0@sn3rd.com>
References: <CABcZeBPCz229n6sZZYGF=suFoXVt1MdCWJU5e1gyG0sj=Zgt5Q@mail.gmail.com>
 <92c3be5c-4522-4072-d4ce-d7b41cdfebf0@akamai.com>
To: Benjamin Kaduk <bkaduk@akamai.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/qTX1CG8msVOrnD6q5e9QaGYY4Ec>
Subject: Re: [TLS] Duplicate oid_filters
Precedence: list

Okay so the OIDs can=E2=80=99t appear twice in the certificate, because =
certificate extensions are only supposed to appear once so why don=E2=80=99=
t we just follow suit and require no dupes?

spt

> On Mar 9, 2018, at 16:44, Benjamin Kaduk <bkaduk@akamai.com> wrote:
>=20
> (See also https://github.com/tlswg/tls13-spec/issues/1179)
>=20
> On 03/09/2018 03:35 PM, Eric Rescorla wrote:
>> See issue #1166.
>>=20
>> The current text neither allows nor prohibits the same OID appearing
>> twice. We should do one or the other.
>>=20
>=20
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls