Re: [Masque] Re: draft-ietf-masque-connect-ethernet-06 early Httpdir review

On Tue, Jun 3, 2025 at 2:38 AM Martin Thomson <mt@lowentropy.net> wrote:
>
> On Thu, May 29, 2025, at 00:51, Alejandro Sedeño wrote:
> > Here, as Mirja said, I'm going for consistency with the rest of the
> > MASQUE suite.  Would it be more palatable if the /.well-known/ example
> > was only for the non-parameterized case and not the hypothetical and
> > underspecified vlan-identifier case?  Adding the "ethernet" entry to the
> > "masque" table in the .well-known registry is cheap, and registering it
> > now means it's available for future extension work.
>
> Just because it takes you five minutes to type the text that gets something into an IANA registry, or even the code that adds it to your implementation, that doesn't make it cheap.  Even if this isn't used, once you do that, this is a resource that now exists on every web server in existence.
>
> What you need to do is establish whether there is an actual need for someone to be given a domain name and use that as the only input they need to create a new Ethernet tunnel.  Given the additional information that this to-be-standard requires, from authentication details to all the business of how to Ethernet, that seems like a pretty unlikely case to me.

I've opened https://github.com/ietf-wg-masque/draft-ietf-masque-connect-ethernet/pull/24
with the intent to remove the entry, and will give that a couple of
days for anyone to speak up in favor of keeping it.

I'll follow up with additional changes early next week.

Thanks for the review,
-Alejandro

Received on Friday, 6 June 2025 14:49:10 UTC