Re: Identity mechanism at risk?

Hi All,

I think it is essential to keep the Identity feature.

I reported the Identity Feature Request in chrome bug track in issue
493640 <https://bugs.chromium.org/p/chromium/issues/detail?id=493640>,
and the status of this issue has changed recently(Mar 6) from Available
to Assigned.
This way I hope this is an indication that chrome considered finally to
implement this feature.
I hope we will have a second implementation in chrome.

Furthermore our NREN community enjoying for a long while the benefits of
the federated (World Wide) AAI service.
IMHO to integrate already established AAI Identity federations, like
eduGAIN <https://technical.edugain.org/status> / REFEDS
<https://refeds.org/federations/federations-map> or our new OIDC federation
with WebRTC Identity will definitely add value to our community.

Misi

2017-03-14 10:35 keltezéssel, Dominique Hazael-Massieux írta:
> Hi all,
>
> As we are getting closer to clearing our issue lists for webrtc-pc and
> thus hopefully moving to Candidate Recommendation soon, and looking at
> the overall rough implementation status of the spec, it strikes me that
> at the moment the identity mechanism of the spec is one part for which I
> have very little clarity on implementations plan beyond Firefox.
>
>
> Given that part of the CR process is to demonstrate that each of the
> feature in the spec will be getting two independent implementations, I'm
> wondering how likely we feel we will achieve this for that part of the spec.
>
> In particular, if our current impression is that it is unlikely, it
> might be useful to mark it at risk [1] - beyond the small process
> efficiency it gives (not needing to go back to CR to remove it from the
> spec if we can't demonstrate interop), I think it would also serve as a
> useful way to draw attention to the community that they may voice their
> concerns one way or the other on the lack of adoption of this.
>
> Thoughts?
>
> (I've raised https://github.com/w3c/webrtc-pc/issues/1074 to track this)
>
> Dom
>
> 1. https://www.w3.org/2017/Process-20170301/#candidate-rec
>

Received on Friday, 17 March 2017 09:13:13 UTC