This file will contain the schedule of student lectures/topics for the routing class: We will assume that each lecture will be at least N minutes (assume N == 30-40 until we know better, 30 is minimum). For each lecturer, we will have the following info here: who - name/email when - date/and time-slot on that day (4 talks per day until we know better) what - topic and title if possible bio - who you are and a little about you URL/location - for the major paper (RFC/draft) to read and any supplementary papers that may be of interest. Students are expected to find/read the 1st item. ----------------------------------------------------------- 1. who: Mark Morrissey, markm@cse.ogi.edu when: Feb 17, time slot #1 what: SNMP v3 security model overview bio: Mark is a senior research programmer for the DISC research group at OGI and also the class TA. He has extensive networking experience from such diverse standpoints as writing CCITT X.21 operating system support for Sperry Univac (UNISYS), developing SNMP management standards for Intel, being a network engineer for Intel's Hawthorne Farm campus, and, as OGI/Director of Information Technology, helping to design the new high-speed switched network infrastructure now being deployed at OGI. URL/location: http://www.ibr.cs.tu-bs.de/projects/snmpv3/ (RFC 2274) http://www.simple-times.org/ (current issue overviews v3) 2. who: Bjorn Chambless, bjorn@cs.pdx.edu when: Feb 17, time slot #2 what: HARP, Home Agent Redundancy Protocol bio: URL/location: ftp://zymurgy.admin.ogi.edu/route-class/draft-chambless-mobileip-harp-00.txt 3. who: Zheng Chen, zchen@cs.pdx.edu when: Feb 17, time slot #3 what: Internet Mobility 4x4, Stuart Cheshire, Mary Baker bio: Zhong Chen is a Master's student of CS Department, PSU. He is currently involved in the Secure Mobile Network project of PSU. He is responsible for implementing advanced security for Mobile IP and implementing DCHP support in Mobile IP so that Mobile Hosts can obtain temporary addresses for routing purposes at foreign networks while maintaining "permanent" home address for identity and continuous transport layer connectivity. He worked 2 years at Network Research Center, Tsinghua University, Beijing, China, after he received a Master's degree in Electrical Engineering from the same university before coming to study at PSU. URL: http://ResComp.Stanford.EDU/~cheshire/papers/InternetMobility4x4.html (postscript available, look on zymurgy) also: Mobile-IP rfc 2002 (and info in class text about it as well) ----------------------------------------------------------- 4. who: Dustin Harris/Intel when: Feb 24, time slot #1 what: IPv6 address architecture bio: Dustin has worked as a network engineer at Intel on the Ronler Acres campus for two years. The job basically requires him to support existing networks and build new ones. His network experience includes multi-protocol routing, ATM switching, network management, and ethernet switching technologies. He graduated with a BS in Computer Science from Georgia Tech in 1995. URL/location/s: (Note: arch-vv2-06.txt is NEW out) ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-addr-arch-v2-06.txt ftp://ds.internic.net/internet-drafts/draft-ietf-ipngwg-unicast-aggr-03.txt 5. who - Prakash Iyer / Prakash_Iyer@ccm.jf.intel.com - Monika Jain / monika_jain@ccm.jf.intel.com when - Feb 24, time slot #2 what - Reliable multicast protocols - a brief background of the problem - look at various proposed solutions for reliability and scalability We plan to focus on 2 papers: ** A Reliable Multicast Framework for Light-weight Sessions and Application Level Framing ** Receiver driven layered multicast and will also present other protocols (time and papers TBD). bio - Prakash :- Works in Intel Architecture Labs. IP telephony, real-time A/V, 320/323 conferencing. Monika :- Master's student at OGI. Works in Intel Networking Department. Currently working on automation of testing efforts. URL/location - http://www-nrg.ee.lbl.gov/floyd/srm.html http://http.cs.berkeley.edu/~mccanne/papers.html#sigcomm96 6. who: Jen Ye jenye@cs.pdx.edu when: Feb 24, time slot #3 what: MADRP (Mobile Ad Hoc Demand Routing Protocol) bio: a PSU graduate student and one of the research assistants for Jim Binkley on the Secure Mobile Networking Project group. (See http://www.cs.pdx.edu/research/SMN) URL: http://www.cs.pdx.edu/~jenye/routing/ who: Paul Doherty when: Feb 24, time slot #4 what: GPS based addressing and routing bio: TBD url: rfc 2009 --------------------------------------------- 7. who: Sachin_Godse@ccm.jf.intel.com when: Mar 3, time slot #1 what: RSVP, bio: url: rfc 2205 8. who - Kristen Carlson (kristen_carlson@ccm.jf.intel.com) when - March 3, Time slot #2 what - GMRP and GARP bio - I am a software engineer in Intel's Network Products Division. I write device drivers and intermediate drivers for Network adapter cards. I am also persuing a MS in CSE at OGI. I graduated with a BS in Computer Science from Portland State in 1997. URL/location - If you have access to the IEEE 802.1p spec, you could glance at that. Otherwise, try: http://www.3com.com/technology/research/topics/multimedia_world.html - for a overview of GMRP http://www.globecom.net/(nocl)/ietf/draft/draft-ietf-issll-802-00.shtml - for overview of Priority tagging. http://iworks.interworks.org/conference/IWorks97/sessions/sn009/paper.html - brief overview of GARP who: Kang Li, kangli@cse.ogi.edu when: Mar 3, time slot #3 what: BGP in more depth bio: Kang is now a student in OGI. He is currently involved in the Multimedia and Quality of Service project in DISC of OGI. His research is on the multimedia adaptation on network. He worked in China Education Network Center for 3 years, was responsible for the backbone routing and network management. url: (stick with the text). However cisco has some good BGP material on their web site: http://www.cisco.com/univercd/cc/td/doc/cisintwk/ics/icsbgp4.htm who - Hao Xu haox@pogo.wv.tek.com or xuhao@cs.pdx.edu when - March 3 #4 what - QoS Routing (qosr) Bio - Hao is a software engineer at Tektronix. He is acting as a network engineer on ftpd, telnetd, httpd for the Tek Phaser color printer. He was a research assistant to Jim Binkley at PSU in the Secure Mobile Networks project for a year and he is interested in pursuing some further TCP/IP network research. Url - http://www.ietf.org/html.charters/qosr-charter.html Get the draft (on zymurgy too) draft-ietf-qosr-framework-02.txt --------------------------------------------- who: Dan Clark, dlc@ncube.com when: March 10, time slot #1 what: ATM circuit setup I would like to propose that I cover ITU Q2931/UNI 4.0 & touch on ILMI as it pertains to address registration (see references below). I would really just like to cover the basic layer three transactions required to establish an SVC connection by illustrating a message diagram and walking through the individual packet layouts. This would hardly cover UNI4.0 since most of the basics are defined in Q2931. bio: TBD url: primary reference: http://cell.ucs.indiana.edu/cell- relay/docs/Q.2931.html Broadband Integrated Services Digital Network Signaling System secondary (no, you don't have to read them all or even any): 1 http://ds.internic.net/rfc/rfc1754.txt IP over ATM WG's Recommendations for ATM Forum's Multiprotocol BOF V1 2 http://ds.internic.net/rfc/rfc1577.txt" Classical IP and ARP over ATM 3 http://ds.internic.net/rfc/rfc1932.txt IP over ATM: A Framework Document 4 ftp://ftp.atmforum.com/pub/approved-specs/af-ilmi-0065.000.pdf ILMI 4.0 (Integrated Layer Mgmt. Interface) 5 ftp://ftp.atmforum.com/pub/approved-specs/af-sig-0061.000.pdf" UNI Signaling 4.0 6 http://ds.internic.net/rfc/rfc1755.txt" ATM Signaling Support for IP over ATM who - James H. Bombardier JHBomber@AOL.com when - March 10, time slot #3 what - IP Everywhere may soon include/bypass the telco link layer. bio - I am currently a Senior Systems Engineer with a division of Fort James Corp. My initial exposure to networking was with paper tape/TTY terminals in 1969 where I was helping Weyerhaeuser develop a modified operating system that would automagically queue and process these paper tape messages (lumber orders) at a rate of 300 per minute. URL/location My discussion will focus on recent and potential improvements in telco link layer offerings and how they may be bypassed entirely to provide 10Mbps to homes or businesses. I hope to have reading references soon. url: I would suggest the following three URLs, the first of which is the most entertaining: http://www.isen.com http://www2.computerworld.com/home/online9697.nsf/all/971208adsllinks http://www.webproforum.com/agcommsys/index.html ------------ who: Hongwei Zhao, hwzhao@ee.pdx.edu when: March 10/ time slot #4 what: EIGRP bio: A master student of ECE of OGI. Before I worked for Ericsson Company Ltd. (China) for 2 years, was responsible for the network management. url: TBD (info in book though and on cisco web pages) --------------------------------------------- Following students will have to give Jim a 1-1 personal lecture. I will try to announce the place/time if there are others who might be interested. 1. noone! --------------------------------------------------- pre-lecture notes: Dan Clark - ATM Here is some more detail on the assignment. Asynchronous Transfer Mode (ATM) networks provide either permanent virtual circuit (pvc) or switch virtual circuit (svc) setup for routing packets between endpoints in the network. A PVC network is established by creating fixed tables at the endpoints and the corresponding switches used to create the path between source and destination. A SVC network uses signaling services to dynamically create and destroy connections. The multitude of IP based applications can utilize the higher bandwidth provided by ATM networks with additional support from operating system device drivers for services ranging from classical IP (CIP) to multi- protocol over ATM (MPOA)<1>. What are the detailed transactions which occur on an SVC network in order for two endpoints to establish a virtual circuit for IP based communication? The first step to understanding how IP packets are transported on an ATM network is to select a protocol to carry the data. The implementation of CIP is one fundamental mechanism for providing packet transport. RFC 1577<2> defines IP and ARP over ATM and lays out the eight byte header which replaces the fourteen byte header used for transport on an ethernet network. The elegance of CIP is the simplicity with which it can be implemented at the bottom of an existing operating system stack. ATM ARP is used to maintain ARP data for IP packet routing. Both CIP and ATM ARP are used on a virtual circuit once it has been connected. A high level overview see the IP/ATM framework document RFC 1932<3>. A PVC network can correlate virtual circuits to destination IP addresses by creating ATM ARP table entries which define the coupling of individual paths. As the ARP table entry is created an open is attempted on the virtual circuit. A successful open is assumed to provide an appropriate connection to an endpoint. Normal IP data flow is then attempted over the new connection. A similar process must be performed at the destination node. Dynamic configuration of a network proceeds first by establishing the address of the endpoint in a private network. In an ATM network an endpoint address consists of a network prefix and an end system identifier (ESI). The value of the network prefix is supplied by the UNI signaling side of the network. The end system identifier is similar in size and nature to a hardware ethernet address. The ATM Forum Integrated Local Management Interface (ILMI) Specification V4.0 defines an SNMP protocol for address configuration and registration. Automatic configuration (section 8.3.4) and address registration (section 9) define the procedures and MIB for obtaining the network prefix for an ATM end point<4>. A SVC network provides the capabilities for dynamically binding IP connections to virtual circuits. The heart of the protocol for establishing dynamic connection is defined in ITU Telecommunications standard Q.2931<6>. The ATM Forum further reconciled with ITU Q.2931 in the ATM User-Network Interface (UNI) Signaling Specification UNI 4.0<6>. The ITU standard defines VCI=5 as the single reserved channel for point-to-point signaling. The basic signaling functions outlined are: 1) call/connection request, 2) call/connection answer, 3) call/connection clearing. A description of the control states of individual calls defines a finite state machine for endpoints. A subsequent definition of the messages provide the mechanism for establishing the connections. The core messages for establishing communication are: alerting, call proceeding, connect, connect acknowledgment, setup. The clearing messages are release, release complete. Finally, there are several informational messages: notify, status, status inquiry. For further background material on signaling for IP/ATM see RFC 1755 <7>. ---------------------------------------------------