IETF Logo Mail Archive

Re: [rtcweb] Exchange of trusted identities in server-based conferencing (Re: Use case change request: Identity in multiuser calls)

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Fri, 12 August 2011 14:17 UTC

Return-Path: <igor.faynberg@alcatel-lucent.com>
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 8E29721F86D0 for <rtcweb@ietfa.amsl.com>; Fri, 12 Aug 2011 07:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.742
X-Spam-Level:
X-Spam-Status: No, score=-6.742 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 NF+nt29RhY9k for <rtcweb@ietfa.amsl.com>; Fri, 12 Aug 2011 07:17:46 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id F119C21F84E1 for <rtcweb@ietf.org>; Fri, 12 Aug 2011 07:17:45 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p7CEIHBM012749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 12 Aug 2011 09:18:17 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p7CEIGnm028647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Aug 2011 09:18:16 -0500
Received: from [135.244.38.171] (faynberg.lra.lucent.com [135.244.38.171]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p7CEIEqE029909; Fri, 12 Aug 2011 09:18:15 -0500 (CDT)
Message-ID: <4E453626.50607@alcatel-lucent.com>
Date: Fri, 12 Aug 2011 10:18:14 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <CA69AF47.1CBB0%henry.sinnreich@gmail.com> <4E445F49.6080705@alcatel-lucent.com> <4E449E6B.8020205@alum.mit.edu> <4E450F00.9090908@alvestrand.no>
In-Reply-To: <4E450F00.9090908@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: rtcweb@ietf.org, Phil Zimmermann <prz@mit.edu>
Subject: Re: [rtcweb] Exchange of trusted identities in server-based conferencing (Re: Use case change request: Identity in multiuser calls)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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: Fri, 12 Aug 2011 14:17:46 -0000

On 8/12/2011 7:31 AM, Harald Alvestrand wrote:
> ...
> The normal method of authentication for teleconferences today is that 
> people prove they have the conference number (by calling in), and 
> recognize each others' voices.
> ...

Is there not a conference code, too?  In all (five or six of them that I 
have used) there was one.  This code is, effectively, a shared secret. 
In the service we use, the conference host can create a new code for 
each meeting.  (One problem with relying on recognizing voices is 
passive intruding: I can join your conference and never say a word.)

Igor
>

v2.23.0 | Report a Bug | By Email