- ripe-list - mailman.ripe.net

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

RIPE Meeting Audiocast
by Daniel Karrenberg 24 Sep '92

24 Sep '92

RIPE Meeting Audiocast RIPE plans to audiocast the plenary sessions of its upcoming meeting held in Paris, France from September 30th to October 2nd. Since bandwidth in this part of the world is quite limited the audiocast will use LPC4 encoding. Anyone wishing to ask questions during the question periods is strongly advised to use LPC4 encoding as the conference site will not be able to understand you otherwise. Depending on local conditions questions over the net may not be available at all. We will be using the multicast group used for IETF audiocasts 224.2.0.1 and base port 3456 (vat default). IMPORTANT NOTE: We are looking into using the GSM encodig provided in the latest version of vat (v1.45beta) because this has far superior sound quality at only a modest increase in bandwidth. If you intend to listen to the RIPE meeting audiocast we recommend you fetch this version just in case. It is available from the usual places including ftp.ee.lbl.gov:vat.tar.Z ftp.ripe.net:tools/conf/vat.tar.Z The meeting schedule is appended below. Our friends in the US should note that all times are central European time which at that time will be 5 hours ahead of EST. Enjoy Daniel ripe-a-13 R I P E Agenda of the 13th RIPE meeting =============================== September 30 - October 2, 1992 - - - - - - - - - - - W E D N E S D A Y 14:00 h - - - - - - - - - - - - - 1. Opening (R Blokzijl) 15 min o welcome o apologies o introduction o meeting secretary o dinner for Thursday evening o approval of the agenda o papers tabled o organisation of the meeting 3. Minutes of the last meeting 15 min o approval of the minutes o action list 2. RIPE position paper (R Blokzijl) 15 min o formal approval of the last draft 3. RIPE NCC (D Karrenberg) 60 min o report o the future of the RIPE NCC: - organisational position - budget - financing 4. RIPE and RARE 60 min o report from the RARE CoA, September 24-25. (R Blokzijl) o the RARE technical program (RTC members) An introduction of the RARE technical program, with an emphasis on IP networking. 5. Global Internet traffic measurement (T Nielsen) 30 min o Torben will present a proposal to do a global Internet traffic measurement. The proposal is that (some of) the RIPE networks participate in an effort to measure global IP traffic streams. 6. Global Address Assignement (D Karrenberg) 15 min 7. Delegated Registry inside Europe (D Karrenberg) 15 min o coordination between local NIC/NIS and the RIPE NCC 8. Networking in Russia (M Popov) 15 min o status, including international connectivity o future plans - - - - - - - - - - - - - T H U R S D A Y 09:00 h - - - - - - - - - - - - 9. EBONE (P Jones, B Stockman) 60 min o status report o plans for EBONE 93 10. EMPB IP services (PTT Telecom NL) 30 min o EMPB is going to introduce IP on it's network, EMPB will be connected to some of the RIPE coordinated networks. Issues related to interworking between EMPB/IP and the European Internet will be presented and discussed. 11. Audio conferencing (D Karrenberg) 15 min o introduction o proposal for an MBONE * * * * * * * * * * * * * * * * * * * * * * * The following sessions are meetings of - the RIPE working groups - special interest groups They take place with a degree of parallelism. A. Relationship between Academic & Research networks and Commercial networks [Glenn Kowack] B. Network information services [Nandor Horvath] C. DNS issues [Francis Dupont] D. European connectivity [Milan Sterba] E. RIPE Database [Wilfried Woeber] F. Audio Conferencing [Daniel Karrenberg] G. Global Internet traffic measurement [Torben Nielsen] H. Delegated registry coordination [Daniel Karrenberg] I. EBS managers meeting (closed) [Phil Jones] J. EBONE Germany meeting [Stefan Fassbender] - - - - - - - - - - - - - - F R I D A Y 09:00 h - - - - - - - - - - - - - - 12. Reports from the working groups. 120 min 13. Coordination of the RIPE and RARE technical programs. 30 min o for decission 14. Global Internet traffic measurement (T Nielsen) 30 min o proposal o decission 15. Date, place and time of next meetings 15 min o January 25 - 27, Prague 16. A.O.B. 15 min 17 Closing

1 0

Re: Open letter
by Peter Lothberg 23 Sep '92

23 Sep '92

> Thanks Jon, > > > There are a couple of comments I would like on you comments though: > > >- DNS > > i think dns is subsumed in management - i would say just > routing & Management > (but possibly also IPv7 evolution). > > The whole issue is of course to maintain reasonalbe full control of > routing and mangement so that any migration to IPv7, CIDER TUBA etc > MAY be possible. IPv7 is CLNP on the 'internetworking' layer, no magic, and it still have some of the old source/dest limitation's, even thus it might do some good. (Personally I think we need another kind of toy here) Cider, is something we need today, and put's limitations on the topology if we want it to make the big routing table savings we baadly need, NOW! There is somthing more, routing of troble-tickets, with todays international cooperation among all the actors (maybe not EMPB) we can receive a user complain't and get it resolved , even if it crosses *MANY* operators/networks. > As for DNS, some think they can build Internets without DNS support... > This is the best single reason why all open Internet service providers > has to interconnect. Thus you end up in interconnection agreements, > topology and routing issues. > > --mats Not mentioning those who have 'fake' roots that sometimes poisions the whole system for others. This is actually a crusial point, the DNS system is based on countrycodes and it should be made avaliable for all networking organisations in that country, and it has to be fully interconnected. -Peter

3 2