Closed Bug 891373 Opened 11 years ago Closed 6 years ago

[META] Implementing a connectivity stack for RCS/RTC

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: tauzen, Unassigned)

Details

(Keywords: feature) 

User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36

Steps to reproduce:

We would like B2G to support RCS-e (Rich Communication Services enhanced, see RCS 1.2.2 UNI spec at http://www.gsma.com/rcs/specifications).   

To achieve this we would like to implement a RCS/RTC connectivity stack, expose its functionalities as a WebAPI and introduce suitable changes in Gaia. The propsed WebAPI could be also used by developers to use real time communication functions (capability check, instant messaging, file transfer) in their web apps.
blocking-b2g: --- → 1.3?
Keywords: feature
Summary: Implementing a connectivity stack for RCS/RTC → [META] Implementing a connectivity stack for RCS/RTC
I will extract the requirements relating to RCS and post in here. We can use that as part of the review together with the prioritized user stories.
Not a committed feature for 1.3, so clearing nom.
blocking-b2g: 1.3? → ---
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.