Scribd
Upload
531 views4 pages

RCS-next and Interoperability - Next Steps

RCS-Next is an upgraded and optimized Rich Communication Services (RCS) stack contributed by Google that supports end-to-end encryption, interoperability with over-the-top (OTT) messaging providers, and a common network-agnostic standard based on the MLS RFC 9420. Google presented RCS-Next to the GSMA and received broad support and alignment. This alignment structures an open, interoperable ecosystem for secure messaging. The document outlines proposed work items to update RCS specifications to incorporate RCS-Next.

Uploaded by

Gabriel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
531 views4 pages

RCS-next and Interoperability - Next Steps

RCS-Next is an upgraded and optimized Rich Communication Services (RCS) stack contributed by Google that supports end-to-end encryption, interoperability with over-the-top (OTT) messaging providers, and a common network-agnostic standard based on the MLS RFC 9420. Google presented RCS-Next to the GSMA and received broad support and alignment. This alignment structures an open, interoperable ecosystem for secure messaging. The document outlines proposed work items to update RCS specifications to incorporate RCS-Next.

Uploaded by

Gabriel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Confidential

RCS-Next and Interoperability Standardisation Framework for


Interpersonal Communication
July 2023
Confidential

RCS-Next and Interoperability Overview

● Google presented the ‘RCS Next’ proposal to the GSMA Global Specification Group on June
22nd 2023, which was also attended by members from the IETF MIMI group.

● There was broad support and alignment on:

i. An upgraded and optimised RCS stack - ‘RCS-Next’ - contributed by Google

ii. A common, network agnostic, e2ee standard based on the MLS RFC [9420]

iii. An OTT messaging discovery and interoperability protocol defined by MIMI

● This alignment structures an open, interoperable ecosystem supporting safe, confidential and
secure messaging.

● This paper summarises this alignment, new specification documentation for RCS-Next and
related RCS documentation changes.
Confidential
RCS-Next & Interoperability Specification Alignment with IETF

IETF MLS [RFC 9420] for End-to-End Encryption

GSMA RCS Specifications

Universal Profile Requirements RCC.71 Update

RCS device config RCC.14 Update RCC.14 IETF MIMI

RCS-Next UNI API OTT Discovery RCS


RCS
UNI RCC.07
OTT Messaging
RCS-Next RCC.07 Interworking Payload Providers

Ecosystem Principles WA.09 Update WA.09 Transport

Fraud & Security FS.41 Update FS.41


Candidate RCS-Next NNI to be
evaluated
RCS Interworking IR.90 RCS-Next IR.90 Interworking

E2E Test Spec RCC.17 RCS-Next Test Environment


* RCS-Next specification work items
Confidential

RCS-Next Proposed Work Items

Work Item Description Owner Due

Google to evaluate pending CRs for ‘reactions’ and ‘suggested’ reply PDTF /
1 Universal Profile Requirements RCC.71 Update TBC
requirements and supporting RCC.07 and RCS-Next specs. GSMA

Tighten security model and make TS.43 mandatory for carrier RCS
2 Service Provider Device Config [RCC.14 / 71] GSG TBC
services and SIM enabled devices.

RCS-Next API Specification comprising: gRPC methods, protocol buffer


3 RCS-Next UNI API Specification Google Sept’ 23
RCS schema and QUIC [RFC 9000] transport.

4 RCS-Next Interworking RCS-Next Interworking Guidelines for RCC.07 and RCC.90 Google TBC

Update p2p principles: deprecate RCC.63, RCC.59, RCC.66


‘pre-Universal Profile support’, RCC.53 Device APIs and RCS MoU
5 RCS Ecosystem Principles [WA.09] WAS TBC
WA.08. Add appropriate references to RCS-Next as an alternative to
RCC.07.

Section 4.3, ‘RCS P2P Traffic Control’ needs updating to reflect p2p
7 RCS Fraud & Security Assessment [FS.41] RCS-Next SIM based auth and e2ee. Separately, requires updating to FASG TBC
reflect the current state of operations for RCS Business Messaging.

8 RCS-Next Test Environment Google supported UNI and NNI test environment Google Q1 2024

You might also like