Re: draft-ietf-fax-esmtp-conneg-08.txt
Keith Moore <moore@cs.utk.edu> Sat, 26 July 2003 16:02 UTC
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h6QG2vqt076567 for <ietf-smtp-bks@above.proper.com>; Sat, 26 Jul 2003 09:02:57 -0700 (PDT) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h6QG2v9l076566 for ietf-smtp-bks; Sat, 26 Jul 2003 09:02:57 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h6QG2qqt076558; Sat, 26 Jul 2003 09:02:53 -0700 (PDT) (envelope-from moore@cs.utk.edu)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org) by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 19gRVN-0001ua-00; Sat, 26 Jul 2003 09:02:45 -0700
Date: Sat, 26 Jul 2003 12:01:50 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: moore@cs.utk.edu, presnick@qualcomm.com, tamura@toda.ricoh.co.jp, ietf-smtp@imc.org, ietf-fax@imc.org, toyoda.kiyoshi@jp.panasonic.com
Subject: Re: draft-ietf-fax-esmtp-conneg-08.txt
Message-Id: <20030726120150.3cf1875d.moore@cs.utk.edu>
In-Reply-To: <17216546082.20030716140831@brandenburg.com>
References: <20030626.085226.01368429.tamura@toda.ricoh.co.jp> <20030715.144343.01366541.tamura@toda.ricoh.co.jp> <p06001b00bb3ae5ee54a0@[81.160.98.150]> <17216546082.20030716140831@brandenburg.com>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>
> PR> Why is the CONPERM command necessary? Isn't putting Content-Convert > PR> parts in a message implicit permission to do such transformations? Or > PR> is CONPERM really just signalling the server to go look inside the > PR> message? > > Without the ESMTP option, SMTP relays must look into the message > content, to determine whether conversion is permitted. Hence we decided > to put a basic permission mechanisn into the explicit transfer > mechanism, with the fine-grained permission detail in the content. also, messages can be forwarded, but the permission granted by the original sender to perform conversions might not be desired by the party forwarding the message. (having the content-convert information in the message body at all seems likely to cause problems later - ideally it should be entirely in the envelope. however I understand why it's in the message body.)
- draft-ietf-fax-esmtp-conneg-08.txt Hiroshi Tamura
- Re: draft-ietf-fax-esmtp-conneg-08.txt Keith Moore
- Re: draft-ietf-fax-esmtp-conneg-08.txt Keith Moore
- Re: draft-ietf-fax-esmtp-conneg-08.txt Dave Crocker
- Re: draft-ietf-fax-esmtp-conneg-08.txt Pete Resnick
- Re: draft-ietf-fax-esmtp-conneg-08.txt Dave Crocker
- Re: draft-ietf-fax-esmtp-conneg-08.txt Valdis.Kletnieks
- Re: draft-ietf-fax-esmtp-conneg-08.txt Dave Crocker
- Re: draft-ietf-fax-esmtp-conneg-08.txt Hiroshi Tamura
- Re: draft-ietf-fax-esmtp-conneg-08.txt Keith Moore
- Re: draft-ietf-fax-esmtp-conneg-08.txt Dave Crocker
- Re: draft-ietf-fax-esmtp-conneg-08.txt John C Klensin
- Re: draft-ietf-fax-esmtp-conneg-08.txt Valdis.Kletnieks
- Re: draft-ietf-fax-esmtp-conneg-08.txt Dave Crocker