Re: I-D Action:draft-duerst-iana-namespace-00.txt

Mark Nottingham <mnot@mnot.net> Mon, 18 February 2008 20:31 UTC

Return-Path: <discuss-bounces@ietf.org>
X-Original-To: ietfarch-discuss-archive@core3.amsl.com
Delivered-To: ietfarch-discuss-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E22228C63A; Mon, 18 Feb 2008 12:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kVc37EEyex0X; Mon, 18 Feb 2008 12:31:31 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47E0128C67B; Mon, 18 Feb 2008 12:28:12 -0800 (PST)
X-Original-To: discuss@core3.amsl.com
Delivered-To: discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86FFE28C675 for <discuss@core3.amsl.com>; Mon, 18 Feb 2008 12:28:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9aUYutVbLXji for <discuss@core3.amsl.com>; Mon, 18 Feb 2008 12:28:06 -0800 (PST)
Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by core3.amsl.com (Postfix) with ESMTP id 6ED8728C6F2 for <discuss@apps.ietf.org>; Mon, 18 Feb 2008 12:22:50 -0800 (PST)
Received: from [127.0.0.1] (unknown [216.145.54.7]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id DFB8723E4B0; Mon, 18 Feb 2008 15:22:44 -0500 (EST)
Message-Id: <9A910F0F-7930-4D84-A0A8-46FE86A6618E@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <47B9D5F5.3020808@gmx.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: I-D Action:draft-duerst-iana-namespace-00.txt
Date: Tue, 19 Feb 2008 07:22:41 +1100
References: <6.0.0.20.2.20080218203629.058cf7c0@localhost> <048BF0AB-6FCB-411B-AD4B-726DF8B13B08@osafoundation.org> <47B9D5F5.3020808@gmx.de>
X-Mailer: Apple Mail (2.919.2)
Cc: Thomas Narten <narten@us.ibm.com>, Tim Bray <Tim.Bray@Sun.COM>, Apps Discuss <discuss@apps.ietf.org>, IANA <iana@iana.org>
X-BeenThere: discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@ietf.org>
List-Help: <mailto:discuss-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@ietf.org?subject=subscribe>
Sender: discuss-bounces@ietf.org
Errors-To: discuss-bounces@ietf.org

Details:
   http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic

Personally, if I had to serve this traffic, I'd put a highly- 
concurrent Web server (e.g., Lighttpd) in place and build a one-second 
+ delay into serving those responses. Fine for human use, but will  
motivate software authors to find out why things suddenly got so slow...

Beyond that, question: how many IETF specs use a namespace URI as the  
primary means of identifying the format/protocol? As opposed to a  
media type. My suspicion is that the number is fairly small. If that's  
the case, I wonder if there's a need for these URIs to be resolvable.

Cheers,


On 19/02/2008, at 6:01 AM, Julian Reschke wrote:

> Lisa Dusseault wrote:
>> Hi,
>> I'm adding IANA and Thomas Narten (author of IANA considerations  
>> docs) to this thread to get early IANA feedback about this idea.   
>> It may well be a good idea, but we definitely want to think it  
>> through:
>> - A registry for HTTP URLs in the IANA domain
>>   ... including a HTML or XML document hosted by IANA on its  
>> Website at the location specified in the registered URL
>>  ... which means that end-users and developers will use these URIs,  
>> perhaps very frequently
>> What do we know about the W3 experience hosting namespace URIs with  
>> actual documents at the URIs?  I've been hearing rumours lately  
>> about something like this causing expensive levels of traffic, but  
>> I can't recall the details.
>> ...
>
> That was about DTDs (fetched by XML parsers), not namespace documents.
>
> BR, Julian


--
Mark Nottingham     http://www.mnot.net/