Hi Juha,
Chapter 6 of RFC3261 DOES define Back-to-Back User Agent.
Back-to-Back User Agent: A back-to-back user agent (B2BUA) is a
logical entity that receives a request and processes it as a
user agent server (UAS). In order to determine how the request
should be answered, it acts as a user agent client (UAC) and
generates requests. Unlike a proxy server, it maintains dialog
state and must participate in all requests sent on the dialogs
it has established. Since it is a concatenation of a UAC and
UAS, no explicit definitions are needed for its behavior.
We could of course say something like:
"UAS, when part of a B2BUA"
Regards,
Christer
________________________________
From: [EMAIL PROTECTED] on behalf of Juha Heinanen
Sent: Sat 14/06/2008 08:59
To: Paul Kyzivat
Cc: [email protected]; Francois Audet
Subject: Re: [Sip] Draft submission: draft-ietf-sip-199-00
Paul Kyzivat writes:
> Seems to me we need a pretty strong SHOULD NOT here, with the B2BUA
> being the known exception.
i don't agree excepting B2BUA for anything as long as b2bua has been
officially added and defined as a new sip related entity in addition to
UAs, registrars and proxies. once that is done, then every sip
specification has to state if/when ua procedures also apply to these
B2BUAs.
-- juha
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip