Before I begin, I must emphasize the word "Scratch".
Normally when I make this proposal, I have to go through 7 or 8
iterations until my victim finally realizes that when I say "scratch",
I do mean "scratch." So perhaps the title of this post should be
"Design A New Networking Protocol From Scratch With Near-Zero Regard
For TCP/IP." No attempt shall be made to synthesize the engine via
incremental modification of existing protocols (as was done with
IPv6). We will necessarily make a clean break from all things TCP,
UDP, IP, DCE, CORBA, DCOM, .NET, RPC, SSL, sockets, ARP, RARP, SNMP,
CIDR, NAT, EGP, RIP, DNS, etc. If any legacy elements are recognized
in the new protocol, it shall be those that are fundamentally
persistent, like the end-to-end model and retransmission as a
mechanism to overcome errors.
I would like to propose that a group of us band to together to find a
virtuous framework to the problem that can be broadly defined as
"Distribute d Communication". This proposal is relevant to C++ because
its reference implementation will be in C++.
Specifically, I propose that we create a new full-featured networking
engine that facilitates distributed communication between machines on
a global network. This engine will provide mechanisms for naming,
numbering, addressing, security, mobility, multicasting, and highly
elegant interprocess communication. A library shall be created to
allow third-party developers to write applications against the new
DCE.
After this new engine has been created, we will choose, from among
several "killer" applications, one that demonstrates both the
potential and necessity of the new distributed communications engine,
and implement a prototype of that application against the new engine.
All software shall be written in C++ and made strictly portable
(greater than 95% inter-OS compilability with no allowance for
#ifdef's).
If I did not feel that I had the technical insight to guide such a
project to success, I would not have made the proposal.
This has been a dream of mine for quite a while. If I lost both my
hands, I would continue to type with my teeth to see that it was done.
I am firmly comitted.
I hope to appeal to the insight, creativity, ambition, perceptivity,
and intelligence in all of you, as it would be much more enjoyable to
not do it alone.
I know some of the best C++ programmers in the world lurk in this
group. It is to you I make this appeal. If you have an opinion one
way or another, I would like to hear it, here, or via email.
Best Regards,
-J. C. Jones-
Research Scientist
Normally when I make this proposal, I have to go through 7 or 8
iterations until my victim finally realizes that when I say "scratch",
I do mean "scratch." So perhaps the title of this post should be
"Design A New Networking Protocol From Scratch With Near-Zero Regard
For TCP/IP." No attempt shall be made to synthesize the engine via
incremental modification of existing protocols (as was done with
IPv6). We will necessarily make a clean break from all things TCP,
UDP, IP, DCE, CORBA, DCOM, .NET, RPC, SSL, sockets, ARP, RARP, SNMP,
CIDR, NAT, EGP, RIP, DNS, etc. If any legacy elements are recognized
in the new protocol, it shall be those that are fundamentally
persistent, like the end-to-end model and retransmission as a
mechanism to overcome errors.
I would like to propose that a group of us band to together to find a
virtuous framework to the problem that can be broadly defined as
"Distribute d Communication". This proposal is relevant to C++ because
its reference implementation will be in C++.
Specifically, I propose that we create a new full-featured networking
engine that facilitates distributed communication between machines on
a global network. This engine will provide mechanisms for naming,
numbering, addressing, security, mobility, multicasting, and highly
elegant interprocess communication. A library shall be created to
allow third-party developers to write applications against the new
DCE.
After this new engine has been created, we will choose, from among
several "killer" applications, one that demonstrates both the
potential and necessity of the new distributed communications engine,
and implement a prototype of that application against the new engine.
All software shall be written in C++ and made strictly portable
(greater than 95% inter-OS compilability with no allowance for
#ifdef's).
If I did not feel that I had the technical insight to guide such a
project to success, I would not have made the proposal.
This has been a dream of mine for quite a while. If I lost both my
hands, I would continue to type with my teeth to see that it was done.
I am firmly comitted.
I hope to appeal to the insight, creativity, ambition, perceptivity,
and intelligence in all of you, as it would be much more enjoyable to
not do it alone.
I know some of the best C++ programmers in the world lurk in this
group. It is to you I make this appeal. If you have an opinion one
way or another, I would like to hear it, here, or via email.
Best Regards,
-J. C. Jones-
Research Scientist
Comment