Jeffrey Hutzelman wrote:
> On Thu, 2013-08-01 at 01:10 -0700, Amanda Baber wrote:
>> Hi,
>>
>> The link in RFC3315 is actually incorrect -- it should have been
>> http://www.iana.org/assignments/enterprise-numbers, without the file
>> extension, and there's an erratum abou
Hi, Amanda,
In my experience, at some point, IANA was instructing authors to replace
registry URLs (i.e., URLs to specific registries) with a generic pointer to
http://www.iana.org instead. This had been based on text from RFC 5226, namely
[1] and [2].
Before that there were URLs identifying t
I sent IANA a list of 45 iana.org URLs found in the RFCs that generate
404 NOT FOUND (along with the number of the RFC(s) where that URL was
found). Amanda said she'd pass the list on to "the redirector".
Tony
On 8/1/2013 2:48 PM, Jeffrey Hutzelman wrote:
> Nonetheless, it's an existing URL i
Hi,
The link in RFC3315 is actually incorrect -- it should have been
http://www.iana.org/assignments/enterprise-numbers, without the file extension,
and there's an erratum about this. HTML was generally (I say "generally"
because there may be exceptions Michelle would know about) reserved for f
On Thu, 2013-08-01 at 01:10 -0700, Amanda Baber wrote:
> Hi,
>
> The link in RFC3315 is actually incorrect -- it should have been
> http://www.iana.org/assignments/enterprise-numbers, without the file
> extension, and there's an erratum about this. HTML was generally (if
> not exclusively) reserve
> Hi,
> The link in RFC3315 is actually incorrect -- it should have been
> http://www.iana.org/assignments/enterprise-numbers, without the file
> extension, and there's an erratum about this. HTML was generally (if not
> exclusively) reserved for files that needed to include links to registrati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/1/13 2:01 PM, John Curran wrote:
> On Jul 31, 2013, at 10:11 AM, Peter Saint-Andre
> wrote:
>>
>> That's true, but cool URIs don't change:
>>
>> http://www.w3.org/Provider/Style/URI.html
>
> Even cooler would have been URN's (e.g.
> urn:ietf:e
On Jul 31, 2013, at 10:11 AM, Peter Saint-Andre wrote:
>
> That's true, but cool URIs don't change:
>
> http://www.w3.org/Provider/Style/URI.html
Even cooler would have been URN's (e.g. urn:ietf:enterprise-numbers),
which was designed specifically as a persistent handle to information
(ref: ht
Hi,
The link in RFC3315 is actually incorrect -- it should have been
http://www.iana.org/assignments/enterprise-numbers, without the file extension,
and there's an erratum about this. HTML was generally (if not exclusively)
reserved for files that needed to include links to registration forms .
> On 7/31/13 4:06 PM, Barry Leiba wrote:
> >> I just followed http://www.iana.org/assignments/enterprise-numbers.html
> >> From RFC3315 (DHCPv6)'s reference section. Ten years later, the URL
> >> doesn't work.
> >>
> >> I know that things were reworked when we went to XML based storage, but
> >> I
> From: Barry Leiba
> They have: they are keyed off the suffix-less URIs. That's why they
> want us to use those.
That doesn't change the point that breaking URLs in _previously-published,
static_ documents is a Bad Thing.
Noel
>>> I discovered that dropping the .html gets me the right data at:
>>> http://www.iana.org/assignments/enterprise-numbers
>>
>> Yes: that's the form that IANA would like you to use. They changed
>> their registries from HTML to XML, and the URLs changed.
>
> That's true, but cool URIs don't cha
On 7/31/13 4:06 PM, Barry Leiba wrote:
>> I just followed http://www.iana.org/assignments/enterprise-numbers.html
>> From RFC3315 (DHCPv6)'s reference section. Ten years later, the URL
>> doesn't work.
>>
>> I know that things were reworked when we went to XML based storage, but
>> I thought that
> I just followed http://www.iana.org/assignments/enterprise-numbers.html
> From RFC3315 (DHCPv6)'s reference section. Ten years later, the URL
> doesn't work.
>
> I know that things were reworked when we went to XML based storage, but
> I thought that the old URLs would at least have a 301 error
I just followed http://www.iana.org/assignments/enterprise-numbers.html
From RFC3315 (DHCPv6)'s reference section. Ten years later, the URL
doesn't work.
I know that things were reworked when we went to XML based storage, but
I thought that the old URLs would at least have a 301 error on them.
15 matches
Mail list logo
