Well, the specification could be abstracted to remove the mention of the
B2BUA while still having the same effect. It would have to say something
about a UAS should send a 199 if it knows the dialog will be terminated
before it can send the final response. But I think we would still need
to include an example of a B2BUA in order for anybody to have a clue
what we were talking about.
Paul
Juha Heinanen wrote:
> Christer Holmberg writes:
>
> > 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.
> >
> > We could of course say something like:
> >
> > "UAS, when part of a B2BUA"
>
> according to the B2BUA definition:
>
> Since it is a concatenation of a UAC and
> UAS, no explicit definitions are needed for its behavior.
>
> this means that there is no need to say anything special about 199
> either. b2bus in terms of protocol specification, is just an uas like
> any other.
>
> -- 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
