[spfbis] RFC7208 dual-cidr-length clarification
Jan Schaumann <jschauma@netmeister.org> Wed, 31 August 2022 19:18 UTC
Return-Path: <jschauma@netmeister.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 C50A1C15AE02 for <spfbis@ietfa.amsl.com>; Wed, 31 Aug 2022 12:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=netmeister.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QF3UGTW-qJhn for <spfbis@ietfa.amsl.com>; Wed, 31 Aug 2022 12:18:39 -0700 (PDT)
Received: from panix.netmeister.org (panix.netmeister.org [166.84.7.99]) (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 B5223C15AE0B for <spfbis@ietf.org>; Wed, 31 Aug 2022 12:18:39 -0700 (PDT)
Received: by panix.netmeister.org (Postfix, from userid 1000) id 03053852CD; Wed, 31 Aug 2022 15:18:36 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=netmeister.org; s=2022; t=1661973517; bh=ODLwN22X0kiBFBMYo+b7wC1q+VjS89Oor72JQyeWIOY=; h=Date:From:To:Subject; b=XqKBZ8cPiQQEKpOZ2mlbiCw2AV+6J1dWp7b/cGgJ9bueGLZO7HERzC/LzSZbXg5yg pmi7R8cVbMRm8cBiwjjh9xgjs5GTgVl+1iKlFV2xrpw0k2rtq7ufOFvP8xk2dM+G4S difTgT8J3wRwc5vav7kjJkPljFE9XbE8Vo006Ik2RMEd7kQQA1Cy51sDnqsd0TOU4j MoTZehCxqUxxO+QCDtEB5QtRd9U2ZmBELPpCI/oGmoJLO4mvN34DWV0PUnF5QClYOZ Qh+/Jsw0WqWyNVVsyrJVgOcg3JxeCV4mA5l+Yy6lKh7uiE/NKypPn+qMFug8iD+khz 8f9cj5mb/a8zA==
Date: Wed, 31 Aug 2022 15:18:36 -0400
From: Jan Schaumann <jschauma@netmeister.org>
To: spfbis@ietf.org
Message-ID: <20220831191836.GL18101@netmeister.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.11.1 (2018-12-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/afHA_krDQKMpnGe2CAthI7xvbRk>
Subject: [spfbis] RFC7208 dual-cidr-length clarification
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.39
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, 31 Aug 2022 19:18:43 -0000
Hello, Reading RFC7208 leaves me wondering whether the correct syntax when specifying both an ip4-cidr-length and an ip6-cidr-length requires two slashes to separate them: a = "a" [ ":" domain-spec ] [ dual-cidr-length ] ip4-cidr-length = "/" ("0" / %x31-39 0*1DIGIT) ; value range 0-32 ip6-cidr-length = "/" ("0" / %x31-39 0*2DIGIT) ; value range 0-128 dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ] This reads to me that the correct syntax would need to be: a:example.com/24//64 +--++--+ || ||| || ||+---> "64" (ip6-cidr-length value range 0-128) || || || |+----> "/" from 'ip6-cidr-length' definition || | || +-----> "/" from 'dual-cidr-length' definition || |+-------> "24" (ip4-cidr-length value range 0-32) | +--------> "/" from 'ip4-cidr-length' definition I suspect that the "/" in 'dual-cidr-length' is intended to allow an empty ip4-cidr-length, so that it'd be possible to say a:example.com//64 to convey that no ip4-cidr-length is specified (and would then be equivalent to "a:example.com/32/64"), but I think as written above, specifying both an ip4-cidr-length and an ip6-cidr-length would require dual-slashes as shown above, rather than the more intuitive a:example.com/24/64 Perhaps the intended grammar was dual-cidr-length = ( "/" / [ ip4-cidr-length ] ) [ ip6-cidr-length ] ? Thanks for any clarification here, -Jan
- [spfbis] RFC7208 dual-cidr-length clarification Jan Schaumann
- Re: [spfbis] RFC7208 dual-cidr-length clarificati… David Bürgin
- Re: [spfbis] RFC7208 dual-cidr-length clarificati… Jan Schaumann
- Re: [spfbis] RFC7208 dual-cidr-length clarificati… David Bürgin