Skip to main content

Using Telephone Related Information (TeRI) with the Distributed Registry Protocol (DRiP)

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Jon Peterson , Chris Wendt
Last updated 2018-09-06 (Latest revision 2018-03-05)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The Distributed Registry Protocol (DRiP) allows a set of nodes to implement a decentralized registry function. This document explores how Telephone Related Information (TeRI) Records can be shared by DRiP, and a decentralized registry approaches the operations necessary to assign, provision, and route for telephone numbers.


Jon Peterson
Chris Wendt

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