What does the URI path represent? about draft-ietf-masque-connect-ip HOT 4 CLOSED

Perhaps all we need is a reference to how those are defined for the http and https schemes:

The hierarchical path component and optional query component serve as an identifier for a potential target resource within that origin server's name space.

from draft-ietf-masque-connect-ip.

The /vpn and /proxy examples were just arbitrary names that were examples of paths the proxies could run on. Adding a reference and explaining these are examples sounds good.

from draft-ietf-masque-connect-ip.

To my understanding we currently don't specify multiple different functionalities based on the URI path component. Therefore we can work without any type of well-known URI suffix https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml#well-known-uris-1 and the discovery procedure here is that the MASQUE client need to be configured/supplied with a base URI that gives the proxy as host component, and the path that is relevant on that proxy to invoke the MASQUE service. So unless we want to something more advance I think we can just make clear that the masque service resource is identified however the proxy want it to be.

from draft-ietf-masque-connect-ip.

I think that having MASQUE be able to work with any URI is a feature, and whether someone else down the line wants to make an auto-discovery for MASQUE-based proxies, either with .well-known or some other mechanism, should be a separate discussion (and likely separate document).

from draft-ietf-masque-connect-ip.