Using Telephone Related Information (TeRI) with the Distributed Registry Protocol (DRiP)
draft-peterson-modern-drip-teri-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-09-06 (latest revision 2018-03-05) | ||
| 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) | ||
https://www.ietf.org/archive/id/draft-peterson-modern-drip-teri-00.txt
Abstract
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.
Authors
Jon Peterson
(jon.peterson@neustar.biz)
Chris Wendt
(chris-ietf@chriswendt.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)