IETF Logo Mail Archive

Re: [Sip] Comments on draft-kaplan-sip-info-events-00

Paul Kyzivat <pkyzivat@cisco.com> Sun, 02 December 2007 17:35 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iysic-0007S5-A2; Sun, 02 Dec 2007 12:35:02 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Iysib-0007Px-4Z for sip-confirm+ok@megatron.ietf.org; Sun, 02 Dec 2007 12:35:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iysia-0007OF-QS for sip@ietf.org; Sun, 02 Dec 2007 12:35:00 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IysiZ-0005Jy-Dp for sip@ietf.org; Sun, 02 Dec 2007 12:35:00 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 02 Dec 2007 12:34:59 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lB2HYxMp019179; Sun, 2 Dec 2007 12:34:59 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lB2HYxBa017392; Sun, 2 Dec 2007 17:34:59 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 2 Dec 2007 12:34:58 -0500
Received: from [10.86.241.240] ([10.86.241.240]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 2 Dec 2007 12:34:58 -0500
Message-ID: <4752ECC1.5020004@cisco.com>
Date: Sun, 02 Dec 2007 12:34:57 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "Sanjay Sinha (sanjsinh)" <sanjsinh@cisco.com>
Subject: Re: [Sip] Comments on draft-kaplan-sip-info-events-00
References: <8983EC086A9D954BA74D9763E853CF3E04468C35@xmb-rtp-215.amer.cisco.com>
In-Reply-To: <8983EC086A9D954BA74D9763E853CF3E04468C35@xmb-rtp-215.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Dec 2007 17:34:58.0321 (UTC) FILETIME=[A8CF8810:01C83509]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1800; t=1196616899; x=1197480899; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sip]=20Comments=20on=20draft-kaplan-sip-info-events- 00 |Sender:=20 |To:=20=22Sanjay=20Sinha=20(sanjsinh)=22=20<sanjsinh@cisco.com>; bh=5Do090fsiTnHCZ+LXu45nmGX6IP8XiAyPgqo1Eergos=; b=jR3Cjq3AOP/5pWM+wCXKyCQJgINrwCN0q/uMJp+Y1YWuFTqnHRVTF/g7CYd+/cJ11t2iEnPL F/Hi/kssQuQB65jhCUWF2o/SNTbPna5WAe4fWt/NKfDrc4bOx1em7L9a;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: sip@ietf.org, "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

I think iw will have to be a responsibility of the sending UA to 
serialize all things that need to travel via INFO.

	Paul

Sanjay Sinha (sanjsinh) wrote:
> Inline ...
> 
>> -----Original Message-----
>> From: Paul Kyzivat (pkyzivat) 
>> Sent: Saturday, December 01, 2007 2:31 PM
>> To: DRAGE, Keith (Keith)
>> Cc: sip@ietf.org
>> Subject: Re: [Sip] Comments on draft-kaplan-sip-info-events-00
>>
>> Keith,
>>
>> A comment about one of your points:
>>
>> DRAGE, Keith (Keith) wrote:
>>
>>> In particular, one area which needs to be covered is how the 
>> embedded 
>>> information tranfer caters for out of sequence delivery, given that 
>>> the carriage mechanism does not guarantee order of delivery in all 
>>> circumstances of SIP usage.
>> I'm wondering what you have in mind here.
>>
>> It is possible to send request R1 then send R2 before getting 
>> a response to R1. And then it is possible for R2 to arrive 
>> before R1, and in that case it will be accepted. But then, 
>> when R1 arrives there will be a CSeq error so it will be rejected.
> 
> But if the INFO is used for dtmf, the rejected request will be a problem
> as it will result in loss of digit information. So I think package type
> should define whether it is ok to send overlapping requests or not.
> 
> Sanjay
> 
>> The end result is that you can get *nondelivery* of a message, 
>> but not *out of order delivery*.
>>
>> 	Thanks,
>> 	Paul
>>
>>
>> _______________________________________________
>> 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

v2.23.0 | Report a Bug | By Email