Subject: Re: [T2TRG] draft-wu-t2trg-network-telemetry-00

From: "[email-masked]" <[email-masked]>
Date: Fri, 1 Apr 2016 17:17:03 +0800

Hi, Qin and folks,
I've tried to do a thorough review of the draft-wu-t2trg-network-telemetry-00. 
My general feeling about the document is that it may be a good way to improve the visibility of the IoT network topology and the available network resources. 
As we know, network administrator should know real-time running state of the whole IoT devices, at least, should know whether a device works well. 
For high-capacity IoT devices such as appliances (e.g., television, refrigerator, air conditioner, and washing machine), which can be directly connected to internet through access device, we may read the logs of these access devices to get the state data.  
For low-capacity and non-IP IoT devices such as sensors (e.g., light, meter, room temperature controller, and sensors) , which may be first connect to a transform device(such as cluster header, home gateway or bridge, etc.) and then to internet, the situation is even more complicated. The non-IP IoT devices may use different protocols(e.g., WiFi, Bluetooth, and ZigBee) to communicate with the transform device, and use like"heart-beat message" to tell their manager they are still on line and work well. we may have to access each transform device to extract these "heart-beat message" to get the state data. The above manual operation will be cumbersome and time-consuming as the number of them increases rapidly in a network.
So, network telemetry is worth to do.  

Best wishes
Xiaowei Qin