RFC 5626 on Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org Fri, 23 October 2009 23:20 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 8A4833A6839; Fri, 23 Oct 2009 16:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.922
X-Spam-Status: No, score=-16.922 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id WVu2DxzcLblc; Fri, 23 Oct 2009 16:20:27 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id AAF333A67DA; Fri, 23 Oct 2009 16:20:27 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 660243513C8; Fri, 23 Oct 2009 16:17:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5626 on Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
From: rfc-editor@rfc-editor.org
Message-Id: <20091023231755.660243513C8@bosco.isi.edu>
Date: Fri, 23 Oct 2009 16:17:55 -0700
Cc: sip@ietf.org, 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: Fri, 23 Oct 2009 23:20:28 -0000

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

        RFC 5626

        Title:      Managing Client-Initiated Connections in the 
                    Session Initiation Protocol (SIP) 
        Author:     C. Jennings, Ed.,
                    R. Mahy, Ed.,
                    F. Audet, Ed.
        Status:     Standards Track
        Date:       October 2009
        Mailbox:    fluffy@cisco.com, 
        Pages:      50
        Characters: 116344
        Updates:    RFC3261, RFC3327

        I-D Tag:    draft-ietf-sip-outbound-20.txt

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

The Session Initiation Protocol (SIP) allows proxy servers to
initiate TCP connections or to send asynchronous UDP datagrams to
User Agents in order to deliver requests.  However, in a large number
of real deployments, many practical considerations, such as the
existence of firewalls and Network Address Translators (NATs) or the
use of TLS with server-provided certificates, prevent servers from
connecting to User Agents in this way.  This specification defines
behaviors for User Agents, registrars, and proxy servers that allow
requests to be delivered on existing connections established by the
User Agent.  It also defines keep-alive behaviors needed to keep NAT
bindings open and specifies the usage of multiple connections from
the User Agent to its registrar.  [STANDARDS TRACK]

This document is a product of the Session Initiation Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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