Hi, As [draft-ietf-p2psip-base-03] said: “RELOAD is designed to support a variety of applications, including P2P multimedia communications with the Session Initiation Protocol [I-D.ietf-p2psip-sip]. RELOAD allows the definition of new application usages. ” I think this draft has given an example following this guideline. There is still one important issue to be badly noticed and discussed:
For RELOAD is “designed specifically to meet the requirements for a P2P protocol to support SIP” [draft-ietf-p2psip-base-03], it is applied to support content sharing in this draft, are there some specific requirements for content sharing usage that are too different from the SIP usage for RELOAD to support ? Or if you would make some extensions, which part needs extension and to what extent? I think this question would be general for all the P2P application usage which is inclined to use RELOAD. It is necessary to clarify the specific requirements, especially those are not supported well by current RELOAD. Regards Tao Ma 16th, July, 2009 Mobile Life New Media Lab, Beijing University of Posts and Telecommunications On Wed, Jul 1, 2009 at 9:16 AM, <shen.jiong at zte.com.cn> wrote: > > Hi all, > > We have submitted a draft on content sharing usage for RELOAD. It provides > the functionality of distributing and fetching shared content efficiently to > and from a P2P overlay network, which performs as Content Delivery Network > and is service insensitive. > > The draft can be found at > http://www.ietf.org/internet-drafts/draft-shen-p2psip-content-sharing-00.txt. > Comments are welcome. > > > Thanks, > Jiong > > > -------------------------------------------------------- >
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
