RE: [Sip] sip-session-timer-11: why explicitly impose proxy restrictions on all the b2bua's

["Rosen, Brian" <Brian.Rosen@marconi.com>]

I thought it was because the two sessions the B2BUA bridges ought
to be considered one session wrt the session timer.  If one side
dies, the other one needs to be cleaned up.

That being said, if one side can support session timer, and the
other can't, the B2BUA could, if it was smart enough, maintain
the session timer on the one side, and clean up the other side
on failure.  It couldn't detect failure of the non-session-timer
side of course.

I was about to release -12, with only minor updates.  I guess
I'll let this thread play out before I release it.  I could
soften the text pretty easily.

I personally liked the fact that B2BUA behavior was discussed.

Brian

> -----Original Message-----
> From: Brett Tate [mailto:brett@broadsoft.com]
> Sent: Thursday, September 04, 2003 3:49 PM
> To: jdrosen@dynamicsoft.com
> Cc: sip-ietf (E-mail)
> Subject: [Sip] sip-session-timer-11: why explicitly impose proxy
> restrictions on all the b2bua's
> 
> 
> Why does draft-ietf-sip-session-timer-11 
> explicitly impose proxy related restrictions 
> on all the B2BUA's?
> 
> I agree that some of the proxy concepts are 
> good recommendations for some types of B2BUA's; 
> however they definitely do not apply to all 
> types of B2BUA's.  
> 
> And in general, I am surprised to see
> any draft explicitly requiring a B2BUA to act 
> like a proxy.  Some B2BUA's act completely like
> a UA; others act mostly like a proxy; and others
> act at various degrees between a proxy and UA.
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip