IETF Logo Mail Archive

Re: [sipcore] SIP/websocket: SIP Identity question

Dean Willis <dean.willis@softarmor.com> Fri, 08 November 2013 05:58 UTC

Return-Path: <dean.willis@softarmor.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B253021E81C9 for <sipcore@ietfa.amsl.com>; Thu, 7 Nov 2013 21:58:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.314
X-Spam-Level:
X-Spam-Status: No, score=-102.314 tagged_above=-999 required=5 tests=[AWL=0.285, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0K-QOGnHA6aj for <sipcore@ietfa.amsl.com>; Thu, 7 Nov 2013 21:58:20 -0800 (PST)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA2811E8158 for <sipcore@ietf.org>; Thu, 7 Nov 2013 21:58:02 -0800 (PST)
Received: by mail-pb0-f54.google.com with SMTP id ro8so572091pbb.27 for <sipcore@ietf.org>; Thu, 07 Nov 2013 21:57:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=id1qxv3nIRphiD2OwZEJJKmbhr2bswVCIplbVdeS3pU=; b=b+qXP0+mtREB3HTisdh0DGYHtrN+RNAevC880rthmng1tkX4zPVjr8tcPG6IutDXKp CXCA/d+ueavtT5USaBn7PvhDD3PNQTugo+/QzbRL+AqpiqgouzEs6dC9V8G4akmDX6zK 29cYFdctMEMa/ZrGaqKBBD0cfKnDk55Hnkdec=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=id1qxv3nIRphiD2OwZEJJKmbhr2bswVCIplbVdeS3pU=; b=PsntJQWo/pvP6m3lSUY1ABguCXrPA2YPHlk4PEXqp66Bc9Da4nJWugTXO0blrvbQxC LiQXN+pil5VTZf9qXjnKr3G983WIUbKKge+Op03iLwJdKuDwrWHARqxDXGToOEy5R8M1 W4Mp8b74FiRHPcRMEF/oOpsmUORZJkhfQtPQoLUbDBg8sVLrZnpItCCcCXtwXNN2B2p6 JIkf04ZAWcLWsKbISW4WFsciQbFlEniQ016W4YnMPR5+csHtE7Lzr8e0H+t3uweHiexm oWco9qUSdamyubDILIIG2MqaAz8UEXZYOwQSgPO9PDQuO4pkb+b+950rjJCJnjmfJcr0 7Z1w==
X-Gm-Message-State: ALoCoQmoWKx6Dfg8oxwJcw8pXfgl2QhXYqObiW6ES+i09UsvciBfhn+B5ZFLA9RySi+NwTOBfxZV
X-Received: by 10.68.229.2 with SMTP id sm2mr13081014pbc.68.1383890272501; Thu, 07 Nov 2013 21:57:52 -0800 (PST)
Received: from [10.143.89.29] (S0106001b2fe1bb13.vc.shawcable.net. [174.6.170.174]) by mx.google.com with ESMTPSA id gf5sm9394280pbc.22.2013.11.07.21.57.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Nov 2013 21:57:51 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <527B1830.30000@oracle.com>
Date: Thu, 07 Nov 2013 23:57:49 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <033FDA36-997D-4A72-B26A-979DCEDBC1F3@softarmor.com>
References: <5264AB70.7000408@oracle.com> <527B1830.30000@oracle.com>
To: binod pg <binod.pg@oracle.com>
X-Mailer: Apple Mail (2.1822)
Cc: sipcore@ietf.org
Subject: Re: [sipcore] SIP/websocket: SIP Identity question
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2013 05:58:21 -0000

On Nov 6, 2013, at 10:33 PM, binod pg <binod.pg@oracle.com> wrote:

> I have few more further questions on this section.
> 
> 1. The text in section 7 does not talk about which SIP header contains SIP identity that
>    will be used for matching against the SIP Identity associated to the websocket
>    connection. Section A.2 mentions it as From URI value. But A.2 is non-normative.
>    So, will it be always From URI? In a discussion in SIP servlet expert group a question
>    was asked, whether it can be P-Asserted-Identity. Can it be?
> 
> 2. Doesn't the requirement for matching implies that the user can not use more than
>    one SIP identity(eg: IMPU)?
> 
> 3. If a user want to keep the SIP identity private/anonymous (RFC 3323), would the rule for
>    matching the SIP identity still apply?
> 
> thanks,
> Binod.

Congratulations. You have found the elephant in the room that others have been tiptoeing around without mentioning.

SIP Identity is broken, and needs to be fixed before any other standard can reasonably build on it. Most IMS systems will use the P-Asserted-Identity header for this role, but outside of IMS, it’s absolute mayhem.

There’s ongoing work in STIR on a completely analogous issue for telephone number identity assertions. It would be nice to converge on a unified approach.

—
Dean

v2.23.0 | Report a Bug | By Email