From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: ron minnich <rminnich@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] conventions around zero padding in ip4
Date: Sat, 07 May 2022 20:49:15 +0200 [thread overview]
Message-ID: <20220507184915.nXfTT%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAP6exY++wLs+qqAaHL-7bJGfahS6AE1uitxZG1=yP4Se7sZ_rg@mail.gmail.com>
ron minnich wrote in
<CAP6exY++wLs+qqAaHL-7bJGfahS6AE1uitxZG1=yP4Se7sZ_rg@mail.gmail.com>:
|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. [side note: it's weird and wonderful
|to still have so many people "present at the creation" of computing as
|we know it still around, and to find they are so willing to answer
|naive questions!]
|
|Padding is a standard in ip6, possibly because the addresses are so
|long. :: is your friend.
It was/is called compression there, and it was optional ("may") at
first (in RFC 1884). RFC 1884 was an overall wonderful RFC,
uppercase or lowercase are possible, leading zeros in a field were
optional ("not necessary") etc.
Unfortunately RFC 5952 loaded too much Sushi and Sake first, and
turned this to a soldiers dream, "Leading zeros MUST be
suppressed", "Shorten as Much as Possible", " "::" MUST NOT be
used to shorten just one 16-bit 0 field", "longest run [.] MUST be
shortened", "MUST [.] lowercase".
Luckily SMTP seems to keep the elder
|IP4 padding came up recently: the ip command interprets 10.2 as
|10.2.0.0, whereas most things (golang libraries, ping, ...) interpret
|it as 10.0.0.2. The latter interpretation accords with what I learned
|40y ago.
|
|But, I find myself wondering: where was the first use of the IP4 zero
|padding convention?
I did not even know this is possible, but for special software
like postfix SMTP etc., where it de-facto means "substring", so
10.2 is 10.2.0.0/16 (unless i am totally mistakent now).
I could imagine that the introduction of CIDR notation as such
(RFC 1519) played a role?
I have had no idea of networks but modem beeps at all, coming from
a staid pupils' desk with C64 -> DOS -> 4DOS / Windows 3.1 -> 4DOS
/ Windows95B (and then, and then!! It became real) , and there
you had the GUI boxes which "zero padded" anything, unless i am
mistaken.
Btw ipcalc(1) (of RedHat aka https://gitlab.com/ipcalc) is
incapable to deal with that abbreviation at all.
So it maybe is a generation issue, like most other things.
"'Hope i die before i get old".
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2022-05-07 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2022-05-07 19:43 Noel Chiappa
2022-05-08 14:54 ` Michael Kjörling
2022-05-09 16:14 Noel Chiappa
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=20220507184915.nXfTT%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=rminnich@gmail.com \
--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).