- From: Eric Rescorla <ekr@rtfm.com>
- Date: Mon, 13 Aug 2012 09:21:42 -0700
- To: Li Li <Li.NJ.Li@huawei.com>
- Cc: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
I have been wokring on a proposal here and expect to have something soonish. -Ekr On Mon, Aug 13, 2012 at 9:13 AM, Li Li <Li.NJ.Li@huawei.com> wrote: > Hi, > > I wonder if this WG is responsible for the item 3 below [1] as I didn't remember seeing any discussions about it: > > > 5.6.3. Items for Standardization > > > In order to make this work, we must standardize the following items: > > o The precise information from the signaling message that must be > cryptographically bound to the user's identity and a mechanism for > carrying assertions in JSEP messages. Section 5.6.4 > o The interface to the IdP. Section 5.6.5 specifies a specific > protocol mechanism which allows the use of any identity protocol > without requiring specific further protocol support in the browser > o The JavaScript interfaces which the calling application can use to > specify the IdP to use to generate assertions and to discover what > assertions were received. > > The first two items are defined in this document. The final one is > defined in the companion W3C WebRTC API specification [TODO:REF] > > Thanks. > Li > > [1] http://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-03 > > > -----Original Message----- > From: Stefan Hakansson LK [mailto:stefan.lk.hakansson@ericsson.com] > Sent: Wednesday, August 08, 2012 4:31 AM > To: public-webrtc@w3.org > Subject: Call for proposals on agenda items > > All, > > as we're planning for a new Telco, the chairs would like proposals on > what we should discuss at the meeting. An obvious candidate is the new > API proposal recently submitted, but what else should we cover? > > Stefan for the chairs > >
Received on Monday, 13 August 2012 16:23:00 UTC