To:
"Andrew Newton" <andy@hxr.us>, "Andrew Sullivan" <andrew@ca.afilias.info>
Cc:
<ietf-provreg@cafax.se>
From:
"Dan Maharry" <dan@mcd.coop>
Date:
Mon, 27 Feb 2006 17:54:00 -0000
Content-class:
urn:content-classes:message
Sender:
owner-ietf-provreg@cafax.se
thread-index:
AcY7xVH5OniNS2a8RFq8Sp+GTXuizwAAUccg
thread-topic:
[ietf-provreg] Registry Escrow Information as EPP Spec?
Subject:
RE: [ietf-provreg] Registry Escrow Information as EPP Spec?
Last I looked, my escrow doc needs to be zipped up with PGP anyway, which is programmable, so yes it would be smaller. If you're doing the escrow for .com though, small is relative :) -----Original Message----- From: owner-ietf-provreg@cafax.se [mailto:owner-ietf-provreg@cafax.se] On Behalf Of Andrew Newton Sent: 27 February 2006 17:17 To: Andrew Sullivan Cc: ietf-provreg@cafax.se Subject: Re: [ietf-provreg] Registry Escrow Information as EPP Spec? On Feb 27, 2006, at 10:49 AM, Andrew Sullivan wrote: > But note the problem with doing this in XML: for any largish database > with heavy traffic, you're already looking at _at least_ megabytes of > deposit data. I'm not totally convinced that the benefits of XML in > this instance outweigh the considerable additional cost in chattiness. Admittedly, XML is verbose. However, you should be able to easily achieve 10:1 compression with standard gzip libraries. For one of my DNS zone scanning projects, I generate 8GB XML files which compress down to 700MB with no problems. -andy ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________