Re: Last Call: draft-ietf-usefor-usepro (Netnews Architecture and Protocols) to Proposed Standard

SM <sm@resistor.net> Thu, 25 September 2008 22:36 UTC

Return-Path: <owner-ietf-usefor@mail.imc.org>
X-Original-To: ietfarch-usefor-archive@core3.amsl.com
Delivered-To: ietfarch-usefor-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0D543A677C for <ietfarch-usefor-archive@core3.amsl.com>; Thu, 25 Sep 2008 15:36:48 -0700 (PDT)
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=[AWL=0.000, 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 sHUKPRg5JFXH for <ietfarch-usefor-archive@core3.amsl.com>; Thu, 25 Sep 2008 15:36:48 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id A8B743A67A3 for <usefor-archive@ietf.org>; Thu, 25 Sep 2008 15:36:44 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m8PMYNs3035415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Sep 2008 15:34:23 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m8PMYNDf035414; Thu, 25 Sep 2008 15:34:23 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m8PMYCao035404 for <ietf-usefor@imc.org>; Thu, 25 Sep 2008 15:34:23 -0700 (MST) (envelope-from sm@resistor.net)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.3/8.14.3) with ESMTP id m8PMY1sL029589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Sep 2008 15:34:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1222382051; x=1222468451; bh=bviMXgwDLmZFQQml9oMbbtCWtj2pc+18aykn bGZBxGA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=QgUYAh1CbFIOKURQD3g5K4PXmd XjPT8o09rIElE7HR2nQywVyoqS7VUY6UcFXkTYuG4hao0GxXnh5CWaSROCW+BV0Zh9Q pClINBkuIFq2c9BrzCbiQmfHkM8IecJX/JXjeCNfz/N52sWLSo75ol2xqn7tEwtj8hq 5vBywOY2dtE=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=vXpOe0jlL0+O+wrZg6ftiMP1GDFTKiybfvuTCD/CJ5xQwLo1e7fC75N0nAG3bVudb zFlIn1wI/vdY6cFCE0pG8oRpwtaSj41HvPe8ky2KBUk90/e268Cl2WHufea67fA9d5o XYhPS4BfTy12VjJQzHQvBHOhaJnd6NXG64c2Il0=
Message-Id: <6.2.5.6.2.20080925144536.03013e58@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 25 Sep 2008 15:33:40 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: draft-ietf-usefor-usepro (Netnews Architecture and Protocols) to Proposed Standard
Cc: ietf-usefor@imc.org, Russ Allbery <rra@stanford.edu>
In-Reply-To: <87ej39dkbn.fsf@windlord.stanford.edu>
References: <6.2.5.6.2.20080923215214.030a7ce0@resistor.net> <87ej39dkbn.fsf@windlord.stanford.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>

Hi Russ,

[I-D author requested Cc]

At 19:35 24-09-2008, Russ Allbery wrote:
>Well, I find that statement unobjectionable but essentially meaningless,
>in that I don't think the document says anything substantively different
>including that statement than without it.  But if it makes others feel
>more comfortable, I don't object to including it.

If you don't find that the addition changes anything, there is no 
point in including it.  The point was that the author address should 
be fixed if it's not according to the specifications for that 
medium.  I did not elaborate as the medium is not restricted to mail.

>That provision doesn't document what happens in practice, nor would it be
>possible to limit the header additions.  (For example, it's essentially
>impossible to send something as an e-mail message without adding Received
>headers.)  I prefer to give implementors a better idea of what to expect,
>and in practice arbitrary headers will get added by the transit through
>the mail system, including all sorts of X-* headers, trace headers, and
>random detritus from spam filters.

Okay.

>We could easily remove that specific header field name from the example
>and instead just say:
>
>     The news-to-mail gateway adds an X-* header field to all messages it
>     generates.  The mail-to-news gateway discards any incoming messages
>     containing this header field.
>
>Would that be an improvement?

Yes, that's better.

Regards,
-sm