From: Wladimir <laanwj@gmail•com>
To: Melvin Carvalho <melvincarvalho@gmail•com>
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 09:16:55 +0100 [thread overview]
Message-ID: <CA+s+GJC2Z2NNdSWTvkwcJS8jEHx=ytFiWLH7-4OLD8-L89AOuQ@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYhJmBT7Fai525-+Wba0HeU=WTjTpf_Ox66FnWQgsJatSOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
>
> 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.
>
I'm sure it would be *possible*, but testnet and mainnet are entirely
separate networks. Not only that, but the entire point of the testnet is
separation. There is no logic to multiplexing them.
If conservation is an issue, I'd forgo the testnet port. We don't have a
'test ssh' or 'test mail server' port either, most people will just
allocate a temporary number for those themselves.
In case the port is already in use, bitcoin can run on and announce any
another port. There is no strict need for it to be 8333 (or 18333) at all.
There isn't even an argument for convenience. Most of the time, users don't
specify nodes. And in the rare cases that they do they can specify a port
as well.
If a whole slew of alt coins also tried to reserve ports, I suspect that
> may raise eyebrows.
>
That's somebody else's problem. Bitcoin is by far the most well-known of
the 'coins' so it may be considered realistic to allocate one or two ports
for it. Or not, in which case the altcoins can forget it too.
Regards,
Wladimir
[-- Attachment #2: Type: text/html, Size: 2149 bytes --]
next prev parent reply other threads:[~2014-01-03 8:17 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
2014-01-03 8:16 ` Wladimir [this message]
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='CA+s+GJC2Z2NNdSWTvkwcJS8jEHx=ytFiWLH7-4OLD8-L89AOuQ@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=melvincarvalho@gmail$(echo .)com \
/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