Re: [P2PSIP] Status of RELOAD

Bruce,

I appreciate the clarification and look forward to Reload-3. Just a 
reminder, in early December, Cullen and I had the following Q&A, which I 
hope to be formally defined in the upcoming draft.

Thanks

--Michael

On Nov 28, 2007, at 6:57 PM, Michael Chen wrote:
> I don't see where the protocol sends the originator's peer-ID. At the 
> end of section 4.1, it says the via list starts out empty and the 
> route list has the intermediate and destination peer IDs.  Say A wants 
> to reach C through B, then in the forwarding header sent by A, the 
> route-list contains [B, C], and the via list is empty.  Where does C 
> or B for that matter know the peer ID of A when it's time to send the 
> respond back?
>
> Should the via-list in the forwarding header sent by A contains the 
> peer ID of A?
Yes, we do need the A to get in the list,  but the ID is inserted by B. 
The logic behind this had to do with some security issues and logic 
about what B inserts. B actually inserts the peer it perceives the 
message came from. This helps with spoofing return routes by having 
responses go to where they came from. Sorry this email is brief, I will 
try and write a clearer one if this does make sense.

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip