From owner-freebsd-hackers Thu Aug 12 15:16:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abalaea.ircache.net (abalaea.scd.ucar.edu [128.117.28.9]) by hub.freebsd.org (Postfix) with ESMTP id 1C96814D48 for ; Thu, 12 Aug 1999 15:16:30 -0700 (PDT) (envelope-from glenn@abalaea.ircache.net) Received: from localhost (glenn@localhost) by abalaea.ircache.net (8.9.2/8.9.1) with ESMTP id QAA58419; Thu, 12 Aug 1999 16:15:05 -0600 (MDT) (envelope-from glenn@abalaea.ircache.net) Date: Thu, 12 Aug 1999 16:15:05 -0600 (MDT) From: Glenn Chisholm To: Evren Yurtesen Cc: Bill Fumerola , Michael Mannsberger , freebsd-hackers@FreeBSD.ORG Subject: Re:(2) hey In-Reply-To: <37B343A8.A94CD343@ispro.net.tr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I am the person who has this problem. > The RFCs does not explicitly say that we should not use underscore > character > as far as I understood. But it suggests which characters we should use. > RFC 952 1. A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of "domain style names". RFC 1101 The current syntax for network names, as defined by [RFC 952] is an alphanumeric string of up to 24 characters, which begins with an alpha, and may include "." and "-" except as first and last characters. This is the format which was also used for host names before the DNS. Upward compatibility with existing names might be a goal of any new scheme. The above two documents limit the characters that may be used a a _ is not one of them. FreeBSD behaves correctly in this manner. RFC 1033 is only a informational RFC and should not be treated as a standard. glenn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message