Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

CPE5006 Virtual Private Networks

Chief Examiner

This field records the Chief Examiner for unit approval purposes. It does not publish, and can only be edited by Faculty Office staff

To update the published Chief Examiner, you will need to update the Faculty Information/Contact Person field below.

NB: This view restricted to entries modified on or after 19990401000000

Unit Code, Name, Abbreviation

CPE5006 Virtual Private Networks (17 Mar 2004, 11:53am) [VPN (17 Mar 2004, 11:53am)]

Reasons for Introduction

Reasons for Introduction (17 Mar 2004, 12:39pm)

The past decade has witnessed unprecedented advances in network based information processing. The number of organisations that have been connected to the open and insecure Internet has been growing steadily at an exponential rate. A large number of these organisations are now moving towards establishing corporate Intranets within the organisations while maintaining access to the Internet. Following an emerging future direction in this line of development, an increasing number of organisations are further extending their corporate Intranets to so-called Extranets. These Extranets would facilitate reliable and secure information sharing and transactions between business partners via the open Internet. The key technology that underpins Intranets and Extranets is virtual private networks (VPNs), and it is particularly important for a network computing professional to understand VPNs and be able to use VPNs to design, implement and manage an Intranet and Extranet for a business organisation. It is therefore timely to introduce a level 5 subject in the Master of Network Computing course that provides students with an opportunity to understand thoroughly the technical details of major protocols and tools used in virtual private networks (VPNs), the knowledge and skills required in using VPNs to design and implement Intranets and Extranets, and fundamental techniques for managing Intranets and Extranets.

Reasons for Change (17 Mar 2004, 12:45pm)

The unit was originally proposed in 1999 for a tentative class size of 20. The changes account for the technological developments since then and the impact of a larger class size.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (17 Mar 2004, 11:59am)

At the completion of this subject, students should have

Relationships, Communication and TeamWork (Social Domain Objectives) (17 Mar 2004, 12:03pm)

The students would work in small groups for their second assignment.

Unit Content

Summary (17 Mar 2004, 12:04pm)

Layered structure of networks, security threats in an open network environment, and basic security. Detailed exposition of major tools and protocols used in VPNs, including firewalls, IPSec, Internet Security Association and Key Management Protocol (ISAKMP), Internet Key Exchange (IKE), Point-to-Point Protocol (PPP) and Point-to-Point Tunnelling Protocol (PPTP), Layer 2 Tunnelling Protocol (L2TP), Secure Sockets Layer (SSL), and SOCKS. Exposition of principles and methodologies for the design and implementation of Intranets and Extranets using VPNs. Techniques for managing security, naming and address services, and performance of a VPN.

Recommended Reading (17 Mar 2004, 12:06pm)

by Dennis Fowler, Paperback: 222 pages ; Dimensions (in inches): 0.68 x 9.03 x 7.04, Publisher: Morgan Kaufmann; 1st edition (June 15, 1999), ISBN: 1558605754

by Oleg Kolesnikov, Brian Hatch, Paperback: 408 pages ; Dimensions (in inches): 0.84 x 8.96 x 7.10, Publisher: Que; 1st edition (February 4, 2002), ISBN: 1578702666

Teaching Methods

Mode (17 Mar 2004, 12:07pm)

On-Campus

Strategies of Teaching (17 Mar 2004, 12:08pm)

The concepts covered in the lectures are reinforced during the tutorials with the aid of examples and exerices. Hands-on work is included within the tutorials to link the theory with the practice to enhance the understanding. The assignment work allows students develop research and problem solving skills; individually and within a team environment.

Teaching Methods Relationship to Objectives (17 Mar 2004, 12:09pm)

In Summer Semester the subject will have a 3-hour lecture and a 2-hour tutorial (in computer laboratories) per week for ten weeks, for other semesters the lectures and tutorial classes would be of 2-hour duration each per week for 13-weeks.

The lecture stream will present the implementation details and design principles of VPN protocols as well as other relevant networking protocols. It will also show students how to build VPNs. This will address all the five objectives.

The tutorial sessions will reinforce the concepts learned during the lectures through the hands-on work and completion of the exercises relating to the theory covered in the lectures. This will address objectives 1, 2, 3, and 5.

Assessment

Strategies of Assessment (17 Mar 2004, 12:13pm)

The assessment would be done through assignment work and the practical exercises done during the tutorials. The assignment work would comprise two assignments worth 60% of the marks and the assessment of the tutorial work would be worth the remaining 40% of the marks.

Assessment Relationship to Objectives (17 Mar 2004, 12:14pm)

The first assignment would be worth 20% of the total marks for the unit and would have to be completed individually. The assignment would entail in a report written by the student based upon the information available within the lecture notes, the text books, and information obtained by researching of the Internet and the Library. This will address objectives 1 and 2.

The work done in the tutorials would be assessed at the end of the semester and will be worth 40% of the total marks for the unit. This will address objectives 1,2, 3, 4, and 5.

The second assignment would be worth 40% of the total marks for the unit and would be done as in groups. It would entail in a wide range of activities including the research, design, implementation, testing, and presentation of their project in a work-environment-like situation. This will address objectives 2, 3, 4, and 5.

Workloads

Workload Requirement (17 Mar 2004, 12:15pm)

Students are expected to spend an average of 12 hours per week for a semester on this unit, with the following detailed breakdown:

Resource Requirements

Lecture Requirements (17 Mar 2004, 12:16pm)

Lecture for 180 students.

Tutorial Requirements (17 Mar 2004, 12:17pm)

9 tutorials for 20 students each.

Laboratory Requirements (17 Mar 2004, 12:18pm)

A laboratory containing approximately twenty (20) personal computers with Internet connection, removable disks, and some additional networking hardware (e.g. hubs, cables, and connectors).

Staff Requirements (17 Mar 2004, 12:19pm)

Lecturer, 2 hours per week. Tutor, 2 hour per week per tutorial session.

Software Requirements (21 Oct 2005, 1:04pm)

None

Library Requirements (17 Mar 2004, 12:30pm)

Library Impact Statement was completed and sent to library at the submission of the course proposal document.

Originals of signed library impact statements are held by the Faculty of Information Technology Secretariat. Copies may be available on request (Tel. 9903 2726/2983, Fax 99032745, email jillian.oldfield@infotech.monash.edu.au).

Teaching Responsibility (Callista Entry) (17 Mar 2004, 12:20pm)

100% from the School of Network Computing.

Implications for CASPA (17 Mar 2004, 12:22pm)

None

Interfaculty Involvement (17 Mar 2004, 12:22pm)

None

Interschool Involvement (17 Mar 2004, 12:23pm)

None

Prerequisites

Prerequisite Units (17 Mar 2004, 12:24pm)

None

Prerequisite Knowledge (17 Mar 2004, 12:29pm)

Admission to the Master of Network Computing, or equivalent Masters level programs of the Faculty of Information Technology; some programming experience in C, C++ or Java.

Corequisites (17 Mar 2004, 12:30pm)

None

Prohibitions (17 Mar 2004, 12:31pm)

None

Alias Titles (17 Mar 2004, 12:33pm)

None

Level (17 Mar 2004, 12:34pm)

5

Proposed year of Introduction (for new units) (17 Mar 2004, 12:34pm)

Semester 2, 2003

Frequency of Offering (17 Mar 2004, 12:35pm)

Once or twice a year as required.

Enrolment (17 Mar 2004, 12:35pm)

180

Location of Offering (17 Mar 2004, 12:35pm)

Caulfield

Faculty Information

Proposer

Asad Khan

Contact Person (17 Mar 2004, 12:36pm)

Asad I. Khan

Unit Coordinator (17 Mar 2004, 12:36pm)

Asad I. Khan

Approvals

School:
Faculty Education Committee:
Faculty Board:
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

17 Mar 2004 Asad Khan modified UnitName; modified UnitName; modified Abbreviation; modified UnitObjectives/ObjText; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjAffective; modified UnitObjectives/ObjPsychomotor; modified UnitObjectives/ObjPsychomotor; modified UnitObjectives/ObjSocial; modified Classification; modified UnitContent/Summary; modified UnitContent/RecommendedReading; modified Teaching/Mode; modified Teaching/Strategies; modified Teaching/Objectives; modified Assessment/Strategies; modified Assessment/Objectives; modified Workload/WorkHours; modified ResourceReqs/LectureReqs; modified ResourceReqs/TutorialReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SchoolReqs; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/CaspaImpact; modified ResourceReqs/InterFaculty; modified ResourceReqs/IntraFaculty; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/OtherReqs; modified ResourceReqs/OtherReqs; modified ResourceReqs/OtherReqs; modified Prerequisites/PreReqUnits; modified Prerequisites/PreReqKnowledge; modified ResourceReqs/LibraryReqs; modified Corequisites; modified Prohibitions; modified AliasTitles; modified Level; modified DateOfIntroduction; modified Frequency; modified Enrolment; modified LocationOfOffering; modified FacultyInformation/FIContact; modified FacultyInformation/FICoordinator
17 Mar 2004 Asad Khan modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RChange
17 Oct 2005 David Sole Added Software requrirements template
21 Oct 2005 David Sole Updated requirements template to new format

This version: