IETF Logo Mail Archive

Re: [dbound] Requirements for administrative boundary data sources?

Jeffrey Walton <noloader@gmail.com> Mon, 11 April 2016 08:35 UTC

Return-Path: <noloader@gmail.com>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78B6F12E928 for <dbound@ietfa.amsl.com>; Mon, 11 Apr 2016 01:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1cGvI8aDt8Rb for <dbound@ietfa.amsl.com>; Mon, 11 Apr 2016 01:35:05 -0700 (PDT)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B3DE12E927 for <dbound@ietf.org>; Mon, 11 Apr 2016 01:35:05 -0700 (PDT)
Received: by mail-ig0-x235.google.com with SMTP id gy3so55507303igb.0 for <dbound@ietf.org>; Mon, 11 Apr 2016 01:35:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-transfer-encoding; bh=X3j9xE4h+yG4x0VAw/QVyDHOMHfAPpnG/G6cTojMjkg=; b=cK8mZmCLl/MMOVD7btMrcmPEfujiQhnrp/mhrFPX3i/D6FK6MUAy6q7hx1UZCcnxgA r7UeTJMgZahP/TfuaTl6ymCzEX5LPt/Om80otLdrcyfu6elpC7QIqF/KSZumEcAfyl/4 5hgGXWGBKGr+/RHmGIqFwB7gnt7l8tdaZxcZsoFT4/9WBRkfC08Y0NyezF+u3V04f7I0 ft9Q0tglCnlzi9RSwS1Zd/7Z+o+OQ+CqNz5pqGdxSo7fF8dxErJfQ4FLdIpVmRhGiJb9 kqtwkDwMRbeG2yFdBtsG+1gmlnBLNqbyx5GRWBCz+FEFALFJUmXzTdWxFc/Eu68MJwy7 PYww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-transfer-encoding; bh=X3j9xE4h+yG4x0VAw/QVyDHOMHfAPpnG/G6cTojMjkg=; b=IGHKHRQuQuBbl5T4Wq+sQY+zH7PBHENpZdfsmxcH7YPcIS5iciBJWZ61t6F9dbOBqj WizwBYhDtgnVdR5U/+pNZLMnw3cfJ7IsWQ+EaHzvw0Qn0S2XmtntyPvCnqZu9H4YYhjR woDOsh4LY3Bv0LFt/KpOK2wcaoYg78KsIES0Idqmfxh9trr70kZXx2x4orAWcAxmY1Sg b4kG1eDrBQlN5k9F+lOpjPZ3PZSyn1spevTqNDN4qKnzZAqbdZY1sY6nyuyMxbgwa1y2 U0La3H1ay1lqzeNrlZF2y2Qj0YIY7DrGmsfV/H6/u6zweysB+L6tydLNQrqni7RkvhcO CttQ==
X-Gm-Message-State: AD7BkJINjUd03TmnBPdKv1DZEKhKGbxO4FeFDhUmcv6hhRm/Spo0BYAO9o0euVx4nsEv+BiW6Lj5XQcdfpTAeg==
MIME-Version: 1.0
X-Received: by 10.50.124.36 with SMTP id mf4mr17112291igb.92.1460363704597; Mon, 11 Apr 2016 01:35:04 -0700 (PDT)
Received: by 10.36.193.133 with HTTP; Mon, 11 Apr 2016 01:35:04 -0700 (PDT)
In-Reply-To: <570B5E12.6030909@it.aoyama.ac.jp>
References: <CAH8yC8maLvy34_visC3XvvUcxSBUD50ZFq6NQ4rV7Fve-=rHGA@mail.gmail.com> <570B5E12.6030909@it.aoyama.ac.jp>
Date: Mon, 11 Apr 2016 04:35:04 -0400
Message-ID: <CAH8yC8mwh0ddwu3MXdvJ9_JEccmcVx8F+tLi4ckps9Ru-ExaQw@mail.gmail.com>
From: Jeffrey Walton <noloader@gmail.com>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dbound/rRS9eOn1eeAyjw7Y2NpmmN2HkMs>
Cc: "dbound@ietf.org" <dbound@ietf.org>
Subject: Re: [dbound] Requirements for administrative boundary data sources?
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: noloader@gmail.com
List-Id: DNS tree bounds <dbound.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dbound>, <mailto:dbound-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound/>
List-Post: <mailto:dbound@ietf.org>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dbound>, <mailto:dbound-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2016 08:35:06 -0000

On Mon, Apr 11, 2016 at 4:19 AM, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
> On 2016/04/11 02:31, Jeffrey Walton wrote:
>>
>> What are the requirements for the data source? I.e., does it have to
>> come from DNS?
>
>
> Not necessarily, as far as I remember. But one requirement (or at least
> desideratum) is that it come as directly as possible from the actual entity
> that's in charge. That property would be met easily by DNS.

Thanks.

If the PSL is moved into owner/operators web services and out of DNS,
then it may be easier to build a new system (say a PSL.txt like a
Robots.txt) rather than retrofitting (adding DNS infrastructure and
pushing record changes into DNS).

Jeff

v2.23.0 | Report a Bug | By Email