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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1Vyxl0-0007Vj-Gu
for bitcoin-development@lists.sourceforge.net;
Fri, 03 Jan 2014 05:57:18 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.53 as permitted sender)
client-ip=209.85.215.53; envelope-from=gmaxwell@gmail.com;
helo=mail-la0-f53.google.com;
Received: from mail-la0-f53.google.com ([209.85.215.53])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vyxkz-0000vi-JG
for bitcoin-development@lists.sourceforge.net;
Fri, 03 Jan 2014 05:57:18 +0000
Received: by mail-la0-f53.google.com with SMTP id mc6so7741033lab.26
for <bitcoin-development@lists.sourceforge.net>;
Thu, 02 Jan 2014 21:57:10 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.92.112 with SMTP id cl16mr33641342lbb.15.1388728630908;
Thu, 02 Jan 2014 21:57:10 -0800 (PST)
Received: by 10.112.198.65 with HTTP; Thu, 2 Jan 2014 21:57:10 -0800 (PST)
In-Reply-To: <20140103052243.GK3180@nl.grid.coop>
References: <20140103052243.GK3180@nl.grid.coop>
Date: Thu, 2 Jan 2014 21:57:10 -0800
Message-ID: <CAAS2fgR89wcBLUedXGz1Rsr3eyN5tLH6Bb9k6qsutnA=cydmTQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Troy Benjegerdes <hozer@hozed.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Vyxkz-0000vi-JG
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP: register with IANA for
bitcoin/cryptocoin port numbers
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: Fri, 03 Jan 2014 05:57:18 -0000
On Thu, Jan 2, 2014 at 9:22 PM, Troy Benjegerdes <hozer@hozed.org> wrote:
> I believe this is self-explainatory:
>
> 1) Bitcoin usually runs on port 8333. Why?
>
> 2) Bitcoin does not show in up http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml .. why?
>
> 3) What needs to happen to have someone from the Bitcoin foundation
> to fill out the form asking for an assigned port (see
> http://www.iana.org/form/ports-services )
I have requested an assignment.
|
