From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1TdCG2-0004wr-Nn for bitcoin-development@lists.sourceforge.net; Tue, 27 Nov 2012 03:54:50 +0000 X-ACL-Warn: Received: from mail-ye0-f175.google.com ([209.85.213.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TdCG1-0001E3-Qa for bitcoin-development@lists.sourceforge.net; Tue, 27 Nov 2012 03:54:50 +0000 Received: by mail-ye0-f175.google.com with SMTP id q7so961400yen.34 for ; Mon, 26 Nov 2012 19:54:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=tcmVNYkHKBAZi2VuhpSKG8IddeDdbgOQEkrWsp/ocgo=; b=Ho9RafNDqr4L2bpfHKK/cgff23Ek/1hdWH+gHe23wgSi6CUYbeqtrXIwsSLDTPtGEp H7dWblyxN49jENc0nT0fw4tmJnkvnsCiNJFKGxFlPICqY2AD3YOMoCkbonQCAH6CR699 3XCeKJYoMmx5d3uiGTHwUiFToR4k1cA6Aq7D5NBPgpekqizFhcc0kszf0gTwdd4WUNUN oalJdvLIQX19vKDiKFfVBDbJUozGNQ8oeaZxpkIw6SEcE7uZOF8LUm5hSW/L9llCjNfF /+jPjmaXNtuLgPZLWayePt5mO6buhVNHFP598KHEMwsykZLV6S7HKJk35cSu9FxmBlWU rm6Q== MIME-Version: 1.0 Received: by 10.101.180.27 with SMTP id h27mr3959028anp.60.1353988484409; Mon, 26 Nov 2012 19:54:44 -0800 (PST) Received: by 10.101.69.3 with HTTP; Mon, 26 Nov 2012 19:54:44 -0800 (PST) In-Reply-To: References: Date: Mon, 26 Nov 2012 19:54:44 -0800 Message-ID: From: Rick Wesson To: Walter Stanish Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQm1QEtd351NEbc7c6gga91hAGigWFkVid534vtVamK1auxAtjlJqtxbSI1Ubh3EdGdOpgh+ 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: 1TdCG1-0001E3-Qa Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Payment Protocol Proposal: Invoices/Payments/Receipts 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: Tue, 27 Nov 2012 03:54:50 -0000 > > We are not establishing an IETF working group, which is an option that > was explored prior to the Paris meeting and has been sidelined at > present for depth-of-bureaucracy by the backing commercial entities. > Rather, we are establishing a top-level IANA registry group. This is > not anticipated by the IETF old-guard working with us to be either (a) > controversial or (b) possible to block. My last note in this sub-thread. There are no IANA registry groups, there is no such thing, and no way to form one. The IETF can ask the IANA to form a registry but these things take lots of support and take a long time, and these are only created through standards track RFC. ICANN runs the IANA and there is no such framework that you elude to. Review http://www.iana.org/protocols/ If you are applying for a gTLD, good luck with that. -rick