3 ms·
Looking at the RFC it's never explained why this is needed. Or was needed back in 1996, perhaps something to go with universities and data center logistics back
by politelemon 1y ago
Looking at the RFC it's never explained why this is needed. Or was needed back in 1996, perhaps something to go with universities and data center logistics back then?
- edent 1y agoRFCs are, in my experience, vague about the problem they're attempting to solve. There's no reason this couldn't be a human-readable string like "42 Wallaby Way, Sidney".
- teddyh 1y agoSNMP sysLocation already existed, with its free-form text content. Presumably, people wanted something both more precise and machine-readable.
- echoangle 1y ago> Looking at the RFC it's never explained why this is needed. Chapter 5.1 (Suggested Uses) has at least some vague suggestions: > Some uses for the LOC RR have already been suggested, including the > USENET backbone flow maps, a "visual traceroute" application showing > the geographical path of an IP packet, and network management > applications that could use LOC RRs to generate a map of hosts and > routers being managed.