From owner-freebsd-stable@FreeBSD.ORG Tue Mar 25 17:51:12 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAD5937B401 for ; Tue, 25 Mar 2003 17:51:12 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B5DB43FA3 for ; Tue, 25 Mar 2003 17:51:12 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0212.cvx21-bradley.dialup.earthlink.net ([209.179.192.212] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18y04M-0000CA-00; Tue, 25 Mar 2003 17:51:10 -0800 Message-ID: <3E81073F.459270AE@mindspring.com> Date: Tue, 25 Mar 2003 17:49:51 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David J Duchscher References: <64BD550E-5EFD-11D7-8571-0003930B3DA4@nostrum.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4bb69fb7f5ccb9e541fac8b4d93baa7a4350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Spam-Status: No, hits=-22.2 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT, RCVD_IN_OSIRUSOFT_COM,REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: stable@freebsd.org Subject: Re: Resolver Issues (non valid hostname characters) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 01:51:15 -0000 X-List-Received-Date: Wed, 26 Mar 2003 01:51:15 -0000 David J Duchscher wrote: > On Tuesday, March 25, 2003, at 05:03 AM, Terry Lambert wrote: > > > It's probably not very useful to talk about doing this until > > local caching-only name servers on border servers are capable > > of handling the 8-bit, as well. For the RFC's that FreeBSD > > currently complies with, it's right to be strict about this. > > I think this is the wrong approach to take with this problem. > Linux, Windows, and Solaris do not enforce this restriction. If > RFC 952 is being thrown out the window, then why should FreeBSD > continue to enforce this restriction? At the moment, the > problems I am seeing have little to do with 8-bit data but > characters outside of the what RFC 952 allows. RFC 952 is in effect until a subsequent standards track RFC is in effect. Just because Linux allows you to specif host names that break other machines, doesn't mean FreeBSD should. "If your friends OS jumped off a cliff...?" This is not that hard to understand: if FreeBSD is going to need to (effectively) rewrite the resolver code, it should be done once, not hundreds of times. It is an expensive proposition. If you want to provide a patch that allows this behaviour to be optional in the FreeBSD resolver, through the use of an "xrfc952" option in the /etc/resolv.conf file, I invite you to submit code. -- Terry