1 / 5

Scope Discussion

Scope Discussion. Seems to be a good deal of interest in moving this toward a working group If we want to work toward this, we need to have a clearly defined and narrow scope of what we are interested in doing

zona
Download Presentation

Scope Discussion

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. Scope Discussion • Seems to be a good deal of interest in moving this toward a working group • If we want to work toward this, we need to have a clearly defined and narrow scope of what we are interested in doing • Want to drive toward getting some rough consensus on what is in scope, might be in scope, might be in scope later, and most importantly of all what is not in the scope of a working group that might someday be formed in this area

  2. P2P protocols only as they apply to real time communications Usage Scenarios, requirements and architecture as they pertain to the above Development or selection of acceptable overlay network structure, algorithms and protocols with requirements exclusively for P2PSIP Security and authentication mechanisms for the overlay network. (If additional SIP auth/security work is needed, provide requirements to SIPPING) Mechanisms for interoperability between P2PSIP and client server SIP-based communications Development of a system to enable basic real time communications sessions – P2P based registration and routing Mapping of SIP URIs/resources to overlay IDs in a P2PSIP environment (such as hashing) Drive to have consensus: In scope

  3. Don’t think we have consensus • Anonymized communications • Architecture for interaction of heterogeneous overlays • Mobility of P2PSIP devices/users • Advanced features that may be different in P2PSIP (such as voicemail, transfer and many others) • Mechanisms for distributing and locating services in a P2PSIP architecture • Distributed P2P Conferencing services

  4. Possible future work • Automatic discovery and provisioning mechanisms specific to P2PSIP architectures • Abuse prevention (stopping file sharing) • Reputation management (malicious node detection) • Using P2PSIP mechanisms to locate optimal nodes for NAT traversal/media relay in P2PSIP networks (only if this work proves unique to P2PSIP) • Document to enable testing of P2PSIP networks (such as callflow documents)

  5. NOT in scope • Anything in the scope of any existing group • File sharing or general media sharing • Design of general purpose P2P overlays, algorithms and/or protocols • Exhaustive evaluation of all P2P mechanisms • Media transcoding/translation • Solving completely distributed, decentralized, server-less identity/namespace • Emergency/911 services • Legal intercept • Comparison between client-server SIP and P2P SIP

More Related