diff options
author | Samuel Ortiz <sameo@linux.intel.com> | 2011-04-04 19:21:27 +0200 |
---|---|---|
committer | Samuel Ortiz <sameo@linux.intel.com> | 2011-04-04 19:21:27 +0200 |
commit | 686b3102882d10a497fe5d22fd936b869a7ef71e (patch) | |
tree | ac233386702375fa5ec58bb7363990e6e25faff4 /TODO | |
parent | a889946d31adf60b9f28ec6fe62ac5c37dd148a0 (diff) | |
download | connman-686b3102882d10a497fe5d22fd936b869a7ef71e.tar.gz connman-686b3102882d10a497fe5d22fd936b869a7ef71e.tar.bz2 connman-686b3102882d10a497fe5d22fd936b869a7ef71e.zip |
TODO update
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 114 |
1 files changed, 103 insertions, 11 deletions
@@ -53,6 +53,76 @@ Core credentials, ConnMan should be able to initiate a WiSPR authentication. +- DNS caching + + Priority: Low + Complexity: C4 + + A simple initial implementation would see ConnMan's dnsproxy + caching the DNS record based on their TTL. + + +- 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. + + +- IPv6 gateway handling + + Priority: Medium + Complexity: C4 + + We should be able to switch between IPv6 only services and thus + change the default IPv6 gateway on the fly. For that we need to + improve the connection.c code to properly handle IPv6 gateways. + + +- 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. + + +- Personal firewall + + Priority: Low + Complexity: C8 + + Extend the iptables code and provide a D-Bus API for personal firewalling. + + +- PACRunner extensions + + Priority: Low + Complexity: C4 + + Support more URI schemes, support multiple connections, tighter + security integration. + + +- Private networks + + Priority: Medium + Complexity: C4 + + The private networks D-Bus API should provide applications with a + TUN interface linked to a reserved private IP range. + oFono DUN forwarding will use a private network for giving DUN + clients access to the default service connectivity. + + + WiFi ==== @@ -60,7 +130,6 @@ WiFi Priority: Medium Complexity: C2 - Dependencies: Core:IPv4LL Owner: Samuel Ortiz <sameo@linux.intel.com> @@ -103,25 +172,29 @@ WiFi Complexity: C2 -- DUN server + +Bluetooth +========= + +- DUN client Priority: Low Complexity: C4 - Owner: Samuel Ortiz <sameo@linux.intel.com> - For DUN server support, ConnMan needs to provide an API for oFono - to trigger IP forwarding on a point to point interface. An IP range - should also be reserved. +Cellular +======== -Bluetooth -========= +- IPv6 and IPv6v4 cellular data connection -- DUN client + Priority: Medium + Complexity: C2 + Owner: Samuel Ortiz <sameo@linux.intel.com> + + Support IPv6 and dual stack cellular data connections. + oFono already supports it and provide an extensive D-Bus API for it. - Priority: Low - Complexity: C4 VPN @@ -139,3 +212,22 @@ VPN Priority: Low Complexity: C2 Owner: Mohamed Abbas <mohamed.abbas@intel.com> + + +- 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. |