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

SM <sm@resistor.net> Tue, 10 April 2012 09:26 UTC

Return-Path: <sm@resistor.net>
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 341CE11E8089 for <apps-discuss@ietfa.amsl.com>; Tue, 10 Apr 2012 02:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.419
X-Spam-Level:
X-Spam-Status: No, score=-102.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, 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 mJ8RNix-UoeK for <apps-discuss@ietfa.amsl.com>; Tue, 10 Apr 2012 02:25:59 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B0411E8086 for <apps-discuss@ietf.org>; Tue, 10 Apr 2012 02:25:58 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q3A9PfKY016976; Tue, 10 Apr 2012 02:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1334049947; i=@resistor.net; bh=6lnq2cnThKdn2pZOr8fwnJ916gBFZ4dkA3TuriYEWzM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XsZnDQjDI4oRV39R76cocVjgZgm0S7QJcLWSkZuXwGVc4nggXM02CIjSJgXTWNsdo HE5Eg7/LJrpPRMe2+lnWF0CFUHSr3LD35IYN4A8Ugx9lVOia2UF79cr1DRNYJcpPY9 qr1fhpFVTVqDZZYjhWGbwH6mfDAQFfK8DQdSgssU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1334049947; i=@resistor.net; bh=6lnq2cnThKdn2pZOr8fwnJ916gBFZ4dkA3TuriYEWzM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=i3Fl7tiKdiJ2+MX1gnNOx2lCpokQj0/xHyiYgkZ5QQDLFtG9nb/PyTk+6DZmZA31g L8PplPaUNnuCWym3J7yAhBMwB1lg/ln4vNeCZCsysrHL4jjOFunapn07EtqhPa6smr pgmNJ28HFbHdSjPcQFuWsn5cMI6cx13Ogc73YOso=
Message-Id: <6.2.5.6.2.20120410004434.0b0b7920@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 10 Apr 2012 01:23:52 -0700
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Carsten Bormann <cabo@tzi.org>
From: SM <sm@resistor.net>
In-Reply-To: <3553E9F7-3E65-4143-BCF1-D8529D1A7C84@gmx.net>
References: <4F5ADDCA.80303@KingsMountain.com> <CACwuEiPuvW=DxpwHjcOMs+_T9-4YaBSMB+rm-1LX_nJoswk_qg@mail.gmail.com> <CAK3OfOiQ1=c+Dr56jN02HCzVSUyUaFoLG96Aq=1Ru4sMFdttaA@mail.gmail.com> <CACwuEiNfA0waTd6ypLotg+=jus6N4JDw8F4T2o04hnfqTXNL1A@mail.gmail.com> <4F60968D.4020703@stpeter.im> <D50DAB3A-39D0-486F-A329-002DA3DE309A@tzi.org> <CAGQP0AFJnfrNqM2MRWvEVzJzFvU94mntA8mFeJLz3gGqMa61xw@mail.gmail.com> <CACwuEiPgr8ovD2hB8nH2kpjLwck2cNTV52j3T=su-x1atxnjwA@mail.gmail.com> <CAGQP0AEEodF1UeZCR_5Mdf0RjMKQZZFAeyaDBx+OJNH_cvGT_Q@mail.gmail.com> <CAGQP0AGHyJKw-LyYS1TiANBoDb5BxNEjY_g8z5nni-tY3FMfUA@mail.gmail.com> <CACwuEiOUq7FEbEt1c33M9cRz3tMvDG=feYb5jTRLvwXDPSgztw@mail.gmail.com> <CAC4RtVAVskwy8kWkra40UA7ZaPdoAr6YeKR-Ltfz8VFboPS6LQ@mail.gmail.com> <CACwuEiPMLgnquotK=EXaTqewykrnXUhVOCGUiQ=D8bH3p3S-DA@mail.gmail.com> <CALaySJJ1PrabbBgefBmi0R6jqHUFxMGbrxPjn6T3g9WrdtP3Dw@mail.gmail.com> <CACwuEiPf_BPq0_TsdzbfvYo52nO=ujfY72dyphX+9akTXUUnBQ@mail.gmail.com> <CC523D07-9BBA-42D9-8547-1C205E5042C0@ tzi.org> <3553E9F7-3E65-4143-BCF1-D8529D1A7C84@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Payment Protocols -- was Re: 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: Tue, 10 Apr 2012 09:26:04 -0000

At 00:35 10-04-2012, Hannes Tschofenig wrote:
>The title "finance area mailing list" is probably the wrong term. 
>Instead, we are talking

Yes.

This is not the ideal venue for discussing about the creation of a 
new (IETF) area in my opinion.

>I don't know how far these attempts are away from what Walter is 
>trying to accomplish. I believe the main disconnect is in the 
>understanding of how the process works in bringing work to the IETF 
>and the lack of agreed terminology and scope makes is easy to talk 
>past each other.

Agreed.

Although I do point people to the "Tao" and other process-related 
documents (see http://www.ietf.org/newcomers.html for a starter 
guide), it is not helpful to people trying to understand how the 
process works and to bring new work in the IETF.  Please note that 
this should not be construed as an opinion about whether person X is 
a newcomer or not.

>Once getting to the point of talking about the same topic there are 
>various other challenges, such as
>* who are all the stakeholders that need to be involved?
>* are these communities interested to bring their work to the IETF?

The problem has turned into a catch 22.  There is a view that having 
an IETF mailing list would allow communities interested in bringing 
their work to the IETF to discuss and build support.  There is 
another view that by having such a mailing list, the IETF is 
"blessing" the work.

A mailing list allows focused discussions by a group of people 
interested in working on, for example, protocol X.  The absence of a 
mailing list does not hinder that.  One could look at this in terms 
of discussions.  If the volume of discussions is significant enough, 
it makes sense to move the discussion to a new mailing list if there 
isn't already one.

>* why did various earlier attempts fail?

Previous attempts have been about EDINT.  That is not the same as the 
problem discussed recently.

Regards,
-sm