QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, QoS and CoS Developments in COIAS and MECCANO Peter T. Kirstein University College London

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Acknowledgement Slides mainly developed by Patrick Coquet for ACTS COIAS Concertation Meeting Valid equally for COIAS and MECCANO

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, MECCANO Aims MECCANO aims to deploy Medium Quality MM conferences over multicast Internet Underlying networks are those that users can get access to in Europe Tools include video, audio, shared workspace, media servers Networks include research nets, TEN-155, ISDN, DBS and local radio nets Mostly use IPv4; some move to IPv6

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, COIAS Aims Develop IPv6 for a variety of components Develop Integrated architecture for a variety of networks –Same mix as MECCANO, but more emphasis on DBS satellite and less on deployment Apply system to real problems and application developed by Eurocontrol Types of Application similar to MECCANO, but extra real-time problems

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Common Interests Variety of multimedia applications Universal use of IP - with trend to IPv6 Variety of underlying networks Applications able to signal relative priorities and qualities of service Application QoS needs translated to IP CoS Network-level IP able to use CoS to give priorities, choose technology, signal QoS

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, IP - the User-User Protocol ATM CTV ISDN ATM ISDN CTV IEEE ATM IEEE WLAN ATM IEEE @ FR

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Schematic of DBS Addition ACCESS ATM NON- ATM ACCESS G G G

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, MECCANO Topology

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, MECCANO Configuration UK (UCL and HP on SuperJANET) Germany (Bremen, Erlangen, Freiburg, Mannheim, Stuttgart on DFB) Norway (Oslo on Uninett) France (INRIA on RENATER) DBS Up-stations (INRIA and ??) Downstations & Internet at all sites including Canada (CRC) and Poland (Cracow) TEN-155 Connections between countries

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, COIAS Configuration Schematic BTRL CAM UCL ESS R R R R INRIA ACCESS SECUNET DASSAULT TEN-155

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, HIgh Performance NETworks HIPNET= IPv6 (QoS/CoS+SEC+Mobility+Multicast) All existing or Future Technologies Transparency Privacy Multi-users Nomadism Mobility Plug and Play Flexibility

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, The ISPs Problem –Provide new services: voice, video, push and inter- active services... –In an open market, Best quality/price for the customers Best benefit for the ISP –Require a simple solution Provide a limited number of traffic quality classes Boundary devices can differentiate IP flows –Map on ISP traffic classes and hence ATM QoS ISPs Interests in IP and ATM

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Corporate Interest in IP and ATM The Corporate Network Problems –Support new services: web, push and inter-active services …and (if cost effective) voice…and (if the interest is real) video. –By simple migration of the existing network infrastructure –With the guaranty that the existing applications will continue to run (at least as well as before!) ATM could increase bandwidth capacity –Its QoS is not used, because the applications do not signal QoS, and IP layers do not signal CoS,

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Proposed Solutions Differentiated IP classes of service on top of ATM QoS classes - Native ATM end stations –Differentiation of application flows at the API level –Intranet CoS policy Boundary Devices –Mapping of intranet QoS with the ISP CoS Dynamic resource reservation. If implemented : –usage limited to intranets –limited to guaranteed traffic

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Intranet implementation Application QoS Agent RSVP TCP/IPClassifier Shaper/Scheduler Classifier Shaper/Scheduler Classifier Shaper/Scheduler Classifier Shaper/Scheduler TCP/IP Application RSVP QoS Agent QoS Agent Host Router Host Admission control Admission control Admission control QoS Policy CoS/QoS Associations QoS Policy CoS/QoS Associations QoS Policy CoS/QoS Associations ATM SSM

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Shaping/Scheduler Overview Packets are classified according to the flows to which they belong The rate of each class is controlled –maximum throughput per class The rate of each station is controlled –maximum throughput per network attachment Unused bandwidth is re-allocated according to classes priorities

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, SSM configuration Available commands : –class creation, modification,suppression, –statistics per class: Number of bits transmitted in the limits, overlimit, discarded. –set the rate of the station on each subnet, –set each class parameters: priority, maximum rate on the subnet, size of the queue.

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, SSM configuration

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Differentiated Services Assured Audio Traffic Best Effort Audio traffic Traffic injection

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Differentiated Services Assured Audio Rate Best Effort UDP traffic

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, CoS/QoS architecture APPLICATION QoS demux Socket Interface Classifier Shaper/Scheduler ATM QoS (MARS) QoS/CoS Associations per port QoS Policy Classifier policy Queuing policy ATM mapping policy QoS Agent Admission ControlRSVP User interface

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Internet Protocol stack OS RSVP QoS Manager RIPng RTP RTCP RMTELNETFTPHTTP Raw IPUDPTCP IPICMPIGMP IPSECIP MobileNDP Flow Management LAN ATMCTV Satellite CONF Audio visio Terminal Emulator WEB Browser MMI WLAN

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Conclusion Queuing & shaping mechanisms are complementary –necessary and have proved their efficiency Diffserv model should be implemented in all nodes Diffserv model is compatible with the Intserv model – could be used to guaranty some critical dynamic traffic QoS/CoS policy has to be managed at a system level – just as the security policy Must define how to distribute the QoS policy objects –just as security policy objets Differentiated IP service classes should lead to the use of the ATM QoS classes

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, October, Practical Demonstrators COIAS and MECCANO provide good testbeds to experiment Will have mix of technologies - ATM, DBS and ordinary Internet TEN-155 promises to allow wide-area experimentation with QoS Both projects committed to pilot high quality MM services with real QoS