Considerations for URI and FQDN Protocol Parameters
draft-eastlake-uri-fqdn-param-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Donald E. Eastlake 3rd | ||
| Last updated | 2001-02-19 | ||
| 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
It is becoming increasingly common for protocol parameters to be of URI or Domain Name syntax. Examples include TSIG algorithm identifiers, XMLDSIG algorithm and type identifiers, XML namespaces, etc. Considerations are provided for the allocation of such URI or Domain Name syntax protocol parameter values.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)