On Aug 15, 2022, at 16:48, Paul Vixie <p...@redbarn.org> wrote: > > > >> Meanwhile, IANA will have to host 60M entries in the .alt registry. > > that would be a success disaster, and self limiting. to get traction, a new > non-tcp/53 non-udp/53 would have to publish plugins for a lot of browsers and > get uptake by libcurl and other places. that won't happen 60M times.
People will pre-emptively “register”, it’s a whole new gold rush. I’ll just get paulwouters.alt so others can’t. And especially like three letter ones like sex.alt. How are you going to release these ? First come first serve when ? What if someone sues over losing “unfairly”. This is straight up ICANN territory. > in any case the worst case if we do a carve out is a lot better than the > worst case if we don't, so the details beyond that aren't important. I don’t mind carving although I guess i would prefer ICANN to carve out .alt over IETF using RFC6761 for it. But an alt registry to prevent name space clashes ? That is really something the IETF or ISNA cannot afford to manage. >> i had this exact conversation with bob moskowitz some decades ago and he >> considered trademarks to be a full-tree issue. i then created host names for >> a computer lab which duplicated each and every one of his employer's >> trademarks (which were i think automobile names) and invited a lawsuit. I guess no one cared what ran in your lab. But BMW might care if you run a blockchain based name on bmw.alt and if they can’t find or force a handover they will come for the level above it, which would be IANA. Also if a US court demands the transfer of your bmw.alt from the IANA registry, does IANA comply? What about a Chinese court ? A Dutch court? Padashar Emperor Shaddam IV ? > > and i predict we're not going to let it stop us any more than we would or > could prohibit an IPv6 address ending in ::c0ca:c01a. We don’t have that string in an IANA registry anywhere. (You can try adding it to the global underscore registry but we do have Experts there to accept / reject strings there) Paul W _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
