Public Comment is a vital part of our multistakeholder model. It provides a mechanism for stakeholders to have their opinions and recommendations formally and publicly documented. It is an opportunity for the ICANN community to effect change and improve policies and operations.
本内容仅提供以下语言版本
I fully support this proposal as-is, there is a strong need for a private use TLD. The name is perfect as it conveys to both the tech-literate and the layman what it's purpose is for.
After working in a customer service role for an ISP for sometime, having the ability to direct them to [ISP]router.internal instead of the various permutations of 192.168.etc.etc would be a massive boon and simplify the perceived effort needed for a user to access their routers internal settings.
IP addresses are scary to the common user, rarely seen outside of perhaps a workplace background showing the internal IP. Domains are what everyone recognises as something they type into their address bar and is more user-friendly than hoping they type in an IP correctly (and with IPv6 adoption becoming more widespread, I can't even begin to imagine how to enter my routers IP in that format).
And on a personal level, I have already changed my routers default to be 10.0.0.1, and being able to use the aforementioned router.internal to access the settings would just be a nice thing to have, along with being able to access internal devices by their hostname ( where examplePC.internal:12345 would allow me to access a locally hosted service on my home network and theoretically allow it to be router-agnostic as the actual IP will be handled by the router. And since .internal is reserved, I wouldn't even need to worry about DNS settings as it will be set by the relevant network device (at least as far as I understand the proposal)
This is my first comment I have submitted, so I apologise if I am running afoul of etiquette, but I hope my views and input are helpful regardless!
Support proposal as-is
* internal conveys purpose to layman and tech-literate
* private use TLD allows for better support and user-friendliness for home networking (no ambiguity on 192.168.0.1 or 192.168.1.1 etc)
* domains are more widely shared and see vs IPs
* IPv6 addresses may be used and greatly benefit from a TLD
* .internal should not be routed to a public (Internet) resource and should be managed by the internal network
* ability to access resources via hostname.internal
* ability to add a "plug and play" aspect where two devices on one network will be able to find each other via corresponding hostname.internal on a different network