- Test - lists.nanog.org

Speakers: 6th Maryland Workshop on Very High Speed Networks
by Account of Maryland Center for Telecommunications Research 12 Sep '95

12 Sep '95

******************************************************************************* Speaker List 6TH MARYLAND WORKSHOP ON VERY HIGH SPEED NETWORKS ******************************************************************************* 1. Inder Gopal: IBM Watson Research Center (Keynote Address) Electronic Commerce: Technical Issues and Challenges 2. J. H. Maestas: Sandia National Laboratories Experiences with SONET Transport Networks 3. Rick Wilder: MCI The NSF's very-high-speed Backbone Network Service: Architecture and Project Plans 4. J. H. Naegle: Sandia National Laboratories Progress with ATM at Sandia National Laboratories 5. Mani B. Srivastava, P. Agrawal, A. Asthana, M. Cravatts, E. Hyden, P. Krzyzanowski, P. Mishra, B. Narendran, and J. Trotter: AT&T SWAN: Testbed for Mobile Networked Computing 6. Jonathan M. Smith: Univ of Pennsylvania TCP/IP performance of the Penn Afterburner ATM Link Adapter 7. Brad Makrucki: BellSouth Telecomm What's Wrong with Equivalent Bandwidth? 8. Robert J. Aiken: Department of Energy/ Lawrence Livermore Lab The ENERGY of HIgh Speed Networking 9. Vern Paxson: LBL Adapting to Wide-Area Network Dynamics 10. Magda El Zarki: Univ. of Pennsylvania Video over ATM Quality Control 11. Michael Levender: Stratacom Applications Support Over ATM: An Update 12. Bernie Hudson: University of Ottawa High Speed Network Connecting Canada, Europe and North Africa 13. Thomas vonDeak: NASA Lewis Research Center Status of the NASA Advanced Communications Technology Satellite (ACTS) Program and B-ISDN Development 14. Guru Parulkar: Washington University Error Control for Continuous Media Applications 15. Anujan Varma: University of California FAST: A Hardware Simulation Testbed for ATM Network 16. Raj Jain: NSU Traffic management in ATM Networks 17. Donald Smith: Bellcore Adaptive Congestion Controls in SS7 and Implications for Broadband Signaling 18. Javad Boroumand: NASA Goddard Space Flight Center NASA EOSDIS Project ATM Prototyping 19. Ted Faber: USC/ISI Research in the ATOMIC-2 Project at ISI 20. Jorg Liebeherr, I. F. Akyildiz and D. Sarkar: Univ. of Virginia An Explicit Rate Control Scheme for ABR Traffic with Heterogeneous Service Requirements 21. Roch Guerin: IBM Watson Research Center (To be confirmed) <<TITLE(High Speed Networking)>> 22. Bob Collet: Sprint <<TITLE(Sprint's SONET Infrastructure)(To be confirmed)>> NOTE: Other speakers to be confirmed. --------------------------------------------------- 6th Maryland Workshop on Very High Speed Networks --------------------------------------------------- OCTOBER 30-31, 1995 Maryland Center for Telecommunications Research Department of Computer Science and Electrical Engineering University of Maryland Baltimore County The Maryland Center for Telecommunications Research (MCTR) and Department of Computer Science and Electrical Engineering at the University of Maryland Baltimore County (UMBC) in participation with the University of Maryland Institute for Advanced Computer Studies (UMIACS), IEEE Communication Society - Gigabit Networking Technical Committee, and IDA/Center for Computing Sciences will hold the 6th Maryland Workshop on Very High Speed Networks on October 30-31, 1995 at the UMBC campus. The Workshop will be held in Ballroom of University Center on the UMBC campus. The workshop is supported by IBM, SUN and Sprint. The goal of the Workshop is to bring together experts in related areas to discuss progress and research issues in the design and implementation of very high speed communication networks. Each of the previous workshops attracted approximately 150 researchers representing academia, industry and government. The two day meeting will include invited speakers and contributed presentations. Papers on selected presentations will appear in a special issue of the Journal of High Speed Networks. For more information on MCTR and directions to UMBC check our home- page on WWW.(http://www.cs.umbc.edu/~mctr) A registration fee of $150 will include two lunches and conference proceeding. For questions regarding the technical content of the workshop or giving a presentation, please contact the workshop organizer, Dr. Deepinder Sidhu, at Tel: (410) 455-3028, Fax: (410) 455-3969, Email: mctr(a)cs.umbc.edu. ------------------------------------------------------------------------------- 6th Maryland Workshop on Very High Speed Networks (October 30-31, 1995) Registration Form Name: ---------------------------------------------------------------------- Affiliation: ------------------------------------------------------------- Address: ------------------------------------------------------------- ------------------------------------------------------------- Phone: Fax: Email: ---------------- ------------- ------------ Dietary Restriction : Vegetarian Kosher ---------- ------------ ------------------------------------------------------------------------------- Mail checks (payable to University of Maryland Foundation) and registration form to Dr. D. P. Sidhu, Maryland Center for Telecommunications Research, University of Maryland Baltimore County, Baltimore, MD 21228. All funds for this event will be managed by the UM foundation. We plan to provide free admission to a limited number of students if a grant application is approved. Please DO NOT include hotel accommodation expenses in your payment for the Workshop Registration. Room payment should be made directly to the hotel you selected for stay. The following hotels are closest to UMBC campus. Some hotels may offer reduced rate. To obtain the reduced rate, you must identify yourself as an attendee of this workshop. BWI Airport is approximately five miles from UMBC Campus. 1. Sheraton International Hotel - BWI Airport. Closest to airport and UMBC campus. Tel: (410) 859-3300 or (800) 638-5858 2. Holiday Inn - BWI Airport. Close to airport and UMBC campus. Tel: (410) 859-8400 or (800) HOLIDAY 3. Omni Inner Harbor Hotel. Close to Downtown Baltimore / Inner Harbor. About 20 minutes drive to UMBC campus. Tel: (410) 752-1100 or (800) 843-6664

1 0

Re: tape
by sob＠academ.com 12 Sep '95

12 Sep '95

There will be notes on all that happened at NANOG up next week at the following URL: http://www.academ.com/nanog/september1995 -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: amdahl!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

1 0

Re: tape
by Steven J. Richardson 12 Sep '95

12 Sep '95

There are slides John Vollbrecht is using which will be available on-line at the usual place [I don't remember the exact URL, but it is somewhere under the www.ra.net server]. Steve R. == >From nanog-request(a)MERIT.EDU Tue Sep 12 11:00:22 1995 Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6.12/merit-2.0) with ESMTP id LAA00652; Tue, 12 Sep 1995 11:00:15 -0400 Received: (from slist@localhost) by merit.edu (8.6.12/merit-2.0) id LAA08128; Tue, 12 Sep 1995 11:00:12 -0400 Resent-Date: Tue, 12 Sep 1995 11:00:12 -0400 Message-Id: <9509121459.AA12103(a)mailer.psc.edu> To: Nathan Stratton <nathan(a)netrail.net> Cc: nanog(a)MERIT.EDU, mathis(a)zippy.psc.edu Subject: Re: tape In-Reply-To: Your message of "Tue, 12 Sep 1995 10:40:04 EDT." <Pine.LNX.3.91.950912103844.22716B-100000(a)netrail.net> Date: Tue, 12 Sep 1995 10:59:49 -0400 From: "Matt Mathis" <mathis(a)zippy.psc.edu> Resent-Message-ID: <"auLdO3.0.-x1.j1QLm"@merit.edu> Resent-From: nanog(a)MERIT.EDU X-Mailing-List: <nanog(a)MERIT.EDU> archive/latest/54 X-Loop: nanog(a)MERIT.EDU Precedence: list Resent-Sender: nanog-request(a)MERIT.EDU Status: R Sorry, we are not recording, and the talk is already in progress. --MM--

1 0

cusemee?
by Michael F. Nittmann 12 Sep '95

12 Sep '95

is it cusemee'd? reflector? Mike ------------------------------------------------------------------- Michael F. Nittmann mn(a)ios.com Senior Network Architect ------------ IDT/IOS - Internet Online Services ---------- 294 State Street -------- Hackensack, NJ 07601 ------ ---- +1 (201) 928 1000 xt. 500 -- +1 (201) 928 1057 FAX +1 (201) 441 5861 Pager \/

1 0

tape
by Nathan Stratton 12 Sep '95

12 Sep '95

Hi, I am siting in my hotel room working to get a customer up. I wanted to be at the radius talk. Is this being taped? If so how do I get a tape of it? Nathan Stratton CEO, NetRail, Inc. Your Gateway to the World! --------------------------------------------------------------------------- Phone (703)524-4800 NetRail, Inc. Fax (703)534-5033 2007 N. 15 St. Suite B-5 Email sales(a)netrail.net Arlington, Va. 22201 WWW http://www.netrail.net/ Access: (703) 524-4802 guest ---------------------------------------------------------------------------

2 1

Other flapping prefixes. Compare and contrast.
by Sean Doran 12 Sep '95

12 Sep '95

There were several other providers who got notes from me about prefixes that were flapping every several seconds or thereabouts. The tally so far: Polite "we have a ticket open and will get someone to fix things" from three providers (thanks ANS, BBN, EBONE). A trio of no-answer-yets, one of which has since been fixed, one of which will be fixed since I have the advantage of sharing a room with the routing guru of the NSP in question and the bigger advantage of not needing nearly as much sleep. :-) The third no-answer-yet is from a smaller provider in Europe, and I expect they'll get back to me in their morning. Finally, there was the previous reply. Sean. P.S.: Oh, I also have to thank Pushpendra Mohta of CERFNET who replied to an earlier note personally with an explanation of what was going on.

5 5

Re: nisc-03292 (ticket update) badly flapping prefix (204.4.27/24)
by Sean Doran 12 Sep '95

12 Sep '95

Hi Cole - Wish you were here at the NANOG conference. Thanks for the update on the information, and a clarification of your policy. Please don't be too hard on your operator for treading on a landmine; we all know what it's like being on the front lines and making a mistake. Also thanks for the good news that all your new dialup customers from here on will be aggregated into shorter prefixes; this is nice to see! Sean.

1 0

nisc-03292 (ticket update) badly flapping prefix (204.4.27/24)
by PSI NISC 11 Sep '95

11 Sep '95

Ticket #nisc-03292 09/11/95-17:55:14 libby SUBJECT: badly flapping prefix (204.4.27/24) Posted by: Cole G. Libby ---------- Sean, Allow me to correct the too quick response you received from one of my people this weekend. We agree that this network is flapping far too many times and that this is a bad thing. Clearly the customer cannot be getting much useful service here either. We are contacting the customer to assist with his configuration and reduce the number of route flaps. This is something that we do periodically with all our dialup customers to ensure that they are getting good service and are being good 1 neighbors. This is not the only network in this circumstance that we are addressing. This network is not in a PSI CIDR block and is therefore portable and not a candidate for aggregation. Additionally, this network is used with a legacy account that was purchased at a time when this was permitted. In January, we have stopped allowing new dialup customers to use networks that are not in PSINet CIDR blocks. Since these blocks are indeed aggregated this has the effect you desire. Thanks Cole Libby Manager, PSI Customer Support >Sean, > The customer that this network belongs to is a dial-up customer, and >as such, when his connection is up, we broadcast his network IP, and stop >broadcasting when he disables his connection. We are unable to prevent his >route from propagating in the face of what could be frequent log-in/log-outs. > >Aaron Silver >PSI Customer Support > > >Ticket #nisc-03292 09/10/95-17:50:04 silvera SUBJECT: badly flapping prefix (204.4.27/24) >Posted by: Sean Doran <smd(a)icp.net> >---------- > >Hi - > > Could you please look into this badly flapping prefix with >a view to stopping it from oscillating this wildly? > > Thanks! > > Sean. >- -- >SL-CHI-12> sh ip bgp 204.4.27.0 >BGP routing table entry for 204.4.27.0 255.255.255.0, version 656911 >Paths: (2 available, no best path) > 1239 174 (history entry) > 144.228.101.1 (metric 15) from 144.228.50.6 (144.228.56.1) > Origin IGP, metric 1, localpref 90, external > Dampinfo: penalty 2867, flapped 171 times in 20:14:19 > 1239 174 (history entry) > 144.228.101.1 (metric 15) from 144.228.50.3 (144.228.53.1) > Origin IGP, metric 1, localpref 90, external > Dampinfo: penalty 2862, flapped 170 times in 20:13:55 >

1 0

Re: Other flapping prefixes. Compare and contrast.
by lear＠yeager.corp.sgi.com 11 Sep '95

11 Sep '95

The note that was forwarded was simply unbelievable at this day and age. The Internet community has to pay a large price when a major provider has a policy of not aggregating routes and also not using statics for sole dialup customers. Such behavior should be made readily apparent to perspective customers, resellers, and referrals so that they might understand the technical capabilities and marketing tactics of a given provider. Sean is fighting the good fight to get people to do the right thing. That he does so with gorilla tactics at times is probably appropriate given in some cases the lack of response and in other cases completely inappropriate response from various providers and customers. As his customer I *very* much appreciate and encourage his efforts. -- Eliot Lear [lear(a)sgi.com]

1 0

Re: Other flapping prefixes. Compare and contrast.
by hwb＠upeksa.sdsc.edu 11 Sep '95

11 Sep '95

Well, while Sean's wording at times is, ahem, suboptimal, he is referring to a real problem in the Internet System, and in fact one that the North American Network Operators Group should take responsibility for, at least for the North American part. The problem is what others believe is a strength: an anarchic system of many autonomous service providers with little or no service model/metrics (neither for the local nor for the system level), and no well defined rules of conduct for interoperation and problem resolution. A few weeks back I had problems with getting to another CONUS site. Not exactly capillary connectivity, source was at SDSC, destination at FIX-West. My service provider is CERFnet. Some days after emailing about the problem (it happened on a Friday evening that I had very intermittent connectivity, with packets from my traceroute getting lost in Sprintlink land) I got actually quite polite and professional responses that, based on my traceroute, it was outside of CERFnet's domain and best they can do is inform Sprint. As I network engineer I understand the context and the issues. As a network user I do not find the service model acceptable. I thought my service provider was selling me Internet connectivity, not regional connectivity. This is not to single out CERFnet or Sprint, given the way The System is run, the service providers likely are all the same, at least above the 90th percentile. Certainly because there is no global (or even domestic) problem resolution procedure that has any leverage with other service providers. Eventually something hits the roof for someone, and he starts bitching more publicly as his only remaining leverage, which is what seemed happening to Sean. What choice did he have? Run to the government and ask for regulation, as the service providers just can't get their act together at a systemic level? Well, that may not be one of *his* first choices, but sooner or later Real Users (rather than us networking bigots) get pissed. You know, those you sell services to? That you give, say, T1 connectivity to without being clear what it means to a user, who's traffic may have to traverse five ISPs? And who may not be interested in hearing about finger pointing from the service provider or deferred problem resolution? I mean, what would you say if your electrical power would drop to 80 Volts (more than once in a year) and your local power company would tell you "uh, that's not our fault, it is just power company 2000 miles away ran out of oil, or misplaced some nuclear refuelment rod?" This all should be critical to the NANOG agenda if the service providers would want to continue to provide quality services. I think it is an attitude problem of people largely caring about their own swamp.

6 6