I-D Action: draft-bormann-dispatch-modern-network-unicode-04.txt
internet-drafts@ietf.org Thu, 29 February 2024 18:38 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 292EEC14F6BC for <i-d-announce@ietf.org>; Thu, 29 Feb 2024 10:38:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-bormann-dispatch-modern-network-unicode-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 12.6.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170923189915.21897.10631500679090282923@ietfa.amsl.com>
Date: Thu, 29 Feb 2024 10:38:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/Ti2iIkWBnMSqpL2AxaQtK4wEqgI>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Feb 2024 18:38:19 -0000
Internet-Draft draft-bormann-dispatch-modern-network-unicode-04.txt is now available. Title: Modern Network Unicode Author: Carsten Bormann Name: draft-bormann-dispatch-modern-network-unicode-04.txt Pages: 16 Dates: 2024-02-29 Abstract: BCP18 (RFC 2277) has been the basis for the handling of character- shaped data in IETF specifications for more than a quarter of a century now. It singles out UTF-8 (STD63, RFC 3629) as the "charset" that MUST be supported, and pulls in the Unicode standard with that. Based on this, RFC 5198 both defines common conventions for the use of Unicode in network protocols and caters for the specific requirements of the legacy protocol Telnet. In applications that do not need Telnet compatibility, some of the decisions of RFC 5198 can be cumbersome. The present specification defines "Modern Network Unicode" (MNU), which is a form of RFC 5198 Network Unicode that can be used in specifications that require the exchange of plain text over networks and where just mandating UTF-8 may not be sufficient, but there is also no desire to import all of the baggage of RFC 5198. As characters are used in different environments, MNU is defined in a one-dimensional (1D) variant that is useful for identifiers and labels, but does not use a structure of text lines. A 2D variant is defined for text that is a sequence of text lines, such as plain text documents or markdown format. Additional variances of these two base formats can be used to tailor MNU to specific areas of application. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-bormann-dispatch-modern-network-unicode/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-bormann-dispatch-modern-network-unicode-04.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-bormann-dispatch-modern-network-unicode-04 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
- I-D Action: draft-bormann-dispatch-modern-network… internet-drafts