Re: [P2PSIP] Re: HIP pros and cons

"Wei Gengyu" <weigengyu@vip.sina.com> Mon, 17 December 2007 11:19 UTC

Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4E0F-0007zN-Ap; Mon, 17 Dec 2007 06:19:19 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4E0D-0007eq-8F for p2psip@ietf.org; Mon, 17 Dec 2007 06:19:17 -0500
Received: from smtp.vip.sina.com ([202.108.3.172]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4E08-0003JG-JA for p2psip@ietf.org; Mon, 17 Dec 2007 06:19:15 -0500
Received: from dellwei (unknown [211.160.21.17]) by smtp.vip.sina.com (SINAMAIL) with ESMTP id A0C431DD8E1; Mon, 17 Dec 2007 19:19:07 +0800 (CST)
Message-ID: <000e01c8409e$a16f5e60$da07740a@dellwei>
From: Wei Gengyu <weigengyu@vip.sina.com>
To: Henry Sinnreich <hsinnrei@adobe.com>
References: <001201c83fd6$58430e80$da07740a@dellwei><24CCCC428EFEA2469BF046DB3C7A8D223AE412@namail5.corp.adobe.com> <000001c84058$fabe14c0$da07740a@dellwei> <24CCCC428EFEA2469BF046DB3C7A8D223AE41C@namail5.corp.adobe.com>
Subject: Re: [P2PSIP] Re: HIP pros and cons
Date: Mon, 17 Dec 2007 19:18:55 +0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: fc231bf912a450f71747fa7a4e3e2f5a
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0475236093=="
Errors-To: p2psip-bounces@ietf.org

Henry,

NO. 

Please use your searching tool to look-up "p2p layer"in those files.
Do it before replying.

I did not find "P2P layer".
There is no explicit definition or description of "p2p layer"


Gengyu
  ----- Original Message ----- 
  From: Henry Sinnreich 
  To: Wei Gengyu 
  Cc: P2PSIP Mailing List 
  Sent: Monday, December 17, 2007 11:28 AM
  Subject: RE: [P2PSIP] Re: HIP pros and cons


  Gengyu, 

   

  > What is p2p layer? What do you mean "p2p layer"?

   

   

  There is quite clearly exemplified in:

   

   ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-matthews-p2psip-id-loc-00.txt 

   

   ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-baset-p2psip-p2pp-01.txt Please see Fig. 2.

   

  One could not explain it any better IMHO.

   

  Henry

   


------------------------------------------------------------------------------

  From: Wei Gengyu [mailto:weigengyu@vip.sina.com] 
  Sent: Sunday, December 16, 2007 8:59 PM
  To: Henry Sinnreich
  Cc: P2PSIP Mailing List
  Subject: Re: [P2PSIP] Re: HIP pros and cons

   

  Henry,

    

  I am very appreciated your comments. And no new questions about this thread.

   

  But I hope to get hints on some already raised questions. 

  Would you please help me clarify that?

   

  What is p2p layer? What do you mean "p2p layer"?

   

  In "draft-matthews-p2psip-hip-hop-00.",we can see 'p2p-layers' 

  that including IPv4 or IPv6, UDPv4 or UDPv6?, HIP or ESP, TCP or UDP, and distributed database. 

  The 'p2p layers'contain five layers. 

   

  I need to know the difference between "p2p layer" and 'p2p layers'.

  So, I shall see where you put HIP under p2p layer.

   

  In "draft-hautakorpi-p2psip-with-hip-01.txt", there are four suggestions in protocol layer scheme.

  Only (a) of Figure 3 contains HIP, but HIP is set on top of Peer protocol.

  whist there is no words of "p2p layer", it seems that Peer protocol should at that layer.

   

  Refer to  "draft-willis-p2psip-concepts-04 - Concepts and Terminology for Peer to Peer SIP",

  "2.  High Level Description

   

     A P2PSIP Overlay is a collection of nodes organized in a peer-to-peer
     fashion for the purpose of enabling real-time communication using the
     Session Initiation Protocol (SIP).  Collectively, the nodes in the
     overlay provide a distributed implementation of the location service
     [RFC3261] for mapping Addresses of Record (AoRs) to Contact URIs.
     They also provide a transport service by which SIP messages can be
     transported between any two nodes in the overlay.

   

     A P2PSIP Overlay consists of one or more nodes called P2PSIP Peers.
     The peers in the overlay collectively run a distributed database
     algorithm.  This distributed database algorithm allows data to be
     stored on peers and retrieved in an efficient manner.  It may also
     ensure that a copy of a data item is stored on more than one peer, so
     that the loss of a peer does not result in the loss of the data item
     to the overlay.   "

   

  Unforunately, there is no explicit definition of "p2p layer" in the I-D

  although so many people say "p2p layer" in this mailing list.

   

  Even it seems to be a silly quetion, "p2p layer" is still a vague concept when people say it.

  So, I think that WG needs to make this basic definition clear. 

   

  Best regards,

   

  Gengyu 

    ----- Original Message ----- 

    From: Henry Sinnreich 

    To: Wei Gengyu ; P2PSIP Mailing List 

    Sent: Monday, December 17, 2007 7:21 AM

    Subject: RE: [P2PSIP] Re: HIP pros and cons

     

    > My problem is when HIP is used at the application layer, 

    > or using the same algorithm to generate Peer ID. 

     

    HIP runs below the application layer and also below the p2p layer. 

    HI is different from the p2p nodeID or application layer (such as SIP) identifiers, such as AoR.  

     

    Henry


----------------------------------------------------------------------------

    From: Wei Gengyu [mailto:weigengyu@vip.sina.com] 
    Sent: Sunday, December 16, 2007 5:25 AM
    To: P2PSIP Mailing List
    Subject: Fw: [P2PSIP] Re: HIP pros and cons

     

     

    ----- Original Message ----- 

    From: Wei Gengyu 

    To: jeffrey.m.ahrenholz@boeing.com ; spencer@mcsr-labs.org ; Philip Matthews 

    Cc: P2PSIP Mailing List 

    Sent: Saturday, December 15, 2007 10:25 AM

    Subject: Re: [P2PSIP] Re: HIP pros and cons

     

    Jeff,Spencer, and Philip, 

     

    First, thank you all for your correction.

     

    HIP might work well as RFC4423 defined.

     

    My problem is when HIP is used at the application layer, 

    or using the same algorithm to generate Peer ID. 

     

    If HIP-like algorithm is used in the overlay while HIP is used between network layer and transport layer,

    the Peer ID will share the same name space with Host ID.

    For rfc4423, when a node have multiple Host IDs, they only cost memory spaces a little.

    If one host are permited to have multiple Peer IDs that happen to belong to one overlay, 

    it would incur potential risks to the P2PSIP overlay.

     

    And it seems not be capable to tackle this case in RVS of HIP. 

    Is there something wrong?

     

    Regars,

     

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