IETF Logo Mail Archive

Re: [spfbis] prefixed names, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>

"John Levine" <johnl@taugh.com> Tue, 20 August 2013 14:46 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9016E11E8225 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 07:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.821
X-Spam-Level:
X-Spam-Status: No, score=-102.821 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JT7IfJSgCQN4 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 07:46:17 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 584AA21F99E1 for <ietf@ietf.org>; Tue, 20 Aug 2013 07:46:12 -0700 (PDT)
Received: (qmail 83760 invoked from network); 20 Aug 2013 14:46:11 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Aug 2013 14:46:11 -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; s=52138133.xn--9vv.k1308; i=johnl@user.iecc.com; bh=XQWDbqTEzgSKwYhmyfquO/nxBojQ75S8bWVx/Xr9oZs=; b=GzUJcRo3F8Xu5+Csx9mS11P69Eq7Bj++ZGiynytIcsj+pupjIluKHb5QO7sy0YsO3sfwG6KY4s6UJ3TV6DE5TfRZ2XZuUlzGiGqUJfdUrv2RNyKHhp7radrv+NBHVNK7nIuCm1oHqpci2BqZ3fd1WGmWN/MtLF8FHg3d6llOGBCtav0anknobhXHajgcjGzBteD93bQQzzDpLXEPOkPcWzdupoUXVs4P1HqZfvlfJCg2r9ZqnuyPsq44dcLf9Ulx
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; s=52138133.xn--9vv.k1308; olt=johnl@user.iecc.com; bh=XQWDbqTEzgSKwYhmyfquO/nxBojQ75S8bWVx/Xr9oZs=; b=CySugIUIqYnyPJnKURoSGtgG+pVg9xAH+qZKFzrxsPRRguGLCi6xMvfWJZgDGNdQHIArRzmVIHJpj/AdBvhvfS7OTS9avdcNPYjyj1imdVsc+JT19AknqRX0RRWJa17v6V+m5qsbvj/kF0z8J1JwzUyHSusg9u+lLwi68Us3IvrFmUNKyaiGVoEX5GJO41TXU+y+mDeLcVmI8GHn++ZY4ueXJZimYdAFUgjykZwRa1rmGVmiNVd+wu8UKaq8i6Io
Date: Tue, 20 Aug 2013 14:45:48 -0000
Message-ID: <20130820144548.73129.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] prefixed names, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
In-Reply-To: <D2148A40-2673-40C7-8349-0A65D0D01794@frobbit.se>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Cc: paf@frobbit.se
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 14:46:22 -0000

Newsgroups: iecc.lists.ietf.ietf
From: John Levine <johnl@iecc.com>
Subject: Re: [spfbis] prefixed names, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
Summary:
Expires:
References: <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se> <5213174D.7080504@dcrocker.net> <D2148A40-2673-40C7-8349-0A65D0D01794@frobbit.se>
Sender:
Followup-To:
Distribution: 
Organization: 
Keywords: 
Cc: 
Cleverness: some

>The two following MIGHT NOT be in the same zone:
>
>foo.example. IN X RDATAX
>_bar.foo.example. IN TXT RDATAY

Since prefixed names have never been used for anything other than
providing information about the unprefixed name, what conceivable
operational reason could there be to put a zone cut at the prefix?

This impresses me as one of those problems where the solution is
"don't do that."

R's,
John

v2.23.0 | Report a Bug | By Email