Re: Problem with IANA MIME media types registry

Bruce Lilly <blilly@erols.com> Sun, 11 December 2005 15:42 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ElTLW-0002K0-W5; Sun, 11 Dec 2005 10:42:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ElTLU-0002Ja-Sx for ietf@megatron.ietf.org; Sun, 11 Dec 2005 10:42:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04299 for <ietf@ietf.org>; Sun, 11 Dec 2005 10:41:39 -0500 (EST)
Received: from ns5a.townisp.com ([216.195.0.140] helo=ns5.townisp.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElTM1-00026i-Gw for ietf@ietf.org; Sun, 11 Dec 2005 10:43:14 -0500
Received: from mail.blilly.com (dhcp-0-8-a1-c-fa-f7.cpe.townisp.com [216.49.158.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "marty.blilly.com", Issuer "Bruce Lilly" (not verified)) by ns5.townisp.com (Postfix) with ESMTP id B45B1299A4; Sun, 11 Dec 2005 10:42:32 -0500 (EST)
Received: from marty.blilly.com (marty.blilly.com [192.168.99.98] (may be forged)) by mail.blilly.com with ESMTP id jBBFgPqb016101(8.13.1/8.13.1/mail.blilly.com /etc/sendmail.mc.mail 1.26 2005/06/24 20:47:59) (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) ; Sun, 11 Dec 2005 10:42:29 -0500
Received: from marty.blilly.com (localhost [127.0.0.1]) (authenticated (0 bits)) by marty.blilly.com with ESMTP id jBBFgOA7016100(8.13.1/8.13.1/blilly.com submit.mc 1.3 2005/04/08 12:29:31) (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) ; Sun, 11 Dec 2005 10:42:24 -0500
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
To: mankin@psg.com
Date: Sun, 11 Dec 2005 10:42:22 -0500
User-Agent: KMail/1.9
References: <4k8p8p$k8s4a@mx07.mrf.mail.rcn.net>
In-Reply-To: <4k8p8p$k8s4a@mx07.mrf.mail.rcn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200512111042.23160@mail.blilly.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: iana@iana.org, webmaster@iana.org, ietf@ietf.org, ietf-types@alvestrand.no
Subject: Re: Problem with IANA MIME media types registry
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bruce Lilly <blilly@erols.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Sun December 11 2005 10:06, Allison Mankin wrote:
> Bruce, 
> 
> FYI, the other top-level media types are still there on their
> FTP site, so this looks like something went wrong with their web
> generating approach, whatever that is...
> 
> ftp://ftp.iana.org/assignments/media-types/
> 
> Allison
> 
> P.S.  I happened to have the FTP version on my radar.

Thanks for the information -- the index.html file at the ftp site
has a revision date of 23-Aug-2005, whereas the file served via
HTTP is dated 30-November-2005.  I would have expected the same file
to be served by both protocols, with index.html being the default
for HTTP.  That that is evidently not happening is yet another cause
for concern, as it means that different access methods yield
different registration information.  Possibly the IANA HTTP server
is sending the application data (only) instead of index.html.

I've taken the liberty of copying the lists and IANA to update the
information regarding the registry.

Best regards,
  Bruce Lilly

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf