Re: IANA Update: Project to convert registries to XML

Michelle Cotton <michelle.cotton@icann.org> Mon, 21 July 2008 21:27 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E77B28C0F9; Mon, 21 Jul 2008 14:27:20 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0133E3A694B for <ietf@core3.amsl.com>; Mon, 21 Jul 2008 14:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 R7JhOncXiQxg for <ietf@core3.amsl.com>; Mon, 21 Jul 2008 14:27:19 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 00C7328C110 for <ietf@ietf.org>; Mon, 21 Jul 2008 14:27:18 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.233]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Mon, 21 Jul 2008 14:27:59 -0700
From: Michelle Cotton <michelle.cotton@icann.org>
To: James Cloos <cloos@jhcloos.com>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date: Mon, 21 Jul 2008 14:27:51 -0700
Subject: Re: IANA Update: Project to convert registries to XML
Thread-Topic: IANA Update: Project to convert registries to XML
Thread-Index: AcjrcKr0yzEHurL5SuSwU19rTU7BsgAB/YPq
Message-ID: <C4AA4D67.1CB37%michelle.cotton@icann.org>
In-Reply-To: <m3hcaj7zge.fsf@lugabout.jhcloos.org>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0394885932=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

FTP access to the assignments directory has been restored.  It may take up to 24 hours to properly resolve ftp.iana.org.

As James mentioned in his message below, rsync was never operational, however we plan to make that available in the next few weeks.
We are also working on other new services such as the ability to subscribe to be notified when specific registries are updated.

Thanks again for the feedback.

Michelle Cotton
IANA



On 7/21/08 1:29 PM, "James Cloos" <cloos@jhcloos.com> wrote:

>>>>> "Stephane" == Stephane Bortzmeyer <bortzmeyer@nic.fr> writes:

Stephane> Why a dVCS? Any VCS would make it, and Subversion, for
Stephane> instance, would be a good choice. If we use a dVCS,

More efficient.  Everything works better with local history.  Svn wastes
a lot of disk by keeping two copies of every file in each checkout.  At
least a dVCS can compress the store.

Stephane> I vote for darcs.

Doesn't darcs have a bug they can't fix?  esr's recent survey of the
dVCSs concluded that git, hg and bzr are the best choices.  He
considered performance, as well as community involvement and how many
other projects are using each dVCS, on the theory that bugs get fixed
faster when more people use it.

-JimC

(As a side note, my initial mention of rsync breaking was a misnomer.
My rsync job only grabs rfcs and i-ds.  I had conflated that with a
request I sent some months (years?) back to make ftp.iana.org rsyncable.
It is only ftp which hadn't been updated since April.  And in a off-list
reply IANA said they plan to fix that.)

--
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf