MIFARE Application Directory (MAD)

 Mifare DESFire EV1 2K,Mifare DESFire EV1 2K Offset Printing Cards,Mifare DESFire EV1 2K Proximity Contactless Cards,

The MIFARE Application Directory standard proposes the introduction of common data structures for card application directory entries. Registered application identifiers (AIDs) in sector 0×00 (and sector 0×10, if applicable) of any MIFARE card enable identification of all registered card applications. Terminal software should take advantage of this feature using those sector pointers instead of physical sector addresses. In the future it might easily happen that there are more than one MIFARE card in a person’s wallet. The comfort of not having to take out the card of one’s wallet should be possible also with more MIFARE cards in one wallet. A typical case can be that one person has cards for different applications (e.g. airline miles collection and city fare collection). With the MAD the airline check-in terminal identifies two cards and is able to choose the correct one very fast, simply by checking the MAD.

The MAD version 1, 2 and 3.
MAD1 is limited to 16 Sectors (as used in MIFARE Classic).
MAD2 specifies the usage of the MIFARE with a memory >1k (e.g. MIFAREPro and
MIFARE ProX, MIFARE 4k, etc.).
MAD2 is fully compatible to the MAD1, i.e. an MAD1 system can use cards, that use
MAD2 without any changes. In this case only the lower 1k EEPROM can be addressed.             

MAD3 specifies the usage of Registered application identifiers in the context of MIFARE
Observing the following proposed MIFARE Application Directory rules following
proposed opens a lot of future benefits: 

Table 1. Future benefits    
basic requirements ⇒ additional information ⇒ additional flexibility
• reserve 2 blocks in sector
0(and also reserve 3
blocks in sector 16 for
• keep the given format
• request for AID[1]
• use public read-key for
sector 0
• use secret write-key for
sector 0
• use indirect addressing
mode in terminal program
⇒identify any application on
any MIFARE card together with
the sectors in use
⇒identify card issuer
⇒identify free or blocked sector
⇒already existing MIFARE
cards may serve for new
additional applications
⇒already existing MIFARE
applications on multiple cards
may be combined on one single
⇒easy adaptation of memory
structure in case of additional
features or blocked sectors
[1] AID application identifier request form can be found in annex A