Print Page | Close Window

SIP related protocols

Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Beginners @ OneStopTesting
Forum Discription: New to the Club...!!! Don't Worry, We are here for you...!!! Learn the very basics of Software Testing and other pertinent Informations.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=369
Printed Date: 19Jul2025 at 7:08am


Topic: SIP related protocols
Posted By: vidhya
Subject: SIP related protocols
Date Posted: 29Mar2007 at 1:28am
SIP
It is the industry standard protocol described in http://www.ietf.org/rfc/rfc3261.txt - IETF RFC 3261 that defines a standard way for session setup, termination and media negotiation between two parties. It is widely used for VOIP (Voice-Over-IP) call signaling.
SIMPLE
SIMPLE is the Presence and Instant Messaging Extensions to SIP. It is defined by http://www.ietf.org/rfc/rfc3265.txt - IETF RFC 3265 .
SIPPING
It is an IETF working group chartered with defining conferencing extensions to SIP. SIPPING’s charter is to only define conference state event packages schema and explicitly stays out of defining the conference and media control mechanisms which is XCON’s charter. Centralized, star topology conference with the concept of a “focus” is the only topology that is in the scope of SIPPING’s work.

XCon
It is another IETF working group that is responsible for defining the Conference Control mechanisms consisting of the Conference Policy Control Protocol and Conference Media Control Protocol. It works in conjunction with SIPPING but is independent of SIPPING. One could envision using XCON mechanisms without using SIP, if necessary.


PSP

The PSP means Privacy Server Protocol.

The Privacy Server Protocol (PSP) project provides research into large-scale distributed and automated negotiations for privacy and the complementary negotiations for digital rights management. In the paper world, the resulting agreements are essentially non-disclosure agreements.

PSP is an experimental protocol meant initially to extend the P3P and APPEL protocols to
    1. bilateral and negotiated agreements between client and server using HTTP or HTTPS.
    2. agreements that have scope in time (a start and expiration),
    3. agreements that have scope over digital and non-digital interactions (including mail and phone contacts),
    4. agreements that cannot be repudiated
    5. agreements that can be indexed by the server using server-only Privacy Universal Identifiers (PUIDs). This is in contrast with the XNS initiative which is using global PUIDs.



-------------
MBA Examination papers



Print Page | Close Window