summaryrefslogtreecommitdiff
path: root/ed/4f11a792b78022f139c04887d8b96011048416
blob: e7893c54a8bb50bd833d2bb2226025d4a0a18061 (plain)
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
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 <gmaxwell@gmail.com>) id 1UJZdo-0001cZ-H9
	for bitcoin-development@lists.sourceforge.net;
	Sun, 24 Mar 2013 01:22:32 +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=gmaxwell@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 1UJZdn-0000oQ-Dg
	for bitcoin-development@lists.sourceforge.net;
	Sun, 24 Mar 2013 01:22:32 +0000
Received: by mail-la0-f44.google.com with SMTP id eb20so9481328lab.17
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 23 Mar 2013 18:22:24 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.125.239 with SMTP id mt15mr3520119lab.26.1364088144571; 
	Sat, 23 Mar 2013 18:22:24 -0700 (PDT)
Received: by 10.112.96.164 with HTTP; Sat, 23 Mar 2013 18:22:24 -0700 (PDT)
In-Reply-To: <BLU0-SMTP30A4EFEB3349A94802E930C8D60@phx.gbl>
References: <CA+8xBpe9D=poPyJ=soGdN3sovqdmvyGGij6FM8PHYGUB5aUkzQ@mail.gmail.com>
	<CACh7GpFqZtWVQFjM-w1uoB+74sVvE=_mXwBQ4P-qGMp2=HJ_yQ@mail.gmail.com>
	<BLU0-SMTP30A4EFEB3349A94802E930C8D60@phx.gbl>
Date: Sat, 23 Mar 2013 18:22:24 -0700
Message-ID: <CAAS2fgSaHereTkS41ZzErMU6b4ox74hThA_BDfv=b7tkHnoZ3w@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Jay F <jayf@outlook.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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: 1UJZdn-0000oQ-Dg
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A bitcoin UDP P2P protocol extension
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: Sun, 24 Mar 2013 01:22:32 -0000

On Sat, Mar 23, 2013 at 5:57 PM, Jay F <jayf@outlook.com> wrote:
> My first concern was that I and about everyone else only has TCP/UDP
> port forwarding,

You tunnel it!
http://tools.ietf.org/html/draft-tuexen-tsvwg-sctp-dtls-encaps-00

You could do worse to have a data stream that looks like WEBRTC traffic=E2=
=80=A6

In some ways SCTP is a pretty optimal transport for Bitcoin like messaging.