As per Relevance of the word together, we have this rfc below:
Network Working Group M. A.
Request for Comments: 967 Mitre
December 1985
All Victims
STATUS OF THIS
This RFC notes a significant omission from the networking
and proposes to remedy it. Distribution of this memo is unlimited
An interesting thing happened the other day. Some people were
visiting from IBM Federal Systems Division and, during the course
the conversation, one of them pointed out that they had just as
if not more trouble with the operating system purveyors about
OS "changes" in behalf of networking as anyone else. At the time
just observed that it looked as if we were all victims together
went on to the next point, but further reflection prompts me to
a few thoughts on the topic to the RFC community
o To us, it's axiomatic that networking code is system code when
has to be
o To Them, it's anathema
o We haven't really hit very hard on the point in the
(although I guess I have made a few strong assertions along
lines, here and there, and it's at least implicit in some of
Clark's stuff), unless in my usual slipshod fashion I've
missed seeing it
o It would probably be responsible of us to rectify the
(assuming there is one) since the literature is supposed to
the way the researchers educate the practioners
o Therefore, I propose a new subseries of RFCs on how
networking code was integrated with various OSs, with an
toward subsequent publication of the collection in the
literature (RFCs being only semi-open, after all). I'll
volunteer to coordinate, at least to the extent of taking
from people who are willing to tackle various systems and
them who else is having a bash at the same one for purposes
possible collaboration--and possibly even merging the results
separate efforts if people just send in things they've
done. (I suppose I even have to offer to do a bit of editing,
people want.)
Padlipsky [Page 1]
RFC 967 December 1985
All Victims
What I'd like to see emerge is a bunch of little essays along
lines of what I attempted to do on Multics in RFC 928, pp.14-21,
which would probably be a waste of electrons to reproduce here, but
will if Jon thinks it's worthwhile at some level. With luck
volunteers will emerge to discuss all of the major operating
currently on the net and most of the minor ones as well, since one
the most interesting philosophical aspects of the exercise is to
just what cuts and pastes get made to any OS if it's networked.
guess is that given more modern systems' tendencies to make
device drivers more straightforward and to offer
communication primitives at the system level, the
difficulties to encounter would be getting on the process
path appropriately for Telnet--but that's reasoning ahead of
data. Suffice it to say that each piece should address Host-
protocol interpreter(s) integration as well as Host-Comm
Processor PI (including device driver, if one), plus something
Telnet and something else about FTP (at least to the extent
whether it's per-user or "monolithic"--on the server side, that is),
and, of course, some relevant anatomizing of the OS itself
The moral, it seems to me, is that we have a chance to strike back
the oppressors by showing them what they should be furnishing
their silly off-the-rack systems if they are going to continue
object to our alterations to make the bloody things fit anywhere
right. It's a little extra effort on our part, but it's probably
worthy goal. Indeed, if anybody from IPTO is watching I suppose I'
even go so far as to suggest a pro tem System Integration Task
if I hadn't already volunteered once in this thing and used up
quota
Think about it
EDITOR'S
The editor recalls a session at the 5th Data Communication
(the one at Snowbird) titled "Impact of Networks on Host-
Design and Architecture". (1977)
Padlipsky [Page 2]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
