HP3000-L Archives

October 2002, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Woods <[log in to unmask]>
Reply To:
Jeff Woods <[log in to unmask]>
Date:
Thu, 3 Oct 2002 10:35:53 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Tom Emerson wrote:
>I seem to recall from the very first time I came across an HP with
>networking that the values set up were something like "6.xx.yy.zz", and at
>the time, "network 6" was HP's class A network value;  (this is "top of my
>head" memory -- don't take it as gospel...)  Again, the manual at the time
>used that as "an example" and the system manager before me set it that
>way. When we connected to our "parent" company's network, we got into a
>"heap o trouble" because our system was advertising itself as HP... :)

In the very early days of IP networking on MPE, the documentation (maybe of
the README rather than official variety) on configuring IP had you contact
HP to get an address-block.  And HP was passing out class-C address blocks
as needed, but I don't remember what numbers we got "way back when".

Of course, this practice common across the industry contributed to IP
routing on the Internet backbone getting *really* complicated (read:
"slow"); that's why publicly visible IP address blocks are now strongly
encouraged to be ISP-assigned instead of fixed to a small company who may
change from one ISP to another and thus require routing changes at the
backbone.

--
Jeff Woods
[log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2