Re: [spfbis] SPDF Domain Name Syntax

S Moonesamy <sm+ietf@elandsys.com> Tue, 03 May 2016 06:45 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B347712B011 for <spfbis@ietfa.amsl.com>; Mon, 2 May 2016 23:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.786
X-Spam-Level:
X-Spam-Status: No, score=-2.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=Oz1Wxnu9; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=HujjAVky
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cv1kVUQdf_3a for <spfbis@ietfa.amsl.com>; Mon, 2 May 2016 23:45:31 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4557512D126 for <spfbis@ietf.org>; Mon, 2 May 2016 23:45:31 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.49.11]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u436jFHC011766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 May 2016 23:45:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1462257928; x=1462344328; bh=CCc1b1tXNNv7Zy2jSC0TVvS7BFOwHoOcMwad9ly7h58=; h=Date:To:From:Subject:In-Reply-To:References; b=Oz1Wxnu9tDR9O5CIu6PenNZWoQ8bojlPmqr1CoqGCBDMAkNr1es39xTBdj0XudtuQ /al5Jc5P9bqxqADjsc9PiuwACJkqoYHKAcMdXTIIWS+af7YSmR01RiOVV86oPak7Mc PeT5Y0jHPQitIER6+o/fFowxdsSClWe0sI+Iztr4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1462257928; x=1462344328; i=@elandsys.com; bh=CCc1b1tXNNv7Zy2jSC0TVvS7BFOwHoOcMwad9ly7h58=; h=Date:To:From:Subject:In-Reply-To:References; b=HujjAVkyYUPTFBWQsLULPs3nXssFawXP07Y/GmEf5qux4nmsjvJ0KlJ2PHT7M2/ju BSYKz++233dlmBzqZHh4Nia0tKfuYCqrDJovOstlJJ3yR/UeBvuQQkQ8vf2tQ3TmG9 XMRzXFhnvklInx+Sqt/DiXLGahuObQBEef+aOd/g=
Message-Id: <6.2.5.6.2.20160502233007.0dae73b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 02 May 2016 23:44:55 -0700
To: Tobias Perschon <tobias@perschon.at>, spfbis@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <AM4PR09MB065930FACFA477EA02EE919ADD790@AM4PR09MB0659.eurpr d09.prod.outlook.com>
References: <AM4PR09MB065930FACFA477EA02EE919ADD790@AM4PR09MB0659.eurprd09.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/spfbis/rZKRwHNPtWko8QFrg5et7QuYz74>
Subject: Re: [spfbis] SPDF Domain Name Syntax
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spfbis/>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2016 06:45:32 -0000

Hi Tobias,
At 11:55 02-05-2016, Tobias Perschon wrote:
>I have a question regarding RFC 7208. Is a domain name e.g. for an 
>"a:" directive supposed to be a FQDN; more precisely: can a domain 
>name contain a trailing dot?
>e.g.: should this be able to be handled by any software that implements spf:
>v=spf1 a:domain.com. ~all
>
>Postfix for example has no problems with an domain name with 
>trailing dot but I have found a software "mdeamon" which cannot 
>perform a dns lookup if the domain name is a FQDN (with trailing 
>dot). I wrote the developers but they say, they think it's not a bug 
>in their software because "all of the pages about SPF, don't talk 
>about domains with trailing dot" and the RFC does not make it 
>explicit if a FQDN is acceptable.

Section 4.8 of RFC 7208 discusses about "domain-spec".  The issue is 
whether the software implements RFC 7208 and, if so, whether it 
adheres to the ABNF defined in RFC 7208.  The software should be able 
to handle the above-mentioned example.

Regards,
S. Moonesamy