#391: WebOTP API

Visit on Github.

Opened Jun 27, 2019

こんにちはTAG!

I'm requesting a TAG review of:

  • Name: SMS Receiver API
  • Specification URL: not yet available
  • Explainer (containing user needs and example code)¹: explainer
  • GitHub issues (if you prefer feedback filed there): issues
  • Tests: WPT
  • Primary contacts (and their relationship to the specification): @samuelgoto, @sso-google

Further details:

  • Relevant time constraints or deadlines: [please provide]
  • I have read and filled out it here.
  • I have reviewed the TAG's API Design Principles
  • The group where the work on this specification is:

We recommend the explainer to be in Markdown. On top of the usual information expected in the explainer, it is strongly recommended to add:

  • Links to major pieces of multi-stakeholder review or discussion of this specification:
  • Links to major unresolved issues or opposition with this specification:

You should also know that...

[please tell us anything you think is relevant to this review]

We'd prefer the TAG provide feedback as (please select one):

  • open issues in our GitHub repo for each point of feedback
  • open a single issue in our GitHub repo for the entire review
  • leave review feedback as a comment in this issue and @-notify [github usernames]

Please preview the issue and check that the links work before submitting. In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document.

¹ For background, see our explanation of how to write a good explainer.

Discussions

2019-07-10

Minutes

Tess: please assign me.

Dan: me too

David: me too...

Peter: what stops this from slurping all SMS messages

David: a few things - based on an Android API that matches based on a hash.

Dan: main use case is 2FA codes over SMS

Tess: the alternative proposal is already in the HTML spec - a one-time code autocomplete value. David linked to the moz standards position on this. And disclosure: i wrote the PR for the alternative feature.

[milestone set for

2019-07-24

Minutes

[we agreed to bump 2 weeks

2019-08-14

Minutes

David: Didn't get to this in breakout, should schedule one for this week.