--- title: CP Rights Charter tags: [Overview] --- # CP Rights Charter **Connected Services Framework (CSF) — Your Rights as a Communications Provider** Version 2.0 | Published by the Telecom Technical Architecture Group (TAG) --- ## What This Document Is This charter sets out your rights as a Communications Provider (CP) participating in the Connected Services Framework (CSF). It is written in plain language so you can understand what the framework guarantees you — without needing to read the full CSF technical specification. The CSF is the open, free-to-use transport framework that enables your messages (such as Switching for Business requests) to be exchanged securely between you and other CPs through Managed Access Providers (MAPs). **If you use a MAP to send and receive switching messages, these rights apply to you.** --- ## Your Rights ### 1. The right to choose your MAP You are free to choose which MAP you use. No MAP may impose technical or commercial barriers that prevent you from selecting the provider that best meets your needs. You are also free to become your own MAP (a "MAP of 1") and exchange messages directly with the industry. ### 2. The right to change your MAP You can move to a different MAP at any time, subject only to your normal commercial contract terms with your current MAP. No MAP may actively prevent you from moving to a new provider or deliberately obstruct the transition. ### 3. No disruption during a MAP change When you move to a new MAP, your RCPID (your unique identity in the switching network) stays with you — it does not change. Your in-flight switching orders are transferred to your new MAP through a standardised export process, so your end customers are not affected by the move. ### 4. You control your identity Your association with your MAP is recorded in your own DNS records — records that you control, not your MAP. By updating two DNS entries, you determine which MAP is authorised to send messages on your behalf. No MAP can override this — the CSF verifies your DNS records before processing any message. > **CSF Best Practice — keep DNS management in-house.** A CP SHOULD NOT delegate management of these DNS records (or the wider DNS zone they live in) to its MAP. If a CP hands DNS control to its MAP, the CP could lose practical control over **who supplies its switching services** — moving to a different MAP, or becoming a [MAP of 1](part1-framework/04-architecture-overview.md), then requires cooperation from the very MAP the CP wishes to leave. Keep DNS with the CP (or with an independent DNS provider the CP has its own commercial relationship with) so that the right to change MAP remains exercisable unilaterally. ### 5. Your RCPID is yours for life Your RCPID is allocated to your brand permanently. It follows you if you change MAP, and it remains consistent across all historical records, reporting, and in-flight orders. No MAP can reassign, revoke, or alter your RCPID. ### 6. No charges for message exchange No MAP may charge you — or any other CP — for the routing and connectivity of messages between MAPs. The CSF is free to operate. Your commercial relationship with your MAP for their services (portal, integration, support) is separate and between you and your MAP, but the act of exchanging messages across the CSF network carries no transaction fees or levies. ### 7. You control your visibility You can choose your service status in the MAP's registry at any time, regardless of your account status with the MAP: - **ACTIVE** — you are live and available for switching - **TEST** — you are onboarding or testing and will not appear in other CPs' switching lists - **SUSPENDED** — you are temporarily unavailable for new switching activity ### 8. Your messages are delivered securely Every message sent on your behalf is digitally signed using your own cryptographic key pair (DKIM/PKI). The receiving MAP verifies this signature before processing the message. This means: - No one can alter your message in transit without detection - No one can send a fraudulent message pretending to be you - Only the MAP you have authorised (via your DNS records) can sign messages on your behalf ### 9. Your contact details are protected Your operational contact information (phone, email, support URLs) is stored in the CP Registry and is only accessible to other MAPs and CPs via secure, authenticated connections. It is never publicly available and must not be shared with end consumers. ### 10. You have a voice You have the right to raise concerns, provide feedback, or propose improvements to the CSF — either directly to the TAG or through your MAP. The TAG steering group meets weekly and is committed to representing the interests of all participants. --- ## What Your MAP Must Do For You Your MAP has obligations under the CSF framework. These include: | Obligation | What it means for you | |---|---| | **Guaranteed delivery** | Your MAP must deliver your messages reliably, with retry mechanisms and failure reporting if delivery fails | | **Accurate registry** | Your MAP must keep your information in the CP Registry accurate and up-to-date in near-real time | | **Security** | Your MAP must sign your messages with your private key, verify inbound messages, and maintain TLS 1.3 encryption on all connections | | **Connectivity** | Your MAP must maintain connections with all other MAPs so your messages can reach any CP in the network | | **In-flight order export** | If you leave your MAP, they must provide a standardised export of all your in-flight switching orders so your new MAP can continue processing them without disruption | | **No lock-in** | Your MAP must not prevent you from moving to another MAP or obstruct the transition process | | **SLA compliance** | Your MAP must meet the service-level agreements defined by the TAG for MAP-to-MAP activity | --- ## What Your MAP Must Not Do | Prohibited action | Why it matters | |---|---| | **Block your move** to another MAP | You are free to change provider at any time | | **Charge other MAPs** for routing your messages | Message exchange across the CSF is free | | **Withhold your in-flight orders** when you leave | Your switching orders must be exported to your new MAP | | **Misuse your data** from the CP Registry for marketing or customer solicitation | Registry data is for operational purposes only | | **Refuse to process losses** if you are suspended or in administration | In-flight orders transferring customers away from you must still be processed | | **Alter your messages** after you have submitted them | Your messages are digitally signed and any tampering is detected | --- ## If Something Goes Wrong ### Your MAP is not meeting its obligations 1. **Raise it with your MAP directly** — use the support contacts published in the CP Registry 2. **Escalate to the TAG** — if your MAP does not resolve the issue, you can raise it with the TAG steering group (via your MAP or directly) 3. **Move to another MAP** — you always have the right to change MAP; your RCPID and in-flight orders move with you ### Your MAP goes into administration or fails The CSF has built-in protections: - You can migrate to a new MAP, typically within hours - Your RCPID stays the same — no reregistration needed - Your in-flight orders are exported (if the old MAP is still online) or can be reconstructed from your records and the other MAPs involved - Other MAPs will detect the change automatically and route messages to your new MAP ### You believe a MAP is acting anti-competitively The TAG has governance controls including dispute resolution, anti-competitive safeguards, and the ability to warn, suspend, or remove MAPs that breach their obligations. Report concerns to the TAG steering group. --- ## Key Terms (Plain Language) | Term | What it means | |---|---| | **CP** | Communications Provider — that's you. Any organisation that sends or receives switching messages. | | **MAP** | Managed Access Provider — the organisation that handles the technical side of sending and receiving messages on your behalf. | | **RCPID** | Your unique identity in the switching network. It's a code (UUIDv4) that other CPs use to address messages to you. It stays with you for life. | | **CP Registry** | The list your MAP publishes containing your details (brand name, RCPID, contact information, supported processes). Other MAPs collect this to know you exist and how to reach you. | | **DNS records** | Internet records that you control. Two DNS entries link your RCPID to your MAP — this is how you control who represents you in the network. | | **DKIM/PKI signing** | A security mechanism that digitally signs every message sent on your behalf, so the recipient can verify it genuinely came from you and hasn't been tampered with. | | **In-flight order** | A switching order that has been submitted but not yet completed. If you change MAP, these are transferred to your new MAP so your customers aren't affected. | | **TAG** | The Telecom Technical Architecture Group — the industry group that maintains the CSF. They meet weekly and are responsible for the rules that protect your rights. | --- ## Further Information This charter summarises your rights under the Connected Services Framework. The full technical specification is available in the CSF documentation: - [CSF Overview and Documentation Index](README.md) - [Principles & Requirements](part1-framework/03-principles-and-requirements.md) — the formal requirements this charter is derived from - [CP Transitions](part2-implementation/07-cp-transitions.md) — how the MAP change process works technically - [Commercial Scenarios](part2-implementation/08-commercial-scenarios.md) — what happens if a MAP fails or a CP enters administration - [Definitions & Terminology](definitions.md) — full glossary of all CSF terms --- *This charter is maintained by the TAG and will be updated as the CSF evolves. If you have questions or feedback, contact the TAG through your MAP or directly via the TAG steering group.*