> -----Original Message----- > From: Pekka Nikander [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 27, 2007 5:31 AM > To: Henderson, Thomas R > Cc: Bruce Lowekamp; P2PSIP Mailing List > Subject: Re: [P2PSIP] New draft: HIP BONE
<snip> > > > Another related question I have is whether you think the legacy > > application API (based on sockets) would work anymore with > ORCHIDs, > > because if you get a raw ORCHID across the sockets API, you can't > > tell by inspecting the ORCHID which overlay it belongs to, because > > the context ID is not visible. > > Hmm. The situation may be worse. The case may well be that the app > has no information at all about the overlays, so that it may > not even > be possible to tell the right overlay at all. In such a case my > suggestion above, i.e., to send the packet to all overlays > simultaneously, might make sense. > > > It seems that you would need to pass metadata about the ORCHID > > across the sockets API, so that the node knows > > which ORCHID-based overlay that it belongs to, or else you need to > > use LSIs even in the IPv6 case (as suggested by Philip Matthews at > > the Vancouver meeting). > > As far as I can see, that depends on the requirements. If the > requirement is simply create a secured connection to the peer if > reachable at all, then IMHO it would make sense to try all of the > overlays at the same time. As long as the number of overlays is > relatively small, the amount of additional traffic will be quite > small, and originate from the source, i.e., is not replicated in the > network. There may be policy reasons for preferring the use of one overlay over another, though. And, IMO, it seems an inelegant solution akin to replicating IP packets across all interfaces if one does not have a route to the destination. I think we need to be careful not to again conflate identifiers and locators in the architecture, this time with ORCHIDs. Tom _______________________________________________ P2PSIP mailing list [email protected] https://www1.ietf.org/mailman/listinfo/p2psip
