Re: [spfbis] RFC6147 and RFC7208 interoperability issues

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 07 February 2022 15:25 UTC

Return-Path: <ajs@anvilwalrusden.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 8E3103A083C for <spfbis@ietfa.amsl.com>; Mon, 7 Feb 2022 07:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, 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 (1024-bit key) header.d=yitter.info header.b=Pyh4rHP3; dkim=pass (1024-bit key) header.d=yitter.info header.b=jflrkbUf
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 NypXuDr-3S2e for <spfbis@ietfa.amsl.com>; Mon, 7 Feb 2022 07:24:54 -0800 (PST)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D55903A0839 for <spfbis@ietf.org>; Mon, 7 Feb 2022 07:24:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id C90B4BD5C8 for <spfbis@ietf.org>; Mon, 7 Feb 2022 15:24:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644247463; bh=Yzk2sM/vr2upVxFK07N/4uX1ZJxTk5f4byYWKmQWww4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Pyh4rHP34TAmUFyIJj1B4v+GCgnPf/jXVnJFc6PFi9mmlSHhmgE3m171oM+qTAD+W 8oAgZMpCqxdsbhhUHUfa9x1mEpZl39+oyyDI6Sr88n3XxgoOKBi+17sba8YXI2pwRe 9OhjfhfP4JKii3jAJFZMQB5T2sAzh6zFWh/SCgAE=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ruv-LdDxbfsD for <spfbis@ietf.org>; Mon, 7 Feb 2022 15:24:22 +0000 (UTC)
Date: Mon, 07 Feb 2022 10:24:20 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644247462; bh=Yzk2sM/vr2upVxFK07N/4uX1ZJxTk5f4byYWKmQWww4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=jflrkbUf3mdD6YWaWb0Rz3jYK4WyG5ZUxNHhO87/lmJDTpH27ByfinwCU6jILzGWZ 0TmdvLFJLi+LnilRXPRbkC8cZNfXYh5TPjh3moL8UjHOzOX6lqeK0zu03Pkdx1qbKr idJ4g9L9X8Rfo2Ot23UcAfhxzsHhMZjZct99oPcc=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: spfbis@ietf.org
Message-ID: <20220207152420.iom45g3zrhzttdhn@crankycanuck.ca>
Mail-Followup-To: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <8021771.rLJEViv2lv@localhost> <85cb8ec0-4316-c4db-4aed-2d49fda46f49@posteo.de> <45673006.FIhfuaby8d@localhost> <20220206224715.kzynnbwkt5a26wii@crankycanuck.ca> <7ddee9f68efbef4bcf2dbfef69b0766a@leibzon.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <7ddee9f68efbef4bcf2dbfef69b0766a@leibzon.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/mP0HOxiUxymBKj2jDN3g-ogNH-E>
Subject: Re: [spfbis] RFC6147 and RFC7208 interoperability issues
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 07 Feb 2022 15:25:01 -0000

On Sun, Feb 06, 2022 at 04:42:07PM -0800, william@leibzon.org wrote:

>I'm curious, how does DNS64 inter-operates with DNSSEC?

Awkwardly.  There is a long discussion of it in the RFC.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com