IETF Logo Mail Archive

Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues

Klaus Frank <klaus.frank@posteo.de> Mon, 07 February 2022 13:21 UTC

Return-Path: <klaus.frank@posteo.de>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3786D3A0E63 for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 05:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=posteo.de
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 UxedMYPhXAv5 for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 05:21:11 -0800 (PST)
Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 050EE3A0E61 for <behave@ietf.org>; Mon, 7 Feb 2022 05:21:10 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 3EB91240026 for <behave@ietf.org>; Mon, 7 Feb 2022 14:21:06 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644240067; bh=dqqf+B+eO/PzrMvb0I/Q9VnCqoM5vaW/YUvpenIGxTs=; h=Date:Subject:To:From:From; b=VxX23V/RPoRiZMcuPUrXRr3R7oFOjG/lA9nRw2qjPLgC6imdsWSZ7q4nwY8EChAHu ffYo12uMJMxBC2UP8bySy56u0Fu+nD6Ra2RKVT3hNe+yQI4mOn8cFsQWrouA/5kx0O lDaawWR8ci36KgAXu8VqDY51O+gwDnxvtlqSNEl12AFg6jHyr9uuP2djiDG9VefBly yMe0LlLo+gv+VjGrj88uIr6T5WhZteh5jlLOlgidntiT9cs5eunRIOQ1ZNyxZ9Uuwd 8KobV4UMfOzUbjnDFVEASAfhVO5WEtQqsBlFVm8JTSKFhSfRd3Eru+gaXTbTGHLeyB ON5WC5fAC0jLQ==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsmxG3DCkz6tp9 for <behave@ietf.org>; Mon, 7 Feb 2022 14:21:05 +0100 (CET)
Message-ID: <828f848d-5a16-5174-5f16-7527e33ba10f@posteo.de>
Date: Mon, 07 Feb 2022 13:21:05 +0000
MIME-Version: 1.0
Content-Language: de-DE
To: behave@ietf.org
References: <dc15ccc0-3a67-563d-cf0f-08dcc7575fd2@it.uc3m.es> <077D662F-5E6D-44F5-8DD3-B58D8B535C5D@network-heretics.com>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <077D662F-5E6D-44F5-8DD3-B58D8B535C5D@network-heretics.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms020102070108040604060401"
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/VeF88DCF7kM-3GSQeBxAQ1MzQgc>
Subject: Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2022 13:21:16 -0000

How should that be a feature? It's clearly a bug...

On 2022-02-07 14:12, Keith Moore wrote:
>
> Sent from my iPhone
>
>> On Feb 7, 2022, at 1:42 AM, marcelo bagnulo braun <marcelo@it.uc3m.es> wrote:
>>
>> I guess one operative question is whether this issue can be dealt with an errata or should require an update in the spec.
> Neither.  That SPF and TXT records are not altered is a feature, not a bug.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

v2.23.0 | Report a Bug | By Email