Re: [P2PSIP] New draft: HIP BONE

[Spencer] Yes, exactly. I'm not sure that we DON'T have circular 
dependencies yet. I'm still trying to understand whether the peer protocol 
is a user of HIP or an enabler of HIP.

Thanks,

Spencer

From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>

The difficulty I have (also with the OSPF analogy) is that it seems
necessary to avoid circular dependencies.  OSPF and IS-IS build IP
forwarding tables but, in so doing, they do not use those IP forwarding
tables, because that would be a circular dependency.  If you say that
peer protocol and resolution and routing service are combined, then it
seems to me that you are saying in HIP BONE that the peer protocol is
both a user of HIP (in some contexts) and an enabler of HIP (such as
overlay-routing the HIP messages).

If HIP provides connection managment, and the peer protocol provides
data storage and retrieval, and peer protocol uses HIP for its
connections, and HIP uses the peer protocol for data storage, there seem
to be some circular dependencies.  Or does HIP only apply to the media
stream connections?

I'm led to assume that, in the model you're describing, the peer
protocol has to operate in the absence of HIP (and must implement ICE);
i.e., data storage and retrieval is necessary to bootstrap HIP, and
therefore the connections used to implement data storage and retrieval
do not run over HIP.  Is that correct, or am I missing something?

- Tom

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip