summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/tcp_ip_stack.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'community/gsoc/project_ideas/tcp_ip_stack.mdwn')
-rw-r--r--community/gsoc/project_ideas/tcp_ip_stack.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/tcp_ip_stack.mdwn b/community/gsoc/project_ideas/tcp_ip_stack.mdwn
index b56bff51..331336ac 100644
--- a/community/gsoc/project_ideas/tcp_ip_stack.mdwn
+++ b/community/gsoc/project_ideas/tcp_ip_stack.mdwn
@@ -21,7 +21,7 @@ more flexibly. Rather than just having the standard socket interface, plus some
lower-level hooks for special needs, there are explicit (perhaps
filesystem-based) interfaces at all the individual levels; special application
can just directly access the desired layer. All kinds of packet filtering,
-routing, tunneling etc. can be easily achieved by stacking compononts in the
+routing, tunneling etc. can be easily achieved by stacking components in the
desired constellation.
Implementing a complete modular network stack is not feasible as a GSoC
@@ -34,7 +34,7 @@ make such a split later on feasible.
This is [[!GNU_Savannah_task 5469]].
-Possible mentors: ?
+Possible mentors: zhengda
Exercise: You could try making some improvement to the existing pfinet
implementation; or you could work towards running some existing userspace