Browse Prior Art Database

Terminology Used in Internationalization in the IETF (RFC6365)

IP.com Disclosure Number: IPCOM000213053D
Publication Date: 2011-Dec-02

Publishing Venue

The IP.com Prior Art Database

Related People

P. Hoffman: AUTHOR [+2]

Abstract

As the IETF Character Set Policy specification [RFC2277] summarizes: "Internationalization is for humans. This means that protocols are not subject to internationalization; text strings are." Many protocols throughout the IETF use text strings that are entered by, or are visible to, humans. Subject only to the limitations of their own knowledge and facilities, it should be possible for anyone to enter or read these text strings, which means that Internet users must be able to enter text using typical input methods and have it be displayed in any human language. Further, text containing any character should be able to be passed between Internet applications easily. This is the challenge of internationalization.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                        P. Hoffman Request for Comments: 6365                                VPN Consortium BCP: 166                                                      J. Klensin Obsoletes: 3536                                           September 2011 Category: Best Current Practice ISSN: 2070-1721

           Terminology Used in Internationalization in the IETF

Abstract

   This document provides a list of terms used in the IETF when    discussing internationalization.  The purpose is to help frame    discussions of internationalization in the various areas of the IETF    and to help introduce the main concepts to IETF participants.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6365.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

 Hoffman & Klensin         Best Current Practice                 [Page 1]
 RFC 6365            Internationalization Terminology      September 2011

 Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

     1.1.  Purpose of this Document . . . . . . . . . . . . . . . . .  3

     1.2.  Format of the Definitions in This Document . . . . . . . .  4

     1.3.  Normative Terminology  . . . . . . . . . . . . . . . . . .  4

   2.  Fundamental Terms  . . . . . . . . . . . . . . . . . . . . . .  5

   3.  Standards Bodies and Standards . . . . . . . . . . . . . . . . 10

     3.1.  Standards Bodies . . . . . . . . . . . . . . . . . . . . . 11

     3.2.  Encodings and Transformation Formats of ISO/I...