Instructions to RFC Translators
draft-ohta-translation-instr-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Masataka Ohta | ||
| Last updated | 1994-08-24 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
A framework is given to coordinate the worldwide effort of RFC translation into various languages. Translated RFCs will be encoded in 7bit ISO 2022 and will have a name 'TRFC NNNN-LLL-MM' where 'NNNN' is the RFC number of the original RFC, 'LLL' is the language tag and 'MM' is the sequence number to identify different translations. Formatting rules similar to ASCII RFCs are also described.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)