The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] conventions around zero padding in ip4
Date: Mon,  9 May 2022 12:14:16 -0400 (EDT)	[thread overview]
Message-ID: <20220509161416.EDB2F18C073@mercury.lcs.mit.edu> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2437 bytes --]

    > There were other ways of specifying a IP address numerically, initially;

I decided to set the Way-Back Machine to as close to 0 as I could get, and
looked to see what the Terminal Interface Unit:

  https://gunkies.org/wiki/Terminal_Interface_Unit

whose source I recently recovered, did. This is an interesting
implementation, because it was definitely one of the first 4 TCP
implementations done (before any UNIX ones); likely one of the first two,
along with the TENEX one. (Actually, they both likely originally predate the
split of TCP and IP into separate protocols, although this version post-dates
that split.)

The manual:

  http://ana-3.lcs.mit.edu/~jnc/tech/mos/docs/tiunv1.lpt

(in "B. TELNET Commands") and the source:

  http://ana-3.lcs.mit.edu/~jnc/tech/mos/tiu/telnet-1.mac

disagree on how the user gave addresses in numeric form in an 'open' command;
both agree that it was '@O <rest>,<net>,<socket>', but the manual claims
that 'rest' "may be specified symbolically, or numerically in decimal", but the
code shows that '#xxx' could also be used, to give it in hex. (Although if hex
were used, the number could be a max of 16 bits; decimal alloweded up to 42 bits.)


    > From: Michael Kjörling

    > Looks like [A/B/C addresses] happened in 1978 or thereabouts?
    > https://www.rfc-editor.org/ien/ien46.txt

No; it post-dates the IEN era; "Assigned Numbers" of September 1981 (RFC-790)
is the first mention I could find of it. (That Dave Clark IEN is talking
about what later became 'IP subnets' - which ironically long pre-date A/B/C -
see IEN-82, February 1979.)

The Internet Protocol spec of September 1981 (RFC-791) also has A/B/C; my
memory is that this change was _not_ discussed in the INWG, Postel just
sprung it on us in these two RFCs.

I suspect what happened is that Jon (as keeper of the network numbers)
realized that there was an increasing demand for network numbers, and 256
would only last so long, so he sprung into action and did the A/B/C thing.
(If this topic is of more interest, it should get moved to the
'internet-history' list, it's off-topic here.)

Interestingly, RFC-790 says: "One notation for internet host addresses
commonly used divides the 32-bit address into four 8-bit fields and specifies
the value of each field as a decimal number with the fields separated by
periods." Note the "one notation", implying that it wasn't any kind of
standard at that point.

	Noel

             reply	other threads:[~2022-05-09 16:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 16:14 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-07 19:43 Noel Chiappa
2022-05-08 14:54 ` Michael Kjörling
2022-05-07 16:14 ron minnich
2022-05-07 16:38 ` Bakul Shah
2022-05-07 16:48 ` Erik E. Fair
2022-05-07 18:49 ` Steffen Nurpmeso
2022-05-07 19:14 ` Warner Losh
2022-05-07 19:50   ` ron minnich
2022-05-07 19:57     ` ron minnich
2022-05-07 23:19   ` Bakul Shah
2022-05-07 23:49     ` Warner Losh
2022-05-08 10:28     ` Ralph Corderoy
2022-05-08  5:21 ` jason-tuhs
2022-05-08 10:22 ` Ralph Corderoy
2022-05-09 14:08   ` Steffen Nurpmeso
2022-05-10 10:49     ` Ralph Corderoy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220509161416.EDB2F18C073@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).