> Op 5 aug. 2015, om 16:36 heeft Mikael Abrahamsson <[email protected]> het > volgende geschreven: > > On Wed, 5 Aug 2015, Teco Boot wrote: > >> PS. It could be a tough job to get bursty multicast frames in AC_VO. At >> least it needs a shaper for xx% of airtime. > > Why multicast?
At least discovery needs multicast. LSDB sync can be unicast. There is code for IS-IS for that, right? Having unicast LSDB sync in AC_VO could be less hard to implement and adopted. IMHO it SHOULD have a shaper, based on airtime. This results in RP requirements, for having good support for WiFi (or other 802.11 modes, other wireless links). The RP MUST support wireless media, where multicast rate is typically at a low rate and could be lossy. Bulk transfer, e.g. LSDB synchronization, MAY make use of unicast mode, with adaptive rate and a retransmit scheme in case of packet loss. For relayed messages, a jitter mechanism SHOULD be used to desynchronize for collision avoidance. In case of queued or lost packets, path calculation could get desynchronized and packet loops may occur. The RP SHOULD circumvent such convergence problems. Teco _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
