Messages
There are two primary types of messages:
- Path messages (path)
- The path message is sent from the sender host along the data path and stores the path state in each node along the path.
- The path state includes the IP address of the previous node, and some data objects:
-
- sender template to describe the format of the sender data
- sender tspec to describe the traffic characteristics of the data flow
- adspec that carries advertising data (see RFC 2210 for more details).
-
- Reservation messages (resv)
- The resv message is sent from the receiver to the sender host along the reverse data path. At each node the IP destination address of the resv message will change to the address of the next node on the reverse path and the IP source address to the address of the previous node address on the reverse path.
- The resv message includes the flowspec data object that identifies the resources that the flow needs.
The data objects on RSVP messages can be transmitted in any order. For the complete list of RSVP messages and date objects see RFC 2205.
Read more about this topic: Resource Reservation Protocol
Famous quotes containing the word messages:
“Pictures are for entertainment, messages should be delivered by Western Union.”
—Samuel Goldwyn (1882–1974)
“Acknowledging separation feelings directly and sympathetically is the best way of coping with them. It is actually helpful to tell a toddler “I’ll miss you,” or “I will think of you during the day,” or “It is hard to say goodbye,” or “I can’t wait to see you at the end of the day.” These messages tell the child that he is important to the parent even when they are not together and that out of sight need not mean out of mind.”
—Alicia F. Lieberman (20th century)
“Joan: I hear voices telling me what to do. They come from God. Robert: They come from your imagination. Joan: Of course. That is how the messages of God come to us.”
—George Bernard Shaw (1856–1950)