Re: [spfbis] RFC7208 dual-cidr-length clarification
David Bürgin <dbuergin@gluet.ch> Wed, 31 August 2022 19:46 UTC
Return-Path: <dbuergin@gluet.ch>
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 A19E4C1526ED for <spfbis@ietfa.amsl.com>; Wed, 31 Aug 2022 12:46:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=gluet.ch
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 PJ16XQ14bt37 for <spfbis@ietfa.amsl.com>; Wed, 31 Aug 2022 12:46:21 -0700 (PDT)
Received: from mail.gluet.ch (mail.gluet.ch [185.46.57.247]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B179DC1524A1 for <spfbis@ietf.org>; Wed, 31 Aug 2022 12:46:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gluet.ch; s=2020; t=1661975178; bh=rLD1kE7NRbT8a2wKdP7CN215DW3L1AAXOhHE7r0hTHY=; h=Date:Subject:To:References:From:In-Reply-To:From; b=S4dOQJh+zLowf1n8f3rZJKQsP0Y7DeQBWrHiRW06/UT1B1JpRJB3l3rx9NabY5bU5 y9i49KMfSeWNBRDewvHVYWK3105gSA8zxD66ppXUPaqfcj/SfkNOswG8N+bMHQJ6Yd zUZghuvQM0Vz/o8NuUVtgipERSUB+QCzR2AH9eDTV4n3rbkeG0b5ioAtbiDFff1Pc9 y4ZczbTdzlcUKcNEuFLjBphX7vwucXRXS3YGECJSo+vuth7Jv9iYMfoVFkNgOi5Wvz SmJ46oGAB7Ren95xOOHUa/W+bDr/tWZPWlx+P+helA9rmiu1VS9WrFxcJgagfJ1ZgK HE6K0TXUQAhlg==
Received: from [IPV6:2a02:1210:1a9a:2d00:d358:ff9e:7891:d83a] (unknown [IPv6:2a02:1210:1a9a:2d00:d358:ff9e:7891:d83a]) by mail.gluet.ch (Postfix) with ESMTPSA id E397B400D307 for <spfbis@ietf.org>; Wed, 31 Aug 2022 21:46:18 +0200 (CEST)
Message-ID: <0348aab2-a4fb-f479-59ce-d9bb80988730@gluet.ch>
Date: Wed, 31 Aug 2022 21:46:16 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-GB
To: spfbis@ietf.org
References: <20220831191836.GL18101@netmeister.org>
From: David Bürgin <dbuergin@gluet.ch>
In-Reply-To: <20220831191836.GL18101@netmeister.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/Kncyvi-iwV5YhB4anWX1ZIjgrHs>
Subject: Re: [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:46:26 -0000
Jan Schaumann: > 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 ] > > ? Interesting. I interpreted the syntax to allow all of mx mx/24 mx//64 mx/24//64 for IPv4 or IPv6 CIDR prefix length, both, or neither. Right?
- [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