Resources
Identity Use Cases & Scenarios.- FIDIS Deliverables.
- Identity of Identity.
- Interoperability.
- Profiling.
- Forensic Implications.
- HighTechID.
- D3.1: Overview on IMS.
- D3.2: A study on PKI and biometrics.
- D3.3: Study on Mobile Identity Management.
- D3.5: Workshop on ID-Documents.
- D3.6: Study on ID Documents.
- D3.7: A Structured Collection on RFID Literature.
- D3.8: Study on protocols with respect to identity and identification – an insight on network protocols and privacy-aware communication.
- D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management.
- D3.10: Biometrics in identity management.
- D3.11: Report on the Maintenance of the IMS Database.
- D3.15: Report on the Maintenance of the ISM Database.
- D3.17: Identity Management Systems – recent developments.
- D12.1: Integrated Workshop on Emerging AmI Technologies.
- D12.2: Study on Emerging AmI Technologies.
- D12.3: A Holistic Privacy Framework for RFID Applications.
- D12.4: Integrated Workshop on Emerging AmI.
- D12.5: Use cases and scenarios of emerging technologies.
- D12.6: A Study on ICT Implants.
- D12.7: Identity-related Crime in Europe – Big Problem or Big Hype?.
- D12.10: Normality Mining: Results from a Tracking Study.
- Privacy and legal-social content.
- Mobility and Identity.
- Other.
- IDIS Journal.
- FIDIS Interactive.
- Press & Events.
- In-House Journal.
- Booklets
- Identity in a Networked World.
- Identity R/Evolution.
D3.3: Study on Mobile Identity Management
 |
Study on Mobile Identity Management COMPARISON OF ANONYMOUS COMMUNICATION MECHANISMS |
 |
Therefore, we can summarise the comparison of the anonymity mechanisms applied in ad hoc networks in the following table. The table contents correspond to a brief summary of the analysis of the mechanisms.
| Crowds | Tarzan | MorphMix | Hordes |
Performance | DH between Crowds nodes -in the newest Crowds version | ( L )2 messages needed, dummy traffic and ( L ) public key operations | 6*L+2*∑(i-1) messages,(4*L) public key operations and ( L ) DH | DH between Hordes nodes |
Scalability | Depends on the blender (server) may scale well | May not scale well in large and dynamic networks | Not exactly clear | Different paths from forward and reverse traffic increases scalability |
Security | Depends on the probability (pf) of forwarding messages | Initiator sets the anonymous tunnel path | Collusion detection mechanism | Depends on the number of nodes in each multicast group |
Robustness | Tunnel path is rebuild from the broken link | The broken part of the tunnel path is rebuild | The whole tunnel shall be rebuild | Forward path is Crowd similar. reverse path is multicast based |
Independent of a deployed infrastructure | No, blender is a directory server | Yes | Apparently yes, but not exactly clear | Membership is controlled by a central server |
| |
   |
|
| 27 / 36 |
