RFC 5638 on Simple SIP Usage Scenario for Applications in the Endpoints

rfc-editor@rfc-editor.org Wed, 23 September 2009 23:41 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 3683E3A6767 for <ietf-announce@core3.amsl.com>; Wed, 23 Sep 2009 16:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.677
X-Spam-Status: No, score=-15.677 tagged_above=-999 required=5 tests=[AWL=-0.533, BAYES_00=-2.599, FRT_ADOBE2=2.455, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id L+3P4wILvRn1 for <ietf-announce@core3.amsl.com>; Wed, 23 Sep 2009 16:41:06 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id E156C3A67A6 for <ietf-announce@ietf.org>; Wed, 23 Sep 2009 16:41:05 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id DC3FB32BF61; Wed, 23 Sep 2009 16:41:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5638 on Simple SIP Usage Scenario for Applications in the Endpoints
From: rfc-editor@rfc-editor.org
Message-Id: <20090923234147.DC3FB32BF61@bosco.isi.edu>
Date: Wed, 23 Sep 2009 16:41:47 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 23:41:07 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5638

        Title:      Simple SIP Usage Scenario for 
                    Applications in the Endpoints 
        Author:     H. Sinnreich, Ed.,
                    A. Johnston, E. Shim,
                    K. Singh
        Status:     Informational
        Date:       September 2009
        Mailbox:    henrys@adobe.com, 
        Pages:      19
        Characters: 45946
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-sinnreich-sip-tools-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5638.txt

For Internet-centric usage, the number of SIP-required standards for
presence and IM and audio/video communications can be drastically
smaller than what has been published by using only the rendezvous
and session-initiation capabilities of SIP.  The simplification is
achieved by avoiding the emulation of telephony and its model of
the intelligent network.  'Simple SIP' relies on powerful computing endpoints.  Simple SIP desktop applications can be combined with rich Internet applications (RIAs).  Significant telephony features may also be implemented in the endpoints.

This approach for SIP reduces the number of SIP standards with which
to comply -- from roughly 100 currently, and still growing, to about 11.

References for NAT traversal and for security are also provided.  This memo provides information for the Internet community.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute