1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
|
Background
==========
- Priority scale: High, Medium and Low
- Complexity scale: C1, C2, C4 and C8.
The complexity scale is exponential, with complexity 1 being the
lowest complexity. Complexity is a function of both task 'complexity'
and task 'scope'.
Core
====
- Session API implementation
Priority: High
Complexity: C4
Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
Owner: Patrik Flykt <patrik.flykt@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
- IP ranges allocation and check
Priority: High
Complexity: C2
Guillaume Zajac <guillaume.zajac@linux.intel.com>
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
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.
- PACRunner extensions
Priority: Low
Complexity: C4
Support more URI schemes, support multiple connections, tighter
security integration.
WiFi
====
- EAP-AKA/SIM
Priority: Medium
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.
- EAP-FAST
Priority: Low
Complexity: C1
- Wireless background scan
Priority: Medium
Complexity: C4
Owner: Samuel Ortiz <sameo@linux.intel.com>
While connected ConnMan should offload the background scanning to
wpa_supplicant. Wpa_supplicant allows for a fancy background scan
which frequency increases after the current connection signal level
drops below a defined threshold.
We should also be able to have wpa_supplicant do the background
scanning for us when we're not connected, if we have configured our
favorite networks.
- WiFi p2p
Priority: Medium
Complexity: C2
Bluetooth
=========
- DUN client
Priority: Low
Complexity: C4
Owner: Mario Tokarz <mario.tokarz@bmw-carit.de>
Cellular
========
VPN
===
- IPsec
Priority: Medium
Complexity: C4
Owner: Jukka Rissanen <jukka.rissanen@linux.intel.com>
- Split tunnelling
Priority: Low
Complexity: C8
Dependencies: Core:Private networks
Owner: Jukka Rissanen <jukka.rissanen@linux.intel.com>
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.
Tools
=====
- Command line tool
Priority: Low
Complexity: C4
Owner: Patrik Flykt <patrik.flykt@linux.intel.com>
For platforms not running python, it could prove useful to provide them
with a native single binary command line tool.
User Interface
==============
- GNOME3 UI
Priority: Low
Complexity: C4
Owner: Alok Barsode <alok.barsode@linux.intel.com>
A GNOME3 shell user interface would make it easier for mainstream distros
users to use ConnMan.
|
