ASCII Encoding for Domain Names
draft-andrews-dns-ascii-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark P. Andrews | ||
| Last updated | 1996-05-23 (Latest revision 1996-05-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
[RFC 1035 Section 5.1] describes how to encode domain names as character strings. It however allows non printable characters to be used. It also allows for encodings of text files which would not survive intact ftp ASCII mode transfers, different end of line conventions. This document addresses these problems by stating where decimal escapes SHOULD be used. While a applications MUST continue to read the full range as expressed by [RFC 1035 5.1]. They SHOULD emit only this selected subset.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)