1 / 10

RSVP Resource Sharing Remote Identification Association

This draft proposes an extension to define a new association type, "Resource Sharing Remote Identification," for RSVP resource sharing. It introduces a method for the sender to convey crucial information to identify an upstream-initiated resource sharing to the receiver, useful in scenarios where the receiver lacks prior knowledge. The association rule specifies that this does not create any association across path states. This draft aims to address challenges in RSVP flows with different SESSION objects sharing resources, explaining its importance through use cases like Symmetric NAT and VoIP call sharing. The proposed solution suggests separating resource sharing from the SESSION object to enable sharing between different calls and reservations, particularly beneficial in diverse destination scenarios.

dcroy
Download Presentation

RSVP Resource Sharing Remote Identification Association

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RSVP Resource Sharing Remote Identification Association draft-narayanan-tsvwg-rsvp-resource-sharing-02 Francois Le Faucheur Ashok Narayanan Subha Dhesikan IETF 77

  2. History berger-ccamp-assoc-info-00 narayanan-tsvwg-rsvp-resource-sharing-01 • Non-GMPLS “Resource Sharing” Association • Upstream Association • Extended Association ID • ASSOCIATION Object as defined in RFC 4872 and RFC 4873 IETF 76 • Resource Sharing Remote Identification Association narayanan-tsvwg-rsvp-resource-sharing-02 berger-ccamp-assoc-info-01 • Resource Sharing Remote Identification Association • ASSOCIATION Object as defined in RFC 4872 and RFC 4873 • Non-GMPLS “Resource Sharing” Association • Upstream Association • Extended Association ID IETF 77

  3. Summary • Extension to draft-berger-ccamp-assoc-info • Standards Track • defines a new association type called "Resource Sharing Remote Identification"

  4. Resource Sharing Remote Identification association • can be used by the sender to convey to the receiver information that can then be used by the receiver to identify an upstream initiated resource sharing • useful in upstream initiated resource sharing applications where the identification of the resource sharing association is not known a priori by the receiver, and instead is known by the sender • type-specific association rule: The Resource Sharing Remote Identification association does not create any association across Path states.

  5. Resource Sharing Remote Identification association Resv(RS, ID=S/100) Path (RSRID, ID=S/100) Receiver1 Cloud of RSVP Routers Sender Receiver2 Path (RSRIS, ID=S/100) Resv(RS, ID=S/100) Resource Sharing across the two reservations RSRID = “Resource Sharing Remote Identification” association RS= “Resource Sharing” association ID= Association Identification

  6. Next Step • Please review

  7. Backup Slides

  8. Recap of problem • Currently RSVP flows with different SESSION objects cannot share resources • There are some use cases where this is important • Symmetric NAT • VoIP call sharing • Proposed solution: separate resource sharing from SESSION object

  9. Problem: VoIP features • Sharing bandwidth between calls currently in call-waiting • Shared calls between shared-line extensions at different locations • Sharing not possible in RSVP for reservations going to different {L3,L4} destinations A Share? B C

  10. Problem: Symmetric NAT • Unidirectional flows to the same destination, traversing symmetric NAT • NAT issues different destination ports to the different senders • Sharing not possible in RSVP for reservations going to different {L3,L4} destinations A Symmetric NAT Share? B C

More Related