IETF Logo Mail Archive

Re: [dnsext] RFC 2142 and "organization's top level domain"

Florian Weimer <fweimer@bfk.de> Mon, 13 September 2010 08:12 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4BC03A6925; Mon, 13 Sep 2010 01:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.816
X-Spam-Level:
X-Spam-Status: No, score=0.816 tagged_above=-999 required=5 tests=[AWL=1.206, BAYES_20=-0.74, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3khhD50UHv7N; Mon, 13 Sep 2010 01:12:43 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C2FAF3A691B; Mon, 13 Sep 2010 01:12:42 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1Ov45w-000NBA-9v for namedroppers-data0@psg.com; Mon, 13 Sep 2010 08:08:56 +0000
Received: from mx01.bfk.de ([193.227.124.2]) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <fweimer@bfk.de>) id 1Ov45t-000NAs-0d for namedroppers@ops.ietf.org; Mon, 13 Sep 2010 08:08:53 +0000
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1Ov3xP-0000Uo-Lj; Mon, 13 Sep 2010 08:00:17 +0000
Received: by bfk.de with local id 1Ov3x7-0001XS-3U; Mon, 13 Sep 2010 07:59:49 +0000
To: dcrocker@bbiw.net
Cc: namedroppers@ops.ietf.org
Subject: Re: [dnsext] RFC 2142 and "organization's top level domain"
References: <4C8AD1C5.1050601@dcrocker.net>
From: Florian Weimer <fweimer@bfk.de>
Date: Mon, 13 Sep 2010 07:59:49 +0000
In-Reply-To: <4C8AD1C5.1050601@dcrocker.net> (Dave CROCKER's message of "Fri\, 10 Sep 2010 17\:48\:05 -0700")
Message-ID: <82hbhut6oa.fsf@mid.bfk.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

* Dave CROCKER:

> Comments?

Just move the RFC to HISTORICAL.

The advice in this RFC on the security mailbox has been interpreted in
a way that in order to receive CERT/CC notices etc., you write to your
organization's postmaster and request addition to the security mail
exploder.  (I've worked for organizations that did not treat security
mailbox mail as on a need-to-know basis, as it is the expectation
nowadays, at least some of them citing the RFC as a rationale.)  I'm
not sure if it was your intent, but the document can be easily read
that way.  Existing practice is rather different, of course.

-- 
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

v2.23.0 | Report a Bug | By Email