Glossary: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
== Whatevercast == | == Whatevercast == | ||
A proposed RINA concept that maps a RINA name to a set of destination names and/or addresses. It purports to "unify unicast and multicast", based on the observation that communication in a network of N nodes is in general n-to-m, and unicast is just the case where n=m=1, and broadcast the case where m=N-1. Basically the proposed API is allocate(whatevercastname) and the network will resolve things for you because the 'whatevercast name' has a set of rules associated with it to resolve the destination addresses. | A proposed RINA concept that maps a RINA name to a set of destination names and/or addresses. It purports to "unify unicast and multicast", based on the observation that communication in a network of N nodes is in general n-to-m, and unicast is just the case where n=m=1, and broadcast the case where m=N-1. Basically the proposed API is allocate(whatevercastname) and the network will resolve things for you because the 'whatevercast name' has a set of rules associated with it to resolve the destination addresses. We found this to be flawed, and 1:1 multicast is distinct from unicast. | ||
Revision as of 11:31, 10 October 2023
This page is under construction
Whatevercast
A proposed RINA concept that maps a RINA name to a set of destination names and/or addresses. It purports to "unify unicast and multicast", based on the observation that communication in a network of N nodes is in general n-to-m, and unicast is just the case where n=m=1, and broadcast the case where m=N-1. Basically the proposed API is allocate(whatevercastname) and the network will resolve things for you because the 'whatevercast name' has a set of rules associated with it to resolve the destination addresses. We found this to be flawed, and 1:1 multicast is distinct from unicast.