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

Scott Burleigh <Scott.Burleigh@jpl.nasa.gov> Wed, 25 May 2005 16:50 UTC

Received: from nmta1.jpl.nasa.gov (nmta1.jpl.nasa.gov [137.78.160.214]) by webbie.berkeley.intel-research.net (8.11.6/8.11.6) with ESMTP id j4PGoKV31356 for <dtn-security@mailman.dtnrg.org>; Wed, 25 May 2005 09:50:20 -0700
Received: from xmta1.jpl.nasa.gov (xmta1.jpl.nasa.gov [137.78.160.144]) by nmta1.jpl.nasa.gov (Switch-3.1.7/Switch-3.1.7) with ESMTP id j4PGoEWq025316; Wed, 25 May 2005 09:50:14 -0700
Received: from [137.79.22.227] (dhcp-79-22-227.jpl.nasa.gov [137.79.22.227]) by xmta1.jpl.nasa.gov (Switch-3.1.7/Switch-3.1.7) with ESMTP id j4PGoD7l002315; Wed, 25 May 2005 09:50:14 -0700
Message-ID: <4294AC82.3060705@jpl.nasa.gov>
Date: Wed, 25 May 2005 09:49:06 -0700
From: Scott Burleigh <Scott.Burleigh@jpl.nasa.gov>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
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: 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>
In-Reply-To: <20050525163945.GC14911@pisco.cs.berkeley.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: dhcp-79-22-227.jpl.nasa.gov [137.79.22.227]
X-Source-Sender: Scott.Burleigh@jpl.nasa.gov
X-AUTH: Internal IP
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/>

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.

Scott