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: Sat,  7 May 2022 15:43:36 -0400 (EDT)	[thread overview]
Message-ID: <20220507194336.DC70918C075@mercury.lcs.mit.edu> (raw)

    > From: Ron Minnich

    > I first learned in the 80s that 127.1 meant 127.0.0.1. I always assumed
    > zero padding was defined in a standard *somewhere*, but am finding out
    > maybe not. I talked to the IP OG, and he tells me that padding was not
    > in any standard.

I don't think it was very standardized; I've been working on the Internet
since 1977, and this is the very first I ever recall hearing of it! :-)


    > From: Bakul Shah 

    > The converse question is who came up with the a.b.c.d format where each
    > of a,b,c,d is in 0..255?

Again, that was not standardized at an early stage, but was, as best I can now
recall, just adopted by general usage (i.e. without any formal discussion).

There were other ways of specifying a IP address numerically, initially;
e.g. for a while at MIT we were using w,x,y,z (with w-z in octal - note the
','s, which were a syntatic tag for the octal form), which was easier to
interpret when looking at a packet dump on a PDP-11. Here:

  http://ana-3.lcs.mit.edu/~jnc/tech/unix/arc/tftp.c.1

is the source for a user command (from July, 1979) which allowed host
addresses to be given in that form.

I'm not sure who came up with the dotted decimal form; I suspect you'd need to
find some really old email archives, and look in that. There was, early on, a
list called "tcp-ip", used by people who were getting their machines ready for
the NCP->TCP/IP conversion. However, I suspect the 'dotted quad' predates
that; there was an even earlier mailing list, used in early experimental work,
by the group working on internet technology, whose name escapes me (it was
something like "internet working group").

It's possible that an IEN:

  https://www.rfc-editor.org/ien/ien-index.html

might mention the 'dotted quad' syntax; TCP and IP meeting minutes
would be a good place to start.

	Noel

PS: The A/B/C addresses are actually a moderately late stage of IP
addresses. At the very start, they were all '8 bits network numbers, and 24
bits of 'rest''.

             reply	other threads:[~2022-05-07 19:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 19:43 Noel Chiappa [this message]
2022-05-08 14:54 ` Michael Kjörling
  -- strict thread matches above, loose matches on Subject: below --
2022-05-09 16:14 Noel Chiappa
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=20220507194336.DC70918C075@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).