RE: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt

Just to clarify what I was trying to say.

A 486 inside a 302 inside a History-Info is also what I was refering to.

I guess there are still some issues about Reason not being explicitely 
allowed in a response today (as John was pointing out).

Regardless, it is indeed sort of confusing, but not the first time we
come up with
something arcane and confusing :^) I'm not necessarily opposing to that,
although I do doubt that it will be practical (i.e., that it will work
in 
real life). It might be be interesting for an "1001 SIP hacks" book
however :^)

My issue was not that. 

My issue is when the endpoint is "faking" the 486 because there was
never any 
486 received. I think a GW (or B2BUA or SIP phone) sending a 302 with an
embedded
fake 486 just to make the other end believe (through History-Info or
not) that
it was Call Forward Busy is an abuse of the protocol.

If there is a 486 Reason in there, it should be because there was a 486
received.

Cheers.

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of Dean Willis
> Sent: Tuesday, October 18, 2005 13:01
> To: Audet, Francois [SC100:9T51:EXCH]
> Cc: sipping; Paul Kyzivat; Elwell,John; Michael Hammer (mhammer)
> Subject: Re: [Sipping] Re: 
> draft-elwell-sipping-service-retargeting-00.txt
> 
> 
> 
> On Oct 17, 2005, at 5:47 PM, Francois Audet wrote:
> 
> > You mean adding a Reason of 486 inside 302????
> >
> > That seems highly confusing to me.
> 
> That's more or less what I think I proposed, except I buried it in a  
> History-Info header field.
> 
> One of the things that puzzles me about H-I is that while the RFC  
> allows use of H-I in 302 responses, it doesn't talk about it in any  
> great detail.
> 
> It would be very nice to have an H-I use-cases draft with some good  
> examples.
> 
> --
> Dean
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 
> 

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