[Sipping] I-D Action:draft-ietf-sipping-sbc-funcs-04.txt

Internet-Drafts@ietf.org Fri, 21 December 2007 10:40 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5fIx-0004xL-1t; Fri, 21 Dec 2007 05:40:35 -0500
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1J5fIv-0004x4-4t for sipping-confirm+ok@megatron.ietf.org; Fri, 21 Dec 2007 05:40:33 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5fIu-0004wt-Pn; Fri, 21 Dec 2007 05:40:32 -0500
Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J5fIu-0005a6-B5; Fri, 21 Dec 2007 05:40:32 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 4504E2AC96; Fri, 21 Dec 2007 10:40:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1J5fIQ-0001MO-1P; Fri, 21 Dec 2007 05:40:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1J5fIQ-0001MO-1P@stiedprstage1.ietf.org>
Date: Fri, 21 Dec 2007 05:40:02 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: sipping@ietf.org
Subject: [Sipping] I-D Action:draft-ietf-sipping-sbc-funcs-04.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.


	Title           : Requirements from SIP (Session Initiation Protocol) Session Border Control Deployments
	Author(s)       : J. Hautakorpi, et al.
	Filename        : draft-ietf-sipping-sbc-funcs-04.txt
	Pages           : 24
	Date            : 2007-12-21

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 additional standards work is required.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-sbc-funcs-04.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-sipping-sbc-funcs-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-sbc-funcs-04.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-sipping-sbc-funcs-04.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-sipping-sbc-funcs-04.txt>
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP