Core
====
-- connman_element removal
-
- Priority: Low
- Complexity: C8
- Owner: Samuel Ortiz <sameo@linux.intel.com>
-
-
-- IPv4LL
+- Session API implementation
- Priority: Medium
+ Priority: High
Complexity: C4
- Owner: Julien Massot <jmassot@aldebaran-robotics.com>
+ Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
+ Owner: Samuel Ortiz <sameo@linux.intel.com>
- The IPv4 Link Local support should be integrated into DHCP-lib.
- IPv4LL should be started when DHCP failed, and then DHCP should
- be scheduled for periodic trials.
- Also, there should be no default route going through an IPv4LL
- interface.
+ 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
-- VPNc
+- DNS caching
Priority: Low
- Complexity: C2
-
-
-- Agent callbacks
-
- Priority: Medium
- Complexity: C2
- Owner: Patrik Flykt <patrik.flykt@nokia.com>
-
- Implement Agent API according to doc/agent-api.txt
-
-
-- Moving DNS proxy code to ConnMan core
+ Complexity: C4
- Priority: Medium
- Complexity: C2
+ A simple initial implementation would see ConnMan's dnsproxy
+ caching the DNS record based on their TTL.
- Supporting DNS proxy or resolv.conf direct editing seems more than
- plenty as far as resolving is concerned. So the idea is to move the
- dnsproxy plugin code to ConnMan core and have an additional command
- line option in case one would like to stick with the current
- resolver.c code for editing resolv.conf.
+- Power management
-- WiFi tethering
Priority: Medium
Complexity: C4
+ Owner: Samuel Ortiz <sameo@linux.intel.com>
- WiFi tethering should be done through an extended wpa_supplicant
- D-Bus API, as STA and AP modes are typically mutually exclusive.
+ 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.
-- Session API implementation
+- IP ranges allocation and check
Priority: High
- Complexity: C4
- Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Complexity: C2
- 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
+ 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.
-- Provisioning D-Bus API
+- Personal firewall
- Priority: Medium
- Complexity: C2
- Owner: Lucio Maciel <lucio.maciel@hp.com>
+ Priority: Low
+ Complexity: C8
+ Owner: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
- The current service provisioning lacks inotify support for adding
- new provision files on the fly, and a D-Bus interface for modifying
- existing ones.
+ Discuss and implement a basic and safe firewalling strategy into
+ Connman. Provide a D-Bus API for personal firewalling.
-- WiSPR support
+- PACRunner extensions
- Priority: Medium
+ Priority: Low
Complexity: C4
- Owner: Marcel Holtmann <marcel@holtmann.org>
- Based on the portal detection parsing results, and provisioned
- credentials, ConnMan should be able to initiate a WiSPR authentication.
+ Support more URI schemes, support multiple connections, tighter
+ security integration.
+
WiFi
====
-- WPS
-
- Priority: Low
- Complexity: C2
- Dependencies: Core:Agent callbacks
-
-
- Ad-Hoc support
Priority: Medium
Complexity: C2
- Dependencies: Core:IPv4LL
Owner: Samuel Ortiz <sameo@linux.intel.com>
through its pcsc-lite API.
-- EAP-Fast
-
- Priority: Low
- Complexity: C1
-
-
-- EAP-GTC
+- EAP-FAST
Priority: Low
Complexity: C1
Complexity: C2
-- WiFi CRDA setting through 3G country
-
- Priority: Medium
- Complexity: C2
- Owner: Samuel Ortiz <sameo@linux.intel.com>
-
- Setting the 802.11 country based on the 3G MNC/MCC.
-
Bluetooth
=========
Priority: Low
Complexity: C4
+ Owner: Mario Tokarz <mario.tokarz@bmw-carit.de>
+
-- DUN server
+Cellular
+========
+
+
+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