On Mar 3, 2008, at 5:15 AM, Song Yongchao wrote: > Please see inline. > >>> * Subsection for the client protocol: The proposals for the >>> client protocol, one of which (draft-pascual-p2psip-clients) is >>> based on >>> P2PP anyway, and should be merged here as well. >>> >> >> No separate client protocol is required. What features of a client >> protocol do you believe are not met by the base protocol? > > You can find the features of client in draft-pascual-p2psip- > clients, only > when you are clear about that, you will know what features are not > met with > Reload-03. No matter whether we need a separate client protocol or a > subsection for client protocol, those features should be discussed > first. I > support Victor to make a presentation and discussion of "clients" > at the > meeting. >
Song, Again, what protocol features do you believe are not supported by reload-03? The source routing and via list allow a client to be reached via the peer protocol from anywhere in the overlay. So the reload-03 protocol is able to exchange messages both between the client and the peer it is using, but also between any other peer (or client) attached anywhere in the overlay with a client behind a peer. In general, I think this framework is sufficient to meet the messaging needs of the various client proposals. (It doesn't propose the necessary parts to implement them, but with appropriate definition of method types and their semantics, the necessary framework from the routing layer is there.) So, as far as the general discussions in section 4, sure, reload-03 supports clients. Of the two specific functions proposed in section 5: - storage provided by clients: You could certainly build this functionality on top of reload-03, with the peer exchanging STORE/ FETCH messages with its clients (or through other mechanisms). So the underlying routing mechanism is there. But at ietf-70, the wg voted to not focus on solving this problem in the immediate future. - p2p relay: I'm not completely clear on this section. If it is a proposal to have clients able to act as TURN servers, there is no restriction in reload-03 that the turn servers are peers, clients, or even members of the overlay. So I don't think there's any issue here. Bruce _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
