At the moment, some of the overlay operation semantics in RELOAD are not usage 
agnostic and there is also an inherent assumption that all nodes in the overlay 
support the same set of usages and kinds.  One big problem with this is that it 
will then require a flag day to upgrade all nodes when usages evolve to 
continue having a functional overlay.  This is quite unrealistic in a 
distributed system and hence, there is a huge benefit to keeping the overlay 
level operations themselves usage agnostic.  This also nicely allows creation 
of multi and heterogeneous usage overlays - i.e., not all nodes will then be 
required to support all usages (or the same usage versions) in the overlay.  

In order to avoid writing a long email to explain the problem and potential 
solutions, I wrote it up in a draft instead.  For now, I've posted it at 
http://www.geocities.com/hellovidya/draft-vidya-p2psip-usage-agnostic-reload-00.txt.
  

It is a very quick and dirty writeup - so, apologies for any oversights and 
blatant errors.  The main body of the draft is reasonably short - I'd 
appreciate people reading and sending their thoughts on the issues and proposed 
solutions to those. 

Thanks,
Vidya
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip

Reply via email to