RE: [Sipping] Possible Solution to HERFP

Phone rings, then somehow call is aborted.

I think it is a common scenario.

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of Rohan Mahy
> Sent: Saturday, July 09, 2005 03:01
> To: Jeroen van Bemmel
> Cc: Rohan Mahy; 'sipping' WG
> Subject: Re: [Sipping] Possible Solution to HERFP
> 
> 
> 
> On Jul 9, 2005, at 2:10, Jeroen van Bemmel wrote:
> 
> > Hi Rohan,
> >
> > Section 3 picture at the end: what happens if UAS1 sends some
> > provisional response (with a to-tag) before sending the 415?
> 
> Why would UAS1 send any provisional response (other than a 
> 100 Trying) 
> before figuring out there was an error?  I've never seen an 
> implementation do this, and the spec is pretty clear that you 
> immediately send these error before you get the the processing stage 
> where you would normally send a 18x.
> 
> > If the proxy generates a to-tag of its own for the 130, wouldn't the
> > UAC get confused?
> 
> are you asking this in general, or only after the UAS sent its own 
> to-tag?
> 
> thanks,
> -rohan
> 
> > Jeroen
> >
> > ----- Original Message ----- From: "Rohan Mahy" <rohan@ekabal.com>
> > To: "'sipping' WG" <sipping@ietf.org>
> > Cc: "Rohan Mahy" <rohan@ekabal.com>
> > Sent: Saturday, July 09, 2005 4:41 AM
> > Subject: [Sipping] Possible Solution to HERFP
> >
> >
> >> Hi Folks,
> >>
> >> I just submitted a new individual I-D that describes a possible
> >> solution to the Heterogeneous Error Response Forking 
> Protocol.  Until 
> >>  it appears in the archives, you can find it here:
> >>
> >> 
> https://scm.sipfoundry.org/rep/ietf-drafts/rohan/herf-fix/draft-mahy-
> >> sipping-herfp-fix-00.txt
> >> 
> https://scm.sipfoundry.org/rep/ietf-drafts/rohan/herf-fix/draft-mahy- 
> >> sipping-herfp-fix-00.html
> >>
> >> thanks,
> >> -rohan
> >> (as an individual)
> >>
> >>
> >> _______________________________________________
> >> 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
> 
> 

_______________________________________________
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