RFC 4085:Embedding Globally-Routable Internet Addr...
RFC-Ref

traffic


Click on the red underlined text to get to the source

... IP address blocks and increasing the cost of operation. Unsolicited traffic may continue to be delivered to the embedded address well after the IP address ...
... hosts the service for which that traffic was intended. Circa 1997, the authors of RFC 2101 [7 ...


... Vendors should, by default, disable unnecessary features in their products. This is especially true of features that generate unsolicited Internet traffic. In this way, these hosts will be conservative regarding the unsolicited Internet traffic ...
... Internet traffic. In this way, these hosts will be conservative regarding the unsolicited Internet traffic they produce. For instance, one of the most common uses of embedded IP addresses ...
... Vendors should provide an operator interface for every feature that generates unsolicited Internet traffic. A prime example is this: the Domain Name System resolver should have an interface ...
... service when necessary to address unexpected, increased traffic and the aforementioned problems. ...


... IP address 128.105.39.11, and hence produces a large scale flood of Internet traffic from hundreds of thousands of source addresses, destined for the University's network, resulting in ...



Google
Web
RFC-Ref