Re: [Sip] Signing P-Asserted-Identity

"Elwell, John" <john.elwell@siemens.com> Tue, 15 July 2008 20:13 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47A893A6A07; Tue, 15 Jul 2008 13:13:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E69D3A6931 for <sip@core3.amsl.com>; Tue, 15 Jul 2008 13:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 Dbk6p5fhaxjb for <sip@core3.amsl.com>; Tue, 15 Jul 2008 13:13:50 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 470B03A6A07 for <sip@ietf.org>; Tue, 15 Jul 2008 13:13:50 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0K420047FDJT6C@siemenscomms.co.uk> for sip@ietf.org; Tue, 15 Jul 2008 21:14:17 +0100 (BST)
Date: Tue, 15 Jul 2008 21:14:15 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <D56CAA4B-FDA0-4DC8-95FA-AE5A25C90E0A@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>, SIP List <sip@ietf.org>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0E66C77@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Signing P-Asserted-Identity
Thread-Index: AcjmmBTaLVeCgPJ5Sl+BGEpnw/WGwAAHuSDA
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <E6C2E8958BA59A4FB960963D475F7AC30EEDF3C361@mail.acmepacket.com> <48752F47.8060905@nostrum.com> <048901c8e20d$1dddda70$eaa36b80@cisco.com> <48753393.5090307@nostrum.com> <48753605.5010604@cisco.com> <487536D9.900@nostrum.com> <48753B83.40205@cisco.com> <5D1A7985295922448D5550C94DE291800210D663@DEEXC1U01.de.lucent.com> <0D5F89FAC29E2C41B98A6A762007F5D0E3B735@GBNTHT12009MSX.gb002.siemens.net> <4877812B.1090802@nostrum.com> <48778FB9.4070206@cisco.com> <0D5F89FAC29E2C41B98A6A762007F5D0E3BC54@GBNTHT12009MSX.gb002.siemens.net> <4877AAEA.5040906@cisco.com> <"4877B3A7.70307 02"@nostrum.com> <037301c8e38d$29d26f90$c2f0200a@cisco.com> <E6C2E8958BA59A4FB960963D475F7AC30EEE09B631@mail.acmepacket.com> <A03891BE-655A-4D91-87C4-3B51542C3EF6@voxeo.com> <F5165830-6EE8-4BA7-AA05-B3C0B007AA6C@sipforum.org> <487BB2E0.8060800@cisco.com> <E6C2E8958BA59A4FB960963D475F7AC30EFF2506EC@mail.acmepacket.com> <"487BC5 81.4040102"@cisco.com> <D56CAA4B-FDA0-4DC8-95FA-AE5A25C90E0A@cisco.com>
Subject: Re: [Sip] Signing P-Asserted-Identity
X-BeenThere: sip@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@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Cullen,

Have you read draft-elwell-sip-e2e-identity-important? I think you will
find that gives a number of reasonable use cases.

John 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Cullen Jennings
> Sent: 15 July 2008 17:23
> To: SIP List
> Subject: Re: [Sip] Signing P-Asserted-Identity
> 
> 
> On Jul 14, 2008, at 2:30 PM, Michael Thomas wrote:
> 
> >>
> >> So far, though, it's mostly just been complaints about why anyone  
> >> would need anything other than 4474.  Now if we could only have  
> >> gotten such a real-world deployment experience requirement before  
> >> moving 4474 to PS...
> >>
> >
> > Indeed.
> 
> There are implementations of 4474 around and were long before it  
> became and RFC but ignoring that ...
> 
> I asked some folks on this thread a few years ago for an 
> example of a  
> real deployment where it would not be possible to use 4474 as 
> long as  
> the SBC implemented 4474. I'm still waiting for an example of 
> where it  
> actually is broken. Hadriel  hypothesized a type of situation 
> where it  
> could be broken. That was the case where service provider A passed  
> call to B who passed call C and they were not using E.164 
> numbers but  
> were using email style addresses and the one in the middle wanted to  
> do media steering or restrict what codecs where allowed.
> 
> Cullen <with my individual contributor hat on>
> 
> _______________________________________________
> Sip mailing list  https://www.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://www.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