Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id TAA15075; Tue, 30 May 1995 19:37:38 -0400 X-Resent-To: drums@CS.UTK.EDU ; Tue, 30 May 1995 19:37:37 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from cnj.digex.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id TAA15068; Tue, 30 May 1995 19:37:35 -0400 Received: from localhost (qlY3IRsnuxD5M@localhost [127.0.0.1]) by cnj.digex.net (8.6.12/8.6.12) with SMTP id TAA18957; Tue, 30 May 1995 19:37:30 -0400 Message-Id: <199505302337.TAA18957@cnj.digex.net> X-Authentication-Warning: cnj.digex.net: Host localhost didn't use HELO protocol To: Eric Thomas cc: drums@CS.UTK.EDU Subject: Re: getting started In-reply-to: Your message of "Tue, 30 May 1995 13:48:57 +0200." <199505301214.IAA22394@CS.UTK.EDU> Organization: XIson, Inc. X-Org-Misc: 1.908.549.3716 (phone) X-Mailer: MH 6.8.3 Date: Tue, 30 May 1995 19:37:28 -0400 From: Ed Levinson Eric, Your note to the drums list piqued my interest, especially about the inconsistent naming issues. Can you provide more detail, where to look in the various RFCs? I'd like to add this information to some work I'm doing on addressing. Thanks.../Ed > One feature that I think needs to be clarified in both 821 and 822 (et > seq) is whether underscore and leading numbers are accepted in hostnames. > > Right now we have a nice mess where 822 allows underscores, 821 doesn't, > and neither does the DNS, but then bind does and so does sendmail, ... > > For leading numeric characters we have another mess where the (modified) > DNS standards allow it, but 821 doesn't. ...