W3C home > Mailing lists > Public > www-tag@w3.org > October 2008

Re: URLs on iana.org, was: Draft minutes from TAG telcon of 2008-10-02

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Wed, 8 Oct 2008 14:47:41 +0200
Message-Id: <D221FEDF-92E3-470D-AD01-5278C95ECFFC@greenbytes.de>
Cc: "Henry S. Thompson" <ht@inf.ed.ac.uk>, www-tag@w3.org
To: Julian Reschke <julian.reschke@gmx.de>

This is so twenty century...

I respect the IETF and everyting. However, if you need a good exmaple  
of a tech organisation that has totally fallen behind current web  
use, look no further.

//Stefan

Am 08.10.2008 um 13:50 schrieb Julian Reschke:

>
> From the meeting minutes:
>
>> DC:How does IANA service this? A 200 response would imply this is  
>> an information resource
>> ... So I suggested we should get them to do the 303 redirect
>> JR: I spoke to someone at IETF, and I think they are unaware of  
>> the issue and are waiting to hear from us
>
> My understanding is that (as of now) the IANA is unwilling to  
> guarantee *anything* about how they serve web content. I'd be  
> surprised if they cared about the fine points of the 303 status  
> code; for now they are even discouraging use of the registration  
> URLs in specifications (<http://tools.ietf.org/html/ 
> rfc5226#section-5.1>):
>
>         Note 2: When referring to an existing registry, providing a  
> URL
>         to precisely identify the registry is helpful.  Such URLs,
>         however, should usually be removed from the RFC prior to final
>         publication, since IANA URLs are not guaranteed to be  
> stable in
>         the future.  In cases where it is important to include a  
> URL in
>         the document, IANA should concur on its inclusion.
>
> BR, Julian
>
>
>

--
<green/>bytes GmbH, Hafenweg 16, D-48155 Münster, Germany
Amtsgericht Münster: HRB5782
Received on Wednesday, 8 October 2008 12:48:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:07 GMT