From: "Erik E. Fair" <fair-tuhs@netbsd.org>
To: George Michaelson <ggm@algebras.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] 4.3 BSD network name resolution
Date: Sat, 29 Jan 2022 14:35:39 -0800 [thread overview]
Message-ID: <616.1643495739@cesium.clock.org> (raw)
In-Reply-To: <CAKr6gn1nmY7QQv1SHNCC3n2qOB3UPA6sMYdPOdnyOAk40u7fYw@mail.gmail.com>
See RFC 1101, which I'm in part responsible for because I asked Mockapetris for preservation of the functionality.
I don't think very many sites bother to maintain this info, and I don't know what (if anything) uses it - kinda like the HINFO RR.
Erik Fair
next prev parent reply other threads:[~2022-01-29 22:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 21:48 Will Senn
2022-01-29 21:56 ` Henry Bent
2022-01-29 22:08 ` Henry Bent
2022-01-29 23:02 ` Theodore Y. Ts'o
2022-01-29 22:13 ` Warner Losh
2022-01-29 22:25 ` George Michaelson
2022-01-29 22:35 ` Erik E. Fair [this message]
2022-01-29 22:59 ` Clem Cole
2022-01-29 23:24 ` Phil Budne
2022-01-30 0:09 ` Jeremy C. Reed
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=616.1643495739@cesium.clock.org \
--to=fair-tuhs@netbsd.org \
--cc=ggm@algebras.org \
--cc=tuhs@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).