Re: [Sipping] Purpose of camarillo-sipping-sbc-funcs-02
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Sat, 29 October 2005 19:07 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVw2h-0005eu-4R; Sat, 29 Oct 2005 15:07:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVw2e-0005ed-F5 for sipping@megatron.ietf.org; Sat, 29 Oct 2005 15:07:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18141 for <sipping@ietf.org>; Sat, 29 Oct 2005 15:06:41 -0400 (EDT)
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVwGS-0003tG-VM for sipping@ietf.org; Sat, 29 Oct 2005 15:21:18 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 8AFB267B; Sat, 29 Oct 2005 21:06:46 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Sat, 29 Oct 2005 21:05:05 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Sat, 29 Oct 2005 21:05:04 +0200
Received: from [131.160.126.79] (rvi2-126-79.lmf.ericsson.se [131.160.126.79]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 3D7B2235F; Sat, 29 Oct 2005 22:05:04 +0300 (EEST)
Message-ID: <4363C7DF.9030407@ericsson.com>
Date: Sat, 29 Oct 2005 22:05:03 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sipping] Purpose of camarillo-sipping-sbc-funcs-02
References: <BF7FC410.56B14%fluffy@cisco.com>
In-Reply-To: <BF7FC410.56B14%fluffy@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2005 19:05:04.0760 (UTC) FILETIME=[ABB3A780:01C5DCBB]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: 7bit
Cc: sipping <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
Hi Cullen, my opinion is that this draft should focus on documenting functions that are needed (i.e., folks are currently implementing them) and that are implemented in a way that breaks SIP somehow. The fact that these functions are implemented by an SBC seems irrelevant to me. A document with such a scope would be useful to: 1) clarify why if a function is implemented in a particular way, it breaks things. The document needs to go beyond "this is evil" and explain what problems you can expect if you implement things in that way. 2) provide input to the community so that we know which functions cannot be implemented with the current SIP toolbox. We may need to come up with extensions for those functions. It may also be possible that a particular function can be implemented in a friendly way and in an unfriendly way. We may need to point out the advantages of choosing the former way. > What I want is a document that is a requirements document on the problems > that people want to solve that they currently solve using a SBC. This would > be informational Yes, we seem to be on the same page. I want to know which functions are implemented in a way that breaks SIP. You want to know which problems are resolved in a way that breaks SIP. Two different ways of saying the same thing. In any case, if seems obvious that the terminology currently used in the draft is confusing. We will try and clarify its scope further in the next revision of the draft. Thanks, Gonzalo Cullen Jennings wrote: > > When this draft was started, my recollection was that the purpose was > > This document gives an overview to Session Border Controllers (SBCs) > and to the functions they perform. The way how SBCs relate to the > telecommunication architectures is also presented. The purpose of > this document is to help the IETF community understand what > functionality existing SBCs provide so that the appropriate working > groups can decide whether or not new standard solutions need to be > developed to provide such functionality (or a subset of it) in a > standard way. > > I like that idea - we need to develop requirements and understanding of why > SBCs are used. Many people felt that we did not want to repeat the path > that > IETF did with NATs that eventually resulted in the behave group. > > However, the document seem to be moving in the direction of 1) assuming > specific ways to build SBC that may or may not reflect how they are all > build 2) turning into a B2BUA are evil documentation which right or wrong, > is not what I was hoping to get out of this document > > What I want is a document that is a requirements document on the problems > that people want to solve that they currently solve using a SBC. This would > be informational - the BCP discussion leaves me feeling very unclear on > what > the purpose of this document is. > > So my questions is - what is the purpose of this document? I recognize > it is > individual and that as it was written, the authors may have changed it's > purpose over time. > > Cullen > > _______________________________________________ > 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 > -- Gonzalo Camarillo Phone : +358 9 299 33 71 Oy L M Ericsson Ab Mobile: +358 40 702 35 35 Telecom R&D Fax : +358 9 299 30 52 FIN-02420 Jorvas Email : Gonzalo.Camarillo@ericsson.com Finland http://www.hut.fi/~gonzalo _______________________________________________ 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
- [Sipping] Purpose of camarillo-sipping-sbc-funcs-… Cullen Jennings
- Re: [Sipping] Purpose of camarillo-sipping-sbc-fu… Jani Hautakorpi (JO/LMF)
- Re: [Sipping] Purpose of camarillo-sipping-sbc-fu… Gonzalo Camarillo