Only register .well-known/masque

[DavidSchinazi]

As per RFC 8615 s3 registrations cannot contain a / character so we register .well-known/masque instead of .well-known/masque/udp

[LPardue]

L602 still includes /udp, Is that intended?

[DavidSchinazi]

Yeah my thinking was that we register masque and for now only define semantics for masque/udp. A future document can tweak the related info line to also assign semantics to masque/foobar

[LPardue]

I'm not a .well-known expert. My interpretation from mnot's suggestion was the prefix ends up as ".well-known/masque" and that the remainder is defined here as "/udp/{target_host}/{target_port}". Yes something else might come along and define other things to follow the prefix .well-known/masque but that can be deferred for later, and that spec needs to state all of its own rules.

An alternative is that we expect everything after the prefix to behave in a similar way, I.e. .well-known/masque/{masque_type}/{target_host}/{target_port}. I don't know if that holds true.

[DavidSchinazi]

From reading RFC 8615 s3 it appears that there is a lot of flexibility on how to organize additional path components so this appears OK to me, but I'll let @mnot provide insights here

[mnot]

Yep, how you deal with what's "under" your registration is up to you. One option is to create a separate registry; another is to require additional values to update the registering RFC.