Re: [splices] SIP INVOKE method

Paul Kyzivat <pkyzivat@cisco.com> Tue, 17 May 2011 19:08 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: splices@ietfa.amsl.com
Delivered-To: splices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51846E0780 for <splices@ietfa.amsl.com>; Tue, 17 May 2011 12:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.547
X-Spam-Level:
X-Spam-Status: No, score=-109.547 tagged_above=-999 required=5 tests=[AWL=-1.052, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LWpm+SeOR7nD for <splices@ietfa.amsl.com>; Tue, 17 May 2011 12:08:52 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (unknown [64.102.122.149]) by ietfa.amsl.com (Postfix) with ESMTP id 999E3E0748 for <splices@ietf.org>; Tue, 17 May 2011 12:08:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=359; q=dns/txt; s=iport; t=1305659332; x=1306868932; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=IAGrCoe/a/2eYmHZm7vgwT43Tq5Kp4EDI92ssn+7agU=; b=UsK0ZMob4Bj6rf3ohehlyXh43oBvR52K6R9iVCHSpc3zvauwpsticpqV Fh90cpaeSFVHIhgRQgkEH5dU7P8sq7HYWgv1YcKXUbcN+Xz+orFAyrnLC bjd++6WhRlnwiwpo1yYV7azJFpEbjAGJBnAgr406hbhtsQwFnhUKdlEca U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AogIAPnG0k2tJV2d/2dsb2JhbACYEI4Nd4hwoEOeGIYZBJARhC+KYg
X-IronPort-AV: E=Sophos;i="4.65,226,1304294400"; d="scan'208";a="233776986"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rtp-iport-2.cisco.com with ESMTP; 17 May 2011 19:08:51 +0000
Received: from [161.44.174.124] (dhcp-161-44-174-124.cisco.com [161.44.174.124]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id p4HJ8lOP023032 for <splices@ietf.org>; Tue, 17 May 2011 19:08:47 GMT
Message-ID: <4DD2C7BF.1030000@cisco.com>
Date: Tue, 17 May 2011 15:08:47 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: splices@ietf.org
References: <6369CB70BFD88942B9705AC1E639A33822CBDA8EBF@DC-US1MBEX4.global.avaya.com> <BANLkTinLjrS3DocT=_MbnDrHdoTLs7RuhQ@mail.gmail.com> <6369CB70BFD88942B9705AC1E639A33822CBDA9548@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <6369CB70BFD88942B9705AC1E639A33822CBDA9548@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [splices] SIP INVOKE method
X-BeenThere: splices@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Loosely-coupled SIP Devices \(splices\) working group discussion list" <splices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/splices>, <mailto:splices-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/splices>
List-Post: <mailto:splices@ietf.org>
List-Help: <mailto:splices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/splices>, <mailto:splices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2011 19:08:53 -0000

On 5/17/2011 2:20 PM, Shekh-Yusef, Rifaat (Rifaat) wrote:

> Yes, and I have the following open question about these parameters:
> Should a separate header be defined for action parameters?

I can be convinced otherwise (by a good justification), but I'm inclined 
toward describing the action and any parameters in a body part.

	Thanks,
	Paul