1 / 9

MSRP Relays

MSRP Relays. Rohan Mahy ( rohan@cisco.com ) Cullen Jennings (fluffy@cisco.com). Status and Changes. Document still contains inconsistencies Edited late at night with too little time

september-harrington
Download Presentation

MSRP Relays

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. MSRP Relays Rohan Mahy (rohan@cisco.com) Cullen Jennings (fluffy@cisco.com)

  2. Status and Changes Document still contains inconsistencies Edited late at night with too little time The new MSRP draft contains the changes to make the relay draft work. Tried to get MSRP relay draft fully aligned, but we missed a few spots

  3. Significant changes Response/Report Handling Addressing Use of TLS Rechunking

  4. Response/Report Handling responses to SEND requests (if appropriate) are hop-by-hop responses to AUTH requests are end-to-end REPORT requests have no responses

  5. Addressing Client can use SRV to discover its relay, but in SDP always use explicit host, transport, port Client which needs multiple relays, sends AUTH to each one from inside to out Advertise your path Get the remote path and add it to your path Relay authorizes request based on path When forwarding, Relay removes itself from To-Path and adds itself to From-Path

  6. TLS relay to relay is ALWAYS TLS with mutual authentication client to its relay is ALWAYS TLS with Digest foreign relay to client can be either TCP or TLS

  7. Rechunking Core protocol now supports chunking really well Relays can rechunk a message to be bigger or smaller if you send chunks over 2k, you have to be able to interrupt them

  8. Open Issue: Refreshing AUTHs Currently no way to refresh a URI that you got via AUTH Proposal: Client periodically sends new AUTH requests. Client can send to a specific URI in the To-Path. Need to work out details

  9. Next Steps Fix this to be consistent with base MSRP Fix this to be consistent with itself :-) What other changes are needed?

More Related