Finally, the committee had to decide which networking technologies should be selected out of the dozens available. This was done simply by looking at the cost/benefit aspects of each candidate, the experience the various vendors had had with each one, and the realities of the marketplace. The set of technologies specified in BACnet was chosen because it seemed to span the real-world requirements of building control systems in terms of speed, throughput, cost, familiarity, etc. Also, Ethernet, ARCNET, and LonTalk are off-the-shelf LANs, requiring minimal work on the part of the committee to specify how BACnet messages are to be transported on them. For low-cost EIA-485 and dial-up communications we had to "roll our own" protocols in the form of the BACnet "Master-Slave/Token-Passing" protocol and the "Point-to-Point" protocol. The development of BACnet/IP was exciting because it provided not only the specification for transporting BACnet messages between IP devices but also the framework for embracing other new networking technologies with a minimal impact on existing BACnet technology.