![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi -
I actually think the question of how a namespace is to be administered
is a perfectly valid one for the IETF to consider if it impacts the performance or functionality of a protocol.
Yes, as long as it can be expressed technically. RFC 2826 and http://www.iab.org/documents/docs/2003-09-20-dns-wildcards.html are good examples, IMHO. So was RFC 3177, although it needs revisiting today.
We do that all the time when we give explicit instructions to the IANA in an "IANA Considerations" section. The IETF could also do the same in an "ICANN Considerations" section when it comes to the DNS.
Actually, no. It is always IANA. However, RFC 2860 section 4.3 specifically excludes the IETF giving IANA guidance in certain areas.
Carl
Brian E Carpenter wrote, On 29/11/2006 10:43:
your question is linked to whether we treat the namespace as a public good to be administered for the greater public good, or as a commodity to be treated like coffee beans. And that really isn't a question for this technological community.
Depends how you look at it. Technological choices do have an impact on what the society is able to do (or not). It is up to the society to tell the engineers what it needs/wants. But I agree there are other fora for this.
Patrick
____________________________________________From ietf-bounces at ietf.org Thu Nov 30 05:32:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gpj8q-0001TJ-6r; Thu, 30 Nov 2006 05:27:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gpj8p-0001TC-2G for ietf at ietf.org; Thu, 30 Nov 2006 05:27:43 -0500 Received: from mtagate1.de.ibm.com ([195.212.29.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gpj8m-0004x5-UE for ietf at ietf.org; Thu, 30 Nov 2006 05:27:43 -0500 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate1.de.ibm.com (8.13.8/8.13.8) with ESMTP id kAUARYFC060398 for <ietf at ietf.org>; Thu, 30 Nov 2006 10:27:38 GMT Received: from d12av03.megacenter.de.ibm.com (d12av03.megacenter.de.ibm.com [9.149.165.213]) by d12nrmr1607.megacenter.de.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id kAUAV53w3219522 for <ietf at ietf.org>; Thu, 30 Nov 2006 11:31:05 +0100 Received: from d12av03.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av03.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id kAUARPug016332 for <ietf at ietf.org>; Thu, 30 Nov 2006 11:27:25 +0100 Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av03.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id kAUARPDT016324; Thu, 30 Nov 2006 11:27:25 +0100 Received: from zurich.ibm.com ([9.4.210.199]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA87488; Thu, 30 Nov 2006 11:27:24 +0100 Message-ID: <456EB20E.3000609 at zurich.ibm.com> Date: Thu, 30 Nov 2006 11:27:26 +0100 From: Brian E Carpenter <brc at zurich.ibm.com> Organization: IBM User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en, fr, de MIME-Version: 1.0 To: Carl Malamud <carl at media.org> References: <200611292355.kATNtUnZ005495 at bulk.resource.org> In-Reply-To: <200611292355.kATNtUnZ005495 at bulk.resource.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Cc: ietf at ietf.org Subject: Re: Something better than DNS? X-BeenThere: ietf at ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF-Discussion <ietf.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=unsubscribe> List-Post: <mailto:ietf at ietf.org> List-Help: <mailto:ietf-request at ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=subscribe> Errors-To: ietf-bounces at ietf.org
Hi -
I actually think the question of how a namespace is to be administered
is a perfectly valid one for the IETF to consider if it impacts the performance or functionality of a protocol.
Yes, as long as it can be expressed technically. RFC 2826 and http://www.iab.org/documents/docs/2003-09-20-dns-wildcards.html are good examples, IMHO. So was RFC 3177, although it needs revisiting today.
We do that all the time when we give explicit instructions to the IANA in an "IANA Considerations" section. The IETF could also do the same in an "ICANN Considerations" section when it comes to the DNS.
Actually, no. It is always IANA. However, RFC 2860 section 4.3 specifically excludes the IETF giving IANA guidance in certain areas.
Carl
Brian E Carpenter wrote, On 29/11/2006 10:43:
your question is linked to whether we treat the namespace as a public good to be administered for the greater public good, or as a commodity to be treated like coffee beans. And that really isn't a question for this technological community.
Depends how you look at it. Technological choices do have an impact on what the society is able to do (or not). It is up to the society to tell the engineers what it needs/wants. But I agree there are other fora for this.
Patrick
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.