IETF Logo Mail Archive

Re: [DNSOP] Terminology: operator

Paul Hoffman <paul.hoffman@vpnc.org> Sun, 17 May 2015 23:59 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2D01A8820 for <dnsop@ietfa.amsl.com>; Sun, 17 May 2015 16:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.552
X-Spam-Level:
X-Spam-Status: No, score=0.552 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_MISMATCH_COM=0.553] autolearn=no
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 pc2mpgo0zDai for <dnsop@ietfa.amsl.com>; Sun, 17 May 2015 16:59:48 -0700 (PDT)
Received: from proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA9231A1B1B for <dnsop@ietf.org>; Sun, 17 May 2015 16:59:48 -0700 (PDT)
Received: from [10.20.30.101] (50-1-98-218.dsl.dynamic.fusionbroadband.com [50.1.98.218]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t4HNxhVJ049748 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 May 2015 16:59:44 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 50-1-98-218.dsl.dynamic.fusionbroadband.com [50.1.98.218] claimed to be [10.20.30.101]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <8B7949CC-9312-4E49-B227-244B42E1CE2D@dotat.at>
Date: Sun, 17 May 2015 16:59:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <21462642-0B52-4952-BA7B-7FD886BA9BA4@vpnc.org>
References: <FF8A90DC-ABEE-4224-B9BE-695165BE8EF6@vpnc.org> <8B7949CC-9312-4E49-B227-244B42E1CE2D@dotat.at>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/Rw57--URT2n9TNfWoWE0Dl1bHgQ>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Terminology: operator
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 May 2015 23:59:49 -0000

On May 15, 2015, at 1:40 AM, Tony Finch <dot@dotat.at> wrote:
> Another item for section 7:
> 
> DNS operator -- an entity responsible for running DNS servers. For a zone's authoritative servers, the registrant may act as their own DNS operator, or their registrar may do it on their behalf, or they may use a third-party operator.

It was pointed out to me offline that I was taking the term "DNS operator" too far, and that this is really part of the registration model. (I found it in RFC 2181 in the general sense, but that seems to be a one-short use of the term).

So, I'm OK with the above definition if other folks here are.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email