Integrated Services Test BOF (INTSERVT)

Reported by Fred Baker/Cisco Systems


Purpose of Interop Demonstration

The purpose of the demonstration is to show various real-time
applications, network behavior and value of the architecture.


Marketing Responsibilities

Seenu Banda is to arrange the showcase booth with Interop and coordinate
with marketing from other vendors in the demonstration.


Demonstration Questions

   o Precisely what service is to be offered?  WFQ-based Controlled
     Delay with one real-time service level.

   o Testing implementation interoperability will be handled by pairwise
     testing of interoperability between Bay Networks (Bay) and Cisco
     Systems (Cisco), and between workstation vendors with routers.  Sun
     Microsystems (Sun) and Information Sciences Institute (ISI) are to
     provide alpha code to promote earlier testing.

   o Topology

      -  Four to six routers from Bay and Cisco, plus some workstation
         routers.

      -  Acyclic configuration.

      -  Routers will provide Ethernets to interconnect workstations; T1
         between routers.

      -  Potential link to DartNet.


   o Baseline MIB set:  JJ and Fred to commune on the MIB. Bay will need
     a MIB to configure their routers, and will likely use their
     proprietary MIB. Cisco will use a command line interface to provide
     comparable services.

   o Applications:  commonly supported applications (VAT) and
     proprietary applications.

   o Multicast Routing:  Sun/ISI and Bay to use DVMRP; Cisco to use PIM.

   o Unicast Routing:  RIP.

   o Minimal subset of RSVP objects supported in the demonstration:

      -  IP encapsulation
      -  Common Header
      -  Session Object
      -  Next/Previous Hop
      -  Style:  Wild card Filter (WF) and Fixed Filter (FF)
      -  Flow Specification
      -  UDP/TCP Filter Specification
      -  Sender Template
      -  Sender Tspec
      -  Error Specification
      -  UDP encapsulation also required, but as a fall-back position
         can be done by putting ISI reference router between PCs and
         Cisco/Bay


   o Other items:  IP/no fragmentation and simple merging support.

   o Dependencies/Timeline

      -  Required of this IETF: Consensus to advance RSVP to Proposed
         Standard.  Frozen definition of controlled delay service and
         flow specification.

      -  Alpha test code from ISI/Sun early in August.

      -  Go/no go decision 5 September on list; fall-back is March
         Interop.

      -  Requirements for ``Go'':  Bay and Cisco have
         working/interoperable alpha code.  Two or more application
         vendors interoperating with routers.