From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Troy Benjegerdes <hozer@hozed•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP: register with IANA for bitcoin/cryptocoin port numbers
Date: Fri, 3 Jan 2014 06:56:59 +0100 [thread overview]
Message-ID: <CAKaEYhJmBT7Fai525-+Wba0HeU=WTjTpf_Ox66FnWQgsJatSOg@mail.gmail.com> (raw)
In-Reply-To: <20140103052243.GK3180@nl.grid.coop>
[-- Attachment #1: Type: text/plain, Size: 2565 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 3930 bytes --]
next prev parent reply other threads:[~2014-01-03 5:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 5:22 Troy Benjegerdes
2014-01-03 5:56 ` Melvin Carvalho [this message]
2014-01-03 8:16 ` Wladimir
2014-01-03 5:57 ` Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKaEYhJmBT7Fai525-+Wba0HeU=WTjTpf_Ox66FnWQgsJatSOg@mail.gmail.com' \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=hozer@hozed$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox