[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] B2B-UA's provide an unsolveable identity problem (was RE: submission of a new I-D: "Dialog Event foRIdentityVErification")
On Oct 31, 2008, at 5:30 AM, Victor Pascual Ávila wrote:
Elwell, John writes:
I support draft-kuthan-sip-derive-00, and hope the WG can devote >
time and energy to improving and standardizing it to work well > >
across a variety of networks.
[JRE] I agree. This must include networks that contain B2BUAs/SBCs.
A B2BUA is a man-in-the-middle, there's no feasible end-to-end
scenario here.
One might argue that we could define a "standard B2BUA function for
optimal transparency". We would then add "Considerations at the
Standard B2BUA" into every SIP extension.
Would this change what SBCs do to make them application transparent?
I rather doubt it. My sense is that the SBCs do what they do for
reasons that are not dictated by our specifications, but from the
valid or invalid perceptions of network operators and the business
decisions they make in response to those perceptions.
We can tell them that not beating their heads on the wall will reduce
their cranial pain, but it is entirely possible that they're beating
their heads because they enjoy it, feel that it will scare away the
bogeyman, are using it to distract themselves from other self-
inflicted wounds, don't have anything better to do with their money,
or have found that ritual head-beFrom sip-bounces at ietf.org Fri Oct 31 15:02:26 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 7EF783A6802;
Fri, 31 Oct 2008 15:02:26 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 995843A67B2
for <sip at core3.amsl.com>; Fri, 31 Oct 2008 15:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5
tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 WwvxnedMzzAz for <sip at core3.amsl.com>;
Fri, 31 Oct 2008 15:02:25 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
by core3.amsl.com (Postfix) with ESMTP id D78713A6359
for <sip at ietf.org>; Fri, 31 Oct 2008 15:02:24 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
[76.185.142.113]) (authenticated bits=0)
by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
m9VM2KMO004462
(version=TLSv1/SSLv3 cipher®S128-SHA bits8 verify=NOT);
Fri, 31 Oct 2008 17:02:21 -0500
Message-Id: <8D041140-D5C3-4AA3-B785-B6BD8C896773 at softarmor.com>
From: Dean Willis <dean.willis at softarmor.com>
To: =?ISO-8859-1?Q?Victor_Pascual_Ávila?= <victor.pascual.avila at gmail.com>
In-Reply-To: <618e24240810310330h765b06bele08cd9cef8de2de9 at mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 17:02:15 -0500
References: <680808427CF931459462C3D78CB5EC60038B6296 at EXVS02.nasstar-t1.net>
<618e24240810310330h765b06bele08cd9cef8de2de9 at mail.gmail.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip at ietf.org
Subject: Re: [Sip] B2B-UA's provide an unsolveable identity problem (was RE:
submission of a new I-D: "Dialog Event foRIdentityVErification")
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
On Oct 31, 2008, at 5:30 AM, Victor Pascual Ávila wrote:
Elwell, John writes:
I support draft-kuthan-sip-derive-00, and hope the WG can devote >
time and energy to improving and standardizing it to work well > >
across a variety of networks.
[JRE] I agree. This must include networks that contain B2BUAs/SBCs.
A B2BUA is a man-in-the-middle, there's no feasible end-to-end
scenario here.
One might argue that we could define a "standard B2BUA function for
optimal transparency". We would then add "Considerations at the
Standard B2BUA" into every SIP extension.
Would this change what SBCs do to make them application transparent?
I rather doubt it. My sense is that the SBCs do what they do for
reasons that are not dictated by our specifications, but from the
valid or invalid perceptions of network operators and the business
decisions they make in response to those perceptions.
We can tell them that not beating their heads on the wall will reduce
their cranial pain, but it is entirely possible that they're beating
their heads because they enjoy it, feel that it will scare away the
bogeyman, are using it to distract themselves from other self-
inflicted wounds, don't have anything better to do with their money,
or have found that ritual head-beating seating sedates the liability vultures
and auditing zombies.
Happy Halloween!
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
dates the liability vultures
and auditing zombies.
Happy Halloween!
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip