50 likes | 60 Views
Explore issues in RSVP-TE and how to improve transport layer for reliable messaging. Learn from RSVP, use multiple protocols, and aim for simplicity and flexibility.
E N D
RSVP Transport Issues Ping Pan Henning Schulzrinne
Issues • Reliable Messaging: • Reliable delivery & soft-state. • Staged refresh timers (RFC2961). • At the end, very TCP-like. • Message Packing • One session per RSVP message. • The size does not matter…. It is the message count that kills the CPU. • Message Bundling (RFC2961).
Issues (cont.) • RSVP MTU • Cannot handle fragments. • Not an issue in RSVP-TE. • In e2e, message size may increase due to security overhead. • RSVP-TE vs. real-time applications • RSVP-TE does not have scaling problems. • Always enable RFC2961 • Controlled triggered messages • Real-time applications may have a problem.
Where do we go? • RSVP-TE: no thanks. • Already deployed RFC2961. • 50,000+ sessions per router. • Other applications: • Transport layer is an concern. • Recommendation on transport layer: • Make it flexible. • Make it TCP-like, • … and make it simple.
What about RSVP • Learn from RSVP: • Application-neutral. • Multiple transport protocols: • UDP and raw mode. • Change/swap the transport layer. • Re-use the original protocol? • Re-define a new signaling protocol?