vendor
Click on the red underlined text to get to the source
...
Some vendors of consumer electronics and network gear have
unfortunately chosen to embed, or "hard-code", globally-routable
...
... hosts, they cannot be relied upon to fix problems, if and
when they arise. Therefore, a significant responsibility lies with
the manufacturer or vendor of an Internet host to avoid embedding IP
addresses ...
...
Vendors should, by default, disable unnecessary features in their
products. This is especially true of features that generate
unsolicited Internet traffic ...
...
Vendors should provide an operator interface for every feature that
generates unsolicited Internet traffic ...
... of deployed Internet hosts, designers and vendors are encouraged to
introduce service names. These names should be within a domain ...
... domain name.
For instance, a vendor named "Example, Inc." with the domain
"example.com" might configure its product to find its SNTP ...
... server.v1.widget.config.example.com". Here the "config.example.com"
namespace is dedicated to that vendor's product configuration, with
subdomains introduced as deemed necessary. Such special-purpose
domain names ...
... lifetime.
An alternative to inventing vendor-specific domain naming conventions
for a product's service ...
... domain
name space are also ephemeral and can change owners for various
reasons, including acquisitions and litigation. As such, developers
and vendors should explore a product's potential failure modes
resulting from the loss of administrative control of a given domain ...
... Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC 2132draft, March 1997. ...
... In May 2003, the University of Wisconsin discovered that a network
product vendor named NetGear had manufactured and shipped over
700,000 routers with firmware containing a hard-coded reference to
...