____________

System Implementation

____________


We are currently implementing the proposed protocol stack in MK 7.3 using the CORDS system provided (which is an extension of x-kernel with the notion of paths). In particular, the proposed QoS-enhanced CBT protocol and the rate-based message scheduling paradigm are being implemented in the routing module and in the traffic control and message scheduling module, respectively. As a preamble to implementation, we have defined, in compliance with the APIs provided in MK 7.3 and CORDS, the interfaces exported by

  • the QoS coordinator to applications. (We have also defined the callback (or upcall) functions which the QoS coordinator exports to (i) RSVP and (ii) traffic control and scheduling module, respectively.
  • RSVP to (i) the QoS coordinator, (ii) the unicast/multicast routing protocol, and (iii) the traffic control and message scheduling module, respectively.
  • the unicast/multicast routing protocol to (i) the QoS coordinator and (ii) RSVP, respectively (and the callback functions exported to the traffic control and message scheduling module).
  • the traffic control and message scheduling module to (i) the QoS coordinator (e.g., during runtime, the traffic control and message scheduling module notifies the QoS coordinator in case of QoS violation), (ii) RSVP, and (iii) unicast/multicast routing protocol (for inquiring on resources availability/usage). (The above figure depicts a subset of interfaces exported by the traffic control and message scheduling module to RSVP.)
  • A preliminary version of the interfaces exported by the QoS coordinator to the other modules is listed here.

    We are also using the GateD Multicast source codes (distributed by the GateD Consortium, Merit Network, Inc.) to prototype the proposed QoS-driven core-based tree multicast routing protocol both as a stand alone mechanism and as part of the protocol stack in NetBSD and will empirically measure its performance.


    GateD is a portable routing protocol development platform that factors out (and separately provides) functionality common to most protocol implementations. As depicted in the above figure, the modular GateD software consists of core service modules, a routing database, and protocol modules (that support multiple routing protocols). The multicast protocols currently supported by GateD include IGMP (version 2), DVMRP (version 3), CBT, and PIM-SM. We take advantage of all the core services provided, and implement, based on the CBT code available, the proposed QoS-driven core based tree protocol as one of the protocol modules. Moreover, we have defined and are currently implementing a rich, well-specified API through which a suite of multicast services with different QoS guarantees (guaranteed bandwidth, bounded delay, bounded inter-destination delay jitter, and/or a combination thereof) can be exported.


    Return to Project Home Page
    Date last modified -- August 6, 1998
    Direct comments concerning this WWW site to: jhou@ece.osu.edu