Student Lectures - Winter/2001 PSU/CS 510 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. -------------------------------------------------------------- Who : Maruti Gupta mgupta@cs.pdx.edu when: what: Routing Protocol MIBS (BGP/OSPF) bio : I am from India, a CS graduate at PSU, nearly always mistaken for a high-school student. I am really tiny. URL/Location: RFCs 1657/1850 http://www.ietf.cnri.reston.va.us/rfc/rfc1850.txt?number=1850 http://www.ietf.cnri.reston.va.us/rfc/rfc1657.txt?number=1657 Abstract : As the number of networks within an organization grows in diversity as well as number, it becomes increasingly important to manage all the systems within a coherent framework. Network management of a TCP/IP internet consists of network management stations(managers) communicating with network elements. The network elements can be anything that runs the TCP/IP protocol suite: hosts, routers, X terminals etc. TCP/IP network management consists of 3 parts one of which is a MIB. A Management Information Base (MIB) is the database of information maintained by the network element or agent that the manager can query or set. The protocol used for talking between the manager and the agent is called SNMP. The main topics which will be discussed are those related to what kind of information do the OSPF/BGP MIBs contain and how is it accessed, used for network management etc. -------------------------------------------------------------- #2 Who: Shiv Saxena (saxenas@cs.pdx.edu) When: TBD What: Gigabit Ethernet Bio: I am a graduate CS student at PSU (part-time). I have about 7 years of experience developing Windows applications in C/C++/Java. Presentation Abstract: In a relatively short time span, network connections have evolved from shared or switched Ethernet to shared or switched Fast Ethernet to accommodate rising bandwidth demand. Within the enterprise networks, business applications are now advancing to embrace high-resolution graphics, video, and other rich media types that exceed the capacity of even Fast Ethernet performance. Gigabit Ethernet delivers the scaleable performance of Ethernet technology. Outline: - Briefly provide a historical context for Gigabit Ethernet - n-signal-phy nomenclature - Gigabit Ethernet MAC operation - The need for Flow Control - Auto-Negotiation - Gigabit Media-Independent Interfacing - Gigabit Interface Converter (GBIC) - Fiber to the Home - Case studies: (i) Content-Neutral Video-Speed Ubiquitous Residential Gigabit Ethernet (CONVURGE) (ii) Canadian Network for the Advancement of Research (CANARIE) Ethernet, Fast Ethernet and Gigabit Ethernet have clearly been adopted as the technologies of choice for building high-performance local area networks (LANs). 10 Gigabit Ethernet is simply the next logical development in this Ethernet bandwidth hierarchy. - The emerging 10 Gigabit Ethernet Standard 802.3ae - 10 Gigabit Ethernet MAN/WAN Applications Bibliography: Gigabit Ethernet by Rich Seifert CONVURGE by David R. Cheriton & Andreas Bechtolsheim CANARIE by Bill St. Arnaud http://www.cisco.com/warp/public/cc/techno/media/lan/gig/tech/gigbt_tc.htm http://www.cisco.com/warp/public/cc/techno/lnty/etty/ggetty/tech/10gig_wp.htm http://www.worldwidepackets.com/solutions/white_papers.jsp -------------------------------------------------------------- #3 who - Ryan Devlin (ryan.p.devlin@intel.com, ryanpdevlin@home.com) when - TBD, assigned by Jim what - VoDSL bio - I have about 7 years of networking experience from positions at Monsanto and Intel in Information Technology and Quality Assessment. I have a BSEE from the University of Illinois at Urbana-Champaign. I am currently working toward my MSEE at Portland State University and continue to perform roles related to Quality Assessment at Intel in the Broadband Access Operation, which focuses on Digital Subscriber Line (DSL) products. Presentation Abstract: The broadband access market continues to expand. Both telephone companies and cable operators are searching for new sources of revenue and as a result are often fighting for the same customer base. In addition, Large telephone companies, commonly called ILECs or Incumbent Local Exchange Carriers, are also facing competition from CLECs (Competitive) or DLECs (Data) due to governmental deregulation of telephone wiring infrastructure. This increased competition and emerging market opportunity has forced many companies to consider new ways to deliver services to consumers. The telephone company industry (ILECs, CLECs, and DLECs) are seeking ways to leverage their existing Asynchronous Transfer Mode (ATM) infrastructure and their emerging Digital Subscriber Line (DSL) infrastructure to provide both voice and data services simultaneously. This lecture will focus on the infrastructure and protocols necessary to make Voice over Digital Subscriber Lines (VoDSL) a market reality. Outline: I.ATM Intro Where did ATM come from and why? The ATM Network Architecture ATM Adaptation Layer AAL5 for Data AAL2 for Voice II.ADSL Intro Where did ADSL come from and why? The ADSL Network Architecture Physical Layer Technology and POTS Coexistence III.VoDSL The VoDSL Reference Model VoDSL Functional Blocks VoDSL Interfaces Defined VoDSL Requirements Broadband Loop Emulation Service (BLES) The VoDSL Network Architecture PSTN Signaling Model CO-IWF/CP-IWF Operation GR-303/TR-008 Operation IV.Conclusion Technical References for VoDSL The Emerging Companies in VoDSL URLs/Bibliography: (links also at http:\\www.europa.com\~rdevlin\) Industry Technical Documents: ADSL Forum Technical Reports: http://www.dslforum.org/tr_table.html Requirements for Voice over DSL TR-036 ATM Forum Technical Specifications: http://www.atmforum.com/atmforum/specs/approved.html Loop Emulation Service using AAL2 af-vmoa-0145.000 Background Preparation: ATM Tutorial: http://www.atmforum.com/atmforum/library/notes1.html ADSL Tutorial: http://www.dslforum.org/adsl_tutorial.html Voice over ATM White Paper: http://www.atmforum.com/atmforum/library/practical_voiceover.html ATM Switched Virtual Circuits using ATM Adaptation Layer 2 (AAL-2) http://www.acceleratednetworks.com/whitepapers/svc/svc.html Intel White Paper on VoDSL: http://www.intel.com/design/network/papers/vodsl.htm -------------------------------------------------------------- -------------------------------------------------------------- #4/#5 who - LiFeng Bian Yuan-mei wang what - EIGRP bio - LiFeng Bian, graduate student in psu. bio - yuan-mei wang,graduate student in psu. Presentation abstract EIGRP is an enhanced distance vector protocol. Its work relies on neighbor discovery/recovery, reliable transport protocol, DUAL finite state machine and protocol dependent modules. It provides extremely quick converge times with minimal network traffic and scale well. . Introduction . EIGRP tables . neighbor table . topology table . EIGRP metrics . Rerouting process . feasible successor . Redistribution . Redistribution between two EIGRP . Redistribution between EIGRP and IGRP . Tags in Redistribution . Conclusion Presentation Bibliography . http://www.cisco.com/warp/public/103/1.html . http://www.cisco.com/warp/public/103/eigrp-toc.html . Advanced IP Routing in Cisco Networks Terry Slattery, and Bill Burton, McGraw Hill, 2000, ISBN 0-07-212591-8. 2nd edition. . R. Albrightson, J.J. Garcia-Luna-Aceves and J. Boyle, "EIGRP-A Fast Routing Protocol Based on Distance Vectors", Proc. Networld/Interop 94, Las Vegas, Nevada, May 1994. . J.J. Garcia-Luna-Aceves, Loop-Free Routing Using Diffusing Computations, IEEE/ACM TRANSACTION ON NETWORKING, vol 1. no.1 February 1993. LiFeng (Brian) Bian webpage: http://i.am/bian2 voice mail: (503) 725-7321 -------------------------------------------------------------- #6 who - Nikhil Rao, nikhil.rao@intel.com when - TBD, assigned by Jim what - Mobility in IPv6 bio - Software Engineer in the Broadband Access Organisation in Intel. URL/location - http://search.ietf.org/internet-drafts/draft-ietf-mobileip-ipv6-13.txt http://www.iprg.nokia.com/~charliep/ http://www.monarch.cs.cmu.edu/ietf.html -------------------------------------------------------------- # 7 who - Kip Frey when - TBD what - geographical routing Bio: Ancient CS Grad student. 57 credits, can I quit now? I have a consulting business, developing software for business and engineering since 1980. Abstract: The continuing decrease in the cost of GPS products is creating an opportunity to incorporate GPS capabilities into a variety of electronic devices, particularly cellular phones, PDAs and mobile computers. Several reasons for a using some method of geographical routing of IP packets are identified. Several methods of accomplishing this routing are presented in the initial paper, and said methods are refined in later papers by the same authors. Possible extensions to DNS and RIP to enable and enhance geographic routing are discussed. A total solution of geographical routers, storage nodes and routing protocol are described. Outline. I. Introduction II. Uses of geographical routing A. Emergency broadcasting B. Advertising C. Geographically limited web links III. GPS interface A. What is GPS B. Coordinate representation C. Accuracy of representation D. Destination specification IV. Routing by geographical coordinates A. Determining destination IP B. Routing methodology C. Destination storage node D. Routing table considerations E. Optimizations V. Current thinking on geographical routing A. Refinements to destination polygon B. Routing improvements References: IETF RFC 2009. Imielinski and Navas. 1996. Geographic Addressing,Routing, and Resource Discovery with the Global Positioning System. Imielinski and Navas. 1996 Multi-hop Dynamic Geographic Routing. Navas and Imielinski. 1998 All papers available at: http://www.cs.rutgers.edu/~navas/dataman/papers/ -------------------------------------------------------------- #8 Who: Run Zhang zhangr@cs.pdx.edu When: TBD by instructor What: Virtual Router Redundancy Protocol Bio: Run Zhang -- Graduate Student at PSU CS department Presentation Abstract: The presentation is based on an Internet-Draft, which is in full conformance with all provisions of Section 10 of [RFC 2026]. Virtual Router Redundancy Protocol (VRRP) is an election protocol that specifies dynamic assignment of responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IP addresses associated with a virtual router is called the "Master", and forwards packets sent to these IP addresses.If the Master becomes unavailable, the election process can provide dynamic fail over in the forwarding responsibility. This allows any of the virtual router IP addresses on the LAN to be used as the default first hop router IP by end-hosts. The advantage gained from using VRRP is a higher availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. Outline: I. Preliminaries: > Definitions > VRRP Mandatory Design Features II. VRRP Overview and Sample Configurations III. Theory of VRRP > VRRP packet format > IP Field Description > Protocol State Machine > Transmitting Packets IV. Operational Issues and Examples (FDDI, Token Ring, etc.) V. Security Consideration VI. Summary URL/Location: The main internet-draft can be viewed at: http://search.ietf.org/internet-drafts/draft-ietf-vrrp-spec-v2-05.txt Others: International Standard ISO/IEC 10038: 1993, ANSI/IEEE Std 802.1D, 1993 edition. Kent, S., R. Atkinson, "IP Authentication Header", RFC2402, November 1998. Braden, R., D. Borman, C. Partridge, "Computing the Internet Checksum", RFC1071, September 1988. -------------------------------------------------------------- #9 Who: Harikeshavan Gomatam (gomatam@cs.pdx.edu) What: Inet traffic engineering Bio: Full time graduate student in the CS dept at PSU. URL / Location: "A framework for internet traffic engineering" by Daniel O. Awduche, Angela Chiu, Anwar Elwalid Indra Widjaja and Xipeng Xao www.ietf.org/internet-drafts/draft-ietf-tewg-framework-02.txt Abstract: Traffic Engineering encompasses the application of technology and scientific principles to the measurement, characterization, modeling, and control (optimization) of internet traffic. The framework discusses issues surrounding traffic engineering in IP networks to provide a common basis for the development of traffic engineering capabilities for the internet. The principles, architectures, and methodologies for performance evaluation and performance optimization of operational IP networks will be discussed, the optimization goal being to enhance the performance of IP traffic while utilizing network resources economically and reliably. Additional information: "Measurement and analysis of IP network usage" www.research.att.com/~albert/papers/ieeecomm00/ieeecomm00.pdf "Deriving traffic demands for operatinal IP networks: Methodology and experience" www.research.att.com/~albert/papers/sigcomm00/sigcomm00.pdf ------------------------------ #10 Who: Satyajit Grover, satyajit@cs.pdx.edu When: TBD would like to not be the week of Mar 5. What: Multiprotocol Label Switching (MPLS) Architecture Bio: PSU CS graduate student. More info at http://www.cs.pdx.edu/~satyajit Info/URL: The MPLS architecture RFC is rfc3031.txt. Here is a link to it: http://www.ietf.org/rfc/rfc3031.txt Links to other MPLS related stuff can be found from the IETF MPLS charter page at: http://www.ietf.org/html.charters/mpls-charter.html ----------------------------------------------------- #11 who - Ansuya Negi (negi@cs.pdx.edu) when - TBA what - Simple Multicast: A Design for Simple, Low-Overhead Multicast bio - Graduate student at PSU Abstract - Multicast schemes focus on formulation of groups. Neither flooding or spanning tree schemes focus on groups only, they reach all the nodes. Introduction of core routers simplify routing to group members, but in a dynamically changing group membership, core routers may or may not be the same. Simple multicast allows a core to be uniquely associated with a multicast address. So a group shares a single tree, instead of creating a new tree. This scheme is scalable and simple to implement. > URL/location - http://www.ten-34.net/mbone/refs/draft-perlman-simple-multicast-03.txt http://www.winsock2.com/multicast/views/view_1998_11.htm ----------------------------------------------------- #12 Name and Email: Ramachandra N. Pai (like to be called as Ram) psu_ram@yahoo.com or pair@us.ibm.com Title of the talk: Stream controlled transmission Protocol (RFC2960) Bio: Graduated in Computer Science from University of Mysore (India). Worked in parallel computing as well as operating system software. For the last 5 years I have been working on Storage Management software at Sequent computers,(currently IBM). URL/location: http://www.ietf.org/rfc/rfc2960.txt Abstract: SCTP is a reliable transport protocol operating on top of a connectionless packet network such as IP. Its adds to the services provided by TCP by including features like (1) sequenced delivery of user messages within multiple streams, with an option for order-of-arrival delivery of individual user messages (2) optional bundling of multiple user messages into a single SCTP packet, (3) network level fault tolerance through supporting of multihoming at either or both ends of an association. The core feature of SCTP is multistreaming and multihoming. OVERVIEW: 1. Introduction 2. SCTP packet format 3. SCTP Association state diagram 4. Brief description of a. Association Initialization b. User Data Transfer c. Congestion Control d. Fault Management e. Termination of Association f. Security Considerations Bibliography: http://www.ietf.org/rfc/rfc2960.txt the actual rfc. It has references to lots of related rfc. http://www.sctp.chicago.il.us/sctpoverview.html for an overview of SCTP http://tdrwww.exp-math.uni-essen.de/pages/forschung/sod-large.png for state diagram of SCTP http://www.exp-math.uni-essen.de/~ajung/sctp-atm2000-97/ some power-point presentation of SCTP performance. ---------------------------------------------- #13 who - Sumit Chawla, merawalasumit@hotmail.com when - not feb. 22 what - Group Key Management Protocol (GKMP): H. Harney & C.Muckenhirn (multicast key exchange protocol) bio - I am an Advisory Software Engineer with IBM, working on advanced development projects for ISV support. I am also interested in Networking and Network Security, and am seeking admission in PSU as a full-time student. URL/location - Primarily RFCs 2093 and 2094. These can be viewed at http://www.faqs.org/rfcs/ or at any other place that keeps RFCs. ---------------------------------------------------- #14 Name : Shashidhar Lakkavalli What : BGMP Bio : Full time graduate student at PSU. I have 3 years of experience as a software engineer in wireless communications. Abstract Current multicasting protocols like DVMRP, PIM Dense Mode use flood and prune messages for joining and leaving multicast groups. They thereby leave state in parts of the network that are not in the multicast delivery tree. CBT and PIM Sparse Mode use shared group trees to which all members join and hear from all other sources. But, with larger networks they all have scalability problems. BGMP is a scalable multicast routing protocol which addresses these problems. Like CBT and PIM Sparse Mode, BGMP chooses a global root for a delivery tree. However, the root is a domain, not a single router, so if there is any path available to the domain, connectivity can be maintained. BGMP builds a bidirectional, shared tree of domains. Similarly to the unicast EGP/IGP split, BGMP is used as the inter-domain or external protocol, while domains can run any multicast IGP internally (such as CBT or PIM Sparse Mode), and can build source-specific shortest-path distribution branches to supplant the shared tree where needed. I will be explaining the following 1. The purpose of BGMP w.r.t existing multicasting protocols. 2. Overview of Unidirectional and Bidirectional trees. 3. Formation of Shared distribution trees and shortest path distribution trees. 4. Interaction with EGP and M-IGP protocols like DVMRP, PIM-DM, PIM-SM, CBT and MOSPF 5. Brief description to Message formats and Error Handling. 6. BGMP state machine. 7. Comparison of BGMP with other inter domain routing protocols like PIM-SM/MSDP etc., References IETF Draft : http://www.ietf.org/internet-drafts/draft-ietf-bgmp-spec-02.txt The MASC/BGMP Architecture for Inter-domain Multicast Routing : http://citeseer.nj.nec.com/update/185189 Intra- and Inter-Domain Multicast Routing Protocols: A Survey and Taxonomy http://www.comsoc.org/pubs/surveys/1q00issue/ramalho.html ---------------------------------------------------- #15 Who - Bokyung Wang What - Ad-hoc On-demand Distance Vector Routing (AODV) Bio - I'm a graduate student at PSU URL/Location: http://beta.ece.ucsb.edu/~eroyer/txt/aodv.ps http://www.ietf.org/internet-drafts/draft-ietf-manet-aodv-07.txt http://beta.ece.ucsb.edu/~eroyer/aodv.html http://ftp.ietf.org/ids.by.wg/manet.html Abstract: An ad-hoc network is the cooperative engagement of a collection of mobile nodes without the required intervention of any centralized access point or existing infrastructure. In this paper we present Ad-hoc On Demand Distance Vector Routing (AODV), a novel algorithm for the operation of such ad-hoc networks. Each Mobile Host operates as a specialized router, and routes are obtained as needed (i.e., on demand) with little or no reliance on periodic advertisements. Our new routing algorithm is quite suitable for a dynamic self-starting network, as required by users wishing to utilize ad-hoc networks. AODV provides loop-free routes even while repairing broken links. Because the protocol does not require global periodic routing advertisements, the demand on the overall bandwidth available to the mobile nodes is substantially less than in those protocols that do necessitate such advertisements. Nevertheless we can still maintain most of the advantages of basic distance-vector routing mechanisms. We show that our algorithm scales to large populations of mobile nodes wishing to form ad-hoc networks. We also include an evaluation methodology and simulation results to verify the operation of our algorithm. ---------------------------------------------------- #16 Who: Ravikiran Ghanta What: Multicast Address-set Claim (MASC) protocol - RFC 2909 Bio: I am a graduate student in Computer Science at Portland State University since Fall 2000. Presentation Abstract: Multicast Address-Set Claim (MASC) protocol can be used for inter-domain multicast address set allocation. MASC is used by a node (typically a router) to claim and allocate one or more address prefixes to that node's domain. While a domain does not necessarily need to allocate group addresses, allocating an address set to the domain does ensure that inter-domain group-specific distribution trees will be locally-rooted, and that traffic will be sent outside the domain only when and where external receivers exist. Outline: - Introduction (Terminology and Definitions) - Requirements for Inter-Domain Address Allocation - Overall Architecture - MASC Topology - Portocol Details - Messaging Formats - MASC Error Handling - MASC Finite State Machine - Update Message Processing URLS: http://www.ietf.org/rfc/rfc2029.txt http://netweb.usc.edu/masc/ ---------------------------------------------------- #17 who - Saravanan Jayakumar and saravn@cs.pdx.edu what - Routing in Ad Hoc Networks of Mobile Hosts by David B.Johnson bio - I am a grsduate student doing my masters in computer science at Portland State University Abstract- Ad hoc networks is a collection of wireless mobile hosts forming a temporary network.Using conventional routing protocols for routing in ad hoc networks,treating each mobile host as a router gives rise to a number of problems.This paper points of those problems and suggests a new approach based on separate route discovery and route maintenance protocols. URL - http://citeseer.nj.nec.com/johnson94routing.html ---------------------------------------------------- #18 who - Madhusudhan Jujare (jujarem@cs.pdx.edu) when - what - IDPR (Inter-domain policy routing) bio - I started full time graduate studies in cs at PSU this quarter. Previously, I was working for IBM(Sequent) from Wipro Infotech as a software engineer for around 3 years. URL/location - rfc1479 http://www.quantum.de/cgi-bin/rfcprint?rfc=1479 Abstract: IDPR is an example for policy based routing in Inter-domain i.e between Autonomous systems. The objective of IDPR is to construct and maintain routes between source and destination administrative domains, that provide user traffic with the services requested within the constraints stipulated for the domains transited. IDPR supports link state routing information distribution and route generation in conjunction with source specified message forwarding. IDPR includes the virtual gateway protocol, the flooding protocol, the route server query protocol, the route generation procedure, the path control protocol, and the data message forwarding procedure. Outline: Introduction Control Message Transport Protocol Virtual Gateway Protocol Routing Information Distribution Route Server Query Protocol Route Generation Path Control Protocol and Data Message Forwarding Procedure Security Considerations ---------------------------------------------------- #19 WHO: William Yiu Fu Kwok (kwoky@cs.pdx.edu) WHAT: Bluetooth (short range radio technology) BIO: PSU CS graduate student, third-world strong man PRESENTATION OUTLINE: Bluetooth 1. Background 1.1. The Players 1.2. The Justification 2. Architecture 2.1. Protocol Stack 2.2. Profiles 2.3. Usage Models 3. Facts and Fiction 3.1. Vaporware 3.2. Realware PRESENTATION BIBLIOGRAPHY: Bluetooth Core v1.0 http://www.bluetooth.com/developer/specification/core_10_b.pdf Bluetooth Profiles v1.0 http://www.bluetooth.com/developer/specification/profile_10_b.pdf Bluetooth Whitepaper by AU-System http://www.palowireless.com/infotooth/documents/Bluetooth_Whitepaper_-_AU_System.zip Bluetooth Architecture Overview by James Kardach http://www.palowireless.com/infotooth/documents/Bluetooth_Architecture_Overview.zip Complete Bluetooth Tutorial from palowireless.com http://www.palowireless.com/infotooth/tutorial/complete.asp SITES OF INTEREST: http://www.bluetooth.com http://www.bluetooth.com/developer/specification/specification.asp http://www.bluetooth.com/developer/whitepaper/whitepaper.asp http://www.palowireless.com/bluetooth/ http://www.palowireless.com/infotooth/download.asp ---------------------------------------------------- #20 who Li Fang when TBD what IEEE 802.11 and IEEE 802.11b for wireless LANs bio ECE Master student in OGI URL/location: http://www.manta.ieee.org/groups/802/11/ http://www.grouper.ieee.org/groups/802/11/ http://www.3com.com/technology/tech_net/white_papers/503072.html http://www.wlana.com/index.htm http://www.cs.pdx.edu/~jrb/tcpip/lectures/mipetc/index.html ---------------------------------------------------- #21 who: Noan Nguyen, email: nbnguyen@cs.pdx.edu what: voice over IP bio: part-time graduate student full-time employee of Dupont Photomask Incorporation Info/URL http://www.techguide.com/comm/sec/voiceip.pdf http://www.protocols.com/papers/voip2.htm rfc 1889: Real-time Protocol(RTP), RTP Control Protocol Book: Voice and Data Internetworking, 2nd edition, by Gil Held Voice Over IP: Strategies for the Converged Network by Mark A. Miller I. Overview Voice over IP is an advance in communications technology which enables voice to be transferred through the Internet in a cost effective way. II. Techniques 1. Voice processing a) Voice properties b) Voice compression 2. Telephone operations 3. Voice over IP a) Basic methods b) Protocols: RTP, RTCP, SIP, RSVP c) Constraints III. Conclusion __________________________________________________________________________ #22 who - Anu Wadhwa, anu@cs.pdx.edu what - Internet Routing Measurement bio - I'm a graduate CS student at PSU URL/location - "End to End Routing Behavior in the Internet", by Vern Paxson in IEEE/ACM 'Transactions on Networking' 5(5), pages 601-615 The paper can also be found on the web at www.santafe.edu/~alderson/papers/p601-paxson.pdf - Some related reading at can be found at http://citeseer.nj.nec.com/37187.html Abstract: Very few attempts have been made to formalize the study of large scale behavior of Internet routing. This paper analyzes about 40,000 routing measurements to determine and characterize the problems and failures that occur in Internet routing. The paper also investigates other routing dynamics like routing stability and routing symmetry. ___________________________________________________________________________ #23 who - Reena John, rrphilipos@hotmail.com what - Wavelength Division Multiplexing(WDM) bio - PSU CS grad student URL/location - "Evolution of Optical Transport Technologies: From SONET/SDH to WDM" by Dirceu Cavendish, IEEE Comm Magazine, June 2000 ___________________________________________________________________________ #24 who - Ravi.Sahita (@intel.com) what - MANET Routing Protocol Performance Issues and Evaluation Considerations (rfc 2501) - S. Corson, J. Macker and the Fisheye State Routing Protocol (FSR) for MANETs (I-D) bio - I'm a software engineer in Intel's Internet and Communication Lab, working on Enhanced Network Services (Policy based network mgmt, participation in the IETF O&M area (RAP wg) standards) bibliography - MANET Routing Protocol Performance Issues http://www.ietf.org/rfc/rfc2501.txt Fisheye State Routing Protocol (FSR) for Ad Hoc Networks http://www.ietf.org/internet-drafts/draft-ietf-manet-fsr-00.txt http://citeseer.nj.nec.com/pei00fisheye.html abstract - A Mobile Ad hoc Network (MANET) consists of mobile nodes which are free to move about arbitrarily, thus changing the network topology randomly and rapidly. They typically have low capacity wireless links. This presentation contrasts the characteristics of MANETs, with respect to traditional packet networks. It discusses the effect of these differences on the design and evaluation of MANET routing protocols. Fisheye State Routing is a recent proposal of a MANET Link State routing protocol that reduces routing update overhead. ----------------------------------------- # 25 who : Harkirat Singh harkirat@cs.pdx.edu When : TBD What : ATCP - TCP for Mobile Ad Hoc Networks Bio : PSU CS Graduate Student Info/URL : Paper by Dr. Suresh Singh http://www.cs.pdx.edu/~singh Abstract : Transport connections set up in wireless ad hoc networks are plagued by problems such as high bit error rate (BER), frequent route changes and partitions. If we run TCP over such connections, the throughput of the connection is observed to be extremly poor because TCP treates lost or delayed ACK's as congestion. In this paper authors present an approach where they implement a thin layer between IP and standard TCP that corrects these problems and maintains high end-to-end TCP throughput.