Wearing my ICANN hat:
When a topic is in a public comment period, it is very appropriate and
appreciated for community members to send comments in, as Paul Marks has.
Having a discussion on an external forum will have no effect on the public
comment period because the comment from Paul Marks
On Sat, Jan 27, 2024 at 8:33 PM Paul Wouters wrote:
>
> LAN implies local area network. So an organization with multiple locations
> would have a LAN at each location, but the .LAN would be their collection of
> LANs? I think that would lead to confusion.
>
> Paul
There are non-commercial
According to Paul Wouters :
>
>> On Jan 27, 2024, at 16:42, Paul Marks wrote:
>>
>>  pick .lan
>> instead? It seems that a lot of people are already using this abbreviation
>> on their internal
>networks, which happen to be local in
>> area.
>
>LAN implies local area network. So an
> On Jan 27, 2024, at 16:42, Paul Marks wrote:
>
> pick .lan
> instead? It seems that a lot of people are already using this abbreviation
> on their internal networks, which happen to be local in
> area.
LAN implies local area network. So an organization with multiple locations
would have
I recently sent this idea to ICANN, but I'm curious if DNSOP finds it
interesting.
There is currently a proposal to reserve .internal for private use. I
think this word is bureaucratically and semantically the right choice,
but 8 characters is too many to type.
So let's take .internal and
