dtnrg-3----Page:32
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
|
Late Binding in SPINDLE DTN endpoint names can have multiple time-varying attributes a source may not have the information necessary to determine which endpoints match the destination name attributes due to intermittent connectivity in DTNs therefore, we need late binding of attributes i.e., not at originator, but in-network We focus on two key late binding services: bind destination name attributes to values, and map partially bound intentional destination names to canonical names, e.g.: Intentional destination name: teamLeader@{org=Army,loc=36N/43E} Canonical name: JohnDoe@unit101.army.mil bind convergence layer attributes (e.g. protocol, interface, address) coarse grained information about a future adjacency may be used by routing but CL attribute bindings deferred until discovery and/or bundle forwarding |