Connected: An Internet Encyclopedia
2.10 Host Model

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 2205
Up: 2. RSVP Protocol Mechanisms
Prev: 2.9 Non-RSVP Clouds
Next: 3. RSVP Functional Specification

2.10 Host Model

2.10 Host Model

Before a session can be created, the session identification (DestAddress, ProtocolId [, DstPort]) must be assigned and communicated to all the senders and receivers by some out-of-band mechanism. When an RSVP session is being set up, the following events happen at the end systems.

A receiver joins the multicast group specified by DestAddress, using IGMP.

A potential sender starts sending RSVP Path messages to the DestAddress.

A receiver application receives a Path message.

A receiver starts sending appropriate Resv messages, specifying the desired flow descriptors.

A sender application receives a Resv message.

A sender starts sending data packets.

There are several synchronization considerations.

A specific application program interface (API) for RSVP is not defined in this protocol spec, as it may be host system dependent. However, Section 3.11.1 discusses the general requirements and outlines a generic interface.

Next: 3. RSVP Functional Specification

Connected: An Internet Encyclopedia
2.10 Host Model