Re: [Sip] comments on draft-ietf-sip-dtls-framework

Cullen Jennings <fluffy@cisco.com> Mon, 03 December 2007 06:00 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iz4M9-0001pV-PO; Mon, 03 Dec 2007 01:00:37 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Iz4M7-0001pA-N6 for sip-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 01:00:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iz4M7-0001p1-C9 for sip@ietf.org; Mon, 03 Dec 2007 01:00:35 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iz4M6-0005eJ-RV for sip@ietf.org; Mon, 03 Dec 2007 01:00:35 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 02 Dec 2007 22:00:34 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lB360Y98023248; Sun, 2 Dec 2007 22:00:34 -0800
Received: from [130.129.86.243] (sjc-vpn3-316.cisco.com [10.21.65.60]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lB360X76014188; Mon, 3 Dec 2007 06:00:34 GMT
In-Reply-To: A<0D5F89FAC29E2C41B98A6A762007F5D0441C01@GBNTHT12009MSX.gb002.siemens.net>
References: <4741BB94.80202@cisco.com> <4F6C1429-EABB-452A-A542-94078E8AA151@cisco.com> <0D5F89FAC29E2C41B98A6A762007F5D0441A85@GBNTHT12009MSX.gb002.siemens.net> <474AC204.9080606@cisco.com> <474B62C7.6050604@cisco.com> A<0D5F89FAC29E2C41B98A6A762007F5D0441C01@GBNTHT12009MSX.gb002.siemens.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <73B36FE5-9E94-40C9-AF30-123AC8667FB4@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sip] comments on draft-ietf-sip-dtls-framework
Date: Sun, 02 Dec 2007 21:58:45 -0800
To: "Elwell, John" <john.elwell@siemens.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3149; t=1196661634; x=1197525634; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20[Sip]=20comments=20on=20draft-ietf-sip-dtls-framework |Sender:=20; bh=GoMKtjenEJWSuJrqtVNmBLtLezVM2XC8CwexALnQoSE=; b=iSoNT/d2P4WyRv8fCsiJ1n7Hi40eRaoymlvfw23d8aTjNfkRLAbvRZA2VNTP/9qqHsqArile VvwVgNU4B2gvgCab20TogtVX11kRyZsP3GgORKEUZrpiUqJpAIziLNiEKlaFLEM5GLns716onp tstAZl7ArzkxcSRV8QoOrgCZE=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: IETF SIP List <sip@ietf.org>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

I agree that if a device is going to have much usefulness in  
indicating that media is encrypted, it also needs to say who it is  
from so one can determine that it is not from the MiTM.

Cullen <with my individual contributor hat on>



On Nov 26, 2007, at 11:28 PM, Elwell, John wrote:

> The point is, when showing the padlock icon to say that a call's media
> are secured, it needs to accompanied by a display of the domain to  
> which
> it has been verified to be secure. The same way that when I go to a
> secure web site I can see the URL and, if I desire, view the
> certificate. For SIP, this should be true whether the user-ID within
> that domain is a phone number or not.
>
> So if I make a call to somebody in example1.com, I would expect  
> that to
> be shown and not something like MitM.net.
>
> John
>
> > -----Original Message-----
> > From: Jonathan Rosenberg [mailto:jdrosen@cisco.com]
> > Sent: 27 November 2007 00:20
> > To: Paul Kyzivat
> > Cc: Cullen Jennings; IETF SIP List; Elwell, John
> > Subject: Re: [Sip] comments on draft-ietf-sip-dtls-framework
> >
> > inline:
> >
> > Paul Kyzivat wrote:
> > > John,
> > >
> > > I agree with your analysis. And yet in many contexts there
> > is a strong
> > > desire to display "phone numbers", because of custom and
> > limitations of
> > > protocols and devices. So there is a tendency to coerce a
> > sip URI into a
> > > phone number whenever it looks like that can be done.
> >
> > Its more than a rendering problem. The identifier is meaningful for
> > security because the person on the receiving end of the call
> > can tie it
> > to user - the one that they know has been assigned this
> > identifier. And
> > thus, they can be assured that, when they answer the phone, they  
> know
> > the user that is calling (let us put aside issues when
> > someone else uses
> >   my phone to make calls).
> >
> > The root issue is that FUNDAMENTALLY, phone numbers are not scoped
> > within a domain. For this reason, the mapping that exists in peoples
> > heads from identifiers to users is of one of two forms:
> >
> > "user@domain" --> some person
> > "1 (408) 902-5000" ---> some person
> >
> > so, even if you user interface could render the fact that,
> > the call was
> > from sip:14089025000@somedomain.com, I believe that users
> > would anyway
> > ignore the domain part since there is no domain part for
> > phone numbers.
> >
> > -Jonathan R.
> >
> > --
> > Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
> > Cisco Fellow                                   Edison, NJ 08837
> > Cisco, Voice Technology Group
> > jdrosen@cisco.com
> > http://www.jdrosen.net                         PHONE: (408) 902-3084
> > http://www.cisco.com
> >
> >
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> >
>


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip