Re: [apps-discuss] Proposal for a Finance Area Mailing List

=JeffH <Jeff.Hodges@KingsMountain.com> Thu, 08 March 2012 17:41 UTC

Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5609021F8585 for <apps-discuss@ietfa.amsl.com>; Thu, 8 Mar 2012 09:41:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.373
X-Spam-Level:
X-Spam-Status: No, score=-99.373 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihukuaduZo-4 for <apps-discuss@ietfa.amsl.com>; Thu, 8 Mar 2012 09:41:13 -0800 (PST)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by ietfa.amsl.com (Postfix) with SMTP id C16DF21F8550 for <apps-discuss@ietf.org>; Thu, 8 Mar 2012 09:41:13 -0800 (PST)
Received: (qmail 12581 invoked by uid 0); 8 Mar 2012 17:41:13 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy9.bluehost.com with SMTP; 8 Mar 2012 17:41:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=PRssfvhExRzURJO9oZ5SU/Y28PGmsPLZjGkEgK4+MGo=; b=mCZU9wzpxDATyxByiSmj1uMs103UWb0my/8eCd7UYfZYE8u582AhuWffbyHYdxSrVNn0Yw9JdP4hp1jVBaos52SqPLB2ekVVbaEh5YzRBE1gby/hk1fpnVOZwFmZSckT;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.137.56]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1S5hKy-0001O1-Aa for apps-discuss@ietf.org; Thu, 08 Mar 2012 10:41:12 -0700
Message-ID: <4F58EF37.8010802@KingsMountain.com>
Date: Thu, 08 Mar 2012 09:41:11 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19
MIME-Version: 1.0
To: Apps Discuss <apps-discuss@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: Re: [apps-discuss] Proposal for a Finance Area Mailing List
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 17:41:14 -0000

In addition to the previously mentioned EDI and IOTP work, there was also this 
back in the late 1990s..

CyberCash Credit Card Protocol Version 0.8
file:///home/hodges/doc/IETF/rfc/rfc1898.txt

ECML v1: Field Names for E-Commerce
file:///home/hodges/doc/IETF/rfc/rfc2706.txt

ECML v1.1: Field Specifications for E-Commerce
file:///home/hodges/doc/IETF/rfc/rfc3106.txt

..and then fwiw, it's not clear what happened to these expired I-Ds..

draft-eastlake-internet-payment
draft-eastlake-universal-payment
draft-hallam-micropayment-01


Donald Eastlake and Steve Crocker were involved in the above work (they were 
apparently affiliated with CyberCash at the time). They'd likely have some 
input into this discussion (as has been noted).


A separate but related question is whether "financial-protocol" folk need 
different underlying  protocols, for transport/transfer of this particular type 
of data and notifications, than what is extant (and implemented & shipping) 
today (e.g., HTTP, TLS/SSL, SCTP, XMPP, etc.).

If not, then perhaps they might concentrate on the stuff at their "financial" 
layer and concoct "bindings" to the existing underlying stuff (eg, as we did in 
SAML & Liberty (to HTTP)) as appropriate, and they then could perhps more 
easily work on their "financial" layer whereever (eg, W3C, OASIS, SomeNew.org, 
etc).

The overall key is (as has been noted in this thread) getting a critical mass 
of subject matter experts to show up with the cycles/commitment to 
accomplishing something. So one should select a venue that such folk are most 
likely to participate in. That may or may not be the IETF (Your Mileage May Vary..)

HTH,

=JeffH