Re: [P2PSIP] New draft: HIP BONE

My general concern with running a peer protocol (RELOAD or P2PP) on top of 
HIP is that one will need to understand somewhat two completely different 
documents (HIP and peer protocol document) to implement a working 
solution. That increases the bar for someone who will like to quickly 
design and develop a working p2p solution.

I think there is a need to carefully perform message overhead analysis of 
HIP under different levels of churn. I am a bit confused about splitting 
the functionality between the overlay layer and the HIP layer. Is peer 
protocol no more than an encoding mechanism when implemented on top of 
HIP?

-salman

On Fri, 21 Dec 2007, Gonzalo Camarillo wrote:

> Hi,
>
> we have seen a lot of discussions on how HIP could relate to P2PSIP on this 
> list lately. While this level of interest on HIP is a good thing (from the 
> HIP community's perspective), there have been a few misconceptions and 
> misunderstandings on what is essential to HIP (e.g., the ID/locator split) 
> and what are just design or configuration choices made in a given HIP 
> deployment (e.g., using self-certifying identifiers).
>
> With the draft below, we have tried to clarify a few of the design choices 
> that can be made while defining the use of HIP in a given scenario (e.g., the 
> use of a centralized enrollment server). In particular, we have focused on 
> the use of HIP to build overlays. The draft also includes tutorial material 
> on HIP so that readers who are not familiar with HIP can still follow what it 
> is said in the draft.
>
> http://www.ietf.org/internet-drafts/draft-camarillo-hip-bone-00.txt
>
> The draft also discusses the relationship between HIP and P2PSIP. It 
> clarifies that while HIP can be used to implement connection management, 
> other functions such as overlay maintenance, and data storage and retrieval 
> are implemented using a peer protocol such as RELOAD or P2PP. We thought that 
> this clarification was important because it seems some people mistakingly 
> thought HIP was a full-blown peer protocol proposal while, in reality, HIP 
> only provides connection management.
>
> Enjoy your Christmas reading! ;o)
>
> Cheers,
>
> Gonzalo
>
> _______________________________________________
> 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