TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:OUTCOME re A network terminology question From:"Mark L. Levinson" <markl -at- gilian -dot- com> To:TechWr-L <TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM> Date:Mon, 24 Apr 2000 11:24:24 +0200
A while ago I asked about terminology for a pair of
NICs. I was worried because the NICs were being
referred to as "inbound" and "outbound" though
to me it seemed that the distinction between them
was entirely different. On behalf of a small
network, one NIC was interfacing with the outside
world for both inbound and outbound traffic, and
the other NIC was interfacing with the small
network itself for both inbound and outbound
traffic. Sort of like the two doors of an airlock,
come to think of it.
I received a lot of good answers and suggestions,
and I thank everyone who replied. Suggestions
included LAN/WAN, inside/outside, intra/extra,
a couple of ideas for getting around the problem by
using numbers or other device-specific identifiers,
and one vote for inbound/outbound.
I had no problem with "outside." But I was wary
of "inside," "intra," and that whole concept because
it could sound like "inside the computer" rather
than "inside the small network." I decided to go
for private/public instead, and our programmers,
having understood that inbound/outbound was misleading,
acceded.
Today one of the programmers came by to say that
he'd noticed that similar configurations are used
in load balancing, and that there the terminology
is internal/external. I don't see my quibble
(it's inside the small network, not inside the
computer) as strong enough to oppose established
terminology, so I'm planning to go with internal/external.