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
FLUTE
Click on the red underlined text to get to the source
...
This document defines FLUTE version 1, a protocol for unidirectional
delivery of files over the Internet ...
... transport of objects is not enough, however. The
end systems need to know what the objects actually represent. This
document specifies a technique called FLUTE - a mechanism for
signaling and mapping the properties of files to concepts of ALC ...
... describes the use of congestion control and channels with FLUTE.
Section 5 defines how the Forward Error Correction (FEC ...
... security considerations regarding file delivery with FLUTE. Last,
there are two informative appendices. The first appendix describes
an envisioned receiver ...
... delivery sessions of several seconds or more. For
instance, FLUTE could be used for the delivery of large software
updates to many hosts ...
...
Massive scalability is a primary design goal for FLUTE. IP multicast
is inherently massively scalable, but the best effort service ...
... ALC building block [2] and to any additional building blocks
that FLUTE uses also apply to FLUTE.
...
... multicast file delivery.
FLUTE requires connectivity between a sender and receivers but does
...
... not require connectivity from receivers to a sender. FLUTE
inherently works with all types of networks, including LANs ...
... IPv6 as no part of the packet
is IP version specific. FLUTE works with both multicast models:
Any-Source Multicast ...
... 15].
FLUTE is applicable for both Internet use, with a suitable congestion
control building block, and provisioned/controlled systems, such as
...
... networks are not amenable to some congestion control protocols
that could be used with FLUTE. In particular, for a satellite or
wireless network ...
... reliability using the FEC building block. This will
reduce the error rate as seen by applications. However, FLUTE does
not provide a method for senders ...
... transport object size is delivered
to receivers as part of the FLUTE protocol.
* Security properties ...
... * The TOI field MUST be included in ALC packets sent within a FLUTE
session, with the exception that ALC ...
... FEC Encoding ID 0 is the default for
FLUTE, this implies that Source Block Number and Encoding Symbol
ID lengths both default to 16 bits ...
... FDT Instance with the same ID. It would be reasonable for
FLUTE Senders to only construct and deliver FDT Instances with
...
... FDT Instance IDs resulting in larger increments than one) is
outside the scope of this specification and left to individual
implementations of FLUTE.
...
... already given in this and previous FDT Instances). For example, this
may be used to provide a complete list of files in an entire FLUTE
session (a "complete FDT ...
... channels and congestion control. There are
four scenarios FLUTE is envisioned to be applied.
(a) Use a single channel ...
... are delivered sequentially using a single channel. Thus, if the
application of FLUTE has a mandatory or critical requirement that the
...
... session. In this section, two methods are specified for FLUTE for
this purpose: the use of ALC specific LCT ...
... the EXT_FTI header extension. The following sections specify EXT_FTI
when used in FLUTE.
In FLUTE ...
...
* An indication that the session is a FLUTE session. The need to
demultiplex objects upon reception is implicit in any use of
...
... session. The need to
demultiplex objects upon reception is implicit in any use of
FLUTE, and this fulfills the ALC requirement of an indication of
...
... whether or not a session carries packets for more than one object
(all FLUTE sessions carry packets for more than one object).
...
... and held in a file which would be acquired by the receiver before the
FLUTE session begins by means of some transport protocol (such as
...
... 3] and FEC [4] also apply to FLUTE. In addition, any
security considerations that apply to any congestion control ...
... TOI 'n' can carry a Trojan Horse or some other type of virus.
It is thus STRONGLY RECOMMENDED that the FLUTE delivery service at
...
... IANA considerations. In particular, the FEC
building block used by FLUTE does require IANA registration of the
FEC ...