Re: What's an experiment?

Andrew Newton <andy@hxr.us> Sat, 18 February 2006 20:38 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAYqn-0001sP-R0; Sat, 18 Feb 2006 15:38:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAYqm-0001sK-Is for ietf@ietf.org; Sat, 18 Feb 2006 15:38:40 -0500
Received: from zeke.ecotroph.net ([69.31.8.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAYql-0007A1-CN for ietf@ietf.org; Sat, 18 Feb 2006 15:38:40 -0500
Received: from [10.0.1.105] ([::ffff:64.83.8.179]) (AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA) by zeke.ecotroph.net with esmtp; Sat, 18 Feb 2006 15:37:57 -0500 id 0158811F.43F785A5.000028A6
In-Reply-To: <43F74DDF.4D35@xyzzy.claranet.de>
References: <198A730C2044DE4A96749D13E167AD3792A99D@MOU1WNEXMB04.vcorp.ad.vrsn.com> <43F74DDF.4D35@xyzzy.claranet.de>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <F37B4970-582D-46B8-A6B5-07675786CAA4@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Date: Sat, 18 Feb 2006 15:38:19 -0500
To: Frank Ellermann <nobody@xyzzy.claranet.de>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf@ietf.org
Subject: Re: What's an experiment?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

On Feb 18, 2006, at 11:39 AM, Frank Ellermann wrote:

> Hallam-Baker, Phillip wrote:
>
>> Given the impressive lack of success of BEEP vs SOAP it would
>> be much better for the IESG to formally recognize that this
>> attempt to ratify a 'me too' protocol in 9 months has
>> backfired and is now harming IETF Web Services efforts.
>
> Are they related ?  I had the vague impression that BEEP is
> a way to multiplex one TCP-connection, and SOAP is a kind of
> RPC with XML over http-post (and other bindings).  Not the
> same layer, different problems => different solutions (?)

Frank,

You are right.  They solve two different problems.  In fact, I  
believe one of the bragging points about SOAP (other than it can  
defeat your firewalls and snooker your security admins) is that it  
can be run over various transfer protocols, such as that defined in  
RFC 3288.  If great harm can come from using SOAP as intended, that  
says more about SOAP than it does BEEP.

-andy

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf