IETF Logo Mail Archive

Re: [Sipping] Draft: Functions of Current SBCs

Jonathan Rosenberg <jdrosen@cisco.com> Wed, 02 March 2005 09:30 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17259 for <sipping-web-archive@ietf.org>; Wed, 2 Mar 2005 04:30:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D6QCd-0003J7-FS for sipping-web-archive@ietf.org; Wed, 02 Mar 2005 04:31:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D6QAW-0000cE-Mq; Wed, 02 Mar 2005 04:29:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D6Q9g-0000VZ-C4 for sipping@megatron.ietf.org; Wed, 02 Mar 2005 04:28:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17043 for <sipping@ietf.org>; Wed, 2 Mar 2005 04:28:30 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D6QAn-0003GJ-B1 for sipping@ietf.org; Wed, 02 Mar 2005 04:29:42 -0500
Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-4.cisco.com with ESMTP; 02 Mar 2005 01:29:34 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com [171.71.163.28]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j229SDTM023525; Wed, 2 Mar 2005 01:28:13 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-1-16.cisco.com [10.86.240.16]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AIE09179; Wed, 2 Mar 2005 01:28:12 -0800 (PST)
Message-ID: <4225872B.9070603@cisco.com>
Date: Wed, 02 Mar 2005 04:28:11 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Roy, Radhika" <RoyR@saic-abingdon.com>
Subject: Re: [Sipping] Draft: Functions of Current SBCs
References: <37B2A14433611A4C93B9A22A082E8ED6D403BE@bh-exchange01.saic-abingdon.com>
In-Reply-To: <37B2A14433611A4C93B9A22A082E8ED6D403BE@bh-exchange01.saic-abingdon.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

inline.

Roy, Radhika wrote:

> Medhavi:
>  
> We did discuss this during RFC 3261 (Jonathan R. - is this ALG example 
> for modifying SDP an exception or we are missing something?).

Proxies are not permitted to modify SDP, period. A SIP ALG that does so 
is a violation of RFC3261. Indeed, ALGs present many problems, of which 
SDP rewriting is just one. Please take a look at:

http://www.ietf.org/internet-drafts/draft-iab-nat-traversal-considerations-00.txt

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
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

v2.23.0 | Report a Bug | By Email