diff options
| author | antrik <antrik@users.sf.net> | 2009-03-10 22:56:08 +0100 |
|---|---|---|
| committer | antrik <antrik@users.sf.net> | 2009-03-10 23:56:57 +0100 |
| commit | deef6b8304618ed79d96660aba786373016b718d (patch) | |
| tree | c56caffe5d17c6be686e036be63094ae1b0d852f | |
| parent | 297c7451dbf7ae312e7785f3aeb107c8d220b815 (diff) | |
Network stack GSoC task: Monolitic implementation sufficient for the beginnig
A modular implementation is not realistic in the GSoC timeframe; and
starting with a monolithic one probably makes sense from an engineering
standpoint anyways. Also, it's probably better than what we have now...
| -rw-r--r-- | community/gsoc/project_ideas/tcp_ip_stack.mdwn | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/community/gsoc/project_ideas/tcp_ip_stack.mdwn b/community/gsoc/project_ideas/tcp_ip_stack.mdwn index b1a2536f..8306f008 100644 --- a/community/gsoc/project_ideas/tcp_ip_stack.mdwn +++ b/community/gsoc/project_ideas/tcp_ip_stack.mdwn @@ -24,10 +24,13 @@ can just directly access the desired layer. All kinds of packet filtering, routing, tunneling etc. can be easily achieved by stacking compononts in the desired constellation. -While the general architecture is pretty much given by the various network -layers, it's up to the student to design and implement the various interfaces -at each layer. This task requires understanding the Hurd philosophy and -translator programming, as well as good knowledge of TCP/IP. +Implementing a complete modular network stack is not feasible as a GSoC +project, though. Instead, the task is to take some existing user space TCP/IP +implementation, and make it run as a single Hurd server for now, so it can be +used in place of the existing pfinet. The idea is to split it up into +individual layers later. The initial implementation, and the choice of a TCP/IP +stack, should be done with this in mind -- it needs to be modular enough to +make such a split later on feasible. This is [[GNU_Savannah_task 5469]]. |