View source for EDIFY

==Intro==
So you´ve got the net, now what about the data it should deliver? After examining different aspects of DTNs from TCP replacements over routing to network coding, this section deals with the actual transport of data. 

The authors of the paper i investigated think that the "classic" DTN architecture has some severe flaws when it comes to ''dynamic'' groups of ''mobile'' DTN nodes. The proposal - named [http://www.cse.lehigh.edu/~chuah/publications/dtn_globecom_final.pdf "Enhanced Disruption and Fault Tolerant Network" aka. EDIFY] - points out these flaws in the current (2006) DTN architecture and proposes some enhancements to correct these.


=="Classic" DTNs==
First, I'll try to clarify some DTN-related things and buzzwords, to be able to explain which flaws of the current design the "Enhanced Disruption and Fault Tolerant Network" tries to correct. I'll concentrate on aspects that relate to EDIFY.

The [http://www.dtnrg.org/docs/tutorials/warthman-1.1.pdf concept] of the [http://www.dtnrg.org DTN research group] views a DTN as a network of networks, as some sort of overlay on top of other nets, being able to support communication between these (maybe diverse) nets. These possibly diverse nets are also called '''region''' in DTN terminology ([http://www.cs.berkeley.edu/~kfall/dtn-icir.pdf]). 

DTN-wide addressing is now done via a tuple '''(region,locator)''', where ''region'' marks a network and ''locator'' a node belonging to this network. Note that addressing ''within'' a region/network can be completely different, it's up to the network how this is done. The (R,L)-addresses are specific to the overlying DTN, used to do inter-group addressing.

To actually be able to communicate with different regions, each region possesses at least one special '''gateway''' node, translating between the region's own protocol and DTN-speak and resolving global (R,L)-style DTN names into local, region-specific ones.

While this addressing scheme is quite fine with static regions, it is unable to deal with ''ad hoc'' or ''mobile'' regions...


==Problems==
===ad-hoc regions===
First, why are ''ad-hoc'' regions not supported: The assumption that is made is that nodes within a region are always able to communicate with their region members, gateway nodes being the most crucial ones.

But in reality, this isn't true: regions/networks can be split, i.e. the communication within the region can be disrupted (imagine a platoon of soldiers having to split due to enemy fire). Now there are a number of region members that are unable to talk to their region's gateway. Therefore these nodes are now unreachable from other parts of the DTN...

Another mere management problem is the joining of regions: The traditional approach makes no statements about merging of networks, not answering some important questions: How is the new region called? Does it get the name of the first or the second region coming together? More important: Who is going to be the new region's gateway?


===mobile regions===
Second, there are problems with ''mobile'' regions: Imagine a whole region/network moving around (e.g. some people in a plane). The traditional approach assumes static, non-moving regions/networks and so are it's assumptions about routing. However, with a moving network, one has to think about new aspects of routing data...


==Solution ?==
The mentioned problems are the central ones that EDIFY wants to solve. They mainly do this by using a new naming scheme for DTNs. 

I tried to summarize the whole story from problems to solution in in a talk, with the slides being downloadable [http://www2.informatik.hu-berlin.de/~beier/pdfs/iplanet-06-edify.pdf here]. Have a look if you're interested what their solution looks like...


==Material==
* the paper: [http://www.cse.lehigh.edu/~chuah/publications/dtn_globecom_final.pdf "Enhanced Disruption and Fault Tolerant Network" aka. EDIFY] by Mooi Choo Chuah, Liang Cheng, Brian D. Davison
* my slides: [http://www2.informatik.hu-berlin.de/~beier/pdfs/iplanet-06-edify.pdf are here]