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

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


Hi,

>>Well, I think the use-cases justifies the existing 
>>requirement. Do you want to have specific requirement for all 
>>the use-cases?
>
>Yes.

Again, I thought we normally use use-cases in order to justify the requirement(s). All use-cases justify the same requirement: being able to indicate that the early dialog has been terminated.

Regards,

Christer


_______________________________________________
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


g?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org



Hi,

>>Well, I think the use-cases justifies the existing 
>>requirement. Do you want to have specific requirement for all 
>>the use-cases?
>
>Yes.

Again, I thought we normally use use-cases in order to justify the requirement(s). All use-cases justify the same requirement: being able to indicate that the early dialog has been terminated.

Regards,

Christer


_______________________________________________
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