Questions about IOTP 1.0

Cullen Jennings <fluffy@cisco.com> Mon, 03 May 2004 03:20 UTC

Return-Path: <ietf-trade-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0HX400102BXTQZ@elistx.com> (original mail from fluffy@cisco.com); Sun, 02 May 2004 23:20:17 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0HX400101BXRQY@elistx.com> for ietf-trade@lists.elistx.com; Sun, 02 May 2004 23:20:15 -0400 (EDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0HX400FK7BXIG2@elistx.com> for ietf-trade@lists.elistx.com; Sun, 02 May 2004 23:20:15 -0400 (EDT)
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; Sun, 02 May 2004 20:19:53 -0700
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i433JNjO004898 for <ietf-trade@lists.elistx.com>; Sun, 02 May 2004 20:19:24 -0700 (PDT)
Received: from [10.0.1.3] (sjc-vpn4-1169.cisco.com [10.21.84.144]) by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AOP20188; Sun, 02 May 2004 20:19:21 -0700 (PDT)
Date: Sun, 02 May 2004 17:19:24 -1000
From: Cullen Jennings <fluffy@cisco.com>
Subject: Questions about IOTP 1.0
To: ietf-trade@lists.elistx.com
Message-id: <BCBADE1C.3BB91%fluffy@cisco.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
User-Agent: Microsoft-Entourage/10.1.4.030702.0
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-trade/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-trade-request@lists.elistx.com?body=help>
List-Id: <ietf-trade.lists.elistx.com>

I apologize in advance for these naive questions but I'm just trying to get
up to speed on IOTP. If there is an implementers lists or a better list to
ask them on - please point me that way. I'm looking at this for use with
VoIP applications. 

In an OfferRespBlk, you can have a Payment which contains a BrandListRef but
I don't see how to put a BrandList in an OfferRespBlk. The text in section
3.2.1 about offer exchanges indicates that organization such as the Merchant
and Payment Handler can be indicated in the OfferRespBlk but again, I don't
see how to do that. Are both of these solved by putting them in a TpoBlk in
the same IotpMessage?

The DeliveryReqBlk is described in section 2.2.3 as having a Payment Receipt
Signature.  I don't see how to include that. It also seems that the actually
Payment Receipt is needed so that the Delivery service and validate the
signature but I don't see any mention of including a PayReceipt in the
DeliveryReqBlk. Even if signatures are not being used, it seems very
desirable to have the Payment Receipt available in the Delivery Request. Is
there a way to do this?

I'm confused about how HMAC works as a signature algorithm.

Our there common interoperation tests folks implementing this do? Interop
events? Common implementations that are good to test against? Open source
implementations? Operational deployments? There seem to be really a lot of
typos in the RFC. Do people recommend to use this in new things or is it
just an historical document?

Many Thanks, Cullen