1 - 3 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - R - S - T - U - V - W - X
network
Click on the red underlined text to get to the source
... congestion status
of the network. It is also suitable for the basic transport of
metadata, for example SDP ...
...
Some networks are not amenable to some congestion control protocols
that could be used with FLUTE ...
... FLUTE. In particular, for a satellite or
wireless network, there may be no mechanism for receivers to
effectively reduce their reception rate ...
... session. As an example, the sender may be behind
a Network Address Translation (NAT) device that temporarily assigns
...
... sender may send its original packets using IPv6,
but some portions of the network may not be IPv6 capable and thus
there may be an IPv6 ...
... receivers
in the IPv4 portion of the network will receive packets containing
the IPv4 address, and thus the TSI ...
... integer fields are carried in
"big-endian" or "network order" format, that is, most significant
byte (octet) first. As defined in [2], all ALC ...
... FDT Instance
starts. However, due to unexpected network conditions, packets for
the FDT Instances MAY be interleaved ...
... congestion control supplied by ALC,
but only when in a controlled network environment where flow/
congestion control ...
... congestion control supplied by ALC,
but only when in a controlled network environment where flow/
congestion control ...
... is because in this case, even when there is no packet loss in the
network, a lower rate receiver will not receive all packets sent
for an FDT Instance ...
... multicast stream,
thereby potentially adversely affecting network elements and
receivers downstream ...
... downstream of the attack, and much less significantly the
rest of the network and other receivers. Thus, it is also
RECOMMENDED that packet level authentication ...
... multiple rate congestion control building block may affect health of
the network in the path between the sender and the receiver, and may
...
... higher rate than they are capable of, thereby disrupting traffic in
portions of the network. To avoid these problems, it is RECOMMENDED
that measures be taken to prevent receivers from accepting incorrect
...
... Mills, D., "Network Time Protocol (Version 3) Specification, Implementation", RFC 1305draft, March 1992. ...
... Perrig, A., Canetti, R., Song, D., and J. Tygar, "Efficient and Secure Source Authentication for Multicast, Network and Distributed System Security Symposium, NDSS 2001, pp. 35-46.", February 2001. ...