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

"DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com> Sun, 02 December 2007 21:28 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 1IywML-0006KV-KC; Sun, 02 Dec 2007 16:28:17 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IywMK-0006Jp-F2 for sip-confirm+ok@megatron.ietf.org; Sun, 02 Dec 2007 16:28:16 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IywMK-0006IR-41 for sip@ietf.org; Sun, 02 Dec 2007 16:28:16 -0500
Received: from ihemail4.lucent.com ([135.245.0.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IywMH-0001U7-Ec for sip@ietf.org; Sun, 02 Dec 2007 16:28:13 -0500
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id lB2LS62F004691; Sun, 2 Dec 2007 15:28:10 -0600 (CST)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 2 Dec 2007 15:28:07 -0600
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 2 Dec 2007 22:28:05 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Comments on draft-kaplan-sip-info-events-00
Date: Sun, 02 Dec 2007 22:28:04 +0100
Message-ID: <5D1A7985295922448D5550C94DE29180019B77BE@DEEXC1U01.de.lucent.com>
In-Reply-To: <4751B684.7060603@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Comments on draft-kaplan-sip-info-events-00
Thread-Index: Acg0UMMcw5pBr7DHT1SOwTH56E2kzQA2TgTw
References: <5D1A7985295922448D5550C94DE29180019B7775@DEEXC1U01.de.lucent.com> <4751B684.7060603@cisco.com>
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
X-OriginalArrivalTime: 02 Dec 2007 21:28:05.0655 (UTC) FILETIME=[39E95270:01C8352A]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: sip@ietf.org
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

Working backwards through my mailbox, and I guess I should have read this first.

Yes, what I had in mind was the non-delivery of packets, e.g. for the reason of non-sequential delivery.

SIP will not tell you you have missed any packets in this case.

Regards

Keith 

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: Saturday, December 01, 2007 7: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.
> 
> 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