Re: this seems to have become broken some time back

ned+ietf@mauve.mrochek.com Wed, 19 January 2011 04:34 UTC

Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 232D83A70C9 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 20:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 zxq5mKWTMg46 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 20:34:43 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 8FDD63A6F6B for <ietf@ietf.org>; Tue, 18 Jan 2011 20:34:43 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NWS5YPY0RK00I20G@mauve.mrochek.com> for ietf@ietf.org; Tue, 18 Jan 2011 20:37:21 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NWRL7QI6DS007CHU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 18 Jan 2011 20:37:17 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01NWS5YOMEMA007CHU@mauve.mrochek.com>
Date: Tue, 18 Jan 2011 20:23:22 -0800
Subject: Re: this seems to have become broken some time back
In-reply-to: "Your message dated Tue, 18 Jan 2011 21:12:11 -0500" <5444AF4B-7A0A-4DE7-9F06-67535B1F5ECE@hopcount.ca>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <E48F738E-F0EB-4A91-BAB1-E01F2A0CF9F9@isi.edu> <5444AF4B-7A0A-4DE7-9F06-67535B1F5ECE@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1295408802; i=@mrochek.com; bh=vfAe0HG0RJI4Nlabm7tAVe5JZbRw8LeahrRdagCCG+k=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=TJeH7YkyKYGIL3xp6aJLDw9i5queKsIqmPnXDIyLDClaW4Eh/RPC3jZASm7O+t0/a BonOWL41hIeuVgjpMBq131Rn/u8KszLnBbX07kSvB0/9tt+xADr0nmP9M/n+nHKVJV gGijXQr1Cj3DLvqKWbYEPx8XDw4rckw1lMVwCeOM=
Cc: bill manning <bmanning@sfc.keio.ac.jp>, IETF discussion list <ietf@ietf.org>, bill manning <bmanning@isi.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2011 04:34:45 -0000

> On 2011-01-18, at 15:03, bill manning wrote:

> > and I guess I am the only one who might still use it - but regardless, if its broken, it should ....  seems that the mail attachment (MIME) is no longer a copy of the draft in question, its a dummy text block.

> I don't think it was ever a copy of the draft in question; it has been an
> RFC1873-compliant Message/External-Body section as long as I have been
> watching. To draw from another random example that came through recently on
> i-d-announce:

> > Content-Type: Message/External-body;
> > 	name="draft-ietf-idr-bgp-identifier-13.txt"; site="ftp.ietf.org";
> > 	access-type="anon-ftp"; directory="internet-drafts"

That's an anon-ftp access type, which is described in RFC 2046 section
5.2.3.3. RFC 1873 defines the content-id access-type.

> I've never used a mail client that knows what to do with that, though.

The client I'm using right now (which I coauthored) is one of the very few with
support for external body dereferencing. It's too bad really; it's a very
useful feature, especially if the client does a good job of merging the
external reference into the message.

				Ned