IETF Logo Mail Archive

[dbound] Requirements for administrative boundary data sources?

Jeffrey Walton <noloader@gmail.com> Sun, 10 April 2016 17:31 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 C5D3F12D61A for <dbound@ietfa.amsl.com>; Sun, 10 Apr 2016 10:31:13 -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 Lj0ttBQw884R for <dbound@ietfa.amsl.com>; Sun, 10 Apr 2016 10:31:12 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 71CAA12D095 for <dbound@ietf.org>; Sun, 10 Apr 2016 10:31:12 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id o126so161360275iod.0 for <dbound@ietf.org>; Sun, 10 Apr 2016 10:31:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to; bh=x5HrCYSHFiuR5MdvxPe1kbloPGPufufKr4YbCzMGdNc=; b=KnTlDXUfraXc1d+49KmMtuTdxyDrGc/9G0aWkewoitnQ7nhUUxkw6+T6TbqLh8/5Fn /Q37qFHHaX4p18LCH/EsJRnZ7zFtXHIIN5QHo0uys1j2Z9hlIyDoh7scYdNvwd0vviFM 9sX0K6TrCYBLKvSa2nUn7YXOX5qShP4/Y71+b/yDh9wUexxhrZrMlf3vwOrE/rh3RWLY RL48a2alZOo9syfJAH3Zh3PfShcZ8QduCNMiLBYXTEim3Y5praWh0y9tfGzJHenwsiam 6UjwRYvGb6byzRVZ3jdiQWePU4vdOvwndcDt9euKekpRDR3id/fgZ/Rqxd8C9fWNk2tN 3ANA==
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:date:message-id:subject :from:to; bh=x5HrCYSHFiuR5MdvxPe1kbloPGPufufKr4YbCzMGdNc=; b=UWXKiSijMGK9sh+bIolXq1Puc9u2G+x15S6TABzRVsyFauzjSJMucjw2+XqPChYdNP BpAzRmyf9aVyAK2yax37W468HrDICjNUDwcT4YdZBW9EgbsPR1wTEk9LiK7sfhKXouIV O7Se+My1Vldt2wwdGzIhBRut1x6Te02tVPfMkEHmsnfvcrX00aXMM3yBErERvSPdb9CF FaAYsnc7S2HDJSl26R80MLZFdxzq1rjTiOkg+Bc64xeSR8lel/iHrjKn0h0/jwUHf1R9 fcRkW+68N9nij5jgXobcFatr9HsmsHEceIfo7Fu/VBAWJHyTaeznR1iKpwqQxfdC3vt5 b+xw==
X-Gm-Message-State: AD7BkJJmxiAVgOIUHKFf6Hb/twK+yw/JvQL4JBLg/MqVVq6myVBIp5PQdEJg3BiS8i+2CpkzRpagz0ir9Za0ng==
MIME-Version: 1.0
X-Received: by 10.107.150.8 with SMTP id y8mr18663484iod.66.1460309471843; Sun, 10 Apr 2016 10:31:11 -0700 (PDT)
Received: by 10.36.193.133 with HTTP; Sun, 10 Apr 2016 10:31:11 -0700 (PDT)
Date: Sun, 10 Apr 2016 13:31:11 -0400
Message-ID: <CAH8yC8maLvy34_visC3XvvUcxSBUD50ZFq6NQ4rV7Fve-=rHGA@mail.gmail.com>
From: Jeffrey Walton <noloader@gmail.com>
To: "dbound@ietf.org" <dbound@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dbound/yAvPFZDjDA8siUSPIN9DLRvGPcQ>
Subject: [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: Sun, 10 Apr 2016 17:31:13 -0000

What are the requirements for the data source? I.e., does it have to
come from DNS?

v2.23.0 | Report a Bug | By Email