Re: [Sip] nit in draft-wing-sip-e164-rrc-01

"Dan Wing" <dwing@cisco.com> Sat, 01 March 2008 00:36 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: ietfarch-sip-archive@core3.amsl.com
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C82E428C8B8; Fri, 29 Feb 2008 16:36:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.827
X-Spam-Level:
X-Spam-Status: No, score=-0.827 tagged_above=-999 required=5 tests=[AWL=-0.390, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 p57tCcXCMkld; Fri, 29 Feb 2008 16:36:02 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4575A28C901; Fri, 29 Feb 2008 16:36:02 -0800 (PST)
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 8C23928C81C for <sip@core3.amsl.com>; Fri, 29 Feb 2008 16:36:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 tTrFLy24ocHX for <sip@core3.amsl.com>; Fri, 29 Feb 2008 16:35:59 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id C619228C80D for <sip@ietf.org>; Fri, 29 Feb 2008 16:35:59 -0800 (PST)
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 29 Feb 2008 16:35:52 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m210ZqfS010041; Fri, 29 Feb 2008 16:35:52 -0800
Received: from dwingwxp01 (dhcp-128-107-163-88.cisco.com [128.107.163.88]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m210ZhCQ024427; Sat, 1 Mar 2008 00:35:52 GMT
From: Dan Wing <dwing@cisco.com>
To: 'David Schwartz' <David.Schwartz@Kayote.com>
References: <1DDB0D3CC4E7F14FAE946361C0A6065504FCB700@isr-jlm-mail.Kayote.com>
Date: Fri, 29 Feb 2008 16:35:43 -0800
Message-ID: <004d01c87b34$3406dd00$58a36b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ach4x0TCNh6QwqPNQeO7TMN1gaeTRACbLenw
In-Reply-To: <1DDB0D3CC4E7F14FAE946361C0A6065504FCB700@isr-jlm-mail.Kayote.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=996; t=1204331752; x=1205195752; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[Sip]=20nit=20in=20draft-wing-sip-e164- rrc-01 |Sender:=20; bh=C0ontvuKXJR+3+nYKe098hYtlKB6sZw1/YrkXaNZ98U=; b=fP+n9NQUXDocJ3Mg6X4Z41BAeQO2cuUnwd/GiDmfsqaW09sa5utgoiq6xC plNugsnO1g4xfy/mqAJfCUYne36DgdBDgJtSpfUZAzvR0dJVodqX6h9PS8bz qOZTMXIHia;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: sip@ietf.org
Subject: Re: [Sip] nit in draft-wing-sip-e164-rrc-01
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

 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of David Schwartz
> Sent: Tuesday, February 26, 2008 2:31 PM
> To: dwing@cisco.com
> Cc: sip@ietf.org
> Subject: [Sip] nit in draft-wing-sip-e164-rrc-01
> 
> 
> Hi Dan
> 
> a quick comment on this draft...
> 
> There is no discussion of what happens when there is a 
> validation failure. While obvious, you should probably 
> reference 4474 processing upon validation failure (i.e. 
> respond with 438 'Invalid Identity Header'). And while on the 
> topic in your second example where the cert comparison test 
> fails your diagram still shows the call proceeding to its 
> destination (hence the earlier comment).

I'm not sure we want to fail a call if validation fails; 
rather, we may want to allow it to complete and tell the
user 'unauthenticated caller' (similar to what the PSTN 
does today by displaying "unidentified call" when caller
ID failed).

-d

_______________________________________________
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