The RFC is for a different time and place. Though some of the principles still stand and I have deployed/used many of them, but not all are applicable. I'm not

The RFC is for a different time and place. Though some of the principles still stand and I have deployed/used many of them, but not all are applicable. I'm not saying my scheme is perfect, or even very good, but it works for my needs and I've used the following convention for around 30+ years. I've got two schemes, one for small sites/personal installations, and one for big sites. w for workstations. t for tables. p for printers. c for cameras. a for access points. s for servers. m for mobiles/cellphones. v for vms. i for iot devices. u for "devices we don't know how to designate." x for sensors, e.g water leak sensor, package delivery box sensor. Obviously if you only have three devices in your entire home, it doesn't really make sense to have a "naming scheme." For personal installations and small sites (not an exhaustive list): a-studio-ap6 (access point in studio) a-catbathroom-ap6pro (access point in cats' bathroom) a-workshop-ap6 (access point in the workshop) a-rv-aplr (access point in the rv) w-lloyd-vr (workstation, household VR/gaming computer) w-justin-storm (workstation, storm is the CPU case manufacturer) l-justin-surfacebook2 (my surface laptop) l-joyce-surfacebook2 (wife's surface laptop) l-joyce-surfacestudio (wife's surface laptop) l-justin-mbp2013 (my old macbook) p-office-hp3600 (office printer) p-workshop-konica (konica minolta printer in workshop) p-office-canon (office printer) v-justin-ubuntu (virtualized linux) v-justin-arch (virtualized linux) v-justin-win10 (virtualized linux) t-lloyd-weather (samsung table for weather) t-lloyd-ipad00 t-lloyd-ipad01 c-lloyd-frontdoor (camera at front door) c-lloyd-garagedoor (camera on outside of garage door) c-lloyd-garageceiling (camera on the garage ceiling) s-lloyd-main (main home server) s-lloyd-backup (backup server) s-lloyd-storage (backup server at the storage locker) s-lloyd-cloud (our racked server in some midwest datacenter) s-lloyd-rv (server in the rv) m-joyce-pixel6 (wife's cellphone) m-justin-pixelpro7 (cellphone belonging to me) m-justin-note20 (cellphone belonging to me) m-justin-iphone13 (cellphone belonging to me) The local machine is given the name, though some cannot be easily renamed, or they have a restriction such as NETBIOS name length, and then the MAC is also set with a name on the router too, so magic packets and other tools know what the device is named even if the device is not broadcasting any name. It helps with identifying mystery devices on the network, and who owns the device. I apply the same principle to naming cats and people. "grey-cat", "black-cat", "fuzzy-black-cat", "pink-human", "mao" (cat), "cat", "cath" (also cat), "orange-cat", "chat" (also cat), "gatto" (cat). For large sites with dozens or hundreds of servers or multiple sites/data centers: IATA codes with rack and machine name and absolutely nothing creative, and clear separators between each part. e.g. lax-r01-s17. And then I make sure that any publicly accessible machines sit on their own "prod" domain separate from the company's main domain, e.g. hn-prod.com, or bigcorp-prod.com