Re: [apps-discuss] WGLC on draft-ietf-appsawg-rfc5451bis-00

Alessandro Vesely <> Thu, 16 May 2013 15:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CF5DA21F90B3 for <>; Thu, 16 May 2013 08:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.519
X-Spam-Status: No, score=-3.519 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_54=0.6, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lZWPJClH4xuh for <>; Thu, 16 May 2013 08:22:22 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3195F21F8FDD for <>; Thu, 16 May 2013 08:22:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=beta; t=1368717735; bh=xD+BkjwcDFY3V//maoF7wu0VNDXsLBxNcwr5LbIxyCE=; l=1647; h=Date:From:To:CC:References:In-Reply-To; b=StK4QfGpSCBc50BGXBjpPiQacUy3ks+gyOUs2qBc2nwK4eBSa9erklwt2oAdnjHkk FSFnGzQEuVF2/JmrOH33uezzkfA2Yp0+YCUbMGDLmo5ees2hEeJXkzbmayBCNt3j9G sSwcw9MTKqpEemfsU6qSmpBOEBVYUBR6uomb7xxU=
Authentication-Results:; auth=pass (details omitted)
Received: from [] (printer.tana []) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by with ESMTPSA; Thu, 16 May 2013 17:22:15 +0200 id 00000000005DC02B.000000005194F9A7.00002702
Message-ID: <>
Date: Thu, 16 May 2013 17:22:15 +0200
From: Alessandro Vesely <>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Murray S. Kucherawy" <>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: Sam Varshavchik <>, IETF Apps Discuss <>
Subject: Re: [apps-discuss] WGLC on draft-ietf-appsawg-rfc5451bis-00
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 May 2013 15:22:36 -0000

On Thu 16/May/2013 16:27:00 +0200 Murray S. Kucherawy wrote:
> On Thu, May 16, 2013 at 6:24 AM, Alessandro Vesely <> wrote:
>> One is the DNS White List (dnswl) method, used by Courier (mentioned
>> in Appendix E).  It writes:
>>   Authentication-Results:;
>>       dnswl=pass
>>       policy.ip=
>>       policy.txt=""
>> Since it was me who suggested to use Authentication-Results, I think
>> it's up to me to register that.  I'm waiting for this I-D to get
>> published so as to avail of Designated Expert rather than IETF review.
> To be consistent with the other registered methods, the policy.ip and
> policy.txt things wouldn't be included.  A-R is meant to provide results
> and return details of what visible parts of a message were evaluated (e.g.,
> header fields, SMTP properties).  The client IP isn't one of those, nor is
> resulting text.

That's not a client IP, but the return value of the lookup.  Passing
that value to downstream filters is the whole point of adding this
header field, otherwise it would have to be looked up again.  Details
such as DKIM's key length, IMHO, are often in a comment because they
are of minor importance, not because they are not a visible part of
the message.)

The policy.txt is important as it contains a domain name.  Albeit A-R
is not intended to be restricted to domain-based authentication,
that's by far the most common case, a granularity that was settled
many years ago.  By indicating a "somewhat responsible" entity, the
method is semantically consistent with that strategy.