
From klaus.frank@posteo.de  Sun Feb  6 10:09:28 2022
Return-Path: <klaus.frank@posteo.de>
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 1B3E43A0B38 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:09:28 -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=unavailable 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 BdFrZ08-Z1WY for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:09:19 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 44A5A3A0B72 for <spfbis@ietf.org>; Sun,  6 Feb 2022 10:09:19 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id 61EAB240104 for <spfbis@ietf.org>; Sun,  6 Feb 2022 19:09:16 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644170956; bh=rnzPtNVVEr4g7RWlAU/mtH90s4IagqICOEYD2omDIy0=; h=Date:To:From:Subject:From; b=gQQA0lmmIEnEDvP7LATptI1VGjJpN716lIDKlOYP4Z60RRemeuiSDOeAS2tLG/GZ2 WpXDBYtNiRk17qd1UYUPp/UD5sJSoLE4nZqGfp6UA2tyWKA2pzLcR1A6JyJ15QQsoK BCC+YVKro2K7vkXwdT7NdAuVvyLb7sFIvHXAqniwF8DyrlaXGDPSTyXcNU956nXTd1 djsl9+aTXeM2YsQggOHYk//O4TaxWi5aMQi01nUQP21uaoM5Te/O7D1Dgmb9GD8fPR WkCiktAm8eVbPDp6+QwCDPVF36l+cGD58waOQ0Rfd7LmwQCU1NLn7QvEmG/G6KfDGA isjOnFp8LgK8A==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsHND0CMQz6tmG; Sun,  6 Feb 2022 19:09:16 +0100 (CET)
Message-ID: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de>
Date: Sun,  6 Feb 2022 18:09:13 +0000
MIME-Version: 1.0
Content-Language: en-US
To: behave@ietf.org, spfbis@ietf.org
From: Klaus Frank <klaus.frank@posteo.de>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms090706070609010002080607"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/ZqWmiOrnUY0aQo_Ai5J1CZccutg>
Subject: [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: Sun, 06 Feb 2022 18:11:27 -0000

This is a cryptographically signed message in MIME format.

--------------ms090706070609010002080607
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

we had some issues with SPF and a mail server that was behind 
NAT64+DNS64. I at first thought that it was just a misconfiguration. But 
after the DNS64 server seamed to work as intended I went to the 
implementation and the RFC. Thereby while reading RFC6147 I stumbled 
across section 5.3.3 which says "All other RRs MUST be returned 
unchanged." which is the cause of my issues. This section is basically 
ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64 
implementations from addressing this limitation.

Would it be possible to create an extension to RFC6147 that mandates SPF 
record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in 
IPv6 only environments won't be able to work as expected.

Like:
If the DNS64 server receives a SPF-record (within either the TXT-RR or 
the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites 
the ipv4 address according to the same rules as A-records are and 
synthesizes a new SPF record within the response that contains 
additional "ip6" entries. The original "ip4" should not be removed from 
the response.

Sincerely,
Klaus Frank


--------------ms090706070609010002080607
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYxODA5MTRaME8GCSqGSIb3DQEJBDFCBECair8rfLpp3pZZtm0ERyqE
8sq+436Xnpr3Nyd/kjDpt/486yCklS+yxZAqjx0/WzprfAxONi4souyrIi1RXdknMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICACIfpfki
p3pniNWWHGGeHdl7DEel9kfOD6SxZ9f8W9Fb7/Nh21wqp39rezYAPc7bS3Nr2JnTLIriRItv
ozSGtRPGN8RbwCU4tyjQwd9EUvrF3JTHxptkRFBp+odvifk6TyZ/i0koztsHg6+++u+Y5MnU
VOMjdjRxrKgm2CNytf4V+uWj4HDjb+KEy7CrbbYpDuFgrD7Euq7xaMzm/KyGcGS9lP3iOW1T
UqryZhIXUn4mY4gAlXr+1FnCWdKm3C07Pst2bM19+ejglrgsI7kBcKIO9g7ydVthDjaZZ4nj
SnmtlHb4RqWT4AaE2eobUNJYtc9kV9hH3QLpNOx08Qxk+2A3VofnorEL5IWm46lRWnfqJRhB
q2a3z9KAnRliJXcZjiFmYyB71LRIOyU/dzOz3JcOgTxOy1PaAdNZubVRM75kYxNWHM68yXZp
ekVfox5fkoe0rMuiTcvWH5O0wGRPdg8QiYM4XttMj1QDGLX1rgXDHzqDB2EAmXuE9/2K/wj4
XyktB+wgYRmpwhScRMMMWXzYKCWcbS4hMSBbb8Dr4LSM0fyoQJPIazGhojXQc/CP2mAsmyw/
KjKmtcCrlSzNQZ2nU3KEyBM4fUkiSDlnThUh6TO3UlxiJIyBwGrpKf0voLJgWHgKHDGhe6H9
FnV0aYXHtdIzQzpaaHD8lD/Kt9zhAAAAAAAA
--------------ms090706070609010002080607--


From nobody Sun Feb  6 10:25:25 2022
Return-Path: <spf2@kitterman.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 923833A0B7F for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=SB2Tm71k; dkim=pass (2048-bit key) header.d=kitterman.com header.b=Hcr2DEPV
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 9VSLg9nwuC8J for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:25:17 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4918F3A0B7C for <spfbis@ietf.org>; Sun,  6 Feb 2022 10:25:17 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id A1D0BF80277 for <spfbis@ietf.org>; Sun,  6 Feb 2022 13:25:11 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1644171911; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=8N7jMYAuxCLq83OdfoaTtD1yj/w7l334qJgjosk04fY=; b=SB2Tm71kWaPk8XHwjCve5+ANFhsPQlqKSR7XtHFVcJkl2lZj6tfVNd6olRTPqrHnhJcfr S+wicElEqxu+yGdCA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1644171911; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=8N7jMYAuxCLq83OdfoaTtD1yj/w7l334qJgjosk04fY=; b=Hcr2DEPVEDwBpu79kb6pPM85ncc09CT+sZau9yIW1nFvMgNFrInWykElNF53qjBNClryC 4kLKWKelSd6+cJInC21izimfTP69Ksd8b+lnO2I3M909eoT63WB/BIIy5lPJEfP/P1kJwMl f/Qo5j7cHUk0Rk6fc7xBVLHiDCNuh4LsQB80/1GJv77qF1bPJAFHC4eOslfI+D7kwbRf+oK tWasU1Zqk9yTu8/hrwGLFV6md7U/fpqHDsW3dn22xc+TDqZl4JG6/VJph2cd7kVbBtXDnoQ ZjMMA1oyrvTWxnMHjYTpO6tk0bI4g/yLozsMSIeQMsKNu0Q5dsA78OR5lxVg==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 8224AF801A9 for <spfbis@ietf.org>; Sun,  6 Feb 2022 13:25:11 -0500 (EST)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Sun, 06 Feb 2022 13:25:11 -0500
Message-ID: <2098569.QsC3VX2HWt@localhost>
In-Reply-To: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/Z9y9qiqD5skrS2-y-HuU6Zh9GjI>
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: Sun, 06 Feb 2022 18:25:23 -0000

On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote:
> Hi,
> 
> we had some issues with SPF and a mail server that was behind
> NAT64+DNS64. I at first thought that it was just a misconfiguration. But
> after the DNS64 server seamed to work as intended I went to the
> implementation and the RFC. Thereby while reading RFC6147 I stumbled
> across section 5.3.3 which says "All other RRs MUST be returned
> unchanged." which is the cause of my issues. This section is basically
> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
> implementations from addressing this limitation.
> 
> Would it be possible to create an extension to RFC6147 that mandates SPF
> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
> IPv6 only environments won't be able to work as expected.
> 
> Like:
> If the DNS64 server receives a SPF-record (within either the TXT-RR or
> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
> the ipv4 address according to the same rules as A-records are and
> synthesizes a new SPF record within the response that contains
> additional "ip6" entries. The original "ip4" should not be removed from
> the response.

What's preventing the SPF record publisher from solving this problem by adding 
the ip6: mechanisms themselves?  Perhaps I don't understand the issue you are 
raising.  Would you please clarify what it is you're asking be done that an 
administrator can't do on their own?

Scott K



From nobody Sun Feb  6 10:31:21 2022
Return-Path: <klaus.frank@posteo.de>
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 6E5EB3A0BA7 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:31:18 -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 xnsYJNvE724r for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:31:12 -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 C0F273A0BA4 for <spfbis@ietf.org>; Sun,  6 Feb 2022 10:31:11 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout01.posteo.de (Postfix) with ESMTPS id B7187240026 for <spfbis@ietf.org>; Sun,  6 Feb 2022 19:31:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644172268; bh=iN+roM4pLXdOvS5wAv19yp/lr/lLqUcBIzbumLwxL+U=; h=Date:Subject:To:From:From; b=asf31Jr/NybjRSnSRXpYb6I7yOajkYxm5KcDOugqnTnpwXfgQoBxNB+ywUeYZDVz5 bq5CILToHt/kUe2uO7VWDEhAn5vAsJNKzB/wh6e6+/L4eVMB8PVX0w9rbizFLvW2aZ uOyT+fENqP21UjY3XYjSRfqhXzXBGl3BarLoOTpnvzo3X80DQ1P7IHD/NWEF2bqJ4U pIfxDXWnc4AVWyyVCy4RC3O1KEHq/ZoMy2CP4pmYTAK8D/x3kcavhagOcFDxyLtufg XI6gDSWNyh07Wb6OonBMmgXtSDfe+YUAg7OtQ9SkJtayAI6hGAdrFp1QnF+WXUWtZm CX/2/4YpRhr5g==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsHsR5N7lz6tmq for <spfbis@ietf.org>; Sun,  6 Feb 2022 19:31:07 +0100 (CET)
Message-ID: <ae4f7b97-3f78-aa9c-4274-025d29622269@posteo.de>
Date: Sun,  6 Feb 2022 18:31:06 +0000
MIME-Version: 1.0
Content-Language: de-DE
To: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <2098569.QsC3VX2HWt@localhost>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms010402020309080001090708"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/O7QnCYt0OCmGUDdR5Dub6rxtUz0>
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: Sun, 06 Feb 2022 18:31:19 -0000

This is a cryptographically signed message in MIME format.

--------------ms010402020309080001090708
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

the DNS64 record is a syntetic dns record that is created by the 
resolver to fill in a missing AAAA-RR for responses to make the IPv4 
internet reachable from IPv6 only networks. Basically the issue is that 
the recipient admin would have to make a change on the sending domains 
side depending on the recipients infrastructure.

Sincerely,
Klaus Frank

On 2022-02-06 19:25, Scott Kitterman wrote:
> On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote:
>> Hi,
>>
>> we had some issues with SPF and a mail server that was behind
>> NAT64+DNS64. I at first thought that it was just a misconfiguration. But
>> after the DNS64 server seamed to work as intended I went to the
>> implementation and the RFC. Thereby while reading RFC6147 I stumbled
>> across section 5.3.3 which says "All other RRs MUST be returned
>> unchanged." which is the cause of my issues. This section is basically
>> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
>> implementations from addressing this limitation.
>>
>> Would it be possible to create an extension to RFC6147 that mandates SPF
>> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
>> IPv6 only environments won't be able to work as expected.
>>
>> Like:
>> If the DNS64 server receives a SPF-record (within either the TXT-RR or
>> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
>> the ipv4 address according to the same rules as A-records are and
>> synthesizes a new SPF record within the response that contains
>> additional "ip6" entries. The original "ip4" should not be removed from
>> the response.
> What's preventing the SPF record publisher from solving this problem by adding
> the ip6: mechanisms themselves?  Perhaps I don't understand the issue you are
> raising.  Would you please clarify what it is you're asking be done that an
> administrator can't do on their own?
>
> Scott K
>
>
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms010402020309080001090708
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYxODMxMDdaME8GCSqGSIb3DQEJBDFCBEDRbxm68DfhtE/fGYPJVaMk
As8FJl1q/iJdN6ytrLHPNBWmroClZbAQ9EKj6dxKm+sgOwpFQgtzvmYJLdD0j9l9MGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAFNcQjnD
rAUVf+jldLxDIJ/MI9vpn61qRFyqeuDgI+065aDD+wJSvR6EFqJnuOBkDLo8HNr2yJIVYHWB
rp3UoPYFm7iNfjKbqK05W5RSy9f301ghE5Znqwwyqi/IurNMBpCtRalTsbxt3Xw+Igb4wI0c
/aRqwSksZR9ZkUc4Ft6Io3wVQ79/kk/VWoAq9V7rhDCD1lKvM8z1+vPSiYWHi1sn4zAxhL+l
eQGYo8mLtFEd8B5HzWO7GEbRBrvNDhvOzVN2uA1nBh78sTNMe+JrfmYSJj1hUrhVUXukRmEW
N7f95nApOW65ErnxuK4FMpML/ejVDU3IkJ7WuRoxTqb8Y3JCsW3ueWnPrl4WVkDy4hI3T9pK
TD+hyxl9ddDtyQ5Uwv4ltIPZJaz20aZA8b83YTnSmWmMDL79eh2JcDX0x5n02tdvwwh5gjtc
HxA0/vSteMJQIhEe1yJC9vs1pe+mhrRSfhT7sEmVaJwjR+9CySNemWp2ogmug+/mACaLl6UQ
sSRbMkwu3u+exmowrJ6KJgRkMivym9Qk6T+BoPziE7eJJnfwBkhAIyyX3KWdpjycUvpPM2nO
UfzoFlgVkOUaCUH3jWjOxGYaiKmFl7DY4tIvplpXzlvTc50utjQMieDKg0AAiHGrv1BFibEI
inrIq/rKFmzG94O1JGXnM3fHcLrjAAAAAAAA
--------------ms010402020309080001090708--


From nobody Sun Feb  6 10:35:58 2022
Return-Path: <marc.blanchet@viagenie.ca>
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 D9FF93A0BAA for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=viagenie-ca.20210112.gappssmtp.com
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 jmjl0RDwdn9l for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:35:44 -0800 (PST)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1C933A0BAD for <spfbis@ietf.org>; Sun,  6 Feb 2022 10:35:43 -0800 (PST)
Received: by mail-qv1-xf2a.google.com with SMTP id k9so9807334qvv.9 for <spfbis@ietf.org>; Sun, 06 Feb 2022 10:35:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=viagenie-ca.20210112.gappssmtp.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wXZAyy7gacbcp0VXG+xiZkRmp+rnc78vHrh7AI/Jwus=; b=d6XlVM6nz2soqKM3sjmSr/MuUuPuEwONJYB10SV0NB73k0njShU0C2ENBpCazypwgK c4ULjwyxXu3mfHxJrL2rgHohQSpfvFmXuSk/wsDR3lt1hv3YDZb1eO8ZdexiUhshV+fa HNfdLFnOrIL1IZPQeulORL4b+jkSa/N2DQDO9Uj7X2sdXOKnRSuIVcaCebz5catchPz5 Ck3fcCmj0TK1N8pepRncJ7ZJmFLsHfK1Z0NTIdMUFWJ2HIpJc7r0vxjocF1i7BAliMiH 0cOujxZRPD1i7fenUc76Fd70OQYFo5DufLaJW4fSe/pldJtYWwoWLSZJEnPsE9njoIkP Z/8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wXZAyy7gacbcp0VXG+xiZkRmp+rnc78vHrh7AI/Jwus=; b=04sVyQceqEDuh2vu4tZeTIFWo6xDSVca7m0cpDxUuj2u7+2/WkdupIK8I5F0ZyaLKn DVXEbz2ChIyI6EkcSjjEhS2eBIgI0Mv1B1RIEXJ/48/lteUpyUw17z6sscuKIIynYeUg ZUGgKRClwrLJxabTKT1Btqanb7LdJZjf/rEt52BVZZSpqq69EzJ3tsjiqs7GUD6w+jnB tO1kTzBsepJrnwdC3H0rqG70XT+6/nznDXpFQAAsIif0c6X4MhEgAAJi9m3fkWB7eAWY 3UPouPz8rbG4zcbF0ujUbylBc3QPgYinNnNWaagv9L/OTn7FXOcmYr0NCQyZu2G5Ea0t QROA==
X-Gm-Message-State: AOAM530OfFjD3NIdJfDxfO1YmAhtL4i6Kpz3lUzKXJ09YpWkU8W8KTzc Cvil+neg1ZhtgMIhrxitBbKqbw==
X-Google-Smtp-Source: ABdhPJx6UT2Ymew3Jkn0GyH6gD/PbfX+y4Kz+c/Wx6/SogzCGfA0zXhMFjycXUgDzxfmGebhl+1vgg==
X-Received: by 2002:a05:6214:2a85:: with SMTP id jr5mr7979988qvb.3.1644172541683;  Sun, 06 Feb 2022 10:35:41 -0800 (PST)
Received: from smtpclient.apple (modemcable161.124-162-184.mc.videotron.ca. [184.162.124.161]) by smtp.gmail.com with ESMTPSA id 66sm4333101qte.42.2022.02.06.10.35.41 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 Feb 2022 10:35:41 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de>
Date: Sun, 6 Feb 2022 13:35:40 -0500
Cc: behave@ietf.org, spfbis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de>
To: Klaus Frank <klaus.frank@posteo.de>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/rr1Hxca6fjBmqkJnltVhsKw8xVQ>
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: Sun, 06 Feb 2022 18:35:50 -0000

> Le 6 f=C3=A9vr. 2022 =C3=A0 13:09, Klaus Frank <klaus.frank@posteo.de> =
a =C3=A9crit :
>=20
> Hi,
>=20
> we had some issues with SPF and a mail server that was behind =
NAT64+DNS64. I at first thought that it was just a misconfiguration. But =
after the DNS64 server seamed to work as intended I went to the =
implementation and the RFC. Thereby while reading RFC6147 I stumbled =
across section 5.3.3 which says "All other RRs MUST be returned =
unchanged." which is the cause of my issues. This section is basically =
ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64 =
implementations from addressing this limitation.
>=20
> Would it be possible to create an extension to RFC6147 that mandates =
SPF record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 =
in IPv6 only environments won't be able to work as expected.
>=20
> Like:
> If the DNS64 server receives a SPF-record (within either the TXT-RR or =
the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites =
the ipv4 address according to the same rules as A-records are and =
synthesizes a new SPF record within the response that contains =
additional "ip6" entries. The original "ip4" should not be removed from =
the response.

I agree there is a problem. However, I can think of =E2=80=9Cinteresting=E2=
=80=9D problems to solve, like: what if the ip4 contains a prefix, like =
192.168.1.0/25. How would you translate this into IPv6 prefix by the =
DNS-64?

Marc.

>=20
> Sincerely,
> Klaus Frank
>=20
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis


From nobody Sun Feb  6 10:39:38 2022
Return-Path: <klaus.frank@posteo.de>
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 1859F3A0BCE for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 RVLnun42Ipv5 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:39:31 -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 9BFCF3A0BC4 for <spfbis@ietf.org>; Sun,  6 Feb 2022 10:39:30 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout01.posteo.de (Postfix) with ESMTPS id 0ED78240027 for <spfbis@ietf.org>; Sun,  6 Feb 2022 19:39:29 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644172769; bh=I/aY/IYgRgULIB2gSLLAwr8r25mFrw3zRCHbekGhddk=; h=Date:Subject:To:Cc:From:From; b=mm5k6hsYRt4hTo1jAKHC39qpcbnyqnrg7eBZhsI7WnbS3VgUpouLPFYH7CpMNCgNW CI+Loc33/Yvqj836N29BgkK671lK5txXR8yPDc8C8tFAHJ/YC7ELigGxgXrbnE1/mG gKn/lNajt7ZKHaJ68PQ08YrGDIE5KNwXNsXX1aRlvhCxkG2kyfR8B82XpbDKrLxSVn vWii46XPDLUvocfnbvcX8XrXD+VDKcTeDoYynVIxMZiCnOTk6hcGM/xeJ2xhgykwnN DguaqwP2zjayMifhXrZtNdnM9ZSngLtanUQjKLR2UGN74GzMojAUdHeS+KCKRW2IB3 hFmXiUjn9BtKg==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsJ344PYDz6tn9; Sun,  6 Feb 2022 19:39:28 +0100 (CET)
Message-ID: <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de>
Date: Sun,  6 Feb 2022 18:39:28 +0000
MIME-Version: 1.0
Content-Language: en-US
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Cc: behave@ietf.org, spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms040107010609050604040605"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/-vqtbtRDCPYPhkhTGdVy0hu5KOQ>
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: Sun, 06 Feb 2022 18:39:36 -0000

This is a cryptographically signed message in MIME format.

--------------ms040107010609050604040605
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit


On 2022-02-06 19:35, Marc Blanchet wrote:
>> Le 6 févr. 2022 à 13:09, Klaus Frank <klaus.frank@posteo.de> a écrit :
>>
>> Hi,
>>
>> we had some issues with SPF and a mail server that was behind NAT64+DNS64. I at first thought that it was just a misconfiguration. But after the DNS64 server seamed to work as intended I went to the implementation and the RFC. Thereby while reading RFC6147 I stumbled across section 5.3.3 which says "All other RRs MUST be returned unchanged." which is the cause of my issues. This section is basically ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64 implementations from addressing this limitation.
>>
>> Would it be possible to create an extension to RFC6147 that mandates SPF record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in IPv6 only environments won't be able to work as expected.
>>
>> Like:
>> If the DNS64 server receives a SPF-record (within either the TXT-RR or the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites the ipv4 address according to the same rules as A-records are and synthesizes a new SPF record within the response that contains additional "ip6" entries. The original "ip4" should not be removed from the response.
> I agree there is a problem. However, I can think of “interesting” problems to solve, like: what if the ip4 contains a prefix, like 192.168.1.0/25. How would you translate this into IPv6 prefix by the DNS-64?
Literally, your address of 192.168.1.0 would be e.g. ::ffff:c0a8:0100 
and the prefix would just be 25+96
>
> Marc.
>
>> Sincerely,
>> Klaus Frank
>>
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms040107010609050604040605
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYxODM5MjhaME8GCSqGSIb3DQEJBDFCBEDhzzFmrGiVqGEriJowaRHK
homsJz14u7gRi8LhdiQ2oatbXN+ddaxW/JCsXtnlmYJkDuH3cJRdYqHIbOpe24GSMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAECGZ9/u
xNLap+fjycWMWC4R8JcZdt9cfbzs/5od2JR/zUaHFMeVhz7zZsGmstfUe7WnF3ga3X1+OESz
w/9W8ufBbuNO39C2zjiU3fpD+zweGVb4PJE2C6EvGWWG5BBwxDICXOV+Hk9RcQ5Iu7pvdfVf
IfROVUzEP+votDEbbK+fKQ8Qm2S82tFTwvUfRcZROJFzZsAwqMegC1nl79pvDl8BJCCJnFbH
BrP58fdbhcY4wI92TV8nP/B+qMq44daA8o74UEOi/B+E+3YYqc6cMUslVG3rZ24gvuz+9stm
ZMUkRnVjfTyaB2zpBLn3oOVwyTDgLa+Z3cO0BLWzXUCdgdoheOQ/l0Xs1FnW4Jbfn3RTTkIP
F6gfPyj4eW/IzYkmOV+d5sDz+55YZsbhCnFSlsMVh8mYaCIETE3q3E2uVmpSJVvxB0zL9vOX
bR1B7dgLJ8kBHQxp13W6ywM/TuhLwXYj08WKFYAuvhLgDh/uczUXIkGmJaMRL/jWIxKrfKI1
1+SJRAds7+PgyYIdJNltFlChE67HsITX77p5yKrUoI/EqL05hor0u6Ataf5sIgZ6vEF1M8ZS
dPpKxxjYkicp4/ByeW/ByYfO7MLSijZtnrIrR2f/6rBVxcWyKcZi8/cPQE9PuX9uVT5CcHOT
5PFZEZ/XFdi0UHBi3cBJ4wLoTwg0AAAAAAAA
--------------ms040107010609050604040605--


From nobody Sun Feb  6 10:55:13 2022
Return-Path: <william@leibzon.org>
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 8393A3A0AD7 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:55:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 POdPJziYjjhU for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:55:05 -0800 (PST)
Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0204E3A0C08 for <spfbis@ietf.org>; Sun,  6 Feb 2022 10:55:04 -0800 (PST)
Received: from omf02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 7FC8E22F87; Sun,  6 Feb 2022 18:55:03 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: william@leibzon.org) by omf02.hostedemail.com (Postfix) with ESMTPA id 48AC18000A;  Sun,  6 Feb 2022 18:54:40 +0000 (UTC)
MIME-Version: 1.0
Date: Sun, 06 Feb 2022 10:55:02 -0800
From: william@leibzon.org
To: Scott Kitterman <spf2@kitterman.com>
Cc: spfbis@ietf.org
In-Reply-To: <2098569.QsC3VX2HWt@localhost>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost>
Message-ID: <d606050e47c4ae22b53448e56ff29ad2@leibzon.org>
X-Sender: william@leibzon.org
Content-Type: multipart/alternative; boundary="=_d4d403845ba3de9bdffc2d0948361f7e"
X-Rspamd-Queue-Id: 48AC18000A
X-Stat-Signature: 1tg15d81r8pcnuydgo5b4ojdoyronw1b
X-Rspamd-Server: rspamout06
X-Session-Marker: 77696C6C69616D406C6569627A6F6E2E6F7267
X-Session-ID: U2FsdGVkX18kCJq+xvKh8NZK+51BFVlX5nD5pHNwKJ0=
X-HE-Tag: 1644173680-285985
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/Dj5Y3GM2vCVnVDJ3AzbIXfrwKQU>
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: Sun, 06 Feb 2022 18:55:10 -0000

--=_d4d403845ba3de9bdffc2d0948361f7e
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII;
 format=flowed



This is like NAT where entirety of DNS is re-written to make internet 
appear to be IPV6 only. So yes, SPF records would be an issue then.

There is more than one way to solve it. The proposal to re-write SPF is 
probably the most correct way within context of NAT64-DNS64. The other 
option would be to update SPF specifying that validating servers on IPv6 
only network can use IPv4 spf records for validation if the ip address 
of connecting mail server is a mapped IPv4->IPv6. That is far less 
elegant though.

BTW, I bet SPF is not going to be the only protocol with these types of 
issues. How about SIEVE? Have you checked how well NAT64 inter-operates 
with that?

On 2022-02-06 10:25, Scott Kitterman wrote:

> On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote:
> 
>> Hi,
>> 
>> we had some issues with SPF and a mail server that was behind
>> NAT64+DNS64. I at first thought that it was just a misconfiguration. 
>> But
>> after the DNS64 server seamed to work as intended I went to the
>> implementation and the RFC. Thereby while reading RFC6147 I stumbled
>> across section 5.3.3 which says "All other RRs MUST be returned
>> unchanged." which is the cause of my issues. This section is basically
>> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
>> implementations from addressing this limitation.
>> 
>> Would it be possible to create an extension to RFC6147 that mandates 
>> SPF
>> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
>> IPv6 only environments won't be able to work as expected.
>> 
>> Like:
>> If the DNS64 server receives a SPF-record (within either the TXT-RR or
>> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
>> the ipv4 address according to the same rules as A-records are and
>> synthesizes a new SPF record within the response that contains
>> additional "ip6" entries. The original "ip4" should not be removed 
>> from
>> the response.
> 
> What's preventing the SPF record publisher from solving this problem by 
> adding
> the ip6: mechanisms themselves?  Perhaps I don't understand the issue 
> you are
> raising.  Would you please clarify what it is you're asking be done 
> that an
> administrator can't do on their own?
> 
> Scott K
> 
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis
--=_d4d403845ba3de9bdffc2d0948361f7e
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p><br />This is like NAT where entirety of DNS is re-written to make inter=
net appear to be IPV6 only. So yes, SPF records would be an issue then.<br =
/><br />There is more than one way to solve it. The proposal to re-write SP=
F is probably the most correct way within context of NAT64-DNS64. The other=
 option would be to update SPF specifying that validating servers on IPv6 o=
nly network can use IPv4 spf records for validation if the ip address of co=
nnecting mail server is a mapped IPv4-&gt;IPv6. That is far less elegant th=
ough.&nbsp;<br /><br />BTW, I bet SPF is not going to be the only protocol =
with these types of issues. How about SIEVE? Have you checked how well NAT6=
4 inter-operates with that?</p>
<div id=3D"signature"></div>
<p id=3D"reply-intro">On 2022-02-06 10:25, Scott Kitterman wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote:
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">Hi,<br /><br />we had some issues with SPF and a mail =
server that was behind<br />NAT64+DNS64. I at first thought that it was jus=
t a misconfiguration. But<br />after the DNS64 server seamed to work as int=
ended I went to the<br />implementation and the RFC. Thereby while reading =
RFC6147 I stumbled<br />across section 5.3.3 which says "All other RRs MUST=
 be returned<br />unchanged." which is the cause of my issues. This section=
 is basically<br />ignoring SPF records (RFC7208 section 5.6) and also prev=
enting DNS64<br />implementations from addressing this limitation.<br /><br=
 />Would it be possible to create an extension to RFC6147 that mandates SPF=
<br />record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in=
<br />IPv6 only environments won't be able to work as expected.<br /><br />=
Like:<br />If the DNS64 server receives a SPF-record (within either the TXT=
-RR or<br />the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST re=
writes<br />the ipv4 address according to the same rules as A-records are a=
nd<br />synthesizes a new SPF record within the response that contains<br /=
>additional "ip6" entries. The original "ip4" should not be removed from<br=
 />the response.</blockquote>
<br />What's preventing the SPF record publisher from solving this problem =
by adding <br />the ip6: mechanisms themselves? &nbsp;Perhaps I don't under=
stand the issue you are <br />raising. &nbsp;Would you please clarify what =
it is you're asking be done that an <br />administrator can't do on their o=
wn?<br /><br />Scott K<br /><br /><br />___________________________________=
____________<br />spfbis mailing list<br /><a href=3D"mailto:spfbis@ietf.or=
g">spfbis@ietf.org</a><br /><a href=3D"https://www.ietf.org/mailman/listinf=
o/spfbis" target=3D"_blank" rel=3D"noopener noreferrer">https://www.ietf.or=
g/mailman/listinfo/spfbis</a></div>
</blockquote>
</body></html>

--=_d4d403845ba3de9bdffc2d0948361f7e--


From nobody Sun Feb  6 10:59:06 2022
Return-Path: <spf2@kitterman.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 74A283A0C0B for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:59:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=WCSCdd1a; dkim=pass (2048-bit key) header.d=kitterman.com header.b=oTwPNMW1
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 pV8ocBOEMmWY for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 10:58:59 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7DC73A0C08 for <spfbis@ietf.org>; Sun,  6 Feb 2022 10:58:58 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id 7DB85F80277 for <spfbis@ietf.org>; Sun,  6 Feb 2022 13:58:54 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1644173934; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=Be9sX1Eq3DQqbGyqRqjx+wa/w9Z/Sn1zOfTQ6MZMTGs=; b=WCSCdd1ae4W3vZ56VmuKDQXbmvNBDgwPS+b56zINTmgC4fKYZ3LL+1qXrT3YngydTgNVc LgsWwbGoChUmxFXCg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1644173934; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=Be9sX1Eq3DQqbGyqRqjx+wa/w9Z/Sn1zOfTQ6MZMTGs=; b=oTwPNMW1yLX3FpDGnNuB6Xc6b2TFheGnQ1x5PMKW5clE+KFsVejnieiYjEj4YZ2XIc4Pq Txc4Hn8NosGIyo7/42TKWFYvlLBh7XBh0IAkrH+dNwO6EyrWW0sPUSGlD/YWXoaUpsvEHHl oQhZzI9BvnzetptDZjv4m4xb1K8u2CksDqUay2bDOEQi4IVWs19oIvBE8W/5HxtrRSrRnbV OZ3BnaJC5bGugPru8HT1FuXVrY7ngifC60K04e5vFqAftOcsAF0JAvZlO83beu+qgZD07Ms pJviz4Yb21whSgrKjT6B2NGNM0ulk4wqsJoqFLHTXucLaiEqMqDUN4Zzwq+g==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 52397F801A9 for <spfbis@ietf.org>; Sun,  6 Feb 2022 13:58:54 -0500 (EST)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Sun, 06 Feb 2022 13:58:54 -0500
Message-ID: <8021771.rLJEViv2lv@localhost>
In-Reply-To: <ae4f7b97-3f78-aa9c-4274-025d29622269@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost> <ae4f7b97-3f78-aa9c-4274-025d29622269@posteo.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/oYLLgWLZQobRG4d2CdDEwTvzOYM>
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: Sun, 06 Feb 2022 18:59:05 -0000

On Sunday, February 6, 2022 1:31:06 PM EST Klaus Frank wrote:
> Hi,
> 
> the DNS64 record is a syntetic dns record that is created by the
> resolver to fill in a missing AAAA-RR for responses to make the IPv4
> internet reachable from IPv6 only networks. Basically the issue is that
> the recipient admin would have to make a change on the sending domains
> side depending on the recipients infrastructure.

Thanks.  So this would apply to any DNS record that contains an IP address 
(IPv4) and RFC 6147 addresses A?  This would affect PTR lookups too, right (not 
the SPF PTR mechanism, but when a receiving mail sever does a PTR lookup on 
the connect address to see if it matches the EHLO name)?

Scott K

> 
> On 2022-02-06 19:25, Scott Kitterman wrote:
> > On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote:
> >> Hi,
> >> 
> >> we had some issues with SPF and a mail server that was behind
> >> NAT64+DNS64. I at first thought that it was just a misconfiguration. But
> >> after the DNS64 server seamed to work as intended I went to the
> >> implementation and the RFC. Thereby while reading RFC6147 I stumbled
> >> across section 5.3.3 which says "All other RRs MUST be returned
> >> unchanged." which is the cause of my issues. This section is basically
> >> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
> >> implementations from addressing this limitation.
> >> 
> >> Would it be possible to create an extension to RFC6147 that mandates SPF
> >> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
> >> IPv6 only environments won't be able to work as expected.
> >> 
> >> Like:
> >> If the DNS64 server receives a SPF-record (within either the TXT-RR or
> >> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
> >> the ipv4 address according to the same rules as A-records are and
> >> synthesizes a new SPF record within the response that contains
> >> additional "ip6" entries. The original "ip4" should not be removed from
> >> the response.
> > 
> > What's preventing the SPF record publisher from solving this problem by
> > adding the ip6: mechanisms themselves?  Perhaps I don't understand the
> > issue you are raising.  Would you please clarify what it is you're asking
> > be done that an administrator can't do on their own?
> > 
> > Scott K
> > 
> > 
> > _______________________________________________
> > spfbis mailing list
> > spfbis@ietf.org
> > https://www.ietf.org/mailman/listinfo/spfbis





From nobody Sun Feb  6 11:08:20 2022
Return-Path: <klaus.frank@posteo.de>
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 D1B183A0C2F for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 11:08: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 zB9dQv8G33Rs for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 11:08:11 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 8359F3A0C27 for <spfbis@ietf.org>; Sun,  6 Feb 2022 11:08:10 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id E6C7C240104 for <spfbis@ietf.org>; Sun,  6 Feb 2022 20:08:06 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644174486; bh=7jLRS8v0AxUWb1gdlp47ALAYgQp7wPKQPPHrKV6Wubs=; h=Date:Subject:To:From:From; b=Ug0DURFq/KDUd2Az0rn5Y7fbbl+mZN2E315OlZbGntf4D/Hzl2san0PY4y+ZxFhbG a8R2NAz/pXNWtXk/9V1+Qwkbr+2/X19M9U9H4PedYxYvtLBPM0n0ma379zNQ75ZIWI Tda+r3Hz5xgPM1aXHtEWoN9/g7yK4FO+pJCQVKH6yhiVE6nAfthtScIZ71/b5doRe/ tvZNKr5MUQ3SdWXgBROxcXk23RiPnyKAuYrhHKOOo1ZTDi9BMiCgozO0qw+Znx4kol unROmZCLbuRSed2uIGqek17nFJje8PmBLskQgdczjmVHBPIobwRTYcedN+NmESaopR OhVyA1PiVf0gA==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsJh64v82z9rxL for <spfbis@ietf.org>; Sun,  6 Feb 2022 20:08:05 +0100 (CET)
Message-ID: <85cb8ec0-4316-c4db-4aed-2d49fda46f49@posteo.de>
Date: Sun,  6 Feb 2022 19:08:05 +0000
MIME-Version: 1.0
Content-Language: en-US
To: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost> <ae4f7b97-3f78-aa9c-4274-025d29622269@posteo.de> <8021771.rLJEViv2lv@localhost>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <8021771.rLJEViv2lv@localhost>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms000703080201080300010007"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/3ihwyMRJThhtVyVc8RIwrP_HMS4>
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: Sun, 06 Feb 2022 19:08:17 -0000

This is a cryptographically signed message in MIME format.

--------------ms000703080201080300010007
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Yes, exactly. Every DNS entry that doesn't have an AAAA-RR will get one 
by DNS64 generated using the configured NAT64 prefix and the A-RR.
This also covers the PTR-RRs.

 From RFC6147 5.3.1:

    If a DNS64 server receives a PTR query for a record in the IP6.ARPA
    domain, it MUST strip the IP6.ARPA labels from the QNAME, reverse the
    address portion of the QNAME according to the encoding scheme
    outlined in Section 2.5 of [RFC3596], and examine the resulting
    address to see whether its prefix matches any of the locally
    configured Pref64::/n or the default Well-Known Prefix.  There are
    two alternatives for a DNS64 server to respond to such PTR queries.
    A DNS64 server MUST provide one of these, and SHOULD NOT provide both
    at the same time unless different IP6.ARPA zones require answers of
    different sorts:

    1.  The first option is for the DNS64 server to respond
        authoritatively for its prefixes.  If the address prefix matches
        any Pref64::/n used in the site, either a NSP or the Well-Known
        Prefix (i.e., 64:ff9b::/96), then the DNS64 server MAY answer the
        query using locally appropriate RDATA.  The DNS64 server MAY use
        the same RDATA for all answers.  Note that the requirement is to
        match any Pref64::/n used at the site, and not merely the locally
        configured Pref64::/n.  This is because end clients could ask for
        a PTR record matching an address received through a different
        (site-provided) DNS64, and if this strategy is in effect, those
        queries should never be sent to the global DNS.  The advantage of
        this strategy is that it makes plain to the querying client that
        the prefix is one operated by the (DNS64) site, and that the
        answers the client is getting are generated by DNS64.  The
        disadvantage is that any useful reverse-tree information that
        might be in the global DNS is unavailable to the clients querying
        the DNS64.

    2.  The second option is for the DNS64 name server to synthesize a
        CNAME mapping the IP6.ARPA namespace to the corresponding
        IN-ADDR.ARPA name.  In this case, the DNS64 name server SHOULD
        ensure that there is RDATA at the PTR of the corresponding
        IN-ADDR.ARPA name, and that there is not an existing CNAME at
        that name.  This is in order to avoid synthesizing a CNAME that
        makes a CNAME chain longer or that does not actually point to
        anything.  The rest of the response would be the normal DNS
        processing.  The CNAME can be signed on the fly if need be.  The
        advantage of this approach is that any useful information in the
        reverse tree is available to the querying client.  The
        disadvantages are that it adds additional load to the DNS64
        (because CNAMEs have to be synthesized for each PTR query that
        matches the Pref64::/n), and that it may require signing on
        the fly.

    If the address prefix does not match any Pref64::/n, then the DNS64
    server MUST process the query as though it were any other query;
    i.e., a recursive name server MUST attempt to resolve the query as
    though it were any other (non-A/AAAA) query, and an authoritative
    server MUST respond authoritatively or with a referral, as
    appropriate.

On 2022-02-06 19:58, Scott Kitterman wrote:
> Thanks.  So this would apply to any DNS record that contains an IP address
> (IPv4) and RFC 6147 addresses A?  This would affect PTR lookups too, right (not
> the SPF PTR mechanism, but when a receiving mail sever does a PTR lookup on
> the connect address to see if it matches the EHLO name)?

--------------ms000703080201080300010007
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYxOTA4MDVaME8GCSqGSIb3DQEJBDFCBEC7f8tGS+Tl/sH2HRH9kzDd
/AvZ3j4qQsfI2z2arz5XC7x/rtzlG/iSzzTskOkdkZvQo2OzSWrDSJBGrMFExBVqMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAGc+voRR
BP3/PBAugeliWEGlGu5s213q3K5KaMaf7A7Jp3rS8mWgz3n9YjG9Ki2a/pZNUnNFNYW2JgVc
EaDitmPvcDhcJlyc5nJfOAYqHYeruyJzQIvv5M4iSA/AhMctYddzcQmWVXYNQVQI5V/DKr8C
y66Xtod+wqvZlaJegcp99HdP62dFqdSml6iN/8QzWehRlvnobC39E0TQ0horWekPKNo3weTr
2HO4vdYVU1emG1iOZsXUW0a1S5LbOSOTRPNxb95iKp5wcUDiFD5f9sJ2Mj79vyhagqzjIllb
qaG2Jd0QCCaXf+BfieiRaDWgCVVqYK+3N8gj4y//A8ithtd0lduDs83RwJ/R1fMdJbS3fSYB
WnUccZKlAG1VpKLwG617hp780hGubZZOvcl+4DU2Nfr0+aJG2y52m5dDKKgSkGc7giswEukd
i1WY1J9+QLelMnRQheXHuoRXOwKElimkEP5b27LtcwK7h1NqECtC6HuIalZuTMXamAJrDLxM
NQqCWACOB0xSvmqN7TIhn5VoSLtJNy9TvPQqPGEYHMU4nmloJUpWYVzjDg5bQKz2bmtgz2MW
PqwymUFZzmYkiXN+Rp6Mvk0Wb8TyXVFbFR7sTQq157Qfo+0xUtTRGsSPNliNe5yqA4QtrMq7
eC6j6J4Pg1m+6ECHp1r9pXXcXfgdAAAAAAAA
--------------ms000703080201080300010007--


From nobody Sun Feb  6 11:13:23 2022
Return-Path: <klaus.frank@posteo.de>
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 6847F3A0C3E for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 11:13:22 -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 19OlMckfATjg for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 11:13:17 -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 A53E53A0C3D for <spfbis@ietf.org>; Sun,  6 Feb 2022 11:13:15 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout01.posteo.de (Postfix) with ESMTPS id 9E493240029 for <spfbis@ietf.org>; Sun,  6 Feb 2022 20:13:11 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644174792; bh=yvefcBUh81Rot7T3D29GZFSnhPbyUOkWTYbWZZLI7oc=; h=Date:Subject:To:From:From; b=A2Lyvb61ildW+F/fFIfdnqN0umih1vl9uKhmvRKZTIAfut62w2fPAawEP1Z8CwGC3 46x6JXxFMADWLv0GiVNxiZbTd9OP/+vA4YeVBGtUeafL7DTTwmjVgEiUoTo9x7QYin YDjNICCR2TFBDsIoPVbJE32djNkBilm1FEYMBlVEhhYeOdphuC9zihFoejR6c5VSBe 0IiSCfbg0k7IIsu64jCEzbkyN+pbjywtkM3Z4VsJtUNWVbZhFpp9X8Jov9+ndNs78w ws/EsCelsefAlJQEsvfrMPeDxSrDT451H3JUYOPfbAi4rK0iGlVu4uQSwws92HalGE D2CFb1ltv8ZNA==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsJnz3lnyz6tnL for <spfbis@ietf.org>; Sun,  6 Feb 2022 20:13:11 +0100 (CET)
Message-ID: <7683f14e-113c-e339-f499-bc75bc1644a0@posteo.de>
Date: Sun,  6 Feb 2022 19:13:10 +0000
MIME-Version: 1.0
Content-Language: de-DE
To: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost> <d606050e47c4ae22b53448e56ff29ad2@leibzon.org>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <d606050e47c4ae22b53448e56ff29ad2@leibzon.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms040205090109080008070305"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/h8Frhzm9rqoRJmF8UzuqPFf96P4>
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: Sun, 06 Feb 2022 19:13:23 -0000

This is a cryptographically signed message in MIME format.

--------------ms040205090109080008070305
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

I'm not aware that SIEVE would use the source ip address. Also when 
looking over the main RFCs for it I couldn't find anything that 
specifies ip validation. ATM only the EHLO (which uses the PTR-RR) and 
the SPF validation rely on IP to DNS mapping.

On 2022-02-06 19:55, william@leibzon.org wrote:
>
>
> This is like NAT where entirety of DNS is re-written to make internet 
> appear to be IPV6 only. So yes, SPF records would be an issue then.
>
> There is more than one way to solve it. The proposal to re-write SPF 
> is probably the most correct way within context of NAT64-DNS64. The 
> other option would be to update SPF specifying that validating servers 
> on IPv6 only network can use IPv4 spf records for validation if the ip 
> address of connecting mail server is a mapped IPv4->IPv6. That is far 
> less elegant though.
>
> BTW, I bet SPF is not going to be the only protocol with these types 
> of issues. How about SIEVE? Have you checked how well NAT64 
> inter-operates with that?
>
> On 2022-02-06 10:25, Scott Kitterman wrote:
>
>> On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote:
>>> Hi,
>>>
>>> we had some issues with SPF and a mail server that was behind
>>> NAT64+DNS64. I at first thought that it was just a misconfiguration. But
>>> after the DNS64 server seamed to work as intended I went to the
>>> implementation and the RFC. Thereby while reading RFC6147 I stumbled
>>> across section 5.3.3 which says "All other RRs MUST be returned
>>> unchanged." which is the cause of my issues. This section is basically
>>> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
>>> implementations from addressing this limitation.
>>>
>>> Would it be possible to create an extension to RFC6147 that mandates SPF
>>> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
>>> IPv6 only environments won't be able to work as expected.
>>>
>>> Like:
>>> If the DNS64 server receives a SPF-record (within either the TXT-RR or
>>> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
>>> the ipv4 address according to the same rules as A-records are and
>>> synthesizes a new SPF record within the response that contains
>>> additional "ip6" entries. The original "ip4" should not be removed from
>>> the response.
>>
>> What's preventing the SPF record publisher from solving this problem 
>> by adding
>> the ip6: mechanisms themselves?  Perhaps I don't understand the issue 
>> you are
>> raising.  Would you please clarify what it is you're asking be done 
>> that an
>> administrator can't do on their own?
>>
>> Scott K
>>
>>
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis
>
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms040205090109080008070305
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYxOTEzMTBaME8GCSqGSIb3DQEJBDFCBEBX58oZ68XCytbnRd0fRFMO
e22d/FH/J9ifXgDYdmEqAGhL5OfqfjIgmPHEWW2jXk7G8eU5HK7nZwIU1jVm5nRiMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAKpzylQh
OezuFF9pHNA7nIYnYKcjLmEBFajEsnwTFf2A0HGHH2RPczuTJyeMt6IgC9yvM2ZnfCsgB9zG
6MQoM9F+N0LxW5LlhPLweSSymlM6Wu2Siv2RFz3vzHWw5lQec6ByL/Wsl/4u74G4zVQi281e
t9kSaUWpviVj2CgVjR6S8wZvP2RjfRWtjYR0nPal735IFx0ck2K02zw4fBAFRN9/AzFaPpGz
ARgZ9l5YJV4m2b0YNXdUwAgSW/YETGDBdAWiecdABvHxr996b3H89nZDXOzI7VSZPJhAcnds
RT2Ahyn5k9j1wRB9vO1fbzPbu/7EeOsqUDeYnQpYBb0/d42OpRgMkuery+OmNxpN6Pcd5NNB
PuaQZdDUXvVTGjWLpXKDNbxW5mTKlxZs/kVGiGI6KyzRjDOH5Ck956QQklAIM3I53YaeMGWm
7SORzatovvwsmikdjzC5+nDW/5jO1RWARPIuCFgpJ9EfvDVAl/1N7U1k+/2tgXHl6NLLgT0t
X2TQPfvf3KueRMuS3na8le0Y2qtqDlxbhhqRnmXbKzilHclD3NIcr0taFtoKYyPaEvOSKsNn
2QApu0qpovmJSzVbBCF2YdcF8Wbq5uZRuZKTvySrjaulYOFNT3/Qxhp5w99+nkIyyXGSg9ii
BjPnt98hm16Ram/BDXE+53w7iOMVAAAAAAAA
--------------ms040205090109080008070305--


From nobody Sun Feb  6 11:57:20 2022
Return-Path: <spf2@kitterman.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 9BC383A0CBA for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 11:57:18 -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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=zJNmV1uz; dkim=pass (2048-bit key) header.d=kitterman.com header.b=PZx4TmDp
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 OZDIeQ7uyT3K for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 11:57:13 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 796573A0CB7 for <spfbis@ietf.org>; Sun,  6 Feb 2022 11:57:13 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id F3DB7F80277 for <spfbis@ietf.org>; Sun,  6 Feb 2022 14:57:08 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1644177428; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=YSt29wwnON//B+vtJIMrUa0pAIO8Ri/CJt7K8hlCo84=; b=zJNmV1uzJXXut01HKgfE1Jb8WAz/tQWmLNDXBYZ4PWhSUvHXB4ehP3/XfB1Vl+xi5kOoi 9h+Ge5OsWG6cuU+Bw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1644177428; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=YSt29wwnON//B+vtJIMrUa0pAIO8Ri/CJt7K8hlCo84=; b=PZx4TmDpRpo7DkkgpAsCyhDxQyDPuUvS2D2tRVPS9PhOiMMcobViMATg7srkCvKGkBg3r 9G9NHRJKMRTY6KSsW2GuoelR9yC5YCNo9V4FVFhd5ztYmtEbRHm+qEHCTr5907I/d9WlOH9 ygddRgH5bcCRvKLYT5Rk2MVYFPGrPgkbT9+XkXEBE+/Q1qMoI7KM3YS4pU9C0N4Bch2sqpW SdRY19xsymCMxB5avp1eCEYA1/xjakLDSPz/BHFNdOZ/P4dKL2CIYKN/WBXe+be0EGPY57S C+yAuRfdYZF0oSkdEMkBykfhnwUgHOT5oDe/gRik6yfnfy7JmqDwwOHtFJxw==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id C3786F801A9 for <spfbis@ietf.org>; Sun,  6 Feb 2022 14:57:08 -0500 (EST)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Sun, 06 Feb 2022 14:57:08 -0500
Message-ID: <45673006.FIhfuaby8d@localhost>
In-Reply-To: <85cb8ec0-4316-c4db-4aed-2d49fda46f49@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <8021771.rLJEViv2lv@localhost> <85cb8ec0-4316-c4db-4aed-2d49fda46f49@posteo.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/2FnAI_Q4U28b3WBQeur8KkbUGBs>
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: Sun, 06 Feb 2022 19:57:19 -0000

It looks like situations like this one were contemplated by the RFC 6147 
authors:

> 6.  Deployment Notes
> 
>    While DNS64 is intended to be part of a strategy for aiding IPv6
>    deployment in an internetworking environment with some IPv4-only and
>    IPv6-only networks, it is important to realize that it is
>    incompatible with some things that may be deployed in an IPv4-only or
>    dual-stack context.

On the SPF side of the discussion, I think it would, at least in theory, be 
feasible to interpret an ip4: mechanism as <prefix> + <address> if the 
connection is IPv6, but I don't see how a receiving SPF processor could know 
what the prefix is.  As I read RFC 6147 Section 5.2, it could be anything.

I think your original suggestion that an SPF record be modified by the DNS64 
server to add ip6: mechanisms with <prefix> + <address> is a reasonable path 
forward, but I think it's really an RFC 6147 discussion, not so much RFC 7208.  
It is not, however, without risks.  RFC 7208 Section 3.4 gives advice on SPF 
record size.  Your proposed approach would increase the record size, which, in 
theory, could be problematic.  It might be that anything running on an IPv6 
only network is modern enough that this isn't actually a problem.  I don't 
know.

Scott K

On Sunday, February 6, 2022 2:08:05 PM EST Klaus Frank wrote:
> Yes, exactly. Every DNS entry that doesn't have an AAAA-RR will get one
> by DNS64 generated using the configured NAT64 prefix and the A-RR.
> This also covers the PTR-RRs.
> 
>  From RFC6147 5.3.1:
> 
>     If a DNS64 server receives a PTR query for a record in the IP6.ARPA
>     domain, it MUST strip the IP6.ARPA labels from the QNAME, reverse the
>     address portion of the QNAME according to the encoding scheme
>     outlined in Section 2.5 of [RFC3596], and examine the resulting
>     address to see whether its prefix matches any of the locally
>     configured Pref64::/n or the default Well-Known Prefix.  There are
>     two alternatives for a DNS64 server to respond to such PTR queries.
>     A DNS64 server MUST provide one of these, and SHOULD NOT provide both
>     at the same time unless different IP6.ARPA zones require answers of
>     different sorts:
> 
>     1.  The first option is for the DNS64 server to respond
>         authoritatively for its prefixes.  If the address prefix matches
>         any Pref64::/n used in the site, either a NSP or the Well-Known
>         Prefix (i.e., 64:ff9b::/96), then the DNS64 server MAY answer the
>         query using locally appropriate RDATA.  The DNS64 server MAY use
>         the same RDATA for all answers.  Note that the requirement is to
>         match any Pref64::/n used at the site, and not merely the locally
>         configured Pref64::/n.  This is because end clients could ask for
>         a PTR record matching an address received through a different
>         (site-provided) DNS64, and if this strategy is in effect, those
>         queries should never be sent to the global DNS.  The advantage of
>         this strategy is that it makes plain to the querying client that
>         the prefix is one operated by the (DNS64) site, and that the
>         answers the client is getting are generated by DNS64.  The
>         disadvantage is that any useful reverse-tree information that
>         might be in the global DNS is unavailable to the clients querying
>         the DNS64.
> 
>     2.  The second option is for the DNS64 name server to synthesize a
>         CNAME mapping the IP6.ARPA namespace to the corresponding
>         IN-ADDR.ARPA name.  In this case, the DNS64 name server SHOULD
>         ensure that there is RDATA at the PTR of the corresponding
>         IN-ADDR.ARPA name, and that there is not an existing CNAME at
>         that name.  This is in order to avoid synthesizing a CNAME that
>         makes a CNAME chain longer or that does not actually point to
>         anything.  The rest of the response would be the normal DNS
>         processing.  The CNAME can be signed on the fly if need be.  The
>         advantage of this approach is that any useful information in the
>         reverse tree is available to the querying client.  The
>         disadvantages are that it adds additional load to the DNS64
>         (because CNAMEs have to be synthesized for each PTR query that
>         matches the Pref64::/n), and that it may require signing on
>         the fly.
> 
>     If the address prefix does not match any Pref64::/n, then the DNS64
>     server MUST process the query as though it were any other query;
>     i.e., a recursive name server MUST attempt to resolve the query as
>     though it were any other (non-A/AAAA) query, and an authoritative
>     server MUST respond authoritatively or with a referral, as
>     appropriate.
> 
> On 2022-02-06 19:58, Scott Kitterman wrote:
> > Thanks.  So this would apply to any DNS record that contains an IP address
> > (IPv4) and RFC 6147 addresses A?  This would affect PTR lookups too, right
> > (not the SPF PTR mechanism, but when a receiving mail sever does a PTR
> > lookup on the connect address to see if it matches the EHLO name)?





From nobody Sun Feb  6 12:11:04 2022
Return-Path: <william@leibzon.org>
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 DD2113A0CF0 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:10:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ThKu4IlEVKW0 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:10:53 -0800 (PST)
Received: from relay3.hostedemail.com (relay3.hostedemail.com [64.99.140.33]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C0CF3A0CD9 for <spfbis@ietf.org>; Sun,  6 Feb 2022 12:10:53 -0800 (PST)
Received: from omf02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 3EA5620AE3; Sun,  6 Feb 2022 20:10:52 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: william@leibzon.org) by omf02.hostedemail.com (Postfix) with ESMTPA id 009D08000F;  Sun,  6 Feb 2022 20:10:28 +0000 (UTC)
MIME-Version: 1.0
Date: Sun, 06 Feb 2022 12:10:51 -0800
From: william@leibzon.org
To: Klaus Frank <klaus.frank@posteo.de>
Cc: spfbis@ietf.org
In-Reply-To: <7683f14e-113c-e339-f499-bc75bc1644a0@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost> <d606050e47c4ae22b53448e56ff29ad2@leibzon.org> <7683f14e-113c-e339-f499-bc75bc1644a0@posteo.de>
Message-ID: <5f14e191ab8239dd5dae0e4fbac7d223@leibzon.org>
X-Sender: william@leibzon.org
Content-Type: multipart/alternative; boundary="=_c6aa061c9193dfca769188b393f7a4dd"
X-Stat-Signature: zpazxj3kjc3idt38611tsem19o7rohoi
X-Rspamd-Server: rspamout03
X-Rspamd-Queue-Id: 009D08000F
X-Session-Marker: 77696C6C69616D406C6569627A6F6E2E6F7267
X-Session-ID: U2FsdGVkX1/Ryr6YVrPA0AcMujgwZuU6lNFLPHPBD0c=
X-HE-Tag: 1644178228-510831
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/UX-45pqrREt7Lc6eri3waQP3dOw>
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: Sun, 06 Feb 2022 20:11:01 -0000

--=_c6aa061c9193dfca769188b393f7a4dd
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII;
 format=flowed



In regards to SIEVE take a look at examples in 
http://www.delegate.org/ietf/rfc-html/rfc6134.shtml

There are a lot of various types of ip address validation going on that 
is not documented by IETF or any other authority but is in practice done 
using various unix utilities. Most of these is just to separate local 
and external networks but there are real ip address blocks of large 
sties - both at the router/network and at the local host level. Some 
companies limit what sites their employees can visit and there are many 
ways it is done.

And of course for email ip address block lists still exists and in use 
as well. In some cases DNS is used, in others ip lists are received as 
files and synced.

NAT64 is bound to run into all sorts of issues like this when it begins 
to be more widely used. And I do think this is positive step towards 
IPv6 world. Its just going to take quite some time to work all these 
issues out.

On 2022-02-06 11:13, Klaus Frank wrote:

> I'm not aware that SIEVE would use the source ip address. Also when 
> looking over the main RFCs for it I couldn't find anything that 
> specifies ip validation. ATM only the EHLO (which uses the PTR-RR) and 
> the SPF validation rely on IP to DNS mapping.
> 
> On 2022-02-06 19:55, william@leibzon.org wrote:
> 
> This is like NAT where entirety of DNS is re-written to make internet 
> appear to be IPV6 only. So yes, SPF records would be an issue then.
> 
> There is more than one way to solve it. The proposal to re-write SPF is 
> probably the most correct way within context of NAT64-DNS64. The other 
> option would be to update SPF specifying that validating servers on 
> IPv6 only network can use IPv4 spf records for validation if the ip 
> address of connecting mail server is a mapped IPv4->IPv6. That is far 
> less elegant though.
> 
> BTW, I bet SPF is not going to be the only protocol with these types of 
> issues. How about SIEVE? Have you checked how well NAT64 inter-operates 
> with that?
> 
> On 2022-02-06 10:25, Scott Kitterman wrote:
> 
> On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote: Hi,
> 
> we had some issues with SPF and a mail server that was behind
> NAT64+DNS64. I at first thought that it was just a misconfiguration. 
> But
> after the DNS64 server seamed to work as intended I went to the
> implementation and the RFC. Thereby while reading RFC6147 I stumbled
> across section 5.3.3 which says "All other RRs MUST be returned
> unchanged." which is the cause of my issues. This section is basically
> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
> implementations from addressing this limitation.
> 
> Would it be possible to create an extension to RFC6147 that mandates 
> SPF
> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
> IPv6 only environments won't be able to work as expected.
> 
> Like:
> If the DNS64 server receives a SPF-record (within either the TXT-RR or
> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
> the ipv4 address according to the same rules as A-records are and
> synthesizes a new SPF record within the response that contains
> additional "ip6" entries. The original "ip4" should not be removed from
> the response.
> What's preventing the SPF record publisher from solving this problem by 
> adding
> the ip6: mechanisms themselves?  Perhaps I don't understand the issue 
> you are
> raising.  Would you please clarify what it is you're asking be done 
> that an
> administrator can't do on their own?
> 
> Scott K
> 
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

_______________________________________________
spfbis mailing list
spfbis@ietf.org
https://www.ietf.org/mailman/listinfo/spfbis
_______________________________________________
spfbis mailing list
spfbis@ietf.org
https://www.ietf.org/mailman/listinfo/spfbis
--=_c6aa061c9193dfca769188b393f7a4dd
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p><br />In regards to SIEVE take a look at examples in http://www.delegate=
=2Eorg/ietf/rfc-html/rfc6134.shtml</p>
<div id=3D"signature"></div>
<p>There are a lot of various types of ip address validation going on that =
is not documented by IETF or any other authority but is in practice done us=
ing various unix utilities. Most of these is just to separate local and ext=
ernal networks but there are real ip address blocks of large sties - both a=
t the router/network and at the local host level. Some companies limit what=
 sites their employees can visit and there are many ways it is done.&nbsp;<=
/p>
<p>And of course for email ip address block lists still exists and in use a=
s well. In some cases DNS is used, in others ip lists are received as files=
 and synced.<br /><br />NAT64 is bound to run into all sorts of issues like=
 this when it begins to be more widely used. And I do think this is positiv=
e step towards IPv6 world. Its just going to take quite some time to work a=
ll these issues out.</p>
<p id=3D"reply-intro">On 2022-02-06 11:13, Klaus Frank wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
I'm not aware that SIEVE would use the source ip address. Also when looking=
 over the main RFCs for it I couldn't find anything that specifies ip valid=
ation. ATM only the EHLO (which uses the PTR-RR) and the SPF validation rel=
y on IP to DNS mapping.<br /><br /><span style=3D"white-space: nowrap;">On&=
nbsp;2022-02-06&nbsp;19:55,&nbsp;<a href=3D"mailto:william@leibzon.org">wil=
liam@leibzon.org</a>&nbsp;wrote:</span>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><br /><br />This is like NAT where entirety of DNS is =
re-written to make internet appear to be IPV6 only. So yes, SPF records wou=
ld be an issue then.<br /><br />There is more than one way to solve it. The=
 proposal to re-write SPF is probably the most correct way within context o=
f NAT64-DNS64. The other option would be to update SPF specifying that vali=
dating servers on IPv6 only network can use IPv4 spf records for validation=
 if the ip address of connecting mail server is a mapped IPv4-&gt;IPv6. Tha=
t is far less elegant though.<br /><br />BTW, I bet SPF is not going to be =
the only protocol with these types of issues. How about SIEVE? Have you che=
cked how well NAT64 inter-operates with that?<br /><br /><span style=3D"whi=
te-space: nowrap;">On&nbsp;2022-02-06&nbsp;10:25,&nbsp;Scott&nbsp;Kitterman=
&nbsp;wrote:</span><br /><br />
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">On&nbsp;Sunday,&n=
bsp;February&nbsp;6,&nbsp;2022&nbsp;1:09:13&nbsp;PM&nbsp;EST&nbsp;Klaus&nbs=
p;Frank&nbsp;wrote:</span>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">Hi,</span><br /><=
br /><span style=3D"white-space: nowrap;">we&nbsp;had&nbsp;some&nbsp;issues=
&nbsp;with&nbsp;SPF&nbsp;and&nbsp;a&nbsp;mail&nbsp;server&nbsp;that&nbsp;wa=
s&nbsp;behind</span><br /><span style=3D"white-space: nowrap;">NAT64+DNS64.=
&nbsp;I&nbsp;at&nbsp;first&nbsp;thought&nbsp;that&nbsp;it&nbsp;was&nbsp;jus=
t&nbsp;a&nbsp;misconfiguration.&nbsp;But</span><br /><span style=3D"white-s=
pace: nowrap;">after&nbsp;the&nbsp;DNS64&nbsp;server&nbsp;seamed&nbsp;to&nb=
sp;work&nbsp;as&nbsp;intended&nbsp;I&nbsp;went&nbsp;to&nbsp;the</span><br /=
><span style=3D"white-space: nowrap;">implementation&nbsp;and&nbsp;the&nbsp=
;RFC.&nbsp;Thereby&nbsp;while&nbsp;reading&nbsp;RFC6147&nbsp;I&nbsp;stumble=
d</span><br /><span style=3D"white-space: nowrap;">across&nbsp;section&nbsp=
;5.3.3&nbsp;which&nbsp;says&nbsp;"All&nbsp;other&nbsp;RRs&nbsp;MUST&nbsp;be=
&nbsp;returned</span><br /><span style=3D"white-space: nowrap;">unchanged."=
&nbsp;which&nbsp;is&nbsp;the&nbsp;cause&nbsp;of&nbsp;my&nbsp;issues.&nbsp;T=
his&nbsp;section&nbsp;is&nbsp;basically</span><br /><span style=3D"white-sp=
ace: nowrap;">ignoring&nbsp;SPF&nbsp;records&nbsp;(RFC7208&nbsp;section&nbs=
p;5.6)&nbsp;and&nbsp;also&nbsp;preventing&nbsp;DNS64</span><br /><span styl=
e=3D"white-space: nowrap;">implementations&nbsp;from&nbsp;addressing&nbsp;t=
his&nbsp;limitation.</span><br /><br /><span style=3D"white-space: nowrap;"=
>Would&nbsp;it&nbsp;be&nbsp;possible&nbsp;to&nbsp;create&nbsp;an&nbsp;exten=
sion&nbsp;to&nbsp;RFC6147&nbsp;that&nbsp;mandates&nbsp;SPF</span><br /><spa=
n style=3D"white-space: nowrap;">record&nbsp;rewrites&nbsp;as&nbsp;well?&nb=
sp;Otherwise&nbsp;Mail&nbsp;servers&nbsp;behind&nbsp;NAT64+DNS64&nbsp;in</s=
pan><br /><span style=3D"white-space: nowrap;">IPv6&nbsp;only&nbsp;environm=
ents&nbsp;won't&nbsp;be&nbsp;able&nbsp;to&nbsp;work&nbsp;as&nbsp;expected.<=
/span><br /><br /><span style=3D"white-space: nowrap;">Like:</span><br /><s=
pan style=3D"white-space: nowrap;">If&nbsp;the&nbsp;DNS64&nbsp;server&nbsp;=
receives&nbsp;a&nbsp;SPF-record&nbsp;(within&nbsp;either&nbsp;the&nbsp;TXT-=
RR&nbsp;or</span><br /><span style=3D"white-space: nowrap;">the&nbsp;SPF-RR=
&nbsp;[RFC4408])&nbsp;containing&nbsp;the&nbsp;"ip4"&nbsp;mechanism&nbsp;it=
&nbsp;MUST&nbsp;rewrites</span><br /><span style=3D"white-space: nowrap;">t=
he&nbsp;ipv4&nbsp;address&nbsp;according&nbsp;to&nbsp;the&nbsp;same&nbsp;ru=
les&nbsp;as&nbsp;A-records&nbsp;are&nbsp;and</span><br /><span style=3D"whi=
te-space: nowrap;">synthesizes&nbsp;a&nbsp;new&nbsp;SPF&nbsp;record&nbsp;wi=
thin&nbsp;the&nbsp;response&nbsp;that&nbsp;contains</span><br /><span style=
=3D"white-space: nowrap;">additional&nbsp;"ip6"&nbsp;entries.&nbsp;The&nbsp=
;original&nbsp;"ip4"&nbsp;should&nbsp;not&nbsp;be&nbsp;removed&nbsp;from</s=
pan><br /><span style=3D"white-space: nowrap;">the&nbsp;response.</span></b=
lockquote>
<br />What's preventing the SPF record publisher from solving this problem =
by adding<br />the ip6: mechanisms themselves? &nbsp;Perhaps I don't unders=
tand the issue you are<br />raising. &nbsp;Would you please clarify what it=
 is you're asking be done that an<br /><span style=3D"white-space: nowrap;"=
>administrator&nbsp;can't&nbsp;do&nbsp;on&nbsp;their&nbsp;own?</span><br />=
<br /><span style=3D"white-space: nowrap;">Scott&nbsp;K</span><br /><br /><=
br />_______________________________________________<br /><span style=3D"wh=
ite-space: nowrap;">spfbis&nbsp;mailing&nbsp;list</span><br /><span style=
=3D"white-space: nowrap;"><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.or=
g</a></span><br /><span style=3D"white-space: nowrap;"><a href=3D"https://w=
ww.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noopener nore=
ferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></span></blockquote>
<br />_______________________________________________<br /><span style=3D"w=
hite-space: nowrap;">spfbis&nbsp;mailing&nbsp;list</span><br /><span style=
=3D"white-space: nowrap;"><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.or=
g</a></span><br /><span style=3D"white-space: nowrap;"><a href=3D"https://w=
ww.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noopener nore=
ferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></span></blockquote>
</div>
<br />
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
_______________________________________________<br />spfbis mailing list<br=
 /><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.org</a><br /><a href=3D"h=
ttps://www.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noope=
ner noreferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></div>
</blockquote>
</body></html>

--=_c6aa061c9193dfca769188b393f7a4dd--


From nobody Sun Feb  6 12:15:11 2022
Return-Path: <klaus.frank@posteo.de>
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 83CF23A0CF1 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:15:08 -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 JPM8M4XYQ2mG for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:15:01 -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 5B6A23A0CEB for <spfbis@ietf.org>; Sun,  6 Feb 2022 12:15:00 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout01.posteo.de (Postfix) with ESMTPS id AA3A3240029 for <spfbis@ietf.org>; Sun,  6 Feb 2022 21:14:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644178497; bh=BN6GSjTtVYNuI0avNTp5Aw2JwQ/217xFaTFpQ9DQ2zI=; h=Date:Subject:To:From:From; b=ASuOFP7KIjkoDHhqiWt7VzoE7fLyRTde5D/rCt0KJGvOftminarnUxWJ872+nK1fj /ZhmUASTf8Ekib/E2Q50X2xx7w8UURNiHC0tp71YyFAoTGvydCMis4hW24XJu3iEqQ z5vNUQL9+4l3vU7qQmsrm2DM3RALra4S7Q6HiE0J6SZ3ZVVC8ts4rxioFFLd8pezeh QWmhTD508X1jvsaFArgVpeYNu+PNtAUq1X7+TdWB5FUhnJtiJXYddaZ2Oc5d63wYi1 H9vWKxO5SJtTStb4jedIyh0m6sJcUs3mTCvix03sgvECSX4EBWAZ0zi5lSxUa8nB9i CFdBzw/jIgFcw==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsL9D5BmHz9rxN for <spfbis@ietf.org>; Sun,  6 Feb 2022 21:14:56 +0100 (CET)
Message-ID: <5c3967a4-ccb8-7a32-b83e-2e20ac81ba1c@posteo.de>
Date: Sun,  6 Feb 2022 20:14:55 +0000
MIME-Version: 1.0
Content-Language: de-DE
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>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <45673006.FIhfuaby8d@localhost>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms020207040308040901060904"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/pD4GQlbGhlZBxTLcDSCCFiYLb5U>
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: Sun, 06 Feb 2022 20:15:09 -0000

This is a cryptographically signed message in MIME format.

--------------ms020207040308040901060904
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


On 2022-02-06 20:57, Scott Kitterman wrote:
> On the SPF side of the discussion, I think it would, at least in theory, be
> feasible to interpret an ip4: mechanism as <prefix> + <address> if the
> connection is IPv6, but I don't see how a receiving SPF processor could know
> what the prefix is.  As I read RFC 6147 Section 5.2, it could be anything.

It could be queried by a AAAA-RR lookup of ipv4only.arpa (RFC7050).

e.g. with the DNS64 server 2606:4700:4700::64 it returns:

  * 64:ff9b::c000:aa
  * 64:ff9b::c000:ab

but without DNS64 using 2606:4700:4700::1111 it doesn't return any AAAA-RR.

The domain ipv4only.arpa is defined to only have A-RRs (192.0.0.171 and 
192.0.0.170).

But you're right. I also think that an addition to RFC6147 would be the 
best and cleanest implementation (as also william@leibzon.org noted in 
his reply).

> I think your original suggestion that an SPF record be modified by the DNS64
> server to add ip6: mechanisms with <prefix> + <address> is a reasonable path
> forward, but I think it's really an RFC 6147 discussion, not so much RFC 7208.
> It is not, however, without risks.  RFC 7208 Section 3.4 gives advice on SPF
> record size.  Your proposed approach would increase the record size, which, in
> theory, could be problematic.  It might be that anything running on an IPv6
> only network is modern enough that this isn't actually a problem.  I don't
> know.
Right, the SPF record size is limited. I completely forgot about that. 
But reading that part of the RFC, I don't think that that's a problem, 
as it's very common to put validation tokens into TXT. And the RFC also 
says that the size limit would include them as well. Also the issue 
would solely lie on the side of the party that also implements DNS64, so 
adjusting a firewall to allow ENDS0 or DNS-over-TCP should be in scope 
for them.

--------------ms020207040308040901060904
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYyMDE0NTVaME8GCSqGSIb3DQEJBDFCBEBd7NxImJ0GhkiLJeqByX8V
H150l5C5hZ5+7CXZtR9vT0mLWRR3dMgQmKfGsv9fUABcqiH4TKGm/NEzJQJko+6lMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAKxLco9m
YefWvCw2dZCOZu4TlHV9AdozUpnS88EJpOpggtonw3a0z6QBa1/HZtEEVzLqbgBxpeyR5q4n
LD99jWqiJwPraBC6NkIabBNIl06HDeexDpMjb0jdDjyL3GcOgiQnl27s18j/vvCc8K3o/0yW
oi2JUESLhZo/l7E4XEhNFkx2PCzDZn3tZYBx92l+aXcGqGnyvnOhxXAfcWvtt7F7IpaZ/AvT
1rss48SNsGfJEznM2RednzcU8HsIH+QHZXYsQr+s4v8kDv7kTbwPlUxxoKW/8Cbh+n8qkT1P
KuP7bHVH8LOspEXEF7GwaJb7jpX2Ajhhp6tVmZRsDOSRKPuJqbKgp0OU8JWava5wM3UalzsC
xsyoiheVY2kZd2a/dFiWsKXatjT7dGC78rpg6wxfPVoFO425Ia416E0GjeOXRxDfr2fUUlNG
iIwYvwQ4Bkr6h5Z2BOliwjbtGb2yITRURSYg+KR2BeFME3/ZcG/n8IkIkuN71SqsGC9IiOxQ
yrQyeg6OojZTSKlNQC8V2Zl3mI45ousDW46SO2K5H4jqJNJ+/Qgpyl+C2vKxLsxOqjCyVKP7
+/IAIVb2o8Myhelb/G4VL2kmHmK3pFgDMY4cqui+aqG1qg/J0sOZdjz4smkv1KcX6cN4nqeM
Y1Gjj90uItp4MdMsbEcRQym7A+EqAAAAAAAA
--------------ms020207040308040901060904--


From nobody Sun Feb  6 12:21:55 2022
Return-Path: <klaus.frank@posteo.de>
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 CCF993A0D02 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:21:52 -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 PLWZ7ma3jLW4 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:21:47 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 EC76F3A0CFD for <spfbis@ietf.org>; Sun,  6 Feb 2022 12:21:46 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id A6EFC240107 for <spfbis@ietf.org>; Sun,  6 Feb 2022 21:21:42 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644178903; bh=D+RmdGd8IwwKwR4bmFnCeYOrd7rNL3boxYx/p/fpbW8=; h=Date:Subject:To:Cc:From:From; b=pwJAqIu3FuOA+CPl7jebFsnEgpc5EwR2956kqnW8GsrkVjjfFRIV7zgNcsRpsYmWu 8xpYbC759FD8Vgvu7/+5ksYOBAILe0/JsPKKBS23NKFsOeaz51Sd92BVfi7BX9TvHg Nj+j4kGacrw8EcR9TNPITw5/xdPWpvkdyGdRFgT23zhe5eyWD0D3cmVrn77vbhOqPr ZWHAcY59PsdZnV4Cm5JXfLG8SDB5l5B9s4JuG22ejeNf28Tu0pscKpBj2hOmQN/B+X b3evcakWwuvEhBngGdFku4x+U0mtDWdhiEhUALCPbabCyaatFfaUsmXXpR/euA3qaO MtAMLWZqFS+bA==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsLK14yXbz9rxD; Sun,  6 Feb 2022 21:21:41 +0100 (CET)
Message-ID: <6745ef81-3b55-de02-b6c7-def2d6d33e61@posteo.de>
Date: Sun,  6 Feb 2022 20:21:40 +0000
MIME-Version: 1.0
Content-Language: en-US
To: william@leibzon.org
Cc: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost> <d606050e47c4ae22b53448e56ff29ad2@leibzon.org> <7683f14e-113c-e339-f499-bc75bc1644a0@posteo.de> <5f14e191ab8239dd5dae0e4fbac7d223@leibzon.org>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <5f14e191ab8239dd5dae0e4fbac7d223@leibzon.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms070502040707040902050507"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/KOR_Jvzc1SsVa5Ss93GIrdAQbX8>
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: Sun, 06 Feb 2022 20:21:53 -0000

This is a cryptographically signed message in MIME format.

--------------ms070502040707040902050507
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

But if I see that correctly that's a list that the admin of the 
recipient side has under his control and could update, right? Therefore 
the same entity that deploys DNS64 would just have to make sure to also 
update the list of IPs within their SIEVE configuration, right?

If so a possible migration would be to duplicate these sections with the 
corresponding NAT64 addresses and after NAT64+DNS64 is deployed for the 
mail infrastructure to decommission the ipv4 only ones.

This doesn't look like a hard/RFC limitation (like the SPF record thing) 
to me. Or am I missing something?

On 2022-02-06 21:10, william@leibzon.org wrote:
>
>
> In regards to SIEVE take a look at examples in 
> http://www.delegate.org/ietf/rfc-html/rfc6134.shtml
>
> There are a lot of various types of ip address validation going on 
> that is not documented by IETF or any other authority but is in 
> practice done using various unix utilities. Most of these is just to 
> separate local and external networks but there are real ip address 
> blocks of large sties - both at the router/network and at the local 
> host level. Some companies limit what sites their employees can visit 
> and there are many ways it is done.
>
> And of course for email ip address block lists still exists and in use 
> as well. In some cases DNS is used, in others ip lists are received as 
> files and synced.
>
> NAT64 is bound to run into all sorts of issues like this when it 
> begins to be more widely used. And I do think this is positive step 
> towards IPv6 world. Its just going to take quite some time to work all 
> these issues out.
>
> On 2022-02-06 11:13, Klaus Frank wrote:
>
>> I'm not aware that SIEVE would use the source ip address. Also when 
>> looking over the main RFCs for it I couldn't find anything that 
>> specifies ip validation. ATM only the EHLO (which uses the PTR-RR) 
>> and the SPF validation rely on IP to DNS mapping.
>>
>> On 2022-02-06 19:55, william@leibzon.org wrote:
>>>
>>>
>>> This is like NAT where entirety of DNS is re-written to make 
>>> internet appear to be IPV6 only. So yes, SPF records would be an 
>>> issue then.
>>>
>>> There is more than one way to solve it. The proposal to re-write SPF 
>>> is probably the most correct way within context of NAT64-DNS64. The 
>>> other option would be to update SPF specifying that validating 
>>> servers on IPv6 only network can use IPv4 spf records for validation 
>>> if the ip address of connecting mail server is a mapped IPv4->IPv6. 
>>> That is far less elegant though.
>>>
>>> BTW, I bet SPF is not going to be the only protocol with these types 
>>> of issues. How about SIEVE? Have you checked how well NAT64 
>>> inter-operates with that?
>>>
>>> On 2022-02-06 10:25, Scott Kitterman wrote:
>>>
>>>> On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote:
>>>>> Hi,
>>>>>
>>>>> we had some issues with SPF and a mail server that was behind
>>>>> NAT64+DNS64. I at first thought that it was just a misconfiguration. But
>>>>> after the DNS64 server seamed to work as intended I went to the
>>>>> implementation and the RFC. Thereby while reading RFC6147 I stumbled
>>>>> across section 5.3.3 which says "All other RRs MUST be returned
>>>>> unchanged." which is the cause of my issues. This section is basically
>>>>> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
>>>>> implementations from addressing this limitation.
>>>>>
>>>>> Would it be possible to create an extension to RFC6147 that mandates SPF
>>>>> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
>>>>> IPv6 only environments won't be able to work as expected.
>>>>>
>>>>> Like:
>>>>> If the DNS64 server receives a SPF-record (within either the TXT-RR or
>>>>> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
>>>>> the ipv4 address according to the same rules as A-records are and
>>>>> synthesizes a new SPF record within the response that contains
>>>>> additional "ip6" entries. The original "ip4" should not be removed from
>>>>> the response.
>>>>
>>>> What's preventing the SPF record publisher from solving this 
>>>> problem by adding
>>>> the ip6: mechanisms themselves?  Perhaps I don't understand the 
>>>> issue you are
>>>> raising.  Would you please clarify what it is you're asking be done 
>>>> that an
>>>> administrator can't do on their own?
>>>>
>>>> Scott K
>>>>
>>>>
>>>> _______________________________________________
>>>> spfbis mailing list
>>>> spfbis@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/spfbis
>>>
>>> _______________________________________________
>>> spfbis mailing list
>>> spfbis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spfbis
>>
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms070502040707040902050507
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYyMDIxNDBaME8GCSqGSIb3DQEJBDFCBEDzNdMrMObVkQE/Atw69Zv8
r7rjHYAdjfTAwxTwtql51SJe1p+gHjbsoPi1MCh8U99EWYQPOu1hHkUah+XPmG3yMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAATNO04W
ALhXzTmBGU296+VczcA03sc1D0Y4TDGf5UlnsMPpT8eiiNZGm82M/xnuzQgxN4p29dTaV7vz
muGeQerjsVnbbdBFRLXgGolUv7UezAmDDTcVH2UvO+8GyG0Sz/eTEjhlzTfKtZeb/Otr9QDG
jrbhYUkKK5uuSzWdn+tbIJr9EnbQqMIXY/rMrC7MFkccA864keocZd8ClnDiq+V7noWxwKx/
YehEE18c2gwe6m2SWHcXJ3LF34uVFgOx5UeVwMZhDnTz1qfSkmmE6cHjx6/hxt0iATboNwq5
tiIYw0GCJfQ2OA4gE7Vas0xFU2KHYvBwVq9ZDDAJ/s4BiXspXKwAMXYyLUCx5GgLUS3rMO+V
T/4Ky3ekTIBS5EUR3ZfQY+Wsyv2LFXqOFZvThW4U1swTzNpt6oWdznu/E8JcyPPEpHrW9Ulj
lQkc89cFdFnJppU1V17xzLra2M4+c+oVKrWwe/8ANGbeSbtwU9kLmYlNIA/VzeFIuznY7F2f
95zbX8Rqaf5ORHPdfeufy9nZCWHBDLG6GV7h4arbtaD3yrS83EhSUBvre2hhfByG629272vJ
YrdSwluS7u2nbI6+O6E3UIRAGqUf3y+SnjraGJuxmrIcsarrNm0Fwkkne5q4gV6Y/cqMdUhL
aStdU3vnRGQ2rarBFmf1J3IJQfAIAAAAAAAA
--------------ms070502040707040902050507--


From nobody Sun Feb  6 12:44:46 2022
Return-Path: <william@leibzon.org>
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 8C04D3A0D48 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 NEPY21yThQ_f for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:44:38 -0800 (PST)
Received: from relay5.hostedemail.com (relay5.hostedemail.com [64.99.140.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95DBB3A0D47 for <spfbis@ietf.org>; Sun,  6 Feb 2022 12:44:38 -0800 (PST)
Received: from omf15.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id DF99822855; Sun,  6 Feb 2022 20:44:36 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: william@leibzon.org) by omf15.hostedemail.com (Postfix) with ESMTPA id 8D46B1E;  Sun,  6 Feb 2022 20:44:18 +0000 (UTC)
MIME-Version: 1.0
Date: Sun, 06 Feb 2022 12:44:36 -0800
From: william@leibzon.org
To: Klaus Frank <klaus.frank@posteo.de>
Cc: spfbis@ietf.org
In-Reply-To: <6745ef81-3b55-de02-b6c7-def2d6d33e61@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost> <d606050e47c4ae22b53448e56ff29ad2@leibzon.org> <7683f14e-113c-e339-f499-bc75bc1644a0@posteo.de> <5f14e191ab8239dd5dae0e4fbac7d223@leibzon.org> <6745ef81-3b55-de02-b6c7-def2d6d33e61@posteo.de>
Message-ID: <d766a8ec819493fefb89d60c3180d8e3@leibzon.org>
X-Sender: william@leibzon.org
Content-Type: multipart/alternative; boundary="=_a649f8b754ccf4f91ecaa20c331ee951"
X-Stat-Signature: 9j557e3d37yfwj67zqu4mgeebaemi5kb
X-Rspamd-Server: rspamout04
X-Rspamd-Queue-Id: 8D46B1E
X-Session-Marker: 77696C6C69616D406C6569627A6F6E2E6F7267
X-Session-ID: U2FsdGVkX1+BCBsdXVe0PEIZoeVzo96AITgJmFj+134=
X-HE-Tag: 1644180258-850650
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/a5LxuGx7lgFGTMbrVqG1fU2Y2Oc>
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: Sun, 06 Feb 2022 20:44:45 -0000

--=_a649f8b754ccf4f91ecaa20c331ee951
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII;
 format=flowed



These are closer to implementation, yes. But how SIEVE is used is that a 
mail server operator can be on one network and they have users on other 
networks that use this protocol to tell the operator what their mail 
filtering preferences are. So mail server operator (if they were behind 
NAT64) would have to do this re-writing or re-interpretation of SIEVE 
rules. This may require knowledge of how IPv4 is mapped to IPv6 for 
them. And it is not much different than trying to re-interpret SPF 
records when on IPv6 only network.

One of the ways of solving issues like this is special IPv4 in-addr like 
dns map and lookup which would allow hosts behind NAT64 to find what 
IPv4->IPv6 translation for their site is when they have an IPv4 address 
from some filtering system or protocol and they need to locally 
re-interpret it. This is not as elegant as DNS64 rewriting but I think 
its going to be needed in the end anyway for various cases (maybe as 
interim solution).

On 2022-02-06 12:21, Klaus Frank wrote:

> But if I see that correctly that's a list that the admin of the 
> recipient side has under his control and could update, right? Therefore 
> the same entity that deploys DNS64 would just have to make sure to also 
> update the list of IPs within their SIEVE configuration, right?
> 
> If so a possible migration would be to duplicate these sections with 
> the corresponding NAT64 addresses and after NAT64+DNS64 is deployed for 
> the mail infrastructure to decommission the ipv4 only ones.
> 
> This doesn't look like a hard/RFC limitation (like the SPF record 
> thing) to me. Or am I missing something?
> 
> On 2022-02-06 21:10, william@leibzon.org wrote:
> 
> In regards to SIEVE take a look at examples in 
> http://www.delegate.org/ietf/rfc-html/rfc6134.shtml
> 
> There are a lot of various types of ip address validation going on that 
> is not documented by IETF or any other authority but is in practice 
> done using various unix utilities. Most of these is just to separate 
> local and external networks but there are real ip address blocks of 
> large sties - both at the router/network and at the local host level. 
> Some companies limit what sites their employees can visit and there are 
> many ways it is done.
> 
> And of course for email ip address block lists still exists and in use 
> as well. In some cases DNS is used, in others ip lists are received as 
> files and synced.
> 
> NAT64 is bound to run into all sorts of issues like this when it begins 
> to be more widely used. And I do think this is positive step towards 
> IPv6 world. Its just going to take quite some time to work all these 
> issues out.
> 
> On 2022-02-06 11:13, Klaus Frank wrote:
> 
> I'm not aware that SIEVE would use the source ip address. Also when 
> looking over the main RFCs for it I couldn't find anything that 
> specifies ip validation. ATM only the EHLO (which uses the PTR-RR) and 
> the SPF validation rely on IP to DNS mapping.
> 
> On 2022-02-06 19:55, william@leibzon.org wrote:
> 
> This is like NAT where entirety of DNS is re-written to make internet 
> appear to be IPV6 only. So yes, SPF records would be an issue then.
> 
> There is more than one way to solve it. The proposal to re-write SPF is 
> probably the most correct way within context of NAT64-DNS64. The other 
> option would be to update SPF specifying that validating servers on 
> IPv6 only network can use IPv4 spf records for validation if the ip 
> address of connecting mail server is a mapped IPv4->IPv6. That is far 
> less elegant though.
> 
> BTW, I bet SPF is not going to be the only protocol with these types of 
> issues. How about SIEVE? Have you checked how well NAT64 inter-operates 
> with that?
> 
> On 2022-02-06 10:25, Scott Kitterman wrote:
> 
> On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote: Hi,
> 
> we had some issues with SPF and a mail server that was behind
> NAT64+DNS64. I at first thought that it was just a misconfiguration. 
> But
> after the DNS64 server seamed to work as intended I went to the
> implementation and the RFC. Thereby while reading RFC6147 I stumbled
> across section 5.3.3 which says "All other RRs MUST be returned
> unchanged." which is the cause of my issues. This section is basically
> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
> implementations from addressing this limitation.
> 
> Would it be possible to create an extension to RFC6147 that mandates 
> SPF
> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
> IPv6 only environments won't be able to work as expected.
> 
> Like:
> If the DNS64 server receives a SPF-record (within either the TXT-RR or
> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
> the ipv4 address according to the same rules as A-records are and
> synthesizes a new SPF record within the response that contains
> additional "ip6" entries. The original "ip4" should not be removed from
> the response.
> What's preventing the SPF record publisher from solving this problem by 
> adding
> the ip6: mechanisms themselves?  Perhaps I don't understand the issue 
> you are
> raising.  Would you please clarify what it is you're asking be done 
> that an
> administrator can't do on their own?
> 
> Scott K
> 
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

_______________________________________________
spfbis mailing list
spfbis@ietf.org
https://www.ietf.org/mailman/listinfo/spfbis
_______________________________________________
spfbis mailing list
spfbis@ietf.org
https://www.ietf.org/mailman/listinfo/spfbis
_______________________________________________
spfbis mailing list
spfbis@ietf.org
https://www.ietf.org/mailman/listinfo/spfbis
--=_a649f8b754ccf4f91ecaa20c331ee951
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<div id=3D"signature"></div>
<p><br />These are closer to implementation, yes. But how SIEVE is used is =
that a mail server operator can be on one network and they have users on ot=
her networks that use this protocol to tell the operator what their mail fi=
ltering preferences are. So mail server operator (if they were behind NAT64=
) would have to do this re-writing or re-interpretation of SIEVE rules. Thi=
s may require knowledge of how IPv4 is mapped to IPv6 for them. And it is n=
ot much different than trying to re-interpret SPF records when on IPv6 only=
 network.<br /><br />One of the ways of solving issues like this is special=
 IPv4 in-addr like dns map and lookup which would allow hosts behind NAT64 =
to find what IPv4-&gt;IPv6 translation for their site is when they have an =
IPv4 address from some filtering system or protocol and they need to locall=
y re-interpret it. This is not as elegant as DNS64 rewriting but I think it=
s going to be needed in the end anyway for various cases (maybe as interim =
solution).<br /><br />On 2022-02-06 12:21, Klaus Frank wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
But if I see that correctly that's a list that the admin of the recipient s=
ide has under his control and could update, right? Therefore the same entit=
y that deploys DNS64 would just have to make sure to also update the list o=
f IPs within their SIEVE configuration, right?<br /><br />If so a possible =
migration would be to duplicate these sections with the corresponding NAT64=
 addresses and after NAT64+DNS64 is deployed for the mail infrastructure to=
 decommission the ipv4 only ones.<br /><br />This doesn't look like a hard/=
RFC limitation (like the SPF record thing) to me. Or am I missing something=
?<br /><br /><span style=3D"white-space: nowrap;">On&nbsp;2022-02-06&nbsp;2=
1:10,&nbsp;<a href=3D"mailto:william@leibzon.org">william@leibzon.org</a>&n=
bsp;wrote:</span>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><br /><br />In regards to SIEVE take a look at example=
s in <a href=3D"http://www.delegate.org/ietf/rfc-html/rfc6134.shtml" target=
=3D"_blank" rel=3D"noopener noreferrer">http://www.delegate.org/ietf/rfc-ht=
ml/rfc6134.shtml</a><br /><br />There are a lot of various types of ip addr=
ess validation going on that is not documented by IETF or any other authori=
ty but is in practice done using various unix utilities. Most of these is j=
ust to separate local and external networks but there are real ip address b=
locks of large sties - both at the router/network and at the local host lev=
el. Some companies limit what sites their employees can visit and there are=
 many ways it is done.<br /><br />And of course for email ip address block =
lists still exists and in use as well. In some cases DNS is used, in others=
 ip lists are received as files and synced.<br /><br />NAT64 is bound to ru=
n into all sorts of issues like this when it begins to be more widely used.=
 And I do think this is positive step towards IPv6 world. Its just going to=
 take quite some time to work all these issues out.<br /><br /><span style=
=3D"white-space: nowrap;">On&nbsp;2022-02-06&nbsp;11:13,&nbsp;Klaus&nbsp;Fr=
ank&nbsp;wrote:</span><br /><br />
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">I'm not aware that SIEVE would use the source ip addre=
ss. Also when looking over the main RFCs for it I couldn't find anything th=
at specifies ip validation. ATM only the EHLO (which uses the PTR-RR) and t=
he SPF validation rely on IP to DNS mapping.<br /><br /><span style=3D"whit=
e-space: nowrap;">On&nbsp;2022-02-06&nbsp;19:55,&nbsp;william@leibzon.org&n=
bsp;wrote:</span>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><br /><br />This is like NAT where entirety of DNS is =
re-written to make internet appear to be IPV6 only. So yes, SPF records wou=
ld be an issue then.<br /><br />There is more than one way to solve it. The=
 proposal to re-write SPF is probably the most correct way within context o=
f NAT64-DNS64. The other option would be to update SPF specifying that vali=
dating servers on IPv6 only network can use IPv4 spf records for validation=
 if the ip address of connecting mail server is a mapped IPv4-&gt;IPv6. Tha=
t is far less elegant though.<br /><br />BTW, I bet SPF is not going to be =
the only protocol with these types of issues. How about SIEVE? Have you che=
cked how well NAT64 inter-operates with that?<br /><br /><span style=3D"whi=
te-space: nowrap;">On&nbsp;2022-02-06&nbsp;10:25,&nbsp;Scott&nbsp;Kitterman=
&nbsp;wrote:</span><br /><br />
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">On&nbsp;Sunday,&n=
bsp;February&nbsp;6,&nbsp;2022&nbsp;1:09:13&nbsp;PM&nbsp;EST&nbsp;Klaus&nbs=
p;Frank&nbsp;wrote:</span>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">Hi,</span><br /><=
br /><span style=3D"white-space: nowrap;">we&nbsp;had&nbsp;some&nbsp;issues=
&nbsp;with&nbsp;SPF&nbsp;and&nbsp;a&nbsp;mail&nbsp;server&nbsp;that&nbsp;wa=
s&nbsp;behind</span><br /><span style=3D"white-space: nowrap;">NAT64+DNS64.=
&nbsp;I&nbsp;at&nbsp;first&nbsp;thought&nbsp;that&nbsp;it&nbsp;was&nbsp;jus=
t&nbsp;a&nbsp;misconfiguration.&nbsp;But</span><br /><span style=3D"white-s=
pace: nowrap;">after&nbsp;the&nbsp;DNS64&nbsp;server&nbsp;seamed&nbsp;to&nb=
sp;work&nbsp;as&nbsp;intended&nbsp;I&nbsp;went&nbsp;to&nbsp;the</span><br /=
><span style=3D"white-space: nowrap;">implementation&nbsp;and&nbsp;the&nbsp=
;RFC.&nbsp;Thereby&nbsp;while&nbsp;reading&nbsp;RFC6147&nbsp;I&nbsp;stumble=
d</span><br /><span style=3D"white-space: nowrap;">across&nbsp;section&nbsp=
;5.3.3&nbsp;which&nbsp;says&nbsp;"All&nbsp;other&nbsp;RRs&nbsp;MUST&nbsp;be=
&nbsp;returned</span><br /><span style=3D"white-space: nowrap;">unchanged."=
&nbsp;which&nbsp;is&nbsp;the&nbsp;cause&nbsp;of&nbsp;my&nbsp;issues.&nbsp;T=
his&nbsp;section&nbsp;is&nbsp;basically</span><br /><span style=3D"white-sp=
ace: nowrap;">ignoring&nbsp;SPF&nbsp;records&nbsp;(RFC7208&nbsp;section&nbs=
p;5.6)&nbsp;and&nbsp;also&nbsp;preventing&nbsp;DNS64</span><br /><span styl=
e=3D"white-space: nowrap;">implementations&nbsp;from&nbsp;addressing&nbsp;t=
his&nbsp;limitation.</span><br /><br /><span style=3D"white-space: nowrap;"=
>Would&nbsp;it&nbsp;be&nbsp;possible&nbsp;to&nbsp;create&nbsp;an&nbsp;exten=
sion&nbsp;to&nbsp;RFC6147&nbsp;that&nbsp;mandates&nbsp;SPF</span><br /><spa=
n style=3D"white-space: nowrap;">record&nbsp;rewrites&nbsp;as&nbsp;well?&nb=
sp;Otherwise&nbsp;Mail&nbsp;servers&nbsp;behind&nbsp;NAT64+DNS64&nbsp;in</s=
pan><br /><span style=3D"white-space: nowrap;">IPv6&nbsp;only&nbsp;environm=
ents&nbsp;won't&nbsp;be&nbsp;able&nbsp;to&nbsp;work&nbsp;as&nbsp;expected.<=
/span><br /><br /><span style=3D"white-space: nowrap;">Like:</span><br /><s=
pan style=3D"white-space: nowrap;">If&nbsp;the&nbsp;DNS64&nbsp;server&nbsp;=
receives&nbsp;a&nbsp;SPF-record&nbsp;(within&nbsp;either&nbsp;the&nbsp;TXT-=
RR&nbsp;or</span><br /><span style=3D"white-space: nowrap;">the&nbsp;SPF-RR=
&nbsp;[RFC4408])&nbsp;containing&nbsp;the&nbsp;"ip4"&nbsp;mechanism&nbsp;it=
&nbsp;MUST&nbsp;rewrites</span><br /><span style=3D"white-space: nowrap;">t=
he&nbsp;ipv4&nbsp;address&nbsp;according&nbsp;to&nbsp;the&nbsp;same&nbsp;ru=
les&nbsp;as&nbsp;A-records&nbsp;are&nbsp;and</span><br /><span style=3D"whi=
te-space: nowrap;">synthesizes&nbsp;a&nbsp;new&nbsp;SPF&nbsp;record&nbsp;wi=
thin&nbsp;the&nbsp;response&nbsp;that&nbsp;contains</span><br /><span style=
=3D"white-space: nowrap;">additional&nbsp;"ip6"&nbsp;entries.&nbsp;The&nbsp=
;original&nbsp;"ip4"&nbsp;should&nbsp;not&nbsp;be&nbsp;removed&nbsp;from</s=
pan><br /><span style=3D"white-space: nowrap;">the&nbsp;response.</span></b=
lockquote>
<br />What's preventing the SPF record publisher from solving this problem =
by adding<br />the ip6: mechanisms themselves? &nbsp;Perhaps I don't unders=
tand the issue you are<br />raising. &nbsp;Would you please clarify what it=
 is you're asking be done that an<br /><span style=3D"white-space: nowrap;"=
>administrator&nbsp;can't&nbsp;do&nbsp;on&nbsp;their&nbsp;own?</span><br />=
<br /><span style=3D"white-space: nowrap;">Scott&nbsp;K</span><br /><br /><=
br />_______________________________________________<br /><span style=3D"wh=
ite-space: nowrap;">spfbis&nbsp;mailing&nbsp;list</span><br /><span style=
=3D"white-space: nowrap;"><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.or=
g</a></span><br /><span style=3D"white-space: nowrap;"><a href=3D"https://w=
ww.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noopener nore=
ferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></span></blockquote>
<br />_______________________________________________<br /><span style=3D"w=
hite-space: nowrap;">spfbis&nbsp;mailing&nbsp;list</span><br /><span style=
=3D"white-space: nowrap;"><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.or=
g</a></span><br /><span style=3D"white-space: nowrap;"><a href=3D"https://w=
ww.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noopener nore=
ferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></span></blockquote>
<br />_______________________________________________<br /><span style=3D"w=
hite-space: nowrap;">spfbis&nbsp;mailing&nbsp;list</span><br /><span style=
=3D"white-space: nowrap;"><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.or=
g</a></span><br /><span style=3D"white-space: nowrap;"><a href=3D"https://w=
ww.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noopener nore=
ferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></span></blockquote>
</blockquote>
</div>
<br />
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
_______________________________________________<br />spfbis mailing list<br=
 /><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.org</a><br /><a href=3D"h=
ttps://www.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noope=
ner noreferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></div>
</blockquote>
</body></html>

--=_a649f8b754ccf4f91ecaa20c331ee951--


From nobody Sun Feb  6 12:58:12 2022
Return-Path: <klaus.frank@posteo.de>
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 9840D3A0D66 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:58:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 ZWeWGrilsn5O for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 12:58:02 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 5F5A23A0D65 for <spfbis@ietf.org>; Sun,  6 Feb 2022 12:58:01 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id 64392240103 for <spfbis@ietf.org>; Sun,  6 Feb 2022 21:57:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644181076; bh=Ns5aTnHzfJHOvEscr1PqYXYAmK0qD2PVyF3uXKZOELo=; h=Date:Subject:To:Cc:From:From; b=qWb+zxhvfSDNKWtUh7PAinysP0mlNQpuUvTkI1wTcaDqbSamTQJA9mKvl6diFOJYA 0l4YRqF9Ub75QPyWpkKpjI9IsFD7qj0Kf14vuzNlV6aIOsa5DN1Wkq2vZmbzAR04aM CQZAVenzgStIxrhU5yTRgdTmLdugeeslwDDHgHEEb4ZaPR2gGSRqUScv7RqSZho3wF hfHOKeMFApw8TjOCm2qZv1MrkmxH5q8M4bGErsmp1s8iYFD9TK4OpztNRCvjcM5p74 E7eDEFv1CBLWf1KQaHiTsEJAhuLAZOfuJB08BMcxQ0tHL77w8i57Gpm7yHN/3h999f dHLlECKcXqSGA==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsM6q3FmCz9rxP; Sun,  6 Feb 2022 21:57:55 +0100 (CET)
Message-ID: <b2930d9e-c0f8-e5fb-56f4-3427caa1cf9b@posteo.de>
Date: Sun,  6 Feb 2022 20:57:54 +0000
MIME-Version: 1.0
Content-Language: en-US
To: william@leibzon.org
Cc: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <2098569.QsC3VX2HWt@localhost> <d606050e47c4ae22b53448e56ff29ad2@leibzon.org> <7683f14e-113c-e339-f499-bc75bc1644a0@posteo.de> <5f14e191ab8239dd5dae0e4fbac7d223@leibzon.org> <6745ef81-3b55-de02-b6c7-def2d6d33e61@posteo.de> <d766a8ec819493fefb89d60c3180d8e3@leibzon.org>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <d766a8ec819493fefb89d60c3180d8e3@leibzon.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms030806070306090703080208"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/9NDTJQICg_EhStt-B6aUg2O_Lq0>
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: Sun, 06 Feb 2022 20:58:09 -0000

This is a cryptographically signed message in MIME format.

--------------ms030806070306090703080208
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit


On 2022-02-06 21:44, william@leibzon.org wrote:
>
>
> These are closer to implementation, yes. But how SIEVE is used is that 
> a mail server operator can be on one network and they have users on 
> other networks that use this protocol to tell the operator what their 
> mail filtering preferences are. So mail server operator (if they were 
> behind NAT64) would have to do this re-writing or re-interpretation of 
> SIEVE rules. This may require knowledge of how IPv4 is mapped to IPv6 
> for them. And it is not much different than trying to re-interpret SPF 
> records when on IPv6 only network.
>
 From my perspective SPF should be covered as it's also DNS and when 
doing DNS64 it's reasonable for the admin to assume that it's consistent 
and complete. Therefore translating the SPF would be something that 
anyone using DNS64 would take as given.

SIEVE on the other hand isn't part of DNS. I'd consider it more like a 
firewall. Another system that does filtering utilizing DNS but not being 
part of DNS. And for those systems there is RFC7050 
https://datatracker.ietf.org/doc/html/rfc7050#section-3.4 or the admin 
manually updating the IPs in the configuration.

But for SPF on the other hand we're basically serving incorrect 
information from an admins perspective. As DNS64+NAT64 should make the 
IPv4 internet a part of the ipv6 only internet, but then it doesn't 
serve ipv6 IPs within the SPF...

> One of the ways of solving issues like this is special IPv4 in-addr 
> like dns map and lookup which would allow hosts behind NAT64 to find 
> what IPv4->IPv6 translation for their site is when they have an IPv4 
> address from some filtering system or protocol and they need to 
> locally re-interpret it. This is not as elegant as DNS64 rewriting but 
> I think its going to be needed in the end anyway for various cases 
> (maybe as interim solution).
>
> On 2022-02-06 12:21, Klaus Frank wrote:
>
>> But if I see that correctly that's a list that the admin of the 
>> recipient side has under his control and could update, right? 
>> Therefore the same entity that deploys DNS64 would just have to make 
>> sure to also update the list of IPs within their SIEVE configuration, 
>> right?
>>
>> If so a possible migration would be to duplicate these sections with 
>> the corresponding NAT64 addresses and after NAT64+DNS64 is deployed 
>> for the mail infrastructure to decommission the ipv4 only ones.
>>
>> This doesn't look like a hard/RFC limitation (like the SPF record 
>> thing) to me. Or am I missing something?
>>
>> On 2022-02-06 21:10, william@leibzon.org wrote:
>>>
>>>
>>> In regards to SIEVE take a look at examples in 
>>> http://www.delegate.org/ietf/rfc-html/rfc6134.shtml
>>>
>>> There are a lot of various types of ip address validation going on 
>>> that is not documented by IETF or any other authority but is in 
>>> practice done using various unix utilities. Most of these is just to 
>>> separate local and external networks but there are real ip address 
>>> blocks of large sties - both at the router/network and at the local 
>>> host level. Some companies limit what sites their employees can 
>>> visit and there are many ways it is done.
>>>
>>> And of course for email ip address block lists still exists and in 
>>> use as well. In some cases DNS is used, in others ip lists are 
>>> received as files and synced.
>>>
>>> NAT64 is bound to run into all sorts of issues like this when it 
>>> begins to be more widely used. And I do think this is positive step 
>>> towards IPv6 world. Its just going to take quite some time to work 
>>> all these issues out.
>>>
>>> On 2022-02-06 11:13, Klaus Frank wrote:
>>>
>>>> I'm not aware that SIEVE would use the source ip address. Also when 
>>>> looking over the main RFCs for it I couldn't find anything that 
>>>> specifies ip validation. ATM only the EHLO (which uses the PTR-RR) 
>>>> and the SPF validation rely on IP to DNS mapping.
>>>>
>>>> On 2022-02-06 19:55, william@leibzon.org wrote:
>>>>>
>>>>>
>>>>> This is like NAT where entirety of DNS is re-written to make 
>>>>> internet appear to be IPV6 only. So yes, SPF records would be an 
>>>>> issue then.
>>>>>
>>>>> There is more than one way to solve it. The proposal to re-write 
>>>>> SPF is probably the most correct way within context of 
>>>>> NAT64-DNS64. The other option would be to update SPF specifying 
>>>>> that validating servers on IPv6 only network can use IPv4 spf 
>>>>> records for validation if the ip address of connecting mail server 
>>>>> is a mapped IPv4->IPv6. That is far less elegant though.
>>>>>
>>>>> BTW, I bet SPF is not going to be the only protocol with these 
>>>>> types of issues. How about SIEVE? Have you checked how well NAT64 
>>>>> inter-operates with that?
>>>>>
>>>>> On 2022-02-06 10:25, Scott Kitterman wrote:
>>>>>
>>>>>> On Sunday, February 6, 2022 1:09:13 PM EST Klaus Frank wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> we had some issues with SPF and a mail server that was behind
>>>>>>> NAT64+DNS64. I at first thought that it was just a misconfiguration. But
>>>>>>> after the DNS64 server seamed to work as intended I went to the
>>>>>>> implementation and the RFC. Thereby while reading RFC6147 I stumbled
>>>>>>> across section 5.3.3 which says "All other RRs MUST be returned
>>>>>>> unchanged." which is the cause of my issues. This section is basically
>>>>>>> ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64
>>>>>>> implementations from addressing this limitation.
>>>>>>>
>>>>>>> Would it be possible to create an extension to RFC6147 that mandates SPF
>>>>>>> record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 in
>>>>>>> IPv6 only environments won't be able to work as expected.
>>>>>>>
>>>>>>> Like:
>>>>>>> If the DNS64 server receives a SPF-record (within either the TXT-RR or
>>>>>>> the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites
>>>>>>> the ipv4 address according to the same rules as A-records are and
>>>>>>> synthesizes a new SPF record within the response that contains
>>>>>>> additional "ip6" entries. The original "ip4" should not be removed from
>>>>>>> the response.
>>>>>>
>>>>>> What's preventing the SPF record publisher from solving this 
>>>>>> problem by adding
>>>>>> the ip6: mechanisms themselves?  Perhaps I don't understand the 
>>>>>> issue you are
>>>>>> raising.  Would you please clarify what it is you're asking be 
>>>>>> done that an
>>>>>> administrator can't do on their own?
>>>>>>
>>>>>> Scott K
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> spfbis mailing list
>>>>>> spfbis@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/spfbis
>>>>>
>>>>> _______________________________________________
>>>>> spfbis mailing list
>>>>> spfbis@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/spfbis
>>>>
>>>> _______________________________________________
>>>> spfbis mailing list
>>>> spfbis@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/spfbis
>>
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms030806070306090703080208
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYyMDU3NTRaME8GCSqGSIb3DQEJBDFCBEDd6WYGgTPLC+AKcGfXmsYt
qR8bPzvvbskQ+oO51HbcXs2cJ8XtFyfxCQH9rpCZc7M3pYfNPC9Fg0Lxgs5UdJPfMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAJGFn5tt
h+40eqSaf5TKv0NW1HTykYZPKlWSsoZ94gkZVwxfptPp5JPa5Sr8kCSYpVmnG4MbDjEnnvw6
2U921bRiRaC47oIO765VppumCpwnzBqkTdLMesEB8sLzaErAVVqGs+VfHzoFCIRC3rdp0eEZ
nLvkBYHYLeVv3zEBSZDvAb0PUWxlOcl6gQqxAsieaR7AwxuyecHZh+Lz1Z5ve1P3ZjukA8Jd
+vmJDsbTUEHrOLp2YiOXJal2OmDDPJbKts/4JQvcKdolO+WBnCEXFBobud3U0MOMLduUgPMv
k7+cftLS0ESCjRwHQD048yORuz089RiAmCfBrZXaFWMCy9bC4n6mcBjI6mDNDmWDef+K2lM4
FkrxqNVZy4HBpBZFSYNv4G7JXMKfosj0Wgenfq1XOTC+Mgd5CgvmHrGe9rlPnYwwMa38GGeS
ji0lLtzHhWol5DHB+qXrQh5DF1IdkR8mtBgKZf9JPruM9NhIu4XPebSqqLcWsG1Y4o8tame+
ZKpE3DmoJg0cJbP+ME7CZNfzqdmr2pkgxKF102QkCSytfOc5HXdBFLjLOM+5b0bCfV3VoSXb
R1r6gS2+ccTrOPVDZNBbr4qwSv5gC0NimvX5zmZN66IHxJQ+j5F2XGsXQZg8XbcSCcGu6/6t
aWwhjTiTw6fXRoUF5uhlPsZFUifgAAAAAAAA
--------------ms030806070306090703080208--


From nobody Sun Feb  6 14:16:32 2022
Return-Path: <johnl@iecc.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 EECFA3A0E38 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 14:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level: 
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=iecc.com header.b=LRjxE2b3; dkim=pass (2048-bit key) header.d=taugh.com header.b=nbMP/WQZ
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 Kke4T0WTm65L for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 14:16:24 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 B8E743A0E37 for <spfbis@ietf.org>; Sun,  6 Feb 2022 14:16:23 -0800 (PST)
Received: (qmail 64693 invoked from network); 6 Feb 2022 22:16:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=fcb3.620048b4.k2202; bh=Sr/7PNRI+cEBFcQo7vGvI8ogjMQ8hs2lPX8FMwc5b/o=; b=LRjxE2b35o4qzaY4/RubbXZ6i2k9MhTMwggFNEmNMHfz3Ulk0964+WMcrG/4FgZ+nyell0aw9jEaL/5tJk+M9nMXPAX2Rn8mqxwsM57uKaEWuECYTKBXcwt6kdXJkUpYqQtCfaLSTnH+OlRuyA4lQNgxdP42/BqsqlAmGb+3fqFFkTpsPrbpzvVeetou9s7nkE0a2s15VICv5CyVeZxDWyLIfjtX4WW1SYuXsH9SODwnbFU1ru+lZiekSZHYTbo1JqatY53Hi54jpBs4/HEIG+RL6g3XAGGJU0skxjVXwzcwxzdjIpsoCubaTgj8ZSPEKDxlN8jidBwLF8U4hYiwNA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=fcb3.620048b4.k2202; bh=Sr/7PNRI+cEBFcQo7vGvI8ogjMQ8hs2lPX8FMwc5b/o=; b=nbMP/WQZKn0FPFEsWyVgnDv4Ep3/3e5dCbaAnxNW54B9oEA8FNJkPICXqhH0bj13aFRLUClnQhXtQR04VXXvdVXZZD8RC80bfKmfwL8g0ga8Q4AjPM6P1lQNsqX6QMc27ku4709zl8wYLYs6+xw3gMecVtLp0jQLMdhHcqJZHT8Danhf8JJsWru37ApOW9kmC53n52J8UC1ZbusLTKs+jjlewImMYhnquKRdnAQxG60Sowabh/i0wxI2ZT7ikirEVoLzZkc/jUD4bySHmpMPFvaFngegd2kcLb+0PxluUeBv2JMiX7dEXdxKok72X0dSVHW0TnR0v0MbVOIUfxQuhg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 06 Feb 2022 22:16:20 -0000
Received: by ary.qy (Postfix, from userid 501) id 53E4836687AF; Sun,  6 Feb 2022 17:16:18 -0500 (EST)
Date: 6 Feb 2022 17:16:18 -0500
Message-Id: <20220206221619.53E4836687AF@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: spfbis@ietf.org
Cc: spf2@kitterman.com
In-Reply-To: <45673006.FIhfuaby8d@localhost>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/zjZPv8IjqW2wwIq1CiwOJKbtcpg>
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: Sun, 06 Feb 2022 22:16:30 -0000

It appears that Scott Kitterman  <spf2@kitterman.com> said:
>It looks like situations like this one were contemplated by the RFC 6147 
>authors:
>
>> 6.  Deployment Notes
>> 
>>    While DNS64 is intended to be part of a strategy for aiding IPv6
>>    deployment in an internetworking environment with some IPv4-only and
>>    IPv6-only networks, it is important to realize that it is
>>    incompatible with some things that may be deployed in an IPv4-only or
>>    dual-stack context.
>
>On the SPF side of the discussion, I think it would, at least in theory, be 
>feasible to interpret an ip4: mechanism as <prefix> + <address> if the 
>connection is IPv6, but I don't see how a receiving SPF processor could know 
>what the prefix is.  As I read RFC 6147 Section 5.2, it could be anything.

See RFCs 7050 and 8880 for how you find the prefix(es).

That seems like a more reasonable way to go, patch the SPF library so it
can use the NAT's Pref64 to fudge the interpretation of ip4 and ptr.

It looks like you could automate the entire thing -- when the library starts
up, do an AAAA query on ipv4only.arpa, and if you get plausible answers,
you know you're behind NAT64 and reinterpret ip4 and ptr terms appropriately.

R's,
John



From nobody Sun Feb  6 14:47:30 2022
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 F36383A0E93 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 14:47:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, 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=Mb8rUsZV; dkim=pass (1024-bit key) header.d=yitter.info header.b=a59BGQ8j
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 3kgeGO3YIUCn for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 14:47:22 -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 215663A0E8C for <spfbis@ietf.org>; Sun,  6 Feb 2022 14:47:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 85D83BD5C8 for <spfbis@ietf.org>; Sun,  6 Feb 2022 22:47:19 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644187639; bh=RMr/6b4GKxU4nHermOQhQ7BNoZB76rqbev5xL7WZT1s=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Mb8rUsZV/5RCFR5TlnsJNS8FnJMt0S0LFLemxapNxgfw8WCJc6B72gIeqnyaHVyhC cvC7WxWGxX/rOZtc6yudMsmUIu4i7CY5caAElQNGBYWTkAJbvvYkS7r4vQ9jXrzoC3 Xc48uqhB1981/m5yunxuOOmtgSFO7/YXqAKC0Fb0=
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 Zw3V4KK-EO67 for <spfbis@ietf.org>; Sun,  6 Feb 2022 22:47:17 +0000 (UTC)
Date: Sun, 6 Feb 2022 17:47:15 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644187637; bh=RMr/6b4GKxU4nHermOQhQ7BNoZB76rqbev5xL7WZT1s=; h=Date:From:To:Subject:References:In-Reply-To:From; b=a59BGQ8jYN404nQFnJXv0W679e9d3+zwAKhSmEXJMvyGNPoejv/GGB/06bttGC6kY 9rfCiphDYuJ2eL4Lwx/U0TF2P94KsRH7+84ivHVTPZtDTV2qhZoXl15XwxoKyoL2qM E550Hf/Mr5CErMRsMSw7hNQ18YYFeOU9x0GFYdH0=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: spfbis@ietf.org
Message-ID: <20220206224715.kzynnbwkt5a26wii@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <45673006.FIhfuaby8d@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/bv7b44T3JjmHOtmo5HGEuM9WzX0>
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: Sun, 06 Feb 2022 22:47:28 -0000

Hi,

I'm one of the primary offenders behind DNS64.  I work for the Internet Society but I am not speaking for them (or anyone eles) right now.

On Sun, Feb 06, 2022 at 02:57:08PM -0500, Scott Kitterman wrote:

>I think your original suggestion that an SPF record be modified by the DNS64
>server to add ip6: mechanisms with <prefix> + <address> is a reasonable path
>forward, but I think it's really an RFC 6147 discussion, not so much RFC 7208.

The problem with this is that it's importing the DNS64 intimate knowledge of this protocol for TXT records, which means in effect that DNS64 needs to start parsing arbitrary data in TXT records.  (There is a reason DNS weenies always got upset about ignoring the strong typing in DNS, and this is an example of it.)

DNS64, to be honest, was always sort of a hack that was intended to make transition to v6 easier.  It really basically depended on the strong data typing of A, AAAA, and PTR records in order to give it clear places to insert itself.  "Look at every TXT record," doesn't really support that plan.  I never thought we were designing it for long life or high degrees of robustness, and I think it is likely to be extremely difficult to operate a modern mail server on v6-only infrastructure and be able to talk to v4-only mail servers.  In any case, I guess it would be _possible_ to teach a DNS64 server to parse and edit TXT records on the fly, but the idea that this is going to be limited to SPF is, I suspect, a false hope.  For that reason, my reaction is that it wouldn't be a great idea to do.  I nevertheless sympathize with the desire, even though I am made nervous about the implications.

>It is not, however, without risks.  RFC 7208 Section 3.4 gives advice on SPF
>record size.  Your proposed approach would increase the record size, which, in
>theory, could be problematic.  It might be that anything running on an IPv6
>only network is modern enough that this isn't actually a problem.  I don't
>know.

I'd be especially worried about RRset size, because a lot of stuff in contemporary operations is jammed into TXT records (all those application keys, for instance).  I can imagine cases where the change could move the response size across the response size boundary, forcing truncation and TCP fallback.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Sun Feb  6 15:35:09 2022
Return-Path: <klaus.frank@posteo.de>
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 44F263A0FBE for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 15:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.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, 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 (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 YikueNMD1tHY for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 15:34:58 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 022173A0FBB for <spfbis@ietf.org>; Sun,  6 Feb 2022 15:34:57 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id E62C7240105 for <spfbis@ietf.org>; Mon,  7 Feb 2022 00:34:52 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644190492; bh=wfy0hmdh2dPHjCmWlg+BEMTe7p+3fU+p1JMt6kPYr84=; h=Date:Subject:To:From:From; b=RmQreKRXLw3UNG6bycKtoy6ccTAK5GJokPgG+XMBWCjw+O8Bms+jLJCL88GAwzWDG d2szDRn0b7zse/CZZ9V5kigd1bC3HnCna3a9AxdC96N2R/KqMjuOWt6WLNMkS4RAUB 1xr229hRJEqgwdHSYacGhpmt+k6t7nEy3cKDs59MyjVsqLmaNuOy6dD9wnQ8ZwTpij Fp41kPZ8IOCtuBlLqTvlslsvjl+vCEH3PJVHNrFe7bsJYvnk04dsV3tCtd5l8Ufq5E ElTueGvPPA1ztMcyJBzLM9llQ202Qyb9COM5T4NzjIJJ48Oj6350ljrCJVscORfMpO QwlUraeTULHDw==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsQbv66ZVz6tnm for <spfbis@ietf.org>; Mon,  7 Feb 2022 00:34:51 +0100 (CET)
Message-ID: <9843fdc5-4443-e327-751b-330453ad7bf2@posteo.de>
Date: Sun,  6 Feb 2022 23:34:49 +0000
MIME-Version: 1.0
Content-Language: en-US
To: spfbis@ietf.org
References: <20220206221619.53E4836687AF@ary.qy>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <20220206221619.53E4836687AF@ary.qy>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms080500090904070005030002"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/3fGXXBW9FdeU9f_8kz-fdCoto-o>
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: Sun, 06 Feb 2022 23:35:05 -0000

This is a cryptographically signed message in MIME format.

--------------ms080500090904070005030002
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Either way one of both RFCs needs an addendum to address this.

I personally think that because the SPF record is part of DNS it should 
be updated by DNS64 as well. But if RFC7208 gets an addendum that 
mandates the SPF library to consider the NAT64 (RFC7050 and RFC8880) 
prefix when doing validation would also work for me.

On 2022-02-06 23:16, John Levine wrote:
> It appears that Scott Kitterman  <spf2@kitterman.com> said:
>> It looks like situations like this one were contemplated by the RFC 6147
>> authors:
>>
>>> 6.  Deployment Notes
>>>
>>>     While DNS64 is intended to be part of a strategy for aiding IPv6
>>>     deployment in an internetworking environment with some IPv4-only and
>>>     IPv6-only networks, it is important to realize that it is
>>>     incompatible with some things that may be deployed in an IPv4-only or
>>>     dual-stack context.
>> On the SPF side of the discussion, I think it would, at least in theory, be
>> feasible to interpret an ip4: mechanism as <prefix> + <address> if the
>> connection is IPv6, but I don't see how a receiving SPF processor could know
>> what the prefix is.  As I read RFC 6147 Section 5.2, it could be anything.
> See RFCs 7050 and 8880 for how you find the prefix(es).
>
> That seems like a more reasonable way to go, patch the SPF library so it
> can use the NAT's Pref64 to fudge the interpretation of ip4 and ptr.
>
> It looks like you could automate the entire thing -- when the library starts
> up, do an AAAA query on ipv4only.arpa, and if you get plausible answers,
> you know you're behind NAT64 and reinterpret ip4 and ptr terms appropriately.
>
> R's,
> John
>
>
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms080500090904070005030002
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDYyMzM0NDlaME8GCSqGSIb3DQEJBDFCBECC7/1WYoygry4I1PtCFdrI
HgooJLgqv+pj40VKiZcVDA7GJU26fgW5gmBpqMI3BK9SyI9oJTbsYxL2h/6BmIcDMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICADQ9p/7n
4KDye6VcxwnP7JJlE2XPWzeytN83npguzG5GJQJNDKybEu9YlS3+dK1gxVBERsW9Nm6QMFUy
qnWP5x0zdrcC6LPf0P3Hhm52811Te7niU4nJyH6iS0er0TeVSI1SFyQCMhyJSezEJ6q5EPPf
trVS5YG9RjzR4cV82XGnJTqTIWm/FAB0WAJ1XaRPpHlOZbMDHncTbzC4IrOvRkMwaAzrJyaZ
sGFASZM2OBH68djkHw176AXU0MYd31KJQ2EoDTchmHubXK/Yo4C0SGRnWtUKHSBHXVgogPXn
j+TM/jw2a2dvC6vIm4Kc3BkElyJrEDBY0OoRhe3IHDJCCOuGw78N2eKZ4PlKIKPnI4gaAtcm
QbZYljs8tgHOWPKYA993wEgxL7mxmRDw/fnLZ+Ze0eGal9lwFFuLT1xRU9P6xtn2tRWftegC
HrcxWSuojVP5Pe12bwKc55pqfH6Rm8dm2iSQUjErwE7VibfhO7vfwE1hOGqEUjAJRdf17QYT
y6OS4eqaFY/YZ0+6G5nXrVLx2ZlENeSbEQZhSzOsv723w4hknZq0qCjeRlg2KeUL9aze7f9P
mU4ln3aFSlhLy8ZTRaFRcZzryFH0dHgNSXtKNvKTjF4K/SeMGHsC5Qviz56LD9vItVsMfFsd
ezNwvBUJF7HMxDMJNkTMSSPTFqMyAAAAAAAA
--------------ms080500090904070005030002--


From nobody Sun Feb  6 16:09:30 2022
Return-Path: <klaus.frank@posteo.de>
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 CFB603A102B for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 16:09:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 WIMnTA6gUfDz for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 16:09:17 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 334103A1029 for <spfbis@ietf.org>; Sun,  6 Feb 2022 16:09:17 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id 46507240101 for <spfbis@ietf.org>; Mon,  7 Feb 2022 01:09:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644192554; bh=TkpTPjWjKy1mlTr4wHn5wV0xAluKzBXb322V9ZivDVY=; h=Date:Subject:To:From:From; b=p9D4pTprMkx0TXeefFfKWxdm6Vl+8Wdthjd4uIKnhOAhwHUFDe5xY7B+JPYa0v2il F5JwjSVd1r7CUdzcLifUKC9pSL+vWmqsQNARdwn2ElqMvVI1LrZq5pipc3XJWBq6IV AvRJz1CJxRUqvt/k2+R6u21VbRSJ6rJpzEYli/WdQo98k2kLiqXz2LiiDEV9iBEimK PX3UNpiYDHixOgzL9ITcwYGnKZlgIplWQIHLH5efu5E425BGPP68BndxmzHJii1Gd+ 6WQCrUXGcmbjavpwVc+9Z8Kvw3tQQoytmuxyXns09nWJaaMmk4vlome3kY1IKXJgs9 VlmAKh4R4wMPQ==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsRMY2vSXz6tpL for <spfbis@ietf.org>; Mon,  7 Feb 2022 01:09:13 +0100 (CET)
Message-ID: <b8e38c6a-aee9-8f86-350c-636c2f9d5efc@posteo.de>
Date: Mon,  7 Feb 2022 00:09:11 +0000
MIME-Version: 1.0
Content-Language: en-US
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>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <20220206224715.kzynnbwkt5a26wii@crankycanuck.ca>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms060403050104050805000808"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/oPBs9qOLX_VwopB2R9kKiavmVGk>
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 00:09:24 -0000

This is a cryptographically signed message in MIME format.

--------------ms060403050104050805000808
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 2022-02-06 23:47, Andrew Sullivan wrote:
> It really basically depended on the strong data typing of A, AAAA, and 
> PTR records in order to give it clear places to insert itself.  "Look 
> at every TXT record," doesn't really support that plan. 

But it wouldn't be "every TXT record". If it doesn't start with "v=spf1" 
it can be passed as is and does not require parsing. And even then it's 
also a defined structure and not "arbitrary".

On 2022-02-06 23:47, Andrew Sullivan wrote:
> I never thought we were designing it for long life or high degrees of 
> robustness, and I think it is likely to be extremely difficult to 
> operate a modern mail server on v6-only infrastructure and be able to 
> talk to v4-only mail servers.

Actually the only limitation for that is the SPF record not being 
updated by DNS64... And for outgoing it's not an issue at all. A 
stateless NAT64 mapping is enough...

A combination of stateless and statefull NAT64 is enough to cover all 
the ugly IPv4 stuff. Also because IPv4 was already highly NAT44ed 
anyway. There is no difference between a mail server behind a NAT44 and 
one behind a NAT64 as long as the correct public facing IP is used in 
the configuration of one owns SPF record...

But tbh, in some situations it would be very helpful if I could just 
swap the calls for generating IPv4 packets by one that generates IPv6 
packets instead. I thought about writing something that works via 
LD_PRELOAD similarly to torsocks or IP2Unix, but it went way over my 
head to make it anything close to performant and reliable...

On 2022-02-06 23:47, Andrew Sullivan wrote:
> but the idea that this is going to be limited to SPF is, I suspect, a 
> false hope.  For that reason, my reaction is that it wouldn't be a 
> great idea to do.
What do you have in mind? What else would be there? From my point of few 
the only thing missing for a complete DNS64 rewrite is the SPF record. 
As nothing else contains IP addresses but only dns names. I've looked at 
the other record types. Did I miss something?

--------------ms060403050104050805000808
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDcwMDA5MTFaME8GCSqGSIb3DQEJBDFCBEBccy4eqt06OaIktf/34pAt
zjbJYSv1UnhPKOeBjxwCmM1S0fZD/z6tR/3hY9PQLzTcWq0R6FErtun+xTaT2lLzMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAIhNplF/
PA7xNpHKqidtbme7yr5dWiRDB8/pieQ+rTXvFeYEGKP+sflha7P2aDWsdtr5+/64zEzwn8d6
HVLIQUYn/WNJVkX4KwXljEUoB157Z3FKdaVFgCuR9hHav3u0qLlO5UPcG/uM0gPBIiWhEmYW
MfORlGTayPjy7H+lhoPHObFAN3k/Zf1l6IWJZIJTW2cw75UICi4QMdRDcrxgero0VbX1XHjl
ZPMPlNXJ6sOi1ojURk/mwE21dOXb0n2lwmBp229oaZWFjcgO+oH1xOpmMiD/WC8VzOe9pos0
1uDMPpk4bekcW3WEZ488ebTlMJ0NuHkB7FxMjGiDlSBxY6o1iOacMM1KgK/7M4FFLHjcsLc2
C0n+pS4njYeQZBVq2wvL3I2LU74HU9tLkqhB7FHg6LD5qmav1S70kpwGY/xtuUHGFTAttx5o
n9cybuWKiDh8UiH10jNxkDJVcJAY/LIiMFiJQw8lvlnHyXfuiRemuLEpHlgHk+dySCuJkDhD
Bk2R4WLXBNWXUv9GX1ipIHG9BQnPUJdi/CJO75aZdvyjxKC/8DFk+vnnrV9GtVyyF83QZR2d
uJD00tHdFJlMR2ql+p0XTympMXTH3NtQOf+qfwK370spke3IlWxFgcaH6vHGrS0ZORgrfvF1
pM4IG+HLBWd7pL7ND6Xet5/2R3WhAAAAAAAA
--------------ms060403050104050805000808--


From nobody Sun Feb  6 16:42:20 2022
Return-Path: <william@leibzon.org>
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 5FA7E3A107C for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 16:42:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 8h__nohijOfG for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 16:42:09 -0800 (PST)
Received: from relay4.hostedemail.com (relay4.hostedemail.com [64.99.140.36]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F7AB3A107D for <spfbis@ietf.org>; Sun,  6 Feb 2022 16:42:09 -0800 (PST)
Received: from omf14.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 52DC8219FD for <spfbis@ietf.org>; Mon,  7 Feb 2022 00:42:08 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: william@leibzon.org) by omf14.hostedemail.com (Postfix) with ESMTPA id A52292D for <spfbis@ietf.org>; Mon,  7 Feb 2022 00:41:53 +0000 (UTC)
MIME-Version: 1.0
Date: Sun, 06 Feb 2022 16:42:07 -0800
From: william@leibzon.org
To: spfbis@ietf.org
In-Reply-To: <20220206224715.kzynnbwkt5a26wii@crankycanuck.ca>
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>
Message-ID: <7ddee9f68efbef4bcf2dbfef69b0766a@leibzon.org>
X-Sender: william@leibzon.org
Content-Type: multipart/alternative; boundary="=_c9d161a7968064d7d4f327b4deb1f8b3"
X-Stat-Signature: 5etnwqtciamcrp58n7kj49texnpo1cnj
X-Rspamd-Server: rspamout01
X-Rspamd-Queue-Id: A52292D
X-Session-Marker: 77696C6C69616D406C6569627A6F6E2E6F7267
X-Session-ID: U2FsdGVkX1/yLZVVNDpXjQL2OBvSZ2dj2XfgzPQUjvo=
X-HE-Tag: 1644194513-346566
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/VlKO7eWoQtzJdvtqOuVquEXAc98>
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 00:42:16 -0000

--=_c9d161a7968064d7d4f327b4deb1f8b3
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII;
 format=flowed



Yeah, I wasn't thrilled with the idea of SPF using TXT record way back 
when. It opened it for quite a few others who followed. Putting ip 
addresses there though is not something that is done for any other 
protocol or software I can immediately think of.

I'm curious, how does DNS64 inter-operates with DNSSEC? Would that not 
break it and make DNSSEC folks very uncomfortable about what others 
could decide to do?

I think it could be helpful to collect various protocol operational and 
similar issues for those running mail servers (and other servers) behind 
NAT64 and write informational RFC which would be soft of experimental 
best practice. I'd expect that some server software would have to add 
special features to be used in this setup.

On 2022-02-06 14:47, Andrew Sullivan wrote:

> Hi,
> 
> I'm one of the primary offenders behind DNS64.  I work for the Internet 
> Society but I am not speaking for them (or anyone eles) right now.
> 
> On Sun, Feb 06, 2022 at 02:57:08PM -0500, Scott Kitterman wrote:
> 
>> I think your original suggestion that an SPF record be modified by the 
>> DNS64
>> server to add ip6: mechanisms with <prefix> + <address> is a 
>> reasonable path
>> forward, but I think it's really an RFC 6147 discussion, not so much 
>> RFC 7208.
> 
> The problem with this is that it's importing the DNS64 intimate 
> knowledge of this protocol for TXT records, which means in effect that 
> DNS64 needs to start parsing arbitrary data in TXT records.  (There is 
> a reason DNS weenies always got upset about ignoring the strong typing 
> in DNS, and this is an example of it.)
> 
> DNS64, to be honest, was always sort of a hack that was intended to 
> make transition to v6 easier.  It really basically depended on the 
> strong data typing of A, AAAA, and PTR records in order to give it 
> clear places to insert itself.  "Look at every TXT record," doesn't 
> really support that plan.  I never thought we were designing it for 
> long life or high degrees of robustness, and I think it is likely to be 
> extremely difficult to operate a modern mail server on v6-only 
> infrastructure and be able to talk to v4-only mail servers.  In any 
> case, I guess it would be _possible_ to teach a DNS64 server to parse 
> and edit TXT records on the fly, but the idea that this is going to be 
> limited to SPF is, I suspect, a false hope.  For that reason, my 
> reaction is that it wouldn't be a great idea to do.  I nevertheless 
> sympathize with the desire, even though I am made nervous about the 
> implications.
> 
>> It is not, however, without risks.  RFC 7208 Section 3.4 gives advice 
>> on SPF
>> record size.  Your proposed approach would increase the record size, 
>> which, in
>> theory, could be problematic.  It might be that anything running on an 
>> IPv6
>> only network is modern enough that this isn't actually a problem.  I 
>> don't
>> know.
> 
> I'd be especially worried about RRset size, because a lot of stuff in 
> contemporary operations is jammed into TXT records (all those 
> application keys, for instance).  I can imagine cases where the change 
> could move the response size across the response size boundary, forcing 
> truncation and TCP fallback.
> 
> Best regards,
> 
> A
--=_c9d161a7968064d7d4f327b4deb1f8b3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p><br />Yeah, I wasn't thrilled with the idea of SPF using TXT record way =
back when. It opened it for quite a few others who followed. Putting ip add=
resses there though is not something that is done for any other protocol or=
 software I can immediately think of.</p>
<div id=3D"signature"></div>
<p>I'm curious, how does DNS64 inter-operates with DNSSEC? Would that not b=
reak it and make DNSSEC folks very <span>uncomfortable about what others co=
uld decide to do?<br /><br /></span>I think it could be helpful to collect =
various protocol operational and similar issues for those running mail serv=
ers (and other servers) behind NAT64 and write informational RFC which woul=
d be soft of experimental best practice. I'd expect that some server softwa=
re would have to add special features to be used in this setup.</p>
<p id=3D"reply-intro">On 2022-02-06 14:47, Andrew Sullivan wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
<span style=3D"white-space: nowrap;">Hi,</span><br /><br /><span style=3D"w=
hite-space: nowrap;">I'm&nbsp;one&nbsp;of&nbsp;the&nbsp;primary&nbsp;offend=
ers&nbsp;behind&nbsp;DNS64.&nbsp;&nbsp;I&nbsp;work&nbsp;for&nbsp;the&nbsp;I=
nternet&nbsp;Society&nbsp;but&nbsp;I&nbsp;am&nbsp;not&nbsp;speaking&nbsp;fo=
r&nbsp;them&nbsp;(or&nbsp;anyone&nbsp;eles)&nbsp;right&nbsp;now.</span><br =
/><br /><span style=3D"white-space: nowrap;">On&nbsp;Sun,&nbsp;Feb&nbsp;06,=
&nbsp;2022&nbsp;at&nbsp;02:57:08PM&nbsp;-0500,&nbsp;Scott&nbsp;Kitterman&nb=
sp;wrote:</span><br /><br />
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">I&nbsp;think&nbsp=
;your&nbsp;original&nbsp;suggestion&nbsp;that&nbsp;an&nbsp;SPF&nbsp;record&=
nbsp;be&nbsp;modified&nbsp;by&nbsp;the&nbsp;DNS64</span><br /><span style=
=3D"white-space: nowrap;">server&nbsp;to&nbsp;add&nbsp;ip6:&nbsp;mechanisms=
&nbsp;with&nbsp;&lt;prefix&gt;&nbsp;+&nbsp;&lt;address&gt;&nbsp;is&nbsp;a&n=
bsp;reasonable&nbsp;path</span><br /><span style=3D"white-space: nowrap;">f=
orward,&nbsp;but&nbsp;I&nbsp;think&nbsp;it's&nbsp;really&nbsp;an&nbsp;RFC&n=
bsp;6147&nbsp;discussion,&nbsp;not&nbsp;so&nbsp;much&nbsp;RFC&nbsp;7208.</s=
pan></blockquote>
<br /><span style=3D"white-space: nowrap;">The&nbsp;problem&nbsp;with&nbsp;=
this&nbsp;is&nbsp;that&nbsp;it's&nbsp;importing&nbsp;the&nbsp;DNS64&nbsp;in=
timate&nbsp;knowledge&nbsp;of&nbsp;this&nbsp;protocol&nbsp;for&nbsp;TXT&nbs=
p;records,&nbsp;which&nbsp;means&nbsp;in&nbsp;effect&nbsp;that&nbsp;DNS64&n=
bsp;needs&nbsp;to&nbsp;start&nbsp;parsing&nbsp;arbitrary&nbsp;data&nbsp;in&=
nbsp;TXT&nbsp;records.&nbsp;&nbsp;(There&nbsp;is&nbsp;a&nbsp;reason&nbsp;DN=
S&nbsp;weenies&nbsp;always&nbsp;got&nbsp;upset&nbsp;about&nbsp;ignoring&nbs=
p;the&nbsp;strong&nbsp;typing&nbsp;in&nbsp;DNS,&nbsp;and&nbsp;this&nbsp;is&=
nbsp;an&nbsp;example&nbsp;of&nbsp;it.)</span><br /><br /><span style=3D"whi=
te-space: nowrap;">DNS64,&nbsp;to&nbsp;be&nbsp;honest,&nbsp;was&nbsp;always=
&nbsp;sort&nbsp;of&nbsp;a&nbsp;hack&nbsp;that&nbsp;was&nbsp;intended&nbsp;t=
o&nbsp;make&nbsp;transition&nbsp;to&nbsp;v6&nbsp;easier.&nbsp;&nbsp;It&nbsp=
;really&nbsp;basically&nbsp;depended&nbsp;on&nbsp;the&nbsp;strong&nbsp;data=
&nbsp;typing&nbsp;of&nbsp;A,&nbsp;AAAA,&nbsp;and&nbsp;PTR&nbsp;records&nbsp=
;in&nbsp;order&nbsp;to&nbsp;give&nbsp;it&nbsp;clear&nbsp;places&nbsp;to&nbs=
p;insert&nbsp;itself.&nbsp;&nbsp;"Look&nbsp;at&nbsp;every&nbsp;TXT&nbsp;rec=
ord,"&nbsp;doesn't&nbsp;really&nbsp;support&nbsp;that&nbsp;plan.&nbsp;&nbsp=
;I&nbsp;never&nbsp;thought&nbsp;we&nbsp;were&nbsp;designing&nbsp;it&nbsp;fo=
r&nbsp;long&nbsp;life&nbsp;or&nbsp;high&nbsp;degrees&nbsp;of&nbsp;robustnes=
s,&nbsp;and&nbsp;I&nbsp;think&nbsp;it&nbsp;is&nbsp;likely&nbsp;to&nbsp;be&n=
bsp;extremely&nbsp;difficult&nbsp;to&nbsp;operate&nbsp;a&nbsp;modern&nbsp;m=
ail&nbsp;server&nbsp;on&nbsp;v6-only&nbsp;infrastructure&nbsp;and&nbsp;be&n=
bsp;able&nbsp;to&nbsp;talk&nbsp;to&nbsp;v4-only&nbsp;mail&nbsp;servers.&nbs=
p;&nbsp;In&nbsp;any&nbsp;case,&nbsp;I&nbsp;guess&nbsp;it&nbsp;would&nbsp;be=
&nbsp;_possible_&nbsp;to&nbsp;teach&nbsp;a&nbsp;DNS64&nbsp;server&nbsp;to&n=
bsp;parse&nbsp;and&nbsp;edit&nbsp;TXT&nbsp;records&nbsp;on&nbsp;the&nbsp;fl=
y,&nbsp;but&nbsp;the&nbsp;idea&nbsp;that&nbsp;this&nbsp;is&nbsp;going&nbsp;=
to&nbsp;be&nbsp;limited&nbsp;to&nbsp;SPF&nbsp;is,&nbsp;I&nbsp;suspect,&nbsp=
;a&nbsp;false&nbsp;hope.&nbsp;&nbsp;For&nbsp;that&nbsp;reason,&nbsp;my&nbsp=
;reaction&nbsp;is&nbsp;that&nbsp;it&nbsp;wouldn't&nbsp;be&nbsp;a&nbsp;great=
&nbsp;idea&nbsp;to&nbsp;do.&nbsp;&nbsp;I&nbsp;nevertheless&nbsp;sympathize&=
nbsp;with&nbsp;the&nbsp;desire,&nbsp;even&nbsp;though&nbsp;I&nbsp;am&nbsp;m=
ade&nbsp;nervous&nbsp;about&nbsp;the&nbsp;implications.</span><br /><br />
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">It&nbsp;is&nbsp;n=
ot,&nbsp;however,&nbsp;without&nbsp;risks.&nbsp;&nbsp;RFC&nbsp;7208&nbsp;Se=
ction&nbsp;3.4&nbsp;gives&nbsp;advice&nbsp;on&nbsp;SPF</span><br /><span st=
yle=3D"white-space: nowrap;">record&nbsp;size.&nbsp;&nbsp;Your&nbsp;propose=
d&nbsp;approach&nbsp;would&nbsp;increase&nbsp;the&nbsp;record&nbsp;size,&nb=
sp;which,&nbsp;in</span><br /><span style=3D"white-space: nowrap;">theory,&=
nbsp;could&nbsp;be&nbsp;problematic.&nbsp;&nbsp;It&nbsp;might&nbsp;be&nbsp;=
that&nbsp;anything&nbsp;running&nbsp;on&nbsp;an&nbsp;IPv6</span><br /><span=
 style=3D"white-space: nowrap;">only&nbsp;network&nbsp;is&nbsp;modern&nbsp;=
enough&nbsp;that&nbsp;this&nbsp;isn't&nbsp;actually&nbsp;a&nbsp;problem.&nb=
sp;&nbsp;I&nbsp;don't</span><br /><span style=3D"white-space: nowrap;">know=
=2E</span></blockquote>
<br /><span style=3D"white-space: nowrap;">I'd&nbsp;be&nbsp;especially&nbsp=
;worried&nbsp;about&nbsp;RRset&nbsp;size,&nbsp;because&nbsp;a&nbsp;lot&nbsp=
;of&nbsp;stuff&nbsp;in&nbsp;contemporary&nbsp;operations&nbsp;is&nbsp;jamme=
d&nbsp;into&nbsp;TXT&nbsp;records&nbsp;(all&nbsp;those&nbsp;application&nbs=
p;keys,&nbsp;for&nbsp;instance).&nbsp;&nbsp;I&nbsp;can&nbsp;imagine&nbsp;ca=
ses&nbsp;where&nbsp;the&nbsp;change&nbsp;could&nbsp;move&nbsp;the&nbsp;resp=
onse&nbsp;size&nbsp;across&nbsp;the&nbsp;response&nbsp;size&nbsp;boundary,&=
nbsp;forcing&nbsp;truncation&nbsp;and&nbsp;TCP&nbsp;fallback.</span><br /><=
br /><span style=3D"white-space: nowrap;">Best&nbsp;regards,</span><br /><b=
r />A</div>
</blockquote>
</body></html>

--=_c9d161a7968064d7d4f327b4deb1f8b3--


From nobody Sun Feb  6 17:08:04 2022
Return-Path: <klaus.frank@posteo.de>
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 B00AE3A10D0 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 17:08:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 1Z5trFgVuE6U for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 17:07:57 -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 C4C363A10CE for <spfbis@ietf.org>; Sun,  6 Feb 2022 17:07:55 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout01.posteo.de (Postfix) with ESMTPS id C4DF1240026 for <spfbis@ietf.org>; Mon,  7 Feb 2022 02:07:53 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644196073; bh=nfUabnfHe2Ws2qH+7S93y+Df/tuBwelwogJCZy2+Ros=; h=Date:Subject:To:From:From; b=JnLnTpKGcsQM5Z1Sk9lTV/EH/DgBeCKcLH+cm4BGNKkF2OCF5FwWrgkvlIJmv2O/D xWNDofHb7uu9WoXcTXPqJKozyWQM6OWDeFY9EdlN848vZfkbdppWZkgQCtOc4ek77y pjawVXSoGmwZ/Uo6ni3G7QSSHVsj+k9dsGWGiqVUyrWBB3ctx6wleqvxOQ+1vbcads tGgjrnTM/tNiGIUCsnHfoHjARNdGzwN8dF+8JCnRsLg6n0aIPFQetjD2Mnm6TIUwIj DkTQPAtO6AAB9yfrIkpKQSL0lvPGZSrnCTHdwvAHHI2cMBk3lhnYjMya2WqCGT4ud4 4Z/81h2uawXpQ==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsSgF2Ps6z9rxF for <spfbis@ietf.org>; Mon,  7 Feb 2022 02:07:53 +0100 (CET)
Message-ID: <f2fccd74-355e-12b4-6b8a-539f61561a12@posteo.de>
Date: Mon,  7 Feb 2022 01:07:51 +0000
MIME-Version: 1.0
Content-Language: en-US
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>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <7ddee9f68efbef4bcf2dbfef69b0766a@leibzon.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms060600050103090301040507"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/C1boga9kdg2vqMPy82pOVdVVvXw>
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 01:08:03 -0000

This is a cryptographically signed message in MIME format.

--------------ms060600050103090301040507
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64

DQpPbiAyMDIyLTAyLTA3IDAxOjQyLCB3aWxsaWFtQGxlaWJ6b24ub3JnIHdyb3RlOg0KPg0K
PiBZZWFoLCBJIHdhc24ndCB0aHJpbGxlZCB3aXRoIHRoZSBpZGVhIG9mIFNQRiB1c2luZyBU
WFQgcmVjb3JkIHdheSBiYWNrIA0KPiB3aGVuLiBJdCBvcGVuZWQgaXQgZm9yIHF1aXRlIGEg
ZmV3IG90aGVycyB3aG8gZm9sbG93ZWQuIFB1dHRpbmcgaXAgDQo+IGFkZHJlc3NlcyB0aGVy
ZSB0aG91Z2ggaXMgbm90IHNvbWV0aGluZyB0aGF0IGlzIGRvbmUgZm9yIGFueSBvdGhlciAN
Cj4gcHJvdG9jb2wgb3Igc29mdHdhcmUgSSBjYW4gaW1tZWRpYXRlbHkgdGhpbmsgb2YuDQo+
DQo+IEknbSBjdXJpb3VzLCBob3cgZG9lcyBETlM2NCBpbnRlci1vcGVyYXRlcyB3aXRoIERO
U1NFQz8gV291bGQgdGhhdCBub3QgDQo+IGJyZWFrIGl0IGFuZCBtYWtlIEROU1NFQyBmb2xr
cyB2ZXJ5IHVuY29tZm9ydGFibGUgYWJvdXQgd2hhdCBvdGhlcnMgDQo+IGNvdWxkIGRlY2lk
ZSB0byBkbz8NCj4NCkJhc2ljYWxseSBieSBvZmZsb2FkaW5nIGl0IHRvd2FyZHMgdGhlIERO
UzY0IHNlcnZlci4NCg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9y
ZmM2MTQ3I3NlY3Rpb24tNi4yDQoNCjYuMi7CoCBETlNTRUMgVmFsaWRhdG9ycyBhbmQgRE5T
NjQNCg0KIMKgwqAgQW4gZXhpc3RpbmcgRE5TU0VDIHZhbGlkYXRvciAoaS5lLiwgb25lIHRo
YXQgaXMgdW5hd2FyZSBvZiBETlM2NCkNCiDCoMKgIG1pZ2h0IHJlamVjdCBhbGwgdGhlIGRh
dGEgdGhhdCBjb21lcyBmcm9tIEROUzY0IGFzIGhhdmluZyBiZWVuDQogwqDCoCB0YW1wZXJl
ZCB3aXRoIChldmVuIGlmIGl0IGRpZCBub3Qgc2V0IENEIHdoZW4gcXVlcnlpbmcpLiAqSWYg
aXQgaXMqKg0KKirCoMKgIG5lY2Vzc2FyeSB0byBoYXZlIHZhbGlkYXRpb24gYmVoaW5kIHRo
ZSBETlM2NCwgdGhlbiB0aGUgdmFsaWRhdG9yKioNCioqwqDCoCBtdXN0IGtub3cgaG93IHRv
IHBlcmZvcm0gdGhlIEROUzY0IGZ1bmN0aW9uIGl0c2VsZiouIEFsdGVybmF0aXZlbHksDQog
wqDCoCB0aGUgdmFsaWRhdGluZyBob3N0IG1heSBlc3RhYmxpc2ggYSB0cnVzdGVkIGNvbm5l
Y3Rpb24gd2l0aCBhIEROUzY0LA0KIMKgwqAgYW5kIGFsbG93IHRoZSBETlM2NCByZWN1cnNp
dmUgcmVzb2x2ZXIgdG8gZG8gYWxsIHZhbGlkYXRpb24gb24gaXRzDQogwqDCoCBiZWhhbGYu
DQoNCj4gSSB0aGluayBpdCBjb3VsZCBiZSBoZWxwZnVsIHRvIGNvbGxlY3QgdmFyaW91cyBw
cm90b2NvbCBvcGVyYXRpb25hbCANCj4gYW5kIHNpbWlsYXIgaXNzdWVzIGZvciB0aG9zZSBy
dW5uaW5nIG1haWwgc2VydmVycyAoYW5kIG90aGVyIHNlcnZlcnMpIA0KPiBiZWhpbmQgTkFU
NjQgYW5kIHdyaXRlIGluZm9ybWF0aW9uYWwgUkZDIHdoaWNoIHdvdWxkIGJlIHNvZnQgb2Yg
DQo+IGV4cGVyaW1lbnRhbCBiZXN0IHByYWN0aWNlLiBJJ2QgZXhwZWN0IHRoYXQgc29tZSBz
ZXJ2ZXIgc29mdHdhcmUgd291bGQgDQo+IGhhdmUgdG8gYWRkIHNwZWNpYWwgZmVhdHVyZXMg
dG8gYmUgdXNlZCBpbiB0aGlzIHNldHVwLg0KPg0KInNwZWNpYWwgZmVhdHVyZXMiIGlzIGV4
YWN0bHkgd2hhdCBJIHdhbnRlZCB0byBhdm9pZC4gQWxzbyBJIGRvbid0IGtub3cgDQppZiBp
dCdzIHN0cmljdGx5IG5lY2Vzc2FyeSB0byBoYXZlIGEgZGVkaWNhdGVkIFJGQyBmb3IgaG93
IHRvIGRvIHRoZSANCm1pZ3JhdGlvbi4gQmVzaWRlcyB0aGlzIGlzc3VlIHdpdGggdGhlIFNQ
RiByZWNvcmQgaXQncyBiYXNpY2FsbHkgdGhlIA0Kc2FtZSBhcyBmb3IgYW55IG90aGVyIHNl
cnZlciBhcHBsaWNhdGlvbi4gVXNlIHN0YXRlbGVzcyBOQVQ2NCAoYWthLiANCklQdjRhYVMp
IHRvIGhhdmUgYSBkZWRpY2F0ZWQgcHVibGljIElQdjQuIFB1dCB0aGF0IElQdjQgKHByZWZp
eCkgaW50byANCnRoZSBTUEYgcmVjb3JkIGFzIHVzdWFsLiBBbmQgZm9yIG5vdyBkaXNhYmxl
IHRoZSBTUEYgdmFsaWRhdGlvbiBmb3IgDQppbmJvdW5kIG1haWxzLiBUaGUgb25seSByZWFs
bHkgbm90ZXdvcnRoeSB0aGluZyBpcyB3aXRoIGZpbHRlcmluZyBzdHVmZiANCmxpa2UgU0lF
VkUgdGhhdCB0aGVzZSBuZWVkIHRvIGJlIHVwZGF0ZWQgdG8gaW5jbHVkZSB0aGVpciBtYXBw
ZWQgSVB2NiANCmFkZHJlc3NlcyBvciBzaW1pbGFyLiBFdmVyeXRoaW5nIGVsc2UganVzdCB3
b3JrcyBiZWNhdXNlIG9mIE5BVDY0IGFuZCANCkROUzY0Li4uDQoNCj4gT24gMjAyMi0wMi0w
NiAxNDo0NywgQW5kcmV3IFN1bGxpdmFuIHdyb3RlOg0KPg0KPj4gSGksDQo+Pg0KPj4gSSdt
wqBvbmXCoG9mwqB0aGXCoHByaW1hcnnCoG9mZmVuZGVyc8KgYmVoaW5kwqBETlM2NC7CoMKg
ScKgd29ya8KgZm9ywqB0aGXCoEludGVybmV0wqBTb2NpZXR5wqBidXTCoEnCoGFtwqBub3TC
oHNwZWFraW5nwqBmb3LCoHRoZW3CoChvcsKgYW55b25lwqBlbGVzKcKgcmlnaHTCoG5vdy4N
Cj4+DQo+PiBPbsKgU3VuLMKgRmViwqAwNizCoDIwMjLCoGF0wqAwMjo1NzowOFBNwqAtMDUw
MCzCoFNjb3R0wqBLaXR0ZXJtYW7CoHdyb3RlOg0KPj4NCj4+PiBJwqB0aGlua8KgeW91csKg
b3JpZ2luYWzCoHN1Z2dlc3Rpb27CoHRoYXTCoGFuwqBTUEbCoHJlY29yZMKgYmXCoG1vZGlm
aWVkwqBiecKgdGhlwqBETlM2NA0KPj4+IHNlcnZlcsKgdG/CoGFkZMKgaXA2OsKgbWVjaGFu
aXNtc8Kgd2l0aMKgPHByZWZpeD7CoCvCoDxhZGRyZXNzPsKgaXPCoGHCoHJlYXNvbmFibGXC
oHBhdGgNCj4+PiBmb3J3YXJkLMKgYnV0wqBJwqB0aGlua8KgaXQnc8KgcmVhbGx5wqBhbsKg
UkZDwqA2MTQ3wqBkaXNjdXNzaW9uLMKgbm90wqBzb8KgbXVjaMKgUkZDwqA3MjA4Lg0KPj4N
Cj4+IFRoZcKgcHJvYmxlbcKgd2l0aMKgdGhpc8KgaXPCoHRoYXTCoGl0J3PCoGltcG9ydGlu
Z8KgdGhlwqBETlM2NMKgaW50aW1hdGXCoGtub3dsZWRnZcKgb2bCoHRoaXPCoHByb3RvY29s
wqBmb3LCoFRYVMKgcmVjb3JkcyzCoHdoaWNowqBtZWFuc8KgaW7CoGVmZmVjdMKgdGhhdMKg
RE5TNjTCoG5lZWRzwqB0b8Kgc3RhcnTCoHBhcnNpbmfCoGFyYml0cmFyecKgZGF0YcKgaW7C
oFRYVMKgcmVjb3Jkcy7CoMKgKFRoZXJlwqBpc8KgYcKgcmVhc29uwqBETlPCoHdlZW5pZXPC
oGFsd2F5c8KgZ290wqB1cHNldMKgYWJvdXTCoGlnbm9yaW5nwqB0aGXCoHN0cm9uZ8KgdHlw
aW5nwqBpbsKgRE5TLMKgYW5kwqB0aGlzwqBpc8KgYW7CoGV4YW1wbGXCoG9mwqBpdC4pDQo+
Pg0KPj4gRE5TNjQswqB0b8KgYmXCoGhvbmVzdCzCoHdhc8KgYWx3YXlzwqBzb3J0wqBvZsKg
YcKgaGFja8KgdGhhdMKgd2FzwqBpbnRlbmRlZMKgdG/CoG1ha2XCoHRyYW5zaXRpb27CoHRv
wqB2NsKgZWFzaWVyLsKgwqBJdMKgcmVhbGx5wqBiYXNpY2FsbHnCoGRlcGVuZGVkwqBvbsKg
dGhlwqBzdHJvbmfCoGRhdGHCoHR5cGluZ8Kgb2bCoEEswqBBQUFBLMKgYW5kwqBQVFLCoHJl
Y29yZHPCoGluwqBvcmRlcsKgdG/CoGdpdmXCoGl0wqBjbGVhcsKgcGxhY2VzwqB0b8KgaW5z
ZXJ0wqBpdHNlbGYuwqDCoCJMb29rwqBhdMKgZXZlcnnCoFRYVMKgcmVjb3JkLCLCoGRvZXNu
J3TCoHJlYWxsecKgc3VwcG9ydMKgdGhhdMKgcGxhbi7CoMKgScKgbmV2ZXLCoHRob3VnaHTC
oHdlwqB3ZXJlwqBkZXNpZ25pbmfCoGl0wqBmb3LCoGxvbmfCoGxpZmXCoG9ywqBoaWdowqBk
ZWdyZWVzwqBvZsKgcm9idXN0bmVzcyzCoGFuZMKgScKgdGhpbmvCoGl0wqBpc8KgbGlrZWx5
wqB0b8KgYmXCoGV4dHJlbWVsecKgZGlmZmljdWx0wqB0b8Kgb3BlcmF0ZcKgYcKgbW9kZXJu
wqBtYWlswqBzZXJ2ZXLCoG9uwqB2Ni1vbmx5wqBpbmZyYXN0cnVjdHVyZcKgYW5kwqBiZcKg
YWJsZcKgdG/CoHRhbGvCoHRvwqB2NC1vbmx5wqBtYWlswqBzZXJ2ZXJzLsKgwqBJbsKgYW55
wqBjYXNlLMKgScKgZ3Vlc3PCoGl0wqB3b3VsZMKgYmXCoF9wb3NzaWJsZV/CoHRvwqB0ZWFj
aMKgYcKgRE5TNjTCoHNlcnZlcsKgdG/CoHBhcnNlwqBhbmTCoGVkaXTCoFRYVMKgcmVjb3Jk
c8Kgb27CoHRoZcKgZmx5LMKgYnV0wqB0aGXCoGlkZWHCoHRoYXTCoHRoaXPCoGlzwqBnb2lu
Z8KgdG/CoGJlwqBsaW1pdGVkwqB0b8KgU1BGwqBpcyzCoEnCoHN1c3BlY3QswqBhwqBmYWxz
ZcKgaG9wZS7CoMKgRm9ywqB0aGF0wqByZWFzb24swqBtecKgcmVhY3Rpb27CoGlzwqB0aGF0
wqBpdMKgd291bGRuJ3TCoGJlwqBhwqBncmVhdMKgaWRlYcKgdG/CoGRvLsKgwqBJwqBuZXZl
cnRoZWxlc3PCoHN5bXBhdGhpemXCoHdpdGjCoHRoZcKgZGVzaXJlLMKgZXZlbsKgdGhvdWdo
wqBJwqBhbcKgbWFkZcKgbmVydm91c8KgYWJvdXTCoHRoZcKgaW1wbGljYXRpb25zLg0KPj4N
Cj4+PiBJdMKgaXPCoG5vdCzCoGhvd2V2ZXIswqB3aXRob3V0wqByaXNrcy7CoMKgUkZDwqA3
MjA4wqBTZWN0aW9uwqAzLjTCoGdpdmVzwqBhZHZpY2XCoG9uwqBTUEYNCj4+PiByZWNvcmTC
oHNpemUuwqDCoFlvdXLCoHByb3Bvc2VkwqBhcHByb2FjaMKgd291bGTCoGluY3JlYXNlwqB0
aGXCoHJlY29yZMKgc2l6ZSzCoHdoaWNoLMKgaW4NCj4+PiB0aGVvcnkswqBjb3VsZMKgYmXC
oHByb2JsZW1hdGljLsKgwqBJdMKgbWlnaHTCoGJlwqB0aGF0wqBhbnl0aGluZ8KgcnVubmlu
Z8Kgb27CoGFuwqBJUHY2DQo+Pj4gb25secKgbmV0d29ya8KgaXPCoG1vZGVybsKgZW5vdWdo
wqB0aGF0wqB0aGlzwqBpc24ndMKgYWN0dWFsbHnCoGHCoHByb2JsZW0uwqDCoEnCoGRvbid0
DQo+Pj4ga25vdy4NCj4+DQo+PiBJJ2TCoGJlwqBlc3BlY2lhbGx5wqB3b3JyaWVkwqBhYm91
dMKgUlJzZXTCoHNpemUswqBiZWNhdXNlwqBhwqBsb3TCoG9mwqBzdHVmZsKgaW7CoGNvbnRl
bXBvcmFyecKgb3BlcmF0aW9uc8KgaXPCoGphbW1lZMKgaW50b8KgVFhUwqByZWNvcmRzwqAo
YWxswqB0aG9zZcKgYXBwbGljYXRpb27CoGtleXMswqBmb3LCoGluc3RhbmNlKS7CoMKgScKg
Y2FuwqBpbWFnaW5lwqBjYXNlc8Kgd2hlcmXCoHRoZcKgY2hhbmdlwqBjb3VsZMKgbW92ZcKg
dGhlwqByZXNwb25zZcKgc2l6ZcKgYWNyb3NzwqB0aGXCoHJlc3BvbnNlwqBzaXplwqBib3Vu
ZGFyeSzCoGZvcmNpbmfCoHRydW5jYXRpb27CoGFuZMKgVENQwqBmYWxsYmFjay4NCj4+DQo+
PiBCZXN0wqByZWdhcmRzLA0KPj4NCj4+IEENCj4NCj4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gc3BmYmlzIG1haWxpbmcgbGlzdA0KPiBz
cGZiaXNAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9zcGZiaXMNCg==

--------------ms060600050103090301040507
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDcwMTA3NTFaME8GCSqGSIb3DQEJBDFCBEC5VpAm4yM4AXoYM+boK7K6
Q44aP8Bj/wRrtrhTUUXoHAmRFyKOBh0Z/jb/kmDvnB2uAcKx3jC6eQ2LP/HF/RMFMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAH+2bud2
3cQRosxQzHyOVY5rocURw1Tr5Il2ys6Q3ZBucMGb92jzF0xvCuZPUk1H+UIn1BWqNXL3StIi
8UITIqH3rnqyFcNxYxmnjWziEVUkkLYrkaH1Ho/5A0Rg0YzaJOcLT83sCryhgNGsWJq7zyqY
XVcfLNuxCBn8P5Tvv63WSMx4c/G3ye69nehKaQr+OA6h3sMG64KhHWvH3fxtrP2G+fiZfesR
DDt00FKx/aqUv6ZvOfin/ha1ug96IN/u/G5OAVVW/hekXzVH2cJcdJuIhWgCh7516nXRAl72
i9PnLeOLcIl8fGi8dmpHwwC8WsWmBFJm4UA4JuVoc5wWUORjosusnws/OQEmFC77luZLyM/9
CuLTMIZTIfIgw+GQRg4Kn3Q5WuwAAVVBnSNq0z8mcXSDwiOnS6L5sj52JNaoz6IBiw3ptPuK
5cPS4iHI2jLd8K944VDJ3V29LitWFOmEwhZKAzCn9MlcStRYfZF68CVJexZBmCH5Fl9EGVce
eYxqeuOlTrj+Y5c0Ma3wR0yM2MH5bCmuYmwYYZNAfOCtd6UygjSDdE33GgpO7RvHAffIZWT/
HncvT1W1ZH12oyKoTWiVNQDqye+Z/ElIwzsZTeFx4qVNMd32znnfEOzD9xKMqSVOO/QFz73L
uUu6s/EPJDMCv+Wp1gq5bHlamwlgAAAAAAAA
--------------ms060600050103090301040507--


From nobody Sun Feb  6 17:46:14 2022
Return-Path: <marka@isc.org>
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 C24D03A1143 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 17:46:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=isc.org header.b=T9MaypD3; dkim=pass (1024-bit key) header.d=isc.org header.b=Dr0o3ta8
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 YLufP3p7a-eO for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 17:46:05 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05F7A3A1142 for <spfbis@ietf.org>; Sun,  6 Feb 2022 17:46:04 -0800 (PST)
Received: from zimbrang.isc.org (zimbrang.isc.org [149.20.1.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id A05EE3AB009; Mon,  7 Feb 2022 01:46:02 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 mx.pao1.isc.org A05EE3AB009
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=isc.org; s=ostpay; t=1644198362; bh=CSFrNF1UizFctoTwKDx52M7YuXc//hKSsrYyrVWydzU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=T9MaypD3RnRkqrvTxWpkeuAw3PF4aHFDK/2ZfmTIiqyYn9re49zoBjgx8irzbleqo A5rXzeNagB73z6KOykm58JoXTD+E4UxVEOlagsxzzEf/YM5u8nIhvvfWNZAF/nJ9kS agItQ6JoIUz1qszJqVCzQV2H9O9f9rHzOExI1cF0=
Received: from zimbrang.isc.org (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTPS id 96207FE5318; Mon,  7 Feb 2022 01:46:02 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTP id 67DD2FE531A; Mon,  7 Feb 2022 01:46:02 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbrang.isc.org 67DD2FE531A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1644198362; bh=nUvyev1vVYNorikzoaVa/uYkU8thq1zD5xnYcNyHQOk=; h=Mime-Version:From:Date:Message-Id:To; b=Dr0o3ta8j64EnieWljEEH8/f53vz5+Gp0ROgZjLRv3jkfcBf2IOFzoYwL4aPgpemF onTSdAJqAhCj4ZG+a4K8JpJ3siRWAI9oNu5ciAnOfP/bR/oQhTmfa40iM2DYqc3Sco 0vKDSj9U4hdGPlP+J94DGRCt5Md3591yWkZRYCxo=
Received: from zimbrang.isc.org ([127.0.0.1]) by localhost (zimbrang.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 4ZF0VRgTstWX; Mon,  7 Feb 2022 01:46:02 +0000 (UTC)
Received: from smtpclient.apple (n114-74-26-107.bla4.nsw.optusnet.com.au [114.74.26.107]) by zimbrang.isc.org (Postfix) with ESMTPSA id C03C8FE5318; Mon,  7 Feb 2022 01:46:01 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <f2fccd74-355e-12b4-6b8a-539f61561a12@posteo.de>
Date: Mon, 7 Feb 2022 12:45:57 +1100
Cc: spfbis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E633D5D6-AFE1-4BDD-B202-1ED90A1F9CEF@isc.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> <f2fccd74-355e-12b4-6b8a-539f61561a12@posteo.de>
To: Klaus Frank <klaus.frank@posteo.de>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/qh-jAsCnbREgJEZb5634fTUPuZo>
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 01:46:12 -0000

Despite what you quote here, DNS64 is incompatible with DNSSEC because =
it hijacked the CD bit for a different purpose.  For a DNSSEC validator =
to work through another nameserver it needs to be able to send both CD=3D0=
 and CD=3D1
requests WITHOUT the records being modified.  The DNS64 working group =
was told this at the time but refused to listen. =20

CD=3D1 to handle bad time / bad trust anchors in the upstream =
nameservers.
CD=3D0 to handle spoofed / expired responses being sent to the upstream =
nameservers.

in BOTH cases the client validates the responses.  If the validation =
fails the first way, it should attempt the
request again with the CD bit in the other state.  If the second query =
fails then you have an actual DNSSEC failure.

Below was just wishful thinking upon behalf of the DNS64 working group.  =
They wanted a signal that meant the client is performing validation and =
refused to accept =E2=80=9Cif DO=3D1 then you have to assume the client =
is validating."

   3.  A security-aware and non-validating DNS64 receives a query with
       the DO bit set and the CD bit clear.  Such a resolver is not
       validating responses, likely due to local policy (see [RFC4035],
       Section 4.2).  For that reason, this case amounts to the same as
       the previous case, and no validation happens.

Making CD into a modify the response signal was/is incompatible with how =
DNSSEC uses CD.

Mark

> On 7 Feb 2022, at 12:07, Klaus Frank <klaus.frank@posteo.de> wrote:
>=20
>=20
> On 2022-02-07 01:42, william@leibzon.org wrote:
>>=20
>> Yeah, I wasn't thrilled with the idea of SPF using TXT record way =
back when. It opened it for quite a few others who followed. Putting ip =
addresses there though is not something that is done for any other =
protocol or software I can immediately think of.
>>=20
>> I'm curious, how does DNS64 inter-operates with DNSSEC? Would that =
not break it and make DNSSEC folks very uncomfortable about what others =
could decide to do?
>>=20
> Basically by offloading it towards the DNS64 server.
>=20
> https://datatracker.ietf.org/doc/html/rfc6147#section-6.2
>=20
> 6.2.  DNSSEC Validators and DNS64
>=20
>    An existing DNSSEC validator (i.e., one that is unaware of DNS64)
>    might reject all the data that comes from DNS64 as having been
>    tampered with (even if it did not set CD when querying). *If it =
is**
> **   necessary to have validation behind the DNS64, then the =
validator**
> **   must know how to perform the DNS64 function itself*. =
Alternatively,
>    the validating host may establish a trusted connection with a =
DNS64,
>    and allow the DNS64 recursive resolver to do all validation on its
>    behalf.
>=20
>> I think it could be helpful to collect various protocol operational =
and similar issues for those running mail servers (and other servers) =
behind NAT64 and write informational RFC which would be soft of =
experimental best practice. I'd expect that some server software would =
have to add special features to be used in this setup.
>>=20
> "special features" is exactly what I wanted to avoid. Also I don't =
know if it's strictly necessary to have a dedicated RFC for how to do =
the migration. Besides this issue with the SPF record it's basically the =
same as for any other server application. Use stateless NAT64 (aka. =
IPv4aaS) to have a dedicated public IPv4. Put that IPv4 (prefix) into =
the SPF record as usual. And for now disable the SPF validation for =
inbound mails. The only really noteworthy thing is with filtering stuff =
like SIEVE that these need to be updated to include their mapped IPv6 =
addresses or similar. Everything else just works because of NAT64 and =
DNS64...
>=20
>> On 2022-02-06 14:47, Andrew Sullivan wrote:
>>=20
>>> Hi,
>>>=20
>>> I'm one of the primary offenders behind DNS64.  I work for the =
Internet Society but I am not speaking for them (or anyone eles) right =
now.
>>>=20
>>> On Sun, Feb 06, 2022 at 02:57:08PM -0500, Scott Kitterman wrote:
>>>=20
>>>> I think your original suggestion that an SPF record be modified by =
the DNS64
>>>> server to add ip6: mechanisms with <prefix> + <address> is a =
reasonable path
>>>> forward, but I think it's really an RFC 6147 discussion, not so =
much RFC 7208.
>>>=20
>>> The problem with this is that it's importing the DNS64 intimate =
knowledge of this protocol for TXT records, which means in effect that =
DNS64 needs to start parsing arbitrary data in TXT records.  (There is a =
reason DNS weenies always got upset about ignoring the strong typing in =
DNS, and this is an example of it.)
>>>=20
>>> DNS64, to be honest, was always sort of a hack that was intended to =
make transition to v6 easier.  It really basically depended on the =
strong data typing of A, AAAA, and PTR records in order to give it clear =
places to insert itself.  "Look at every TXT record," doesn't really =
support that plan.  I never thought we were designing it for long life =
or high degrees of robustness, and I think it is likely to be extremely =
difficult to operate a modern mail server on v6-only infrastructure and =
be able to talk to v4-only mail servers.  In any case, I guess it would =
be _possible_ to teach a DNS64 server to parse and edit TXT records on =
the fly, but the idea that this is going to be limited to SPF is, I =
suspect, a false hope.  For that reason, my reaction is that it wouldn't =
be a great idea to do. I nevertheless sympathize with the desire, even =
though I am made nervous about the implications.
>>>=20
>>>> It is not, however, without risks.  RFC 7208 Section 3.4 gives =
advice on SPF
>>>> record size.  Your proposed approach would increase the record =
size, which, in
>>>> theory, could be problematic.  It might be that anything running on =
an IPv6
>>>> only network is modern enough that this isn't actually a problem.  =
I don't
>>>> know.
>>>=20
>>> I'd be especially worried about RRset size, because a lot of stuff =
in contemporary operations is jammed into TXT records (all those =
application keys, for instance).  I can imagine cases where the change =
could move the response size across the response size boundary, forcing =
truncation and TCP fallback.
>>>=20
>>> Best regards,
>>>=20
>>> A
>>=20
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Sun Feb  6 18:08:27 2022
Return-Path: <johnl@iecc.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 1BB213A117A for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 18:05:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level: 
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=iecc.com header.b=Ps1WarRr; dkim=pass (2048-bit key) header.d=taugh.com header.b=mufEWxMi
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 nSrgztwO08sT for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 18:04:58 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 1440A3A119A for <spfbis@ietf.org>; Sun,  6 Feb 2022 18:04:57 -0800 (PST)
Received: (qmail 57546 invoked from network); 7 Feb 2022 02:04:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=e0c6.62007e47.k2202; bh=qjW2Qlm+c2CnJKsH5K9g8uUUQYCl7JHNEMj9+CWcKuU=; b=Ps1WarRr3ZX9OFNck9uw7ND3k554pVIYHDXfKHjchVHHf6haC3SjjaH69eWXzueDARXfxl7ewNn7l/rBWa9Qzx6hqS/WIXDmYuhSpBHMSkvnz3N/xASt5sQuzqpsvYUPH4iePl0kLICm3A0IWFda2/9vtuVo5quzX8gPOvYqnsWBuPvU7fc4W58HVh4fxwhq8nYefLHe+rpU6slTm+V2redq8W2NvtsTs6A6Uo9XysBmisZxWv2t6M6cRhK2HqI41fSgIHj4snFL4XHGCH2YCDWvddRIKj1uFw0W9WLYQ8m9TWF6RekPluYbsSdfSC/ltfNTyYQX7xHwMaGd4xKPkw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=e0c6.62007e47.k2202; bh=qjW2Qlm+c2CnJKsH5K9g8uUUQYCl7JHNEMj9+CWcKuU=; b=mufEWxMio40NL6XodqV6Lp6C0z8SRhxUBgfG6ukHcoMzfGKnUGeipx4PNVkbgpO+21MNrsk453MxWgzUPnxIAhdTNyKQjcdi2AiCc8tBRJiVStuc/V8ZqfXBv10d2GUmGJRgsexexocImR+R0Y1YTxGi+Gn+MHa7v05IURroOcSp1mdaNAWW7h5xMTMpNXtYXELcpdKTMoRSpdfpB6YkI1jqQAnwcmExef37MIeL22bV8krWOcDWkr1wZSxcrXz5s31qgJPMUoaMqj2D7tMZTvTz+XvHPnP1MspotVS5H9nrhfsaKDcqQvi2TzerMUyIhdEPp2qfPOuue4IhxoqqnQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 07 Feb 2022 02:04:54 -0000
Received: by ary.qy (Postfix, from userid 501) id 1DE0C366A4FD; Sun,  6 Feb 2022 21:04:53 -0500 (EST)
Date: 6 Feb 2022 21:04:53 -0500
Message-Id: <20220207020454.1DE0C366A4FD@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: spfbis@ietf.org
Cc: klaus.frank@posteo.de
In-Reply-To: <9843fdc5-4443-e327-751b-330453ad7bf2@posteo.de>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/2Mv85Ejht8X9fCbZZ92cnciL6Jg>
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 02:05:08 -0000

It appears that Klaus Frank  <klaus.frank@posteo.de> said:
>-=-=-=-=-=-
>Either way one of both RFCs needs an addendum to address this.

Unless you can find other people attempting to do SPF validation from
behind DNS64, it seems like a very low priority.

SPF has been in wide use since RFC 4408 was published fifteen years ago,
and I don't ever recall anyone else raising this issue before.

If you want to try writing the patches for whatever SPF library you use,
I expect the maintainers would be happy to look at them, but since they
don't use DNS64 or NAT64 it'd be hard for them to test or validate them.

R's,
John


From nobody Sun Feb  6 18:21:56 2022
Return-Path: <angel@16bits.net>
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 096AF3A11AE for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 18:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 QqTmnCkZklPp for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 18:21:46 -0800 (PST)
Received: from mail.direccionemail.com (mail.direccionemail.com [199.195.249.9]) (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 4BC053A11A9 for <spfbis@ietf.org>; Sun,  6 Feb 2022 18:21:45 -0800 (PST)
Message-ID: <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net>
From: =?ISO-8859-1?Q?=C1ngel?= <angel@16bits.net>
To: spfbis@ietf.org
Date: Mon, 07 Feb 2022 03:21:40 +0100
In-Reply-To: <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca> <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/Jobjl8koc6ByLT_mSqh5JuoQajU>
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 02:21:52 -0000

On 2022-02-06 at 18:39 +0000, Klaus Frank wrote:
> >> Like:
> >> If the DNS64 server receives a SPF-record (within either the TXT-
> RR or the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST
> rewrites the ipv4 address according to the same rules as A-records
> are and synthesizes a new SPF record within the response that
> contains additional "ip6" entries. The original "ip4" should not be
> removed from the response.
> > I agree there is a problem. However, I can think of =E2=80=9Cinterestin=
g=E2=80=9D
> problems to solve, like: what if the ip4 contains a prefix, like
> 192.168.1.0/25. How would you translate this into IPv6 prefix by the
> DNS-64?
> Literally, your address of 192.168.1.0 would be e.g.
> ::ffff:c0a8:0100 and the prefix would just be 25+96

Ok, what about a component of "exists:%{ir}.list.dnswl.org" ?


A rewriting DNS64 dns server would need to keep track of spf queries,
learn that *.list.dnswl.org is special with a %{ir} pattern, and
rewrite queries matching that pattern with their ipv6 prefix into the
ipv4 one. Maybe they could rewrite into a pattern
like exists:%{ir}.list.dnswl.org.spfirexists.theirdomain.com which
tells it how it should be mapped, but it gets ugly really quick.

Having the SPF validator know about their IPv6 prefix -or, simply,
translate the IPv6 back into IPv4 before passing the address to the SPF
module- looks like a cleaner approach.

Best regards





From nobody Sun Feb  6 18:30:19 2022
Return-Path: <klaus.frank@posteo.de>
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 404C43A11CE for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 18:30:17 -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 Wj1mchcMJy8c for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 18:30:11 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 20DE63A11CB for <spfbis@ietf.org>; Sun,  6 Feb 2022 18:30:10 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id E0B0F240101 for <spfbis@ietf.org>; Mon,  7 Feb 2022 03:30:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644201008; bh=KiSv9Bneoyv+BtzjAJL2ub3MtSOng0i7ul3yNTME0jI=; h=Date:Subject:To:From:From; b=obSCDuuvcWWBv4+JwuB7TJUtF3e4lrvlWQVEr3/CMPoci7m6ceyEs4S2pWRaAnZzC QN5Ok+FEV/AcJj0GSK08croq3YEB/cNssFW7hGIf9w45X9g0HXh7I0OPDEr78AB8IH BPsONk8DiLsQVIgXwG8aLyYjK1Jl+obhtOt8bJTzFUyZuqNkgIzyfERA4WFEbtQAye BcIJOkoLJbTjOcl9scZoucpbciXA2ibMUJn4qQUKOqNdu5ZA2xmtvtcWbuX87Ndxps 1KgWzpg250Hr+KBXgz323sXbL93ZhUFvgn0oWiRij9HuDa9kz6kAuTy2T9zQbcBme/ z9XinNWQHmR9w==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsVV84TDmz9rxG for <spfbis@ietf.org>; Mon,  7 Feb 2022 03:30:08 +0100 (CET)
Message-ID: <e0f53dcc-a909-9476-691b-84184ba8761c@posteo.de>
Date: Mon,  7 Feb 2022 02:30:06 +0000
MIME-Version: 1.0
Content-Language: en-US
To: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca> <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de> <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms050807070408050004070902"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/gQMPrgb1vR33M2QPgp4c9yLvHlk>
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 02:30:18 -0000

This is a cryptographically signed message in MIME format.

--------------ms050807070408050004070902
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Why? Such a query would resolve in the mailserver would make the DNS 
lookup. The DNS64 server than would synthetically add an AAAA-RR to the 
response.

But now when reading the RFC7208 Section 5.7 again. We would need to 
extend that section to also validate the AAAA record. Currently it even 
states the limitation:

    The resulting domain
    name is used for a DNS A RR lookup (even when the connection type is
    IPv6).  If any A record is returned, this mechanism matches.

So the issue here is missing IPv6 support. Nothing no other special 
handling is required by the DNS64 server and it also doesn't need to be 
parsed. But the SPF library would need to also check the AAAA-RR, which 
considering future proving it should be doing anyway...

The DNS64 would only have to rewrite ip4 into ip6.

On 2022-02-07 03:21, Ángel wrote:
> A rewriting DNS64 dns server would need to keep track of spf queries,
> learn that *.list.dnswl.org is special with a %{ir} pattern

--------------ms050807070408050004070902
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDcwMjMwMDZaME8GCSqGSIb3DQEJBDFCBEDLNV9ZI85sTM35t2KZrPNl
qGJmBbpbG39WozLm5mkNtVt5klniaYLSQMa6RRYuWYGZY8cSFsJ1aWFGRw8TQoS2MGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAC9I6WbT
XiACg+T1kSVV5jz0gEuazj2A1iCksnzZCudKWKXGAvoXsoKdAPdtp6Q3aZmzlbXLv2OpsM8+
G//lClQqWDEMRKup4QVqzW8uKSrUYsiHkPDYNg9VQwna0x6HqVzPRYOE8cl7WOHk8oDZjBiF
y/ga4fZvY4/OfNeMnSV9uricYYR1MrUwECBDXTEYAh9PMp7m/NDPH5ilZ1TwL60iTw87pUV0
3Ay1L9Tdk8R4/u4w/YINE7XSbOEziVwapOz4+MN6+t6gkgsvI+XOA5Fp6t1CYum5+N47zlg8
lLiTmpFRYvOXEnKQ7vrZxOjFrdrVu4g87EO4AfG7ekW+/jNUmDmpdSQ4/Fb2GRdfLRvYOOMT
v3Y8ZhrOJZ8MvO6yWY4fc8qKXfmc8KwYfZ9UWBCoXxgOVYdWc/ahL9QDLGOvR+X7ZkcnS+Kl
yQMak6kicp9sK5q3G3QXn5fOY8A45NOQRIMotpvVFoTCR73/5bFg098yV+XwsQkX7qOyJHQ2
uUTfB+xVsFeVw77jdGhvsqreJkXMA8qz6uZx+QYdhGBmkN9sa05WouvYe9wT10n4uMu54IZJ
WUjAPIi1Ww4NixUfWS7e8rOmaUi3bSv2mkqXYjZAk82gyOv6QLOIZTKD/9cBOk7C3Jw1S33n
HFb/DqN2uAI0HZ8Xjrq/sPAGeJC3AAAAAAAA
--------------ms050807070408050004070902--


From nobody Sun Feb  6 18:54:39 2022
Return-Path: <klaus.frank@posteo.de>
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 3D01D3A1220 for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 18:54:35 -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 QDm41gZ3F1hn for <spfbis@ietfa.amsl.com>; Sun,  6 Feb 2022 18:54:28 -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 0DFA43A1215 for <spfbis@ietf.org>; Sun,  6 Feb 2022 18:54:27 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout01.posteo.de (Postfix) with ESMTPS id 9F26E240026 for <spfbis@ietf.org>; Mon,  7 Feb 2022 03:54:25 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644202465; bh=zufe36YGu14D71gHvr87IfNjeo9UGKTXYtW/jLP1cGM=; h=Date:Subject:To:From:From; b=O3uwvIXY/+WYnkZYDQggvmr/qWZE7OpobLIueKv67UM/Jmu2c65gQrpm27kLAOI6Z NeyI6zkjdmt5ZXK3cLqBhPP6jTzj7436FPZm8nyBVhMAG7PQQ4AaK4zh7cJWiIpxbQ os2YTfo73iOuwIn9sSgLjH7U4/8zzpDOiiCHuoVZzAvKMo9wMKFMG7yW/fXHANN/9U R4eMKk5y6oTllpEhietNQL4KtHs45w+UtQw5JtwnRymZUKF3NZsNR0Au+ZcV91P59A bIVA30oQSLptYuuKkN087eJR5I/lHA7qDCqmLUcSyPB3D6T/OJ3hOZZFTjFj1eyUpd MKa73uubHDKZQ==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsW290x60z9rxD for <spfbis@ietf.org>; Mon,  7 Feb 2022 03:54:24 +0100 (CET)
Message-ID: <c4b7de28-3eca-ee3e-fd8c-4181c91504ed@posteo.de>
Date: Mon,  7 Feb 2022 02:54:22 +0000
MIME-Version: 1.0
Content-Language: en-US
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> <f2fccd74-355e-12b4-6b8a-539f61561a12@posteo.de> <E633D5D6-AFE1-4BDD-B202-1ED90A1F9CEF@isc.org>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <E633D5D6-AFE1-4BDD-B202-1ED90A1F9CEF@isc.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms020100020800000802080503"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/sReTrgb85WdxZZ7q3wPFAi2qTkQ>
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 02:54:35 -0000

This is a cryptographically signed message in MIME format.

--------------ms020100020800000802080503
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Oh dear, it's even worse than I thought. Is there an errata or update 
rfc for that?

On 2022-02-07 02:45, Mark Andrews wrote:
> Despite what you quote here, DNS64 is incompatible with DNSSEC because it hijacked the CD bit for a different purpose.  For a DNSSEC validator to work through another nameserver it needs to be able to send both CD=0 and CD=1
> requests WITHOUT the records being modified.  The DNS64 working group was told this at the time but refused to listen.
>
> CD=1 to handle bad time / bad trust anchors in the upstream nameservers.
> CD=0 to handle spoofed / expired responses being sent to the upstream nameservers.
>
> in BOTH cases the client validates the responses.  If the validation fails the first way, it should attempt the
> request again with the CD bit in the other state.  If the second query fails then you have an actual DNSSEC failure.
>
> Below was just wishful thinking upon behalf of the DNS64 working group.  They wanted a signal that meant the client is performing validation and refused to accept “if DO=1 then you have to assume the client is validating."
>
>     3.  A security-aware and non-validating DNS64 receives a query with
>         the DO bit set and the CD bit clear.  Such a resolver is not
>         validating responses, likely due to local policy (see [RFC4035],
>         Section 4.2).  For that reason, this case amounts to the same as
>         the previous case, and no validation happens.
>
> Making CD into a modify the response signal was/is incompatible with how DNSSEC uses CD.
>
> Mark
>
>> On 7 Feb 2022, at 12:07, Klaus Frank <klaus.frank@posteo.de> wrote:
>>
>>
>> On 2022-02-07 01:42, william@leibzon.org wrote:
>>> Yeah, I wasn't thrilled with the idea of SPF using TXT record way back when. It opened it for quite a few others who followed. Putting ip addresses there though is not something that is done for any other protocol or software I can immediately think of.
>>>
>>> I'm curious, how does DNS64 inter-operates with DNSSEC? Would that not break it and make DNSSEC folks very uncomfortable about what others could decide to do?
>>>
>> Basically by offloading it towards the DNS64 server.
>>
>> https://datatracker.ietf.org/doc/html/rfc6147#section-6.2
>>
>> 6.2.  DNSSEC Validators and DNS64
>>
>>     An existing DNSSEC validator (i.e., one that is unaware of DNS64)
>>     might reject all the data that comes from DNS64 as having been
>>     tampered with (even if it did not set CD when querying). *If it is**
>> **   necessary to have validation behind the DNS64, then the validator**
>> **   must know how to perform the DNS64 function itself*. Alternatively,
>>     the validating host may establish a trusted connection with a DNS64,
>>     and allow the DNS64 recursive resolver to do all validation on its
>>     behalf.
>>
>>> I think it could be helpful to collect various protocol operational and similar issues for those running mail servers (and other servers) behind NAT64 and write informational RFC which would be soft of experimental best practice. I'd expect that some server software would have to add special features to be used in this setup.
>>>
>> "special features" is exactly what I wanted to avoid. Also I don't know if it's strictly necessary to have a dedicated RFC for how to do the migration. Besides this issue with the SPF record it's basically the same as for any other server application. Use stateless NAT64 (aka. IPv4aaS) to have a dedicated public IPv4. Put that IPv4 (prefix) into the SPF record as usual. And for now disable the SPF validation for inbound mails. The only really noteworthy thing is with filtering stuff like SIEVE that these need to be updated to include their mapped IPv6 addresses or similar. Everything else just works because of NAT64 and DNS64...
>>
>>> On 2022-02-06 14:47, Andrew Sullivan wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm one of the primary offenders behind DNS64.  I work for the Internet Society but I am not speaking for them (or anyone eles) right now.
>>>>
>>>> On Sun, Feb 06, 2022 at 02:57:08PM -0500, Scott Kitterman wrote:
>>>>
>>>>> I think your original suggestion that an SPF record be modified by the DNS64
>>>>> server to add ip6: mechanisms with <prefix> + <address> is a reasonable path
>>>>> forward, but I think it's really an RFC 6147 discussion, not so much RFC 7208.
>>>> The problem with this is that it's importing the DNS64 intimate knowledge of this protocol for TXT records, which means in effect that DNS64 needs to start parsing arbitrary data in TXT records.  (There is a reason DNS weenies always got upset about ignoring the strong typing in DNS, and this is an example of it.)
>>>>
>>>> DNS64, to be honest, was always sort of a hack that was intended to make transition to v6 easier.  It really basically depended on the strong data typing of A, AAAA, and PTR records in order to give it clear places to insert itself.  "Look at every TXT record," doesn't really support that plan.  I never thought we were designing it for long life or high degrees of robustness, and I think it is likely to be extremely difficult to operate a modern mail server on v6-only infrastructure and be able to talk to v4-only mail servers.  In any case, I guess it would be _possible_ to teach a DNS64 server to parse and edit TXT records on the fly, but the idea that this is going to be limited to SPF is, I suspect, a false hope.  For that reason, my reaction is that it wouldn't be a great idea to do. I nevertheless sympathize with the desire, even though I am made nervous about the implications.
>>>>
>>>>> It is not, however, without risks.  RFC 7208 Section 3.4 gives advice on SPF
>>>>> record size.  Your proposed approach would increase the record size, which, in
>>>>> theory, could be problematic.  It might be that anything running on an IPv6
>>>>> only network is modern enough that this isn't actually a problem.  I don't
>>>>> know.
>>>> I'd be especially worried about RRset size, because a lot of stuff in contemporary operations is jammed into TXT records (all those application keys, for instance).  I can imagine cases where the change could move the response size across the response size boundary, forcing truncation and TCP fallback.
>>>>
>>>> Best regards,
>>>>
>>>> A
>>> _______________________________________________
>>> spfbis mailing list
>>> spfbis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spfbis
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms020100020800000802080503
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDcwMjU0MjJaME8GCSqGSIb3DQEJBDFCBEDR2tF/QLwLMO1QCQpV1rcU
SHlkrsCwPFxFYFGOHuPgR+QwQSu8wVU1dnF6UW/F6F+MvgZxCwYSOhuZ8ADA6FLiMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAFB3xVov
jRRZVVYPEpLGSqtu62U1v35Md0/LpH6CLRaCOIrFSRS+4MpKXQE3Ivthq7xAZ+pmH31uzrBP
1/hLybSmbjM1lEv6EaAb7uSePvP7FYlfpMCbqrMvnHRsDQjf+F4JwksciPBhheWduiAe1mKB
4Wt9oEbO+8ghGuf2FQy6zeF+nsGVVeXLv9FNdWQTdC42zBABuZxerfINJgA14wcH536syi5l
b9FdvX0/hj4H3QMEoYlRxGU3AxTil1OvryN9+lGPtWVteeXYFgt164y9njxpQ0NKNA7FKOgw
2V2DDFiRkz7dwOkMzmofx/30QZh76hXizJv1f65MdexslwKeV3z42+s6KG9pnxvsAMG/e98y
KjQBurAU27xs/oWNqEKh1YtxKRGGZonWPMmrN/gQRdVhD1h2nGHBML4e96Fx933PdPLepdH4
8HDZgedA/q07oPfM1zyl5ExIJVS5ETkC7IvSkmgTwuXsT9ocfJsiWZaQBWFNoKgGchBaw3Bp
X/2vXL1DfH2veyp1UsdAjOqtFAEJM6mau6PTBlKHBr41ywqCCwRPFEsnLcU+QQ8OmaqZX7YY
/04+dzH9RrJ+6fPCCla8DELf4pNpjkeX5MdzdopfzHr73pmUTMh9+3/SD331o9Xzh7Z1GxuT
i2vsW9c79jHFAQwfEeS8tcb8S0kBAAAAAAAA
--------------ms020100020800000802080503--


From nobody Mon Feb  7 06:28:27 2022
Return-Path: <spf2@kitterman.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 8AC9F3A0830 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 06:28:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.1
X-Spam-Level: 
X-Spam-Status: No, score=-7.1 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=KObPWrHZ; dkim=pass (2048-bit key) header.d=kitterman.com header.b=mcbpxDKh
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 klrf30LaN6Bl for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 06:28:19 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE9193A07FE for <spfbis@ietf.org>; Mon,  7 Feb 2022 06:28:19 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id 3E51BF802ED for <spfbis@ietf.org>; Mon,  7 Feb 2022 09:28:17 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1644244097; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=cj39BXWO/YubQ6Zmuv4mJEYPUAdvujgcfZpUOi3Y+wg=; b=KObPWrHZZib+osHCCWLgi33QkFO1qkHfxuI6R52HdO9SrWVXyJ/vJoFPr+b/6bdYGTz5/ hKNsaHRixOTxZDeBg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1644244097; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=cj39BXWO/YubQ6Zmuv4mJEYPUAdvujgcfZpUOi3Y+wg=; b=mcbpxDKhl6/49K4EaUe6MkJHhsZhS9nYmlY1eSvPfuIWC3YOLgfaA1loC6fWWJEadzwFU 5FFGMq/9slGRNijgRQ01wRM7+Zsc3gRlWaCFay/YNYmgsVE1OFlnA0R34pWd5fJ+E94TbsO clOlIqrTwRZrIHA6RpJEX4M0QEeWhfvXCPVReol9zB8z16a92wesCsiKaACXqS1Sq/+EvUb 1/BvYcDbFuIJjJlZdykv5AZXtNIucdk0Pavw+zAm2HUkIeCxvoR+gWfumxjqJ33fsZz4PPT k4bYM1ASuaIH3fOVco9xzs2Ch9Bl1MNV9MOfcKB7eCiqSDmyVtLXnZUq7Efg==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 03DBAF801A9 for <spfbis@ietf.org>; Mon,  7 Feb 2022 09:28:16 -0500 (EST)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Mon, 07 Feb 2022 09:28:16 -0500
Message-ID: <2244581.DCeBYFrMaS@localhost>
In-Reply-To: <20220206221619.53E4836687AF@ary.qy>
References: <20220206221619.53E4836687AF@ary.qy>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/UrbxZlymx0LkbTTtq5sj_bE46aU>
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 14:28:25 -0000

On Sunday, February 6, 2022 5:16:18 PM EST John Levine wrote:
> It appears that Scott Kitterman  <spf2@kitterman.com> said:
> >It looks like situations like this one were contemplated by the RFC 6147
> >
> >authors:
> >> 6.  Deployment Notes
> >> 
> >>    While DNS64 is intended to be part of a strategy for aiding IPv6
> >>    deployment in an internetworking environment with some IPv4-only and
> >>    IPv6-only networks, it is important to realize that it is
> >>    incompatible with some things that may be deployed in an IPv4-only or
> >>    dual-stack context.
> >
> >On the SPF side of the discussion, I think it would, at least in theory, be
> >feasible to interpret an ip4: mechanism as <prefix> + <address> if the
> >connection is IPv6, but I don't see how a receiving SPF processor could
> >know what the prefix is.  As I read RFC 6147 Section 5.2, it could be
> >anything.
> See RFCs 7050 and 8880 for how you find the prefix(es).
> 
> That seems like a more reasonable way to go, patch the SPF library so it
> can use the NAT's Pref64 to fudge the interpretation of ip4 and ptr.
> 
> It looks like you could automate the entire thing -- when the library starts
> up, do an AAAA query on ipv4only.arpa, and if you get plausible answers,
> you know you're behind NAT64 and reinterpret ip4 and ptr terms
> appropriately.

Thanks.

Reading RFC 7050, it looks like ipv4only.arpa can return more than one name.  
That would seem to be a complication if I'm reading it correctly.

As a practical matter, it probably doesn't matter, but RFC 7050 doesn't update 
RFC 6147, so in theory other prefix determination methods could be used.

I guess the ::ffff:0:0/96 (IPv4-mapped Address) prefix should be considered 
similarly.

Is there enough here that it would be worth an Applicability Statement?

Scott K




From nobody Mon Feb  7 07:19:25 2022
Return-Path: <klaus.frank@posteo.de>
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 BD3DE3A0826 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 07:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.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, 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 (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 ZyK1y9olqh_R for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 07:19:18 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 672E63A082C for <spfbis@ietf.org>; Mon,  7 Feb 2022 07:19:18 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id 14257240101 for <spfbis@ietf.org>; Mon,  7 Feb 2022 16:19:14 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644247155; bh=q9Z2Jn8kltN3alE8vahSA9xvtYIIFbuWrs918wDCfW4=; h=Date:Subject:To:From:From; b=r/OWBv3/lV8zidUtuVGyd+B49pkLFSccyazYTPVsdRVkontALEul8+mBrRVb5wBgt XvS1mxhmctebyCnqQDCEQqXJVcp+rRtI/M+6oK9JOH00toJOaie/WtfJmaCtyQLYru 9OzPaTkcmnBFomFWeff5bWdyuCh9TUQOswazq1AfN4bxdbu+Hu3Dc72/21ACdD3UxX jmMjF3VgbzMEa2ZTwbIq3xHXKjIKXKbJ8UvMEb/ECcTGgmF7abpQxhOLCuBoiX0r9W VlWV5dO+mTQKoxmzW5pXWrT2UV+7cUHMu1h3PGv/+WzDHgFUyobv5iehX4dsL6BMeG 2EdmjT6idV9XA==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsqYZ0HRQz9rxB for <spfbis@ietf.org>; Mon,  7 Feb 2022 16:19:13 +0100 (CET)
Message-ID: <8d7a6274-8546-3145-17e3-c20c29d6df2e@posteo.de>
Date: Mon,  7 Feb 2022 15:19:12 +0000
MIME-Version: 1.0
Content-Language: en-US
To: spfbis@ietf.org
References: <20220206221619.53E4836687AF@ary.qy> <2244581.DCeBYFrMaS@localhost>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <2244581.DCeBYFrMaS@localhost>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms050701000809050504040903"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/bcH09i_4XJKUHHjdxca89F_OkVE>
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:19:24 -0000

This is a cryptographically signed message in MIME format.

--------------ms050701000809050504040903
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 2022-02-07 15:28, Scott Kitterman wrote:
> On Sunday, February 6, 2022 5:16:18 PM EST John Levine wrote:
>> It appears that Scott Kitterman  <spf2@kitterman.com> said:
>>> It looks like situations like this one were contemplated by the RFC 6147
>>>
>>> authors:
>>>> 6.  Deployment Notes
>>>>
>>>>     While DNS64 is intended to be part of a strategy for aiding IPv6
>>>>     deployment in an internetworking environment with some IPv4-only and
>>>>     IPv6-only networks, it is important to realize that it is
>>>>     incompatible with some things that may be deployed in an IPv4-only or
>>>>     dual-stack context.
>>> On the SPF side of the discussion, I think it would, at least in theory, be
>>> feasible to interpret an ip4: mechanism as <prefix> + <address> if the
>>> connection is IPv6, but I don't see how a receiving SPF processor could
>>> know what the prefix is.  As I read RFC 6147 Section 5.2, it could be
>>> anything.
>> See RFCs 7050 and 8880 for how you find the prefix(es).
>>
>> That seems like a more reasonable way to go, patch the SPF library so it
>> can use the NAT's Pref64 to fudge the interpretation of ip4 and ptr.
>>
>> It looks like you could automate the entire thing -- when the library starts
>> up, do an AAAA query on ipv4only.arpa, and if you get plausible answers,
>> you know you're behind NAT64 and reinterpret ip4 and ptr terms
>> appropriately.
> Thanks.
>
> Reading RFC 7050, it looks like ipv4only.arpa can return more than one name.
> That would seem to be a complication if I'm reading it correctly.
>
> As a practical matter, it probably doesn't matter, but RFC 7050 doesn't update
> RFC 6147, so in theory other prefix determination methods could be used.
>
> I guess the ::ffff:0:0/96 (IPv4-mapped Address) prefix should be considered
> similarly.
Oh yes, for sure good that you remind me of this one. We had one 
mailserver application (proprietary) that once we changed the binding 
from "0.0.0.0:25" to "[::]:25" on a linux system got everything as 
::ffff:0:0/96 and SPF validation also failed. But I'm not sure if that 
was an implementation simplification on their end or a OS dependent 
behavior of when binding a socket... The workaround we got was to "just 
deploy another VM for IPv6 and put them behind the same public DNS name. 
One for IPv4 and another one for the IPv6"
> Is there enough here that it would be worth an Applicability Statement?
>
> Scott K
>
>
>
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms050701000809050504040903
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDcxNTE5MTJaME8GCSqGSIb3DQEJBDFCBECg7imfR06cKEASxwgzUr4V
UCGFbdMbVSq//c17dXI1hDiGUvE/LRXedXJICM0s7evIND6wUhHj0iGGGIBEaj2hMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICABfMm5UJ
4KXr1CtKrTIMZSz7pjjmaV1Qkx71EBtoQ7glRVhmF4sIpQVXozqzkFc7fofrl9J4mXOwEumY
Y2eXFf/hRdGj/JGSvpGEIZTVExjNf7aAEWSR+VuDeNwTyGI92GvI6fBPmFLFczpSwfRLJrY8
z25k2vvNK6JyBlRDA7YePrk/QoM98Kb1uZKFk6BA9dZ/Xmn2yumIfCCmBhVJBEez9r7f+OpM
78a0HhTOuFuJ8WAekXadh8BXE4ZIJ3Qy+ohiIUTAcnPOGILS3Le5Es40dra1nqryykEd5yyS
kyJd3PrMI0hLxGylsvEB0Wktz6cR0leltEtRoOV05N0MihKr4MNN8HV5+qkh2D0/ImCFtH0o
U+yQSmUuxx3CZxshIOnkK7ucwpt4pMI3lM00KIAsYhsxksU+sHSoVtKRSaSqauNLhIJR+IuG
yt0opchlIS73tsbdGZPdSVVGzp67LDVHHn4J9px4Wz/u2bwnyoEdlsuxAuE1BG/Vf0D57HzK
r4yk4dO8JJzzNjeT/fT0tuXLEMBB/CnoVyiAUtfpd4S8o3QsvSP4gBXW5ASxFu5NecyeSwhV
RdCPLqOb+a5yK5qEdsBaKfYkN+ogYbEBuTeDoJXN8cx80hyYq//WJcraSMoD8qVZNxMgjps9
ySZMaAGxsRbJCjXVN7UKnaKXXfENAAAAAAAA
--------------ms050701000809050504040903--


From nobody Mon Feb  7 07:23:03 2022
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 481FD3A0C80 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 07:22:56 -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=m85Sh8Qt; dkim=pass (1024-bit key) header.d=yitter.info header.b=RGTIibBy
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 xEe-lWQwUQLR for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 07:22:51 -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 2A8B43A0CAA for <spfbis@ietf.org>; Mon,  7 Feb 2022 07:22:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id B369CBD5C8 for <spfbis@ietf.org>; Mon,  7 Feb 2022 15:22:11 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644247331; bh=dsAvKPE5lbPQ2LxT4YrMNSgG04SDULjFT4Vn/LkBHj8=; h=Date:From:To:Subject:References:In-Reply-To:From; b=m85Sh8Qt/IuGrO6qWZURQHMQjnLh5SknM9dgDNPo1Rm6gWAG/Mh26p7gdMrH20K2P JHXkJBfS8VrBgNPAyftmHKFHnjLBPTBPeUoFPIQYVZktCLGlaz24qoBq86e+VK3V/E k4hCTcUwCPQLx33W0SIfkOgxuLfJBFt+DlwYXCew=
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 26ebCZ4GfYRI for <spfbis@ietf.org>; Mon,  7 Feb 2022 15:22:10 +0000 (UTC)
Date: Mon, 7 Feb 2022 10:22:07 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644247330; bh=dsAvKPE5lbPQ2LxT4YrMNSgG04SDULjFT4Vn/LkBHj8=; h=Date:From:To:Subject:References:In-Reply-To:From; b=RGTIibBy+04aqSkntZLQDjFkI4Ryc935ya2ORlb+UilhgpoQhLK5Rbk+hk+mWuBzE cf5ISVzTtAtWK10BmlXZd1RgQ7GDBAbI3ShjDT/i2Q72Vvb48gRWe+SDA5CmjsxUet qqxC3l+C5dFjd/SZFTzaHZWqUlJa9ZkhMNkTgUa4=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: spfbis@ietf.org
Message-ID: <20220207152207.hw66pu5zmb6sqfbv@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> <b8e38c6a-aee9-8f86-350c-636c2f9d5efc@posteo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <b8e38c6a-aee9-8f86-350c-636c2f9d5efc@posteo.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/pzNDgZYP5xkNX8il1K0MFV9JNck>
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:23:02 -0000

On Mon, Feb 07, 2022 at 12:09:11AM +0000, Klaus Frank wrote:
>On 2022-02-06 23:47, Andrew Sullivan wrote:
>
>But it wouldn't be "every TXT record". If it doesn't start with 
>"v=spf1" it can be passed as is and does not require parsing. And even 
>then it's also a defined structure and not "arbitrary".

That is only true if you assume that the only case that counts is SPF.  But of course, that probably _isn't_ true.  Moreover, you still have to look at every TXT record and examine the RDATA.  That's not true for the other kinds of records: if you're a DNS64 you know that the A records are something you're going to have to process and you can have a high confidence that you'll probably need to process PTR records too.  What you are proposing is that the DNS64 needs to grab every TXT too, then look at the RDATA and _decide_ whether to process it, which is way more complicated.

>Actually the only limitation for that is the SPF record not being 
>updated by DNS64.

Sounds like a pretty severe limitation to me!

>What do you have in mind? What else would be there?

Anything could be in a TXT record, and once we start setting the precedent that the DNS64 should do rewrites of arbitrary text to capture certain relevant IPv4 addresses and make them IPv6 addresses with the appropriate prefix, there's no reason one has to stop at SPF.  The whole argument for using TXT records for SPF was that it was easy and you get to put what you want in a TXT.  But since "you get to put what you want", you have to live with the fact that there's not structured data in there from the point of view of the DNS.  Just because some other protocol wants to overload TXT and put structure into it does not mean that the DNS ought to be handling that RDATA programmatically.  TXT is arbitrary text data.

>As nothing else contains IP addresses but only dns names. I've 
>looked at the other record types. Did I miss something?

There's nothing that says that SPF is the only use of TXT here, so I don't see how you looking at your sample is proof of anything.  If DNS64 is supposed to start munging TXT records then it needs to do so in some predictable way.  If instead you want a neat hack of the sort John Levine suggested in order to generate the records on the fly, I certainly see the utility.  But I don't think standardizing that as part of DNS64 is a good idea.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Feb  7 07:25:03 2022
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, 7 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


From nobody Mon Feb  7 07:48:31 2022
Return-Path: <johnl@iecc.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 BD1783A0E4C for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 07:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=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=iecc.com header.b=jr1MspPX; dkim=pass (2048-bit key) header.d=taugh.com header.b=vLcjtBBN
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 jv6qcxo6GYvW for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 07:48:12 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 816FE3A0E0A for <spfbis@ietf.org>; Mon,  7 Feb 2022 07:47:18 -0800 (PST)
Received: (qmail 43056 invoked from network); 7 Feb 2022 15:47:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=a82a.62013f03.k2202; bh=WeFhoLdSK21fV3n+4DbjgVIQw/yG3dptKg1RWooJrJY=; b=jr1MspPXIP/1/V3ZuejAUT01ZRkAp71g3493vi92f4X2atrb/VvP2H/KOhzT/9PzYVtc6S/fJMJPvZXctuNuifks98vHLgz/cNH0+KyeTM9EI6OpSHEjX0Drsh/gKEWN5mgqgWVjaW1Mh6O+657frAz8bF/BOWaBOEnBtdTlUQsze4vWaN3hHZKu+DhZYCfVk1zzJHkxPQzNgbhmYpOi8wXvocCQ7mfZD4yRxtw45l6/tPywU68h/Vc6A5sHeDgQDBetaEuYSKIoBnYI2fbmb8QPDyY7tPyacI01i/STGRQrCVHVG5LyDOSIvSXkrkiMWOpVEVUbQuBoO79ALJEShA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=a82a.62013f03.k2202; bh=WeFhoLdSK21fV3n+4DbjgVIQw/yG3dptKg1RWooJrJY=; b=vLcjtBBN24iG+E5hRf6ivoc8K3poPFOXvaKkZi0CRlTpjHyWPfC2zkG2nhJKJHSJ6EfZSs2Y/WArpuEsy4DoYWT/bxF+PmrS5n0hHXULBa0vEDjvXfCooGqibZREotDZqCFkrPgKqa/YWRvCEtkn/gtRVCl00beR3Vj+Lt9y2dy3Sh+e5nif0tLa8d5TChZHgZnlfz4lUDKT6PCt0ibGfq5x/5tuEovweo4y9wKXtnARyb0xl4dOLJK7asOS2vDlj9TApi+NEfpOjL8J7y6iulmlOV3ac5yxtsPAxXYfwi5spM2tH2kbF6Bm7vDCGwiZUlrkpD+bY2wiCq8wtHfOqA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 07 Feb 2022 15:47:14 -0000
Received: by ary.qy (Postfix, from userid 501) id 40A34366F304; Mon,  7 Feb 2022 10:47:13 -0500 (EST)
Date: 7 Feb 2022 10:47:13 -0500
Message-Id: <20220207154714.40A34366F304@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: spfbis@ietf.org
Cc: spf2@kitterman.com
In-Reply-To: <2244581.DCeBYFrMaS@localhost>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/mongUcFbKOP0zGK7-9CWNZTyOZY>
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:48:28 -0000

It appears that Scott Kitterman  <spf2@kitterman.com> said:
>Reading RFC 7050, it looks like ipv4only.arpa can return more than one name.  
>That would seem to be a complication if I'm reading it correctly.
>
>As a practical matter, it probably doesn't matter, but RFC 7050 doesn't update 
>RFC 6147, so in theory other prefix determination methods could be used.
>
>I guess the ::ffff:0:0/96 (IPv4-mapped Address) prefix should be considered 
>similarly.
>
>Is there enough here that it would be worth an Applicability Statement?

On the one hand, I think the implementation would be quite easy.  When the SPF
library receives an external IPv6 address to check, it does the ipv4only
lookup and if the prefix on the address is one of the mapped ones, it
rewrites the IPv6 address to the corresponding IPv4 address and passes it
along to the rest of the SPF code.

On the other hand, since this is the first time in fifteen years that anyone
has run into this, I don't think it's worth fixing.  If you want to put a
mail server behind DNS64, you're on your own.

R's,
John


From nobody Mon Feb  7 08:21:39 2022
Return-Path: <spf2@kitterman.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 748B93A0D65 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 08:21:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.1
X-Spam-Level: 
X-Spam-Status: No, score=-7.1 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=p8/OtxRt; dkim=pass (2048-bit key) header.d=kitterman.com header.b=aZLp3t6Y
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 0c91EgBl-DZ3 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 08:21:20 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BEC03A0D26 for <spfbis@ietf.org>; Mon,  7 Feb 2022 08:21:20 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id F1716F802ED for <spfbis@ietf.org>; Mon,  7 Feb 2022 11:21:15 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1644250875; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=/WLukor1XIO2ToB1AgKQqZFp9swaW55p2M54kCPuVlc=; b=p8/OtxRtV4i+rQUWHbUbOkV+qsZYLAKdbZGmLqdhNeUueYtR1W23LM/nGzwN5DdcPmT89 5rvsiCQz92RUeZlBA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1644250875; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=/WLukor1XIO2ToB1AgKQqZFp9swaW55p2M54kCPuVlc=; b=aZLp3t6Y0IrvsV5rCnki8RP1ijplqJp5FcgI3T5eMvR5ibAY7Ef3PyJJyOeZsZngOkq5Z PxLYz6RlCH8EjxvbWNAYnSrOIK9LCeNnmdloOssUCISWZMDfMElZV86ZrUVc7QW4qzM1b3N YXEds/r90Rzyx0myJDTDv99n1VJAPjRZDUoMqcOTCry8ViJ/vN0U7l9euobYt5ANWLAGK3i I2to+hFaLHSUSF7vfiHUvTm0oAxCED4d5yTXUknDuhBdMyiKGAzQ4BWqYsmA7eD5xB3CBG4 wgay0dbt7BBNhUedqmH+0W8JCjGDy42joUkTEEzFJDctnPkeRtdWYm1hX3Kg==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id C3AF9F801A9 for <spfbis@ietf.org>; Mon,  7 Feb 2022 11:21:15 -0500 (EST)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Mon, 07 Feb 2022 11:21:15 -0500
Message-ID: <6024307.Q3qkd2Czva@localhost>
In-Reply-To: <20220207154714.40A34366F304@ary.qy>
References: <20220207154714.40A34366F304@ary.qy>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/R25ul6xy7nmiZc5nAiOErhaBfiA>
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 16:21:36 -0000

On Monday, February 7, 2022 10:47:13 AM EST John Levine wrote:
> It appears that Scott Kitterman  <spf2@kitterman.com> said:
> >Reading RFC 7050, it looks like ipv4only.arpa can return more than one
> >name. That would seem to be a complication if I'm reading it correctly.
> >
> >As a practical matter, it probably doesn't matter, but RFC 7050 doesn't
> >update RFC 6147, so in theory other prefix determination methods could be
> >used.
> >
> >I guess the ::ffff:0:0/96 (IPv4-mapped Address) prefix should be considered
> >similarly.
> >
> >Is there enough here that it would be worth an Applicability Statement?
> 
> On the one hand, I think the implementation would be quite easy.  When the
> SPF library receives an external IPv6 address to check, it does the
> ipv4only lookup and if the prefix on the address is one of the mapped ones,
> it rewrites the IPv6 address to the corresponding IPv4 address and passes
> it along to the rest of the SPF code.
> 
> On the other hand, since this is the first time in fifteen years that anyone
> has run into this, I don't think it's worth fixing.  If you want to put a
> mail server behind DNS64, you're on your own.

I think that's a fair reading of RFC 6147 itself:

> 6.  Deployment Notes
>
> While DNS64 is intended to be part of a strategy for aiding IPv6
> deployment in an internetworking environment with some IPv4-only and
> IPv6-only networks, it is important to realize that it is
> incompatible with some things that may be deployed in an IPv4-only or
> dual-stack context.

OTOH, how long has DNS64 been deployed (I don't know)?  Will it see increased 
deployment in the future, so this is the leading edge of the issue?

Personally, I don't have an interest in DNS64, but I think it's not 
unreasonable for the IETF to document how to navigate the intersection of two 
standards track documents.

Scott K



From nobody Mon Feb  7 09:31:41 2022
Return-Path: <johnl@iecc.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 9FA483A0FCB for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 09:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.85
X-Spam-Level: 
X-Spam-Status: No, score=-6.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, 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=iecc.com header.b=hC1O2f69; dkim=pass (2048-bit key) header.d=taugh.com header.b=O/urshfN
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 vWGOzXwhQ1nn for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 09:31:34 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 695BA3A0FC2 for <spfbis@ietf.org>; Mon,  7 Feb 2022 09:31:34 -0800 (PST)
Received: (qmail 41644 invoked from network); 7 Feb 2022 17:31:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=a2a0.62015773.k2202; bh=WR35AjToTlCVJcOtE34/DMfh45fDAe770axeWlUnwjc=; b=hC1O2f69mkXM4B7jadj9DZsYN56MS0xuehX//YjNWmPafXYlVnEG5pw2J1eWUMZUtTF4WmXLcuJGo/ZijB8WtLixZwPEywvSBM7XphEHqP5W2wwaCbtfwLFV3g4csWPRPkwziwJR89GBQGBBp9xd73vhBKx6NJ5zWlJlSEGK19nMTiV8wtwfV/g88JGxT5PPQUkpfwkl3nphmbW34fUxJredLW3W9DLj1zVWVQzohKUCk4LXe65nUT9a/w8gwZzzIqqVsbDcAIOeF+xiV/tui0FPH9NT8vCYhIWClH30LXCd/HF4Mi+73ixKOCJcp5WdhvSv04xSkI9qPth6DZLzDg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=a2a0.62015773.k2202; bh=WR35AjToTlCVJcOtE34/DMfh45fDAe770axeWlUnwjc=; b=O/urshfNMvmKem7Tk9daBVBgHHWK4juoV+CCYqw0u71A/69ekwQZDjGQfXCgDKaFB0/Fqrs7lUurYnKVGYq+7xMTla3MG31oaNX1wAcC6aIClXG0AlHyVfAHo2eyIWNZsOCnl6qbbTxRX+SXhxZe70YfhQdH+PMagaMDDEql/AKS15G86Pz5L/khLSUjtVxiQsNmY6kVrycPv7NKC0OMbx5b2nJQt8c+9x4+1U1uCQI6uZ6xtzyXCI2oWEONgsoK5VDj3ZyZhI9aPrS3PViTb9DCurpPzGgz2BLWzjoWEFdfQHQcPJWo8irIaHmqi4TDoUTHqFaODy4PF3XTkUaXeg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 07 Feb 2022 17:31:30 -0000
Received: by ary.qy (Postfix, from userid 501) id B8DE4367046B; Mon,  7 Feb 2022 12:31:28 -0500 (EST)
Date: 7 Feb 2022 12:31:28 -0500
Message-Id: <20220207173129.B8DE4367046B@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: spfbis@ietf.org
Cc: spf2@kitterman.com
In-Reply-To: <6024307.Q3qkd2Czva@localhost>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/jQ7ZdCWyD01hJIelYTtIQsDtsnw>
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 17:31:40 -0000

It appears that Scott Kitterman  <spf2@kitterman.com> said:
>OTOH, how long has DNS64 been deployed (I don't know)?  Will it see increased 
>deployment in the future, so this is the leading edge of the issue?

I think DNS64 and NAT64 fall into the category of "nice try". The idea
was that your devices could all be IPv6 only and the complexity would
all be in the NAT and the DNS translator.

But we now know that DNS64 breaks DNSSEC, it breaks SPF, and as Andrew
has pointed out, it likely breaks other stuff too. NAT64 and DNS64 are
probably OK for mobile networks where everything is a client and P2P
servers are discouraged.

But in reality, all devices are dual stacked, and networks use NAT44
to connect to the IPv4 outside world. I have a bunch of servers at
AWS. They all have real IPv6 addrsses and local 10/8 addresses. The
ones that need to be visible from outside have static real IPv4
addresses routed through the NAT (rumor says at least two levels of
NAT.) The others can get a temporary address from the AWS pool while
they are active. What my hosts see is a /16 of 10/8 where I can
activate /24 subnets in different geographic regions.

It works fine. There is no messing with the DNS, DNSSEC works, the
remote IPv4 addresses my servers see are the real ones so if they were
doing SPF, it would work too.

For a long time the IETF desperately tried to pretend that NAT44 was
useless or stupid or didn't exist, and there were a few attempts to
do something that wasn't NAT44.  I think this is one of them.

R's,
John


From nobody Mon Feb  7 09:53:01 2022
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 5E6663A1018 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 09:52:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, 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=VH7QQLdv; dkim=pass (1024-bit key) header.d=yitter.info header.b=B8DyakaJ
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 eY1f8_LO6J6p for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 09:52: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 9C8103A107C for <spfbis@ietf.org>; Mon,  7 Feb 2022 09:52:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 3537FBD5C8 for <spfbis@ietf.org>; Mon,  7 Feb 2022 17:52:10 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644256330; bh=KSzi/ZLSQYsFE5m9Qqf3UTBT/ebJ6kkwqSrNjxiyUwo=; h=Date:From:To:Subject:References:In-Reply-To:From; b=VH7QQLdv9qWAT2vaohMgNYv98qvIbM12cvXhtLH/giwnEJhCZhcvlvXm5mO1CsYvi finiLBJnS84Qez32Z6axxpo9zHRkUL+8VrXn2bci3e2uUcSTxEQ3yLzjSynDgtFWgi JeRjaaG8MDmHrwuwgmzcJHWpJNgTvhGg3/kX5Fpg=
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 Yp7lDjHYk5w0 for <spfbis@ietf.org>; Mon,  7 Feb 2022 17:52:07 +0000 (UTC)
Date: Mon, 7 Feb 2022 12:52:06 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644256327; bh=KSzi/ZLSQYsFE5m9Qqf3UTBT/ebJ6kkwqSrNjxiyUwo=; h=Date:From:To:Subject:References:In-Reply-To:From; b=B8DyakaJNeicLMtjxu67vu6ule5JdvI6yQA/1kgpZnziPM65q24y3eB2vNZxS2fR6 L6G2MeU+h0TfcIL4fUCulCLhQ+jBxjscpEVONf3RzWsAffy8EjUtCd+2vNDtTCb4c6 Sy5AoNOufeW/dirPTyrJO86rsko1whCbLtE8hy9k=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: spfbis@ietf.org
Message-ID: <20220207175206.rfxlt5s5rxhubjyg@crankycanuck.ca>
Mail-Followup-To: spfbis@ietf.org
References: <6024307.Q3qkd2Czva@localhost> <20220207173129.B8DE4367046B@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20220207173129.B8DE4367046B@ary.qy>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/PfvWbFNWEOO_Xd8gphb8lmqrvGo>
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 17:52:59 -0000

Hi,

(Still working for someone and not speaking for them.)

On Mon, Feb 07, 2022 at 12:31:28PM -0500, John Levine wrote:

>But we now know that DNS64 breaks DNSSEC

To be clear, we _always_ knew this (see RFC 6147 section 5.5).  Mark Andrews felt very strongly that the way it worked was wrong, I am aware.

> it breaks SPF

I don't actually think that is true.  I think SPF is a case where, if you're going to use an application that depends on IPv4 literals behind a NAT64, you're going to need a NAT64-aware application.  That shouldn't be too surprising in my opinion.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Feb  7 10:29:58 2022
Return-Path: <johnl@iecc.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 43DA83A105C for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 10:29:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=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=iecc.com header.b=Os2E/NHg; dkim=pass (2048-bit key) header.d=taugh.com header.b=B7AAV5/t
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 mJNH3v7fFCaI for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 10:29:51 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 1489E3A0B75 for <spfbis@ietf.org>; Mon,  7 Feb 2022 10:29:50 -0800 (PST)
Received: (qmail 68829 invoked from network); 7 Feb 2022 18:29:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=10cda.6201651c.k2202; bh=yN2vJH2draAcprKJ0eQ4Y5JSTyBMRo5RifqBXpyAd6w=; b=Os2E/NHgysOATa35k9rVjm7qJjOGG/tqGyHWWYDvE/aNguXlvPfkcKV2SMjHQmj6+iTrY6rO0udb64QdWzHvtsWuftpbjYffjEUbq3TdlqZ8fwIyw85By8SemOUZ/9t1t04wxIUyEXGX4dFo4jMc0/WX+twRjiIklVoKxsXTxEu0Y60jvzyxizGthEWJ9rn2X/pRHHrzErwuqbvp+NFl0Xb6KcJTca9u2IbA3eLz8H09CK6eBt+/+JKT3vvOR4FD2sHQbZq91SicMuvUQrJm4DifLRRTUAnUHEuipGkLfEBCttGih7xdkp5bKlMh5UM0yR+3U+qBz2NozzxLPO49Hw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=10cda.6201651c.k2202; bh=yN2vJH2draAcprKJ0eQ4Y5JSTyBMRo5RifqBXpyAd6w=; b=B7AAV5/tX+21YdeYfPVS1NCRh/eDVAvgiszttZ7k2G/AZMpgWQMd1E6M7bu1nKc2uIHcN3CZ5grGIe8PslhAtwfsiBeLUR/UG3cUrZUx4hZNnzmyJeDex817aQrv92F+UcvMkDPHPOwN+5h7NdRc426kLpnDR3AQozHalCcZ6u17VimjFaQOuCscxlv+w9IdTiGSEHKfl3TDmAVBpNUFRn7AkVEnTVqX0QZJt20wlqqztSYodSHU7CfEaUuN7Kxwyx5qNW8tN8U6nFxcmBkF+RBYO43obrV6pJf9O8/KftdVaYz8fjmiiF20dj/iHoSIJDi2j3Tcc0uMvx5Z4Loetw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 07 Feb 2022 18:29:48 -0000
Received: by ary.qy (Postfix, from userid 501) id 92BB13670E02; Mon,  7 Feb 2022 13:29:46 -0500 (EST)
Date: 7 Feb 2022 13:29:46 -0500
Message-Id: <20220207182947.92BB13670E02@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: spfbis@ietf.org
Cc: ajs@anvilwalrusden.com
In-Reply-To: <20220207175206.rfxlt5s5rxhubjyg@crankycanuck.ca>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/reVuGraZj6H2s_KXpse8awkcyIY>
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 18:29:56 -0000

It appears that Andrew Sullivan  <ajs@anvilwalrusden.com> said:
>Hi,
>
>(Still working for someone and not speaking for them.)
>
>On Mon, Feb 07, 2022 at 12:31:28PM -0500, John Levine wrote:
>
>>But we now know that DNS64 breaks DNSSEC
>
>To be clear, we _always_ knew this ...
>
>> it breaks SPF
>
>I don't actually think that is true.  I think SPF is a case where, if you're going to use an application that depends on IPv4 literals behind a NAT64, you're going o need a NAT64-aware application.  That shouldn't be too surprising in my opinion.

It seems to me they're really the same. If the application knows it's
behind DNS64 and it sees an AAAA record with a translated address, the
application can translate it back and see if it's valid, e.g., ask for
signed DNS A records and see if the addresses match.

Of course, if you can expect the endpoint to know that much about
what's going on, you might as well skip the DNS hackery ahd do the
address translation in the endpoint's socket routines. I probably
should stop now lest someone think that was a serious suggestion.

R's,
John


From nobody Mon Feb  7 10:40:09 2022
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 9D5A73A112E for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 10:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, 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=ey0UCbhF; dkim=pass (1024-bit key) header.d=yitter.info header.b=hG6kQjHO
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 smpez76UAJSC for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 10:39:43 -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 41FBF3A10D7 for <spfbis@ietf.org>; Mon,  7 Feb 2022 10:39:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 329CFBD5C8 for <spfbis@ietf.org>; Mon,  7 Feb 2022 18:38:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644259125; bh=kso+dcZfI+tSWdM6Am7oGQZn8s86oclza1LEc8yxMAU=; h=Date:From:To:Subject:References:In-Reply-To:From; b=ey0UCbhFdcuM7VyME8/T96I0MCdfLZMkq/2bAQbpucQEyQVvDgucMwo9VW+eQZrRp XQu5WzAuoJxT2gqcVbaz+xwex94keTUX4lq+82wnAuCOwreY5E/dGSkV1ApdzW1YDV kW34zaJIEA700xgqrJwOTXiCe9s+AoIW/ESeisi8=
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 eMVfDbGEiyTm for <spfbis@ietf.org>; Mon,  7 Feb 2022 18:38:43 +0000 (UTC)
Date: Mon, 7 Feb 2022 13:38:41 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1644259123; bh=kso+dcZfI+tSWdM6Am7oGQZn8s86oclza1LEc8yxMAU=; h=Date:From:To:Subject:References:In-Reply-To:From; b=hG6kQjHOe9EBQg3PNcc681CMIN4Uae6qBFNiDo9zE3bGXELVzF3aBRBmIdXGC7KL3 WlyR6IEPstsOISDZkJhWNthbbDUllDSI6gxgPsBzSCBx+ffpp8rjvXt0mtVSbTEc9S 1SgADXPvvyJkru+4q5unxpmqY9b86TjXoJKI2+Lw=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: spfbis@ietf.org
Message-ID: <20220207183841.jhx67gokm63xp2d3@crankycanuck.ca>
Mail-Followup-To: spfbis@ietf.org
References: <20220207175206.rfxlt5s5rxhubjyg@crankycanuck.ca> <20220207182947.92BB13670E02@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20220207182947.92BB13670E02@ary.qy>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/EFZIuDNFvEZPdOUCysvapdBBMmo>
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 18:39:49 -0000

On Mon, Feb 07, 2022 at 01:29:46PM -0500, John Levine wrote:
>Of course, if you can expect the endpoint to know that much about
>what's going on, you might as well skip the DNS hackery ahd do the
>address translation in the endpoint's socket routines. I probably
>should stop now lest someone think that was a serious suggestion.

There's effectively a mode for that in RFC 6147: it's called DNS64 in
stub-resolver mode, and it's really the only way to get validation on
the endpoint working.  I spent a fair amount of time thinking about
that sort of thing, and it's what convinces me you can't really build
the scaffolding correctly in DNS64 to handle embedded v4 literals in
TXT records.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From SRS0=tV5T4=SW==stuart@gathman.org  Mon Feb  7 11:12:51 2022
Return-Path: <SRS0=tV5T4=SW==stuart@gathman.org>
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 936ED3A0BD1 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 11:12:51 -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, RCVD_IN_DNSWL_BLOCKED=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=gathman.org
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 8T9cKVctoZxO for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 11:12:46 -0800 (PST)
Received: from mail.gathman.org (mail.gathman.org [IPv6:2001:470:8:809::1010]) (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 A492E3A0BCB for <spfbis@ietf.org>; Mon,  7 Feb 2022 11:12:45 -0800 (PST)
Authentication-Results: mail.gathman.org; iprev=pass policy.iprev="2001:470:8:809::1010" (wiki.gathman.org); auth=pass (CRAM-MD5 sslbits=256) smtp.auth=stuart
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gathman.org;  i=@gathman.org; q=dns/txt; s=default; t=1644261138;  h=date : from : to : cc : subject : in-reply-to :  message-id : references : mime-version : content-type :  date : from : subject;  bh=stJnL2nxio4lE7exhrvbun6gBP5/vB6rOdVozYpuD9k=;  b=RmNF+fk8BREG6AiIJcW555BRwtJSHjssvPRNJFWfcQD8+9iFCYxpSQjn SDAKegCLCIS358T8hKSUvD01QbYPCWyNT7/hPGvzcv0jJqkxh+m2LqiD3i 5gT5WIsKXS8SsPjHci4wVLyJwpDi0IakVN04z0nsqb9S65tJ0tMhgEy4w=
Received: from wiki.gathman.org (wiki.gathman.org [IPv6:2001:470:8:809::1010]) (authenticated bits=0) by mail.gathman.org (8.14.7/8.14.7) with ESMTP id 217JCEu0029623 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 7 Feb 2022 14:12:15 -0500
Date: Mon, 7 Feb 2022 14:12:14 -0500 (EST)
From: Stuart D Gathman <stuart@gathman.org>
To: John Levine <johnl@taugh.com>
cc: spfbis@ietf.org, ajs@anvilwalrusden.com
In-Reply-To: <20220207182947.92BB13670E02@ary.qy>
Message-ID: <8776eb76-8e6d-6ef8-b3c-92e9c9b8853@gathman.org>
References: <20220207182947.92BB13670E02@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/uccFmv9FvFZ4whUpJLL7p2l0khM>
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 20:16:14 -0000

On Mon, 7 Feb 2022, John Levine wrote:

> It appears that Andrew Sullivan  <ajs@anvilwalrusden.com> said:
> Of course, if you can expect the endpoint to know that much about
> what's going on, you might as well skip the DNS hackery ahd do the
> address translation in the endpoint's socket routines. I probably
> should stop now lest someone think that was a serious suggestion.

Serious suggestion: forget about an IP protocol from the last century,
and use IP6.  If absolutely necessary to receive email from IP4,
use an SMTP gateway listening on IP4 to forward the mail to IP6.  IP info
is captured in headers (either Received or Received-SPF from the trusted
gateway).


From nobody Mon Feb  7 14:41:05 2022
Return-Path: <angel@16bits.net>
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 207833A0E1A for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 14:41:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 GUtwTsvE92PO for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 14:41:00 -0800 (PST)
Received: from mail.direccionemail.com (mail.direccionemail.com [199.195.249.9]) (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 6CE3C3A0E19 for <spfbis@ietf.org>; Mon,  7 Feb 2022 14:40:59 -0800 (PST)
Message-ID: <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net>
From: =?ISO-8859-1?Q?=C1ngel?= <angel@16bits.net>
To: spfbis@ietf.org
Date: Mon, 07 Feb 2022 23:40:56 +0100
In-Reply-To: <e0f53dcc-a909-9476-691b-84184ba8761c@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca> <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de> <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net> <e0f53dcc-a909-9476-691b-84184ba8761c@posteo.de>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/hAdFT4P8dKFJ6W49MgMOyiWTRdg>
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 22:41:03 -0000

On 2022-02-07 at 02:30 +0000, Klaus Frank wrote:
> Why? Such a query would resolve in the mailserver would make the DNS=20
> lookup. The DNS64 server than would synthetically add an AAAA-RR to
> the response.

The issue is not that the response contains an A record but that the
queried domain embeds the remote IP.

The A result is usually a 127.0.0.x address, with some "magic" meaning
(perhaps lost if translated into IPv6) but the main problem is querying
the right label.


From nobody Mon Feb  7 15:22:30 2022
Return-Path: <william@leibzon.org>
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 9364E3A0FBE for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:22:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 JvdHPURI2V3d for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:22:21 -0800 (PST)
Received: from relay5.hostedemail.com (relay5.hostedemail.com [64.99.140.39]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDC623A0EDF for <spfbis@ietf.org>; Mon,  7 Feb 2022 15:22:15 -0800 (PST)
Received: from omf04.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id 4F08921BA6; Mon,  7 Feb 2022 23:22:14 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: william@leibzon.org) by omf04.hostedemail.com (Postfix) with ESMTPA id EA90E20027;  Mon,  7 Feb 2022 23:22:13 +0000 (UTC)
MIME-Version: 1.0
Date: Mon, 07 Feb 2022 15:22:13 -0800
From: william@leibzon.org
To: =?UTF-8?Q?=C3=81ngel?= <angel@16bits.net>
Cc: spfbis@ietf.org
In-Reply-To: <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca> <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de> <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net> <e0f53dcc-a909-9476-691b-84184ba8761c@posteo.de> <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net>
Message-ID: <1fc6a0d819c1872624dcae1e15af0384@leibzon.org>
X-Sender: william@leibzon.org
Content-Type: multipart/alternative; boundary="=_b4f0b268ce40528b133c0d5a6febf659"
X-Rspamd-Queue-Id: EA90E20027
X-Stat-Signature: zx8t4addxj76cmhrp6dwwgryjdjxec1k
X-Rspamd-Server: rspamout08
X-Session-Marker: 77696C6C69616D406C6569627A6F6E2E6F7267
X-Session-ID: U2FsdGVkX19xwLW1hhg66hLWp/Sd2PvakmNvrbXIxj0=
X-HE-Tag: 1644276133-866703
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/SkEa4cW27EQfPBKz2aYXLmG4xbk>
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 23:22:28 -0000

--=_b4f0b268ce40528b133c0d5a6febf659
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8;
 format=flowed



SPF macro tricks: 
https://www.jamieweb.net/blog/using-spf-macros-to-solve-the-operational-challenges-of-spf/
I wonder how many people actually use SPF macros....

But yeah, trying to translate these is the kind of hell that should be 
reserved for full SPF library and not something DNS64 server should 
probably attempt. Looks like those who want SPF to work behind NAT64 
would have to use a library that can discovery what NAT64 prefix is and 
translate everything.

BTW, what's going on with exists and A vs AAAA? The SPF 7206 RFC says:

exists           = "exists"   ":" domain-spec

    The <domain-spec> is expanded as per Section 7 [1].  The resulting 
domain
    name is used for a DNS A RR lookup (even when the connection type is
    IPv6).  If any A record is returned, this mechanism matches."

How is this meant to work for those in IPv6 only world? And what will 
happen when a SPF resolver behind DNS64 tries to resolve this? Is DNS64 
just adding AAAA while preserving the A as well for an application that 
needs it?

  On 2022-02-07 14:40, Ángel wrote:

> On 2022-02-07 at 02:30 +0000, Klaus Frank wrote:
> 
>> Why? Such a query would resolve in the mailserver would make the DNS
>> lookup. The DNS64 server than would synthetically add an AAAA-RR to
>> the response.
> 
> The issue is not that the response contains an A record but that the
> queried domain embeds the remote IP.
> 
> The A result is usually a 127.0.0.x address, with some "magic" meaning
> (perhaps lost if translated into IPv6) but the main problem is querying
> the right label.
> 
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis


Links:
------
[1] https://datatracker.ietf.org/doc/html/rfc7208#section-7
--=_b4f0b268ce40528b133c0d5a6febf659
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p>SPF macro tricks: https://www.jamieweb.net/blog/using-spf-macros-to-solv=
e-the-operational-challenges-of-spf/<br />I wonder how many people actually=
 use SPF macros....</p>
<div id=3D"signature"></div>
<p>But yeah, trying to translate these is the kind of hell that should be r=
eserved for full SPF library and not something DNS64 server should probably=
 attempt. Looks like those who want SPF to work behind NAT64 would have to =
use a library that can discovery what NAT64 prefix is and translate everyth=
ing.<br /><br />BTW, what's going on with exists and A vs AAAA? The SPF 720=
6 RFC says:<br /><br /></p>
<pre class=3D"newpage">exists           =3D "exists"   ":" domain-spec

   The &lt;domain-spec&gt; is expanded as per <a href=3D"https://datatracke=
r.ietf.org/doc/html/rfc7208#section-7">Section 7</a>.  The resulting domain
   name is used for a DNS A RR lookup (even when the connection type is
   IPv6).  If any A record is returned, this mechanism matches."
</pre>
<p>How is this meant to work for those in IPv6 only world? And what will ha=
ppen when a SPF resolver behind DNS64 tries to resolve this? Is DNS64 just =
adding AAAA while preserving the A as well for an application that needs it=
?<br /><br />&nbsp;On 2022-02-07 14:40, &Aacute;ngel wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
On 2022-02-07 at 02:30 +0000, Klaus Frank wrote:
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">Why? Such a query would resolve in the mailserver woul=
d make the DNS <br />lookup. The DNS64 server than would synthetically add =
an AAAA-RR to<br />the response.</blockquote>
<br />The issue is not that the response contains an A record but that the<=
br />queried domain embeds the remote IP.<br /><br />The A result is usuall=
y a 127.0.0.x address, with some "magic" meaning<br />(perhaps lost if tran=
slated into IPv6) but the main problem is querying<br />the right label.<br=
 /><br />_______________________________________________<br />spfbis mailin=
g list<br /><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.org</a><br /><a =
href=3D"https://www.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=
=3D"noopener noreferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></=
div>
</blockquote>
</body></html>

--=_b4f0b268ce40528b133c0d5a6febf659--


From nobody Mon Feb  7 15:30:48 2022
Return-Path: <william@leibzon.org>
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 0BF593A0EE6 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 T0gG6SbvgoOe for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:30:42 -0800 (PST)
Received: from relay4.hostedemail.com (relay4.hostedemail.com [64.99.140.37]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AD8B3A0EEC for <spfbis@ietf.org>; Mon,  7 Feb 2022 15:30:42 -0800 (PST)
Received: from omf09.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay11.hostedemail.com (Postfix) with ESMTP id 6582B8105C; Mon,  7 Feb 2022 23:30:41 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: william@leibzon.org) by omf09.hostedemail.com (Postfix) with ESMTPA id F3D592002C;  Mon,  7 Feb 2022 23:30:40 +0000 (UTC)
MIME-Version: 1.0
Date: Mon, 07 Feb 2022 15:30:40 -0800
From: william@leibzon.org
To: =?UTF-8?Q?=C3=81ngel?= <angel@16bits.net>
Cc: spfbis@ietf.org
In-Reply-To: <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca> <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de> <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net> <e0f53dcc-a909-9476-691b-84184ba8761c@posteo.de> <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net>
Message-ID: <edc7c66c73c6743078691078d973e08b@leibzon.org>
X-Sender: william@leibzon.org
Content-Type: multipart/alternative; boundary="=_f10f6a7290bbfd4a7032970ea67379a3"
X-Stat-Signature: a5atmhnieca3fndtrf5aqndo6sxf4cka
X-Rspamd-Server: rspamout04
X-Rspamd-Queue-Id: F3D592002C
X-Session-Marker: 77696C6C69616D406C6569627A6F6E2E6F7267
X-Session-ID: U2FsdGVkX19sI53EeBW3DqUDrf849b34mcH/ECg/pNY=
X-HE-Tag: 1644276640-747523
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/WI8gakr9Ox6p53I_DwAjFlpd8XA>
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 23:30:47 -0000

--=_f10f6a7290bbfd4a7032970ea67379a3
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8;
 format=flowed



SPF macro tricks: 
https://www.jamieweb.net/blog/using-spf-macros-to-solve-the-operational-challenges-of-spf/
I wonder how many people actually use SPF macros....

But yeah, trying to translate these is the kind of hell that should be 
reserved for full SPF library and not something DNS64 server should 
probably attempt. Looks like those who want SPF to work behind NAT64 
would have to use a library that can discovery what NAT64 prefix is and 
translate everything.

BTW, what's going on with exists and A vs AAAA? The SPF 7206 RFC says:

exists           = "exists"   ":" domain-spec

    The <domain-spec> is expanded as per Section 7 [1].  The resulting 
domain
    name is used for a DNS A RR lookup (even when the connection type is
    IPv6).  If any A record is returned, this mechanism matches."

How is this meant to work for those in IPv6 only world? And what will 
happen when a SPF resolver behind DNS64 tries to resolve this? Is DNS64 
just adding AAAA while preserving the A as well for an application that 
needs it?

On 2022-02-07 14:40, Ángel wrote:

> On 2022-02-07 at 02:30 +0000, Klaus Frank wrote:
> 
>> Why? Such a query would resolve in the mailserver would make the DNS
>> lookup. The DNS64 server than would synthetically add an AAAA-RR to
>> the response.
> 
> The issue is not that the response contains an A record but that the
> queried domain embeds the remote IP.
> 
> The A result is usually a 127.0.0.x address, with some "magic" meaning
> (perhaps lost if translated into IPv6) but the main problem is querying
> the right label.
> 
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis


Links:
------
[1] https://datatracker.ietf.org/doc/html/rfc7208#section-7
--=_f10f6a7290bbfd4a7032970ea67379a3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p><br />SPF macro tricks: https://www.jamieweb.net/blog/using-spf-macros-t=
o-solve-the-operational-challenges-of-spf/<br />I wonder how many people ac=
tually use SPF macros....</p>
<div id=3D"v1signature"></div>
<p>But yeah, trying to translate these is the kind of hell that should be r=
eserved for full SPF library and not something DNS64 server should probably=
 attempt. Looks like those who want SPF to work behind NAT64 would have to =
use a library that can discovery what NAT64 prefix is and translate everyth=
ing.<br /><br />BTW, what's going on with exists and A vs AAAA? The SPF 720=
6 RFC says:</p>
<pre class=3D"v1newpage">exists           =3D "exists"   ":" domain-spec

   The &lt;domain-spec&gt; is expanded as per <a href=3D"https://datatracke=
r.ietf.org/doc/html/rfc7208#section-7" target=3D"_blank" rel=3D"noopener no=
referrer">Section 7</a>.  The resulting domain
   name is used for a DNS A RR lookup (even when the connection type is
   IPv6).  If any A record is returned, this mechanism matches."
</pre>
<p>How is this meant to work for those in IPv6 only world? And what will ha=
ppen when a SPF resolver behind DNS64 tries to resolve this? Is DNS64 just =
adding AAAA while preserving the A as well for an application that needs it=
?</p>
<div id=3D"signature"></div>
<p id=3D"reply-intro">On 2022-02-07 14:40, &Aacute;ngel wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
On 2022-02-07 at 02:30 +0000, Klaus Frank wrote:
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">Why? Such a query would resolve in the mailserver woul=
d make the DNS <br />lookup. The DNS64 server than would synthetically add =
an AAAA-RR to<br />the response.</blockquote>
<br />The issue is not that the response contains an A record but that the<=
br />queried domain embeds the remote IP.<br /><br />The A result is usuall=
y a 127.0.0.x address, with some "magic" meaning<br />(perhaps lost if tran=
slated into IPv6) but the main problem is querying<br />the right label.<br=
 /><br />_______________________________________________<br />spfbis mailin=
g list<br /><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.org</a><br /><a =
href=3D"https://www.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=
=3D"noopener noreferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></=
div>
</blockquote>
</body></html>

--=_f10f6a7290bbfd4a7032970ea67379a3--


From nobody Mon Feb  7 15:32:09 2022
Return-Path: <klaus.frank@posteo.de>
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 D78703A0EF2 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:32:06 -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 o8JPInoaeaVf for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:32:02 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 AAFF23A0EEC for <spfbis@ietf.org>; Mon,  7 Feb 2022 15:32:01 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id 9AF92240106 for <spfbis@ietf.org>; Tue,  8 Feb 2022 00:31:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644276717; bh=eu5bQHH2cCUQp6KVnIzhlp1qNUXbC+m2yYFb/LSQPPI=; h=Date:Subject:To:From:From; b=UAbw/qe5BzXS2jUl4JRqp3wzBGy0/AY2zekZA57uhW4A5PVp+IeV1KSCLTlmoAsHR XiuJQiOjHjzf7W0fxZ5FSsaXnayvv0luzYaTypAnTvcMCcIixdH6pm+f53jrVcJhO0 AVuG+nJdZ6sqvAXScr4xtrw78DDSrtEh1YTlh9ZNlMUYQqcM1ABHzPPOj7oD4iawBB lea5lrnmUAaucssL/queKe8mSXejHLnH8S1Y3bXpJj8PHJ0YbQ8vVVLFIz2lMyLOYX 7jFsO/7vIm7cuCK0Pc0YFmWFosLZsypXT1axqh8Yda7j6apxTGSdC+5AEbMH9yCFqH Ie2g1hU8HtweQ==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Jt2V44j5rz9rxF for <spfbis@ietf.org>; Tue,  8 Feb 2022 00:31:56 +0100 (CET)
Message-ID: <3f9e531c-3b78-2c9d-3776-bf2ab297dead@posteo.de>
Date: Mon,  7 Feb 2022 23:31:55 +0000
MIME-Version: 1.0
Content-Language: en-US
To: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca> <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de> <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net> <e0f53dcc-a909-9476-691b-84184ba8761c@posteo.de> <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net> <1fc6a0d819c1872624dcae1e15af0384@leibzon.org>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <1fc6a0d819c1872624dcae1e15af0384@leibzon.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms080205050909090803090101"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/vpZ0Qu1nDMKnxyTr123y9pAJM1c>
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 23:32:07 -0000

This is a cryptographically signed message in MIME format.

--------------ms080205050909090803090101
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit


On 2022-02-08 00:22, william@leibzon.org wrote:
>
> SPF macro tricks: 
> https://www.jamieweb.net/blog/using-spf-macros-to-solve-the-operational-challenges-of-spf/
> I wonder how many people actually use SPF macros....
>
We don't have to. This is all done by the SPF library and we just need 
to care about the DNS requests it'll perform because of this. The new 
dns queries are also SPF records. And also start with "v=spf1 ", so no 
problems as long as we'd rewrite all ip4's within it and that's the same 
as we'd already do anyway. Therefore no change to macros needed.
>
> But yeah, trying to translate these is the kind of hell that should be 
> reserved for full SPF library and not something DNS64 server should 
> probably attempt. Looks like those who want SPF to work behind NAT64 
> would have to use a library that can discovery what NAT64 prefix is 
> and translate everything.
>
> BTW, what's going on with exists and A vs AAAA? The SPF 7206 RFC says:
>
> exists           = "exists"   ":" domain-spec
>
>     The <domain-spec> is expanded as perSection 7  <https://datatracker.ietf.org/doc/html/rfc7208#section-7>.  The resulting domain
>     name is used for a DNS A RR lookup (even when the connection type is
>     IPv6).  If any A record is returned, this mechanism matches."
>
> How is this meant to work for those in IPv6 only world? And what will 
> happen when a SPF resolver behind DNS64 tries to resolve this? Is 
> DNS64 just adding AAAA while preserving the A as well for an 
> application that needs it?
>
IPv4 records are preserved. But yea, it was already noted in the 
discussion that that part is a minor problematic.

Here is a DNS64 resolver from cloudflare if you want to try it yourself: 
2606:4700:4700::64

>  On 2022-02-07 14:40, Ángel wrote:
>
>> On 2022-02-07 at 02:30 +0000, Klaus Frank wrote:
>>> Why? Such a query would resolve in the mailserver would make the DNS
>>> lookup. The DNS64 server than would synthetically add an AAAA-RR to
>>> the response.
>>
>> The issue is not that the response contains an A record but that the
>> queried domain embeds the remote IP.
>>
>> The A result is usually a 127.0.0.x address, with some "magic" meaning
>> (perhaps lost if translated into IPv6) but the main problem is querying
>> the right label.
>>
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis
>
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms080205050909090803090101
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDcyMzMxNTVaME8GCSqGSIb3DQEJBDFCBEAJCkRfMPTM58SI7I3ZkTTa
BSj7MQYohkz8FoS20EuP5kkul5lzoP0Si1WCo1uLhvN2niu2pErKlA8UaWC+WKntMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICAHrwjFDk
l6O16FAQvZ92rQmcr/La/ZUwvyxPC1OKDynGKjvv19Ihqq56i8HW7hhtmePTn/avrDwk8KME
T0BpgmIWHl9Sy7Un6cmzs3s6MYaAATDP+PXwZ+x56RiOzDZirhDD3vJXldROc/lhlf6SWnrD
Sx4R2EcOdYlYNxMGizyk2ZQVjHq4TRrRMUstqspHI6EATCtOPd2r2zn9mD2yiwUJf6Sh4LaG
63mS7SW8KWgOIR8gbSC1oxcL4U3yYD2qNt0T7gGquVyM6NJfJ3HOuhpo+HEv1XWIbaqT7Ino
/JMmndpw7OJbZJHoPGw1TgS7pkLBVKTo+oXKVBCpxWBGehksqctvLJMWiie9s7kgwEMPu4hZ
kyfG3BDTZjOx5COb3zkSy9ff+fQTZZ8lMBB//J/hbhYHhVwrpOq0qVecx5Wz5MqCSuQyS5fz
QgINyJmB64aP6ZsiaGIEfCa8KhiFO/hsmXBMAsJCgN4tAf1wTMB/pvfMaQ/a0t01CddFUDUl
kvkozvWQ+4jlib2TKLZ5U2cA0gr6ZnApmKzUlHicPEErXQ6KnzysDryp+PFs+R0zBO6bGNze
DzYEZxjw0WzW7myvO+Lpik3xVkNk/mekzm1fgyPQknRHphX6DPqh/Q6oMFAlD6navUDxTFbG
1wc5lrLKAGOtGpVdyue+KSClBjRDAAAAAAAA
--------------ms080205050909090803090101--


From nobody Mon Feb  7 15:36:01 2022
Return-Path: <spf2@kitterman.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 9F6663A1010 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=OSHQXBOj; dkim=pass (2048-bit key) header.d=kitterman.com header.b=Rnwyrcle
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 fb3QBGvXk3a4 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:35:54 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70FE73A100E for <spfbis@ietf.org>; Mon,  7 Feb 2022 15:35:54 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 9B5C3F802ED for <spfbis@ietf.org>; Mon,  7 Feb 2022 18:35:47 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1644276947; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=4/Dwl/ytxawZH47YS5qwfNSUy/7ZigWqx4LWTnJ3Vwk=; b=OSHQXBOj0i9Rb5BhKpeKaW4cWX9HcR0/F3Glhchx4dkFGPSPEgUNfx7IF3H6DHPUYIzut rvALbAqVO7BdnU8CA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1644276947; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=4/Dwl/ytxawZH47YS5qwfNSUy/7ZigWqx4LWTnJ3Vwk=; b=RnwyrclerC94VjRAc05wbashKRYwD8tIqO0GkMZDcybT/tNXvkJU+97kl5tumMOhMXtYl 4CE/0pOhH58BY9qEpEEtvPphH4NLBEV3pTa0HylFMgO8P+5CMvhw5UQDJTJprDH4pTPYSqZ BSxI1kPBHCSQlSq5rpXwYdjXqtxHHvIaCHY8P3bylHIpNnV2ds5vLFc4LxfTxr70NPlJrIz d1fgf8FQYtB9lkAK3+eOi65x9jQ7wpBt/YjGCax0xlRIi2DWCFpGBVgYc/sWePT/TM2R2Ra te7y+HHJGTYqgq3Dm/xMTYzzINNjTQqt20Xpzil2HTMh+r89XUonRg4a5Fkw==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 6A1A9F802DE for <spfbis@ietf.org>; Mon,  7 Feb 2022 18:35:47 -0500 (EST)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Mon, 07 Feb 2022 18:35:47 -0500
Message-ID: <10214311.ZiOWkujHqK@localhost>
In-Reply-To: <1fc6a0d819c1872624dcae1e15af0384@leibzon.org>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net> <1fc6a0d819c1872624dcae1e15af0384@leibzon.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/IDlDViLDOl1-VoktnsPo2TUOlJg>
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 23:36:00 -0000

As far as I can tell, not very many people use them, but there were enough=
=20
that the SPFbis working group concluded they were in use and could not be=20
removed.

I'm working from several year old memories, but my recollection is that sin=
ce=20
the DNS server receiving the query has controls how to respond, it can resp=
ond=20
just fine to an A query, even if via IPv6.  This should work until IPv4 is =
dead=20
enough that people start ripping the ability to query for A records out of =
DNS=20
servers (or the heat death of the universe, whichever comes first).

Scott K

On Monday, February 7, 2022 6:22:13 PM EST william@leibzon.org wrote:
> SPF macro tricks:
> https://www.jamieweb.net/blog/using-spf-macros-to-solve-the-operational-c=
hal
> lenges-of-spf/ I wonder how many people actually use SPF macros....
>=20
> But yeah, trying to translate these is the kind of hell that should be
> reserved for full SPF library and not something DNS64 server should
> probably attempt. Looks like those who want SPF to work behind NAT64
> would have to use a library that can discovery what NAT64 prefix is and
> translate everything.
>=20
> BTW, what's going on with exists and A vs AAAA? The SPF 7208 RFC says:
>=20
> exists           =3D "exists"   ":" domain-spec
>=20
>     The <domain-spec> is expanded as per Section 7 [1].  The resulting
> domain
>     name is used for a DNS A RR lookup (even when the connection type is
>     IPv6).  If any A record is returned, this mechanism matches."
>=20
> How is this meant to work for those in IPv6 only world? And what will
> happen when a SPF resolver behind DNS64 tries to resolve this? Is DNS64
> just adding AAAA while preserving the A as well for an application that
> needs it?
>=20
>   On 2022-02-07 14:40, =C1ngel wrote:
> > On 2022-02-07 at 02:30 +0000, Klaus Frank wrote:
> >> Why? Such a query would resolve in the mailserver would make the DNS
> >> lookup. The DNS64 server than would synthetically add an AAAA-RR to
> >> the response.
> >=20
> > The issue is not that the response contains an A record but that the
> > queried domain embeds the remote IP.
> >=20
> > The A result is usually a 127.0.0.x address, with some "magic" meaning
> > (perhaps lost if translated into IPv6) but the main problem is querying
> > the right label.
> >=20
> > _______________________________________________
> > spfbis mailing list
> > spfbis@ietf.org
> > https://www.ietf.org/mailman/listinfo/spfbis
>=20
> Links:
> ------
> [1] https://datatracker.ietf.org/doc/html/rfc7208#section-7





From nobody Mon Feb  7 15:57:47 2022
Return-Path: <marka@isc.org>
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 1D7E13A0BD6 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=isc.org header.b=PZbxywSA; dkim=pass (1024-bit key) header.d=isc.org header.b=XxWC3hnP
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 5qdUv9m3bQ_0 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 15:57:41 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B0543A105C for <spfbis@ietf.org>; Mon,  7 Feb 2022 15:57:37 -0800 (PST)
Received: from zimbrang.isc.org (zimbrang.isc.org [149.20.1.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id 9143C3AB006; Mon,  7 Feb 2022 23:57:36 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 mx.pao1.isc.org 9143C3AB006
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=isc.org; s=ostpay; t=1644278256; bh=Li+W5Ni90WfLeQksal1slVt+rO7lfA71ZS0e2yHKnxE=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=PZbxywSAdglFEUaErs9BPEdcVgDxUrZHJcOQL+P0+2yWaBfbixNHM1oYAtEKCEb0A fKSQEKDOkULEp2VrFQhFESPolzi7itl9Z+Vlh7vAXovoBL6PDqC4O0NEOb9sgTMpmo FBWBxgic1VJPDWfqtCE9n8TnmVENC4ViIhJZCw+I=
Received: from zimbrang.isc.org (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTPS id 80743FE5AE0; Mon,  7 Feb 2022 23:57:36 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTP id 5095BFE5AE4; Mon,  7 Feb 2022 23:57:36 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbrang.isc.org 5095BFE5AE4
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1644278256; bh=1LqMpFLVCrpiWY5fEzF4iT8235PjjZOvBtjmeSJgxqg=; h=Mime-Version:From:Date:Message-Id:To; b=XxWC3hnPXv/9tgbYfZovoqi2d2MOrtlql57iqZg5UkYf5wqn6++HYsSnom9SV38At 41J87witIDAZ8a4Qs7v9byjCXS0AxYkHZ+900JDu6fRMFpW5siG0fzC/DA2OnuTLi+ l1OLnMugvEYcAlkL9fKF2jsjnZdwOJXbdoFeQshY=
Received: from zimbrang.isc.org ([127.0.0.1]) by localhost (zimbrang.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id uMHrZM1XKmTR; Mon,  7 Feb 2022 23:57:36 +0000 (UTC)
Received: from smtpclient.apple (n114-74-26-107.bla4.nsw.optusnet.com.au [114.74.26.107]) by zimbrang.isc.org (Postfix) with ESMTPSA id A161FFE5AE0; Mon,  7 Feb 2022 23:57:35 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <8d7a6274-8546-3145-17e3-c20c29d6df2e@posteo.de>
Date: Tue, 8 Feb 2022 10:57:32 +1100
Cc: spfbis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <997A20D6-2C1F-4EE6-89E1-F8A595446941@isc.org>
References: <20220206221619.53E4836687AF@ary.qy> <2244581.DCeBYFrMaS@localhost> <8d7a6274-8546-3145-17e3-c20c29d6df2e@posteo.de>
To: Klaus Frank <klaus.frank@posteo.de>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/3Cgp1cpXjijUnKNwByUEE3ayapU>
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 23:57:46 -0000

> On 8 Feb 2022, at 02:19, Klaus Frank <klaus.frank@posteo.de> wrote:
>=20
> On 2022-02-07 15:28, Scott Kitterman wrote:
>> On Sunday, February 6, 2022 5:16:18 PM EST John Levine wrote:
>>> It appears that Scott Kitterman  <spf2@kitterman.com> said:
>>>> It looks like situations like this one were contemplated by the RFC =
6147
>>>>=20
>>>> authors:
>>>>> 6.  Deployment Notes
>>>>>=20
>>>>>    While DNS64 is intended to be part of a strategy for aiding =
IPv6
>>>>>    deployment in an internetworking environment with some =
IPv4-only and
>>>>>    IPv6-only networks, it is important to realize that it is
>>>>>    incompatible with some things that may be deployed in an =
IPv4-only or
>>>>>    dual-stack context.
>>>> On the SPF side of the discussion, I think it would, at least in =
theory, be
>>>> feasible to interpret an ip4: mechanism as <prefix> + <address> if =
the
>>>> connection is IPv6, but I don't see how a receiving SPF processor =
could
>>>> know what the prefix is.  As I read RFC 6147 Section 5.2, it could =
be
>>>> anything.
>>> See RFCs 7050 and 8880 for how you find the prefix(es).
>>>=20
>>> That seems like a more reasonable way to go, patch the SPF library =
so it
>>> can use the NAT's Pref64 to fudge the interpretation of ip4 and ptr.
>>>=20
>>> It looks like you could automate the entire thing -- when the =
library starts
>>> up, do an AAAA query on ipv4only.arpa, and if you get plausible =
answers,
>>> you know you're behind NAT64 and reinterpret ip4 and ptr terms
>>> appropriately.
>> Thanks.
>>=20
>> Reading RFC 7050, it looks like ipv4only.arpa can return more than =
one name.
>> That would seem to be a complication if I'm reading it correctly.
>>=20
>> As a practical matter, it probably doesn't matter, but RFC 7050 =
doesn't update
>> RFC 6147, so in theory other prefix determination methods could be =
used.
>>=20
>> I guess the ::ffff:0:0/96 (IPv4-mapped Address) prefix should be =
considered
>> similarly.
> Oh yes, for sure good that you remind me of this one. We had one =
mailserver application (proprietary) that once we changed the binding =
from "0.0.0.0:25" to "[::]:25" on a linux system got everything as =
::ffff:0:0/96 and SPF validation also failed. But I'm not sure if that =
was an implementation simplification on their end or a OS dependent =
behavior of when binding a socket... The workaround we got was to "just =
deploy another VM for IPv6 and put them behind the same public DNS name. =
One for IPv4 and another one for the IPv6"

One could have just set IPV6_V6ONLY=3D1 at the system level (sysctl =
net.ipv6.bindv6only=3D1) or prior to bind(2)
on the individual sockets if you don=E2=80=99t want mapped connections.  =
IPV6_V6ONLY is described in RFC 2535, Basic
Socket Interface Extensions for IPv6 (February 2003) and is in also in =
POSIX as of 2008.  Alternatively SPF
libraries could just learn about mapped connections and apply IPv4 rules =
against them.

>> Is there enough here that it would be worth an Applicability =
Statement?
>>=20
>> Scott K
>>=20
>>=20
>>=20
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Mon Feb  7 16:09:24 2022
Return-Path: <klaus.frank@posteo.de>
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 4D53B3A1084 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 16:09:22 -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 p79BR7UVrT8N for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 16:09:17 -0800 (PST)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 404F83A1075 for <spfbis@ietf.org>; Mon,  7 Feb 2022 16:09:16 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169])  by mout02.posteo.de (Postfix) with ESMTPS id 53B1F240101 for <spfbis@ietf.org>; Tue,  8 Feb 2022 01:09:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644278954; bh=FtPXNxuppjkF+RZE5y6sgOLPYjLS9nNbU/ExowqE1NQ=; h=Date:Subject:To:Cc:From:From; b=FYXpJ4cBUZICoUqCmgWYiWCs/ZHverYAmPDEGgP89AthfRdxyuOvzKyjifyXUugSG SDd7XKQg1w60bTmVS7Du1KBEdgOJk8vo/MFrXFcKA1gjyvZCJw0uOU258lZ8ZwmNwp fUwjMRYs34QIuuJzzO+GMDrNFP/F00l0qt7zsFAm7A+D2vic8dMQ+cXBi41kyNbYRc TWKiEtQuGP41mGskBR+z9puG38MxeUIJFObQsrh2kTEw3Fm3C86WVYv6z/+G+S1Nzo YeybE/KY2qupGHrIV/QXAariFG93LNYSs6wXt8uTUFCsI0KiiwiHFltlOs9SjRNdbX hRbptwA6fO10A==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Jt3K513H9z9rxF; Tue,  8 Feb 2022 01:09:12 +0100 (CET)
Message-ID: <411a41fe-ff2d-5fa8-d2d1-68706b57c838@posteo.de>
Date: Tue,  8 Feb 2022 00:09:12 +0000
MIME-Version: 1.0
Content-Language: en-US
To: Mark Andrews <marka@isc.org>
Cc: spfbis@ietf.org
References: <20220206221619.53E4836687AF@ary.qy> <2244581.DCeBYFrMaS@localhost> <8d7a6274-8546-3145-17e3-c20c29d6df2e@posteo.de> <997A20D6-2C1F-4EE6-89E1-F8A595446941@isc.org>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <997A20D6-2C1F-4EE6-89E1-F8A595446941@isc.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms060302010708050804000105"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/c3IwXPN4lDIKdwVWRqtj4v50Yss>
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: Tue, 08 Feb 2022 00:09:22 -0000

This is a cryptographically signed message in MIME format.

--------------ms060302010708050804000105
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit


On 2022-02-08 00:57, Mark Andrews wrote:
>
>> On 8 Feb 2022, at 02:19, Klaus Frank <klaus.frank@posteo.de> wrote:
>>
>> On 2022-02-07 15:28, Scott Kitterman wrote:
>>> On Sunday, February 6, 2022 5:16:18 PM EST John Levine wrote:
>>>> It appears that Scott Kitterman  <spf2@kitterman.com> said:
>>>>> It looks like situations like this one were contemplated by the RFC 6147
>>>>>
>>>>> authors:
>>>>>> 6.  Deployment Notes
>>>>>>
>>>>>>     While DNS64 is intended to be part of a strategy for aiding IPv6
>>>>>>     deployment in an internetworking environment with some IPv4-only and
>>>>>>     IPv6-only networks, it is important to realize that it is
>>>>>>     incompatible with some things that may be deployed in an IPv4-only or
>>>>>>     dual-stack context.
>>>>> On the SPF side of the discussion, I think it would, at least in theory, be
>>>>> feasible to interpret an ip4: mechanism as <prefix> + <address> if the
>>>>> connection is IPv6, but I don't see how a receiving SPF processor could
>>>>> know what the prefix is.  As I read RFC 6147 Section 5.2, it could be
>>>>> anything.
>>>> See RFCs 7050 and 8880 for how you find the prefix(es).
>>>>
>>>> That seems like a more reasonable way to go, patch the SPF library so it
>>>> can use the NAT's Pref64 to fudge the interpretation of ip4 and ptr.
>>>>
>>>> It looks like you could automate the entire thing -- when the library starts
>>>> up, do an AAAA query on ipv4only.arpa, and if you get plausible answers,
>>>> you know you're behind NAT64 and reinterpret ip4 and ptr terms
>>>> appropriately.
>>> Thanks.
>>>
>>> Reading RFC 7050, it looks like ipv4only.arpa can return more than one name.
>>> That would seem to be a complication if I'm reading it correctly.
>>>
>>> As a practical matter, it probably doesn't matter, but RFC 7050 doesn't update
>>> RFC 6147, so in theory other prefix determination methods could be used.
>>>
>>> I guess the ::ffff:0:0/96 (IPv4-mapped Address) prefix should be considered
>>> similarly.
>> Oh yes, for sure good that you remind me of this one. We had one mailserver application (proprietary) that once we changed the binding from "0.0.0.0:25" to "[::]:25" on a linux system got everything as ::ffff:0:0/96 and SPF validation also failed. But I'm not sure if that was an implementation simplification on their end or a OS dependent behavior of when binding a socket... The workaround we got was to "just deploy another VM for IPv6 and put them behind the same public DNS name. One for IPv4 and another one for the IPv6"
> One could have just set IPV6_V6ONLY=1 at the system level (sysctl net.ipv6.bindv6only=1) or prior to bind(2)
> on the individual sockets if you don’t want mapped connections.  IPV6_V6ONLY is described in RFC 2535, Basic
> Socket Interface Extensions for IPv6 (February 2003) and is in also in POSIX as of 2008.  Alternatively SPF
> libraries could just learn about mapped connections and apply IPv4 rules against them.

Thanks for the hint. I know that that existed, but didn't know how to 
configure it or what exactly causes it.

Also I just re-read the SPF record RFC, and it indeed should already 
cover IPv4-mapped IPv6. So strictly speaking that's a violation of the 
RFC and therefore an implementation bug...

    When any mechanism fetches host addresses to compare with <ip>, when
    <ip> is an IPv4, "A" records are fetched; when <ip> is an IPv6
    address, "AAAA" records are fetched.  SPF implementations on IPv6
    servers *need to handle both "AAAA" and "A" records, for clients on**
**   IPv4-mapped IPv6 addresses *[RFC4291].  IPv4 <ip> addresses are only
    listed in an SPF record using the "ip4" mechanism.

>>> Is there enough here that it would be worth an Applicability Statement?
>>>
>>> Scott K
>>>
>>>
>>>
>>> _______________________________________________
>>> spfbis mailing list
>>> spfbis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spfbis
>> _______________________________________________
>> spfbis mailing list
>> spfbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/spfbis

--------------ms060302010708050804000105
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC
CyAwggUNMIID9aADAgECAhB4SqkQP6W/vt51CLE0kx0AMA0GCSqGSIb3DQEBCwUAMEwxIDAe
BgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMw
EQYDVQQDEwpHbG9iYWxTaWduMB4XDTIwMDkxNjAwMDAwMFoXDTI4MDkxNjAwMDAwMFowWzEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMTAvBgNVBAMTKEdsb2Jh
bFNpZ24gR0NDIFIzIFBlcnNvbmFsU2lnbiAyIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQC9sKZcJyxtn9rR9EhAwHGniAmefJ6d4VikS03J2tln4Z4pIx0eIOBc
PVSdFIi50qj6ahDpiUI67i2tVY78SJd9icrvN6inbqvLVGkq2iAHv87XXnO6W0DPrjJ1Bgt7
5rV79zOQAuDeyBNw45wVlNeTfx5qqxeyKmhfW+w26uo+2cLbtNawDumTi4pexwWOR5QTwlm7
0EMpqzBnKDEE48FAHCsDn7bRbGWTqTV7oQppo1o1lTLfSrcCsR/fRkOlfJ8K2Jee6mNIrxZT
ZwriqwS2PT0lLj6aGLQJMKsKdcDO6be2BwdwdGDSmtxLPMRQNBagXHK6rCLCEe7ew9A2YU4z
AgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCAYYwYAYDVR0lBFkwVwYIKwYBBQUHAwIGCCsG
AQUFBwMEBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQBgjcKAwwG
CCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSWM9Hm
WBdbNHWKgVZk1b5I3qGPzzAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDB6Bggr
BgEFBQcBAQRuMGwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLmdsb2JhbHNpZ24uY29tL3Jv
b3RyMzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQv
cm9vdC1yMy5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBaBgNVHSAEUzBRMAsGCSsGAQQBoDIBKDBCBgorBgEEAaAyASgKMDQw
MgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMA0G
CSqGSIb3DQEBCwUAA4IBAQB0BeT9cKcN4A532c0RS9Y/FuU5D/mj+ro4h5Ni+gS9RSLaodQ6
1t+MEZ1Om0Wxdd7hGCNUX1voO6LOBh/L5wgua+LmF+TcirwwBmyC1b4D+i1Cwm8rbBFq0sTr
VFvORfz385cRnXNPu3+rZGImrOm9Xw0KHEiP4/tZO16k+b0AiPQp6576BLaq/MBkBjfhll5E
eADuDk7hM8n+hN37iuCJT77AsOVxlh3+yUWRpPfGDipYN6kQyNPhPWoU5Agv6KNQCthLijCk
+D00hJMprWqopYmMWjKazR3QbA6eIghsG+EjYwnsFJj0xi1ZVPmMk7e2xUfCPhyn3YJIW4bC
6cUzMIIGCzCCBPOgAwIBAgIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBCwUAMFsxCzAJBgNV
BAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTEwLwYDVQQDEyhHbG9iYWxTaWdu
IEdDQyBSMyBQZXJzb25hbFNpZ24gMiBDQSAyMDIwMB4XDTIxMDExNTIyNDMxN1oXDTIzMDUw
NzEwNDU1NVowSTELMAkGA1UEBhMCREUxFDASBgNVBAMTC0tsYXVzIEZyYW5rMSQwIgYJKoZI
hvcNAQkBFhVrbGF1cy5mcmFua0Bwb3N0ZW8uZGUwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDJynviIV8lWEwIyAH5oxm4405Hy5PyN5b+VNSk+/cNA0bWcDfiJXa+O0JXQS22
Xwhu2MomP54d34PUsoMOxtc1fMUkLAP3QPYcxtklhlrW2g8Vl1kxfNbJFSDSacCzty3VZBw0
VGABUpu2IdzRYl6W5DEZkZByOWGv7J4bKV7hbh0NaWJ4OPwOCyeb0bAenBjLj7Xv6gTjjTQu
UxXcn7HGXY6WqSmcPPaB18PRMiiCWalW4nmL0Ng+hEdos3dkPMKwIAVNI1fpbSfW0R1J6orc
dfqI8CZPbrYo75N06kzm1XNHf0CcqgjOArvffp1caTTqtcYzehvgXLlVHZ97kjNq8JMWtkgj
/4JjevLotHFylzJqmVVu/POE/nsLU0muMLPn5C3j/KOcp2CJcALbpWWDSgnmc35pKDA8gH8V
DqUVmQbxFJ0FwgnqKZDycyGRmX5piUFkXFVySAL5AMhISFy7jrvIE/B/mHhUVeVOotZIrzs6
CZik2w5dcPXZH1888GsoTqVVWt8bQtUBDYA2srN57K34CP/4rrZXJPN9z2oONenUYu33fiOw
nf3AGPjnGepE3IKbmd9wkfAnWB/qOUEKxut8kfa90Seg0ZCpFbSilYmndxibHzyFuGTlqlJG
WTYuhPEOqvGRIJmW96Cnv8F8p0LfBn0u/lYBhsdv7E4XGwIDAQABo4IB3zCCAdswDgYDVR0P
AQH/BAQDAgWgMIGjBggrBgEFBQcBAQSBljCBkzBOBggrBgEFBQcwAoZCaHR0cDovL3NlY3Vy
ZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvZ3NnY2NyM3BlcnNvbmFsc2lnbjJjYTIwMjAuY3J0
MEEGCCsGAQUFBzABhjVodHRwOi8vb2NzcC5nbG9iYWxzaWduLmNvbS9nc2djY3IzcGVyc29u
YWxzaWduMmNhMjAyMDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEkGA1Ud
HwRCMEAwPqA8oDqGOGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NnY2NyM3BlcnNvbmFs
c2lnbjJjYTIwMjAuY3JsMCAGA1UdEQQZMBeBFWtsYXVzLmZyYW5rQHBvc3Rlby5kZTAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHwYDVR0jBBgwFoAUljPR5lgXWzR1ioFWZNW+
SN6hj88wHQYDVR0OBBYEFI9o2WnL3RYlPYT5/Nll9FkTqkpDMA0GCSqGSIb3DQEBCwUAA4IB
AQBz4NRmY5rvOME2JwipWlLmF48zf7fJMFrd7B4LqS8SDSvXc5Z7Rmxl8+dOtaXSsPAd+jks
jQ4pzcWsFPM6WlpzjQzvJtV8NoqEIiOiv9Sb+jvH70Nq1zqitfkKK9GqPunPaRT8k+tHpD3J
yFV/T9XCezXPHAwnu60kcatRIMZhx713hVWimimnZH1ZEzyWaeuTBv5xmYRiyB+Q/zF6XsQW
/0hhZ+USow22bo+Wb10sORRRzLL4INJVBDxkt2bFz5doNGUjC7o41a2ukj1/G+HpXxZxtyJ4
/4Ce4QaynJJ5eDTAx1xTmttJRs5AKUCvaSYvvLzxg1sVif9f+Rv4tYWyMYIEizCCBIcCAQEw
azBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMo
R2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFU
MA0GCWCGSAFlAwQCAwUAoIIB8TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMjAyMDgwMDA5MTJaME8GCSqGSIb3DQEJBDFCBECe16cduNl4QPuSkwas7T3V
xhA7NDd7zHFgPsjllvSPfoTEU0sTNKILd6fvI0bgLuN1nOV8A20Bx3amGW/szQNIMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJ
KwYBBAGCNxAEMW0wazBbMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29uYWxTaWduIDIgQ0EgMjAyMAIM
XENzSjBANdaEAmFUMHwGCyqGSIb3DQEJEAILMW2gazBbMQswCQYDVQQGEwJCRTEZMBcGA1UE
ChMQR2xvYmFsU2lnbiBudi1zYTExMC8GA1UEAxMoR2xvYmFsU2lnbiBHQ0MgUjMgUGVyc29u
YWxTaWduIDIgQ0EgMjAyMAIMXENzSjBANdaEAmFUMA0GCSqGSIb3DQEBAQUABIICABK/zb04
UfMn500zYRSfCHJI86z5H14WPGnDSnoV36IQcovRr55kaLmstrcEGITb4e2j6CgQVxAIlpU5
0Twir6zU3ieUsRbCAYZJsvmVC4J0XwJgDjj7eenDXsQ5TAQzPNq2moGYXBv5bS8y7F7SYbXx
KTaq3aD6I3K8Kf36WEMKbBRsYdqJUNEyCMiC2q8LBusgth7joibdLghoUchE8VOutYR3zl7Y
FHnNI+LggFHkiRz/LTlbTY/+yAtWK6zU0jcJ36vS+vfgssuZAq5tz+hY6EdZciU5/0hg1tjJ
+L36XtXfEg4wt+J+okyvEut7g4idVHXx7XbabrxV8k7CFFBor1X4Vh8bQjlauus9BiwgzEKw
a5grYrdqcKB0CfFm1X46R01q+KJDOsR0sWR9YI3LKUC+665K1/5z0EqGx+jYK6Huob6kvZ7C
QTyQ3SMO84A2rxQ2wygAF1nyxp+PPt5/Hi2RcnttAimc0oY9N2ecPJ58cl8l358skS9fs7RV
lJZ+HU615OExV+YYlsLVhbHA5t3Fzl8aawMpxDuW6ZpiBsLn1vCj0nDfo961+Lj9++owyzhm
YN5FQVE94CpK8HxxXTp0427AQIqR0bfWKtv8TzHQ7AJAuHKW0t8alAozfi7mjY4f9jdDRey9
j23OdHtkuH/kJoFRTpwbE8xmcNRRAAAAAAAA
--------------ms060302010708050804000105--


From nobody Mon Feb  7 16:28:38 2022
Return-Path: <marka@isc.org>
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 463C23A0F5C for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 16:28:36 -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 (1024-bit key) header.d=isc.org header.b=VUxwDXNt; dkim=pass (1024-bit key) header.d=isc.org header.b=f0XGh8pi
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 ra8GqmZ43PuV for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 16:28:31 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C76063A10B3 for <spfbis@ietf.org>; Mon,  7 Feb 2022 16:28:27 -0800 (PST)
Received: from zimbrang.isc.org (zimbrang.isc.org [149.20.1.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id 822A23AB006; Tue,  8 Feb 2022 00:28:25 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 mx.pao1.isc.org 822A23AB006
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=isc.org; s=ostpay; t=1644280105; bh=q1Keazx95hBWyNl78qXrAm+NMD3zOa6MrA1/Nh35aKw=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=VUxwDXNt8wZxpx5l13UPs2rgWJHtt9Z1Zq36MVIWgmjHK4DX5dcrDW00iEc3mhWIQ 8lGrDUk5XQbuwDjK1PVyO4hlnWTyR0R2tZ4TDiykhfwS47czOiU7erDwhJtUZQ5G0P btGFbFscxGbGR2StIoyxzL+tc3oBvRgtICFHOpxo=
Received: from zimbrang.isc.org (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTPS id 6F900FE58BB; Tue,  8 Feb 2022 00:28:25 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTP id 40B10FE5B9F; Tue,  8 Feb 2022 00:28:25 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbrang.isc.org 40B10FE5B9F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1644280105; bh=JbPLpDY3ySuYf+wYlt8gRlGBg5egvvL9ZrRMi7xeA/k=; h=Mime-Version:From:Date:Message-Id:To; b=f0XGh8piJ7gIO+alBXnaRzvrMLYfKgY2Ky7XcoH+B9igygNz8m1gFfdcbn46mKCtf eyewnaGFIwhfNOQk4vX4soVE0PP8Sj5vSmZP2gCkC5kHG7E/ppv5Ib3IqrfApWhAM6 xF/ttLvJ9Ey3TQRDLxA1L/JA88Q7If73hFL0Qr28=
Received: from zimbrang.isc.org ([127.0.0.1]) by localhost (zimbrang.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3xhJvJIxQSec; Tue,  8 Feb 2022 00:28:25 +0000 (UTC)
Received: from smtpclient.apple (n114-74-26-107.bla4.nsw.optusnet.com.au [114.74.26.107]) by zimbrang.isc.org (Postfix) with ESMTPSA id 948CDFE58BB; Tue,  8 Feb 2022 00:28:24 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <411a41fe-ff2d-5fa8-d2d1-68706b57c838@posteo.de>
Date: Tue, 8 Feb 2022 11:28:22 +1100
Cc: spfbis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B9FE83E-DF07-4CA0-A27D-62C8172B88CD@isc.org>
References: <20220206221619.53E4836687AF@ary.qy> <2244581.DCeBYFrMaS@localhost> <8d7a6274-8546-3145-17e3-c20c29d6df2e@posteo.de> <997A20D6-2C1F-4EE6-89E1-F8A595446941@isc.org> <411a41fe-ff2d-5fa8-d2d1-68706b57c838@posteo.de>
To: Klaus Frank <klaus.frank@posteo.de>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/T9nvdylsjzM3egSw2azoY5awNR4>
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: Tue, 08 Feb 2022 00:28:36 -0000

> On 8 Feb 2022, at 11:09, Klaus Frank <klaus.frank@posteo.de> wrote:
>=20
>=20
> On 2022-02-08 00:57, Mark Andrews wrote:
>>=20
>>> On 8 Feb 2022, at 02:19, Klaus Frank <klaus.frank@posteo.de> wrote:
>>>=20
>>> On 2022-02-07 15:28, Scott Kitterman wrote:
>>>> On Sunday, February 6, 2022 5:16:18 PM EST John Levine wrote:
>>>>> It appears that Scott Kitterman  <spf2@kitterman.com> said:
>>>>>> It looks like situations like this one were contemplated by the =
RFC 6147
>>>>>>=20
>>>>>> authors:
>>>>>>> 6.  Deployment Notes
>>>>>>>=20
>>>>>>>    While DNS64 is intended to be part of a strategy for aiding =
IPv6
>>>>>>>    deployment in an internetworking environment with some =
IPv4-only and
>>>>>>>    IPv6-only networks, it is important to realize that it is
>>>>>>>    incompatible with some things that may be deployed in an =
IPv4-only or
>>>>>>>    dual-stack context.
>>>>>> On the SPF side of the discussion, I think it would, at least in =
theory, be
>>>>>> feasible to interpret an ip4: mechanism as <prefix> + <address> =
if the
>>>>>> connection is IPv6, but I don't see how a receiving SPF processor =
could
>>>>>> know what the prefix is.  As I read RFC 6147 Section 5.2, it =
could be
>>>>>> anything.
>>>>> See RFCs 7050 and 8880 for how you find the prefix(es).
>>>>>=20
>>>>> That seems like a more reasonable way to go, patch the SPF library =
so it
>>>>> can use the NAT's Pref64 to fudge the interpretation of ip4 and =
ptr.
>>>>>=20
>>>>> It looks like you could automate the entire thing -- when the =
library starts
>>>>> up, do an AAAA query on ipv4only.arpa, and if you get plausible =
answers,
>>>>> you know you're behind NAT64 and reinterpret ip4 and ptr terms
>>>>> appropriately.
>>>> Thanks.
>>>>=20
>>>> Reading RFC 7050, it looks like ipv4only.arpa can return more than =
one name.
>>>> That would seem to be a complication if I'm reading it correctly.
>>>>=20
>>>> As a practical matter, it probably doesn't matter, but RFC 7050 =
doesn't update
>>>> RFC 6147, so in theory other prefix determination methods could be =
used.
>>>>=20
>>>> I guess the ::ffff:0:0/96 (IPv4-mapped Address) prefix should be =
considered
>>>> similarly.
>>> Oh yes, for sure good that you remind me of this one. We had one =
mailserver application (proprietary) that once we changed the binding =
from "0.0.0.0:25" to "[::]:25" on a linux system got everything as =
::ffff:0:0/96 and SPF validation also failed. But I'm not sure if that =
was an implementation simplification on their end or a OS dependent =
behavior of when binding a socket... The workaround we got was to "just =
deploy another VM for IPv6 and put them behind the same public DNS name. =
One for IPv4 and another one for the IPv6"
>> One could have just set IPV6_V6ONLY=3D1 at the system level (sysctl =
net.ipv6.bindv6only=3D1) or prior to bind(2)
>> on the individual sockets if you don=E2=80=99t want mapped =
connections.  IPV6_V6ONLY is described in RFC 2535, Basic
>> Socket Interface Extensions for IPv6 (February 2003) and is in also =
in POSIX as of 2008.  Alternatively SPF
>> libraries could just learn about mapped connections and apply IPv4 =
rules against them.
>=20
> Thanks for the hint. I know that that existed, but didn't know how to =
configure it or what exactly causes it.
>=20
> Also I just re-read the SPF record RFC, and it indeed should already =
cover IPv4-mapped IPv6. So strictly speaking that's a violation of the =
RFC and therefore an implementation bug...
>=20
>    When any mechanism fetches host addresses to compare with <ip>, =
when
>    <ip> is an IPv4, "A" records are fetched; when <ip> is an IPv6
>    address, "AAAA" records are fetched.  SPF implementations on IPv6
>    servers *need to handle both "AAAA" and "A" records, for clients =
on**
> **   IPv4-mapped IPv6 addresses *[RFC4291].  IPv4 <ip> addresses are =
only
>    listed in an SPF record using the "ip4" mechanism.

The SPF libraries (or the MTAs) could also use RFC 8781, Discovering =
PREF64
in Router Advertisements.  Failing that, as has already been mentioned =
they
could use ipv6only.arpa to get the mapping.

>>>> Is there enough here that it would be worth an Applicability =
Statement?
>>>>=20
>>>> Scott K
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> spfbis mailing list
>>>> spfbis@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/spfbis
>>> _______________________________________________
>>> spfbis mailing list
>>> spfbis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spfbis

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Mon Feb  7 16:36:45 2022
Return-Path: <william@leibzon.org>
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 046EF3A1013 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 16:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 1C36bFxLSGt7 for <spfbis@ietfa.amsl.com>; Mon,  7 Feb 2022 16:36:39 -0800 (PST)
Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7329E3A100D for <spfbis@ietf.org>; Mon,  7 Feb 2022 16:36:39 -0800 (PST)
Received: from omf10.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 46E1D2085E; Tue,  8 Feb 2022 00:36:38 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: william@leibzon.org) by omf10.hostedemail.com (Postfix) with ESMTPA id E166B3E;  Tue,  8 Feb 2022 00:36:31 +0000 (UTC)
MIME-Version: 1.0
Date: Mon, 07 Feb 2022 16:36:31 -0800
From: william@leibzon.org
To: Klaus Frank <klaus.frank@posteo.de>
Cc: spfbis@ietf.org
In-Reply-To: <3f9e531c-3b78-2c9d-3776-bf2ab297dead@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca> <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de> <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net> <e0f53dcc-a909-9476-691b-84184ba8761c@posteo.de> <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net> <1fc6a0d819c1872624dcae1e15af0384@leibzon.org> <3f9e531c-3b78-2c9d-3776-bf2ab297dead@posteo.de>
Message-ID: <20716dc8319f4d931e2346a24ccb4440@leibzon.org>
X-Sender: william@leibzon.org
Content-Type: multipart/alternative; boundary="=_62e2e97d3957bf21771e039665d6c4a6"
X-Stat-Signature: 77hpfiukoerbdypxjazrtg7mpi49giic
X-Rspamd-Server: rspamout04
X-Rspamd-Queue-Id: E166B3E
X-Session-Marker: 77696C6C69616D406C6569627A6F6E2E6F7267
X-Session-ID: U2FsdGVkX1+gt4mB5hiDpuc1nnvY7Wp0BQXslGlX/Zo=
X-HE-Tag: 1644280591-438342
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/9T3BRY-555cujPvpCCqeW-1C1cE>
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: Tue, 08 Feb 2022 00:36:44 -0000

--=_62e2e97d3957bf21771e039665d6c4a6
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8;
 format=flowed



On 2022-02-07 15:31, Klaus Frank wrote:

> On 2022-02-08 00:22, william@leibzon.org wrote:
> 
>> SPF macro tricks: 
>> https://www.jamieweb.net/blog/using-spf-macros-to-solve-the-operational-challenges-of-spf/
>> I wonder how many people actually use SPF macros....
> We don't have to. This is all done by the SPF library and we just need 
> to care about the DNS requests it'll perform because of this. The new 
> dns queries are also SPF records. And also start with "v=spf1 ", so no 
> problems as long as we'd rewrite all ip4's within it and that's the 
> same as we'd already do anyway. Therefore no change to macros needed.

The macros don't need to be changed if the library knows real IPv4 
address. Otherwise there would be an issue with:

%{ir}.%{v}._spf.%{d2}
       3.2.0.192.in-addr._spf.example.com

which when an ip address of connecting server is IPv6 is translated as:

%{ir}.%{v}._spf.%{d2}
        
1.0.b.c.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6._spf.example.com

I wonder if there even are people doing ip6 exist macros... More likely 
people forgot about this if they are ip4, ip6 dual stack.

>> But yeah, trying to translate these is the kind of hell that should be 
>> reserved for full SPF library and not something DNS64 server should 
>> probably attempt. Looks like those who want SPF to work behind NAT64 
>> would have to use a library that can discovery what NAT64 prefix is 
>> and translate everything.
>> 
>> BTW, what's going on with exists and A vs AAAA? The SPF 7206 RFC says:
>> 
>> exists           = "exists"   ":" domain-spec
>> 
>> The <domain-spec> is expanded as perSection 7  
>> <https://datatracker.ietf.org/doc/html/rfc7208#section-7>.  The 
>> resulting domain
>> name is used for a DNS A RR lookup (even when the connection type is
>> IPv6).  If any A record is returned, this mechanism matches."
>> 
>> How is this meant to work for those in IPv6 only world? And what will 
>> happen when a SPF resolver behind DNS64 tries to resolve this? Is 
>> DNS64 just adding AAAA while preserving the A as well for an 
>> application that needs it?
> IPv4 records are preserved. But yea, it was already noted in the 
> discussion that that part is a minor problematic.
> 
> Here is a DNS64 resolver from cloudflare if you want to try it 
> yourself: 2606:4700:4700::64
> 
> On 2022-02-07 14:40, Ángel wrote:
> 
> On 2022-02-07 at 02:30 +0000, Klaus Frank wrote: Why? Such a query 
> would resolve in the mailserver would make the DNS
> lookup. The DNS64 server than would synthetically add an AAAA-RR to
> the response.
> The issue is not that the response contains an A record but that the
> queried domain embeds the remote IP.
> 
> The A result is usually a 127.0.0.x address, with some "magic" meaning
> (perhaps lost if translated into IPv6) but the main problem is querying
> the right label.
> 
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

_______________________________________________
spfbis mailing list
spfbis@ietf.org
https://www.ietf.org/mailman/listinfo/spfbis
_______________________________________________
spfbis mailing list
spfbis@ietf.org
https://www.ietf.org/mailman/listinfo/spfbis
--=_62e2e97d3957bf21771e039665d6c4a6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<div id=3D"signature"></div>
<p id=3D"reply-intro">On 2022-02-07 15:31, Klaus Frank wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
<br /><span style=3D"white-space: nowrap;">On&nbsp;2022-02-08&nbsp;00:22,&n=
bsp;<a href=3D"mailto:william@leibzon.org">william@leibzon.org</a>&nbsp;wro=
te:</span>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><br />SPF macro tricks: <a href=3D"https://www.jamiewe=
b.net/blog/using-spf-macros-to-solve-the-operational-challenges-of-spf/" ta=
rget=3D"_blank" rel=3D"noopener noreferrer">https://www.jamieweb.net/blog/u=
sing-spf-macros-to-solve-the-operational-challenges-of-spf/</a><br /><span =
style=3D"white-space: nowrap;">I&nbsp;wonder&nbsp;how&nbsp;many&nbsp;people=
&nbsp;actually&nbsp;use&nbsp;SPF&nbsp;macros....</span><br /><br /></blockq=
uote>
We don't have to. This is all done by the SPF library and we just need to c=
are about the DNS requests it'll perform because of this. The new dns queri=
es are also SPF records. And also start with "v=3Dspf1 ", so no problems as=
 long as we'd rewrite all ip4's within it and that's the same as we'd alrea=
dy do anyway. Therefore no change to macros needed.</div>
</blockquote>
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
&nbsp;</div>
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
The macros don't need to be changed if the library knows real IPv4 address.=
 Otherwise there would be an issue with:<br /><br />
<pre class=3D"newpage">%{ir}.%{v}._spf.%{d2}
      3.2.0.192.in-addr._spf.example.com
</pre>
<p><br />which when an ip address of connecting server is IPv6 is translate=
d as:<br /><br /></p>
<pre class=3D"newpage">%{ir}.%{v}._spf.%{d2}                               =
<br />       1.0.b.c.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.=
2.ip6._spf.example.com</pre>
<p><br />I wonder if there even are people doing ip6 exist macros... More l=
ikely people forgot about this if they are ip4, ip6 dual stack.</p>
</div>
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
&nbsp;</div>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><br />But yeah, trying to translate these is the kind =
of hell that should be reserved for full SPF library and not something DNS6=
4 server should probably attempt. Looks like those who want SPF to work beh=
ind NAT64 would have to use a library that can discovery what NAT64 prefix =
is and translate everything.<br /><br /><span style=3D"white-space: nowrap;=
">BTW,&nbsp;what's&nbsp;going&nbsp;on&nbsp;with&nbsp;exists&nbsp;and&nbsp;A=
&nbsp;vs&nbsp;AAAA?&nbsp;The&nbsp;SPF&nbsp;7206&nbsp;RFC&nbsp;says:</span><=
br /><br /><span style=3D"white-space: nowrap;">exists&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D&nbsp;"exists"&nbsp;&nbsp;&=
nbsp;":"&nbsp;domain-spec</span><br /><br /><span style=3D"white-space: now=
rap;">&nbsp;&nbsp;&nbsp;&nbsp;The&nbsp;&lt;domain-spec&gt;&nbsp;is&nbsp;exp=
anded&nbsp;as&nbsp;perSection&nbsp;7&nbsp;&nbsp;&lt;<a href=3D"https://data=
tracker.ietf.org/doc/html/rfc7208#section-7" target=3D"_blank" rel=3D"noope=
ner noreferrer">https://datatracker.ietf.org/doc/html/rfc7208#section-7</a>=
&gt;.&nbsp;&nbsp;The&nbsp;resulting&nbsp;domain</span><br /><span style=3D"=
white-space: nowrap;">&nbsp;&nbsp;&nbsp;&nbsp;name&nbsp;is&nbsp;used&nbsp;f=
or&nbsp;a&nbsp;DNS&nbsp;A&nbsp;RR&nbsp;lookup&nbsp;(even&nbsp;when&nbsp;the=
&nbsp;connection&nbsp;type&nbsp;is</span><br /><span style=3D"white-space: =
nowrap;">&nbsp;&nbsp;&nbsp;&nbsp;IPv6).&nbsp;&nbsp;If&nbsp;any&nbsp;A&nbsp;=
record&nbsp;is&nbsp;returned,&nbsp;this&nbsp;mechanism&nbsp;matches."</span=
><br /><br />How is this meant to work for those in IPv6 only world? And wh=
at will happen when a SPF resolver behind DNS64 tries to resolve this? Is D=
NS64 just adding AAAA while preserving the A as well for an application tha=
t needs it?<br /><br /></blockquote>
IPv4 records are preserved. But yea, it was already noted in the discussion=
 that that part is a minor problematic.<br /><br />Here is a DNS64 resolver=
 from cloudflare if you want to try it yourself: 2606:4700:4700::64<br /><b=
r />
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">&nbsp;On&nbsp;202=
2-02-07&nbsp;14:40,&nbsp;&Aacute;ngel&nbsp;wrote:</span><br /><br />
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">On&nbsp;2022-02-0=
7&nbsp;at&nbsp;02:30&nbsp;+0000,&nbsp;Klaus&nbsp;Frank&nbsp;wrote:</span>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><span style=3D"white-space: nowrap;">Why?&nbsp;Such&nb=
sp;a&nbsp;query&nbsp;would&nbsp;resolve&nbsp;in&nbsp;the&nbsp;mailserver&nb=
sp;would&nbsp;make&nbsp;the&nbsp;DNS</span><br /><span style=3D"white-space=
: nowrap;">lookup.&nbsp;The&nbsp;DNS64&nbsp;server&nbsp;than&nbsp;would&nbs=
p;synthetically&nbsp;add&nbsp;an&nbsp;AAAA-RR&nbsp;to</span><br /><span sty=
le=3D"white-space: nowrap;">the&nbsp;response.</span></blockquote>
<br /><span style=3D"white-space: nowrap;">The&nbsp;issue&nbsp;is&nbsp;not&=
nbsp;that&nbsp;the&nbsp;response&nbsp;contains&nbsp;an&nbsp;A&nbsp;record&n=
bsp;but&nbsp;that&nbsp;the</span><br /><span style=3D"white-space: nowrap;"=
>queried&nbsp;domain&nbsp;embeds&nbsp;the&nbsp;remote&nbsp;IP.</span><br />=
<br /><span style=3D"white-space: nowrap;">The&nbsp;A&nbsp;result&nbsp;is&n=
bsp;usually&nbsp;a&nbsp;127.0.0.x&nbsp;address,&nbsp;with&nbsp;some&nbsp;"m=
agic"&nbsp;meaning</span><br /><span style=3D"white-space: nowrap;">(perhap=
s&nbsp;lost&nbsp;if&nbsp;translated&nbsp;into&nbsp;IPv6)&nbsp;but&nbsp;the&=
nbsp;main&nbsp;problem&nbsp;is&nbsp;querying</span><br /><span style=3D"whi=
te-space: nowrap;">the&nbsp;right&nbsp;label.</span><br /><br />___________=
____________________________________<br /><span style=3D"white-space: nowra=
p;">spfbis&nbsp;mailing&nbsp;list</span><br /><span style=3D"white-space: n=
owrap;"><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.org</a></span><br />=
<span style=3D"white-space: nowrap;"><a href=3D"https://www.ietf.org/mailma=
n/listinfo/spfbis" target=3D"_blank" rel=3D"noopener noreferrer">https://ww=
w.ietf.org/mailman/listinfo/spfbis</a></span></blockquote>
<br />_______________________________________________<br /><span style=3D"w=
hite-space: nowrap;">spfbis&nbsp;mailing&nbsp;list</span><br /><span style=
=3D"white-space: nowrap;"><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.or=
g</a></span><br /><span style=3D"white-space: nowrap;"><a href=3D"https://w=
ww.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noopener nore=
ferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></span></blockquote>
</div>
<br />
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
_______________________________________________<br />spfbis mailing list<br=
 /><a href=3D"mailto:spfbis@ietf.org">spfbis@ietf.org</a><br /><a href=3D"h=
ttps://www.ietf.org/mailman/listinfo/spfbis" target=3D"_blank" rel=3D"noope=
ner noreferrer">https://www.ietf.org/mailman/listinfo/spfbis</a></div>
</blockquote>
</body></html>

--=_62e2e97d3957bf21771e039665d6c4a6--


From nobody Tue Feb  8 06:44:48 2022
Return-Path: <vesely@tana.it>
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 4A0C73A0E67 for <spfbis@ietfa.amsl.com>; Tue,  8 Feb 2022 06:44:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level: 
X-Spam-Status: No, score=-2.812 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, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=tana.it header.b=9mY4e1w8; dkim=pass (1152-bit key) header.d=tana.it header.b=AQobNAUm
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 W541b_7V1OWF for <spfbis@ietfa.amsl.com>; Tue,  8 Feb 2022 06:44:30 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 4A86E3A0E62 for <spfbis@ietf.org>; Tue,  8 Feb 2022 06:44:16 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it; s=epsilon; t=1644331450; bh=0Z0MnEYYDi9SMuDVvUB006kSjOl6YcmghliQl4xrDY0=; h=Date:Subject:To:References:From:In-Reply-To; b=9mY4e1w8UzjCyXX2BZ/eBBRMneSuvwPmBH2DgT9LCOdDhkSPXWtBdUtSlOJum0vPX FTPe9/kGVaCkDlI7186CQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1644331450; bh=0Z0MnEYYDi9SMuDVvUB006kSjOl6YcmghliQl4xrDY0=; h=Date:To:References:From:In-Reply-To; b=AQobNAUmcgsMUrOe10SqnQpkQueV4zMl7mlmNq3nTeP1IBL+lTjK1wEeO3n5gAkxA uRPoWrlSJOgRvPbLkRFPMLNfiATLFgRwx0qwVVANJ10UHgsRap4qqsajO6O1+iIzz7 KdZ0mG7lampwKIuORmYM+wk1tI2RyrYSAxWVOSBbqFdbKtWmgAmLWHtIKXjhE
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [192.168.1.108] (host-95-249-175-244.retail.telecomitalia.it [95.249.175.244]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC0DD.00000000620281BA.00006AA6; Tue, 08 Feb 2022 15:44:10 +0100
Message-ID: <622e97dd-09ec-21f4-a561-e9aa5328c2bc@tana.it>
Date: Tue, 8 Feb 2022 15:44:11 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: spfbis@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <DF73F58F-D33E-495A-B18C-58BC994ADE8B@viagenie.ca> <5b5f5a2a-8250-4ee5-3560-80e67b540204@posteo.de> <e061ff19f8bf10bef43399d82a29bee48fbcee5d.camel@16bits.net> <e0f53dcc-a909-9476-691b-84184ba8761c@posteo.de> <b7fe33e0f8982bb5f4560ed546ac35bdff25e03b.camel@16bits.net> <1fc6a0d819c1872624dcae1e15af0384@leibzon.org> <3f9e531c-3b78-2c9d-3776-bf2ab297dead@posteo.de> <20716dc8319f4d931e2346a24ccb4440@leibzon.org>
From: Alessandro Vesely <vesely@tana.it>
In-Reply-To: <20716dc8319f4d931e2346a24ccb4440@leibzon.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/8fkWVLiEraeNgE-qFUa9G7yvXas>
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: Tue, 08 Feb 2022 14:44:47 -0000

On Tue 08/Feb/2022 01:36:31 +0100 William wrote:
> On 2022-02-07 15:31, Klaus Frank wrote:
>> On 2022-02-08 00:22, william@leibzon.org <mailto:william@leibzon.org> wrote:
>>>
>>> SPF macro tricks: 
>>> https://www.jamieweb.net/blog/using-spf-macros-to-solve-the-operational-challenges-of-spf/ 
>>> I wonder how many people actually use SPF macros....
>>>
>> We don't have to. This is all done by the SPF library and we just 
>> need to care about the DNS requests it'll perform because of this. 
>> The new dns queries are also SPF records. And also start with 
>> "v=spf1 ", so no problems as long as we'd rewrite all ip4's within 
>> it and that's the same as we'd already do anyway. Therefore no 
>> change to macros needed.
> The macros don't need to be changed if the library knows real IPv4 
> address.


Right.


> I wonder if there even are people doing ip6 exist macros...


Macros like the one Ángel cited, exists:%{ir}.list.dnswl.org, 
explicitly require to lookup a white list.  RFC 7208 suggest receivers 
do so implicitly, in order to account for forwarding, but not all 
receivers comply.  A white list lookup is required if the record 
terminates with -all.  With IPv6, it is even more required, IMHO.


Best
Ale
-- 






From nobody Wed Feb  9 09:36:55 2022
Return-Path: <hsantos@isdg.net>
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 C99FD3A0A84 for <spfbis@ietfa.amsl.com>; Wed,  9 Feb 2022 09:36:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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=isdg.net header.b=LE4f0M7H; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=y9Qsj8Eh
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 rz668wTvr62b for <spfbis@ietfa.amsl.com>; Wed,  9 Feb 2022 09:36:49 -0800 (PST)
Received: from mail.winserver.com (mail.santronics.com [76.245.57.69]) (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 ADFA13A0A71 for <spfbis@ietf.org>; Wed,  9 Feb 2022 09:36:48 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; l=6462; t=1644428202; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:From:Message-Id:Subject: Date:To:Organization:List-ID; bh=4Id5QVsQPa1xR8yD8Z7cdtHYh6hycXW +dQMbrK5oa0I=; b=LE4f0M7HlvUGxRIfx7IiBBf24p3iM1h59/yWd/ZZEYKlwBN tmBeNSrTZJlEnClOYNRQouHYVoNV8e0muH3HFoNMlkf2C+k2haGNomxV/uaZfsWl Fd/vWo81JtQ1W6q2Uo6WeM67iFuh3VD0d4AX75Fhy8FcX594Ix14mthstSvo=
Received: by mail.winserver.com (Wildcat! SMTP Router v8.0.454.12) for spfbis@ietf.org; Wed, 09 Feb 2022 12:36:42 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  dmarc=pass policy=reject author.d=isdg.net signer.d=beta.winserver.com (atps signer); 
Received: from beta.winserver.com ([76.245.57.74]) by mail.winserver.com (Wildcat! SMTP v8.0.454.12) with ESMTP id 2057876658.1.3132; Wed, 09 Feb 2022 12:36:40 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=6462; t=1644427964; h=Received:Received:From: Message-Id:Subject:Date:To:Organization:List-ID; bh=4Id5QVsQPa1x R8yD8Z7cdtHYh6hycXW+dQMbrK5oa0I=; b=y9Qsj8Eh1UzSYQL4h0qCsn6T2U/k Bwlz/QTzPe2oDg1p6kQNVyoxmZt3mllRfiggqeXs7BbsuDZvHsBI/G0hdO6zlYfo ywPM82WLEVYi/daDGU/WCiZVXLlhpKPCtK5K0aLCeTukUe26AxOXGOkae05W8l8V vN5/qdHuII8BKg0=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.12) for spfbis@ietf.org; Wed, 09 Feb 2022 12:32:44 -0500
Received: from smtpclient.apple ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.12) with ESMTP id 1181413595.1.49096; Wed, 09 Feb 2022 12:32:43 -0500
From: Hector Santos <hsantos@isdg.net>
Message-Id: <96278466-0EFF-4931-8AA3-9B49FFAF77B3@isdg.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_88357179-F5AF-44ED-852B-6FCD436B5E49"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
Date: Wed, 9 Feb 2022 12:36:38 -0500
In-Reply-To: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de>
Cc: behave@ietf.org, spfbis@ietf.org
To: Klaus Frank <klaus.frank@posteo.de>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/cvn5tXoHzOC4qmD1KGQ7QVBfVmM>
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: Wed, 09 Feb 2022 17:36:54 -0000

--Apple-Mail=_88357179-F5AF-44ED-852B-6FCD436B5E49
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

You could do a independent draft tech note to show technical details, =
perhaps implementation details for SPF/DNS resolvers learning about IP6 =
related issues and coding requirements. =20

In general, when dealing with unknown Resource Records (RR), the DNS =
server and client SHOULD be supporting RFC 3597:

https://datatracker.ietf.org/doc/html/rfc3597 =
<https://datatracker.ietf.org/doc/html/rfc3597>

A small dig into RFC6147, I don=E2=80=99t see a reference to RFC3597.  =
Maybe RFC6147 should be updated as well?

See this 2012 thread I had with Microsoft when I was updating our =
Wildcat! SAP package  for SPF RR support in its Wildcat! DNS client and =
local cache resolving API logic. We are not at IP6 but it sounds =
DNS64/NAT64 should review its level of support for RFC3597.

=
https://social.technet.microsoft.com/Forums/Lync/en-US/5841e884-db22-42a1-=
8530-615a375662cc/dns-server-support-for-new-or-unamed-rr-type-records =
<https://social.technet.microsoft.com/Forums/Lync/en-US/5841e884-db22-42a1=
-8530-615a375662cc/dns-server-support-for-new-or-unamed-rr-type-records>


Hope any of this helps

=E2=80=94
HLS



> On Feb 6, 2022, at 1:09 PM, Klaus Frank <klaus.frank@posteo.de> wrote:
>=20
> Hi,
>=20
> we had some issues with SPF and a mail server that was behind =
NAT64+DNS64. I at first thought that it was just a misconfiguration. But =
after the DNS64 server seamed to work as intended I went to the =
implementation and the RFC. Thereby while reading RFC6147 I stumbled =
across section 5.3.3 which says "All other RRs MUST be returned =
unchanged." which is the cause of my issues. This section is basically =
ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64 =
implementations from addressing this limitation.
>=20
> Would it be possible to create an extension to RFC6147 that mandates =
SPF record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 =
in IPv6 only environments won't be able to work as expected.
>=20
> Like:
> If the DNS64 server receives a SPF-record (within either the TXT-RR or =
the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites =
the ipv4 address according to the same rules as A-records are and =
synthesizes a new SPF record within the response that contains =
additional "ip6" entries. The original "ip4" should not be removed from =
the response.
>=20
> Sincerely,
> Klaus Frank


--Apple-Mail=_88357179-F5AF-44ED-852B-6FCD436B5E49
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">You =
could do a independent draft tech note to show technical details, =
perhaps implementation details for SPF/DNS resolvers learning about IP6 =
related issues and coding requirements. &nbsp;<div class=3D""><br =
class=3D""></div><div class=3D"">In general, when dealing with unknown =
Resource Records (RR), the DNS server and client SHOULD be supporting =
RFC 3597:<div class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/html/rfc3597" =
class=3D"">https://datatracker.ietf.org/doc/html/rfc3597</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">A small dig into =
RFC6147, I don=E2=80=99t see a reference to RFC3597. &nbsp;Maybe RFC6147 =
should be updated as well?</div><div class=3D""><br class=3D""></div><div =
class=3D"">See this 2012 thread I had with Microsoft when I was updating =
our Wildcat! SAP package &nbsp;for SPF RR support in its Wildcat! DNS =
client and local cache resolving API logic. We are not at IP6 but it =
sounds DNS64/NAT64 should review its level of support for =
RFC3597.</div><div class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://social.technet.microsoft.com/Forums/Lync/en-US/5841e884-db=
22-42a1-8530-615a375662cc/dns-server-support-for-new-or-unamed-rr-type-rec=
ords" =
class=3D"">https://social.technet.microsoft.com/Forums/Lync/en-US/5841e884=
-db22-42a1-8530-615a375662cc/dns-server-support-for-new-or-unamed-rr-type-=
records</a></div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">Hope any of this helps</div><div =
class=3D""><br class=3D""></div><div class=3D"">=E2=80=94</div><div =
class=3D"">HLS</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Feb 6, 2022, at 1:09 PM, Klaus Frank =
&lt;<a href=3D"mailto:klaus.frank@posteo.de" =
class=3D"">klaus.frank@posteo.de</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Hi,<br=
 class=3D""><br class=3D"">we had some issues with SPF and a mail server =
that was behind NAT64+DNS64. I at first thought that it was just a =
misconfiguration. But after the DNS64 server seamed to work as intended =
I went to the implementation and the RFC. Thereby while reading RFC6147 =
I stumbled across section 5.3.3 which says "All other RRs MUST be =
returned unchanged." which is the cause of my issues. This section is =
basically ignoring SPF records (RFC7208 section 5.6) and also preventing =
DNS64 implementations from addressing this limitation.<br class=3D""><br =
class=3D"">Would it be possible to create an extension to RFC6147 that =
mandates SPF record rewrites as well? Otherwise Mail servers behind =
NAT64+DNS64 in IPv6 only environments won't be able to work as =
expected.<br class=3D""><br class=3D"">Like:<br class=3D"">If the DNS64 =
server receives a SPF-record (within either the TXT-RR or the SPF-RR =
[RFC4408]) containing the "ip4" mechanism it MUST rewrites the ipv4 =
address according to the same rules as A-records are and synthesizes a =
new SPF record within the response that contains additional "ip6" =
entries. The original "ip4" should not be removed from the response.<br =
class=3D""><br class=3D"">Sincerely,<br class=3D"">Klaus Frank<br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_88357179-F5AF-44ED-852B-6FCD436B5E49--



From nobody Wed Feb  9 19:28:36 2022
Return-Path: <marka@isc.org>
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 C03DC3A1334; Wed,  9 Feb 2022 19:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.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, 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=isc.org header.b=fM6CnU78; dkim=pass (1024-bit key) header.d=isc.org header.b=Gzmvunah
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 ixsH2S5KMlAd; Wed,  9 Feb 2022 19:28:23 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95F463A080F; Wed,  9 Feb 2022 19:27:21 -0800 (PST)
Received: from zimbrang.isc.org (zimbrang.isc.org [149.20.1.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id A7AC33AB008; Thu, 10 Feb 2022 03:27:19 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 mx.pao1.isc.org A7AC33AB008
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=isc.org; s=ostpay; t=1644463639; bh=opmVIZUij9cOxmDQaIUBvRL8d98t1YYdmXXBWLxE2MU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=fM6CnU78qZGVXunA2JD/E+qNSkb3W/RsEJjVCF0u++mTBWffxIrFv73wfUPoW/jRP b4i7VN9HwU+dMA1P2G4RL1HWT7ED8d6yV3PXI1GLbpGdi//hxv/+bR5wilxzLq4xlb onmTC8/uQEGt1OXiggVoHxA1BFSK0Tdj1KkDtxWY=
Received: from zimbrang.isc.org (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTPS id 8F284FE6ACB; Thu, 10 Feb 2022 03:27:19 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTP id 5BF88FE6ACD; Thu, 10 Feb 2022 03:27:19 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbrang.isc.org 5BF88FE6ACD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1644463639; bh=BdRz7xQGW/p9K936aHqA+t+eKLKFEYtCGGcTlT3il2Q=; h=Mime-Version:From:Date:Message-Id:To; b=GzmvunahzDr0AifS4lrNrTiBZQssVrfCihEyTD/NmuHLjoaWskzSef49XhwQW8sOu Quy70+JTAYWuykqMIhu6kDjiJuzGxkfUCUhKh65gWXWEspNdFeF+40d4FxptQMivmn 4Y3FwOPt1PexRZdR8oImGvEFDip59zwbuaO14/6s=
Received: from zimbrang.isc.org ([127.0.0.1]) by localhost (zimbrang.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id KDQtndOJ6ITp; Thu, 10 Feb 2022 03:27:19 +0000 (UTC)
Received: from smtpclient.apple (n114-74-26-107.bla4.nsw.optusnet.com.au [114.74.26.107]) by zimbrang.isc.org (Postfix) with ESMTPSA id 49A14FE6ACB; Thu, 10 Feb 2022 03:27:18 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <96278466-0EFF-4931-8AA3-9B49FFAF77B3@isdg.net>
Date: Thu, 10 Feb 2022 14:27:14 +1100
Cc: Klaus Frank <klaus.frank@posteo.de>, spfbis@ietf.org, behave@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D9FC0E6-F066-40CB-8ED7-894F7A57DD34@isc.org>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <96278466-0EFF-4931-8AA3-9B49FFAF77B3@isdg.net>
To: Hector Santos <hsantos=40isdg.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/5nTH-LDyZaRTStSgzjLDtRwWC3s>
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: Thu, 10 Feb 2022 03:28:28 -0000

> On 10 Feb 2022, at 04:36, Hector Santos =
<hsantos=3D40isdg.net@dmarc.ietf.org> wrote:
>=20
> RFC3597

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Wed Feb  9 20:07:02 2022
Return-Path: <marka@isc.org>
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 22AA83A13B5; Wed,  9 Feb 2022 20:07:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level: 
X-Spam-Status: No, score=-7.097 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=isc.org header.b=aYww0TrI; dkim=pass (1024-bit key) header.d=isc.org header.b=Gm+ctR0+
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 ZaQeXwWMn_sB; Wed,  9 Feb 2022 20:06:55 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B1013A13B2; Wed,  9 Feb 2022 20:06:55 -0800 (PST)
Received: from zimbrang.isc.org (zimbrang.isc.org [149.20.1.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id 235213AB008; Thu, 10 Feb 2022 04:06:55 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 mx.pao1.isc.org 235213AB008
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=isc.org; s=ostpay; t=1644466015; bh=9rTIkqkLOuroWXtieI20BXDvn6jOJAYQHMLiPm6ClFA=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=aYww0TrIONI8nvysplgEfIoP5z/dNGxL7a/id0ajVFIVgjNGdP6G14SHxDtFCfKLW olUj+X4Lyr35OenEYqfIELgH4o43s7pRR7dQbZX8AXk6yXvftniBN+IfBanHbU6G98 15rRO3Gc7vCwFhVQ8yb6pFYA6Idy2xirm86u3TG8=
Received: from zimbrang.isc.org (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTPS id 0BE19FE69D7; Thu, 10 Feb 2022 04:06:55 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTP id BF478FE69DC; Thu, 10 Feb 2022 04:06:54 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbrang.isc.org BF478FE69DC
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1644466014; bh=Rx7+VIpsd7yunbh8B+Ug5yBS9mEGWyi7r52W2unW464=; h=Mime-Version:From:Date:Message-Id:To; b=Gm+ctR0+TnP+B2z5gnByddrZJvNBMsf3FHEXu67PQv8pQNnYW9dAKPDY5AInksN/3 It+HOUanY5YCh3AMmAgkmfSKW9MtDtTuG59wzX/iEJivaPLuxaG9aBCwePSadgADUo oP7NKBIp63u2h/Fy+/cUJUjgayuvuQ79q+aGUhME=
Received: from zimbrang.isc.org ([127.0.0.1]) by localhost (zimbrang.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id VktHMqNSgex5; Thu, 10 Feb 2022 04:06:54 +0000 (UTC)
Received: from smtpclient.apple (n114-74-26-107.bla4.nsw.optusnet.com.au [114.74.26.107]) by zimbrang.isc.org (Postfix) with ESMTPSA id A9040FE69D7; Thu, 10 Feb 2022 04:06:53 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <96278466-0EFF-4931-8AA3-9B49FFAF77B3@isdg.net>
Date: Thu, 10 Feb 2022 15:06:51 +1100
Cc: Klaus Frank <klaus.frank@posteo.de>, spfbis@ietf.org, behave@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECED3F0C-8CDD-4209-9E2A-38AB6E6C8717@isc.org>
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <96278466-0EFF-4931-8AA3-9B49FFAF77B3@isdg.net>
To: Hector Santos <hsantos=40isdg.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/bcSeL6ZKHebHhXrigpGMY81Ztcg>
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: Thu, 10 Feb 2022 04:07:00 -0000

Unfortunately some resolver developers failed to read / understand
RFC 1034.  RFC 3597 provided a standard textual representation, which
allowed nameservers to load and publish records that they didn=E2=80=99t =
know
about.  Handling of arbitrary records by resolvers was expected from
the very beginning.  New record types where expected from the very
beginning.

RFC 1034

   3. General lookup function

      This function retrieves arbitrary information from the DNS,
      and has no counterpart in previous systems.  The caller
      supplies a QNAME, QTYPE, and QCLASS, and wants all of the
      matching RRs.  This function will often use the DNS format
      for all RR data instead of the local host's, and returns all
      RR content (e.g., TTL) instead of a processed form with local
      quoting conventions.

When the resolver performs the indicated function, it usually has one of
the following results to pass back to the client:

   - One or more RRs giving the requested data.

     In this case the resolver returns the answer in the
     appropriate format.

   - A name error (NE).

     This happens when the referenced name does not exist.  For
     example, a user may have mistyped a host name.

   - A data not found error.

     This happens when the referenced name exists, but data of the
     appropriate type does not.  For example, a host address
     function applied to a mailbox name would return this error
     since the name exists, but no address RR is present.

RFC 1035

The domain system is a mixture of functions and data types which are an
official protocol and functions and data types which are still
experimental.  Since the domain system is intentionally extensible, new
data types and experimental behavior should always be expected in parts
of the system beyond the official protocol.  The official protocol parts
include standard queries, responses and the Internet class RR data
formats (e.g., host addresses).  Since the previous RFC set, several
definitions have changed, so some previous definitions are obsolete.

Mark

> On 10 Feb 2022, at 04:36, Hector Santos =
<hsantos=3D40isdg.net@dmarc.ietf.org> wrote:
>=20
> You could do a independent draft tech note to show technical details, =
perhaps implementation details for SPF/DNS resolvers learning about IP6 =
related issues and coding requirements. =20
>=20
> In general, when dealing with unknown Resource Records (RR), the DNS =
server and client SHOULD be supporting RFC 3597:
>=20
> https://datatracker.ietf.org/doc/html/rfc3597
>=20
> A small dig into RFC6147, I don=E2=80=99t see a reference to RFC3597.  =
Maybe RFC6147 should be updated as well?
>=20
> See this 2012 thread I had with Microsoft when I was updating our =
Wildcat! SAP package  for SPF RR support in its Wildcat! DNS client and =
local cache resolving API logic. We are not at IP6 but it sounds =
DNS64/NAT64 should review its level of support for RFC3597.
>=20
> =
https://social.technet.microsoft.com/Forums/Lync/en-US/5841e884-db22-42a1-=
8530-615a375662cc/dns-server-support-for-new-or-unamed-rr-type-records
>=20
>=20
> Hope any of this helps
>=20
> =E2=80=94
> HLS
>=20
>=20
>=20
>> On Feb 6, 2022, at 1:09 PM, Klaus Frank <klaus.frank@posteo.de> =
wrote:
>>=20
>> Hi,
>>=20
>> we had some issues with SPF and a mail server that was behind =
NAT64+DNS64. I at first thought that it was just a misconfiguration. But =
after the DNS64 server seamed to work as intended I went to the =
implementation and the RFC. Thereby while reading RFC6147 I stumbled =
across section 5.3.3 which says "All other RRs MUST be returned =
unchanged." which is the cause of my issues. This section is basically =
ignoring SPF records (RFC7208 section 5.6) and also preventing DNS64 =
implementations from addressing this limitation.
>>=20
>> Would it be possible to create an extension to RFC6147 that mandates =
SPF record rewrites as well? Otherwise Mail servers behind NAT64+DNS64 =
in IPv6 only environments won't be able to work as expected.
>>=20
>> Like:
>> If the DNS64 server receives a SPF-record (within either the TXT-RR =
or the SPF-RR [RFC4408]) containing the "ip4" mechanism it MUST rewrites =
the ipv4 address according to the same rules as A-records are and =
synthesizes a new SPF record within the response that contains =
additional "ip6" entries. The original "ip4" should not be removed from =
the response.
>>=20
>> Sincerely,
>> Klaus Frank
>=20
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org

