Article: 35397 of alt.sysadmin.recovery
From: Rick Dickinson <rtd@notesguy.com>
Newsgroups: alt.sysadmin.recovery
Approved: For external use only.  Do not inhale.
Subject: Re: Planning what's that?
Organization: Dickinson Consulting Services
Message-ID: <25qv3vsh0nvaelfgkla8sj35k8jpb08525@4ax.com>
References: <etoof6095b1.fsf@wormtongue.emschwar>  <1fpjdaa.148u1vadfclf2N%jim@magrathea.plus.com>  <0v8f3vg964gh4gts27itrcl9kskhbd8dj6@4ax.com>  <1fpkfvm.hpyxxwfy022kN%jim@magrathea.plus.com>  <etou1fr7jax.fsf@wormtongue.emschwar>  <1fpkgen.1uz1hp0owpiwwN%jim@magrathea.plus.com>  <bn6h3vck06dsgk3ni99kqbtf2cihiv0ufj@4ax.com>  <jfki3v4net15794o2vi58jm2gtc4pv4uk1@4ax.com>  <1fpovkf.d8xtu01lp9vc4N%jim@magrathea.plus.com> <3e3f59d0$14$fuzhry+tra$mr2ice@news.patriot.net>
X-Newsreader: Forte Agent 1.8/32.548
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 39
Date: Tue, 04 Feb 2003 16:22:18 GMT
NNTP-Posting-Host: 24.55.19.115
X-Complaints-To: abuse@adelphia.net
X-Trace: news1.news.adelphia.net 1044375738 24.55.19.115 (Tue, 04 Feb 2003 11:22:18 EST)
NNTP-Posting-Date: Tue, 04 Feb 2003 11:22:18 EST
Path: news.meer.net!sea-read.news.verio.net!dfw-artgen!iad-peer.news.verio.net!news.verio.net!washdc3-snh1.gtei.net!nycmny1-snh1.gtei.net!news.gtei.net!bloom-beacon.mit.edu!newsfeed.stanford.edu!logbridge.uoregon.edu!router1.news.adelphia.net!news1.news.adelphia.net.POSTED!not-for-mail
Xref: archive.mv.meer.net alt.sysadmin.recovery:35397

On Tue, 04 Feb 2003 01:12:32 -0500, "Shmuel (Seymour J.) Metz"
<spamtrap@library.lspace.org.invalid> is alleged to have written:

>You think RITA is the only bird in there? There's also an RFC for a
>somewhat unusual data transmission medium with moderately less
>bandwidth than you're used to.

Yup: RFC 1149.  Of course, if you want to implement RFC 1149 with QOS,
then you use RFC 2549....

Of course, RFC 1217 deserves a look, as well, if you're looking for
even lower bandwidth.

I'd really like to see RFC 748 implemented, as it would seriously
improve uptime of a number of servers I deal with.  And, seeing as how
February 14th is rapidly approaching, implementation of RFC 1605 might
be appropriate.

Pardon me, I need to initiate an RFC 2324 compliant session.....
<sips>  ...ah, that's good coffee.  Where were we?

Oh, yes.  RFC 2100 provides some host naming advice, applicable to
everyone but TS Eliot, and, for that matter, David Addison (who hates
iambic pentameter).

And, RFC 2795 provides not only a full description of an intriguing
protocol suite, but a wealth of information in its footnotes.

RFC 1776 is particularly informative.

Finally, RFC 1606 provides a much-needed historical perspective on the
usage of IPv9.

 - Rick "Did I miss any good ones?" Dickinson
-- 
The best laid schemes o' Mice an' Men, 
Gang aft agley, 
An' lea'e us nought but grief an' pain, 
For promis'd joy!