Op 16 okt. 2022 om 15:03 heeft Brian Dickson <brian.peter.dick...@gmail.com> het volgende geschreven:
> For example, using a hash function, such as sha2-256, with output encoded as > base32hex. > (This is just an example; any suitable function that takes URI as input and > produces an ASCII DNS-compatible label as output would suffice.) If we start from the position that names in this shared namespace don't need to be semantically meaningful to humans then this whole problem space becomes a whole lot easier, or perhaps doesn't even rise to the level of "problem". See also 98% of the work done by the ICANN community and arguably the entire business models of registries and registrars. However, I don't think we are starting from that position. For example we hear there is demand for .giraffe for the giraffe naming system described at https://giraffe.org/ because using giraffe.org as an anchor for that naming system in the namespace is not acceptable to anybody who cares about GNS. If giraffe.org doesn't cut the mustard then I have my doubts that jduxbenebrnjxudnxznbrnr.alt will satisfy anybody either. (If giraffe.org can't be tolerated then I also don't see why giraffe.alt is an obvious solution, but I sense people are tired of hearing me say that so I'll leave it this parenthetical cloak of invisibility and continue whistling innocently.) Joe _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
