Student Lectures - Winter/2002 PSU/CS 595 Internet Routing 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 and email when - TBD, assigned by Jim what - title of talk including authors 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: Biddappa N. Berera bid@cs.pdx.edu bnbiddappa@yahoo.com When: TBD, assigned by Jim What: Nimrod Routing Architecture Bio: Born and brought up in India. Completed my Bachelor's degree in Computer Science from Bangalore University in India(2000).Worked for a year in an Internet Professional Services Company. Was involved in projects dealing with intranets and quality assessment tools.Currently a graduate student at PSU. URL: ftp://ftp.isi.edu/in-notes/rfc1992.txt [Nimrod] Isidro Castineyra, Noel Chiappa, Martha Steenstrup, "The Nimrod Routing Architecture", RFC 1992, August 1996. http://users.exis.net/~jnc/tech/book2.html http://www.faqs.org/rfcs/rfc1992.html Nimrod Abstract Nimrod is a scalable internetwork routing architecture.Its architecture design aims to support a dyanmic internetwork of any size which may have distinct service needs and limitations.It also supports an incremental deployment throughout the entire network.The scability of Nimrod stems from the fact that it can represent and manipulate routing information at differnt levels of abstraction.It can be applied to both OSI and TCP/IP environments as well as for routing within single and multiple domains. The architecture provides for separate subsystems which work cohesively with other subsytems of the internetwork layer to provide a service model. In short it envisions an architecture that provides for an improving and continually growing internetwork. I propose an outline that closely mirrors the rfc 1992 content. Outline 1) Introduction 2) History and Overview. * Constraints * Routing Functions * Scalability 3) Architecture 4) Physical Realization 5) Forwarding 6) References 7) Questions -------------------------------------------------------------- 2. who - Jeanie M. Schwenk jschwenk@oregon.idt.com jschwenk@easystreet.com when - TBD, assigned by Jim what - EIGRP bio - I'm an automation software engineer for IDT and a part-time graduate student. I'm in this class because it fits well with becoming a CCNA (almost ready to take the test) and because we have a Cisco project coming up in the spring/summer. ABSTRACT: ========= EIGRP is a routing protocol that extends IGRP. An extension to IGRP was necessary for scalability and speed of convergence. It integrates the capabilities of link-state protocols into distance-vector protocols and utilizes a loop-free routing algorithm. EIGRP does not make periodic updates, it recomputes only as necessary when a metric for a route changes. Each route keeps a copy of its neighbor's routing tables NOT the entire router/link relationship for the entire network. Routers advertise destinations with corresponding distances. Each router receiving the update adjusts the distance and sends the information to its neighbors. EIGRP uses DUAL (the Diffusing-Update Algorithm) finite state machine to determine the best route to a destination. This algorithm/finite state machine is what produces loop-free routes. OUTLINE: ======== A. Overview of features: 1. Efficient a. Automatic distribution of minimum needed information (partial updates) b. Low network use once convergence happens c. Fast convergence 2. Scales well 3. Support for variable-length subnet mask 4. Support multiple network layer protocols B. Metrics Used (distance vector) 1. Bandwidth 2. Delay 3. Load utilization 4. Link reliability 5. Formula C. What is EIGRP (Main Differences between IGRP and EIGRP) 1. Convergence properties 2. Operating efficiency 3. additional components a. Neighbor discovery/recovery 1. Periodic hellos to keep in touch 2. Packet Formats b. Reliable Transport Protocol 1. Responsible for guaranteed delivery (not everything requires it) 2. Supports unicast, multicast and mixed c. DUAL finite state machine/basic description of algorithm 1. Terminology (neighbor tables, topology tables, route states, route tagging, feasible successor ...) 2. determines most efficient/least cost route to a destination 3. How it determines feasible successor 4. How it avoids loops 5. When to recompute d. Protocol dependent module 1. How it interoperates with IGRP (may also add RIP if time) 2. IP, AppleTalk, Novell Netware BIBLIOGRAPHY: ============= www.cisco.com/warp/public/103/5.html Introduction to IGRP www.cisco.com/warp/public/103/11.html Basic Terminology for EIGRP www.cisco.com/warp/public/103/1.html Cisco - Introduction to Enhanced IGRP www.cisco.com/warp/public/103/eigrpfaq.shtml EIGRP Frequently Asked Questions www.cisco.com/warp/public/103/eigrp-toc.html Cisco - White Paper: EIGRP www.cisco.com/warp/public/105/52.html Redistributing Between Classful and Classless Protocols: EIGRP or OSPF into RIP or IGRP www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/en_igrp.htm Chapter 40, Enhanced EIGRP, Internet-working Technologies Handbook J.J. Garcia-Luna-Aceves "Loop-Free Routing Using Diffusing Computations", IEEE/ACM Transactions on Networking, Vol. 1, No. 1, February 1993. http://www.cse.ucsc.edu/research/ccrg/publications.html (# 48 under Routing) J.J. Garcia-Luna-Aceves "Loop-Free Routing Using Diffusing Computations", IEEE/ACM Transactions on Networking, Vol. 1, No. 1, February 1993.) Routing in the Internet, Christian Huitema, pp 173-178 -------------------------------------------------------------- 3. Who: Banita Gupta@cs.pdx.edu When: TBD by instructor What: Wireless LAN's and IEEE 802.11 Bio: Graduate Student at PSU CS department Presentation Abstract: The major motivation and benefit from wireless LANs is increased = mobility. Untethered from conventional network connections, network users can move about almost without restriction and = access LANs from nearly anywhere.In addition to increased mobility, = wireless LANs offer increased flexibility. Mobile IP [3] was suggested as a means to attain wireless networking. It = focuses its attention at the Network Layer, In this protocol, the IP address of the mobile machine does not change = when it moves from a home network to a foreign network. In order to = maintain connections between the mobile node and the rest of the = network, a forwarding routine is implemented.The IEEE 802.11 standard = places specifications on the parameters of both the physical (PHY) and = medium access control (MAC) layers of the network. The PHY layer, which = actually handles the transmission of data between nodes, the MAC layer = is a set of protocols which is responsible for maintaining order in the = use of a shared medium. Outline: I. Introduction The topic covered will answer some basic questions of why and where = wireless local area networks can be used, and present a brief = description of the protocol that have been developed, for IEEE 802.11. II. IEEE 802.11 Architectures III. IEEE 802.11 Layers > Network topology > Logical addressing IV. Operational Issues V. Security Consideration VI. Summary Bibliography: IEEE 802.11: References R. LaMaire, et al, "Wireless LANs and Mobile Networking: Standards = and Future Directions," IEEE Communications Magazine, August 1996, pp. 86-94, = http://www.comsoc.org/pubs/ci/comsoc/=20 K. Pahlavan, et al, "Trends in Local Wireless Networks," IEEE = Communications Magazine, March 1995, pp. 88-95.=20 C. Links, et al, "Universal Wireless LANs," Byte, May 1994, pp. = 99-108.=20 Daniel L. Lough, T. Keith Blankenship, Kevin J. Krizman. "A Short = Tutorial on Wireless LANs and IEEE 802.11."=20 http://www.computer.org/students/looking/summer97/ieee802.htm. =20 L. Goldberg. ""Wireless LANs: Mobile Computing's Second Wave"." = Electronic Design 26 June 1995. =20 -------------------------------------------------------------- 4. Who - Meka Srikant (mekas@cs.pdx.edu) When- TBD, assigned by Jim What- Session description Protocol (SDP) Bio - I am a full-time graduate student at PSU in the CS dept. URL/Location - RFC 2327 http://www.ietf.org/rfc/rfc2327.txt Abstract ________ The Session Description Protocol (SDP) is used for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. On the Internet multicast backbone (Mbone), a session directory tool is used to advertise multimedia conferences and communicate the conference addresses and conference tool-specific information necessary for participation. SDP is primarily intended for use in a internetwork although it is sufficiently general that it can describe conferences in other network environments. A multimedia session, for these purposes is defined as a set of media streams that exist for a duration of time. Media streams can be many-to-many. The times during which the session is active need not be continuous. SDP basically serves two primary purposes - as a means to communicate the existence and timing of a session, and as a means to convey sufficient information to enable joining and participating in the session. Outline _______ 1. Introduction - What is SDP - Why is it necessary 2. Information Necessary for joining a Session - Media Information - Timing Information - Other Information 3. SDP specification 4. Security Considerations 5. SDP issues 6. Summary. -------------------------------------------------------------- 5. Who: Lily Yang, lily.l.yang@intel.com Topic: GPRS (General Packet Radio Service) in Wireless 2.5G/3G Summary: I will present: * the general motivation behind GPRS as a stepping stone toward Wireless 3G * the GPRS architecture/protocol stack and functionality of new nodes (Node B, RNC, SGSN, GGSN) * How a data packet is routed between your GPRS-enabled mobile terminal and the Internet References: A note: It's hard to find good reference with enough technical detail, unless you read the spec. But given the spec is almost 200 pages long (without yet getting into any particular protocol!), I don't expect you read the spec. So if you can, browse the first two URLs -- these provide some very high level overview of the "why and what" without much "how". 1) An Introduction to the General Packet Radio Service, by Simon Buckingham, Mobile Lifestreams Limited http://www.gsmworld.com/technology/yes2gprs.html. (Very highlevel intro.) 2) A white paper from Trillium Digital Systems (an Intel company now) on 3G wireless. (Good diagrams on the architecture and the nodes involved. More detail than above.) http://www.3gnewsroom.com/html/whitepapers/year_2000.shtml, click on 11th Dec 00 <<...OLE_Obj...>> Third Generation (3G) Wireless (Trillium Digital Systems) 3) The spec, if you really want it -- http://pda.etsi.org/pda/home.asp?wki_id=15342 ETSI TS 123 060 V4.3.0 (2002-01) - Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); General Packet Radio Service (GPRS) Service description; Stage 2 (3GPP TS 23.060 version 4.3.0 Release 4) Presenter: Lily Yang. I am currently a Sr. Network Software Engineer at Intel. Had Ph.D. in EE. My previous research and industry experience was heavily in digital signal processing, speech recognition, data compression, esp. speech/video compression. Even taught classes on Image Processing for OCATE (I think in the same classroom). Here I am again in the classroom, but this time as a humble student. Why? Changed my career direction about 2 years ago toward networking. Took classes from Jim before (TCP/IP, SNMP) and want to get this one under my belt before I claim myself a real network engineer. Just started getting involved in two new exciting projects at Intel, one involving GPRS (good guess), the other one involving standards work in a relatively new IETF routing area working group (ForCES -- forwarding and control element separation). I am having a great time learning new things every day!!! -------------------------------------------------------------- 6. who - Andrew Jauri jauri@cs.pdx.edu when - TBD, assigned by Jim what - Session Initiation Protocol (SIP) bio - I am a CS graduate student at PSU. Completed bachelor in civil engineering in 1999. URL/location - http://www.normos.org/rfc/rfc2543.txt Overview -------- SIP (Session Initiation Protocol) is a new signaling protocol on the application-layer protocol for creating, modifying and terminating multimedia sessions or internet telephony calls (VoIP) with one or more participants. It was not designed from scratch, but resulted from a merger of two IETF protocols that was proposed for the same reason (SIP and SCIP). SIP has a a strong relationship in terms of functionality with H.323, an established protocol that has been widely used. There are several core entities in SIP that play the main role, which are User Agents, Redirect Servers, Proxy Servers and Registrars. SIP can do either multicast or unicast session. SIP is based on the HTTP protocol, which is a request/response protocol. It has the notion of client and server. Some of the advantages that SIP provides are: - End to end protocol - Seperation between establishing and describing a session - Interoperability - Scalability SIP could be implemented for the third generation (3G) mobile systems, PacketCable, and telephony applications such as VoIP (Voice over IP). Outline draft: ------------------ I SIP - What is SIP - History - Functionality provided - SIP entities - SIP features II Protocol Operation - Client/Server - Format of SIP messages - Transport layer III SIP extensions - SIP toolkit - Instant Messages - Caller Preferences IV SIP Application - 3G mobile systems - PacketCable - VOIP -------------------------------------------------------------- 7. who - Yuli Kartika, kartika@cs.pdx.edu when - TBD, assigned by Jim what - Gigabit Ethernet bio - I come from Indonesia and I am a graduate student at PSU CS department. URL/location http://www.3com.com/other/pdfs/infra/corpinfo/en_US/50300302.pdf http://www.cisco.com/warp/public/cc/techno/media/lan/gig/tech/gigbt_tc.htm http://www.iol.unh.edu/training/ge.html Book: Data Communications Gigabit Ethernet Handbook by Saunders, Stephen. Abstract ======== The demands of high bandwidth network for enterprise business applications have triggered FastEthernet deployment from backbone into desktop, therefore raises the need to have faster backbone. Gigabit Ethernet extends the data rate performance from 10/100 Mbps to 1000 Mbps. Based on IEEE 802.3z standard, Gigabit Ethernet is the fastest technology currently available for LANs, MANs, and WANs. Gigabit Ethernet uses the same CSMA/CD protocol, same frame format and same frame size as its predecessors, giving an easy migration to existing network. Outline ======= - History of Ethernet - Evolution of Ethernet generation - Gigabit Ethernet technology based on IEEE 802.3z standard - Major differences with FastEthernet - Gigabit Ethernet MAC operation (half & full duxplex operations) - GMII (Gigabit Medium-Independent Interface) - Physical layer technology for Gigabit Ethernet - Auto-negotiation for 1000BASE-X - Gigabit Ethernet topology - Gigabit Ethernet Migration - Future generation Ethernet: 10 Gigabit Ethernet -------------------------------------------------------------- 8. Who: Kavita Kolluri, kavitasri@yahoo.com When: TBD by instructor What: AODV - Ad hoc On Demand Distance Vector Routing Protocol Bio: Graduate Student at PSU CS department Abstract: Ad hoc On Demand Distance Vector (AODV) Routing protocol is the protocol designed for ad hoc mobile networks. AODV enables to maintain a network among the mobile nodes that are wishing to maintain connection with each other. AODV provides a quick and easy way to find new destinations and does not force the mobile nodes to maintain connections with the nodes that are not in active communication. That means nodes can establish connections on demand, as and when required, and hence the name, "on demand routing protocol". AODV is loop-free and overcomes the "counting to infinity" problem of the distance vector protocols. AODV also provides quick convergence among all the participating mobile nodes in situations like link breaks caused due to a moving node. This convergence is brought about by notifying all the affected nodes and allowing them to make all the routes that use the broken link as "unreachable". AODV supports unicast, multicast and broadcast. The multicast operation enables nodes that are part of any multicast group to forward data and signal packets. For the multicast operation, AODV uses the Route Request (RREQ) and Route Reply (RREP) messages. All the nodes in the multicast operation form a tree like structure that enables nodes that are more than one hop away from the multicast group to participate in the multicast operation. Outline: 1. Introduction 2. Overview of the terminology used and formats for the different messages used This includes the following messages used in AODV - RREQ (Route Request) Message - RREP (Route Reply) Message - RERR (Route Error) Message - RREP-ACK (Route Reply - Acknowledgment) Message 3. AODV operation (in detail) - Generating and forwarding Route Requests - Generating and forwarding Route Replies - Maintaining Link connectivity - Processing Route Errors 4. AODV Multicast operation 5. Conclusion Bibliography: http://www.ietf.org/internet-drafts/draft-ietf-manet-aodv-09.txt - This IETF Internet Draft gives a detailed description of the AODV routing protocol that covers the overview and terminology used in AODV, the detailed operation of AODV, and the formats of different messages used for mobile communication. http://www.ietf.org/rfc/rfc2501.txt - This RFC describes the characteristics of ad hoc mobile networks and how to apply the differences between mobile networks and the normal hardwired packet networks in designing the protocols for the mobile networks. http://www.cs.ucsb.edu/~eroyer/aodv.html - Gives a very high level outline of the AODV routing protocol algorithm. ----------------------------------------------------- 9. Who: Michael Supancich supancich@yahoo.com supan@cs.pdx.edu When: TBD by instructor What: Geographic Routing Bio: I am a full-time graduate student at PSU. I have an undergraduate degree in biology and a law degree. My prior work experience includes several years as a research assistant in a biotechnology company and several years as a practicing lawyer specializing in intellectual property and corporate law. Identity and Source of Major Papers: Imielinski & Navas, IETF RFC 2009. 1996 www.ietf.org/rfc/rfc2009.txt?number=2009 Navas & Imielinski, On reducing the computational cost of Geographic Routing. 2000 www.cs.rutgers.edu/dataman/papers.html#Geographic%20Routing Karp, Challenges in Geographic Routing: Sparse Networks, Obstacles, and Traffic Provisioning. 2001 www.aciri.org/bkarp/geochal-dimacs2001.pdf Navas & Tomasz Imielinski, Geographic Routing User's Guide. 1998 www.cs.rutgers.edu/dataman/papers.html#Geographic%20Routing Navas & Imielinski, Multi-hop Dynamic Geographic Routing. 1998 www.cs.rutgers.edu/dataman/papers.html#Geographic%20Routing Imielinski & Navas, Geographic Addressing and Routing. 1997 www.cs.rutgers.edu/~navas/dataman/papers/ Imielinski & Navas, Geographic Routing, Addressing, Routing and Resource Discovery with the Global Positioning System. 1997 www.cs.rutgers.edu/~navas/dataman/papers/ Abstract: Geographic routing has the potential to open a broad range of public and commercial applications by enabling the provision of location dependent services. This is especially true given recent advances in GPS technology and the increase in mobile devices. This presentation will explore proposed geographic routing schemes to efficiently transport data packets through the current network structure using geographic information. Specific issues of interest include addressing, routing tables, and DNS issues. Problems with the proposed schemes will also be discussed. Outline: 1) Introduction 2) Geographic Routing Applications - why do we want it? 3) Introduction to GPS technology a) how it works b) how it can be used in addressing 4) Geographic Routing Schemes a) basic components b) routing scheme overviews 1) how they work and their use of multicast/broadcast c) specific aspects of implementation 1) addressing 2) routing table 3) DNS 4) GeoArp 5) Geographic Email 5) Difficulties and proposed solutions/optimizations a) high computational costs b) use indoors c) reliability and reliance on limited number of satellites d) security issues 6) Conclusion - where are we? -------------------------------------------------------- 10. Who: Ping He E-mail: ping@cs.pdx.edu When: TBD What: Mobile Ipv6 Bio: CS student at PSU Abstract: Major motivation for IPv6 is the rapid growth of the Internet and the limitations in the design of IPv4 such as the available ip address. IPv6 fulfils future demands on not only address space, but also its supporting for mobile devices as well as its built-in security. Special requirements are imposed for Ipv6 host, routers and mobile nodes in order to provide desirable mobile functionality. In MIPv6, a mobile node is always addressable by its home address. When it is currently attached to its home link, packets addressed to its home address are routed to it using conventional routing mechanism. Otherwise, this mobile node is also addressable by one or more care-of addresses (an ip address associated with a mobile node while visiting a particular foreign link). Association between the mobile node's home address and care-of address is known as "binding", which is unique in mobile Ipv6. Authentication is used when "binding update" and "binding acknowledgement" to guard against malicious binding options. Other nice features in MIPv6 include Neighbor Discovery, Correspondent Node Operation, Home Agent Operation and Mobile Node Operation. Security issues related to MIPv6 will also BRIEFLY be addressed and solution/s proposed. Outline: I. Introduction - Why IPv6 (vs. IPv4) and advantages it provides - Why mobile IP, comparison between mobile IPv4 and mobile IPv6 II. Terminology used in IPv6 - General term - Mobile IPv6 term III. Overview of Mobile IPv6 - Requirement - Basic Operation - Binding in MIPv6 IV. Other Features in MIPv6 - Neighbor Discovery - Correspondent Node Operation - Home Agent Operation - Mobile Node Operation. V. Security Issue - Security threats and possible solutions VI. Summary URL: http://www.ietf.org/rfc/rfc3024.txt http://www.ietf.org/internet-drafts/draft-ietf-mobileip-ipv6-15.txt http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-scrty-reqts-02.txt ---------------------------------------------------------- 11. Who: Jaswant Tawdekar jtawdekar@hotmail.com tawdekaj@cs.pdx.edu When: TBD, assigned by Jim What: Real Time Streaming Protocol (RTSP)-RFC 2326 Bio: Computer Science Student at PSU.Previously done research for Intel at Oregon State University.Worked for 2 years in Management Information Systems. URL: http://www.ietf.org/rfc/rfc2326.txt?number=2326 http://www.cs.columbia.edu/~hgs/rtsp/ http://www.cs.columbia.edu/~hgs/rtp/drafts.html Abstract:A complete introduction to Real time streaming protocol.This is a very big RFC but i will try to cover key points which helps better in understanding of Real Time Streaming Protocol. -------------------------------------------------------------- 12. who - Richa Sehgal,richasehgal@hotmail.com what - A Review of Current Routing Protocols for Ad-hoc Mobile Wireless Networks by Elizabet M.Royer and C-K Toh bio - I am from India and currently doing my masters in PSU URL/location - http://users.ece.gatech.edu/~cktoh/royer.html Abstract Mobile Networking has become a very hot area of research these days. There are primarily two techniques of mobile routing . One is table driven where the table will be consulted before a packet is forwarded to the next router. The other is the Source initiated on demand routing where routing takes place by Path Discovery which comprises mainly of a request and reply messages being sent to and fro. This paper actually discusses examples, characteristics and operations of some of the protocols using Table Driven Routing and some using Source Initiated On Demand Routing.It further compares the table driven protocols, source initiated on demand protocols . Outline 1. Introduction – What is Adhoc Mobile Networking and two types of Routing Protocols – Table Driven & Source Initiated Demand Routing 2. Examples, Operation and Characteristics of Table driven Routing Protocols a. Destination Sequenced Distance Vector Routing (DSDV) b. Cluster head Gateway Switch Routing (CGSR) c. Wireless Routing Protocol (WRP) 3. Examples, Operation and Characteristics of Source Initiated On Demand Routing a. Ad-hoc On Demand Distance Vector Routing (AODV) b. Dynamic Source Routing (DSR) c. Temporally –Ordered Routing Algorithm (TORA) d. Associativity Based Routing (ABR) e. Signal Stability Routing 4. Comparisons between Table Driven Routing Protocols 5. Comparisons between Source Initiated On Demand Routing Protocols 6. Comparisons between Table Driven Routing Protocols and Source Initiated On Demand Routing Protocols 7. Applications of Ad-Hoc Mobile Routing and Conclusion -------------------------------------------------------------- 13. Who - Sabina Choudhury choudhus@cs.pdx.edu When - TBD, assigned by Jim What - An Integrated IPSEC and Mobile-IP for FreeBSD Paper by Jim Binkley Bio - Born and brought up in Bangladesh. Completed my Bachelor's degree in Architecture. Currently a graduate student at PSU. URL - http://www.cs.pdx.edu/~jrb/jrb.papers/mipipsec/mipipsec.ps PRESENTATION OUTLINE: --------------------- 1. Introduction: Discuss the WEP security problems. Define terms related to Mobile-IP and Mobile routing security policies. 2. PSU mobile-IP routing architecture: Introduce the Mobile-IP architecture used in the PSU Mobile routing daemons. Illustrate the way routing daemons function vis--vis the BSD routing table. 3. Discuss two IPv4 Mobil-IP/IPSEC routing daemon architecture: A) Closely-Coupled 2.2.8 Free BSD Mobil-IP/IPSEC: Introduce and discuss the architectural aspects of PSUs older 2.2.8 BSD combined Mobile-IP/IPSEC architecture. B) Loosely-Coupled 4.3 FreeBSD Mobile-IP/IPSEC: Introduce and discuss the architectural aspects of PSUs current BSD KAME/IPSEC system 5. Architectural Analysis: Discuss architectural analysis in term of system organization. 6. Conclusion. -------------------------------------------------------------- 14. Who: Baoli li baolics.pdx.edu When: TBD, assigned by Jim What: The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks IETF MANET Working Group David B. Johnson, Rice University INTERNET-DRAFT David A. Maltz, AON Networks 21 November 2001 Yih-Chun Hu, Rice University Jorjeta G. Jetcheva, Carnegie Mellon University Bio: PSU Computer Science major graduate student. Interested in network programming and mobile wireless networks. Network background: 1. TCP/IP, 2. CGI PROGRAMMING. URL: 1. http://search.ietf.org/internet-drafts/draft-ietf-manet-dsr-06.txt 2. Johnson, D.B., and Maltz, D.A., "Dynamic Source Routing in Ad-Hoc Wireless Networks," in Mobile Computing, edited by T. Imielinski and H. Korth, chapter 5, pp. 153-181, Kluwer, 1996 The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks Abstract: Dynamic Source Routing Protocol is an efficient routing protocol that was specially designed for the multi-hop mobile wireless Ad Hoc Networks. It allows mobile users to discover a source route across multiple networks hops and communicate to any other destinations in the Ad Hoc Network without the aid of existing fixed network infrastructure or administration. When a packet was transferred from one mobile into the destination, it needs one or more other mobile hosts to forward the packet since each mobile host has a short range of transmission distance. Difference to traditional network routing protocols which use linked state or distance vector algorithms, DSR dynamically transmits the packet to next host depends on the cache information and a new protocol called Route Discovery Protocol. DSR protocol is composed of two main mechanisms that work together to allow the discovery and maintenance of source routes in the Ad Hoc Network: 1. Route discovery mechanism: the process of sending a packet is composing of two parts. First, construct the source route in the packet's header which giving the addresses of all the host the packet need to send this packet to the destination. This process is called router discovery. Second, send the packet depending on the source route information. 2. Maintenance mechanism: detect the source route, if something wrong happened with the existing source routes, it will invoke Route discovery mechanism to find new route. It could be performed by hop-by-hop acknowledgement, passive acknowledgement, or end-to-end acknowledgement. For reducing the overhead of packets and improving the efficiency of route used on data packets, optimizations were applied to the basic operations of Route Discovery and Maintenance. Optimizations of fully used route cache, piggyback on Route Discovery, reflecting shorter route were the basic techniques to improve the performance of DSR in the networks. Moreover, error handling is also needed to be optimized in this new routing protocol. Presentation Outline: I. Introduction - Ad Hoc Network, conventional Routing protocols, and Dynamic Source Routing - Advantage, disadvantage of Conventional Routing Protocols, why used DSR II. Basic Operations in Dynamic Source Routing Protocol - Discovery Mechanism - Maintenance Mechanism III. Optimization of DSR protocol - Full use of Route Cache - Piggyback on Route Discovery - Reflecting shorter route IV. Summary -------------------------------------------------------------- 15. Who : Rashmi Agrawal rashmi@polyserve.com When : TBD, Assigned by Jim What : Commentry on inter-domain routing on internet BIO : I am presently working, for company Polyserve Tech, in SAN technologies. I started working in 1998 after finishing my Comp Sci graduation from India. Always interested in gaining more and more knowledge and that brings me to PSU part time courses.Why Networking?? because of SAN technologies, I am \ currently working on. Abstract : The purpose of this presentation is to examine the trends visible within the internet's BGP table and to identify the operational practices and protocol factors that contribute to this trend. Finaly we will discuss potential impacts of these practices and protocol properties on the scaling properties of inter domain routing space. Outline : Introduction Network scaling and interdomain routing Measurements of the total size of BGP table Related measurements derived from BGP tables Current state of inter AS routing in internet Future requirements for the Exterior Routing System Architectural approaches to a scalable Exterior Routing Protocol Security Consideration URL/Locations http://www.ietf.org/rfc/rfc3221.txt?number=3221 - Commentry on inter-domain routing in internet http://www.rfc-editor.org/internet-drafts/draft-ambrose-routing-protocol-term-00.txt- Describes the common terminologies used in inter-domain routing protocols. http://www.ietf.org/rfc/rfc1771.txt?number=1771 - Describes BGP. It would be a good idea to have the knowledge of BGP before discussing the trends in inter-domain routing. http://www.ietf.org/rfc/rfc1519.txt?number=1519 : Classless InterDomain Routing (CIDR) -------------------------------------------------------------- 16. Who: Dan Gaur, gaur@cse.ogi.edu When: TBD Bio: Software engineer at Intel; part-time MS student at OGI. What: 10 Gigabit Ethernet. Basic overview of the technology; why we need it and where you're likely to see it. Differences and similarities to existing Ethernet standards. How it fits with older Ethernet infrastructure. References: The intro whitepaper posted by the 10Gigabit Ethernet Alliance. It's an odd combination of marketing propaganda and technical details. The 10GEA has some links to other Ethernet resources on this site as well. http://www.10gea.org/10GEA_Whitepaper_0901.pdf "Networking for the Next Generation" article in Network Computing Magazine, by Joel Conover. Just recently found this; it's a good combination of general overview and technical details. Also describes where 10GbE fits relative to 10/100Mb/s and 1GbE. http://www.nwc.com/shared/printArticle?article=nc/1213/1213ws2full.html&pub= nwc The IEEE 802.3ae group is responsible for the actual 10GbE standard. The spec itself is only available to IEEE members (and it's not finished yet anyway), but there are some related links and an email reflector here: http://grouper.ieee.org/groups/802/3/ae/ 0. Intro: why and where do we need this? - Increasing bandwidth needs - Ethernet "end-to-end" - MAN/WAN applications 1. Is it still Ethernet? - Same frame formats, lengths, etc., ... - But full duplex-only; no more "collisions" 2. Comparison to 10/100/1000 Mb/s Ethernet - No autonegotiation (speed, duplex and flow control) - Fiber media - WAN sub-layer 3. Difficulties in implementation - No reference technologies (unlike 10/100/1000 Mb/s) - Disparity between system and network capacity - Cost 4. Beyond 10G? -------------------------------------------------------------- 17. who - Sashikiran Rachakonda sashi@cs.pdx.edu when - TBD, assigned by Jim What - Multicasting in Ad-Hoc Networks: Comparing MAODV and ODMRP bio - I am a graduate student in computer science at PSU url/Location - www.scs.carleton.ca/~barbeau/wadhc/Papers/kunz.pdf Presentation Abstract : Well-established multicast routing protocols that provide efficient service exits in wired-neworks. As nodes become increasingly mobile, one of the challenges for these protocols is to evolve to provide similar service in the new environment. The presentation brings into light two multicast routing protocols, MAODV and ODMRP, that have been proposed for ad-hoc mobile networks. While MAODV builds and maintains a multicast tree based on hardstate, ODMRP maintains a mesh based on softstate. Further,the performance of these protocols and the comparisions are discussed. Presentation Outline: 1. Motivation 2. Multicast Protocols for Mobile Ad-hoc Networks a) Multicast Ad-hoc On-Demand Distance Vector Protocol (MAODV) b) On-Demand Multicast Routing Protocol( ODMRP) 3. Qualitative Comparision Of the Protocols 4. Simulation-based Comparision a) Experimental setup and Performance Metrics b) Number of Senders c) Node Mobility d) Multicast group size 5. Conclusion -------------------------------------------------------------- 18. Who: Hongyon Suauthai (suauthah@cs.pdx.edu) When: TBD What: Cisco IOS architecture Bio: A full time graduate student at PSU. URL: http://www.cisco.com/warp/public/63/arch_2500_5750.shtml http://www.cisco.com/warp/public/63/arch_1600_5406.shtml http://www.cisco.com/warp/public/63/arch_7200_5810.shtml http://www.cisco.com/warp/public/63/arch_4000.shtml Cisco IOS Architecture Book (TBD) Cisco IOS Architecture OUTLINE: IOS Architecture Overview & Buffer System Management Packet Switches Receiving Rings Transmitt Rings Process Switching Fast Switching Optimum Switching Cisco Express Fowarding Shared Memory Routers(Cisco1600,2500,4000) Packet buffer packet switching Particle-based System(Cisco 7200) Buffer management packet switching Cisco Gigabit Switch Router *** packet switching Summary -------------------------------------------------------------- 19. Who: Benyi Wang (bywang@cs.pdx.edu) When: TBD, assigned by Jim What: Security in Mobile IPv6 Bio: Graduate student of CS dept at PSU. URL: 1. http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-scrty-reqts-02.txt 2. http://www.cs.pdx.edu/research/SMN/papers/mobifirewall.txt 3. http://www.ietf.org/proceedings/01mar/slides/mobileip-9/index.html (slides of Security and Mobile IPv6 by Jeffrey Schiller) 4. http://www.ietf.org/proceedings/01mar/index.html (A1: Security in MIPv6 discussion) Abstract: With more and more attacks occured in Internet, the security of network has become the focus of Internet community. The objective of this presentation is to describe possible threats that should be considered when designing the Mobile IPv6. Through analysis of the characteristics of Mobile IPv6 and classification of threats, this presentation will introduce the secrity requirements for Mobile IPv6. Some examples of threats and attacks are also discussed. Outline: 1. Brief Review MIPv6 2. Assumption and Terminology 3. Classification of Threats and Attackers 4. Examples of Threats or Attacks to MIPv6 5. Requirements for MIPv6 -------------------------------------------------------------- 20. who - Yong Ding Email: yongding@cs.pdx.edu Qiuyi Wu Email: wuq@cs.pdx.edu when - TBD, assigned by Jim what - Routing confederation and BGP bio - Yong Ding: working at Pediatric Cardiology Lab in OHSU to maintain and trouble-shoot computer system and network problems. I wish to gain more knowledge and experience in network field, especially the technologies related to Cisco. Qiuyi Wu : I am a part-time student and working at ZESS technology INC. in part-time. Interested in network programming. Hope to acquire more knowledge about structure of network and network design. It will be very helpful to my part-time job. Abstract In this presentation, we will discuss routing confederations and BGP (Border Gateway Protocol). BGP is used to connect local Autonomous System(AS) to the Internet. However, it requires that all BGP speakers within a single AS must be fully meshed. This causes a serious scaling problem. The confederation of autonomous systems is proposed as a solution to aid in policy administration and reduce the management complexity of maintaining a large AS. Our talk will focus on the limitation of BGP and how the routing confederations is used to resolve the scaling problem. First, we will give an introduction about BGP and scaling problem. Next, we will describe what causes BGP to have scaling problem and several solutions to resolve it. We will show routing confederation is one of best. Third, we will introduce mechanism of routing confederation and describe configuration of routing confederation used in Cisco router. Finally, we conclude our talk and give a brief description about the future application of routing confederation and BGP. Outline: I. Introduction II. BGP's problem and extension --- routing confederation III. How routing confederations and BGP works IV. How routing confederations and BGP is configured in cisco router V. Conclusion URL/location - 1. RFC 3065 2. RFC 1965 3. RFC 1654 4. http://www.mit.edu/afs/sipb/user/jhawk/idr/minutes-95-04-05 5. http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-ext-communities-02.txt 6. http://www.ietf.org/proceedings/99jul/I-D/draft-ietf-idr-route-reflect-v2-01.txt 7. Syngress Media, Inc Staff, "Cisco Router Configuration Answers!: Certified Tech support", Osborne/McGraw-Hill, 1999, ISBN 0-07-211943-8. 8. Terry Slattery, and Bill Burton, "Advanced IP Routing in Cisco Networks," 2nd Edition, McGraw Hill, 2000, ISBN 0-07-212591-8. -------------------------------------------------------------- 21. This is my presentation summary and abstract. who---Zhiyong Sun when--- TBD what--Mobile Mesh Architectural Consideration and Routing Protocol bio-- I am a graduate student in Computer Science Department in PSU Abstract In the presentation, I will focus on characteristics of Mobile network, the important consideration for design of routing protocol in Mobile Mesh networks,and mobile mesh routing protocols. The mobile networks have two salient characteristics: Dynamic and Congested Links. Because of these characteristics, the design of mobile routing protocols should follow a slightly different philosophy than is used in fixed networks. The protocols used in fixed networks are discussed if they can be used in the Mobile Networks, and how those protocols can be changed to meet the Mobile Mesh requirements: rapid protocol convergence and congestion avoidence. In the last part of presentation, the mechanism of Mobile Mesh Routing Protocol, Mobile Mesh Border Discovery Protocol, and Mobile Mesh Link Discovery Protocols are discussed. Outline: 1. Charateristics of Mobile Network 2. Important Consideration for Design of Mobile Mesh Protocol 3. MMBDP, MMLDP, and MMRP Protocols 4. Conclusion Reference and URL 1. Architectural Consideration For Mobile Mesh Networking, http:// www.mitre.org/tech_transfer/mobilemesh 2. Mobile Mesh Link Discovery Protocol http://www.mitre.org/tech_transfer/mobilemesh/#Documentation 3. Mobile Mesh Routing Protocol http://www.mitre.org/tech_transfer/mobilemesh/#Documentation 4. Mobile Mesh Border Discovery Protocol http://www.mitre.org/tech_transfer/mobilemesh/#Documentation