IETF Logo Mail Archive

Re: [weirds] I-D Action: draft-blanchet-weirds-bootstrap-ianaregistries-00.txt

Marc Blanchet <marc.blanchet@viagenie.ca> Tue, 25 June 2013 13:16 UTC

Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2279321F9B84 for <weirds@ietfa.amsl.com>; Tue, 25 Jun 2013 06:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level:
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZQgGyHEyiZtF for <weirds@ietfa.amsl.com>; Tue, 25 Jun 2013 06:16:44 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 90D9121F9A95 for <weirds@ietf.org>; Tue, 25 Jun 2013 06:16:44 -0700 (PDT)
Received: from [IPv6:2620:0:230:2002::1001] (unknown [IPv6:2620:0:230:2002::1001]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 88EFA40425; Tue, 25 Jun 2013 09:16:42 -0400 (EDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <011901ce714b$ed4dfc40$c7e9f4c0$@cn>
Date: Tue, 25 Jun 2013 09:16:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <529D1301-BF28-41E6-951A-757AAC8EAAC9@viagenie.ca>
References: <CDEDEC2F.278C9%bje@apnic.net> <alpine.BSF.2.00.1306240026490.16990@joyce.lan> <011901ce714b$ed4dfc40$c7e9f4c0$@cn>
To: Linlin Zhou <zhoulinlin@cnnic.cn>
X-Mailer: Apple Mail (2.1508)
Cc: "'John R. Levine'" <johnl@iecc.com>, 'John R Levine' <johnl@taugh.com>, weirds@ietf.org
Subject: Re: [weirds] I-D Action: draft-blanchet-weirds-bootstrap-ianaregistries-00.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 13:16:45 -0000

Le 2013-06-24 à 22:30, "Linlin Zhou" <zhoulinlin@cnnic.cn> a écrit :

>> 
>> It's perfectly possible to represent the allocation information in a
> compact and
>> efficiently searchable form (it is, after all, on three pages at IANA),
> but not by
>> using the formats that the DNS provides.  The number bootstrap data
>> changes very rarely, like once a year or less, so it's OK for the update
> not to be
>> automatic.  Hence the per-TLD DNS lookup for the regularly named but
>> frequently updated and uncoordinated DNS registries, and the vague
> baked-in
>> bootstrap hack for the irregularly named, but rarely updated and well
>> coordinated RIRs.
>> 
> I agree with John. I think it is better to use a local table or file for
> numbers bootstrap and update when necessary. We've already adopted this
> method.

The "local table or file" has to come from somewhere. And the right place is IANA registry.  So the specification should tell you where to get the data. The implementation may decide to fetch it more or less frequently, such as software updates or more frequently. THis is implementation choice.  So the whole point of using the IANA registry is to ensure that everybody is taking the right source of information at the right place.

Marc.

> 
>> Does that make more sense?
>> 
>> R's,
>> John
> 
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds

v2.23.0 | Report a Bug | By Email