IETF Logo Mail Archive

Re: The "nomap" Network Identifier Suffix

Ted Lemon <ted.lemon@nominum.com> Tue, 26 November 2013 20:15 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660C71AE1A2 for <ietf@ietfa.amsl.com>; Tue, 26 Nov 2013 12:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 GPg9ePqOX98S for <ietf@ietfa.amsl.com>; Tue, 26 Nov 2013 12:15:42 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 093EF1AE223 for <ietf@ietf.org>; Tue, 26 Nov 2013 12:15:42 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUpUBbgG3zVQsH4sLu2sBe+peQYg+98Uk@postini.com; Tue, 26 Nov 2013 12:15:42 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D4F241B82C6 for <ietf@ietf.org>; Tue, 26 Nov 2013 12:15:41 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CCC8519005C; Tue, 26 Nov 2013 12:15:41 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 26 Nov 2013 12:15:41 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: The "nomap" Network Identifier Suffix
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAL02cgQ7JXG-iRKWyT_eTGT4Ak8ag6FS-z+++yRJztU-tkBb_w@mail.gmail.com>
Date: Tue, 26 Nov 2013 15:15:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <B906EBA7-7BD3-45C0-8AAC-3C4B7E4F61AA@nominum.com>
References: <i9n799hrr1vfp4bobt9tc55rn1aip73rts@hive.bjoern.hoehrmann.de> <3D4E298A-FE87-4FD1-BCC2-EF33E7BD4D99@cs.georgetown.edu> <CAL02cgQ7JXG-iRKWyT_eTGT4Ak8ag6FS-z+++yRJztU-tkBb_w@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: Eric Burger <eburger@cs.georgetown.edu>, Bjoern Hoehrmann <derhoermi@gmx.net>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2013 20:15:43 -0000

On Nov 26, 2013, at 3:13 PM, Richard Barnes <rlb@ipv.sx> wrote:
> The evil bit is ridiculous because evil people have no incentive to set it (thus nobody would ever look for it to be set).  With the _nomap suffix, the people who would need to set it have an incentive to do so, and at least in certain cases, the entities that might consume it have incentives to obey it as well.

Yup.   Google certainly paid a high price recently for doing something analogous to ignoring this suffix.

v2.23.0 | Report a Bug | By Email