Ouroboros Frequently Asked Questions: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Paper Remarks = == Ouroboros claims Unicast and Multicast must be distinct mechanisms. However, these mechanisms interact seamlessly for existing protocols such as IP/ARP a...") |
No edit summary |
||
Line 1: | Line 1: | ||
= General Remarks = | |||
== A new model should demonstrate a NEW capability, not just existing examples. == | |||
= Paper Remarks = | = Paper Remarks = | ||
Revision as of 15:44, 16 October 2022
General Remarks
A new model should demonstrate a NEW capability, not just existing examples.
Paper Remarks
Ouroboros claims Unicast and Multicast must be distinct mechanisms. However, these mechanisms interact seamlessly for existing protocols such as IP/ARP and IPv6 (where, in particular, IPv6 packets are transmitted as Ethernet multicast until MAC learning occurs). Isn't this contradictory?
We need to make a distinction here. The claim which we are making is that the process that is doing either multicast or unicast needs to be aware that it is doing so. In the example given, the application uses IPv6, and IPv6 is doing multicast until MAC learning occurs. It is not the application that is using IPv6 that is a multicast application. The IPv6 protocol