Re: [rtcweb] IdP in RTCWeb
Eric Rescorla <ekr@rtfm.com> Thu, 22 March 2012 17:54 UTC
Return-Path: <ekr@rtfm.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 B71F121F85F3 for <rtcweb@ietfa.amsl.com>; Thu, 22 Mar 2012 10:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 OevTNXUm2jzc for <rtcweb@ietfa.amsl.com>; Thu, 22 Mar 2012 10:54:42 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1C84921F851B for <rtcweb@ietf.org>; Thu, 22 Mar 2012 10:54:42 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so2704437vcb.31 for <rtcweb@ietf.org>; Thu, 22 Mar 2012 10:54:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=XdOAKYid8LT6ZwHS/+Vp37pUXZ4g45nceR6oyeK7cZo=; b=aMNvxmrOOhQi1iDyuSKR8boYxA3qETw6FXCZRiAka/QOz5pSJX6/XbNILpBHqhjxjv mIBjdiiBeIU88VWOCNjSFr3sz+RMjAW4KcVhraWMc9o8JVWV/t5uVEJI4hsZ9ZUTFosh EVJ/LDVhocAHv6hi7ru1wOaJSR39j0kyH/ShAyQIia9v7fMbfq197oLrFfe6t+nSWbqc TPD+TQ+8mJB5j+OUlc685cR3OQBOOoRXTy+QzfMKu6HeC59lke3nRHDvUE8ONuRSbEz1 kL/eWeBvjEziAhJC6U5js6Rlaf6caHc7HPVSD1pWrSiz9LXs8v5nyrLUjZ1/Aczd7EqX yHMA==
Received: by 10.52.67.11 with SMTP id j11mr3477727vdt.40.1332438881316; Thu, 22 Mar 2012 10:54:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.22.195 with HTTP; Thu, 22 Mar 2012 10:53:42 -0700 (PDT)
X-Originating-IP: [81.253.52.0]
In-Reply-To: <4F6B5FEE.9060706@alcatel-lucent.com>
References: <4F6B5FEE.9060706@alcatel-lucent.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 22 Mar 2012 18:53:42 +0100
Message-ID: <CABcZeBPBac83KmE3we1nAV+eEusLrJbUij4DHmuCyDSkQ4fdVQ@mail.gmail.com>
To: igor.faynberg@alcatel-lucent.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlgTJ6Gv7hRl7jfCmRPmOaHTuafrHxAf/glhdO2W1EP6F6lFKQW/7KeetVVakEttMIb/h3r
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] IdP in RTCWeb
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, 22 Mar 2012 17:54:42 -0000
Good question. 1. BrowserID certificates aren't X.509, and that's all the TLS/DTLS will do. 2. This lets us be agnostic about IdP mechanisms without having to change TLS every time we add a new one. -Ekr On Thu, Mar 22, 2012 at 6:22 PM, Igor Faynberg <igor.faynberg@alcatel-lucent.com> wrote: > Eric, > > A question: For the case of BrowserID, I understand that a client gets a > certificate from an IdP. If so, why you and I would not use the > certificates from our respective IdPs in order to authenticate each other > in DTLS? > > Igor > > >
- [rtcweb] IdP in RTCWeb Igor Faynberg
- Re: [rtcweb] IdP in RTCWeb Eric Rescorla
- Re: [rtcweb] IdP in RTCWeb Igor Faynberg
- Re: [rtcweb] IdP in RTCWeb Harald Alvestrand
- Re: [rtcweb] IdP in RTCWeb Igor Faynberg
- Re: [rtcweb] IdP in RTCWeb Ralph Giles