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

Barry Leiba <barryleiba@computer.org> Thu, 08 March 2012 19:15 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 AAE7C21F85B7 for <apps-discuss@ietfa.amsl.com>; Thu, 8 Mar 2012 11:15:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.985
X-Spam-Level:
X-Spam-Status: No, score=-102.985 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-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 7WTxcvEmvkx8 for <apps-discuss@ietfa.amsl.com>; Thu, 8 Mar 2012 11:15:27 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id B306A21F8587 for <apps-discuss@ietf.org>; Thu, 8 Mar 2012 11:15:27 -0800 (PST)
Received: by yenm5 with SMTP id m5so515970yen.31 for <apps-discuss@ietf.org>; Thu, 08 Mar 2012 11:15:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=IovhwNMPVPqw0jqv+elaqSJ5GLUT1ygMovMYbL27478=; b=Mr8gGq4j0DnRoKuGWKGwymBmN/6aWE2MyIJHci84QUASH05p6NwbG+RHeJH4G/L0k9 4HTewfTZRlA3/E71XzQHqW6a2ZAnnq4/NgAcJjMIAAFYO+mLD0qRRvDSwvMsciIb3Wuq k19EIdDwXRYpC2ISEN2xM885qpecgcqMk5ZoC9SZrWfKQWGKZ2geFU/rB2jIbR+xXej/ nK6Hh8qID4iJWldNj525lapFmDGVpxfDl/1QGGwBTfB6wZlAWGQ38lMV0RtQBOsDABre N7hhB8oVvz+mJxxwtF9Lwqw8Q8UuB877N3ohT6W0k9olh/s7CjWMsOys2p8LWg9py+ea 8PFg==
MIME-Version: 1.0
Received: by 10.236.184.129 with SMTP id s1mr12502267yhm.21.1331234127092; Thu, 08 Mar 2012 11:15:27 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Thu, 8 Mar 2012 11:15:26 -0800 (PST)
In-Reply-To: <4F58EF37.8010802@KingsMountain.com>
References: <4F58EF37.8010802@KingsMountain.com>
Date: Thu, 08 Mar 2012 14:15:26 -0500
X-Google-Sender-Auth: coHLfy-SRnHOBijVfCSDpa_BLVA
Message-ID: <CAC4RtVBGtkfH93_bjnq8Wx4KyeqC-ijeA66O4LRxw7Cf7V0Z2Q@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Apps Discuss <apps-discuss@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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 19:15:28 -0000

On Thu, Mar 8, 2012 at 12:41 PM, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
> 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

Yes... this is exactly the sort of discussion I was looking to
generate *here*, before deciding whether it should be spun off to a
separate mailing list.  These are the sorts of questions that aren't
answered in the original request -- and, of course, can't be, yet,
until some discussion happens.

The bar for creating a new non-WG mailing list is fairly low, so the
ADs are not looking for definitive answers.  We just want a sense of
who will participate, where it's (roughly) likely to go, and how
likely it is to wind up with work for the IETF.

And it's OK if we create the mailing list and in the end the
participants decide to go elsewhere.  As I said, the bar is pretty
low.[1]  But there is a bar.

Barry


[1] But is it a pole-vault bar (high is harder) or a limbo bar (low is
harder)?  Hmmmm....