Re: [web-nfc] "A Better Q"

@anssiko If the people reading this issue are unfamiliar with how QR-codes are used on the Web, there seems to be little point developing a detailed technical description.  BTW, I'm _not_ an expert on NFC.  A fruitful outcome would IMO require a _dialog_ between platform and application folks.  The people owning the aforementioned QR-powered systems usually do not talk to platform developers, making this task slightly challenging :)

The issue title is _deliberately_ somewhat "non-technical" because the same title and content have gotten quite a bunch of views (and 👍) by bank people on LinkenIn who I also hope will monitor possible progress on this topic _which already affects several hundred millions of users_.  An important part of this use case is that the same scheme with moderate adjustments would also be used in the physical (non-Web) world including POS terminals, ATMs, and Gas stations.

Now to the technical side of things _as seen from an application point of view_.  A QR-code provides "data" having no pre-defined function.  A Better QR using Web NFC would do the same, with one major difference: The security context (URL + Certificate) of the invoking Web page must also be available so that the OOB communication performed by the App in the phone can _prove_ where it got its invocation from to the server it typically calls.  There is typically "nonce" information involved as well but that belongs to the "data" provided by NFC.

-- 
GitHub Notification of comment by cyberphone
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/128#issuecomment-306172966 using your GitHub account

Received on Monday, 5 June 2017 12:12:25 UTC