Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of m.gmane.org
	designates 80.91.229.3 as permitted sender)
	client-ip=80.91.229.3;
	envelope-from=gcbd-bitcoin-development@m.gmane.org;
	helo=plane.gmane.org; 
To: bitcoin-development@lists.sourceforge.net
From: Andreas Schildbach <andreas@schildbach.de>
Date: Tue, 31 Jan 2012 12:55:01 +0100
Message-ID: <jg8kql$bct$1@dough.gmane.org>
References: <1327881329.49770.YahooMailNeo@web121003.mail.ne1.yahoo.com>
	<jg88ed$i85$1@dough.gmane.org>
	<CA+s+GJDLoUG43hdLKYMwehBO9qqE=YCm7eJ2RN-TTTY_+OLp=A@mail.gmail.com>
	<CAKm8k+2wrsNDxEQXjZmqWQtO5DHiTjc0SgU_+QCU_FybeFFY6g@mail.gmail.com>
	<CA+s+GJAvEPda7UGHDoz84OavSh5jdN8wOhGgrNUgPU_Wh66Xyw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:9.0) Gecko/20111229 Thunderbird/9.0
In-Reply-To: <CA+s+GJAvEPda7UGHDoz84OavSh5jdN8wOhGgrNUgPU_Wh66Xyw@mail.gmail.com>
Subject: Re: [Bitcoin-development] BIP 21 (modification BIP 20)
Precedence: list

On 01/31/2012 11:22 AM, Wladimir wrote:

> To ensure forward compatibility with optional fields, we need to define
> how a client handles fields that it doesn't know about.
> 
> When should it display an error message, and when should it silently
> accept and ignore the extraneous fields?

IMHO its standard that unknown URL parameters are simply ignored. I
think we should not change this principle.

> (For example, if something that restricts the validity, such
> as "expires" is added later on, it is pretty important not to ignore it.
> Older clients should refuse to comply.)

In this case, you'd need to refuse *all* parameters you don't know
about. In consequence, all extensions would break older clients.