Re: Web NFC APIs: Missing transceive

On Thu, May 4, 2017 at 4:22 PM, Raphael COLLADO <Raphael.COLLADO@st.com>
wrote:

> Hi,
>
>
>
> One major limitation of the current Web NFC APIs is that it’s not possible
> to perform NFC-A, NFC-V IO operations through  transceiver commands (like
> a function taking an array of bytes as parameter  and returning an array of
> bytes). That would permit application developers to implement their own
> stacks, hence to use the whole set of NFC tags features not necessarily
> defined by the NFC Forum. From my understanding the WebNFC APIs are so far
> NDEF message oriented only. That is a big limitation wrt the features
> exposed by dynamic tags. Some tags have for instance, crypto, fast transfer
> mode, anti-tampering, multi area features that can only be used through
> specific RF commands.
>
> For Android/Chrome, it should be achievable extending the NFCImpl and/or
> the TagTechnologyHandler interface to take profit of the transceive methods
> exposed in the android.nfc.tech package.
>
>
>

That is true, but the low level NFC APIs are considered out of scope for
Web NFC, as Anssi explained earlier.
To cover low level NFC support, we need a different API object with
different security model, i.e. a different spec with a different charter.

Best regards,
Zoltan