Lines Matching +full:size +full:- +full:report

32 …udes the platform abstraction for Thread Radio Encapsulation Link (TREL) using DNS-SD and UDP/IPv6.
49  * @addtogroup plat-trel
52 …odule includes the platform abstraction for Thread Radio Encapsulation Link (TREL) using DNS-SD and
68 …* 2) Platform layer MUST initiate an ongoing DNS-SD browse on the service name "_trel._udp" within…
72 … guaranteed, however. When a TREL service instance is discovered, a new ongoing DNS-SD query for an
89 …* After this call, the platform layer MUST stop DNS-SD browse on the service name "_trel._udp", st…
90 …* TREL DNS-SD service (from `otPlatTrelRegisterService()`) and MUST close the UDP socket used to r…
97  * Represents a TREL peer info discovered using DNS-SD browse on the service name "_trel._udp".
104      * - TRUE indicates that peer is removed.
105      * - FALSE indicates that it is a new entry or an update to an existing entry.
110 …* The TXT record data (encoded as specified by DNS-SD) from the SRV record of the discovered TREL …
121 …* is determined from the DNS-SD query for AAAA records on the hostname indicated in the SRV record…
128  * This is a callback function from platform layer to report a discovered TREL peer info.
142 …* Ideally the platform underlying DNS-SD should detect changes to advertised port and addresses by…
145 …* restart/confirm the DNS-SD service/address resolution for the peer service and/or take any other…
156  * Registers a new service to be advertised using DNS-SD [RFC6763].
159  * name and the local DNS-SD domain name will produce the full service instance name, for example
160  * "example-host._trel._udp.local.".
163  * used for service registration in the case of a non-mDNS local DNS-SD service.
214     uint64_t mTxBytes;   ///< Sum of size of packets successfully transmitted through TREL.
217     uint64_t mRxBytes;   ///< Sum of size of packets received through TREL.