1. What’s the difference between M2M and IoT?
   
   Machine to Machine (M2M) has been around for a long time to refer to communications that happen between machines or devices. Typically one end of the interaction is a device like a sensor or meter capturing events like a stock level or a temperature. The message is then passed over wired or wireless networks to a hub. M2M may be on both open and closed networks. See more detail on Wikipedia.
   
   The Internet of Things (IoT) begins with the thought that each device sensor meter could take join the internet and pass its events using the internet. IoT has become a broader term encompassing M2M together with mobile device communications and the explosion of internet capable devices - usually using the internet as an open network.
    
2. Is MQTT a standard today?
   
   MQTT is in the process of being standardized with Oasis under the Paho project at the moment. Please see the latest here.
    
3. What’s the difference between mobile and IoT?
   
   There's a lot in common between the mobile and IoT spaces. Some of the most powerful solutions come from combining both technologies. For example in a connected car the sensors are enabled to connect over the 3G wireless network but the solution comes to life when you can click a button in a mobile application running on your phone to unlock the car when you've locked yourself out. 
    
   Some of the light weight technology used for the IoT like MQTT can be useful to make fast secure reliable responsive mobile applications. Stock checks instant messaging and score trackers are particularly appropriate but anything where the server needs to publish frequent updates to one or more waiting users can really take advantage.
    
4. Do you see opportunities in other industries?
   
   There are many opportunities in different industries. The first industries which have been able to take advantage of this technology are in the ConnectedCar where manufacturers will need to rapidly scale to millions of users once enabled cars start rolling off the production lines.
   
   There is a well-established need for this kind of technology in the Energy and Utilities space. Oil and Gas pipelines need instrumentation to monitor their flows; the existing systems are often slow and costly to run as they are built on polling technology.
   
   Smart meters projects are beginning to move the grid to become better monitored and more adaptive and responsive.
   
   There are opportunities in Banking; to improve security and responsiveness for mobile customers and open up new possibilities - giving companies security of their messages from end to end.
   
   We've seen lots of innovative ideas for assisted living allowing people to live in their own homes for longer whilst giving peace of mind for relatives that they'll be alerted if something goes wrong.
    
5. Can MQTT used for real-time request/response paradigm?
   
   MQTT is designed to be lightweight and fast. There are different qualities of service (QoS) which give tradeoffs between performance and reliability:
   
   - QoS0 At most once: The message is delivered at most once or it may not be delivered at all. Its delivery across the network is not acknowledged. The message is not stored. The message could be lost if the client is disconnected or if the server fails. QoS0 is the fastest mode of transfer. It is sometimes called "fire and forget".
   
   - QoS1 At least once: The message is always delivered at least once. It might be delivered multiple times if there is a failure before an acknowledgment is received by the sender. The message must be stored locally at the sender until the sender receives confirmation that the message has been published by the receiver. The message is stored in case the message must be sent again.
   
   - QoS2 Exactly once: The message is always delivered exactly once. The message must be stored locally at the sender until the sender receives confirmation that the message has been published by the receiver. The message is stored in case the message must be sent again. QoS2 is the safest but slowest mode of transfer. A more sophisticated handshaking and acknowledgement sequence is used than for QoS1 to ensure no duplication of messages occurs.
   
   'Real-time' means different things to different people. There is real time as used by a fighter pilot when controlling an aircraft when only the fastest possible response will be appropriate. 
   
   For practical purposes MQTT responses happen as you look at them almost all of the latency is in the network rather than in the processing in MessageSight. It makes it appropriate for instant messaging and unlocking of car doors in key fob response time.
    
6. How is MQTT different from IBM MQ?
   
   IBM MQ is designed to run enterprise messaging workloads. It supports point to point as well as pub/sub style messaging. It gives you a huge amount of control on clustering and reliability aimed specifically at enterprise workloads. 
   
   IBM MessageSight gives you a secure hardened appliance specifically built to be deployed in the DMZ coupled with the lightweight fast responsiveness of MQTT designed for the IoT.
   
   On slide 13 it is mentioned : 1 rack = 273M msg/sec 21M concurrent connections. 1 M concurrent connection on slide 14.
   
   One million connections per appliance. If you fill a rack with appliances then you can achieve higher numbers.
    
7. Is this product available as a SaaS on SoftLayer? Can I see a demo?
    
   IBM's statement of direction on IoT Cloud refers to a SaaS offering that will be available in the cloud in the future.
   
   There is a MessageSight for developers Virtual image available for download here.
   
   Demos of MessageSight can be seen here. 
    
8. What is the cost of MessageSight basic startup appliance cost?
    
   An IBM MessageSight appliance list price is $188k USD. Please check with your IBM representative for your region.
    
9. Are devices in general designed to share data to talk MQTT?
   
   More and more devices are capable of communicating using MQTT. MQTT clients are available in many different formats and languages to suit different devices large and small. Our experience with working with device manufacturers is that it's been very straight forward for them to pick up and start using MQTT.
    
10. What patterns do you see for business gaining access/permission to the data from these sensors? Consumer opt-in? Commercial datamarts? (not sure I want anyone to know how much beer/junk-food is in my fridge!)
    
    The topic of data ownership is really hot at the moment. Companies are recognizing that the data is valuable and there are lots of different people with a claim on ownership. Does the user who generated the data own it? What kind of incentive would they need to part with that data? Does the driver of a car own the data from it or does the manufacturer or the fleet leasing company? Can they legitimately sell that data on? These questions are inconsistently answered across different industries at present - expect to see some consolidation as the solutions mature.

To learn more about this webcast please download the presentation. The video replay is coming soon!