RealTime Internet Peering for Telephony
draft-rosenbergjennings-dispatch-ript-00

Document Type Active Internet-Draft (individual)
Last updated 2020-02-07
Replaces draft-rosenbergjennings-dispatch-ripp
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       J. Rosenberg
Internet-Draft                                                     Five9
Intended status: Standards Track                             C. Jennings
Expires: August 10, 2020                                   Cisco Systems
                                                            A. Minessale
                                                   Signalwire/Freeswitch
                                                            J. Livingood
                                                                 Comcast
                                                               J. Uberti
                                                                  Google
                                                        February 7, 2020

                RealTime Internet Peering for Telephony
                draft-rosenbergjennings-dispatch-ript-00

Abstract

   This document specifies the Realtime Internet Peering for Telephony
   (RIPT) protocol.  RIPT is used to provide peering of voice and video
   communications between entities.  These include a traditional voice
   trunking provider (such as a telco), and a trunking consumer (such as
   an enterprise PBX or contact center), or between a video conferencing
   endpoint deployed in an enterprise, and a video conferencing SaaS
   service.  RIPT is an alternative to SIP, SDP and RTP for these use
   cases, and is designed as a web application using HTTP/3.  Using
   HTTP/3 allows implementors to build their applications on top of
   cloud platforms, such as AWS, Azure and Google Cloud, all of which
   are heavily focused on HTTP based services.  RIPT also addresses many
   of the challenges of traditional SIP-based peering.  It supports
   modern techniques for load balancing, autoscaling, call-preserving
   failover, graceful call migrations, security by default, STIR-based
   caller ID, provisioning, and capabilities - all of which have been
   challenges with traditional SIP peering and voice trunking.  Since it
   runs over HTTP/3, it works through NATs and firewalls with the same
   ease as HTTP does.

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 https://datatracker.ietf.org/drafts/current/.

Rosenberg, et al.        Expires August 10, 2020                [Page 1]
Internet-Draft                    RIPT                     February 2020

   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 August 10, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Structure of this Document  . . . . . . . . . . . . . . . . .   5
   3.  Solution Requirements . . . . . . . . . . . . . . . . . . . .   5
   4.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Reference Architecture  . . . . . . . . . . . . . . . . . . .   7
   6.  Web Resource Model  . . . . . . . . . . . . . . . . . . . . .   9
   7.  Deployment Examples . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Enterprise Voice Trunking . . . . . . . . . . . . . . . .  11
     7.2.  BYO Voice for CCaaS . . . . . . . . . . . . . . . . . . .  12
     7.3.  Inter-Carrier Voice Peering . . . . . . . . . . . . . . .  12
     7.4.  Video Endpoint to Meetings Provider . . . . . . . . . . .  13
   8.  Overview of Operation . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Bootstrap . . . . . . . . . . . . . . . . . . . . . . . .  13
     8.2.  Login . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.3.  TG Discovery  . . . . . . . . . . . . . . . . . . . . . .  14
     8.4.  Customer TG Registration  . . . . . . . . . . . . . . . .  15
     8.5.  Handler Registration  . . . . . . . . . . . . . . . . . .  16
Show full document text