Warning
This chapter has not been developed yet. It covers one of six topics that students must select two from for the Achievement Standard 3.44; the other 5 topics have chapters available, so there is still a wide range of choice available. This chapter will be developed during 2013, but it is not guaranteed to be ready in time for teaching 3.44 during 2013.
The brainstorming material is in the Brainstorming section at the end of the chapter
Note
For teachers
This chapter supports the “Network communication protocols” option of the NZ achievement standard 3.44.
Currently all material in this chapter is relevant to the standard, although students can choose one or two examples to focus on to meet the requirements of the standard.
Network communication protocols focus on the techniques applied in computer networks to ensure reliable communication of data between two parts of a network in the face of different kinds of threats and failures. The project would typically be done by giving examples of the sequence of events that occur in these situations, discussing how the protocols and their coding schemes overcome the problems, and evaluating how successful they are at addressing them. This topic is distinct from the coverage of networking in the infrastructure standards because it focuses on the issues that the protocols address (i.e. the design of the protocol), rather than how to configure a system that uses a given protocol
The following lists are concepts, algorithms, techniques, applications and problems that students at level 3 are likely to be able to work with; it isn’t a list of all the key ideas in the area.
Key concepts that are likely to be encountered are: addressing, reliability, security, failure, packet loss, human-readable addresses, quality of service, network performance, cyber attacks, routing Algorithms: (techniques are more relevant to this area than algorithms) Techniques: packet switching, handshaking, acknowledgement, authentication, checksums, wireless and wired security Applications: many real protocols (e.g. TCP/IP) could rapidly become overwhelming at this level. Protocols that students could investigate that are less complex are DNS, UDP, HTTP (get and post), the addressing part of IP, SMTP and CDMA, and Internet security protocols such as SSL, IPSec and PGP.
[some introductory activities/ideas to open up the topic]
[an area that is worth knowing about, including activities/exercises to explore it, and guidance for teachers (possibly to be separated) on how to help students use this topic for A/M/E
[an area that is worth knowing about, including activities/exercises to explore it, and guidance for teachers (possibly to be separated) on how to help students use this topic for A/M/E
[an area that is worth knowing about, including activities/exercises to explore it, and guidance for teachers (possibly to be separated) on how to help students use this topic for A/M/E
[an area that is worth knowing about, including activities/exercises to explore it, and guidance for teachers (possibly to be separated) on how to help students use this topic for A/M/E
[explain where the material above has oversimplified things, and if there are any well-known concepts or techniques that have been deliberately left out because they are too complex for this age group. This may include things that require advanced maths, advanced programming, or things where students have seen the problem but not a thorough solution]
Real snail mail (a snail as part of the network): http://www.cs4fn.org/internet/realsnailmail.php - see also pigeon RFC?
here’s the link to the English version of our form on asymetric encryption: http://it-lehren.de/asymcrypt Feel free to resuse, recycle and adjust whatever suits your plan for fürther csunplugged activities! All the other material (in German) is published at http://informatik-im-kontext.de/index.php/entwuerfe/email-nur-fuer-dich/ Greetings from Berlin, Andreas
From CAS: If you do a TRACERT to 216.81.59.173 you get an amusing result. This of course, may be used as a way of talking about Internet nomenclature and routing of data packets… see article here: http://www.theregister.co.uk/2013/02/15/star_wars_traceroute/
Lovely Pete - thanks. Far from this being a silly thing it’ll be a great way into a discussion about packets, routers and tracing traffic. I find children love running tracert. Running this one would really capture their interest. You could go on to experiment with whether the same route is always returned each time. Trying it from school and home should make that point. Once familiar with the concept, moving to a visual tool to lay the tracert on a map is often a big ‘wow’. There are loads of these available, try for example http://www.yougetsignal.com/tools/visual-tracert/ or Visualware.com. Again, there is often lots of other analysis in these to explore, particularly the time between hops. But there is even more discussion still to be had, particularly for older students and those with inquiring minds. Understanding how tracert works helps in explaining Time To Live, why the internet doesn’t fill up with undelivered packets, and why the results it returns may not be correct. There is a good animation of the concept at Caida (which is a wonderful set of resources to explore). See http://www.caida.org/publications/animations/ and scroll down to the Active Monitoring section. Once students grasp this, the challenge would be to try to explain why tracert always returns the same router order for those that make up the Star Wars intro, when the routes to that point could differ. How come the router names that make up the story don’t get returned in a different order? I think The Register piece you quote would round off a great investigation.