[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Sip] B2BUA & Max-Forwards



Hi,

I think your confusion comes from mixing two email threads; the first statement in context says if a specific B2BUA demonstrates header transparency it doesn't change headers; the second statement is about B2BUAs in general and says they can do whatever they want (without commenting on the desirability of their actions).

Max-Forwards probably are an important case for your particular application, in general they may not be required (e.g. routing to an element you can guarantee not to proxy).

Your comment on Max-Forwards highlights well the difficulties faced in defining a B2BUA more specifically than the definition in 3261.

James 

> -----Original Message-----
> From: Pete Cordell [mailto:pete@tech-know-ware.com]
> Sent: 05 December 2002 12:10
> To: Dean Willis; sip@ietf.org
> Subject: Re: [Sip] B2BUA & Max-Forwards
> 
> 
> Dean,
> 
> Firstly, your statement that "The B2BUA doesn't change 
> headers that transit
> it." seems inconsistent with the statement "It does the same 
> thing as ...
> ANY 500-pound gorilla does".  I don't understand.
> 
> Secondly, I think max-forwards is a special case.  It is 
> important for the
> protection of SIP systems as it prevents loops.
> 
> Indeed, there is a major difference between a UAS and a B2BUA 
> and that is
> that the former terminates a request, and the latter 
> terminates a request
> AND ALSO forwards an associated request (or more).  The impact of this
> difference should be covered in the spec in the interests of 
> protecting
> other SIP systems.
> 
> Pete.
> 
> ----- Original Message -----
> From: "Dean Willis" <dean.willis@softarmor.com>
> To: "'Pete Cordell'" <pete@tech-know-ware.com>; <sip@ietf.org>
> Sent: 05 December 2002 01:23
> Subject: RE: [Sip] B2BUA & Max-Forwards
> 
> 
> > > One issue that the recent B2BUA discussion has raised in my
> > > mind is what a B2BUA (whatever its decided that should be)
> > > should do with Max-Forwards.
> >
> > It does the same thing as it does with any other header or 
> body part,
> > which is the same thing that ANY 500-pound gorilla does to 
> somebody's
> > body parts -- whatever it wants.
> >
> > What you're asking is "what is the transparency of this node with
> > respect to max-forwards", which is "#4 -- Header Transaprency" in my
> > top-10 list. The specification of a back-to-back user agent doesn't
> > mandate any level of transparency on this or any other header.
> >
> > --
> > 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@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
> 
_______________________________________________
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