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

Dean Willis <dean.willis@softarmor.com> Mon, 03 December 2007 22:13 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 1IzJXi-0002xc-GA; Mon, 03 Dec 2007 17:13:34 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IzJXg-0002qi-SF for sip-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 17:13:32 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzJXg-0002nA-C5 for sip@ietf.org; Mon, 03 Dec 2007 17:13:32 -0500
Received: from nylon.softarmor.com ([66.135.38.164]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IzJXf-0001Gw-W2 for sip@ietf.org; Mon, 03 Dec 2007 17:13:32 -0500
Received: from [130.129.87.72] ([130.129.87.72]) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id lB3MDQUk018001 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 3 Dec 2007 16:13:28 -0600
In-Reply-To: <200712032036.lB3KaJB6006338@dragon.ariadne.com>
References: <5D1A7985295922448D5550C94DE29180019B7775@DEEXC1U01.de.lucent.com> <4751B684.7060603@cisco.com> <5D1A7985295922448D5550C94DE29180019B77BE@DEEXC1U01.de.lucent.com> <2B132E65-667C-4C0E-B21C-E3CEC3FBC748@softarmor.com> <47544E62.2030808@nostrum.com> <200712032036.lB3KaJB6006338@dragon.ariadne.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <FB3B915D-3EEF-41B3-B44D-F1FB70190F88@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Comments on draft-kaplan-sip-info-events-00
Date: Mon, 03 Dec 2007 16:13:15 -0600
To: Dale.Worley@comcast.net
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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

On Dec 3, 2007, at 2:36 PM, Dale.Worley@comcast.net wrote:

>    From: Adam Roach <adam@nostrum.com>
>
>    I had it in my head many years ago that overlapping NITs were  
> illegal
>    also, but I couldn't ever find any supporting text in RFCs. I  
> think it
>    was in some pre-publication versions of 2543-bis, but got pulled  
> out
>    before finalization.
>
> I think that overlapped transactions is a basic feature of SIP.  (The
> UAC has to be able to deal with the occasional 500 Out Of Order
> situation, of course.)

Yes, but just because the protocol can handle overlapped NITs doesn't  
mean the application should send them that way. If you have  
sequential data that needs to be delivered in order (for example,  
MESSAGE requests) you have to sequence the requests at the  
application level.

--
Dean


_______________________________________________
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