DOCSLIB.ORG

RCC.07 Rich Communication Suite

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
RCC.07 Rich Communication Suite GSM Association Non-confidential Official Document RCC.07 - Rich Communication Suite - Advanced Communications Services and Client Specification Rich Communication Suite - Advanced Communications Services and Client Specification Version 12.0 16 October 2020 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Non-confidential Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice Copyright © 2020 GSM Association Disclaimer The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V12.0 Page 1 of 384 GSM Association Non-confidential Official Document RCC.07 - Rich Communication Suite - Advanced Communications Services and Client Specification Table of Contents 1 Introduction 6 1.1 RCS Principles and Vision 6 1.2 Scope 6 1.3 Definition of Terms 6 1.4 Document Cross-References 12 1.5 Differences to previous specifications 19 1.5.1 New features and procedures 20 1.5.2 Removed features and procedures 20 1.5.3 Modified features and procedures 20 2 RCS General Procedures 21 2.1 RCS architecture 21 2.2 RCS devices and client types 23 2.3 Configuration Procedures 23 2.3.1 Client configuration parameters 23 2.3.2 RCS client autoconfiguration mechanisms 24 2.4 IMS registration 29 2.4.1 General 29 2.4.2 Procedures for multidevice handling 31 2.4.3 Telephony feature tag 31 2.4.4 Services feature tags 32 2.4.5 P-CSCF discovery 33 2.4.6 IMS Flow Set Management 34 2.4.7 Loss of Registration 35 2.5 Addressing and identities 36 2.5.1 Overview 36 2.5.2 Sender Identification for Device Incoming SIP Request 36 2.5.3 Device Outgoing SIP Requests 37 2.5.4 Addressing related to Chatbots 38 2.5.5 RCS Addressing Model 41 2.6 Capability and new user discovery mechanisms 42 2.6.1 Capability discovery 42 2.6.2 Handling of Capabilities 57 2.7 RCS protocols 58 2.7.1 void 60 2.7.2 MSRP session matching 60 2.7.3 SIP Issues 60 2.8 RCS and Access Technologies 60 2.8.1 RCS and Cellular/EPC-integrated Wi-Fi Access 60 2.8.2 Other access networks 64 2.9 End User Confirmation Requests 64 2.10 Multidevice support 64 2.10.1 Overview 64 2.10.2 Addressing of individual clients 65 v12.0 Page 2 of 384 GSM Association Non-confidential Official Document RCC.07 - Rich Communication Suite - Advanced Communications Services and Client Specification 2.11 Interconnect principles and guidelines 65 2.12 Access Security 65 2.12.1 IMS Security 65 2.12.2 OpenID Connect 71 2.12.3 Common Message Store Authentication and Security 72 2.13 Emergency Services 72 2.13.1 General 72 2.13.2 RCS Service Feature List 72 2.14 CPIM header extension support 72 2.14.1 CPIM header extension support feature tag 73 2.14.2 Procedures in the client 73 2.14.3 Procedures in the Messaging Server 74 3 RCS Services 75 3.1 General Service Overview 75 3.2 Messaging 75 3.2.1 1-to-1 Messaging Technology Selection 75 3.2.2 Standalone messaging 79 3.2.3 1-to-1 Chat 85 3.2.4 Group Chat 100 3.2.5 File Transfer 110 3.2.6 Geolocation Push services 121 3.2.7 Audio Messaging 127 3.3 Void 129 3.4 Void 129 3.5 Void 129 3.6 Chatbots 129 3.6.1 Architecture 129 3.6.2 Chatbot Feature tags 132 3.6.3 Discovery and specific management of Chatbots 133 3.6.4 Chatbot Information 147 3.6.5 Privacy Protection 167 3.6.6 Spam and other Inappropriate Chatbot Behaviour Handling 174 3.6.7 Traffic identification 178 3.6.8 Chatbot Service 179 3.6.9 Deferred Messaging 189 3.6.10 Rich Cards and Suggested Chip Lists 191 3.6.11 Critical Chatbots 226 3.6.12 Menu 226 4 Cross-service functionality 232 4.1 Common Message Store 232 4.1.1 Overview 232 4.1.2 Support of GBA in the Common Message Store 232 4.1.3 Support of OpenID Connect in the Common Message Store 233 4.1.4 Support for Digest Authentication 233 v12.0 Page 3 of 384 GSM Association Non-confidential Official Document RCC.07 - Rich Communication Suite - Advanced Communications Services and Client Specification 4.1.5 Support for Basic Authentication 233 4.1.6 RESTful Web Service Calls 234 4.1.7 Folder Structure 235 4.1.8 Common Message Store and pager/multimedia-messages 237 4.1.9 Correlating SMS/MMS messages with messages stored in the Common Message Store 239 4.1.10 Correlation Algorithm for SMS 239 4.1.11 Dealing with Collisions 244 4.1.12 Recording of SMS messages 245 4.1.13 Recording of MMS messages 253 4.1.14 Optimisations for UNI operations to Common Message Store 263 4.1.15 A Common File Store for File Transfer via HTTP 264 4.1.16 Client behaviour 267 4.2 HTTP Content Server 274 4.2.1 Overview 274 4.2.2 File Upload Procedures 274 4.2.3 File Download Procedure 285 4.2.4 Schema Definition 287 4.2.5 HTTP Content Server URL 289 4.2.6 HTTP State Management 291 4.2.7 Security considerations 291 Annex A Managed objects and configuration parameters 292 A.1. Management objects parameters overview 292 A.1.1. Configuration parameters for the management of RCS services 292 A.1.2. Presence related configuration 293 A.1.3. Messaging related configuration 294 A.1.4. File Transfer related configuration 299 A.1.5. Void 301 A.1.6. IMS Core / SIP related configuration 301 A.1.7. Geolocation related configuration 305 A.1.8. Configuration related with Address book Back-up/Restore 306 A.1.9. Capability discovery related configuration 306 A.1.10. Void 308 A.1.11. Void 308 A.1.12. Service Provider specific extensions 308 A.1.13. Void 308 A.1.14. Data Off 308 A.2. Provisioning Document of the RCS Management tree 311 A.2.1. Application characteristic type for the RCS Management tree 311 A.2.2. Services sub tree additions 312 A.2.3. Presence sub tree 319 A.2.4. Messaging sub tree additions 319 A.2.5. Capability discovery MO sub tree 336 A.2.6. Service Provider Extensions MO sub tree 341 A.3. Other Management Objects 341 v12.0 Page 4 of 384 GSM Association Non-confidential Official Document RCC.07 - Rich Communication Suite - Advanced Communications Services and Client Specification A.3.1. Overview 341 A.3.2. IMS sub tree additions 342 A.4. Configuration XML document structure and examples 345 A.4.1. HTTP configuration XML structure 345 A.4.2. Configuration XML document example 347 Annex B : Additional diagrams 351 B.1. Chat and store and forward diagrams 351 B.1.1. Store and forward: Receiver offline 351 B.1.2. Store and forward: Message deferred delivery with sender still on an active Chat session 352 B.1.3. Store and forward: Message deferred delivery with sender online 353 B.1.4. Store and forward: Message deferred delivery with sender offline (delivery notifications) 354 B.1.5. Store and forward: Notifications deferred delivery 355 B.1.6. Network Interworking to SMS/MMS 356 B.1.7. Message Revoke: Successful Request 357 B.1.8. Message Revoke: Failed Request 358 B.1.9. Deliver Stored Group Chat Messages while Chat is idle 359 B.1.10. Multi-device 360 B.1.11. Chat and store and forward diagrams: Notes 361 B.2. Restful Message Store Flows (informative) 363 B.2.1. Client Initialization and Synchronization using RESTful Approach 363 B.2.2. RESTful Notification Events 367 B.2.3. Notification Channel Setup 368 B.2.4. Object Upload 368 B.2.5. Example Object Download 369 B.2.6. Example RESTful Search operation 369 Annex C Special Procedures 374 C.1. SIP/TCP and NAT traversal 374 C.2. Errata for RFC 5438 375 C.3. Definition of RCS CPIM Header Extensions 375 C.3.1. RCS CPIM Extension Name Space 375 C.3.2. Definition of rcs.Service-Centre-Address header 376 C.3.3. Definition of rcs.Reply-Path header 376 C.3.4. Definition of rcs.Replace-Short-Message-Type header 376 C.3.5. Definition of rcs.Mms-Message-Class header 377 C.3.6. Definition of rcs.Message-Correlator header 377 C.3.7. Definition of rcs.Message-Context header 378 C.4. Definition of SIP Header Extensions 378 C.4.1. User-Agent and Server Header Extensions 378 Document Management 382 Document History 382 Other Information 382 v12.0 Page 5 of 384 GSM Association Non-confidential Official Document RCC.07 - Rich Communication Suite - Advanced Communications Services and Client Specification 1 Introduction 1.1 RCS Principles and Vision RCS (Rich Communication Suite) provides a framework for discoverable and interoperable advanced communication services and detailed specifications for a basic set of such advanced communication services.
Load more

Recommended publications
  • Avaya Session Border Controller for Enterprise Overview and Specification
    Avaya Session Border Controller for Enterprise Overview and Specification Release 7.2.2.2 Issue 8 April 2019 © 2017-2019, Avaya Inc. YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED Notice SERVICE. While reasonable efforts have been made to ensure that the Licenses information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA the right to make changes and corrections to the information in this WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO, document without the obligation to notify any person or organization UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya of such changes. Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED “Documentation” means information published in varying mediums FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA which may include product information, operating instructions and CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL performance specifications that are generally made available to users AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. of products. Documentation does not include marketing materials. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, Avaya shall not be responsible for any modifications, additions, or AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE deletions to the original published version of Documentation unless WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA such modifications, additions, or deletions were performed by or on AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA the express behalf of Avaya.
    [Show full text]
  • TMS Xdata Documentation
    Overview TMS XData is a Delphi framework that allows you to create HTTP/HTTPS servers that expose data through REST/JSON. It is highly integrated into TMS Aurelius in a way that creating XData services based on applications with existing Aurelius mappings are just a matter of a few lines of code. XData defines URL conventions for adressing resources, and it specifies the JSON format of message payloads. It is heavily based on the OData standard. Such conventions, with the benefit of existing Aurelius mapping, allow building a full REST/JSON server with minimum writing of code. TMS XData uses TMS Sparkle as its core communication library. TMS XData product page: https://www.tmssoftware.com/site/xdata.asp TMS Software site: https://www.tmssoftware.com TMS XData is a full-featured Delphi framework that allows you to create REST/JSON servers, using server-side actions named service operations, and optionally exposing TMS Aurelius entities through REST endpoints. Consider that you have an Aurelius class mapped as follows: [Entity, Automapping] TCustomer = class strict private FId: integer; FName: string; FTitle: string; FBirthday: TDateTime; FCountry: TCountry; public property Id: Integer read FId write FId; property Name: string read FName write FName; property Title: string read FTitle write FTitle; property Birthday: TDateTime read FDateTime write FDateTime; property Country: TCountry read FCountry write FCountry; end; With a few lines of code you can create an XData server to expose these objects. You can retrieve an existing TCustomer
    [Show full text]
  • Security Management Fundamentals Release: 6.0 Document Revision: 03.08
    Nortel Communication Server 1000 Security Management Fundamentals Release: 6.0 Document Revision: 03.08 www.nortel.com .NN43001-604 Nortel Communication Server 1000 Release: 6.0 Publication: NN43001-604 Document release date: 14 April 2010 Copyright © 2008-2010 Nortel Networks. All Rights Reserved. While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their respective owners. 3 . Contents New in this release 11 Other changes 11 Revision history 11 How to get help 15 Getting help from the Nortel Web site 15 Getting help over the telephone from a Nortel Solutions Center 15 Getting help from a specialist by using an Express Routing Code 16 Getting help through a Nortel distributor or reseller 16 Introduction 17 Purpose 17 Navigation 18 Other security information 18 About this document 19 Subject 19 Intended audience 20 Terminology conventions 20 Fundamentals of system security management 21 System security overview 23 General signaling security overview 23 Key management concepts 23 Public-key certificate concepts 25 Platform security overview 28 Unified Communications Management security services 28 Unified Communications Management security server roles 29 Security Domain Manager concepts 30 Linux security hardening 31 Internal communications security overview 36 ISSS/IPsec 36 Secure File Transfer Protocol concepts 38 Port access restrictions concepts 40 Linux Master Firewall Control 41 Media and signaling security overview 42 Nortel Communication Server 1000 Security Management Fundamentals NN43001-604 03.08 14 April 2010 Copyright © 2008-2010 Nortel Networks.
    [Show full text]
  • Configuring 9600 Series SIP Telephones with Avaya Auratm Session Manager Release 6.0 and Avaya Auratm Communication Manager Evolution Server Release 6.0 – Issue 1.0
    Avaya Solution Interoperability Test Lab Configuring 9600 Series SIP Telephones with Avaya AuraTM Session Manager Release 6.0 and Avaya AuraTM Communication Manager Evolution Server Release 6.0 – Issue 1.0 Abstract These Application Notes describe the configuration of 9600 Series SIP Telephones with Avaya AuraTM Session Manager Release 6.0 supported by Avaya AuraTM Communication Manager Evolution Server Release 6.0. Avaya AuraTM Session Manager provides SIP proxy/routing functionality, routing SIP sessions across a TCP/IP network with centralized routing policies and registrations for SIP endpoints. Avaya AuraTM Communication Manager Evolution Server serves as an Evolution Server within the Avaya Aura™ Session Manager architecture and supports the SIP endpoints registered to Avaya AuraTM Session Manager. These Application Notes provide information for the setup, configuration, and verification of the call flows tested on this solution. DJH Reviewed: Solution Interoperability Lab Application Notes 1 of 51 SPOC 10/1/2010 ©2010 Avaya Inc. All Rights Reserved. SM6_CM-ES_R6 Table of Contents: 1. Introduction ............................................................................................................. 4 2. Equipment and Software Validated......................................................................... 5 3. Configure Avaya AuraTM Communication Manager ................................................ 6 3.1. Verify System Capacities and Licensing ................................................................. 6 3.1.1.
    [Show full text]
  • NICC ND 1035 V2.1.1 (2016-02) NICC Document
    NICC ND 1035 V2.1.1 (2016-02) NICC Document SIP Network to Network Interface Signalling NICC Standards Limited Michael Faraday House, Six Hills Way, Stevenage SG1 2AY Tel.: +44(0) 20 7036 3636 Registered in England and Wales under number 6613589 2 NICC ND 1035 V2.1.1 (2016 -02) NOTICE OF COPYRIGHT AND LIABILITY © 2016 NICC Standards Limited The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be that printing on NICC printers of the PDF version kept on a specific network drive within the NICC. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other NICC documents is available at: http://www.niccstandards.org.uk/publications/ If you find errors in the present document, please send your comments to: mailto:[email protected] Copyright All right, title and interest in this document are owned by NICC Standards Limited (“NICC”) and/or the contributors to the document (unless otherwise indicated that copyright is owned or shared with a third party). Such title and interest is protected by United Kingdom copyright laws and international treaty provisions. The contents of the document are believed to be accurate at the time of publishing, but no representation or warranty is given as to their accuracy, completeness or correctness.
    [Show full text]
  • Security Management Fundamentals
    Nortel Communication Server 1000 Security Management Fundamentals NN43001-604 . Document status: Standard Document version: 01.46 Document date: 31 October 2007 Copyright © 2008, Nortel Networks All Rights Reserved. LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Sourced in Canada Nortel, the Nortel Logo, the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks. Entrust is a trademark of Entrust, Inc. Verisign and Thawte are trademarks of Verisign, Inc. VxWorks is a trademark of Wind River Systems, Inc. All other trademarks are the property of their respective owners. 3 Revision History October 2007 Standard 01.46 This document is up-issued to support Communication Server 1000 (CS 1000) Release 5.0, and to reflect changes in technical content related to password reset procedures. October 2007 Standard 01.42 This document is up-issued to support CS 1000 Release 5.0, and to reflect changes in technical content related to Intrasystem Signaling Security Solution (ISSS) configuration. September 2007 Standard 01.34 This document is up-issued to support CS 1000 Release 5.0, and to reflect changes in technical content related primarily to ISSS configuration. June 2007 Standard 01.13 This document is up-issued to support CS 1000 Release 5.0, and to reflect changes in technical content, including changes to information about SIP TLS and ISSS configuration.
    [Show full text]
  • NBAR2 Standard Protocol Pack 1.0
    NBAR2 Standard Protocol Pack 1.0 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 © 2013 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 1 CHAPTER 2 BGP 3 BITTORRENT 6 CITRIX 7 DHCP 8 DIRECTCONNECT 9 DNS 10 EDONKEY 11 EGP 12 EIGRP 13 EXCHANGE 14 FASTTRACK 15 FINGER 16 FTP 17 GNUTELLA 18 GOPHER 19 GRE 20 H323 21 HTTP 22 ICMP 23 IMAP 24 IPINIP 25 IPV6-ICMP 26 IRC 27 KAZAA2 28 KERBEROS 29 L2TP 30 NBAR2 Standard Protocol Pack 1.0 iii Contents LDAP 31 MGCP 32 NETBIOS 33 NETSHOW 34 NFS 35 NNTP 36 NOTES 37 NTP 38 OSPF 39 POP3 40 PPTP 41 PRINTER 42 RIP 43 RTCP 44 RTP 45 RTSP 46 SAP 47 SECURE-FTP 48 SECURE-HTTP 49 SECURE-IMAP 50 SECURE-IRC 51 SECURE-LDAP 52 SECURE-NNTP 53 SECURE-POP3 54 SECURE-TELNET 55 SIP 56 SKINNY 57 SKYPE 58 SMTP 59 SNMP 60 SOCKS 61 SQLNET 62 SQLSERVER 63 SSH 64 STREAMWORK 65 NBAR2 Standard Protocol Pack 1.0 iv Contents SUNRPC 66 SYSLOG 67 TELNET 68 TFTP 69 VDOLIVE 70 WINMX 71 NBAR2 Standard Protocol Pack 1.0 v Contents NBAR2 Standard Protocol Pack 1.0 vi CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 NBAR2 Standard Protocol Pack Overview The Network Based Application Recognition (NBAR2) Standard Protocol Pack 1.0 is provided as the base protocol pack with an unlicensed Cisco image on a device.
    [Show full text]
  • HT801/HT802 Analog Telephone Adaptors Administration Guide
    Grandstream Networks, Inc. HT801/HT802 Analog Telephone Adaptors Administration Guide COPYRIGHT ©2021 Grandstream Networks, Inc. http://www.grandstream.com All rights reserved. Information in this document is subject to change without notice. Reproduction or transmittal of the entire or any part, in any form or by any means, electronic or print, for any purpose without the express written permission of Grandstream Networks, Inc. is not permitted. The latest electronic version of this user manual is available for download here: http://www.grandstream.com/support Grandstream is a registered trademark and Grandstream logo is trademark of Grandstream Networks, Inc. in the United States, Europe and other countries. CAUTION Changes or modifications to this product not expressly approved by Grandstream, or operation of this product in any way other than as detailed by this User Manual, could void your manufacturer warranty. WARNING Please do not use a different power adaptor with your devices as it may cause damage to the products and -void the manufacturer warranty. P a g e | 1 HT801/HT802 Administration Guide Version 1.0.29.8 GNU GPL INFORMATION HT801/HT802 firmware contains third-party software licensed under the GNU General Public License (GPL). Grandstream uses software under the specific terms of the GPL. Please see the GNU General Public License (GPL) for the exact terms and conditions of the license. Grandstream GNU GPL related source code can be downloaded from Grandstream web site from: http://www.grandstream.com/support/faq/gnu-general-public-license/gnu-gpl-information-download P a g e | 2 HT801/HT802 Administration Guide Version 1.0.29.8 Table of Content DOCUMENT PURPOSE ................................................................................................
    [Show full text]
  • TR-069 CPE WAN Management Protocol V1.1
    TECHNICAL REPORT TR-069 CPE WAN Management Protocol v1.1 Version: Issue 1 Amendment 2 Version Date: December 2007 © 2007 The Broadband Forum. All rights reserved. CPE WAN Management Protocol v1.1 TR-069 Issue 1 Amendment 2 Notice The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Technical Report has been approved by members of the Forum. This document is not binding on the Broadband Forum, any of its members, or any developer or service provider. This document is subject to change, but only with approval of members of the Forum. This document is provided "as is," with all faults. Any person holding a copyright in this document, or any portion thereof, disclaims to the fullest extent permitted by law any representation or warranty, express or implied, including, but not limited to, (a) any warranty of merchantability, fitness for a particular purpose, non-infringement, or title; (b) any warranty that the contents of the document are suitable for any purpose, even if that purpose is known to the copyright holder; (c) any warranty that the implementation of the contents of the documentation will not infringe any third party patents, copyrights, trademarks or other rights. This publication may incorporate intellectual property. The Broadband Forum encourages but does not require declaration of such intellectual property. For a list of declarations made by Broadband Forum member companies, please see www.broadband-forum.org. December 2007 © The Broadband
    [Show full text]
  • Ts 103 389 V1.2.1 (2013-09)
    ETSI TS 103 389 V1.2.1 (2013-09) Technical Specification Railway Telecommunications (RT); Global System for Mobile communications (GSM); Usage of Session Initiation Protocol (SIP) on the Network Switching Subsystem (NSS) to Fixed Terminal Subsystem (FTS) interface for GSM Operation on Railways 2 ETSI TS 103 389 V1.2.1 (2013-09) Reference RTS/RT-00021 Keywords FTS, SIP, GSM-R, NSS, railways ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • Version Indication & Negotiation
    SIF Infrastructure Specification 3.3: Version Indication & Negotiation www.A4L.org Version 3.3, May 2019 SIF Infrastructure Specification 3.3: Version Indication & Negotiation Version 3.3, May 2019 Preface ...................................................................................................................................... 4 Disclaimer ................................................................................................................................. 4 Permission and Copyright ....................................................................................................... 5 Document Conventions ........................................................................................................... 5 Terms and Abbreviations .......................................................................................................... 5 Notations ..................................................................................................................................... 6 1. Context ............................................................................................................................... 7 2. Problem Statement ........................................................................................................... 8 3. Method ................................................................................................................................ 9 3.1 Schema Identification .......................................................................................................
    [Show full text]
  • HTTP Working Group M. Nottingham Internet-Draft Akamai Intended Status: Standards Track P
    HTTP Working Group M. Nottingham Internet-Draft Akamai Intended status: Standards Track P. McManus Expires: September 9, 2016 Mozilla J. Reschke greenbytes March 8, 2016 HTTP Alternative Services draft-ietf-httpbis-alt-svc-14 Abstract This document specifies "Alternative Services" for HTTP, which allow an origin’s resources to be authoritatively available at a separate network location, possibly accessed with a different protocol configuration. Editorial Note (To be removed by RFC Editor) Discussion of this draft takes place on the HTTPBIS working group mailing list ([email protected]), which is archived at <https://lists.w3.org/Archives/Public/ietf-http-wg/>. Working Group information can be found at <http://httpwg.github.io/>; source code and issues list for this draft can be found at <https://github.com/httpwg/http-extensions>. The changes in this draft are summarized in Appendix A. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 9, 2016. Nottingham, et al. Expires September 9, 2016 [Page 1] Internet-Draft HTTP Alternative Services March 2016 Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors.
    [Show full text]