Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!nuug!ifi!enag
From: enag@ifi.uio.no (Erik Naggum)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: HINFO record consistency
Message-ID: <ENAG.90Nov28235557@hild.ifi.uio.no>
Date: 28 Nov 90 22:56:06 GMT
References: <1990Nov27.234016.21510@terminator.cc.umich.edu>
Sender: enag@ifi.uio.no (Erik Naggum)
Organization: Naggum Software, Oslo, Norway
Lines: 39
Nntp-Posting-Host: hild.ifi.uio.no
In-Reply-To: bryan@terminator.cc.umich.edu's message of 27 Nov 90 23:40:16 GMT
Originator: enag@hild

Bryan,

The HINFO values are supposed to be chosen from the list in RFC 1060,
Machine Names (page 53 ff), and System Names (page 57).

From RFC 1035, Domain Names - Implementation and Specification:

    3.3.2. HINFO RDATA format

	+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
	/                      CPU                      /
	+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
	/                       OS                      /
	+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

    where:

    CPU             A <character-string> which specifies the CPU type.

    OS              A <character-string> which specifies the operating
		    system type.

    Standard values for CPU and OS can be found in [RFC-1010].

    HINFO records are used to acquire general information about a host.  The
    main use is for protocols such as FTP that can use special procedures
    when talking between machines or operating systems of the same type.

Note: RFC 1060 obsoletes RFC 1010.

Note that the strings listed in RFC 1060 break the general syntax
rules found in RFC 1035 for general domain names.  (Space and slash
are not recommended.)

--
[Erik Naggum]	Snail: Naggum Software / BOX 1570 VIKA / 0118 OSLO / NORWAY
		Mail: <erik@naggum.uu.no>, <enag@ifi.uio.no>
My opinions.	Wail: +47-2-836-863
--