jefsey at jefsey.com
Thu Apr 21 13:49:31 CEST 2011
Barry Leiba, WG/APPSAWG Chair has sent the following most important
mail for us:
>"Paul Hoffman and John Klensin have undertaken to update RFC 3536,
>which specified terminology for use in internationalization-related
>documents and discussions. The editors, appsawg chairs, and
>Applications Area directors think the document needs broad review,
>and propose to make it an appsawg document.
>You can find the document here:
>The editors will soon submit an updated version, and await a
>decision on accepting the document into appsawg before doing
>that. We ask that anyone with a stake in internationalization
>review the current version and state any objections to making this
>an appsawg document by 29 April.
>You may, or course, also send comments on the document at this point
>to the editors and/or the apps-discuss list. Remember that there
>are changes queued, so you might bring up points that they're
>already planning to change/correct.
>The reply-to on this message is set to the apps-discuss list
><apps-discuss at ietf.org>. Please put all responses and discussion there.
This terminology is obviously going to be the mutual understanding
bridge between the IETF and the IUTF communities.
http://iucg.org/wiki/Wiki_RFC_3536bis is the traditional wiki working
transcript (unfinished as yet) of the proposed draft.
This is in line with my own I_D on orthotypography:
I suggest thet our target should be :
1. to make sure RFC 3536bis by APPSAWG is in line with our own
understanding of the terms in our own working contexts (IDNA2008,
ML-DNS, IUI, EST).
2. to build our own Internet extension section to document in a
similar manner the emergent IUse terminology. This section should not
document any concept than the way we read and use the existing
"Internal Internet" technology (i.e. no bit change).
3. to continue building in contnuity our own dictionnary of the new
IUI and Intersem (semiotic/semantic Intercomprehension network) stratum.
NB: due to personal constraints that should now progressively reduce
I was not able to sustain my post-IDNA2008 endeavour as I planned it.
Some terminology used in this mail is not therefore as common and
supported by operational prototypes as our little group hoped. Thank
you to read the used acronyms/terms as follows:
- IDNA2008: as documented by RFC 5890 to 5895
- ML-DNS: multilayer DNS (of which layer 1 is the Internal Internet
DNS, layer 2 is IDNA2008).
- IUI: Intelligent Use Interface (Internet Use Interface from an
Internet perspective). i.e. a generalization of principle introduced
by Paul Hoffman and Pete Resnick in RFC 5895 and a stable optional
response to problems discussed by the IAB in RFC 6055
- IUse: an emergent community interested in an open general
Intelligent Use of the world digital ecosystem (whatever the
- EST: Extended System Theory, a glogalization of the General System
Theory which includes networking and interfaces and is necessary to
better read the IETF RFCs in an IUse perspective.
- IUTF: Intelligent Use Task Force, TF under formation further to the
responses to the appeals to IESG and IAB following the successfull,
but not documented yet as such, introduction of the principle of
subsidiarity (IDNA2008) as the third internet architectural principle
(RFC 1958: principle of permanent change, RFC 3439: principle of
simplicity). I note that subsidiairity should come with suppleance (I
did not found so far an English equivalent for the core to support
peripheral difficulties) and precaution.
- Dictionnary (http://iucg.org/wiki/Dictionnary): this IUCG project
to integrate digital ecosystem convergence and ALFA (Free Acrchitecture) words.
More information about the Idna-update