Instructor | Announcements | Course Info | Class Material | Schedule | Project | Grade | General Policy | Related Links

Instructor

Richard Sinn
Email: richardsinn@yahoo.com
Office Hours: After class, by appointment or email only

Richard Sinn has been teaching in the Computer Engineering and Computer Science departments at San Jose State University since 1998. He also served as Adjunct Professor at University of Minnesota. In addition to his teaching career, Richard is the Security Architect at the Real Time Communication group at Yahoo! Inc. Prior to this he held various senior positions at IBM, Oracle and different Silicon Valley startup companies. Richard is an inventor and has filed over ten invention disclosures (patents). He is also a frequent writer for various magazines and journals, and a frequent speaker at regional and national technology conferences.

Announcements

Check back every now and then for updates.

Jan 24, 2010:

General:

Bring a computer to class. You will need that for lecture assignment.

Add permission code

Students asking for permission codes should complete the request form available on the department wiki at <http://wiki.cmpe.sjsu.edu/lib/exe/fetch.php/documents:permission_number_request_form.pdf>.

The instructor collects thee forms on the first day of classes and passes them all to Lee Chang (who will serve as a clearinghouse). Print your own or More forms will be available in the department office.

No Open university student add in general.

Honesty Pledge can be downloaded here.

Class time:

Every Wednesday at 6:30pm <-----

Class room:

ENG-337 (Both lecture and lab)

Course Information

Objectives

In-depth study of the principles and architecture of Internet protocols in current practice. Analysis of protocols of network, transport, and application layers. Topics will also cover emerging network architecture and protocols. Network analysis project.. Prerequisite: CMPE 206 or instructor consent. Misc/Lab: Lecture 2 hours/lab 3 hours.

Grading

Apart from big term project(s) and presentation, there are homework assignments, a mid-term exam and a final exam. Some exams might be take-home. The weightings for grading are: Term Project(s) 40%, Homework 20%, Midterm 10%, Final Exam 10%, and Team Presentation / Lecture assignments 20%.

No Late Assignment Submission. Put everything in an envelop when submit any material.

Policy Info

Academic Dishonesty

This is just a reminder that ALL cases of academic dishonesty (plagiarism, cheating, etc) should be reported to the chair.

In order be fair to the students we have to maintain a uniform process for handling such cases - there really is no faculty discretion once a case of plagiarism or cheating has been discovered - ALL cases will be reported.

The most relevant Senate policy w.r.t this is S07-2. The policy defines academic dishonesty as follows (please note the very low tolerance definition of plagiarism):

1.1 CHEATING
San José State University defines cheating as the act of obtaining or attempting to obtain credit for academic work through the use of any dishonest, deceptive, or fraudulent means. Cheating includes:

1.1.1. Copying, in part or in whole, from another’s test or other evaluation instrument including homework assignments, worksheets, lab reports, essays, summaries, quizzes, etc.;

1.1.2. Submitting work previously graded in another course without prior approval by the course instructor or by departmental policy;

1.1.3. Submitting work simultaneously presented in two courses without prior approval by both course instructors or by the department policies of both departments;

1.1.4. Using or consulting sources, tools or materials prohibited by the instructor prior to, or during an examination;

1.1.5. Altering or interfering with the grading process;

1.1.6. Sitting for an examination by a surrogate, or as a surrogate;

1.1.7. Any other act committed by a student in the course of their academic work that defrauds or misrepresents, including aiding others in any of the actions defined above.

1.2 PLAGIARISM
San José State University defines plagiarism as the act of representing the work of another as one's own without giving appropriate credit, regardless of how that work was obtained, and submitting it to fulfill academic requirements.

Plagiarism includes:

1.2.1 Knowingly or unknowingly incorporating the ideas, words, sentences, paragraphs, or parts of, or the specific substance of another's work, without giving appropriate credit, and representing the product as one's own work;

1.2.2 Representing another’s artistic/scholarly works such as musical compositions, computer programs, photographs, paintings, drawing, sculptures, or similar works as one's own.

Pledge

Class Material

Lecture Notes

Textbook:

Security Part:

 

Network Part:

TCP/IP Illustrated, Volume 1: The Protocols (Hardcover).

There will be reading assignments in almost every class and reading materials will be tested upon.

Performance Part:

Lecture Notes

 

Non-Textbook: Reading material will be online on this web site before every lecture. Reading this semester:

• HTTP: http://www.w3.org/Protocols/, ftp://ftp.isi.edu/in-notes/rfc2616.txt
• FTP: http://www.ietf.org/rfc/rfc0959.txt
• BitTorrent: http://www.bittorrent.com/protocol.html
• DNS: http://www.faqs.org/rfcs/rfc1035.html, http://www.faqs.org/rfcs/dns-rfcs.html
• IKE: http://www.ietf.org/rfc/rfc2409.txt
• IPSEC Intro: http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23f/ipsec/ch01.htm
• XKMS: http://www.w3.org/TR/2005/REC-xkms2-20050628/
• ICE: http://www.w3.org/TR/1998/NOTE-ice-19981026
• LDAP: http://www.faqs.org/rfcs/rfc2251.html
• OCSP: http://www.faqs.org/rfcs/rfc2560.html
• SSL/TLS: http://wp.netscape.com/eng/ssl3/draft302.txt
• DHCP: http://rfc.net/rfc2131.html
• NFS: http://www.faqs.org/rfcs/rfc1813.html
• Kerberos: http://web.mit.edu/kerberos/www/

Reference

Pick one of the references for term paper. Please spend the time to read and actually reseach (program) into the topics. The class expects a high quality research paper, not some collection of combined internet web pages ...

Schedule

Term Project

Title

Cross Domain Chat Protocol Design Project

Description

The goal of the project is to give you explosure on real life development environment and network programming and design experience on the web. There are two parts into the term project. Part 1 is an individual part performed by one student and part 2 is a group part performed by four group members. The name of the project is called Cross Domain Chat Protocol Design.

Part 1 - User Portal (individual part)

Create a user portal in the form of a web site. This user portal allows a self-service creation of a USER. Each user can create a ROOM and starts a chat session with other USER from the same user portal (domain). Here is a list of rerquirements:

• You must have your own domain for yourself. Otherwise, you cannot do cross domain communication later on in part 2.
• A USER can create and join multiple ROOMs.
• A ROOM can hold one or more USERs.
• You must make the following architecture/design decision:
  • What is domain name to obtain? (in one of the homework).
  • What UI engine do I use to build the web site?
  • What development tools (language, backend, etc) will you use for this project?
  • Any extra feature to support.
  • This is a real web site development project, so enjoy the chance to do so ...

Part 2 - Cross Domain Chat Protocol Design

Form a group of 4 and create a mechansim that allows 4 user portals to create a real time chat session among real web sites. In other words, USERS from a web sites can invite other USERS from the same web site or different web site to join a ROOM. You must define and implement your own communication protocol for this cross domain communication. Besides, as a group you must decide the following:

• The exchange protocol / format of the portals.
• Do you and how do you implement authentication among sites?
• Do you implement secure chat?
• How do you implement access control? So, people not invited to the room cannot join the chat session.

More info will be provided in the semester.

Grading

Project team has to decide on various issues such as:

• What domain name to signup?
• What is the development language to use? Php, Perl or something else.
• Do we use database such as MySQL? What is the database schema to use?
• How do we secure the interface with the backend?
• How do we secure the content (for sharing) on the web server?

As the whole class will be working on similar projects, relative grading will be used. In other words, all the projects will be ranked within the class and points will be assigned accordingly. There are two parts in the project:

• Part I: Requirement Analysis and Design 33%
• Part II: Final report and/or Implementation 67%

Handin

Project Part I consists of a document includes the following:

• Detail project plan. The list of features and functions should be included in the project.
• Schedule and division of work among team members
• Prototype results

Project Final Part will be covered later in class

Final Word of Warning

This is not an "easy" class and the project is an essential part of the overall grade. People who did not deliver the project well enough could really hurt their grade as the project contains more than 40% of the overall grade.

Avoid:

• Forming group late
• Changing group in the middle of the semester
• Start late and rush any part of the project
• Form a group of less than 3 people
• Not enough extra features if the group is more than 3 people
• Did the final integration of the project late
• Do not do enough testing
• All but actually one person in the group does all the programming (No, people do not get lucky and teammate will complain...)

Team Research Presentation (Optional this semester)

Each team will be given one topic to research and present during the semester. Mid-term and final will contain some questions related to the topics presented. The team needs to prepare the following:

• PowerPoint Presentantion of the topic. Pick something you would like to highlight in the topic instead of a general overview.
• A 5 short-paper with detail reference on the topic
• Perform face-to-face presentation in class (10 min)

The following are the possible topics:

• RFID network protoco
• SMTP
• SNMPl
• SSH
• SCP
• Kerberos
• Radius
• Network Intrusion Detection
• SOAP
• UDDI
• XKMS
• NAT
• EAP
• IPX/SPX
• POP3/IMAP4
• BGP
• EGP
• IGP
• RIP
• OSPF
• Socks
• More tables from TCP/IP suite:

Grade

Email sinn@openloop.com to check your grade if necessary.

General Policy

The university and departmental policies and deadlines for course drop will be applied. Makeup exams cannot be offered, except under exceptional conditions, such as documented serious illness/accident, etc., and only at the professor's discretion.

Each student is responsible for his/her individual assignment, and must not copy anyone else's work. Students who borrow solutions from others will find themselves unable to pass the course. The minimum penalty for every student involved in the duplication of individual assignments or exams will be receiving a zero score on the submitted work.

For group project, all the work has to be done by your OWN group. Do not try to download "free code" from the Internet and hand in as a project. WE WILL FIND OUT. Do not share your work with others. So DO YOUR OWN WORK and EARN your grade.

Related Links

Instructor | Announcements | Course Info | Class Material | Schedule | Project | Grade | General Policy | Related Links