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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1Vyxkq-00039y-4z
for bitcoin-development@lists.sourceforge.net;
Fri, 03 Jan 2014 05:57:08 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.44 as permitted sender)
client-ip=209.85.215.44; envelope-from=melvincarvalho@gmail.com;
helo=mail-la0-f44.google.com;
Received: from mail-la0-f44.google.com ([209.85.215.44])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vyxko-0000vN-Q2
for bitcoin-development@lists.sourceforge.net;
Fri, 03 Jan 2014 05:57:08 +0000
Received: by mail-la0-f44.google.com with SMTP id ep20so7933745lab.3
for <bitcoin-development@lists.sourceforge.net>;
Thu, 02 Jan 2014 21:57:00 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.167.42 with SMTP id zl10mr9195lbb.92.1388728620022; Thu,
02 Jan 2014 21:57:00 -0800 (PST)
Received: by 10.112.156.72 with HTTP; Thu, 2 Jan 2014 21:56:59 -0800 (PST)
In-Reply-To: <20140103052243.GK3180@nl.grid.coop>
References: <20140103052243.GK3180@nl.grid.coop>
Date: Fri, 3 Jan 2014 06:56:59 +0100
Message-ID: <CAKaEYhJmBT7Fai525-+Wba0HeU=WTjTpf_Ox66FnWQgsJatSOg@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Troy Benjegerdes <hozer@hozed.org>
Content-Type: multipart/alternative; boundary=001a11c25f1216014d04ef0a94b5
X-Spam-Score: -0.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
(melvincarvalho[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Vyxko-0000vN-Q2
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:08 -0000
--001a11c25f1216014d04ef0a94b5
Content-Type: text/plain; charset=ISO-8859-1
On 3 January 2014 06:22, 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 )
>
> 4) what should the process be for new cryptocoins to get both default
> port numbers, as well as P2P network identifier 'magic numbers'
>
IANA normally register ports with the principle of conservation in mind.
See section 7.2 of RFC6335 for more details.
http://tools.ietf.org/html/rfc6335#section-7.2
8333 and 18333 are currently unassigned, which is good news.
Ideally it would be good to have two ports, one for the main net, and one
for the test net. However, in light of conservation only one may be
granted. The question as to whether traffic could be multiplexed over a
single port may be raised.
tnp 8321 udp Thin(ium) Network Protocol
[Aly_Orady] [Aly_Orady]
2007-08-07
8322-8350 Unassigned
server-find 8351 tcp Server Find
[Chris_Brown] [Chris_Brown]
gv-pf 18262 udp GV NetConfig Service
[Scott_Libert] [Scott_Libert]
2008-01-29
18263-18462 Unassigned
ac-cluster 18463 tcp AC Cluster
[Lisa_Zhong]
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt
If a whole slew of alt coins also tried to reserve ports, I suspect that
may raise eyebrows.
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11c25f1216014d04ef0a94b5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 3 January 2014 06:22, Troy Benjegerdes <span dir=3D"ltr"><<a =
href=3D"mailto:hozer@hozed.org" target=3D"_blank">hozer@hozed.org</a>></=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">I believe this is self-ex=
plainatory:<br>
<br>
1) Bitcoin usually runs on port 8333. Why?<br>
<br>
2) Bitcoin does not show in up <a href=3D"http://www.iana.org/assignments/s=
ervice-names-port-numbers/service-names-port-numbers.xhtml" target=3D"_blan=
k">http://www.iana.org/assignments/service-names-port-numbers/service-names=
-port-numbers.xhtml</a> .. why?<br>
<br>
3) What needs to happen to have someone from the Bitcoin foundation<br>
=A0 to fill out the form asking for an assigned port (see<br>
=A0 <a href=3D"http://www.iana.org/form/ports-services" target=3D"_blank">h=
ttp://www.iana.org/form/ports-services</a> )<br>
<br>
4) what should the process be for new cryptocoins to get both default<br>
port numbers, as well as P2P network identifier 'magic numbers'<br>=
</blockquote><div><br></div><div>IANA normally register ports with the prin=
ciple of conservation in mind.=A0 See section 7.2 of RFC6335 for more detai=
ls.<br>
<br><a href=3D"http://tools.ietf.org/html/rfc6335#section-7.2">http://tools=
.ietf.org/html/rfc6335#section-7.2</a><br><br></div><div>8333 and 18333 are=
currently unassigned, which is good news.<br><br>Ideally it would be good =
to have two ports, one for the main net, and=20
one for the test net.=A0 However, in light of conservation only one may be
granted.=A0 The question as to whether traffic could be multiplexed over a
single port may be raised.<br></div><div><br><pre>tnp 8321 =
udp Thin(ium) Network Protocol [Aly_Orady] =
[Aly_Orady] =
2007-08-07
8322-8350 Unassigned
server-find 8351 tcp Server Find [Chris_B=
rown] [Chris_Brown]<br><br>gv-pf =
18262 udp GV NetConfig Service [Scott_Libert] =
[Scott_Libert] =
2008-01-29
18263-18462 Unassigned
ac-cluster 18463 tcp AC Cluster [Lisa_Zh=
ong] <br></pre><a href=3D"http://www.iana.org/assignments/service-names-p=
ort-numbers/service-names-port-numbers.txt">http://www.iana.org/assignments=
/service-names-port-numbers/service-names-port-numbers.txt</a><br>
<br></div><div>If a whole slew of alt coins also tried to reserve ports, I =
suspect that may raise eyebrows.<br></div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
<br>
---------------------------------------------------------------------------=
---<br>
Rapidly troubleshoot problems before they affect your business. Most IT<br>
organizations don't have a clear picture of how application performance=
<br>
affects their revenue. With AppDynamics, you get 100% visibility into your<=
br>
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynami=
cs Pro!<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D84349831&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D84349831&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div></div>
--001a11c25f1216014d04ef0a94b5--
|
