Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Resource Reservation Protocol
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Main attributes== {{unsourced section|date=October 2019}} #RSVP requests resources for [[Simplex communication|simplex]] flows: a traffic stream in only one direction from sender to one or more receivers.<ref>{{Cite web |date=2020-01-16 |title=Resource Reservation Protocol in Real-time Systems |url=https://www.geeksforgeeks.org/resource-reservation-protocol-in-real-time-systems/ |access-date=2025-01-23 |website=GeeksforGeeks |language=en-US}}</ref> #RSVP is not a routing protocol but works with current and future routing protocols. #RSVP is receiver oriented in that the receiver of a data flow initiates and maintains the resource reservation for that flow. #RSVP maintains [[soft state (computer science)|soft state]] (the reservation at each node needs a periodic refresh) of the host and routers' resource reservations, hence supporting dynamic automatic adaptation to network changes. #RSVP provides several reservation styles (a set of reservation options) and allows for future styles to be added in protocol revisions to fit varied applications. #RSVP transports and maintains traffic and policy control parameters that are opaque to RSVP.{{elucidate|date=October 2019}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)