(Message inbox:825)
Return-Path: <lbm@mit-heracles>
Received: from mit-athena (mit-athena.ARPA) by mit-jason (4.12/4.7)
	id AA14640; Tue, 25 Jun 85 09:44:48 edt
Received: from mit-heracles (mit-heracles.ARPA) by mit-athena (4.12/4.7)
	id AA27529; Tue, 25 Jun 85 09:44:13 edt
Received: by mit-heracles (4.12/4.7)
	id AA06294; Tue, 25 Jun 85 09:44:10 edt
From: lbm@mit-heracles
Message-Id: <8506251344.AA06294@mit-heracles>
Date: 25 Jun 1985 0944-EDT (Tuesday)
To: at_project@mit-heracles
Cc: Saltzer@mit-heracles, martillo@mit-heracles, lbm@mit-heracles
Subject: AT Network Addresses


I have been investigating tftp between AT's and between an AT and an Athena
Unix host.  Although all the paths work, there are some inconsistancies about
the forms of network addresses the paths accept.

1.  To transfer with an AT, you must know its network address.

    - If you are on a Unix system and transferring with an AT,
      you must know the system's DECIMAL address (18. and so forth),
      or its NAME (cassandra, hera, etc.).  The OCTAL representation
      of the AT's address does not work.

    - If you are on another AT and transferring with an AT, you
      can use either the system's OCTAL address, its NAME (I'm not
      sure why this works--are two separate entities resolving
      names?), or its DECIMAL address.

2.  To find out an AT's network address

    - If you can use the telnet command to a remote host, you can find
      out that AT's DECIMAL and OCTAL addresses with F10 I.

    - You can get an AT to tell you its OCTAL address, without the
      need to login and reference anything else, with the \etc\custom
      command.  I know of no way to get at AT to tell you its
      network address in the DECIMAL or NAME form--the two forms that
      always work.

This is needlessly complicated.  Either you ought to be able to
get an AT to tell you its network address in all three forms, or
tftp on Unix should work with octal form addresses, and preferably
both.