Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist of required steps
Description of Organisation
Robust 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, and we shall keep the _PSL txt record in place in the respective zone(s) in the affected section
Submitter affirms the following:
We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook
(there are none)
This request was not submitted with the objective of working around other third-party limits
The Guidelines were carefully read and understood, and this request conforms
The submission follows the guidelines on formatting and sorting
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)
Description of Organisation
Electromagnetic Field (EMF) is a nonprofit 'hacker' festival held in the UK. The next event will be EMF 2024.
I am one of the volunteers organising and running EMF 2024, in particular in the Network (NOC) team, having performed the same for the previous EMF.
A key element of the festival's character is an IP network, with wired and wireless gigabit+ access, running in EMF's Autonomous System (AS60079) with transit links to the wider internet via fibre. The network facilitates the running of the event as well as being offered to attendees.
As a result, EMF's network hosts countless IP-connected projects, installations and demos brought by the public to the event; this is a fact relevant to this PR.
The event's primary domain is
emfcamp.org
, which is used for the public website, internal applications and email systems, but the separate domainemf.camp
is used for DNS in the 'event infrastructure'. This PR is to add a subdomain ofemf.camp
to the PSL, and so there is no concern around breaking our website(s) etc.Organisation Website:
https://www.emfcamp.org/
Reason for PSL Inclusion
Starting at EMF 2024 and continuing in future EMF events, we plan to provide to attendees the option to register DNS records under the
at.emf.camp
domain which point at on-site devices.The intended use is to provide friendly DNS names for network-connected hosts/devices brought by the public (attendees) to the event. These have been known to range in scale from IoT devices to rack-mountable servers, often running a web server and/or other interactive user-facing services.
From a security point of view, these network devices/services are mutually distrustful, having been brought to EMF by people who are most likely to be strangers to each other. While there is no commercial model to consider, the security model for EMF is similar to that of a shared/cloud hosting provider, where our 'customers' are not expected to maintain high levels of mutual trust.
We therefore intend for the PSL inclusion of
at.emf.camp
to establish isolation between direct subdomains, where implemented (e.g. in browser cookies), and to signify the intended security boundaries between its subdomains wherever the PSL is used by third parties to do so.Domain registration declaration
emf.camp
is currently registered until 2 April 2029 and we intend to maintain its registration indefinitely.User count estimate
Number of users this request is being made to serve: at least 3500 (planned EMF 2024 attendance + some accounting (~10% extra) for outside-event internet clients). Over the years the attendance figure at EMF has grown steadily.
The EMF network is open to the internet, and so hosts under
at.emf.camp
will not be generally restricted from being accessed over the internet too. Attendees commonly publicise their projects/installations on social media or other web platforms, leading to increased visitation over the network from the wider internet.DNS Verification via dig
Results of Syntax Checker (
make test
)