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

Document Type Expired Internet-Draft (individual)
Last updated 2020-08-10 (latest revision 2020-02-07)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rosenberg-dispatch-ript-inbound-00.txt

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.

Authors

Jonathan Rosenberg (jdrosen@jdrosen.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)