I18N (was: Re: (dictionary or not) Re: [dtn-security] 00 version of the Bundle Security Protocol Spec.)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 26 May 2005 13:58 UTC

Received: from smtp3.tcd.ie (smtp3.tcd.ie []) by webbie.berkeley.intel-research.net (8.11.6/8.11.6) with ESMTP id j4QDwDV06832 for <dtn-security@mailman.dtnrg.org>; Thu, 26 May 2005 06:58:13 -0700
Received: from Vams.smtp3 (smtp3.tcd.ie []) by smtp3.tcd.ie (Postfix) with SMTP id 9B91214C047; Thu, 26 May 2005 14:58:07 +0100 (IST)
Received: from smtp3.tcd.ie ([]) by smtp3.tcd.ie ([]) with SMTP (gateway) id A00360938FF; Thu, 26 May 2005 14:58:07 +0100
Received: from [] (sfarrel2.dsg.cs.tcd.ie []) by smtp3.tcd.ie (Postfix) with ESMTP id 63AAC14C047; Thu, 26 May 2005 14:58:07 +0100 (IST)
Message-ID: <4295D6E6.2010503@cs.tcd.ie>
Date: Thu, 26 May 2005 15:02:14 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dtn-security@mailman.dtnrg.org
Cc: "Susan F. Symington" <susan@mitre.org>, "'Howard Weiss'" <howard.weiss@sparta.com>
Subject: I18N (was: Re: (dictionary or not) Re: [dtn-security] 00 version of the Bundle Security Protocol Spec.)
References: <200505241854.j4OIsx724035@smtp-bedford-dr.mitre.org> <42944BEF.7090007@cs.tcd.ie> <20050525152359.GB7633@pisco.cs.berkeley.edu> <42949AA1.5080108@cs.tcd.ie> <20050525153739.GA14911@pisco.cs.berkeley.edu> <42949E57.9000309@cs.tcd.ie> <20050525163945.GC14911@pisco.cs.berkeley.edu> <4294AC82.3060705@jpl.nasa.gov>
In-Reply-To: <4294AC82.3060705@jpl.nasa.gov>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiVirus-Status: Checked by TCD Vexira. (version=1.55.010 VDF=8.731)
X-AntiVirus-Status: NONE
X-AntiVirus-Status: Action Taken:
X-AntiVirus-Status: Host: smtp3.tcd.ie
X-AntiVirus-Status: MessageID = A10360938FF
Sender: dtn-security-admin@mailman.dtnrg.org
Errors-To: dtn-security-admin@mailman.dtnrg.org
X-BeenThere: dtn-security@mailman.dtnrg.org
X-Mailman-Version: 2.0.13
Precedence: bulk
Reply-To: dtn-security@mailman.dtnrg.org
List-Unsubscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=unsubscribe>
List-Id: DTN Security Discussion <dtn-security.mailman.dtnrg.org>
List-Post: <mailto:dtn-security@mailman.dtnrg.org>
List-Help: <mailto:dtn-security-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=subscribe>
List-Archive: <http://mailman.dtnrg.org/pipermail/dtn-security/>

Scott Burleigh wrote:

> Michael Demmer wrote:
>>> Aha!  Ok, it can work that way so long as there're no I18N
>>> problems there (there aren't, right?).
>> Well -- we need to decide on what to do re I8N. My inclination is to
>> have the protocol just be in ASCII, and put the burden on the
>> application interface to go to/from some multibyte encoding when
>> interfacing with the application.
> I agree: the external representation locally exposed to applications and 
> users is where the internationalization is really needed.  On the wire I 
> don't think it's useful.

I disageee - endpoint IDs are v. likely to want to include
non-ASCII characters since they'll practically be used
to name things.

Furthermore the way we're farming out identifier scheme
standardisation (via IANA or RFCs or whatever) just
increases the liklihood that I18N will be needed.

Read stringprep to see how bad it gets! Talk to Paul Hoffmann
or someone else that knows if you want to hear to pain that
iDNS invovled.