IETF Logo Mail Archive

[splices] SIP INVOKE method

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Tue, 17 May 2011 13:15 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 BA982E0811 for <splices@ietfa.amsl.com>; Tue, 17 May 2011 06:15:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 X8q6uEwaEPUD for <splices@ietfa.amsl.com>; Tue, 17 May 2011 06:15:08 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id CB117E073E for <splices@ietf.org>; Tue, 17 May 2011 06:15:05 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAG500k3GmAcF/2dsb2JhbACCZaM0d6hUg1kCm2iGGQSUXYpF
X-IronPort-AV: E=Sophos; i="4.65,225,1304308800"; d="scan'208,217"; a="188723502"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 17 May 2011 09:15:04 -0400
X-IronPort-AV: E=Sophos; i="4.65,225,1304308800"; d="scan'208,217"; a="622774029"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 May 2011 09:15:04 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 17 May 2011 09:15:03 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: "splices@ietf.org" <splices@ietf.org>
Date: Tue, 17 May 2011 09:15:02 -0400
Thread-Topic: SIP INVOKE method
Thread-Index: AcwUlG21RcTDGyn+QBi7uyh9D1M1iw==
Message-ID: <6369CB70BFD88942B9705AC1E639A33822CBDA8EBF@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6369CB70BFD88942B9705AC1E639A33822CBDA8EBFDCUS1MBEX4glo_"
MIME-Version: 1.0
Subject: [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 13:15:09 -0000

Hi,

As discussed in the last SPLICES WG meeting in Prague, the REFER method is overloaded and has limitations that prevents it from being the ideal method for action invocation.
We have worked on the following new draft that defines a new SIP method to be used for invoking actions:
https://datatracker.ietf.org/doc/draft-yusef-splices-invoke/

We would appreciate it if people review the document and provide us with their feedback.

Regards,
Rifaat

v2.23.0 | Report a Bug | By Email