Shared Registry System Protocol (SRSP)
draft-crispin-srs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kent Crispin | ||
| Last updated | 1998-11-02 | ||
| 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
This specification describes a protocol for a Shared Registry System (SRS) that allows multiple registrars to register domain names within a single Top Level Domain (TLD). The protocol is high-level, text-based, and can be used over many underlying transport mechanisms, including email. The semantic content of the protocol is expressed as a set of keyword-value pairs; the semantics and structure of this content is, in this document, loosely described as the 'payload'. The protocol described herein is essentially identical to the SRS version 1.5 protocol, specified by the CORE SRS RFP and developed by Curt Meyer of Emergent Corporation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)