Re: IDs first? RE: Last Call: 'Proposed Experiment: Normative Format in AdditiontoASCII Text' to Experimental RFC (draft-ash-alt-formats)

"Hallam-Baker, Phillip" <pbaker@verisign.com> Wed, 21 June 2006 01:53 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsruX-0003RZ-HL; Tue, 20 Jun 2006 21:53:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsruV-0003Og-1C for ietf@ietf.org; Tue, 20 Jun 2006 21:53:39 -0400
Received: from colibri.verisign.com ([65.205.251.74]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsruU-00008B-He for ietf@ietf.org; Tue, 20 Jun 2006 21:53:39 -0400
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id k5L1rWIR024012; Tue, 20 Jun 2006 18:53:32 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Jun 2006 18:53:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 20 Jun 2006 18:53:22 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD375A2CB2@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: IDs first? RE: Last Call: 'Proposed Experiment: Normative Format in AdditiontoASCII Text' to Experimental RFC (draft-ash-alt-formats)
Thread-Index: AcaUwjYTRKADcYSPTyKBr4Rvi0qnJQAE0RG0
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Keith Moore <moore@cs.utk.edu>
X-OriginalArrivalTime: 21 Jun 2006 01:53:23.0035 (UTC) FILETIME=[7A7942B0:01C694D5]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Cc: ietf@ietf.org
Subject: Re: IDs first? RE: Last Call: 'Proposed Experiment: Normative Format in AdditiontoASCII Text' to Experimental RFC (draft-ash-alt-formats)
X-BeenThere: ietf@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@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>
Content-Type: multipart/mixed; boundary="===============1693445265=="
Errors-To: ietf-bounces@ietf.org

The format is straight mime with one added feature, a content header to specify the url of the segment so that links in the document can be disambiguated. 

It should be an rfc, just need someone to get round to writing it up.

I may do that soon because I am looking into using mhtml as an archival format for notarized versions of html documents.

 -----Original Message-----
From: 	Keith Moore [mailto:moore@cs.utk.edu]
Sent:	Tue Jun 20 16:35:27 2006
To:	Hallam-Baker, Phillip
Cc:	ietf@ietf.org
Subject:	Re: IDs first? RE: Last Call: 'Proposed Experiment: Normative Format in AdditiontoASCII Text' to Experimental RFC (draft-ash-alt-formats)

> > I like the idea.  But it has to be compatible with software 
> > that people already have.  How many browsers that people 
> > actually use these days support MHTML?
> 
> It is supported in IE and Firefox and has been for about five years or so.

That might not be quite good enough, but it's close enough to warrant
further investigation.

> The format is currently defined by a Microsoft note but this can easily be made into an RFC, it is a widely supported standard extension of MIME.

What was wrong with RFC 2557?  How can we assume that this is a stable
format given that MS apparently felt they could change it on a whim?

> Creating one of these archives is easy, just view the HTML page and click 'save as archive'.

My copy of firefox doesn't seem to have that feature.

> Another point to consider, the only sustained objection being made to this proposal is that future generations may be unable to read the documents.
> 
> This particular objection cannot be made credibly with respect to Internet Drafts which expire in 6 months in any case. Nor do I think it is reasonable to require support for people using obsolete software in this case. If someone can't install the latest version of Firefox their ability to contribute to a WG is going to be negligible in any case.

Unfortunately, many IETF participants are expected by their employers
to use broken software.

As someone who has actually tried producing I-Ds in alternate formats,
I'm not sure that I agree that there's much benefit to having only I-Ds
use the new format.   People who review the document need to be able to
see something close to the version that will actually be published.  

Keith

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