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'
14 - connman_element removal
18 Owner: Samuel Ortiz <sameo@linux.intel.com>
25 Owner: Julien Massot <jmassot@aldebaran-robotics.com>
27 The IPv4 Link Local support should be integrated into DHCP-lib.
28 IPv4LL should be started when DHCP failed, and then DHCP should
29 be scheduled for periodic trials.
30 Also, there should be no default route going through an IPv4LL
44 Owner: Patrik Flykt <patrik.flykt@nokia.com>
46 Implement Agent API according to doc/agent-api.txt
49 - Moving DNS proxy code to ConnMan core
54 Supporting DNS proxy or resolv.conf direct editing seems more than
55 plenty as far as resolving is concerned. So the idea is to move the
56 dnsproxy plugin code to ConnMan core and have an additional command
57 line option in case one would like to stick with the current
58 resolver.c code for editing resolv.conf.
65 WiFi tethering should be done through an extended wpa_supplicant
66 D-Bus API, as STA and AP modes are typically mutually exclusive.
69 - Session API implementation
73 Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
74 Owner: Samuel Ortiz <sameo@linux.intel.com>
76 The session API should provide a connection abstraction in order to
77 prioritize applications network accesses, prevent or allow network
78 and bearer roaming, or provide applications with a way to request
79 for periodic network connections. On-demand connections will be
80 implemented through this API as well.
81 See http://www.mail-archive.com/connman@connman.net/msg01653.html
84 - Provisioning D-Bus API
88 Owner: Lucio Maciel <lucio.maciel@hp.com>
90 The current service provisioning lacks inotify support for adding
91 new provision files on the fly, and a D-Bus interface for modifying
99 Owner: Marcel Holtmann <marcel@holtmann.org>
101 Based on the portal detection parsing results, and provisioned
102 credentials, ConnMan should be able to initiate a WiSPR authentication.
112 Dependencies: Core:Agent callbacks
119 Dependencies: Core:IPv4LL
120 Owner: Samuel Ortiz <sameo@linux.intel.com>
127 Owner: Samuel Ortiz <sameo@linux.intel.com>
134 Owner: Samuel Ortiz <sameo@linux.intel.com>
136 This EAP is needed for SIM card based network authentication.
137 ConnMan here plays a minor role: Once wpa_supplicant is set up for
138 starting and EAP-AKA/SIM authentication, it will talk to a SIM card
139 through its pcsc-lite API.
160 - WiFi CRDA setting through 3G country
164 Owner: Samuel Ortiz <sameo@linux.intel.com>
166 Setting the 802.11 country based on the 3G MNC/MCC.