1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rick.wesson@iidf.org>) id 1TdBrK-0001CH-78
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 03:29:18 +0000
X-ACL-Warn:
Received: from mail-gg0-f175.google.com ([209.85.161.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TdBrJ-0007oU-GQ
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 03:29:18 +0000
Received: by mail-gg0-f175.google.com with SMTP id y1so1190755ggc.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 26 Nov 2012 19:29:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:x-gm-message-state;
bh=pjPs26qsoT2/2mkTZI8x7orN/4+Z9jVMMiwvltS8B5s=;
b=NgzDMtEU78nq4kORqNz4Ts7ifgthVyH/41FUL5vLCf41r+jCkhu1n/jPmVWU6rW0OT
GScKYhElwgfjpsMrSg8ERbezUUQuGkHrU/LdtakCJBWhjCJYby54U8xVCgCiHr9VCZqE
WsBsAtRujGj7bZHQ9NrBkVSrKtvHub4q/Gs8/M7wZj8TTxtmW7cbdIhnSXtFrT6+duOn
ixG8l38kpCHGnoUdIvmX01je0wLljV91HNrITB+h6BWeWgc4sEoMk17BdVAinmTOtdgt
zKXxM2HwxurYilQcfUR4l90xJi0AxuQ/pg+kUCJYVO6WHCo4uFamadNtERz4/B95fcw/
YF5w==
MIME-Version: 1.0
Received: by 10.236.92.172 with SMTP id j32mr13853448yhf.37.1353986951959;
Mon, 26 Nov 2012 19:29:11 -0800 (PST)
Received: by 10.101.69.3 with HTTP; Mon, 26 Nov 2012 19:29:11 -0800 (PST)
In-Reply-To: <CACwuEiMjf8WYOpfmzHUHMa-sy2VsJHaUNj1cj722Y=P_sosbvw@mail.gmail.com>
References: <CABsx9T0PsGLEAWRCjEDDFWQrb+DnJWQZ7mFLaZewAEX6vD1eHw@mail.gmail.com>
<CACwuEiP7CGeZZGW=mXwrFAAqbbwbrPXTPb8vOEDuO9_96hqBGg@mail.gmail.com>
<CAAS2fgSY8hHiCJYEDv=y48hYRJJtB-R5EBX8JLz6NivBm+Z9PQ@mail.gmail.com>
<CACwuEiMjf8WYOpfmzHUHMa-sy2VsJHaUNj1cj722Y=P_sosbvw@mail.gmail.com>
Date: Mon, 26 Nov 2012 19:29:11 -0800
Message-ID: <CAJ1JLtuJ8HQri7++2bodc2ACRrE7Y48oy0HkPR8d400MooHaqA@mail.gmail.com>
From: Rick Wesson <rick@support-intelligence.com>
To: Walter Stanish <walter@stani.sh>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQl9xBnlIGIUkgiGMYait6BQKUbHg9Oh+GXz7RMZZlFuT0BZ1lB1HiHG2MY/uU3uRmExobdC
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1TdBrJ-0007oU-GQ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment Protocol Proposal:
Invoices/Payments/Receipts
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 03:29:18 -0000
On Mon, Nov 26, 2012 at 7:16 PM, Walter Stanish <walter@stani.sh> wrote:
>>> X-ISO4217-A3
>>
>> I see that draft-stanish-x-iso4217-a3 is not standards track, is there
>> a reason for this?
>
> Of the three currently published proposals, all are essentially IANA
> registry proposals.
>
> We are currently working with IETF staff, with open offers of support
> from multiple well funded commercial bodies, to transition these
> proposals through to IANA management.
I hate to inform you that you have been mislead. The IETF and the IANA
do not operate as you outlined above. Having spent too many years
within ICANN/IETF/IANA I can assure you are mistaken.
Your drafts are expired and it appears that there is no support for a
"finance" working group in the IETF.
-rick
|
