3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W
multicast
Click on the red underlined text to get to the source
... The Negative-acknowledgment (NACK) Oriented Reliable Multicast (NORM)
protocol is designed to provide reliable transport ...
... sender(s) to a group of receivers over an IP multicast
network. The primary design goals of NORM ...
... NORM protocol design provides support for
distributed multicast session participation with minimal coordination
among senders and receivers ...
... senders throughout the lifetime of a reliable
multicast session. NORM is designed to be self-adapting to a wide
range of dynamic network conditions ...
...
This memo contains part of the definitions necessary to fully specify
a Reliable Multicast Transport protocol in accordance with RFC 2357.
As per RFC 2357 ...
... 2357.
As per RFC 2357, the use of any reliable multicast protocol in the
Internet requires an adequate congestion control scheme ...
...
While waiting for such a scheme to be available, or for an existing
scheme to be proven adequate, the Reliable Multicast Transport
working group (RMT ...
... host port numbers. Generally, the
participants exchange packets using an IP multicast group address,
but unicast ...
... unicast transport may also be established or applied as an
adjunct to multicast delivery. In the case of multicast, the
...
... adjunct to multicast delivery. In the case of multicast, the
participating NormNodes will communicate using a common IP multicast
...
... delivery. In the case of multicast, the
participating NormNodes will communicate using a common IP multicast
group address and port number ...
... These static data and file services are anticipated to be useful for
multicast-based cache applications with the ability to reliably
provide transmission of large quantities of static data. Other types
...
... objects transmitted by the sender. This readily-available "out-of-
band" data allows multicast receivers to quickly and efficiently
determine the nature of the corresponding data, file, or stream ...
... session termination, receiver synchronization, etc.) are
specified so that reliable multicast application variants may
construct different, complete bulk transfer communication models to
meet their goals.
...
... transport control
mechanisms are specified for use by applications to form complete
reliable multicast solutions for different purposes.
...
... forward error correction (FEC)
techniques for efficient multicast repair and optional proactive
transmission robustness [10]. FEC ...
... 10]. FEC-based repair can be used to
greatly reduce the quantity of reliable multicast repair requests and
repair transmissions [11] in a NACK ...
... network topology over which it is operating.
Feedback messages can be either multicast to the group at large or
sent via unicast ...
... NORM protocol SHALL be capable of operating in an end-to-end
fashion with no assistance from intermediate systems beyond basic IP
multicast group management, routing ...
... NORM are principally applicable to "flat"
end-to-end IP multicast topologies, they could also be applied in the
sub-levels of hierarchical (e.g., tree ...
... topologies, they could also be applied in the
sub-levels of hierarchical (e.g., tree-based) multicast distribution
if so desired. NORM can make use of reciprocal (among senders ...
... receivers) multicast communication under the Any-Source Multicast
(ASM) model defined in RFC 1112std5 ...
... 3], but SHALL also be capable of
scalable operation in asymmetric topologies such as Source Specific
Multicast (SSM) [14] where there may only be unicast ...
... transmission overhead. This option may be sensible for certain
network conditions and can allow for robust, asymmetric multicast
(e.g., unidirectional routing ...
... FEC-encoded data content. NORM_INFO may
serve special purposes for some bulk transfer, reliable multicast
applications where receivers join ...
... transmission rate set for
each participant by the application. This can be used to limit the
quantity of multicast data transmitted by the group. When NORM's
...
... The operation of the NORM protocol is based primarily upon the
concepts presented in the Nack-Oriented Reliable Multicast (NORM)
Building Block document [4 ...
... architecture and the data transmission, repair, and feedback
strategies discussed in that document. Additional reliable multicast
building blocks are applied in creating the full NORM protocol
...
... congestion
control mechanism (NORM-CC) based on the TCP-Friendly Multicast
Congestion Control (TFMCC) scheme described in [19].
...
... NORM are designed to provide some
measure of general purpose utility, it is important to emphasize the
understanding that "no one size fits all" in the reliable multicast
transport arena. There are numerous engineering tradeoffs involved
in reliable multicast transport design and this requires an increased
...
... understanding that "no one size fits all" in the reliable multicast
transport arena. There are numerous engineering tradeoffs involved
in reliable multicast transport design and this requires an increased
awareness of application and network architecture considerations.
...
... requirements. The NORM protocol and its mechanisms MAY be applied in
multicast applications outside of bulk data transfer, but there is an
assumed model of bulk transfer transport service ...
... 4] and [5], completely specifies a
working reliable multicast transport protocol that conforms to the
requirements described in RFC 2357 ...
... | | to control/suppress excessive receiver |
| | feedback in asymmetric multicast topologies. |
+--------------------+-----------------------------------------------+
...
... methodologies for assignment and potential collision resolution of
node identifiers within a multicast session need to be considered.
For example, the "source identifier" mechanism defined in the Real-
...
... group size estimate of
10,000 ("gsize" = 0x4) is recommended for general purpose reliable
multicast applications using the NORM protocol.
...
... repair. This flag could possibly be used by intermediate systems
implementing functionality to control sub-casting of repair content
to different legs of a reliable multicast topology with disparate
repair needs. NORM ...
... (i.e., do not use a very large coding block size if frequent flushing
occurs). For example, a reliable multicast application transmitting
an on-going series of intermittent, relatively small messaging
...
... congestion control scheme (NORM-CC), based on the TCP-Friendly
Multicast Congestion Control (TFMCC) scheme of [19] is described in
...
... sender. This can
be useful instrumentation for complex or experimental multicast
routing environments.
The "send_time" field is a timestamp ...
... congestion control is enabled) messages via
unicast transmission instead of multicast. By "echoing" this
information to the receiver set, suppression of feedback can be
...
... messages. If another congestion control technique (e.g., Pragmatic
General Multicast Congestion Control (PGMCC) [20]) is used within a
...
... receivers. This message is
used in providing a lightweight positive acknowledgment mechanism
that is OPTIONAL for use by the reliable multicast application. A
range of acknowledgment request types is provided for use at the
...
... and congestion-control operation is described in Sections 5.5.1 and
5.5.2, respectively. However, some multicast applications may
benefit from some limited form of positive acknowledgment for certain
functions. A simple, scalable positive acknowledgment scheme is
...
... additional message formats are defined for general purpose in
NORM multicast sessions whether the participant is acting as a sender
...
... present. Note, in some applications (e.g., web push), this
indication may come out-of-band with respect to the multicast session
via other means. As noted, the periodic transmission of NORM_CMD ...
... network operations. The receivers
participating in the multicast group provide feedback to the sender
as needed. When the sender ...
... constraints to limit the
ability of receivers to disrupt reliable multicast performance by
joining, leaving, and rejoining the group ...
... ancillary information. The backoff factor "Ksender"
MUST be greater than one to provide for effective feedback
suppression. A value of K = 4 is RECOMMENDED for the Any Source
Multicast (ASM) model while a value of K = 6 is RECOMMENDED for
Single Source Multicast ...
... Any Source
Multicast (ASM) model while a value of K = 6 is RECOMMENDED for
Single Source Multicast (SSM) operation.
...
... FEC code
is used, the need for explicit repair will be an exception, and the
fulfillment of reliable multicast can be accomplished quite
efficiently. However, the ability to resort to explicit repair
allows the protocol to be reliable under even very extreme
...
... performance. If such systems are properly positioned with respect to
reciprocal reverse-path multicast routing, they need to sub-cast only
a sufficient count of non-explicit parity repairs to satisfy a
multicast routing ...
... multicast routing, they need to sub-cast only
a sufficient count of non-explicit parity repairs to satisfy a
multicast routing sub-tree's erasure filling needs for a given FEC
...
... receiver set since the
receiver set is not directly sharing their repair needs via multicast
communication. The NORM_CMD ...
... communication. The NORM_CMD(REPAIR_ADV) message is multicast to the
receiver set by the sender ...
... approach described here are an adaptation of the equation-based TCP-
Friendly Multicast Congestion Control (TFMCC) approach described in
...
... NORM implementation is adapted
to use another IETF-sanctioned reliable multicast congestion control
mechanism (e.g., PGMCC [20 ...
... NORM protocol message set may
alternatively be used to support a window-based multicast congestion
control scheme such as PGMCC. The details of that alternative may be
described separately or in a future revision of this document. In
...
... packet loss estimates and RTTs to identify the congestion
control bottleneck path(s) within the multicast topology and adjust
the sender ...
... may be done to collect some estimation of the current state of the
multicast topology with respect to group and individual RTT ...
... sender and group.
This message may be multicast to the group for most effective
suppression in ASM ...
... vulnerabilities that any IP and IP multicast protocol implementation
may be generally subject to, the NACK ...
... tool for the reliable
data transfer over generic IP multicast services. It is not the
intention of the authors to suggest it is suitable for supporting
...
... services. It is not the
intention of the authors to suggest it is suitable for supporting
all envisioned multicast reliability requirements. NORM ...
...
simple and flexible framework for multicast applications with a
degree of concern for network traffic implosion and protocol overhead ...
... FEC-based
repairing improve protocol performance in some multicast scenarios.
A sender-only repair approach often makes additional engineering
...
... service exists. Asymmetric
architectures supporting multicast delivery are likely to make up an
important portion of the future Internet ...
... Kermode, R. and L. Vicisano, "Author Guidelines for Reliable Multicast Transport (RMT) Building Blocks and Protocol Instantiation documents", RFC 3269, April 2002. ...
... Adamson, B., Bormann, C., Handley, M., and J. Macker, "Negative-Acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Building Blocks", RFC 3941exp, November 2004. ...
... Comparison of Sender- Initiated and Receiver-Initiated Reliable Multicast Protocols", In Proc. INFOCOM, San Francisco CA, October 1993. ...
... Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M., and J. Crowcroft, "The Use of Forward Error Correction (FEC) in Reliable Multicast", RFC 3453, December 2002. ...
... Macker, J. and B. Adamson, "The Multicast Dissemination Protocol (MDP) Toolkit", Proc. IEEE MILCOM 99, October 1999. ...
... Nonnenmacher, J. and E. Biersack, "Optimal Multicast Feedback", Proc. IEEE INFOCOMM, p. 964, March/April 1998. ...
... J. Macker, B. Adamson, "Quantitative Prediction of Nack Oriented Reliable Multicast (NORM) Feedback", Proc. IEEE MILCOM 2002, October 2002. ...
... H.W. Holbrook, "A Channel Model for Multicast", Ph.D. Dissertation, Stanford University, Department of Computer Science, Stanford, California, August 2001. ...
... D. Gossink, J. Macker, "Reliable Multicast and Integrated Parity Retransmission with Channel Estimation", IEEE ...
... Whetten, B., Vicisano, L., Kermode, R., Handley, M., Floyd, S., and M. Luby, "Reliable Multicast Transport Building Blocks for One-to-Many Bulk-Data Transfer", RFC 3048, January 2001. ...
... Mankin, A., Romanow, A., Bradner, S., and V. Paxson, "IETF Criteria for Evaluating Reliable Multicast Transport and Application Protocols", RFC 2357, June 1998. ...
... J. Widmer and M. Handley, "Extending Equation-Based Congestion Control to Multicast Applications", Proc ACM SIGCOMM 2001, San Diego, August 2001. ...
... L. Rizzo, "pgmcc: A TCP-Friendly Single-Rate Multicast Congestion Control Scheme", Proc ACM SIGCOMM 2000, Stockholm, August 2000. ...