Core
====
-- connman_element removal
-
- Priority: Low
- Complexity: C8
-
-
-- DHCP lib
+- Session API implementation
Priority: High
- Complexity: C8
- Owner: Martin Xu <martin.xu@intel.com>
+ Complexity: C4
+ Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
+ Owner: Samuel Ortiz <sameo@linux.intel.com>
+ The session API should provide a connection abstraction in order to
+ prioritize applications network accesses, prevent or allow network
+ and bearer roaming, or provide applications with a way to request
+ for periodic network connections. On-demand connections will be
+ implemented through this API as well.
+ See http://www.mail-archive.com/connman@connman.net/msg01653.html
-- IPv6
- Priority: High
+- DNS caching
+
+ Priority: Low
Complexity: C4
- Dependencies: Core:DHCP Lib
- Owner: Martin Xu <martin.xu@intel.com>
+ A simple initial implementation would see ConnMan's dnsproxy
+ caching the DNS record based on their TTL.
-- On demand connection
+
+- Power management
Priority: Medium
Complexity: C4
Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Implement a simple device pm hook that ConnMan's core code would
+ use whenever it decides to put devices in power save mode. Although
+ the kernel runtime power management code should take care of that,
+ not all driver (especially WiFi ones) implement runtime PM hooks.
-- Avahi-zeroconf
- Priority: Medium
- Complexity: C4
+- IP ranges allocation and check
+
+ Priority: High
+ Complexity: C2
+ For both tethering and private networks, but also to detect invalid
+ static IP configurations, we need to have a core IP range layer
+ that manages all currently used IP blocks.
-- OpenVPN
+
+- Personal firewall
Priority: Low
- Complexity: C2
+ Complexity: C8
+ Owner: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
+
+ Discuss and implement a basic and safe firewalling strategy into
+ Connman. Provide a D-Bus API for personal firewalling.
-- VPNc
+- PACRunner extensions
Priority: Low
- Complexity: C2
+ Complexity: C4
+ Support more URI schemes, support multiple connections, tighter
+ security integration.
-- Tethering
- Priority: Medium
- Complexity: C8
+WiFi
+====
-- WAPD - Web Proxy Autodiscovery Protocol
+- Ad-Hoc support
Priority: Medium
Complexity: C2
- Dependencies: Core:HTTP proxy
+ Owner: Samuel Ortiz <sameo@linux.intel.com>
-- Agent callbacks
+- Fast Connect
- Priority: Medium
- Complexity: C2
+ Priority: Low
+ Complexity: C4
+ Owner: Samuel Ortiz <sameo@linux.intel.com>
-- HTTP proxy
+- EAP-AKA/SIM
Priority: Medium
- Complexity: C1
-
-
+ Complexity: C2
+ Owner: Samuel Ortiz <sameo@linux.intel.com>
+ This EAP is needed for SIM card based network authentication.
+ ConnMan here plays a minor role: Once wpa_supplicant is set up for
+ starting and EAP-AKA/SIM authentication, it will talk to a SIM card
+ through its pcsc-lite API.
-WiFi
-====
-- WPS
+- EAP-FAST
Priority: Low
- Complexity: C2
- Dependencies: Core:Agent callbacks
+ Complexity: C1
-- Ad-Hoc support
+- WiFi p2p
Priority: Medium
Complexity: C2
- Dependencies: Core:Avahi-zeroconf
-- libsupplicant
- Priority: Medium
- Complexity: C4
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+Bluetooth
+=========
-- Fast Connect
+- DUN client
Priority: Low
Complexity: C4
- Dependencies: WiFi:libsupplicant
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Owner: Mario Tokarz <mario.tokarz@bmw-carit.de>
-- TTLS EAP support
- Priority: Low
- Complexity: C2
+Cellular
+========
-Bluetooth
-=========
-- DUN client
+VPN
+===
+
+- IPsec
Priority: Low
Complexity: C4
+
+
+- Split tunnelling
+
+ Priority: Low
+ Complexity: C8
+ Dependencies: Core:Private networks
+
+ The current VPN support puts the VPN interface at the top of the
+ service list, giving VPNs the default route. When doing split
+ tunneling, the system routes packet to the VPN interface for
+ private IPs, while going through the default interface for the rest
+ of the traffic.
projects / framework / connectivity / connman.git / blobdiff