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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <g.rowe.froot@gmail.com>) id 1RsMKs-000209-B9
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 22:37:58 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.47 as permitted sender)
client-ip=209.85.213.47; envelope-from=g.rowe.froot@gmail.com;
helo=mail-yw0-f47.google.com;
Received: from mail-yw0-f47.google.com ([209.85.213.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RsMKr-0004oB-6g
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 22:37:58 +0000
Received: by yhfq46 with SMTP id q46so317749yhf.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 31 Jan 2012 14:37:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.236.139.234 with SMTP id c70mr38363845yhj.33.1328049470070;
Tue, 31 Jan 2012 14:37:50 -0800 (PST)
Sender: g.rowe.froot@gmail.com
Received: by 10.236.195.99 with HTTP; Tue, 31 Jan 2012 14:37:50 -0800 (PST)
In-Reply-To: <jg9p4a$c90$1@dough.gmane.org>
References: <1328020046.70720.YahooMailNeo@web121002.mail.ne1.yahoo.com>
<1328025899.2832.5.camel@BMThinkPad.lan.bluematt.me>
<1328034145.2832.11.camel@BMThinkPad.lan.bluematt.me>
<jg9p4a$c90$1@dough.gmane.org>
Date: Tue, 31 Jan 2012 22:37:50 +0000
X-Google-Sender-Auth: P5buBuV5zpsuYAsz3KcJFucAXBc
Message-ID: <CAKm8k+0o0fBcBgRMOEc3nycGaLN7EEvfQ5wrZN4XwO5Gk2Pk5w@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=485b397dceabe8605b04b7da9c25
X-Spam-Score: -0.5 (/)
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
(g.rowe.froot[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RsMKr-0004oB-6g
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
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: Tue, 31 Jan 2012 22:37:58 -0000
--485b397dceabe8605b04b7da9c25
Content-Type: text/plain; charset=UTF-8
Andreas has a good point. See RFC 3986 on URI schemes:
http://tools.ietf.org/html/rfc3986#page-12
The colon is a reserved general delimiter (similar in use to the / in a
typical URL, but applies to URNs etc). As suggested, we get req:something
being changed to one of the unreserved characters that do not have to be
URL encoded. Again, from the RFC these are
* Option A: req_something (underscore)
* Option B: req-something (hyphen)
* Option C: req~something (tilde)
* Option D: req.something (period)
Personally, my eye likes Option B, the hyphen.
On 31 January 2012 22:14, Andreas Schildbach <andreas@schildbach.de> wrote:
> On 01/31/2012 07:22 PM, Matt Corallo wrote:
>
> > that "It is recommended that additional variables prefixed with
> > mustimplement: not be used in a mission-critical way until a grace
>
> Is the ':' sign actually allowed in URL parameter names
> (unescaped/unencoded)? If not, I'd propose an unrestricted char instead,
> maybe '_'.
>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--485b397dceabe8605b04b7da9c25
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Andreas has a good point. See RFC 3986 on URI schemes:=C2=A0<a href=3D"http=
://tools.ietf.org/html/rfc3986#page-12">http://tools.ietf.org/html/rfc3986#=
page-12</a><div><br></div><div>The colon is a reserved general delimiter (s=
imilar in use to the / in a typical URL, but applies to URNs etc). As sugge=
sted, we get req:something being changed to one of the unreserved character=
s that do not have to be URL encoded. Again, from the RFC these are</div>
<div><br></div><div>* Option A: req_something (underscore)</div><div>* Opti=
on B: req-something (hyphen)</div><div>* Option C: req~something (tilde)</d=
iv><div><div>* Option D: req.something (period)</div></div><div><div><br>
</div></div><div>Personally, my eye likes Option B, the hyphen.=C2=A0</div>=
<div><br><div class=3D"gmail_quote">On 31 January 2012 22:14, Andreas Schil=
dbach <span dir=3D"ltr"><<a href=3D"mailto:andreas@schildbach.de">andrea=
s@schildbach.de</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 01/31/2012 07:22 PM, Ma=
tt Corallo wrote:<br>
<br>
> that "It is recommended that additional variables prefixed with<b=
r>
> mustimplement: not be used in a mission-critical way until a grace<br>
<br>
</div>Is the ':' sign actually allowed in URL parameter names<br>
(unescaped/unencoded)? If not, I'd propose an unrestricted char instead=
,<br>
maybe '_'.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
Keep Your Developer Skills Current with LearnDevNow!<br>
The most comprehensive online learning library for Microsoft developers<br>
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,<br=
>
Metro Style Apps, more. Free future releases when you subscribe now!<br>
<a href=3D"http://p.sf.net/sfu/learndevnow-d2d" target=3D"_blank">http://p.=
sf.net/sfu/learndevnow-d2d</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>
</div></div></blockquote></div><br></div>
--485b397dceabe8605b04b7da9c25--
|
