[Sipping] RFC 5853 on Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments
rfc-editor@rfc-editor.org Thu, 29 April 2010 23:37 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3120C3A6898; Thu, 29 Apr 2010 16:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.521
X-Spam-Level:
X-Spam-Status: No, score=-1.521 tagged_above=-999 required=5 tests=[AWL=-0.410, BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwDYch1cWEa7; Thu, 29 Apr 2010 16:37:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id A83F83A6CEA; Thu, 29 Apr 2010 16:37:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B6B7CE0809; Thu, 29 Apr 2010 16:37:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100429233700.B6B7CE0809@rfc-editor.org>
Date: Thu, 29 Apr 2010 16:37:00 -0700
Cc: sipping@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sipping] RFC 5853 on Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Apr 2010 23:37:43 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5853 Title: Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments Author: J. Hautakorpi, Ed., G. Camarillo, R. Penfield, A. Hawrylyshen, M. Bhatia Status: Informational Stream: IETF Date: April 2010 Mailbox: Jani.Hautakorpi@ericsson.com, Gonzalo.Camarillo@ericsson.com, bpenfield@acmepacket.com, alan.ietf@polyphase.ca, mbhatia@3clogic.com Pages: 26 Characters: 60476 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sipping-sbc-funcs-09.txt URL: http://www.rfc-editor.org/rfc/rfc5853.txt This document describes functions implemented in Session Initiation Protocol (SIP) intermediaries known as Session Border Controllers (SBCs). The goal of this document is to describe the commonly provided functions of SBCs. A special focus is given to those practices that are viewed to be in conflict with SIP architectural principles. This document also explores the underlying requirements of network operators that have led to the use of these functions and practices in order to identify protocol requirements and determine whether those requirements are satisfied by existing specifications or if additional standards work is required. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Session Initiation Proposal Investigation Working Group of the IETF. 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 http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist 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 Association Management Solutions, LLC