Closed stevenlawrancesfdc closed 2 months ago
Not sure why this introduces a second block for the organization "Salesforce, Inc." instead of extending the already-existing block.
Good point. I'll extend the existing Salesforce.com block.
@yahesh @simon-friedberger Thanks! I now have the two Salesforce sections merged together.
LGTM.
ping @stevenlawrancesfdc
@simon-friedberger Thanks, and sorry for my delay here. I'll apply the feedback to this pull request now.
Public Suffix List (PSL) Pull Request (PR) Template
Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.
Checklist of required steps
[x] Description of Organization
[x] Robust Reason for PSL Inclusion
[x] DNS verification via dig
[x] Run Syntax Checker (make test)
[x] Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _PSL txt record in place in the respective zone(s) in the affected section: Expiration is now 2029-02-12T23:46:32Z, as per https://whois-webform.markmonitor.com/whois/
Submitter affirms the following:
For Private section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.
To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.
PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.
(Link: about propagation/expectations)
[x] Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.
Description of Organization
Salesforce, Inc. is an American cloud-based software company headquartered in San Francisco, California. It provides customer relationship management (CRM) software and applications focused on sales, customer service, marketing automation, e-commerce, analytics, and application development. A core component of this is Salesforce's Sales, Service, and Experience Cloud, which is an integrated software system that undergoes continuous development by around 10,000 software developers.
I am Steven Lawrance, an architect on Salesforce's Sales, Service, and Experience Cloud that focuses on how the system makes use of DNS names for maximizing web security and isolation for customers in a scalable manner.
Organization Website:
https://www.salesforce.com
Reason for PSL Inclusion
The Salesforce Sales, Service, and Experience Cloud system serves a large number of URL hostname patterns. To represent these in our internal development environment used by ~10,000 developers while separating the actual production and development domains, we use a URL hostname format that looks like MyDomainName.my.salesforce-com.WorkspaceID.w.crm.dev. To have WorkspaceID.w.crm.dev treated the same as 'com', we need to have .w.crm.dev in the PSL. The salesforce-com (or force-com, etc.) subdomain thus gets treated as a registrable domain for cookie and privacy features within web browsers, mimicking the production salesforce.com and force.com domains. In addition to .w.crm.dev, Salesforce has 26 partitions based on a letter that follows the 'w', hence the .wa.crm.dev, .wb.crm.dev, and so on names. Salesforce also has a separate development environment that uses 'd' instead of 'w', which is why *.d.crm.dev is in the list.
Number of users this request is being made to serve: Around 10,000 (estimated)
DNS Verification via dig
Results of Syntax Checker (
make test
)