DNS Editing Through HTTPS (DETH)
draft-hildebrand-deth-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Joe Hildebrand , Paul E. Hoffman | ||
| Last updated | 2016-09-22 (Latest revision 2016-03-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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:
Abstract
There is a strong desire in many communities for service operators to be able to dynamically update DNS records in an easy-to-deploy, standardized method. For example, operating SIP requires DNS records to be added and updated as the SIP service starts and is moved among different servers. This document describes an HTTPS-based mechanism for service operators who are authorized by their DNS administrator to add, change, and delete DNS records.
Authors
Joe Hildebrand
Paul E. Hoffman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)