-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I’ve noticed that an increasing amount of invaluable functionality, such as SRV and soon SVCB records, relies on services being registered with IANA as described in RFC 6335. I’ve also noticed that, in practice, a considerable amount of usage relies on unregistered names that are just squatting on the name.
As an example, take a look at the Wikipedia page on SRV records: <https://en.wikipedia.org/w/index.php?title=SRV_record&oldid=1110599784#Usage>. Of the 19 examples of usage, at least 7 use service names that are not in IANA’s registry. One, Matrix, even squats on an unrelated service that IS registered with IANA. There are a number of potential reasons one may wish to use service names unilaterally, without a formal registration: services under development or only intended for use with a narrow audience, for instance. I have an idea for namespacing service names to a DNS zone under the implementer’s control, thus preventing collision issues. It would not impact or replace existing service registries, but serve as a safe way to bypass them. This would be my first Internet Draft, so if this idea has any merit I’d welcome advice on how to proceed. My hope is that it would encourage developers to design applications around SRV or SVCB records from the start of development, rather than tacking them on later in an ad-hoc or unauthorized fashion. -----BEGIN PGP SIGNATURE----- iMwEARYKAHQWIQST9JhYTT2FVNyHHwCUsC6j0LZIGwUCYznn6lYYJ2h0dHBzOi8v b3BlbnBncGtleS5zYWtsYWQ1LmNvbS9maW5nZXJwcmludC9GRERGQzRBNEE2N0Qw NEVGRkVCOEU0MjQ5Q0EyMTQ5NTgzRURCRjg0JwAKCRCUsC6j0LZIG4VvAQCgIXtl d1aWO8Di5Aa1ooBltvvywQbMwnlFqSUuYiy9twEAuBXdqQowhOgUg0NU+SQp0abQ RSc8RQnBm+HDBLcUFwk= =TNQd -----END PGP SIGNATURE----- _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
