Six companies participated in an "RSVP Technology Showcase" at the Networld+Interop show held in Atlanta, Georgia the week of September 26, 1995. Use Netscape 1.1 or later to view this report.

Highlights:

The Networld+Interop demo involved six companies in a demonstration of RSVP interoperability for Internet video applications. The benefits of RSVP services were dramatically demonstrated on a small, seven-router, internet testbed: Over a three day period, people at Networld+Interop saw that video looked bad on a congested internet, and that video was usable when RSVP services were invoked.

The participants in the Interop RSVP showcase included major host and routing vendors that had enabled prototype products with RSVP. The implicit messages of the showcase were that RSVP is here, it looks promising, and it's about to be introduced into the Internet marketplace.

Report Outline:

1. Overview

• The objectives of the demo
• Short video of one demo
• Topology and what the host vendors showed
• What we did not show
• What's next

2. We met our objectives

• RSVP services permit video on congested internets
• Had good participation of...
  • ...major routing vendors, Cisco & Bay,
  • ...major host vendors, Intel, Sun, SGI,
  • ... and an ISV, Starlight networks

3. We're documenting the event in a video

• contact Mark Baugher or Don Hoffman for more information

4. The topology and applications

• 7 routers, 11 hosts, 3 traffic generators
• Starlight ran 2Mbps CellB over modified TCP/IP stack
• SGI ran VIC and NV
• Sun ran ShowMeTV and NV
• Intel ran Experimental Presenter/Viewer and NFS stored video
• Hosts ran ported versions of ISI RSVP code

host(vendor)	app	rate (kbps)	bucket-size (kb)	style
Sun	ShowMeTV	1500	100	FF
		80	1	FF
SGI	NV	256		WF
Starlight	Starworks	2000		FF
Intel	EViewer	400	40	FF
Sun	NV	256		WF
Intel	HQV/NFS	2000	40	FF

5. What was the service model that we used?

• "1-level controlled delay" or "Best-effort and better than best effort"
• Cisco implemented on WFQ and used RSVP to assign queue weights
• Bay implemented a priority queue
• JJ thought that controlled-load better describes what we ran at Interop

6. What we did not show

• Features not tested (see F.Baker's summary from interop alias archive)
  • SE filters
  • Scope object
  • Multipath network
  • Policy object
  • Integrity object
  • OPWA
  • IS flow spec
  • Traffic policing
• Did not measure delay, delay variation, loss
• Did not evaluate the effects of changing flowspecs
• Loss was negligable, however, since robust video had no problems

7. What's next?

• trials, testbeds and interoperability testing of ID08
• XIWT is supposed to develop a national testbed for RSVP
• Sun is doing a large-scale, internal test of rsvp
• Bay is sponsoring an early-use program starting in January
• Cisco and Intel are establishing MBone connectivity for ID08 testing

---

For More Information

• J.J Krawczy of Bay Networks
• Fred Baker of Cisco Systems
• Mark Baugher of Intel
• Bill Nowicki of SGI
• Joseph Pang of Starlight Networks
• Don Hoffman of Sun Microsystems

Presented by Mark Baugher, Intel Internet Technology Lab