Re: [v6ops] FW: New Version Notification for draft-ipversion6-loopback-prefix-00.txt

Falcon Darkstar Momot <falcon@iridiumlinux.org> Tue, 17 February 2015 02:16 UTC

Return-Path: <falcon@iridiumlinux.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA9A31A86E8 for <v6ops@ietfa.amsl.com>; Mon, 16 Feb 2015 18:16:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 QYHrJIsUVR6x for <v6ops@ietfa.amsl.com>; Mon, 16 Feb 2015 18:16:20 -0800 (PST)
Received: from smtp.iridiumlinux.org (akira.iridiumlinux.org [184.70.203.174]) by ietfa.amsl.com (Postfix) with ESMTP id F08A21A802F for <v6ops@ietf.org>; Mon, 16 Feb 2015 18:16:19 -0800 (PST)
Received: by smtp.iridiumlinux.org (Postfix, from userid 65534) id 571C014FA0CF; Mon, 16 Feb 2015 19:15:49 -0700 (MST)
X-Spam-ASN:
Received: from [192.168.1.135] (unknown [96.53.15.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.iridiumlinux.org (Postfix) with ESMTPSA id 57BCA14FA039 for <v6ops@ietf.org>; Mon, 16 Feb 2015 19:15:48 -0700 (MST)
Message-ID: <54E2A454.3080908@iridiumlinux.org>
Date: Mon, 16 Feb 2015 19:15:48 -0700
From: Falcon Darkstar Momot <falcon@iridiumlinux.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <D1076758.8F7D%edward.lewis@icann.org> <419285087.7936915.1424128613951.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <419285087.7936915.1424128613951.JavaMail.yahoo@mail.yahoo.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms050901060502050208020602"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/zFrgcY1gAdqq0LJdE0gnHCqxCf0>
Subject: Re: [v6ops] FW: New Version Notification for draft-ipversion6-loopback-prefix-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2015 02:16:24 -0000

On 16/02/2015 16:16, Mark ZZZ Smith wrote:
> / These addresses do not have this semantic meaning to me, because I do not deal with DNS black lists (and don't think they're a great way to solve the spam problem anyway).
>
> / This problem is all about signalling colliding names or other semantics in DNS, so DNS is where the problem is best solved, rather than at the IP address layer. The best people to talk to then are the IETF DNS working group (dnsop wg), as they're the experts on DNS. RCODE YXDOMAIN, "Some name that ought not to exist, does exist." at face value sounds like the right one to use, if not, they can assign a new RCODE with corresponding specifications.
I suggest that perhaps the best way to handle this is not to use A or
AAAA records at all, but rather TXT records with specific text in the
tag (or request an entirely new RRtype, called something like MXTRUST). 
Allocating a large swath of IPv6 address space, even though we have a
lot of it, seems like exactly the wrong thing to do here -- addresses
are addresses, not tags.

--
--Falcon Darkstar Momot
--Shadytel