Re: [Sip] Inadequate Requirements for draft-ietf-sip-199-00

["DRAGE, Keith \(Keith\)" <drage at alcatel-lucent.com>]

(As WG cochair)

The agreement in the SIPPING group where this was discussed was that we were not going to solve the HERPF problem. I think you will find a number of mails in the SIPPING archive confirming this.

It would be useful to identify and correct any text that you believe implies that the HERPF problem is to be solved.

Outside the HERPF problem I have no objection to clarifying the requirements and use cases. Please note that supposedly the SIPPING WG has already regarded these as complete. I would like to see clarification rather than feature creep.

Regards

Keith

> -----Original Message-----
> From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] On 
> Behalf Of Christer Holmberg
> Sent: Monday, August 04, 2008 9:29 PM
> To: Francois Audet; sip at ietf.org
> Subject: Re: [Sip] Inadequate Requirements for draft-ietf-sip-199-00
> 
> 
> Hi Francois,
> 
> As was agreed during the "requirements phase", we are not 
> going to solve the HERPF problem as part of this task. Nobody 
> objected to that. 
> 
> It was agreed that the scope is to only be able to indicate 
> that the early dialog has been terminated.
> 
> I have tried to explain different kind of "resources" for 
> which the mechanism could be useful. 
> 
> If you want to start a separate work item in order to solve 
> (with or without using 199) other problems you are free to 
> propose such work :) 
> 
> Regards,
> 
> Christer
> 
> 
> 
> -----Alkuperäinen viesti-----
> Lähettäjä: Francois Audet [mailto:audet at nortel.com]
> Lähetetty: ma 4.8.2008 22:17
> Vastaanottaja: sip at ietf.org
> Kopio: Christer Holmberg
> Aihe: Inadequate Requirements for draft-ietf-sip-199-00
>  
> I believe that the Requirents section for this draft is 
> completely inadequate.
>  
> The only material in section 3 is the following:
> 
> 	REQ 1: It must be possible to indicate to the UAC that 
> an early dialog has been 
> 	terminated before a final response is sent.
> 
> This is almost as good as "REQ: It must be possible to do 
> whatever this draft says".
> 
> This draft must really explain what it is trying to achieve. 
> The Introduction has a bunch of text that describes what 
> looks and smells exactly like the HERFP problem.
> 
> In Dublin, it was stated that this draft does not attempt to 
> solve the HERFP problem. If that is the case, then I am 
> completely baffled by what exactly is it trying to solve. 
> Yes, there is a little bit of wording about the need to 
> "release resources" (whatever that means), but I find it a 
> little bit hard to swallow that we need new protocol for that.
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors at cs.columbia.edu for questions on current sip 
> Use sipping at ietf.org 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 sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip