815554 - (b2g-oma-cp) [meta] Firefox OS 1.2 Client Provisioning feature

Status: RESOLVED FIXED

(Firefox OS Graveyard :: General, defect)

Description

[Daniel Coloma:dcoloma]

Boot2Gecko should support a way to provisioning the device settings OTA. This is very helpful, for instance, in order to support virtual operators.

Comment 1

[Chris Lee [:clee]]

This is a v1+ feature we'd like to add.  Nom'ing so we can triage accordingly.

Comment 2

[Andrew Overholt [:overholt]]

(In reply to Chris Lee [:clee] from comment #1)
> This is a v1+ feature we'd like to add.  Nom'ing so we can triage
> accordingly.

So this is post-v1?  If so, we should - this.  If this is for v1 itself, I don't think we should increase the scope of v1 at this point.

Comment 3

[Beatriz Rodríguez [:brg]]

We agreed this is a post-V1 feature.

Comment 4

[Chris Lee [:clee]]

This is post-v1.

Comment 5

[José Antonio Olivera Ortega [:jaoo]]

This is a meta for tracking OMA Client Provisioning bugs. Releasing tracking flags since this is a meta bug.

Comment 6

[Ken Chang[:kenkai]]

Change the title to track this feature for 1.2

Comment 7

[Ken Chang[:kenkai]]

Please provide the items what we need to configure via OMA-CP.

Comment 8

[Bruce Huang [:bhuang] (inactive)]

(In reply to Ken Chang from comment #7)
> Please provide the items what we need to configure via OMA-CP.

My thoughts on this is we should provide a "generic" implementation.  This means we enable the protocol, but allow partners to customize depending on the settings that each operator would like to provision.  

I've linked a few stories to this:
bug 898994: Enabling OMA CP protocol
bug 898997: Define a mechanism for OEMs to receive the provisioning request and write to settings accordingly