draft-aoki-simple-interdomain-bcp-01 - PowerPoint PPT Presentation

About This Presentation
Title:

draft-aoki-simple-interdomain-bcp-01

Description:

Provide a catalog of high-level BCPs derived from experience in operating large ... submitted with an incorrect expiry date; this will be fixed after the moratorium ... – PowerPoint PPT presentation

Number of Views:13
Avg rating:3.0/5.0
Slides: 7
Provided by: edwin3
Learn more at: https://www.ietf.org
Category:

less

Transcript and Presenter's Notes

Title: draft-aoki-simple-interdomain-bcp-01


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?
Write a Comment
User Comments (0)
About PowerShow.com