1 / 6

draft-aoki-simple-interdomain-bcp-01

This draft provides high-level BCPs for operating large IM communities, focusing on scalability and accuracy. It outlines minimum profiles for SIMPLE implementations and techniques for optimizing presence and IM information. The document explains interdomain issues in SIP/SIMPLE, detailing efficiencies like dialog multiplexing and response caching. Recommendations cover timeouts, compression, and security practices for IM protocols.

luisdow
Download Presentation

draft-aoki-simple-interdomain-bcp-01

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. draft-aoki-simple-interdomain-bcp-01 Edwin Aoki, AOL Avshalom Houri, IBM Tim Rang, Microsoft

  2. Purpose of this Draft • Provide a catalog of high-level BCPs derived from experience in operating large enterprise and consumer IM communities • Two categories of recommendations in this draft • A recommended minimum profile for SIMPLE implementations to satisfy expectations of “real world” users • E.g., implementation of “activity” from RPID draft • Techniques that can assist in scalability and accuracy of presence/IM info in large and very large deployments

  3. What is an “Interdomain” Issue? • SIP/SIMPLE is essentially a point to point (user to user) protocol • But, these users often exist within an administrative domain • Enterprises • Consumer services • ISPs or mobile access providers • By recognizing these domains, we can achieve efficiencies and optimizations • However, many of these BCPs can apply to the point to point case as well.

  4. What Kinds of Efficiencies? • Multiplexing of multiple dialogs over the connection between edge proxies • Optimizations that allow a proxy to cache certain kinds of responses on behalf of identifiers in its namespace • Recommendations on timeouts, refreshes, compression and security usage and use of Page Mode and Session Mode (MSRP) for IMs

  5. History of the Draft/Change Log • Draft originated asdraft-levin-simple-interdomain-reqs-03.txt • Separated provisioning and scalability requirements into requirements drafts (draft-houri-speermint-rtc-provisioning-reqs-00 and draft-rang-simple-problem-statement-00) • Removed discussion of non-MSRP session-based protocols • Simplified language and made more consistent with a BCP • Note: current draft was submitted with an incorrect expiry date; this will be fixed after the moratorium

  6. Next Steps • Does the WG see utility in documenting this kind of information? • Is this the right information to cover? • Are there others with operational experience to contribute?

More Related