RealTime Internet Peering for Single User Endpoints
draft-rosenberg-dispatch-ript-inbound-00

Document Type Active Internet-Draft (individual)
Last updated 2020-02-07
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                        February 7, 2020
Expires: August 10, 2020

          RealTime Internet Peering for Single User Endpoints
                draft-rosenberg-dispatch-ript-inbound-00

Abstract

   The Real-Time Internet Peering for Telephony (RIPT) protocol defines
   a technique for establishing, terminating and otherwise managing
   calls between entities in differing administrative domains.  While it
   can be used for single user devices like an IP phone, it requires the
   IP phone to have TLS certificates and be publically reachable with a
   DNS record.  This specification remedies this by extending RIPP to
   enable clients to receive inbound calls.  It also provides basic
   single-user features such as forking, call push and pull, third-party
   call controls, and call appearances.  It describes techniques for
   resiliency of calls, especially for mobile clients with spotty
   network connectivity.

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/.

   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

Rosenberg                Expires August 10, 2020                [Page 1]
Internet-Draft                RIPT Inbound                 February 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Differences with SIP Outbound . . . . . . . . . . . . . . . .   3
   3.  Overview of Operation . . . . . . . . . . . . . . . . . . . .   4
   4.  Example Use Cases . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Inbound Call Forking  . . . . . . . . . . . . . . . . . .   6
     4.2.  Answer and Stop Ringing Other Devices . . . . . . . . . .   6
     4.3.  Remote in Use . . . . . . . . . . . . . . . . . . . . . .   7
     4.4.  Call Pull . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.5.  Call Push . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.6.  Select Device . . . . . . . . . . . . . . . . . . . . . .   8
     4.7.  Third Party Call Control - Place Outbound . . . . . . . .   8
     4.8.  Third Party Call Control Answer or Decline Inbound  . . .   9
     4.9.  Third Party Call Control  Hangup  . . . . . . . . . . . .   9
     4.10. Third Party Call Control  Move Call . . . . . . . . . . .   9
     4.11. Resiliency Miss Incoming call . . . . . . . . . . . . . .  10
     4.12. Resiliency MidCall Network Change . . . . . . . . . . . .  10
     4.13. Resiliency MidCall Wireless Fade and Recover  . . . . . .  10
     4.14. Resiliency MidCall Wireless Fade and Move . . . . . . . .  11
     4.15. Resiliency MidCall Wireless Fade and Peer Hangup  . . . .  11
     4.16. Resiliency MidCall Wireless Fade and Server Drop  . . . .  11
   5.  Normative Protocol Specification  . . . . . . . . . . . . . .  12
   6.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  13
     10.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].
Show full document text