adding https://www.riseinteractive.com to psl

[steven-chen-rise]

• Description of Organization

• Reason for PSL Inclusion

• DNS verification via dig

• Run Syntax Checker (make test)

• Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration.

Description of Organization

Organization Website: https://www.riseinteractive.com

Director of Web Development at Rise Interactive.
Rise Interactive is a digital media agency.

Reason for PSL Inclusion

Rise is interested in the public suffix list due an Apple iOS 14 update.
Facebook has provided documentation in regards to Enabling More Domain Verification Use Cases in Aggregated Event Measurement.
It mentions it will be supporting the Public Suffix List for domain verification and event configuration.
Rise is adding its domains to the public suffix list to ensure compatability and testing in regards to ad campaigns due to the update.

DNS Verification via dig

make test

[steven-chen-rise]

Creating the PR to get the url available for the DNS verification for dig.
Will be reaching out to our internal IT team to get the DNS updates and the registration expiration updated.
I will comment back on the PR when those changes are completed.

[dnsguru]

Closing as wontfix - see #1245

[dnsguru]

privacycg/private-click-measurement#78

[bedfordsean]

Hi @steven-chen-rise ,

The guidance from Facebook (clarified last week in the help centre article) is that this process is intended for large platform partners (like Shopify) to allow businesses that they host on behalf of to successfully validate their domain as if it were an eTLD+1.

The Public Suffix List is not useful, nor intended to be used as a means to gain additional subdomain events reporting. If you just want to use subdomains as part of Facebook's aggregate event measurement, you already get 8 events under your eTLD+1 of riseinteractive.com.

Can you confirm why you need subdomains under this eTLD+1 to be individually treated as eTLD+1s with cookie separation, which would be the behaviour post-addition to the PSL?

[steven-chen-rise]

@bedfordsean

Apologies for the late response. I reached out to our team member who requested this and here is the response I received.

We are an agency that represents a number of clients that are in similar situations where they only control a subdomain of the parent domain they are attached to...and those clients would like to be able to rank their own events rather than succumb to the parent domain's decisions and we were looking to test if we would be able to instruct our clients on what to do in order to get registered on the suffix list to enable them to rank their own events.

So the Rise Interactive implementation is a POC for one of our clients. If we need to clarify specifically with regards to the client in question, I'd be happy to reach out via email to connect.

[bedfordsean]

Thanks @steven-chen-rise

There are two effects I want to call out based on how public suffix listing works:

1. Once you're on the list, there is a limitation of same domain cookies and local storage, this means that "riseinteractive.com" can no longer have its own cookies, only subdomains can. I'm not sure that I see any subdomains of riseinteractive.com that show reasonable use cases of different clients being hosted on your domain (or none that a Google search shows up anyway!)
2. The browsers will enforce the behaviour described in Update public_suffix_list.dat #1 based on their own update cadence of the public suffix list. Some browsers don't update their lists more regularly than every few months. This means that if you're on the list and a browser updates their copy of the list, and you later decide to not be on the list, there may not be an easy way to back out the behaviour; it's not as simple as submitting another request here to get taken off of the list.

Given that you say this is a proof of concept for a (singular?) client, you may want to think more about these two considerations. I don't believe we'd want to approve public suffix listing for a single use case that isn't a long term direction you want to go in