IETF Logo Mail Archive

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

Dale.Worley@comcast.net Mon, 03 December 2007 20:36 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 1IzI1f-0006GX-S3; Mon, 03 Dec 2007 15:36:23 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IzI1d-0006AU-KR for sip-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 15:36:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzI1d-00064j-6r for sip@ietf.org; Mon, 03 Dec 2007 15:36:21 -0500
Received: from qmta10.westchester.pa.mail.comcast.net ([76.96.62.17]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IzI1c-0005tW-Lv for sip@ietf.org; Mon, 03 Dec 2007 15:36:20 -0500
Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA10.westchester.pa.mail.comcast.net with comcast id LLLg1Y00H0EZKEL0501a00; Mon, 03 Dec 2007 20:36:20 +0000
Received: from dragon.ariadne.com ([24.34.79.42]) by OMTA01.westchester.pa.mail.comcast.net with comcast id LLcK1Y00E0umElk0300000; Mon, 03 Dec 2007 20:36:20 +0000
X-Authority-Analysis: v=1.0 c=1 a=ebA3azEne4CeaAg7KFIA:9 a=VDwZJIVAKXa1OI-c68xGi9MuPxcA:4 a=0MAqpqVwYqEA:10 a=8y7tGHue6YMA:10
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id lB3KaJTc006342 for <sip@ietf.org>; Mon, 3 Dec 2007 15:36:19 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id lB3KaJB6006338; Mon, 3 Dec 2007 15:36:19 -0500
Date: Mon, 03 Dec 2007 15:36:19 -0500
Message-Id: <200712032036.lB3KaJB6006338@dragon.ariadne.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <47544E62.2030808@nostrum.com> (adam@nostrum.com)
Subject: Re: [Sip] Comments on draft-kaplan-sip-info-events-00
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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

   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.)

Dale


_______________________________________________
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