Re: [p2pi] Updated charter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [p2pi] Updated charter



This looks good to me.  Thank you for listening.


On Jul 21, 2008, at 10:10 AM, Vijay K. Gurbani wrote:

Folks: Enrico and I have updated the charter to reflect the caching
discussion we have had on the list over the past few days.

The updated charter is available at
 http://alto.tilab.com/docs/charter.txt

We've added the last bullet list -- reproduce here -- based
on the list discussion:

- A discovery mechanism for locating nearby hosts the querying node
 may not be aware of.  In certain P2P networks, hosts operating caches
 may be able to fulfill the node's needs as well as keep the traffic
 between peers localized.  In VoIP networks, nearby hosts operating
 relays may effectively be discovered to aid a VoIP client in
 establishing multimedia communications.  It is anticipated that
 if existing resource discovery mechanisms are sufficient to suit
 this purpose, then the WG will produce one or more documents
 describing how these discovery mechanisms may be used to
 effectively find the peers.  The discovery mechanism can be
 executed in the clients as well as in the oracle.  To allow
 clients that prefer the oracle to provide such information, the
 WG will produce extensions to the oracle signaling protocol to
 enable the peer or client to transfer the desired properties
 to the oracle for subsequent lookups.

Comments on it will be welcome.

Thanks,

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg at {alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs
_______________________________________________
p2pi mailing list
p2pi at ietf.org
https://www.ietf.org/mailman/listinfo/p2pi

--
Stanislav Shalunov



_______________________________________________
p2pi mailing list
p2pi at ietf.org
https://www.ietf.org/mailman/listinfo/p2pi



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.