Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VY9ux-0004lG-Nn for bitcoin-development@lists.sourceforge.net; Mon, 21 Oct 2013 07:28:47 +0000 X-ACL-Warn: Received: from chrocht.moloch.sk ([62.176.169.44] helo=mail.moloch.sk) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VY9uw-0005im-Bx for bitcoin-development@lists.sourceforge.net; Mon, 21 Oct 2013 07:28:47 +0000 Received: from [192.168.0.102] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id 027D41801A74; Mon, 21 Oct 2013 09:28:39 +0200 (CEST) Message-ID: <5264D7A7.2080308@250bpm.com> Date: Mon, 21 Oct 2013 09:28:39 +0200 From: Martin Sustrik User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Jean-Paul Kogelman References: <38895569-E6E1-4576-9E36-B00B53F9D3CC@me.com> <201310192229.19932.luke@dashjr.org> <19909B49-0895-4130-99FB-9A116140CFE9@me.com> <20131019235746.GA29032@savin> <9EF588BB-14B5-495A-8253-82574DCB1A8A@me.com> <20131020224316.GA25280@savin> <20131021062555.GA10784@savin> <80401395-792A-4637-A75C-1D499C547F98@me.com> <20131021064320.GA17190@savin> <5264D1DB.5060107@250bpm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1VY9uw-0005im-Bx Cc: Bitcoin Development Subject: Re: [Bitcoin-development] A critique of bitcoin open source community X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2013 07:28:47 -0000 On 21/10/13 09:07, Jean-Paul Kogelman wrote: > The list comes from BIP 1. Sorry, I haven't meant you personally. It was just a generic question about using existing process instead of inventing a new one on the go. >> Have it been considered to do this via IETF? The process there is hardened by 40 years of experience and 7000+ RFCs. Probably better than anything you can devise yourself. >> >> Martin >