Re: [apps-discuss] Slash and version number in Authentication-results: header field

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 21 May 2013 21:57 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B077021F9603 for <apps-discuss@ietfa.amsl.com>; Tue, 21 May 2013 14:57:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9OO0QYY1-uYj for <apps-discuss@ietfa.amsl.com>; Tue, 21 May 2013 14:57:49 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 147C421F95FD for <apps-discuss@ietf.org>; Tue, 21 May 2013 14:57:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1369173468; d=isode.com; s=selector; i=@isode.com; bh=e3n3OuPmocwcLXgCCW2YAZ2u2UyMArqUiVd1CSq6JmI=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=dUWEKjspFvbdt+zUf7iy1pHGz+28ij+dOaYIaICD7CuILX5yx6fro+JN33+qQrCJ2uC55f aArofoUnpz3WIv4/lXvA0OhCJLQOuS4SA5owJPXneQgJiMc/VfC8lSh8EXM4VHEl7LKDms hDdumMpO4stezLRCp94gZAkYj63w76I=;
Received: from [172.20.10.2] ((unknown) [212.183.140.62]) by statler.isode.com (submission channel) via TCP with ESMTPA id <UZvt1AA6F2tk@statler.isode.com>; Tue, 21 May 2013 22:57:45 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <519BE7D4.6070504@isode.com>
Date: Tue, 21 May 2013 22:32:04 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: S Moonesamy <sm+ietf@elandsys.com>
References: <CAL0qLwZuMOky2rLBm4UYhgNJmyXaPyO25WhBGrrgK4DUKcAWqg@mail.gmail.com> <20130519052116.75996.qmail@joyce.lan> <CAL0qLwaDwgyKH4DV=s9djw2pf7ULHPzbDn8Unhd_rJLbMaMd1Q@mail.gmail.com> <alpine.BSF.2.00.1305191104290.85717@joyce.lan> <6.2.5.6.2.20130519232054.06b2a318@resistor.net>
In-Reply-To: <6.2.5.6.2.20130519232054.06b2a318@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Slash and version number in Authentication-results: header field
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 21:57:53 -0000

On 20/05/2013 08:14, S Moonesamy wrote:
> Hi Alexey,
>
> Scott Kitterman mentioned [1] that the following:
>
>   authres-header = "Authentication-Results:" [CFWS] authserv-id
>     [ [CFWS] "/" [CFWS] authres-version ]
>
>  'is an incompatible change and if you really want to make it, you should
>   bump the version number.  I checked and with authres, your example is
>   mis-parsed.
>
>     Authentication-Results: example.org/1; none
>
>   In this example, the authserv-id is "example.org", but authres, 
> using the
>   RFC 5451 ABNF parses this and determines the authserv-id is 
> "example.org/1"'
>
> Murray Kucherawy commented that he has "yet to see a single 
> implementation that includes a version number in its output, though 
> there are some that do look for it" [2].  John Levine responded that 
> his implementation does [3].  He also mentioned that the introduction 
> of the slash (see ABNF) creates an incompatibility.
>
> There is also the following in Section 5 of 
> draft-ietf-appsawg-rfc5451bis-02:
>
>   "An MTA SHOULD remove any instance of this header field bearing a
>    version (express or implied) that it does not support."
>
> Will the addition of the slash cause an interoperability issue?

It looks like it might. I haven't implemented the spec yet (although I 
intend to), so this would not affect my [yet-to-be-written] implementation.

> Regards,
> S. Moonesamy
>
> 1. 
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg09460.html
> 2. 
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg09463.html
> 3. 
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg09465.html
>