Re: [splices] SIP INVOKE method

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Wed, 18 May 2011 11:29 UTC

Return-Path: <rifatyu@avaya.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 D19AEE06B6 for <splices@ietfa.amsl.com>; Wed, 18 May 2011 04:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.432
X-Spam-Level:
X-Spam-Status: No, score=-3.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 DFP8zoVq4fL9 for <splices@ietfa.amsl.com>; Wed, 18 May 2011 04:29:34 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6BDE06A3 for <splices@ietf.org>; Wed, 18 May 2011 04:29:33 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiABAGSs003GmAcF/2dsb2JhbACXTI5Ld6xDAptOhhkElF2KRQ
X-IronPort-AV: E=Sophos;i="4.65,231,1304308800"; d="scan'208";a="280525994"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 May 2011 07:29:32 -0400
X-IronPort-AV: E=Sophos;i="4.65,231,1304308800"; d="scan'208";a="623263251"
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 May 2011 07:29:32 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Wed, 18 May 2011 07:29:32 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "splices@ietf.org" <splices@ietf.org>
Date: Wed, 18 May 2011 07:29:30 -0400
Thread-Topic: [splices] SIP INVOKE method
Thread-Index: AcwUxd4Jpp/zCEJrQRuyU21E2rS/BQAiF90w
Message-ID: <6369CB70BFD88942B9705AC1E639A33822CBE5C339@DC-US1MBEX4.global.avaya.com>
References: <6369CB70BFD88942B9705AC1E639A33822CBDA8EBF@DC-US1MBEX4.global.avaya.com> <BANLkTinLjrS3DocT=_MbnDrHdoTLs7RuhQ@mail.gmail.com> <6369CB70BFD88942B9705AC1E639A33822CBDA9548@DC-US1MBEX4.global.avaya.com> <4DD2C7BF.1030000@cisco.com>
In-Reply-To: <4DD2C7BF.1030000@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 18 May 2011 11:29:34 -0000

Hi Paul,

I think that the main reason for using Headers for actions and parameters is to allow for proxy applications on the call path to recognize the requested action, as some UAs might encrypt the body part.

Regards,
 Rifaat


> -----Original Message-----
> From: splices-bounces@ietf.org [mailto:splices-bounces@ietf.org] On Behalf Of
> Paul Kyzivat
> Sent: Tuesday, May 17, 2011 3:09 PM
> To: splices@ietf.org
> Subject: Re: [splices] SIP INVOKE method
> 
> 
> 
> 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
> _______________________________________________
> splices mailing list
> splices@ietf.org
> https://www.ietf.org/mailman/listinfo/splices