ripe-167

------- Forwarded Message
Received: (qmail 4673 invoked from network); 12 Nov 1997 19:52:28 -0000
Received: from ncc.ripe.net (193.0.0.129)
by postman.ripe.net with SMTP; 12 Nov 1997 19:52:28 -0000
Received: from AlphaSite.ukrpack.net by ncc.ripe.net with SMTP
id AA27124 (5.65a/NCC-2.41); Wed, 12 Nov 1997 20:52:27 +0100
Received: from sasha.ukrpack.net (amilutin.ukrpack.net [195.230.150.72]) by Alp
haSite.ukrpack.net (8.6.8.1/SCA-6.6) with ESMTP
id TAA27982 for <local-ir at ripe.net>; Wed, 12 Nov 1997 19:52:01 GMT
Return-Path: <amilutin at ukrpack.net>
Message-Id: <199711121952.TAA27982 at AlphaSite.ukrpack.net>
From: "amilutin" <amilutin at ukrpack.net>
To: <local-ir at ripe.net>
Subject: Re: ripe-167
Date: Wed, 12 Nov 1997 21:46:26 +0200
X-Msmail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
Mime-Version: 1.0
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
With regard to the language; mostly dealing with the Registry comes down to
a sending a template which is, if properly filled in, answered by a short
message. Other then that you very seldom need any language at all. If the
language is still a problem then RosNIIROS would have to produce Russian
language set of documents and templates and further Russian language set of
standards, something like RIPN167 instead of RIPE167. What then about the
entries in databases which are used, by many organizations worldwide as the
information source for their routing policy. So it looks like the usage of
English is still inevitable. Though, translations of documents with
explanations would definitely be of some help for some administrators of
newly created ISPs.
Kind Regards,
Alexander Milutin,
INFOCOM,
Kiev, Ukraine
------- End of Forwarded Message