Subject: Re: [P2PSIP] Comments on draft-baset-p2psip-p2pcommon-01 Attn: Baset/Schulzrinne

From: [email-masked]
Date: Sat, 14 Apr 2007 08:40:18 +0530

Hello Baset/Schulzrinne.

Thanks for your response for my comments.

I have few more comments. Please read below.

When would be the updated draft available ?.

I would like to contribute to this draft. Let me know if  i could

be any help for you.

Thanks & Regards,

Anuroop.

Comments:

1. There is a "Response-Code" parameter in Join Response and Insert Response messages.
The common header has the provision to send the response code as well. Why is
this explicity response code required?. Also there is no TLV object defined for
Response-Code. My understanding is that this parameter shall be removed from
Join Response and Insert Response as the common header would suffice.

2. The Replicate message should have "Expires" field as well. Since the resouces shall
be inserted into peer with as associated "Expires" field, when these resources are
replicated, the associated expires should also get transfered to the Peer who is
owning this resources.

3. The state machine is written only from the perspective of a Peer sending out requests.
A Peer can receive requests from other Peer, which is not addressed in this state machine.
New state should be introduced to indicate the "received request" from other peer. when
a Peer receives a request, as part of processing, it may send the request to the DHT
layer with in the node. Then it should change the state to "Req_Recv" state. On receving
the response from DHT Layer, it shall respond to the other peer, and then move to
sucess or failure state.

4. The protocol should clearly specifiy whether the encoding should be done in big/little
endian format. In the absence of such a statement, the default i think is big endian.

*****Aricent-Unclassified *****=

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of
the individual to whom it is addressed. It may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended. If you have received this message in error,
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information transmitted by this email including damage from virus."

_______________________________________________
P2PSIP mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/p2psip