Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Bandwidth reservation protocol

Mar 29, 2018 11:22AM PDT

Does RSVP reservation protocol allow retaining the reserved path by the host for later use? For example, a host A reserves a path for communicating with host B. After communication is complete, can the path be retained for some duration to avoid signaling (related to reservation) if the same host A needs to communicate with host B or any other host in the same network as host B?

Discussion is locked

- Collapse -
Answer
I'm going with no. Why?
Mar 29, 2018 11:30AM PDT

Because I've seen routers and such claim this but it fails in reality.

Back to the drawing board? Or the maker if this fails to work.

- Collapse -
Please suggest the routers which claim this
Mar 29, 2018 11:41AM PDT

Thank you for your quick response!

I am looking for such an implementation for further research. From your reply, I understand that there could be routers which claim this implementation. Could you please share some references in this regard, which mention presence of such an implementation?
Or are their any RFCs which define such a feature?

Your help is highly appreciated.

Best regards,
John

- Collapse -
Sorry that's too much work.
Mar 29, 2018 11:48AM PDT

I'm going to stick with prior routers didn't do so well with this feature. newer routers have new tricks and you should test it out.

That said when you get out of the consumer routers like Cisco then you're all good again. Juniper, Cisco, the names can't get away with this hodgepodge of does it really work or not.

http://docwiki.cisco.com/wiki/Resource_Reservation_Protocol for example and other docs do not seem to mention that this reservation has a long life span. So again no to your question.