Re: nonexistent-WG Last Call on MIME documents

John Gardiner Myers <jgm+@cmu.edu> Wed, 19 June 1996 21:16 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07913; 19 Jun 96 17:16 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07908; 19 Jun 96 17:16 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa28091; 19 Jun 96 17:16 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id QAA16489; Wed, 19 Jun 1996 16:57:12 -0400
Received: from po10.andrew.cmu.edu (PO10.ANDREW.CMU.EDU [128.2.10.110]) by list.cren.net (8.6.12/8.6.12) with ESMTP id QAA16472 for <ietf-822@list.cren.net>; Wed, 19 Jun 1996 16:56:50 -0400
Received: (from postman@localhost) by po10.andrew.cmu.edu (8.7.5/8.7.3) id QAA00862 for ietf-822@list.cren.net; Wed, 19 Jun 1996 16:56:49 -0400
Received: via switchmail; Wed, 19 Jun 1996 16:56:49 -0400 (EDT)
Received: from hogtown.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/testq0/QF.olm6Zvm00WBw00ZLd=>; Wed, 19 Jun 1996 16:56:28 -0400 (EDT)
Received: from hogtown.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/usr7/jgm/.Outgoing/QF.Ylm6Zry00WBw8aGbNk>; Wed, 19 Jun 1996 16:56:24 -0400 (EDT)
Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Wed, 19 Jun 1996 16:56:21 -0400 (EDT)
Message-Id: <Ulm6Zpy00WBwQaGbBW@andrew.cmu.edu>
Date: Wed, 19 Jun 1996 16:56:21 -0400
X-Orig-Sender: owner-ietf-822@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John Gardiner Myers <jgm+@cmu.edu>
To: ietf-822@list.cren.net
Subject: Re: nonexistent-WG Last Call on MIME documents
In-Reply-To: <17804.834760793@domen.uninett.no>
References: <17804.834760793@domen.uninett.no>
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

I had sent the following comments to the author of
draft-ietf-822ext-mime-hdrs-00.txt; I would like them resolved before
moving to IETF Last Call.

The first one is mostly editorial; the last two deal with the problem
that a mail reader technically needs to have an arbitrary amount of
lookahead in order to determine whether linear-white-space following
an encoded-word should be output or not.


>  75 characters, multiple 'encoded-word's (separated by CRLF SPACE) may

...(separated by CRLF LWSP-char)...

>       When displaying a particular header field that contains multiple
>       'encoded-word's, any 'linear-white-space' that separates a pair of
>       adjacent 'encoded-word's is ignored.  (This is to allow the use of

...'encoded-words's, any amount up to 75 octets of
'linear-white-space' that separate...

(at end of paragraph) Mail readers may choose to ignore between
adjacent 'encoded-word's sequences of 'linear-white-space' that are
longer than 75 octets.

-- 
_.John G. Myers		Internet: jgm+@CMU.EDU
			LoseNet:  ...!seismo!ihnp4!wiscvm.wisc.edu!give!up