Re: [Sip] SIPit21: SDP in a 200OK when using 100rel

Dean Willis <dean.willis@softarmor.com> Thu, 22 November 2007 01:02 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 1Iv0Sz-0003LD-CN; Wed, 21 Nov 2007 20:02:53 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Iv0Sy-0003L2-G6 for sip-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 20:02:52 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iv0Sy-0003Ku-32 for sip@ietf.org; Wed, 21 Nov 2007 20:02:52 -0500
Received: from nylon.softarmor.com ([66.135.38.164]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iv0Sx-00040E-MT for sip@ietf.org; Wed, 21 Nov 2007 20:02:52 -0500
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may be forged)) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id lAM12m9n006592 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 21 Nov 2007 19:02:50 -0600
In-Reply-To: <4744BC10.40301@cisco.com>
References: <8983EC086A9D954BA74D9763E853CF3E0437EE12@xmb-rtp-215.amer.cisco.com> <C8B2F765-1502-46B0-A5C5-371CCE9B2A92@nostrum.com> <32B7DC57-3B9C-43B9-A23E-D4C09F263B6E@softarmor.com> <650EED83-56EA-4C77-B2CC-D8FF5AE0ECC2@nostrum.com> <48A4B771-1AD7-4CCD-BC52-230CE9014DFC@softarmor.com> <4744BC10.40301@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <309C3407-D4BC-4011-BEBE-5E522D338174@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] SIPit21: SDP in a 200OK when using 100rel
Date: Wed, 21 Nov 2007 19:02:40 -0600
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: "Sanjay Sinha (sanjsinh)" <sanjsinh@cisco.com>, sip List <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 Nov 21, 2007, at 5:15 PM, Paul Kyzivat wrote:
>
> That may seem simple and harmless. But it gets ugly when additional  
> offer/answers happen:
>
>   Alice               Bob
>     |  INVITE offer1   |
>     |----------------->|
>     |  183 answer1     |
>     |<-----------------|
>     |  PRACK           |
>     |----------------->|
>     |  200 PRACK       |
>     |<-----------------|
>     |  UPDATE offer2   |
>     |<-----------------|
>     |  200 UP answer2  |
>     |<-----------------|
>     |  200 IN SDP?     |
>     |<-----------------|
>
> Now what should be in the 200 for the invite?
>
> Its better to do what is already required - send no SDP in the 200  
> for the invite.

Huh. Is it actually ok to send a 200 OK for the UPDATE before sending  
the 200 OK for the INVITE? That seems like a race condition from hell.

If it's OK only because you can claim the INVITE's O/A sequence  
completed before the UPDATE was sent, then we're making the SIP state  
machine dependent on the O/A model, and that's just wrong.

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