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

["Brett Tate" <brett@broadsoft.com>]

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