3 ms·
> There are multiple NFC standards with differences in speed, protocol, and range, including NFC-A, NFC-B, NFC-C, NFC-F, and NFC-V. The MIFARE Ultralight cards
by lxgr 2y ago
> There are multiple NFC standards with differences in speed, protocol, and range, including NFC-A, NFC-B, NFC-C, NFC-F, and NFC-V. The MIFARE Ultralight cards use NFC-A, which is defined by the standard "ISO/IEC 14443 Type A".
Pet peeve: Calling these chips "NFC" is a bit misleading. NFC-A isn't defined by ISO 14443-A, but builds on it.
NFC is an umbrella standard that defines a way of storing structured data on a wide variety of existing contactless IC technologies (including, but not limited to ISO 14443) and products (such as NXP's various MIFARE chips, which in turn are based on various layers of ISO 14443 up to -4).
For the concrete example, it's correct to say that one possible implementation of an NFC-A tag is MIFARE Ultralight (that would be a NFC forum type 2 tag), but neither is NFC the only thing you can do with MIFARE Ultralight (and this transit use case almost certainly doesn't put an NDEF container on the ticket), nor is this the only type of tag you could use for NFC.
- moralestapia 2y ago>NFC is an umbrella standard that defines a way of storing structured data on a wide variety of existing contactless IC technologies [...] Yeah, then it's appropriate to call this NFC.
- lxgr 2y agoExcept that the highest layers in that stack is not used by many contactless systems. As an analogy, you wouldn't call HTTP or TCP "web protocols" either, even though the web uses both (but it can also run on QUIC, which is UDP, and you can do non-web-things via HTTP). Importantly, NFC standardizes a way of storing structured data like URLs or phone numbers on NFC tags; transit tickets most likely don't use tags in that way.
- account42 2y agoDid you google all of that on your PC?