to endow T.130-compliant nodes with the ability to advertise attached devices and their associated attributes. A T.RDC protocol will be defined to control, configure, query status and receive event notifications from remote peripherals. Development of T.120 Compliant Products With the T.120 standards complete, third-party developers must now implement them. Several development environments are available for doing SO. Perhaps the oldest and most widely used is DataBeam's T.120 toolkit for developing multimedia data-sharing applications. The toolkit encapsulates the complex T.120 specification into a development environment that can be used to create complex, standards-based point-to-point and multipoint applications. Others have followed in DataBeam's footsteps. DataBeam deserves special mention because it has been involved in the T.120 process since inception, and because it has displayed admirable restraint in Standards for Audiographic Conferencing avoiding any temptation to put its own particular spin on things. DataBeam has acted in the interests of the T.120 family of standards and, therefore, in the interests of users, vendors, and the market in general. Using T.120 mature development environments accelerates the development of software applications and network infrastructure products (i.e., PBXs, bridges, routers, network switches, and LAN servers). T.120-based products can deliver industry-wide interoperability in the areas of data collaboration and document conferencing. For a complete list of companies that supply these products, refer to Appendix H, Interactive Multimedia Suppliers (by Category). T.120 / T.130: A TRIBUTE TO THE ITU-T AND IMTC To respond to proprietary audio video system, standards-based products must provide roughly equal capabilities. The argument that proprietary is better is only difficult to counter when standards bodies stop short of complete specifications that address real-world needs. The ITU-T and the IMTC perform a tremendous service for the video communication and data colla