[p2p-sip] My notes on draft-willis-p2psip-concepts-01

eunsoo at research.panasonic.com (Eunsoo Shim) Thu, 28 September 2006 14:38 UTC

From: "eunsoo at research.panasonic.com"
Date: Thu, 28 Sep 2006 10:38:13 -0400
Subject: [p2p-sip] My notes on draft-willis-p2psip-concepts-01
In-Reply-To: <8b2769930609280617y3a042901sfb8829d2217ebd65@mail.gmail.com>
References: <053b01c6d2b7$ed3f13e0$0500a8c0@china.huawei.com> <85AC9C32-24BE-4E39-8545-C96182959B86@softarmor.com> <080601c6e26f$32492720$0300a8c0@china.huawei.com> <451ADD5F.6010206@research.panasonic.com> <8b2769930609271355q3c7985eeq28406df4bf5041ac@mail.gmail.com> <09db01c6e27c$af4a44e0$0300a8c0@china.huawei.com> <8b2769930609271545i142fe228pe6b2b25107a48394@mail.gmail.com> <451B47C4.5070000@research.panasonic.com> <0abb01c6e2fb$5e12b1f0$0300a8c0@china.huawei.com> <8b2769930609280617y3a042901sfb8829d2217ebd65@mail.gmail.com>
Message-ID: <451BDE55.5070402@research.panasonic.com>

One can put the Proxy functionality and Registrar functionality into a
single entity.
They can be separate, too.
Figure 3 and 4 in draft-shim-sipping-p2p-arch-00.txt show how Registrar
Peer/Client and Proxy Peer/Client can enable interoperation between a UA
Peer/Client and CS SIP UAs.
According to the terminology style of draft-willis-p2psip-concepts-01,
P2P Proxy in the first draft is Proxy Peer/Client and P2P Registrar is
Registrar Peer/Client.

Thanks.

Eunsoo

David A. Bryan wrote:
> I was thinking that an adaptor might be an entity that had more than
> just proxy -- we also specify a registrar in that same section. For a
> true C/S node to work, it would need to be able to do lookups and
> registration.
> 
> We need to make some clarifications to the terminology draft.
> 
> David
> 
> On 9/28/06, Spencer Dawkins <spencer at mcsr-labs.org> wrote:
>> ... I'm still working on precision here ...
>>
>> I may have misunderstood this point in the original draft, but I thought the
>> Proxy Peer was a *SIP* Proxy Peer - roughly, providing what I called
>> "Interaction with CS-SIP" in http://www.p2psip.org/P2PUseCases.php.
>>
>> But, looking back at draft-willis-p2psip-concepts-01 more closely, I find
>>
>>    6.  Proxy: A peer or client that accepts SIP requests, resolves the
>>        next hop or hops using the routing information of the P2PSIP
>>        Overlay, and passes the request on towards the next hop.
>>
>> If the Proxy Peer is a *P2PSIP* Proxy Peer, that's fine - but what should I
>> call the node providing "Interaction with CS-SIP"?
>>
>> Thanks,
>>
>> Spencer
>>
>>
>>> Doesn't the Proxy Peer do a similar function?
>>> We have Proxy Peer in the diagram(s).
>>> Thanks.
>>>
>>> Eunsoo
>>>
>>> David A. Bryan wrote:
>>>
>>>> I don't believe that adaptor node made it into the terminology draft,
>>>> but I'm fine with using it as a label if others are comfortable. (it
>>>> just never happened to come up in that discussion).
>>>>
>>>> David
>> _______________________________________________
>> p2p-sip mailing list
>> p2p-sip at cs.columbia.edu
>> https://lists.cs.columbia.edu/cucslists/listinfo/p2p-sip
>>
> _______________________________________________
> p2p-sip mailing list
> p2p-sip at cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/p2p-sip