...systems.
See for example [KNS90].
...stream
See [GBT93, p. 8,] for the complete formal definitions of timed streams.
...elements
Gibbs' media elements 7#7 correspond to Husemann's data quanta 8#8 belonging to one substream 9#9.
...scenarios.
See [Ste95] for details.
...single
In newer drafts such as [SW96a], the aggregated traffic, which comprises data from a number of application sessions and which is covered by one QoS control request, is also considered as a single flow.
...flowspec.
See [RFC1363] for an alternative flow specification.
...flow.
Nevertheless, the IS architecture is not restricted only to delay-bounded services. See [SW96a] for a service specification template, and [SW96b] for general service parameters.
...service
See [SPG96] for a specification of guaranteed service conforming to [SW96a].
...service
See [Wro96b] for a specification of controlled-load service conforming to [SW96a].
...RSVP
See Section gif and Appendix gif for a description of RSVP.
...loss.
To tolerate n consecutive packet losses, the time-out interval must be set to 34#34 times the refresh period.
...format
See Appendix gif for RSVP's object construction rules.
...classes:
See Appendix gif for the format definition of these classes.
...types
See Appendix gif for a list of all RSVP message types object classes.
...session
A session is defined to be the collection of all data flows that are sent to the same destination by means of the same transport-layer protocol.
...(OPWA).
See [SB95] for a conceptual description of OPWA.
...example.
The ISI RSVP implementation is available at ftp://ftp.isi.edu/rsvp/release/.
...groups
The term is misleading: it is the address, not the membership of the group, that is permanent.
...addresses.
Permanent group addresses are published in the ''Internet Assigned Numbers'', see [RFC1700].
...protocols
Such as the Distance Vector Multicast Routing Protocol (DVMRP), see [RFC1075].
...IP
See [RFC1577].
...diminishes
For example in a video conference, if an MPEG I-frame got lost, the following B- and P-frames would make no sense to the receiver; but by the time the lost I-frame got retransmitted, it would arrive far too late for displaying. Instead, a new I-frame of the current scene, which would be too early compared to the normal MPEG frame rhythm, would be sent.
...Processing.
Integrated Layer Processing is a principle for the implementation of a protocol. Layering is nevertheless considered useful for protocol design.
...are:
See Appendix gif for the complete structure of the RTP packet header.
...packets.
See [RFC1889, A.3,] for an algorithm that determines the number of RTP packets expected and lost.
...estimation.
See [RFC1889, A.8,] for an algorithm that calculates the inter-arrival jitter.
...packets
See Appendix gif for the basic RTCP packet types and their structure.
...reports.
See gif for the structure of RTCP sender reports.
...receiver.
See gif for the structure of RTCP receiver reports.
...receivers.
See gif for the structure of RTCP source description packets.
...anymore.
See gif for the structure of RTCP bye packets.
...share.
See [RFC1889, A.7,] for an algorithm computing the RTCP transmission interval in dependence on the session size and on the RTCP target bandwidth share.
...network:
The usage of the jitter information is subject to further work.
...RTP.
As mentioned in Section gif, see for instance [Par96].
...top.
Figure gif is adapted from [Tan96, p. 754,] with the addition of the RTP layer.
...objects.
The chunk objects of Husemann's video-on-demand case study [Hus96, Section 5.4,] offer a display method, which synchronizes a chunk object with related chunk objects before it displays the object's content on the hardware device associated with the calling player object.
...project
See [HEF+91] for the initial description of the PM project in general and the PM object model in particular.
...level,
Namely, the chunks might have been generated in the network subsystem or some hardware device driver.
...class
The PM model uses the more general notion of shapes instead of classes, see [Hau95].
...ALCAID
See [Hau95] for a description of ALCAID.
...Husemann
See Section 3.5 and Section 4.5 of [Hus96].
...Gibbs
See Section gif above.
...invocations.
For reasons of simplicity, only one LocalSource and one RemoteSource are shown in Figure gif. However, the number of LocalSources or RemoteSources that participate in a session is not limited conceptually.
...implementation
On hosts belonging to IMMD network, the Java source code can be found in the directory /proj/i4pm/MultiMedia/javasrc/.
...timestamp
See [RFC1305] for the specification of Network Time Protocol (NTP).
...representation.
See [RFC1832] for a thorough description of XDR.

tspeuker@cip.informatik.uni-erlangen.de