Folks, we have just submitted a new revision of HIP BONE:
http://www.ietf.org/internet-drafts/draft-camarillo-hip-bone-01.txt we have tried to address the comments received on the list. In particular, the draft now clarifies that hop-by-hop routing uses the overlay as a rendezvous service, where routing tables are located in the architecture and what modules populate them and access them, and why there are no circular dependencies at bootstrap time. The draft also documents the issues discussed on the list related to making HIP optional, mandatory, or not even an option for P2PSIP systems. Cheers, Gonzalo _______________________________________________ P2PSIP mailing list [email protected] http://www.ietf.org/mailman/listinfo/p2psip
