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 We should extend the handover API for support Wi-Fi as well, and implement
38 the neard Wi-Fi handover agent from network manager components
45 Owner: Samuel Ortiz <sameo@linux.intel.com>
51 Owner: Samuel Ortiz <sameo@linux.intel.com>
53 Packaging for both RPM and Debian packages based distributions should
54 be done in order to push neard into the mainstream Linux distributions.
60 Owner: Samuel Ortiz <sameo@linux.intel.com>
70 - MIFARE writer mode support
74 Owner: Dorota Moskal <dorota.moskal@tieto.com>
80 - Bluetooth Handover integration
84 Dependencies: Core:Handover Agent API
85 Owner: Olivier Guiter <olivier.guiter@linux.intel.com>
87 The handover integration has to be done between bluetoothd, obexd and
88 neard. Obexd or BlueZ should be able to call a handover requester
89 org.neard.Manager method to send an Hr to a remote peer. This asynchronous
90 method will return upon reception of an Hs record. This is when BlueZ
91 will be able to initiate the pairing.
92 On the other hand, neard should be able to get the appropriate OOB data
93 from BlueZ through the handover agent API, and build an Hs to send to
94 the handover requester. The latter will then initiate the pairing.
96 - SNEP and LLCP validation tests
100 Owner: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
102 Implement SNEP validation test cases as an optional neard plugin, and
103 LLCP ones as a set of tools/ binaries.
109 Owner: Samuel Ortiz <sameo@linux.intel.com>
111 Microsoft handover implementation does not follow the NFC Forum specs.
112 It is specified here:
114 http://msdn.microsoft.com/en-us/library/ee941641
116 In order to support this handover implementation, a specific plugin
117 should be implemented as there is no overlap between it and the NFC
124 Owner: Samuel Ortiz <sameo@linux.intel.com>
126 PHDC (Personal Health Device Communication) is a protocol on top of LLCP
127 for exchanging ISO/IEEE 11073 PDUs. It has its own LLCP service name and
128 as such could be implemented as a p2p plugin.
129 The PHDC plugin would define its own D-Bus interface for both the PHDC
130 Manager and Agent roles.