Cullen Jennings wrote:
On Aug 11, 2006, at 10:49 PM, <Erkki.Koivusalo at nokia.com>
<Erkki.Koivusalo at nokia.com> wrote:
The UA SHOULD add a Proxy-Require header field with the
value "sip-stun" to its REGISTER request. When the UA
receives 200 OK with Supported: Outbound it can be sure
that the next hop will support STUN keepalives.
The proxy MUST remove the "sip-stun" value from the
Proxy-Require header field and then remove the header
if no values remain before forwarding the request to
the next hop.
My mistake - it was some of the other stuff that was looking more
complicated. I agree this is very easy implement. I also think Bob's
proposal is very easy to implement - if the outbound proxy came from
DHCP or was manually configured on the UA, then do an OPTIONS message
first.
Yay!
How about we say:
Either do 1 or 2 below, then always do 3:
1) Probe the proxy with OPTIONS to verify that it supports STUN
or
2) Use a Proxy-Require as above
and
3) if you don't get a STUN response, stop using STUN on this target
(and I'd be happy to see this in STUN, not Outbound!)
--
Dean
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip