datagram
Click on the red underlined text to get to the source
...
We consider here only the case of unreliable, unsequenced, possibly
duplicated datagram broadcasts (for a discussion of TCP ...
... broadcasting,
see [11].) Even though unreliable and limited in length, datagram
broadcasts are quite useful [1 ...
... broadcast on the local IP net: A
datagrams is destined for a specific IP host, but the sending
...
... IP
layer is not involved, except that a host should discard
datagrams not meant for it without becoming flustered (i.e.,
printing an error message).
...
... This case is the same as local-network broadcasts; the datagram
is routed by normal mechanisms until it reaches a gateway
...
... broadcasting, a host determines if it is the
recipient of a datagram by matching the destination address against
all of its IP addresses ...
... broadcast need only
specify the appropriate destination address and send the datagram as
usual. Any sophisticated algorithms need only reside in gateways ...
... When a gateway receives a local broadcast datagram, there are several
things it might have to do with it. The situation is unambiguous,
but without due care it is possible to create ...
...
The appropriate action to take on receipt of a broadcast datagram
depends on several things: the subnet it was received on, the
...
... The primary rule for avoiding loops is "never broadcast a
datagram on the hardware network it was received on". It is not
...
... hardware network it was received on". It is not
sufficient simply to avoid repeating datagrams that a gateway
has heard from itself; this still allows loops if there are
...
... gateway should consider itself to be a destination of the
datagram (for example, it might be a routing table update.)
...
... source address of an ICMP Information
Request datagram. However, as a notational convention, we refer to
networks ...
... address as a
broadcast, then a datagram sent with a Time-To-Live of T could
potentially give rise to T**N spurious re-broadcasts ...