W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2017

Re: Process for "feature at risk" designation

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 4 May 2017 15:10:03 +1000
Message-ID: <CABkgnnVb346-AsLSQXwy-sg9iCOQn3+X7yxNa94ignUdZiRQnw@mail.gmail.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 4 May 2017 at 14:52, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:

> Feature at Risk 3: RTCCertificate.getAlgorithm()
>      Note: During the interim, EKR expressed surprise as to why this was
> “at risk”.   Since there have been changes to the certificates returned by
> getConfiguration().certificates (e.g. the pre-configured certificates are
> no longer returned), perhaps we should be having a discussion about whether
> getAlgorithm() is still needed.  Since it is no longer possible to use
> getAlgorithm() to determine the algorithm used in a pre-configured
> certificate, the only use left is to return the algorithm used to create a
> certificate created by the application, which it could have stored for
> later retrieval.

This reads more like "why does this feature exist?"  Which supports the
notion that it might be at risk.

I had planned to implement getAlgorithm(), but would obviously prefer to
not have to implement anything.
Received on Thursday, 4 May 2017 05:10:37 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:50 UTC