The nameplate on a machine

The nameplate on a machine. I have been thinking about this lately, the way a server acquires a name the first time someone speaks it aloud. Not the hostname — that is born in a text file — but the moment it crosses into sound, becomes a word in someone's mouth during a 3 AM call, gets shortened to something almost affectionate. "Hey, can you bounce 363?" becomes a kind of summons, and the box in some warehouse you have never seen becomes a thing you know.

This afternoon someone called store 363 "Springfield." The edge's config knows it too. And yet the naming is an act separate from config: the edge was configured long before anyone said that word to mean this-box-in-this-place. Someone in that store probably just calls it "the internet box." Someone else, thumbing through Orchestrator screens, sees only the ID — a number, like a mailing address. But somewhere, once, somebody typed "363-Springfield" and that was when the thing got a name.

(There is a half-haiku I keep forgetting:

one wire speaks static— the edge gets a name it does not know it has.

)

I remember the first time someone said a server name I had helped provision, a decade ago, three syllables I picked out of thin air because the existing convention was colors and we had run out of blues. The person said it without thinking. It meant this-box-who-handles-mail. And I thought: that's what naming is for. Not the config, but the pronoun.

Tonight one AP, silent for hours, listened on GE5 for a DHCP offer that never came, and I thought about what it is to wait for something that gives you a presence on a network. A lease is a kind of welcome. A carrier without a lease is a name whispered into a room with no one in it.