From beepwg-bounces@dbc.mtview.ca.us Mon Apr 09 14:08:37 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HayI9-0006SU-74 for beep-archive@lists.ietf.org; Mon, 09 Apr 2007 14:08:37 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HayI4-0007V7-3X for beep-archive@lists.ietf.org; Mon, 09 Apr 2007 14:08:37 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id l39I557W026069; Mon, 9 Apr 2007 11:05:16 -0700 Received: from ppgia.pucpr.br (hermes.ppgia.pucpr.br [200.192.112.141]) l39I51Hg026065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 9 Apr 2007 11:05:03 -0700 Received: from [10.32.1.22] (helo=localhost) by ppgia.pucpr.br with esmtp (PPGIA PUCPR) id 1HayEQ-0007zQ-Py for ; Mon, 09 Apr 2007 15:04:46 -0300 Received: from 201-66-31-182.ctame704.dsl.brasiltelecom.net.br (201-66-31-182.ctame704.dsl.brasiltelecom.net.br [201.66.31.182]) by wwws.ppgia.pucpr.br (Horde MIME library) with HTTP; Mon, 09 Apr 2007 15:04:44 -0300 Message-ID: <20070409150444.hs1fdfs408cosg04@wwws.ppgia.pucpr.br> Date: Mon, 09 Apr 2007 15:04:44 -0300 From: stihler@ppgia.pucpr.br To: beepwg@lists.beepcore.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) X-Spam-Score: -2.6 (--) X-Virus-Scanned: Verificado contra virus. Subject: [BEEPwg] implementing a profile X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.2 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Greetings. I'm trying to design an authorization framework for web-services, and I'm thinking to use BEEP as the transport protocol for SOAP. I did some research for implementations but found nothing (except for IBM's beeplite, which has a 90-day license). Is there any opensource implementation of the SOAP-over-BEEP profile described on rfc4227? If there is not, would it be too hard to implement it? I'm thinking about using Beepcore for java. The application would be a kind of proxy for SOAP requisitions, it would inspect every SOAP message and check it against the policies, closing the channel in case of policy violation, otherwise it would forward the message to the right web service. ex: client-->[proxy client]<=SOAP/BEEP=>[proxy]-->web-service ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg