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
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
|
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
====
- connman_element removal
Priority: Low
Complexity: C8
Owner: Samuel Ortiz <sameo@linux.intel.com>
- IPv4LL
Priority: Medium
Complexity: C4
Owner: Julien Massot <jmassot@aldebaran-robotics.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.
- VPNc
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
Priority: Medium
Complexity: C2
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.
- WiFi tethering
Priority: Medium
Complexity: C4
WiFi tethering should be done through an extended wpa_supplicant
D-Bus API, as STA and AP modes are typically mutually exclusive.
- Session API implementation
Priority: High
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
- Provisioning D-Bus API
Priority: Medium
Complexity: C2
Owner: Lucio Maciel <lucio.maciel@hp.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.
- WiSPR support
Priority: Medium
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.
- IPv6 enhancements
Priority: High
Complexity: C8
Owner: Jukka Rissanen <jukka.rissanen@nokia.com>
Support IPv6 only networks so that system can go online even if
there is no IPv4 address. Also support more than one IPv6 address
in one device so that the addresses are reported correctly via
dbus interface. The autoconf IPv6 addresses need also some tweaking
so that system will go online properly.
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>
- Fast Connect
Priority: Low
Complexity: C4
Owner: Samuel Ortiz <sameo@linux.intel.com>
- 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
- EAP-GTC
Priority: Low
Complexity: C1
- WiFi p2p
Priority: Medium
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
=========
- DUN client
Priority: Low
Complexity: C4
- DUN server
Priority: Low
Complexity: C4
|
