Re: [rtcweb] Use Case draft

Harald Alvestrand <harald@alvestrand.no> Thu, 03 May 2012 06:11 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34CD721F8564 for <rtcweb@ietfa.amsl.com>; Wed, 2 May 2012 23:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.486
X-Spam-Level:
X-Spam-Status: No, score=-110.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 uDr6p4CmhdJ8 for <rtcweb@ietfa.amsl.com>; Wed, 2 May 2012 23:11:21 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB6721F8562 for <rtcweb@ietf.org>; Wed, 2 May 2012 23:11:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C53D639E113 for <rtcweb@ietf.org>; Thu, 3 May 2012 08:11:20 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sNEvknY1ZcwZ for <rtcweb@ietf.org>; Thu, 3 May 2012 08:11:20 +0200 (CEST)
Received: from [192.168.11.193] (c213-89-143-9.bredband.comhem.se [213.89.143.9]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 261B839E072 for <rtcweb@ietf.org>; Thu, 3 May 2012 08:11:20 +0200 (CEST)
Message-ID: <4FA22187.2000307@alvestrand.no>
Date: Thu, 03 May 2012 08:11:19 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA+9kkMCYArLPRP3c00UdOja64WRT6ghN0PSy7XvM_wbxBBB+vA@mail.gmail.com><E17CAD772E76C742B645BD4DC602CD810616F066@NAHALD.us.int.genesyslab.com><BLU169-W7C59E1EDB4CB06B648577932B0@phx.gbl><387F9047F55E8C42850AD6B3A7A03C6C0E23AFFF@inba-mail01.sonusnet.com><2E496AC9-63A0-464A-A628-7407ED8DD9C4@phonefromhere.com><387F9047F55E8C42850AD6B3A7A03C6C0E23B16B@inba-mail01.sonusnet.com><E2714FBC-D06B-4A12-9E07-C49EBF55084C@phonefromhere.com><4F9EC0B2.10903@alcatel-lucent.com><101C6067BEC68246B0C3F6843BCCC1E31299282765@MCHP058A.global-ad.net> <CAJNg7VKENERKAFA-n5KeoeBNmGgHrnzDOU0BzC9+fSdsuGwdEw@mail.gmail.com> <E17CAD772E76C742B645BD4DC602CD810616F24F@NAHALD.us.int.genesyslab.com> <4FA0F43E.4020308@ericsson.com> <387F9047F55E8C42850AD6B3A7A03C6C148913C5@inba-mail02.sonusnet.com> <4FA15C18.6040509@alcatel-lucent.com> <387F9047F55E8C42850AD6B3A7A03C6C14894717@inba-mail02.sonusnet.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C14894717@inba-mail02.sonusnet.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Use Case draft
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2012 06:11:22 -0000

On 05/03/2012 07:05 AM, Ravindran, Parthasarathi wrote:
> Igor,
>
> When you call Company X, you need to assure that you are talking with Company X agent and not required to distinguish the agent.
>
> The identity could be just X (no userpart) or anonymous. There is no difference between anonymous and agent007@X as there is no means to route directly agent007@x in the call centre scenario.
It' s easy to construct scenarios where having the ability to set up a 
connection directly to agent007@x is desirable - consider the case of 
anonymous counselling, where a call gets dropped in the middle of the 
conversation; while the caller wishes to know that the callee is really 
a representative of "X anonymous", and both parties wish to remain 
anonymous as persons, when the call gets dropped in the middle of the 
conversation, the calling party has a strong incentive to continue the 
conversation with the same party, if possible.

In this case, having a callee identity with a lifetime of "one 
conversation" seems highly desirable; any distributed ID system (such as 
1st party BrowserID) should be able to easily support that.

            Harald