Hi Brett-
Thanks for responding. Comments/questions inline.
Placing the ephemeral port within the Contact does not work when the TCP is
reclaimed unless the device actually listens for new connections on the same
port.
I'm just trying to get it to use the existing connection, effectively
making the Contact header irrelevant (since no new connections would be
needed). Setting the Contact header to the ephemeral port would simply
trick the stack I'm using into realizing it already has the connection.
The outbound draft provides the complete solution for the outbound
connection reuse situation.
If you don't like the outbound draft, the reuse draft can be used. However
the reuse draft does not provide the mechanism to ensure the TCP connection
remains open or is soon recreated.
Right. It doesn't use STUN to keep the connection open, that's what
you're saying? I have to look more closely at the reuse draft. It may
be more what I want, although it looks like it also requires GRUU. I
like the outbound and GRUU drafts fine, but I just don't see why GRUU is
necessary for this purpose, and I'm reluctant to make such a large
change for a problem that appears simpler to me. In particular, GRUU is
meant to solve specific cases where the straight contact header is not
sufficient (refer and conferencing I think). I don't see why the
connection re-use issue is somehow conflated with this.
Maybe you can explain to me why these drafts require GRUU? What am I
missing?
Thanks so much.
-Adam
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
