4 - Priority scale: High, Medium and Low
6 - Complexity scale: C1, C2, C4 and C8.
7 The complexity scale is exponential, with complexity 1 being the
8 lowest complexity. Complexity is a function of both task 'complexity'
18 Dependencies: Core:NDEF building library
19 Owner: Samuel Ortiz <sameo@linux.intel.com>
21 In card emulation mode, the NFC adapter is in passive mode, and gets
22 activated by an initiator mode device. Then the initiator sends command
23 that the target is supposed to interpret and respond to. Most of the
24 commands are tag specific.
25 For a proper card emulation mode support, the NFC adapter must enter the
26 polling loop and not only initiate the RF field, but then wait for intiator
27 to activate it. Once activated, the NFC socket should enter the accept
28 state, and dispatch the various commands to the right plugins (one per
29 protocol, a.k.a. tags).
35 Owner: Samuel Ortiz <sameo@linux.intel.com>
37 Packaging for both RPM packages based distributions should be done in order
38 to push neard into the mainstream Linux distributions.
44 Owner: Samuel Ortiz <sameo@linux.intel.com>
52 NDEF code (Handover related in particular) should be splitted into parsing and
53 acting part. This would make code easier to follow and would also allow to
54 run unit tests on parsing part.
64 - MIFARE writer mode support
68 Owner: Dorota Moskal <dorota.moskal@tieto.com>
74 - SNEP and LLCP validation tests
78 Owner: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
80 Implement SNEP validation test cases as an optional neard plugin, and
81 LLCP ones as a set of tools/ binaries.
87 Owner: Samuel Ortiz <sameo@linux.intel.com>
89 Microsoft handover implementation does not follow the NFC Forum specs.
92 http://msdn.microsoft.com/en-us/library/ee941641
94 In order to support this handover implementation, a specific plugin
95 should be implemented as there is no overlap between it and the NFC
102 Owner: Olivier Guiter <olivier.guiter@intel.com>
104 PHDC (Personal Health Device Communication) is a protocol on top of LLCP
105 for exchanging ISO/IEEE 11073 PDUs. It has its own LLCP service name and
106 as such could be implemented as a p2p plugin.
107 The PHDC plugin would define its own D-Bus interface for the PHDC Manager