My implementation agrees with Mr. Peng. There is no need for JP to use Ping to
find AP. Just send an Attach with a *Resource-ID* as destination which contains
_JP's own ID_ to the bootstrap node. Since this is a *Resource-ID*, it will be
routed to the responsible node, which is AP. AP's reply will be routed back to
JP to start the ICE check.
Did I mention it's a *Resource-ID*? :) It is the key to this join method.
Thanks
--Michael
On 10/24/2010 11:04 PM, [email protected] wrote:
I think JP is correct. The Node of JP is as Resource-ID in Attach. Before
Attaching, a Ping message is redundant.
There is the description above the second dirgram in the draft:
"It sends an Attach to the *Resource-IP* AP+1, which gets routed to NP."
"Resource-IP" should be "Resource-ID".
*Frederic-Philippe Metz <[email protected]>*
发件人: [email protected]
2010-10-23 15:31
收件人
[email protected]
抄送
主题
[P2PSIP] Clarification of initial attach procedure
Hi all,
I've got a question resp. page 123:
The first attach in the call flow diagram states JP as the
destination. I think it should be AP ? JP has got the node-id of AP
from a previous ping, right ? If that assumption is not right, the
attach to node-id JP will fail, because 5.5.1 states that the attach
to a node-id which isn't reached will fail.
Cheers,
Frédéric
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is
solely property of the sender's organization. This mail communication is
confidential. Recipients named above are obligated to maintain secrecy and are
not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify the originator of the
message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
