Re: [Sip] Review of draft-ietf-speechsc-mrcpv2-15

Paul Kyzivat <pkyzivat@cisco.com> Tue, 08 January 2008 17: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 1JCI0a-0005gM-GU; Tue, 08 Jan 2008 12:13:00 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCI0Y-0005fn-Gt for sip-confirm+ok@megatron.ietf.org; Tue, 08 Jan 2008 12:12:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCI0X-0005fQ-EB; Tue, 08 Jan 2008 12:12:57 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCI0U-0004Bj-Vc; Tue, 08 Jan 2008 12:12:57 -0500
X-IronPort-AV: E=Sophos;i="4.24,258,1196658000"; d="scan'208";a="82700040"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 08 Jan 2008 12:12:54 -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 m08HCsa5023261; Tue, 8 Jan 2008 12:12:54 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m08HCOqA022700; Tue, 8 Jan 2008 17:12:54 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 8 Jan 2008 12:12:48 -0500
Received: from [161.44.174.128] ([161.44.174.128]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 8 Jan 2008 12:12:48 -0500
Message-ID: <4783AF11.9030406@cisco.com>
Date: Tue, 08 Jan 2008 12:12:49 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Subject: Re: [Sip] Review of draft-ietf-speechsc-mrcpv2-15
References: <478396EF.3090502@alcatel-lucent.com>
In-Reply-To: <478396EF.3090502@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jan 2008 17:12:48.0144 (UTC) FILETIME=[B13F6100:01C85219]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1259; t=1199812374; x=1200676374; 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]=20Review=20of=20draft-ietf-speech sc-mrcpv2-15 |Sender:=20 |To:=20=22Vijay=20K.=20Gurbani=22=20<vkg@alcatel-lucent.com >; bh=UCtKtK0nNofSnkxkkIES1fcmqPxXZ6/RikTWjhmg1vI=; b=ZtOm8gTe+uWE7rrQna4eyu6UNFzr0f5XnDfAzlnXCVchX2OwK8GaLBgHX/ oaDP5BtpziTGrnvckHvpypNJBSMhvDQvLGwUiNI2/01kEEaJfm/GxesxTCOH 8j9m9ftd8q;
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: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: dburnett@voxeo.com, IETF SIP List <sip@ietf.org>, sarvi@cisco.com, speechsc-chairs@tools.ietf.org, speechsc@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

Vijay,

A very thorough review. I have one comment on it, below.

	Thanks,
	Paul

Vijay K. Gurbani wrote:
> Hi:
> 
> The following is a review of draft-ietf-speechsc-mrcpv2-15 with
> emphasis on S1-S5, S12 and S14.  There are a few general comments
> first; the rest of the comments follow in linear fashion with respect
> to the sections enumerated above.

[snip]

>  4. In SIP, when a server responds with an affirmative response,
>   it always adds a tag parameter to the From header. 

Don't you mean To: header?

The initial INVITE should have a From-tag and the response should 
contain that and a To-tag. All subsequent requests and responses in the 
dialog should have both.

>   In the call
>   flow on page 16, the From header of the 200 OK does not contain
>   a tag parameter, it must.  Interestingly enough, the subsequent
>   ACK request contains the tag in the From parameter (as indeed it
>   should.)  Please add a tag parameter to the From header in the
>   200 OK, and ensure that it matches the one in the ACK request.
>   The tags are maintained for the duration of the lifetime of that
>   dialog.
> 
>   Thus, in the re-INV that starts at the bottom of page 16, the
>   From tag must be maintained.


_______________________________________________
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