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>
21 - Session API implementation
25 Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
26 Owner: Samuel Ortiz <sameo@linux.intel.com>
28 The session API should provide a connection abstraction in order to
29 prioritize applications network accesses, prevent or allow network
30 and bearer roaming, or provide applications with a way to request
31 for periodic network connections. On-demand connections will be
32 implemented through this API as well.
33 See http://www.mail-archive.com/connman@connman.net/msg01653.html
36 - Provisioning D-Bus API
40 Owner: Henri Bragge <henri.bragge@ixonos.com>
42 The current service provisioning lacks a D-Bus interface for modifying
43 existing configurations.
50 Owner: Marcel Holtmann <marcel@holtmann.org>
52 Based on the portal detection parsing results, and provisioned
53 credentials, ConnMan should be able to initiate a WiSPR authentication.
61 A simple initial implementation would see ConnMan's dnsproxy
62 caching the DNS record based on their TTL.
69 Owner: Samuel Ortiz <sameo@linux.intel.com>
71 Implement a simple device pm hook that ConnMan's core code would
72 use whenever it decides to put devices in power save mode. Although
73 the kernel runtime power management code should take care of that,
74 not all driver (especially WiFi ones) implement runtime PM hooks.
77 - IPv6 gateway handling
82 We should be able to switch between IPv6 only services and thus
83 change the default IPv6 gateway on the fly. For that we need to
84 improve the connection.c code to properly handle IPv6 gateways.
87 - IP ranges allocation and check
92 For both tethering and private networks, but also to detect invalid
93 static IP configurations, we need to have a core IP range layer
94 that manages all currently used IP blocks.
102 Extend the iptables code and provide a D-Bus API for personal firewalling.
105 - PACRunner extensions
110 Support more URI schemes, support multiple connections, tighter
111 security integration.
119 The private networks D-Bus API should provide applications with a
120 TUN interface linked to a reserved private IP range.
121 oFono DUN forwarding will use a private network for giving DUN
122 clients access to the default service connectivity.
133 Owner: Samuel Ortiz <sameo@linux.intel.com>
140 Owner: Samuel Ortiz <sameo@linux.intel.com>
147 Owner: Samuel Ortiz <sameo@linux.intel.com>
149 This EAP is needed for SIM card based network authentication.
150 ConnMan here plays a minor role: Once wpa_supplicant is set up for
151 starting and EAP-AKA/SIM authentication, it will talk to a SIM card
152 through its pcsc-lite API.
159 Owner: Henri Bragge <henri.bragge@ixonos.com>
166 Owner: Henri Bragge <henri.bragge@ixonos.com>
189 - IPv6 and IPv6v4 cellular data connection
193 Owner: Samuel Ortiz <sameo@linux.intel.com>
195 Support IPv6 and dual stack cellular data connections.
196 oFono already supports it and provide an extensive D-Bus API for it.
207 Owner: Mohamed Abbas <mohamed.abbas@intel.com>
214 Owner: Mohamed Abbas <mohamed.abbas@intel.com>
227 Dependencies: Core:Private networks
229 The current VPN support puts the VPN interface at the top of the
230 service list, giving VPNs the default route. When doing split
231 tunneling, the system routes packet to the VPN interface for
232 private IPs, while going through the default interface for the rest