mnot
commented
1 month ago BITAG is not on the list of recognised standards organisations, so this will need to be provisional.
That makes the template:
- URI Suffix: broadband-labels
- Reference: https://www.bitag.org/BITAG-BB-Labels.pdf
- Status: provisional
- Change Controller: Broadband Internet Technical Advisory Group (BITAG) https://www.bitag.org/
- Related Information: None
From https://mailarchive.ietf.org/arch/msg/wellknown-uri-review/pEUqnSFE5phmoe43Hc9Bdi3cBFI:
Request Form
This memo registers the 'broadband-labels' well-known URI in the Well-Known URIs registry as defined by RFC 8615.
URI Suffix:
broadband-labels
Change Controller:
Broadband Internet Technical Advisory Group (BITAG)
https://www.bitag.org/
Reference Document(s):
Reference to the document that specifies the field, preferably including a URI that can be used to retrieve a copy of the document. An indication of the relevant sections may also be included, but is not required.
https://www.bitag.org/BITAG-BB-Labels.pdf
Status:
Permanent
Related Information:
None
Existing Use of This Well-Known URI
To the BITAG's knowledge, no one is currently using this well-known URI.
Security Considerations
The URI MUST use TLS to provide validation and transport security.
These machine-readable broadband label files should cover a reasonable number of users, rather than one label for each user, so that it is not possible to identify an end user based solely on the label file.