- ripe-list - mailman.ripe.net

What are the COSINE/CPMU in the Rare officie doing?
by Peter Lothberg 28 Sep '92

28 Sep '92

Some days ago, we all received a long document that looked like this; >NOTE: the document has been received September 8, 1992. > >------------------------------------------------------------------------------ > >COA (92)080 >T.Kalin >24.8.92 > RARE and RIPE / RIPE - NCC ....... >RIPE: > > RIPE should stay a technical IP coordinating body within RARE, but >having much more interaction with the RARE management, technical and >executive bodies (CoA, RTC, REC, Raresec) than in the past > according to its charter, RIPE should be serving wider population than >RARE membership > one should observe gradual merger (or at least very close cooperation) >between identical or related Working Groups of RARE and RIPE, leading to a >coordinated management of technical activities > RIPE should support establishment and utilisation of the EMPB, >particulary in the pilot phase, where the its expertise is crucially needed I have now learned through reliable sources that the EMPB/PTT-telecom is planning to subcontract "IP network Consulting" for EMPB to Softlabs. Another strange thing seems to be that the receiver was "Bruce Wallace at PTT telecom" I thought he was with the CPMU? This means that the IP-comunity of Europe will probably have a zero influence on the network, that are supposed to serve our comunity. And that CPMU totally ignores the skills of the Ripe comunity. We have to pay twice, as the skills of the coumunity are not used, and we have to pay the consultants on our taxes/charges! I might be wrong, if someone has better knowledge about this, please speak up. -Peter

2 1

RIPE DNS Hostcount September 1992
by Marten Terpstra 26 Sep '92

26 Sep '92

RIPErs, Below the DNS hostcount for September 1992. Remarks: - CS has a low count this month due to network reachability problems. I have tried two times more to count CS, but with the same result. - IT also has this problem, a few hundred hosts less due to network reachability problems. - PT has the same problem, although on a smaller scale. Also tried two times more, with the same result. - DE really takes off now, they are the first to reach 50,000+. - Overall another nice increase of just over 10,000 to reach 230,000 plus. - This count was done a bit earlier in the month than usual, but I needed the output for our 2nd Quarterly Report, and for the coming RIPE meeting ;-) - Next month we will start doing some tests with distributed counting. Some people have agreed to do the count for their own country within the country, and make the results available to me. This should decrease the influence of network and link outages, and increase the count even further. - All output can again be found on ftp.ripe.net:/ripe/hostcount. Check the README for details. Previous counts can be found in subdirectory History. - The total history has been appended again. You will find it below the hostcount. Enjoy, -Marten RIPE DNS Hostcount Previous Count : Mon Aug 31 1992 This Count : Sat Sep 26 1992 CY SOA COUNTED DUPL REAL CHANGE ============================================================ al 1 0 0 0 0 at 165 7055 45 7010 + 205 be 21 1574 57 1517 + 60 bg 1 0 0 0 0 by 0 0 0 0 0 ch 94 19586 180 19406 + 1624 cs 3 11 0 11 - 613 de 881 53382 1104 52278 + 4662 dk 71 4404 39 4365 + 1291 dz 0 0 0 0 0 ee 7 57 0 57 + 20 es 156 4280 82 4198 + 364 fi 134 17387 150 17237 + 369 fr 292 19740 167 19573 + 410 gb 1 2 0 2 + 1 gr 45 671 137 534 + 57 hr 0 0 0 0 0 hu 4 121 2 119 + 86 ie 23 843 4 839 + 176 is 10 556 6 550 + 104 it 169 4976 194 4782 - 192 il 41 3238 139 3099 + 253 lt 1 0 0 0 0 lu 5 79 1 78 0 lv 1 0 0 0 0 nl 233 21611 373 21238 + 40 no 311 15683 213 15470 + 601 pl 54 678 9 669 + 4 pt 47 1381 22 1359 - 26 ro 0 0 0 0 0 se 341 22996 194 22802 + 1065 si 1 0 0 0 0 su 127 29 1 28 + 2 tn 2 9 0 9 0 ua 0 0 0 0 0 uk 310 38353 3072 35281 + 10 va 0 0 0 0 0 yu 2 11 0 11 - 2 ============================================================ 3554 238713 6191 232522 +10571 History Oct 1990 31724 Nov 1990 33665 Dec 1990 29230 Jan 1991 43832 Feb 1991 - Mar 1991 44506 Apr 1991 46948 May 1991 - Jun 1991 63267 Jul 1991 - Aug 1991 73069 Sep 1991 92834 Oct 1991 104824 Nov 1991 129652 Dec 1991 - Jan 1992 - Feb 1992 161434 Mar 1992 167939 Apr 1992 170050 May 1992 182528 Jun 1992 196758 Jul 1992 213017 Aug 1992 221951 Sep 1992 232522

1 0

Re: Japanese Public IP providers
by konish＠kddnews3.kddlabs.co.jp 25 Sep '92

25 Sep '92

>Subject: Japanese Public IP providers >From: Peter Houlder <Peter.Houlder(a)uknet.ac.uk> >Date: Fri, 25 Sep 92 10:12:35 +0100 >Message-Id: <5723.717412355(a)uknet.ac.uk> >Sender: Peter.Houlder(a)uknet.ac.uk > > >I have been asked by a UK company with Japanese contacts if >Japan can offer public IP facilities, so that a user in the >UK could speak IP with a Japanese site. I have no clear >indication of the commercial/research/academic status of the >Japanese site, so a general reply stating the alternatives >would be appreciated. > >All information gratefully received. > >Peter Houlder > There is NOT a commercial IP provider in Japan now. There are a few research/academic IP networks in Japan now. The biggest one is WIDE-internet, the owner of which is jun(a)wide.ad.jp. He is a professor of Keio University. We, KDD have operated a UUCP public international gateway for more than seven years, but the regulation for the leased circuit prevents us serving IP connectivity. We have about 250 companies as members. jun(a)wide.ad.jp and KDD have begun to examine a commercial IP provider. We are endeavouring to set up a new company this year, and it will provide a public commercial IP connectivity from January, 1993. KDD will be a big stock-holder, but the details are negotiating. The new provider will have an IP link to Europe via U.S.A. Thanks in advance, Kazunori Konishi

1 0

IETF/IESG Information Architecture
by Greg Vaudreuil 25 Sep '92

25 Sep '92

The announcements of the four Working Groups were sent to the IETF mailing list. For instructions to retreive the charters from anonymous FTP sites or by mail, please send a message to ietf-info(a)nri.reston.va.us. Greg Vaudreuil ------- Forwarded Message Date: Thu, 24 Sep 92 17:55:13 -0400 From: Greg Vaudreuil <gvaudre(a)NRI.Reston.VA.US> To: IETF-Announce: ; Subject: IESG Information Architecture In Following messages, the IESG will announce several new Working Groups in the User Services and Applications Areas chartered to integrate Internet Information services. Below is a draft statement of the architectural framework written by the Working Group chairs and the Area Directors as part of the chartering process. For more information, please contact Joyce Reynolds or Russ Hobby. Greg Vaudreuil IESG Secretary. "Integrated Information Architecture" (Revised 9/15/92) Many new networked services to identify, access, and retrieve information resources have sprung up in the last several years -- archie, WAIS, and Netfind, to name only three. Now, much as the Internet has tied many disparate networks together into an integrated system, the pressing problem is how to integrate these many new services into a single coordinated Internet information naming, discovery, and retrieval system. There are three vital areas of this integration effort that the IESG is interested in pursuing: 1) The identification, cataloging, and documentation of networked information services, new and old. 2) The standardization of descriptions and identification schemes for networked resources, and the distribution and implementation of these identifiers. 3) The integration and interoperability of the various new information services. To this end, the IESG is creating three new working groups: 1) Networked Information Retrieval (NIR) -- NIR will work on the first issue above by identifying, cataloging, and documenting networked information services. The result will be a published catalog of network information retrieval services. In addition, NIR will liaise with other organizations working on this goal, such as RARE ISUS and CNI. 2) Uniform Resource Identifiers (URI) -- URI will concentrate on the second issue above, particularly on the standardization and implementation of identification schemes for networked resources. There will be two primary components in this effort: a Uniform Resource Locator (URL) which is a string which tells how to locate a document. The second part is a Universal Resource Serial Number, which is used to uniquely identify a resource, so that one can, for example tell if two documents with different file names are, in fact, the same. The standard identification scheme developed by URI will be used by NIR to define the standard resource formats. 3) Integration of Internet Information Resources (IIIR) -- IIIR will work on the third issue by developing technical specifications and documentation for a) interoperation between the various information services and b) the integration of new information services into the existing CIM (combined information mesh). After the specifications for interoperation have been completed, IIIR will examine the need for additional protocols necessary to further integrate the CIM, including gateway protocols, query routing protocols, and other mechanisms. In addition to the above named groups, the IETF wishes to facilitate the standardization of descriptions and data formats for various specific information services by chartering single-protocol working groups which will work on this standardization. Examples of such groups are the Internet Anonymous FTP Archive group (IAFA), which is working on standardization of anonymous FTP archives, and the new Whois Network Information Lookup Service (WNILS), which is working on standardization of services using the WHOIS protocol. The IESG considers these WGs to be components of a single coordinated IETF effort to create an integrated Internet information architecture. Therefore, the chairs and membership of each group will be active participants in the other groups. The overall coordination of this effort will be under the joint management of the Applications and User Services Area. Due to the importance of an Integrated Internet Information Service Architecture, the IESG requests the working group chairs and the Applications and User Services area directors to jointly expand this brief overview into a more fully fleshed out architectural statement, and to issue periodic progress reports describing how the integrated information service is developing. ------- End of Forwarded Message

1 0

RE: Japanese Public IP providers
by ROBERT.D.COLLET＠sprint.sprint.com 25 Sep '92

25 Sep '92

Peter: at the current time there are no Commercial IP service providers in Japan. Consequently, there is no commercial infrastructure between the USA CIX members and Japan. Hopefully, that situation will change within the next few months. An interim measure would be for the customer in Japan to connect to an X.25 network which has connectivity to a USA Commercial Internet. Both SprintLink and PSInet utilize SprintNet for applications like this. I think UUnet uses Compuserve. Bob

1 0

Japanese Public IP providers
by Peter Houlder 25 Sep '92

25 Sep '92

Before I get flamed for not mailing ip-providers(a)ripe.net I should say that I am not clear if that list extends to outside of Europe hence my mailing ripe(a)ripe.net. I have been asked by a UK company with Japanese contacts if Japan can offer public IP facilities, so that a user in the UK could speak IP with a Japanese site. I have no clear indication of the commercial/research/academic status of the Japanese site, so a general reply stating the alternatives would be appreciated. All information gratefully received. Peter Houlder

1 0

Re: Found some sort of a clue... (fwd)
by Wilfried Maschtera 24 Sep '92

24 Sep '92

On Thu, 24 Sep 92 13:21:49 EET you said: Dear Colleagues, The entry for .BG points to MAILER(a)AEARN.As a result of the discussion in March MAILER@AEARN routes mail to the domain .BG to SMTP@AEARN. This requires a local supplement to the profile generator. On September, 22nd, I had to generate a new profile. Because of some reasons the changes to the local input were numerous. Unfortunately the entry for .BG in the local file was deleted causing a loop in the network mailer. The error is corrected. I apologize for this mistake. I am surpised to learn from Daniel's letter that this situation also existed during the last six months because nobody has complained between March 9th and September 22nd. I recommend to contact the sites involved if an error occurs to clarify the situation. To the situation in Bulgaria I can only repeat that AEARN does not interfere into this national affair and I ask Daniel to accept this now. Regards / Wilfried >I do not know if you are aware of it, but this did happen already >six months. I hope it would not continue to happen, because users >complain that they do not receive their mail, which is misrouted for >who knows what reasons to AEARN. > >The last story was that the Bulgarian Academy of Sciences claimed to >be the "international networking body" for Bulgaria, which is of >course just a funny statement. I would at least ask you to inform the >.BG top level domain administration if you decide to force route the >traffic somewhere. > >I would ask EARN once again to please not "borrow" the .BG top level >domain from Internet. If you do not know what to do with the mail, >simply route it to your nearest Internet gateway. Thanks! > >Sorry for the long Cc: list, but this problem should really be >solved. > >Sincerely, >Daniel Kalchev > >Forwarded message: >> Subject: Found some sort of a clue... >> Message-Id: <JOHNSON.920923165504(a)maine.maine.EDU> >> From: Johnson(a)Maine.Maine.Edu (Jay Johnson) >> To: daniel(a)danbo.uucp (Daniel Kalchev) >> Date: Wed, 23 Sep 92 16:55:04 EDT >> >> Apparently our mailer got an over-ride record from BITNET >> which directs BG traffic to AEARN. Our mailer treated my >> mail as subject to it and sent it to AEARN which, I guess, >> doesn't know how to get to danbo. >> The mx records are first to try forth.gr and then eu.net >> as I remember which seemed ok though I'd have thought the >> order would be reversed. >> So thought you'd like to know that sites which have BITNET >> as well as Internet links and mailers as dumb as ours may >> be giving grief. >> >

1 0

Re: Found some sort of a clue... (fwd)
by Hank Nussbacher 24 Sep '92

24 Sep '92

On Thu, 24 Sep 1992 14:46:54 +0200 you said: > For the future: let's try to have a little bit more cooperative > attitude, would you? If something goes wrong again: first contact > the AEARN people and *afterward* (if you still like) flame. >I don't remember having flamed you. It's the lack of response >and the background of the whole situation that made me flame; >and not flame those who happen to make a configuration error, >but those who demonstrate non-cooperativeness. > > > Piet Lack of response? I maintain the file that points .BG to AEARN. This afternoon is the first complaint I have heard about it - only after Daniel forwarded me a copy of the complaint. I am not able to read minds over the network - as soon as I got the mail, I forwarded a copy to the 2 people in Austria who are responsible for AEARN and within an hour you had a response from one of them. Can you be more specific with what you mean by "those who demonstrate non-cooperativeness". Having an unnoticed configuration problem in Austria for 2 days happens also to the best of us. Hank

2 1

Re: Found some sort of a clue... (fwd)
by Daniele Bovio 24 Sep '92

24 Sep '92

On Thu, 24 Sep 1992 13:49:17 +0200 you said: > I would ask EARN once again to please not "borrow" the .BG top > level domain from Internet. >So history repeats itself.... Why don't people want >to learn from hard experience? > we learn, dear Piet, we learn, but configuration problems may happen even in the best family, is't it? For the future: let's try to have a little bit more cooperative attitude, would you? If something goes wrong again: first contact the AEARN people and *afterward* (if you still like) flame. Thank you. > > Piet d.

2 1

Found some sort of a clue... (fwd)
by daniel＠digsys.bg 24 Sep '92

24 Sep '92

Dear Colleagues, I do not know if you are aware of it, but this did happen already six months. I hope it would not continue to happen, because users complain that they do not receive their mail, which is misrouted for who knows what reasons to AEARN. The last story was that the Bulgarian Academy of Sciences claimed to be the "international networking body" for Bulgaria, which is of course just a funny statement. I would at least ask you to inform the .BG top level domain administration if you decide to force route the traffic somewhere. I would ask EARN once again to please not "borrow" the .BG top level domain from Internet. If you do not know what to do with the mail, simply route it to your nearest Internet gateway. Thanks! Sorry for the long Cc: list, but this problem should really be solved. Sincerely, Daniel Kalchev Forwarded message: > Subject: Found some sort of a clue... > Message-Id: <JOHNSON.920923165504(a)maine.maine.EDU> > From: Johnson(a)Maine.Maine.Edu (Jay Johnson) > To: daniel(a)danbo.uucp (Daniel Kalchev) > Date: Wed, 23 Sep 92 16:55:04 EDT > > Apparently our mailer got an over-ride record from BITNET > which directs BG traffic to AEARN. Our mailer treated my > mail as subject to it and sent it to AEARN which, I guess, > doesn't know how to get to danbo. > The mx records are first to try forth.gr and then eu.net > as I remember which seemed ok though I'd have thought the > order would be reversed. > So thought you'd like to know that sites which have BITNET > as well as Internet links and mailers as dumb as ours may > be giving grief. >

2 1