3 Expires: September 1996 May 1996
6 ASCII Encoding for Domain Names
8 draft-andrews-dns-ascii-01.txt
10 1. Status of This Memo
12 This document is an Internet Draft. Internet Drafts are working
13 documents of the Internet Engineering Task Force (IETF), its Areas,
14 and its Working Groups. Note that other groups may also distribute
15 working documents as Internet Drafts.
17 Internet Drafts are draft documents valid for a maximum of six
18 months. Internet Drafts may be updated, replaced, or obsoleted by
19 other documents at any time. It is not appropriate to use Internet
20 Drafts as reference material or to cite them other than as a "working
21 draft" or "work in progress."
23 Please check the 1id-abstracts.txt listing contained in the internet-
24 drafts Shadow Directories to learn the current status of any Internet
29 [RFC 1035 Section 5.1] describes how to encode domain names as
30 character strings. It however allows non printable characters to be
31 used. It also allows for encodings of text files which would not
32 survive intact ftp ASCII mode transfers, different end of line
33 conventions. This document addresses these problems by stating where
34 octal escapes MUST be used.
36 While a applications MUST continue to read the full range as
37 expressed by [RFC 1035 5.1]. They MUST emit only this selected
42 Octets within the follow ranges are encoded as backslash followed by
43 three octal digits, 0x00 - 0x20, 0x7f - 0xff.
54 Internet Draft draft-andrews-dns-ascii-01.txt May 1996
57 Period (".") when NOT used as a domain separator is encoded as the
58 sequence backslash period, e.g. "\.". Un-escaped periods indicate
61 Backslash ("\") is encoded as two consecutive backslashes, e.g. "\\".
63 Double quotes ('"') should always be represented as backslash quote
64 as a common nameserver implementation mis-parses strings containing
67 Semi-colon (";") should always be encoded as backslash semi-colon
68 otherwise it will be interpreted as a comment. e.g. "\;".
70 Space may be a literal space when the string is enclosed by double
73 All other characters represent their literal ASCII encoding eighth
78 This draft introduces no known security problems. It may however
79 remove some latent security problems in applications where the
80 encoding is NOT reversible leading to unexpected changes in domain
86 P. Mockapetris, ``DOMAIN NAMES - IMPLEMENTATION AND
87 SPECIFICATION'', RFC-1035, ISI, November 1987.
93 Division of Mathematics and Statistics
98 Mark.Andrews@dms.csiro.au [MA88]