Subject: [precis] draft-blanchet-precis-framework-00.txt

From: Marc Blanchet <[email-masked]>
Date: Mon, 05 Jul 2010 16:37:43 -0400

Hello,
  I just submitted one approach to precis framework. The rationale here 
is that usage of i18n strings in protocols would most likely be grouped 
into a few classes of strings.

Therefore, the proposed idea is to define these classes, and then create 
a variation of the IDNA2008 algorithm to support these classes.

Currently, as a strawman, I've (loosely) defined:
- RI:restricted identifier(typical i18n usernames) and
- LRI less-restrictive identifiers: RI + displayable chars.

The IDNA2008 is then augmented by having PVALID, RI_PVALID, LRI_PVALID, 
and possibly DISALLOWED, RI_DISALLOWED, LRI_DISALLOWED.

The intent here is that customers of precis would just reference the 
string class they choose from the available set and "nothing else"... 
Having a few classes would benefit with high code share, end-user 
similar expectations, protocol friends using same classes, etc...

This document is incomplete and incorrect but would like to see if the 
overall approach would make sense before digging into specific string 
classes and algorithms.

Marc (I'll be on/offline for the next 2 weeks, so RTT may be longer).

Le 10-07-05 16:30, [email-masked] a écrit :
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
> 	Title           : Precis Framework: Handling Internationalized Strings in Protocols
> 	Author(s)       : M. Blanchet
> 	Filename        : draft-blanchet-precis-framework-00.txt
> 	Pages           : 20
> 	Date            : 2010-07-05
>
> Using Unicode codepoints in protocol strings requires preparation of
> the string.  This document describes the Precis Protocol Framework
> that prepares various classes of strings used in protocol elements.
> A protocol specification chooses a class of strings and then
> implements the corresponding preparation steps described in this
> document.  This document is based on the IDNAbis approach.  It
> obsoletes the Stringprep algorithm.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-blanchet-precis-framework-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
>
> _______________________________________________
> I-D-Announce mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca