idnits 2.17.1 draft-rfced-info-tkachuk-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://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. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 1) being 64 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 2 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 4 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 1997) is 9689 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '1' is defined on line 119, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 121, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 1489 (ref. '1') ** Downref: Normative reference to an Informational RFC: RFC 1345 (ref. '2') Summary: 12 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT EXPIRES APR 1998 INTERNET DRAFT 2 Network Working Group R. Tkachuk 3 Internet Draft BitterNet 4 October 1997 6 Ukrainian Code Page KOI8-U 7 9 Status of This Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its 13 areas, and its working groups. Note that other groups may also 14 distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- 19 Drafts as reference material or to cite them other than as 20 "work in progress." 22 To learn the current status of any Internet-Draft, please check 23 the "1id-abstracts.txt" listing contained in the Internet- 24 Drafts Shadow Directories on ftp.is.co.za (Africa), 25 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 26 ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). 28 Distribution of this document is unlimited. 29 2. Abstract 31 This memo is the specification of the code page, which was originally 32 developed for the transmission of texts in the Ukrainian language 33 through networks, and in particular the networks, employing Unix 34 operating systems. It is, however, operating-system-neutral, and is 35 used in various situations, just as its Russian language counterpart 36 KOI-8R. 38 With some minor exceptions, this specification can be considered 39 to be an extension of KOI8-R (RFC-1489). The present edition of the 40 specification is the result of the wide concensus reached after many 41 prolonged exchanges and discussions, which took place in Ukraine and 42 on some Usenet conferences covering Ukraine and read by the public 43 who employs the Ukrainian language. 45 3. Relation to other RFCs 47 This memo should be used in conjunction with RFC-1489, which is an 48 official description of a Cyrillic character set, adapted and 49 adopted for the Russian language, as well as with RFC-1345, 50 ISO10646 (Unicode) and ISO 8859-5. 52 4. Specification 54 The lower (7-bit) part of the Code Page KOI8-U is a perfect copy 55 of ASCII, just as is the case with KOI-8R and the vast majority of 56 other codepages. 58 I/D Ukrainian Code Page KOI-8U October 1997 60 The upper (8-bit) part of the KOI-8U Code Page is compatible with 61 all the symbols of Cyrillic alphabet used in KOI-8R, and adds 62 four (4) pairs of symbols, specific to the Ukrainian alphabet. 64 65 AD 0491 CYRILLIC SMALL LETTER GHE WITH UPTURN 66 A4 0454 CYRILLIC SMALL LETTER UKRAINIAN IE 67 A6 0456 CYRILLIC SMALL LETTER BELORUSSIAN-UKRAINIAN I 68 A7 0457 CYRILLIC SMALL LETTER UKRAINIAN YI 69 B4 0404 CYRILLIC CAPITAL LETTER UKRAINIAN IE 70 B6 0406 CYRILLIC CAPITAL LETTER BELORUSSIAN-UKRAINIAN I 71 B7 0407 CYRILLIC CAPITAL LETTER UKRAINIAN YI 72 BD 0490 CYRILLIC CAPITAL LETTER GHE WITH UPTURN 74 Official two-letter abbreviations for three pairs of these symbols 75 are defined in RFC 1345, "Character Mnemonics & Character Sets", 76 June 1992 78 IE 0404 CYRILLIC CAPITAL LETTER UKRAINIAN IE 79 II 0406 CYRILLIC CAPITAL LETTER BYELORUSSIAN-UKRAINIAN I 80 YI 0407 CYRILLIC CAPITAL LETTER YI (Ukrainian) 81 ie 0454 CYRILLIC SMALL LETTER UKRAINIAN IE 82 ii 0456 CYRILLIC SMALL LETTER BYELORUSSIAN-UKRAINIAN I 83 yi 0457 CYRILLIC SMALL LETTER YI (Ukrainian) 85 These Ukrainian symbols replace the following rarely used symbols 86 present in the KOI8-R table: 88 89 A4 FORMS DOWN DOUBLE AND RIGHT SINGLE 90 A6 FORMS DOWN SINGLE AND LEFT DOUBLE 91 A7 FORMS DOWN DOUBLE AND LEFT SINGLE 92 AD FORMS UP DOUBLE AND LEFT SINGLE 93 B4 FORMS VERTICAL DOUBLE AND LEFT SINGLE 94 B6 FORMS DOWN SINGLE AND HORIZONTAL DOUBLE 95 B7 FORMS DOWN DOUBLE AND HORIZONTAL SINGLE 96 BD FORMS VERTICAL DOUBLE AND HORIZONTAL SINGLE 98 5. Background 100 The specification given in this standard was adopted officially 101 by a conference of postmasters of Ukrainian Internet Service 102 Providers in the town of Slavsk (a resort in the Carpathian 103 Mountains) during the autumn of 1992, from submissions by Igor 104 Sviridov from Kiev and Stas Vorony from Xarkiv. The original 105 specification lacked the symbol pair for the letter GHE WITH 106 UPTURN; this was added by Igor Sviridov in June 1995. 107 The generic KOI-8 Code Page, or, more precisely, KOI-8/KOI-7 108 character sets, trace their origin from the mainframe and Unix 109 worlds of the 1970's. The three letter mnemonic stands for "Code 110 of Information Exchange" (Kod Obminu Informacieu). One of the 111 rationales for its creation was that, as the KOI-8 character set 112 becomes KOI-7 if the 8th bit is lost, the transmitted text remains 113 somewhat readable in KOI-7, with an arguable degree of convenience. 115 I/D Ukrainian Code Page KOI-8U October 1997 117 6. References 119 [1] A. Chernov, "Registration a Cyrillic Character Set", RFC 1489, 120 July 1993 121 [2] K. Simonsen, "Character Mnemonics & Character Sets" RFC 1345, 122 June 1992 124 7. Author's Address 126 Roman A. Tkacuk 127 BitterNet 128 Ternopil, Ukraine 130 E-mail: roman@bit.ternopil.ua 132 Mykola Sereda 133 Gerelo Intercontinental 134 Monreal, Canada 136 E-mail: gerelo@cam.org 138 INTERNET DRAFT EXPIRES APR 1998 INTERNET DRAFT