[e2e] typical network syllabus

[Wu Yan]

Hi,
    As a student, I think splitting is a good idea. Maybe an introductory
course could go first, which covers the concepts of most topics. After
taking this course the students could have an overview of networking
technology. Later they could take advanced courses which deal with specific
topics. For example, a course on network performance, a course on security,
a course on mobile networks.

    It's very hard to include all the materials in one semester-based
course. Some materials are from different areas. For example, security needs
knowledge about cryptography; while mobility is related to materials covered
in wireless communications.



Yan Wu

Telecommunication Research Center

Electrical Engineering Department

Arizona State University

Yan.Wu3 at asu.edu







----- Original Message -----
From: "Henning G. Schulzrinne" <hgs at cs.columbia.edu>
To: "Constantinos Dovrolis" <dovrolis at mail.eecis.udel.edu>
Cc: "Yavatkar, Raj" <raj.yavatkar at intel.com>; "Craig Partridge"
<craig at aland.bbn.com>; "Lloyd Wood" <L.Wood at eim.surrey.ac.uk>;
<end2end-interest at postel.org>; <kurose at cs.umass.edu>
Sent: Tuesday, October 30, 2001 1:09 PM
Subject: Re: [e2e] typical network syllabus


> Thanks for the list. I'm not sure a single 'advanced' course is
> necessarily the best option, given the diversity of topics and
> approaches.
>
> At Columbia, we've been splitting this up into multiple courses,
> including a course on network security and a course on multimedia (with
> multicast, QoS, streaming, scheduling, etc.). See
> http://www.cs.columbia.edu/6181 and
> https://www.cs.columbia.edu/~angelos/teaching/4180.html or
> http://www.cs.columbia.edu/~hgs/teaching/security/
>
> Also, I think wireless and mobility issues deserve broader coverage, in
> addition to web issues (where programming, rather than theory, tends to
> be a major focus).
>
> I don't think you can do justice to network security in just one or two
> lectures, given the background in crypto required to make this more than
> a 30,000' view. Focusing a course on media has the advantage that it
> lends itself to a progressive project, incorporating multicast and
> multimedia.
>
>
> Constantinos Dovrolis wrote:
> >
> > A related question is whether one semester-based course
> > in networking is enough these days. Especially at a
> > graduate program, it would make sense to have an "advanced
> > networking course" with a totally different syllabus than
> > the (required?) undergraduate networking course.
> >
> > Such graduate-level courses are given today in several
> > schools and they mainly cover research papers. Having a textbook
> > that is appropriate for such a 2nd course would be quite
> > useful I think. Possible topics could be:
> > - Router architectures
> > - "Internet algorithmics" (IP lookups, flow classification)
> > - Packet scheduling
> > - Intradomain routing and going deeper in OSPF
> > - Interdomain routing and going deeper in BGP
> > - TCP's congestion control and recent advancements (e.g., SACK)
> > - QoS and traffic management
> > - Multicasting protocols
> > - Traffic modeling and measurements
> > - Networking security issues
> > - HTTP and other Web-related protocols
> > - Web middleware
> > - Streaming apps
> > -  (...)
> >
> > Raj, I am not sure whether any of the books that you mentioned
> > covers all/most of these topics in sufficient depth. I think
> > that the existing textbooks were meant to be mainly appropriate
> > for a first course in networking. I may be wrong..
> >
>
> --
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
>