Session Initiation Proposal Investigation (sipping) In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at: Additional SIPPING Web Page Last Modified: 2009-03-30 Additional information is available at tools.ietf.org/wg/sipping Chair(s):Real-time Applications and Infrastructure Area Director(s):Real-time Applications and Infrastructure Area Advisor:Secretary(ies):Mailing Lists:General Discussion: sipping@ietf.orgTo Subscribe: sipping-request@ietf.org In Body: (un)subscribe Archive: http://www.ietf.org/mail-archive/web/sipping/index.html Description of Working Group:The Session Initiation Protocol Project INvestiGation (SIPPING)working group is chartered to document the use of SIP for several applications related to telephony and multimedia, and to develop requirements for extensions to SIP needed for those applications. Such requirements will be referred to the SIP working group for development of any new SIP method, header, or option-tag as described in Change Policy for SIP (RFC 3467). Guiding principles for the performance of SIPPING's work will include: 1. Documenting the requirements of specific chartered tasks. 2. Documenting the usage of SIP to solve real problems that need to be solved in a standardized way. Examples of important topics identified are the session policy architecture, allowing network entities to convey policy into an User Agent's activity; requirements analysis for session border controllers to determine how best such devices can operate with SIP usage; guidance on IPv4-IPv6 co-existence support by SIP and SIP-supported media; and inclusion of real-time text conversation (ToIP), service invocations benefitting hearing and speech impaired users, and other SIP equal access services as requirements are proposed. 3. Looking for commonalities among the chartered tasks and ongoing SIP-related development, as commonalities may indicate for general, reusable functionality in SIP. 4. Describing the requirements for any extension determined to pass there hurdles, and handing the development task to the SIP WG. 5. Developing procedures and requirements for configuration and delivery of SIP User Profiles Besides performing needed specification of several applications of SIP, SIPPING can be seen as also working out use cases that clarify the role of SIP in the Internet, and help to ensure that Occam's razor is appropriately applied to SIP usage. The security of all the deliverables will be of special importance. The technology for security will be keyed from the SIP Security specification within RFC 3261, and additional SIP specifications as they apply. Goals and Milestones:
Internet-Drafts:A Call Control and Multi-party usage framework for the Session Initiation Protocol (SIP) (101909 bytes)Session Initiation Protocol Call Control - Transfer (119753 bytes) A Framework for Session Initiation Protocol User Agent Profile Delivery (130244 bytes) A Framework for Application Interaction in the Session Initiation Protocol (SIP) (94672 bytes) IPv6 Transition in the Session Initiation Protocol (SIP) (34388 bytes) Registration Event Package Extension for Session Initiation Protocol (SIP) Globally Routable User Agent URIs (GRUUs) (32275 bytes) A User Agent Profile Data Set for Media Policy (68498 bytes) RTCP-XR Summary (84123 bytes) A Session Initiation Protocol (SIP) Event Package for Session-Specific Session Policies. (44509 bytes) Requirements from SIP (Session Initiation Protocol) Session Border Control Deployments (60065 bytes) SIP (Session Initiation Protocol) Usage of the Offer/Answer Model (59564 bytes) Identification of Communications Services in the Session Initiation Protocol (SIP) (61751 bytes) Scaling Requirements for Presence in SIP/SIMPLE (17876 bytes) Updates to Asserted Identity in the Session Initiation Protocol (SIP) (25500 bytes) A Schema and Guidelines for Defining Session Initiation Protocol User Agent Profile Datasets (75767 bytes) Design Considerations for Session Initiation Protocol (SIP) Overload Control (51205 bytes) Request For Comments:User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired individuals (RFC 3351) (33894 bytes)Session Initiation Protocol (SIP) for Telephones (SIP-T): Context and Architectures (RFC 3372) (49893 bytes) Short Term Requirements for Network Asserted Identity (RFC 3324) (21964 bytes) Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping (RFC 3398) (166207 bytes) The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp) (RFC 3485) (80195 bytes) updated by RFC 4896 Mapping of of Integrated Services Digital Network (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP) (RFC 3578) (26667 bytes) Session Initiation Protocol Basic Call Flow Examples (RFC 3665) (163159 bytes) Session Initiation Protocol PSTN Call Flows (RFC 3666) (200478 bytes) Authentication, Authorization and Accounting Requirements for the Session Initiation Protocol (RFC 3702) (31243 bytes) A Session Initiation Protocol (SIP) Event Package for Registrations (RFC 3680) (56306 bytes) Best Current Practices for Third Party Call Control in the Session Initiation Protocol (RFC 3725) (77308 bytes) Using E.164 numbers with the Session Initiation Protocol (SIP) (RFC 3824) (36535 bytes) A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP) (RFC 3842) (36877 bytes) The Early Session Disposition Type for the Session Initiation Protocol (SIP) (RFC 3959) (22160 bytes) Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) (RFC 3960) (31692 bytes) Input 3rd-Generation Partnership Project (3GPP) Release 5 requirements on the Session Initiation Protocol (SIP) (RFC 4083) (80203 bytes) Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc) (RFC 4117) (37951 bytes) Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP) (RFC 4189) (25842 bytes) An INVITE-Inititiated Dialog Event Package for the Session Initiation Protocol (SIP) (RFC 4235) (83268 bytes) High-Level Requirements for Tightly Coupled SIP Conferencing (RFC 4245) (24415 bytes) A Framework for Conferencing with the Session Initiation Protocol (SIP) (RFC 4353) (67405 bytes) Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events (RFC 4411) (49260 bytes) Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP) (RFC 4453) (16833 bytes) Interworking between the Session Initiation Protocol (SIP) and QSIG (RFC 4497) (149992 bytes) Session Initiation Protocol (SIP) Torture Test Messages (RFC 4475) (93264 bytes) Internet Assigned Number Authority (IANA) Registration of the Message Media Feature Tag (RFC 4569) (6920 bytes) Guidelines for Usage of the Session Initiation Protocol (SIP) Caller Preferences Extension (RFC 4596) (82954 bytes) Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents (RFC 4579) (96506 bytes) A Session Initiation Protocol (SIP) Event Package for Conference State (RFC 4575) (97484 bytes) Trait-based Authorization Requirements for the Session Initiation Protocol (SIP) (RFC 4484) (37169 bytes) A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML) (RFC 4730) (120186 bytes) Multiple Dialog Usages in the Session Initiation Protocol (RFC 5057) (62654 bytes) The Session Initiation Protocol (SIP) and Spam (RFC 5039) (73341 bytes) Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6) (RFC 5118) (31829 bytes) Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP) (RFC 5194) (68636 bytes) Session Initiation Protocol Service Examples (RFC 5359) (289446 bytes) The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model (RFC 5370) (23184 bytes) Framework for Transcoding with the Session Initiation Protocol (SIP) (RFC 5369) (20428 bytes) Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists (RFC 5364) (40497 bytes) Framework and Security Considerations for Session Initiation Protocol (SIP) Uniform Resource Identifier (URI)-List Services (RFC 5363) (22912 bytes) The Session Initiation Protocol (SIP) Pending Additions Event Package (RFC 5362) (32137 bytes) A Document Format for Requesting Consent (RFC 5361) (28256 bytes) Requirements for Management of Overload in the Session Initiation Protocol (RFC 5390) (32851 bytes) Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP) (RFC 5407) (120005 bytes) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||