MIME-Version: 1.0
References: <3104294.rU99Ex2XNH@kitterma-e6430>
 <20190117185019.16153200CDA113@ary.qy>
In-Reply-To: <20190117185019.16153200CDA113@ary.qy>
From: Seth Blank <seth@sethblank.com>
Date: Thu, 17 Jan 2019 11:25:33 -0800
Message-ID: <CAD2i3WOV16Hh5qLg9Dp3Kvroi-S+5UOzDWkX=ZBR9vRPTkyuww@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b6691d057fac5c44"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vyylH72yMi0XwbNnWl5B85CsG-g>
Subject: Re: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-01.txt
Precedence: list

--000000000000b6691d057fac5c44
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 17, 2019 at 10:50 AM John Levine <johnl@taugh.com> wrote:

> I wonder if there's any way to get the PSL to tag vanity TLDs.
>

I believe a single list is the best long term solution. It just needs the
domain and two flags, one for if the domain is a public suffix, and the
other is if its a public suffix domain (per this draft).

For instance;

domain          | PS | PSD
---------------------------------
.co.uk           | true | false
.gov.uk          | true | true
.brand           | false | true

This seems to adequately cover all uses cases described (with the .co.uk
example being the state of everything currently on the PSL), is simple, and
in one place.

I think the primary question (before we go down the PSL/Mozilla rabbit
hole) is what the proper technical solution is - one list, multiple lists,
no list.

After clarity on that, then we can dig into how and where this thing lives.

Seth

--000000000000b6691d057fac5c44
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 17, 2019 at 10:50 AM John Lev=
ine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:</=
div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">
I wonder if there&#39;s any way to get the PSL to tag vanity TLDs.<br></blo=
ckquote><div><br></div><div>I believe a single list is the best long term s=
olution. It just needs the domain and two flags, one for if the domain is a=
 public suffix, and the other is if its a public suffix domain (per this dr=
aft).</div><div><br></div><div>For instance;</div><div><br></div><div>domai=
n=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | PS | PSD</div><div>------------------=
---------------</div><div>.<a href=3D"http://co.uk">co.uk</a>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0| true | false<br></div><div>.<a href=3D"http://=
gov.uk">gov.uk</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | true | true</div><di=
v>.brand=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| false | true</div><div><=
br></div><div>This seems to adequately cover all uses cases described (with=
 the .<a href=3D"http://co.uk">co.uk</a> example being the state of everyth=
ing currently on the PSL), is simple, and in one place.</div><div><br></div=
><div>I think the primary question (before we go down the PSL/Mozilla rabbi=
t hole) is what the proper technical solution is - one list, multiple lists=
, no list.</div><div><br></div><div>After clarity on that, then we can dig =
into how and where this thing lives.</div><div><br></div><div>Seth</div><di=
v><br></div></div></div>

--000000000000b6691d057fac5c44--