As I understand it, while an identifier may, in a specific protocol proposal, have structure (hierarchical or otherwise), there are no specific structural requirements for identifiers in general. There is no general requirement that they have structure.
Yours, Joel Xu Xiaohu wrote: >> We discussed this at Dagstuhl and came away with the following: >> >> - topology�\independent >> - stable, at discretion of owner >> - unambiguous >> - distinguishable (two for same object?) >> - facilitate session�\level referrals > > Does the identifier need any structure? e.g. hierarchical information. so as > to make the ID based routing on overlay network (mapping overlay)more > efficient and make the ACL more flexible. > > Xiaohu > > > > ------------------------------------------------------------------------ > > _______________________________________________ > rrg mailing list > [email protected] > http://www.irtf.org/mailman/listinfo/rrg
_______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
