From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 1155 invoked from network); 11 Mar 2021 21:16:24 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 11 Mar 2021 21:16:24 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 2CE1995074; Fri, 12 Mar 2021 07:16:23 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 065799B5B6; Fri, 12 Mar 2021 07:16:00 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=iitbombay-org.20150623.gappssmtp.com header.i=@iitbombay-org.20150623.gappssmtp.com header.b="sdwlI7Y3"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id CE2659B5B6; Fri, 12 Mar 2021 07:15:58 +1000 (AEST) Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) by minnie.tuhs.org (Postfix) with ESMTPS id 1383295074 for ; Fri, 12 Mar 2021 07:15:58 +1000 (AEST) Received: by mail-qt1-f180.google.com with SMTP id f12so2271315qtq.4 for ; Thu, 11 Mar 2021 13:15:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=zwN8UfB50l2RKW+OWaMTqpQk8VbR1sOYjvFeix0yLOA=; b=sdwlI7Y34v+DbbQp8MJ0YdURjZxIhyJjV7ykTC5QSpfvksd0cT/OrLl4T7sM9Cjapc j+PXMWqbOKURBHhssryMTVGvpQCJu5isXbDaR3zZVXA+42Ub999ivpUNJjQ2ETnmacXc bjabmPBJG9HF11xwGb5rCXfogTdopXQngXF3deV7H1CjsDdfpnYLEIepIZ9MD1cgxRiW Sf8VoztqVgpVbvGxTyu+p8gzCnjDSKb35LQmzoS2cvnc/sbpmrilKGS9tNOLKGWQTfg9 DFB8ed2XLP98W07oiNC1iZUU+11s6LaldsESoocGSCJjRVA8IWItDvakAx56JeeKfj7y ZGRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=zwN8UfB50l2RKW+OWaMTqpQk8VbR1sOYjvFeix0yLOA=; b=cCwtpn0mMSD3UTXM/dnVNxfUkLR7efFpKY7sjlYmygiLwBGJuXmPJUO4EtSHgqsFv1 JqT0VQYXdyrDPguiMwolg09qdMOcfjvh8ksPqC1peyihg0wA82WyAVisBmRcDR5chvZS 4cEaYAXAgg/cv3mVMmq8yHAkU5abj+Cqa7eTNa0buedf/V38TayUEP6HusHHPypRrCIP iLQuHrIuO/yIdltIdjDz3XFJdWbRAoDQ8EhcYAldFxBtiVMtBzE73102OyKP++xiQJ3Q Jdk4jKooLjEg9NK4gzh3X4dLWJNXraqRVVL0fHWclUlA2mm9GmMj/APgOeIiJmId9xhI V3oA== X-Gm-Message-State: AOAM532DOitunVzxTkmw4K2dtzWSayoIcVZUdDFnj9SXHuOeaVDCRRoL kR1DzIJ68TgXDVEP7RkK55NcgfMMnqKagw== X-Google-Smtp-Source: ABdhPJylf6zZu7ExxmvwGlNzUv6SmzwBP72Vkwls4BuxGghxHokAAR88mHHx3Tynsd2giR+jd7xlgg== X-Received: by 2002:ac8:5bd1:: with SMTP id b17mr9183174qtb.53.1615497357223; Thu, 11 Mar 2021 13:15:57 -0800 (PST) Received: from [192.168.125.11] (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id e190sm2843015qkd.122.2021.03.11.13.15.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Mar 2021 13:15:56 -0800 (PST) From: Bakul Shah Message-Id: <0690CD07-BFA1-4C65-9C6F-493C3340D559@iitbombay.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_F3281330-5C8E-46B1-8406-E60D75FA3A4C" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Date: Thu, 11 Mar 2021 13:15:54 -0800 In-Reply-To: To: Ron Natalie References: <02d10a8e-2f39-4f88-f4c9-ecb295e0f01e@spamtrap.tnetconsulting.net> <555F9514-DD67-41F1-8151-480F0D9D0EAC@iitbombay.org> X-Mailer: Apple Mail (2.3654.60.0.2.21) Subject: Re: [TUHS] [COFF] Pondering the hosts file X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Unix Heritage Society , Internet History Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --Apple-Mail=_F3281330-5C8E-46B1-8406-E60D75FA3A4C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii As I quoted, the RFC says to refer to the assigned numbers RFC for = specific options and acronyms for machine types, operating systems, and = protocol/services. A host/network/gateway name has no such restriction.=20= > On Mar 11, 2021, at 1:08 PM, Ron Natalie wrote: >=20 > The "name" in this context the host/network/gateway name such as = SRI-NIC.ARPA. 3COM.COM would not have been legal = back then. > Nowhere does it imply that any of the other fields are so restricted. >=20 > ------ Original Message ------ > From: "Bakul Shah" > > To: "Ron Natalie" > > Cc: "The Unix Heritage Society" >; "Internet History" = > > Sent: 3/11/2021 4:02:50 PM > Subject: Re: [TUHS] [COFF] Pondering the hosts file >=20 >> On Mar 11, 2021, at 12:32 PM, Ron Natalie > wrote: >>>=20 >>> Amusingly one day we got an Imagen ethernet-connected laser printer. = Mike Muuss decided the thing should be named BRL-ZAP and since I = didn't know what to put down as the machine type, and it did have a = 68000 in it, I had Jake put 68000 in the entry in the host table. >>>=20 >>> The next day I got all kinds of hate mail from other BSD sites who = assumed I had intentionally sabotaged the host table. Apparently, the = BSD systems used a YACC grammar to parse the NIC table into the Berkeley = one. The only problem is they got the grammar wrong and assumed the = CPU type always began with a letter. There parse blew up on my "ZAP" = host and they assumed that was the desired effect. >>=20 >> This is understandable as >> a) All the "official machine names" in various assigned numbers RFCs = start with a letter. >> b) the BNF syntax for the "host table specification" entries in RFC = 952 or 810 are not precise enough. >> ::=3D PDP-11/70 | DEC-1080 | C/30 | CDC-6400...etc. >>=20 >> NOTE: See "Assigned Numbers" for specific options and acronyms >> for machine types, operating systems, and protocol/services. >> for machine types, operating systems, and protocol/services. >> c) 68000 was not an official name! >> :-) :-) :-) >>=20 >>> I countered back that using a YACC grammar for this was rediculous. = There was already a real popular file on UNIX that had a bunch of = fields separated by colons and commas (/etc/passwd anybody) that it was = never necessary to use YACC to parse. >>=20 >> Can't argue with that! Though that doesn't mean a handwritten parser = wouldn't have complained about 68000. --Apple-Mail=_F3281330-5C8E-46B1-8406-E60D75FA3A4C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii As = I quoted, the RFC says to refer to the assigned numbers RFC for specific options and acronyms for machine types, operating systems, and = protocol/services. A host/network/gateway name has = no such restriction. 

On Mar 11, 2021, at 1:08 PM, = Ron Natalie <ron@ronnatalie.com> wrote:

The "name" in this context the = host/network/gateway name such as SRI-NIC.ARPA.    3COM.COM would not have been legal = back then.
Nowhere does it imply that any of the other = fields are so restricted.

------ Original Message ------
From: "Bakul Shah" <bakul@iitbombay.org>
To: = "Ron Natalie" <ron@ronnatalie.com>
Cc: = "The Unix Heritage Society" <tuhs@minnie.tuhs.org>; "Internet History" <internet-history@postel.org>
Sent: 3/11/2021 4:02:50 PM
Subject: Re: [TUHS] [COFF] Pondering the hosts = file

On Mar 11, 2021, at 12:32 PM, Ron = Natalie <ron@ronnatalie.com> wrote:

Amusingly one day we got an Imagen = ethernet-connected laser printer.    Mike Muuss decided the = thing should be named BRL-ZAP and since I didn't know what to put down = as the machine type, and it did have a 68000 in it, I had Jake put 68000 = in the entry in the host table.

The next day I got all kinds of hate mail from = other BSD sites who assumed I had intentionally sabotaged the host = table.   Apparently, the BSD systems used a YACC grammar to = parse the NIC table into the Berkeley one.   The only problem = is they got the grammar wrong and assumed the CPU type always began with = a letter.    There parse blew up on my "ZAP" host and they = assumed that was the desired effect.

This is understandable = as
a) All the "official machine names" in various = assigned numbers RFCs start with a letter.
b) = the BNF syntax for the "host table specification" entries in RFC 952 or = 810 are not precise enough.
	=
<cputype> ::=3D PDP-11/70 | DEC-1080 | C/30 | =
CDC-6400...etc.

NOTE:  See "Assigned Numbers" for =
specific options and acronyms
         for machine types, operating systems, and protocol/services.

         for machine types, =
operating systems, and protocol/services.

c) 68000 was not =
an official name!
:-) :-) :-)

I countered back that using a YACC grammar for = this was rediculous.   There was already a real popular file = on UNIX that had a bunch of fields separated by colons and commas = (/etc/passwd anybody) that it was never necessary to use YACC to = parse.

Can't = argue with that! Though that doesn't mean a handwritten parser wouldn't = have complained about = 68000.

= --Apple-Mail=_F3281330-5C8E-46B1-8406-E60D75FA3A4C--