[ire] CSV and RFC4180

Gustavo Lozano <gustavo.lozano@icann.org> Thu, 13 December 2012 18:00 UTC

Return-Path: <gustavo.lozano@icann.org>
X-Original-To: ire@ietfa.amsl.com
Delivered-To: ire@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F59E21F8A86 for <ire@ietfa.amsl.com>; Thu, 13 Dec 2012 10:00:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x8pxFr1oAu2Y for <ire@ietfa.amsl.com>; Thu, 13 Dec 2012 10:00:10 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id AA10721F8A0B for <ire@ietf.org>; Thu, 13 Dec 2012 10:00:10 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Thu, 13 Dec 2012 10:00:10 -0800
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: "ire@ietf.org" <ire@ietf.org>
Date: Thu, 13 Dec 2012 10:00:11 -0800
Thread-Topic: CSV and RFC4180
Thread-Index: Ac3ZW7D9ufs4LNVoS7qVrGt6cHeCeQ==
Message-ID: <CCEF57AB.69E1%gustavo.lozano@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.5.121010
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [ire] CSV and RFC4180
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ire>, <mailto:ire-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ire>
List-Post: <mailto:ire@ietf.org>
List-Help: <mailto:ire-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ire>, <mailto:ire-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 18:00:11 -0000

Colleagues,

I find the proposal of Comma-Separated Values (CSV) Objects Mapping
interesting and I think that both approaches CSV or XML for escrow data
have its advantages and disadvantages.

The only RFC related to CSV that I have found is RFC4180.

This text from RFC4180 concerns me:
TEXTDATA =  %x20-21 / %x23-2B / %x2D-7E

The escrow deposit will contain non US-ASCII data.

How can we be sure that the libraries/database tools used to implement the
export/import of CSV will adequately work with non US-ASCII data? There
are different platforms and architectures used by different players
(EBEROs, registry operators and data escrow agents) that will be upgraded
and will evolve during time.

In this regard I feel more confortable with XML because Unicode support
have been present since the beginning.

Thoughts?

Regards,
Gustavo Lozano