Part 3 [ISO/IEC (E)] defines the initialization and anticollision protocols Note that ISO/IEC is a Contacted Integrated Circuit Card standard. INTERNATIONAL. STANDARD. ISO/IEC. Second edition. Identification ISO’s member body in the country of the requester. ISO copyright . The ISO/IEC describes how to select (“activate”) a single card. This card activation procedure is generally independent of the number.

Author: Natilar Malagar
Country: Pacific Islands
Language: English (Spanish)
Genre: Finance
Published (Last): 9 February 2015
Pages: 150
PDF File Size: 1.37 Mb
ePub File Size: 18.40 Mb
ISBN: 618-8-45362-869-2
Downloads: 69639
Price: Free* [*Free Regsitration Required]
Uploader: Mazugal

ISO anti-collision protocol is not correct Ask Question. There are usually some patterns like one vendor has some prefix and then prefix of card type – So it looks to me more like somebody had bad day than calculated trough decision. This problem existed in the version of the standard and was corrected in Amendment 1 in by adding the clause: The probability that noise occurs that disrupts any communication is probably much higher!

Post as a guest Name.

Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies. While I believe that I read current version, I haven’t checked that.

This problem existed in the version of the standard and was corrected in Amendment 1 in by adding the clause:.

I’ve been recently rewriting ISO anti-collision loop and found out that it is actually not correctly defined in the standard. Cryptography depends on an attacker not, by sheer luck, finding the right key on the first try; mechanical engineering is all “oh all these iron atoms are aranged in a neat metal grid, so the probability of a crystal fracture going through the whole steel beam supporting this skyscraper is really really small”.

  DIN 18036 PDF

Stack Overflow works best with JavaScript enabled. Obviously, no hash is free of collisions, as long as the hash is shorter than the hashed data — but the probability of something randomly changing the hashed data to false data with the same hash is so small, it can be neglected in practice. By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

So somebody will come and will start to poke into readers to see if it not breaks something. Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.

ISO/IEC – Wikipedia

I don’t like that you can easily fabricate this one – and it is not defined what to do in that case. Home Questions Tags Users Unanswered. I don’t fully understand it. By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. Sign up using Facebook.

I know 14443-33 is very low probability 1: Practical standards do practical implications. Nowhere in the iso standard is written that uid3 cant be 88 only uid0 cant be By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.

Also generation of UIDs is usually not made in Crypographically friendly way e.

NTAG 216 – ISO 14443 – part 4

Am I right or did I miss something? I 14434-3 agree, this is a bad thing tm to be in a standard. I’d like to understand why the ISO standard describes two types of interfaces, type A and type B. Sign up using Email and Password. Sign up using Facebook.

  BIOMECANICA DEL MOVIMIENTO DENTARIO PDF

nfc – ISO anti-collision protocol is not correct – Stack Overflow

I would expect though I did not check that this is also the case for the version of the standard. Sign up using Email and Password. Post as a guest Name. By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your isoo use of the lso is subject to these policies.

Sign up or log in Sign up using Google. Some limitations quickly occurred: This answer talks about competing technologies brought forward by uso different companies: Look at hash functions, for example. Could you re-phrase this sentence: Or even detect that it happend. The Innovatron company had working microprocessor cards, so their technology was integrated as type B in the standard.

Email Required, but never shown.

I found a nice answer to my question here: Maybe in an effort to phase out type A? At the time, type A couldn’t power up isso microprocessor continuously. This separation is not relevant anymore since you can have type A or type B memory or microprocessor cards, and we ended up with two competing technologies in the same standard.

Email Required, but never shown.

ido Sign up or log in Sign up using Google. But nevertheless it is not correct and the general director of the company I am working for will definitely come to look at what we are doing with two such cards in his wallet.

Can I find more details somewhere?