Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27188; 3 May 93 18:31 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa27182; 3 May 93 18:31 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa22612; 3 May 93 18:31 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa14593; 3 May 93 18:17 EDT Received: from zephyr.isi.edu by NNSC.NSF.NET id aa14589; 3 May 93 18:15 EDT Received: by zephyr.isi.edu (5.65c/5.61+local-10) id ; Mon, 3 May 1993 15:15:28 -0700 Date: Mon, 3 May 1993 15:15:28 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Joyce Reynolds Message-Id: <199305032215.AA04023@zephyr.isi.edu> To: us-wg@nnsc.nsf.net Subject: Announcing the Guide to Network Resource Tools Cc: jkrey@isi.edu ----- Begin Included Message ----- Date: Tue, 27 Apr 93 14:24:07 IST From: David Sitman Subject: Announcing the Guide to Network Resource Tools To: wg-isus@rare.nl Announcing the Guide to Network Resource Tools The Guide to Network Resource Tools describes many of the key tools in use today among the academic networking community for accessing resources on the net. The tools described in this guide have been divided into five functional areas. The first section, "Exploring the Network", covers Gopher and World-Wide Web. WAIS and ASTRA are documented in section two, "Searching Databases". The third section, "Finding Network Resources", deals with Archie, WHOIS and NETSERV. Trickle and BITFTP are covered in section four on "Getting Files". The final section, "Networked Interest Groups", discusses Listserv and Netnews. For each tool, the guide provides a general overview and details on availability, intended audience, basic usage, and examples. Thus, it should complement the work of wg-isus by providing a more detailed picture for those who are interested. The guide was produced by the EARN staff. It has been printed as an A5 booklet. Copies of the booklet will be distributed in Trondheim. We will also discuss the guide at the EARNINFO meeting in Trondheim on Friday, 7.5.93, at 14:00. Comments, corrections and criticisms are encouraged, as EARN plans to produce a second edition of this guide for the NSC'93 in Warsaw in October. The Guide to Network Resource Tools is available electronically from: LISTSERV@EARNCC.BITNET in Postscript format. To get the Guide to Network Resource Tools, send the command: GET NETTOOLS PS Most of the individual sections are available in text format with the command: GET toolname MEMO David Sitman EARN ----- End Included Message -----   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22960; 5 May 93 14:51 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa22954; 5 May 93 14:51 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa20537; 5 May 93 14:51 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa01040; 5 May 93 14:40 EDT Received: from him3.cc.umich.edu by NNSC.NSF.NET id aa01036; 5 May 93 14:39 EDT Date: Wed, 5 May 93 14:37:34 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Susan.R.Harris@um.cc.umich.edu To: us-wg@nnsc.nsf.net Message-ID: <22752662@um.cc.umich.edu> X-MTS-Userid: W080 Subject: Net-Train update Here are a couple of recent NETTRAIN postings. =================================================================== Message forwarded by NETTRAIN moderator. Address inquiries to original sender: Date: Mon, 3 May 1993 15:15:28 -0700 From: Joyce Reynolds ----- Begin Included Message ----- Date: Tue, 27 Apr 93 14:24:07 IST From: David Sitman Subject: Announcing the Guide to Network Resource Tools To: wg-isus@rare.nl Announcing the Guide to Network Resource Tools The Guide to Network Resource Tools describes many of the key tools in use today among the academic networking community for accessing resources on the net. The tools described in this guide have been divided into five functional areas. The first section, "Exploring the Network", covers Gopher and World-Wide Web. WAIS and ASTRA are documented in section two, "Searching Databases". The third section, "Finding Network Resources", deals with Archie, WHOIS and NETSERV. Trickle and BITFTP are covered in section four on "Getting Files". The final section, "Networked Interest Groups", discusses Listserv and Netnews. For each tool, the guide provides a general overview and details on availability, intended audience, basic usage, and examples. Thus, it should complement the work of wg-isus by providing a more detailed picture for those who are interested. The guide was produced by the EARN staff. It has been printed as an A5 booklet. Copies of the booklet will be distributed in Trondheim. We will also discuss the guide at the EARNINFO meeting in Trondheim on Friday, 7.5.93, at 14:00. Comments, corrections and criticisms are encouraged, as EARN plans to produce a second edition of this guide for the NSC'93 in Warsaw in October. The Guide to Network Resource Tools is available electronically from: LISTSERV@EARNCC.BITNET in Postscript format. To get the Guide to Network Resource Tools, send the command: GET NETTOOLS PS Most of the individual sections are available in text format with the command: GET toolname MEMO David Sitman EARN ----- End Included Message ----- ===================================================================== Message forwarded by NETTRAIN moderator. Address inquiries to original sender: Date: Mon, 3 May 1993 18:16:03 -0500 (CDT) From: Gleason Sackman ---------- Text of forwarded message ---------- Date: Mon, 3 May 1993 15:17:39 EDT From: Stan Horwitz To: Multiple recipients of list HELP-NET Subject: LC Files Now on Internet The Library of Congress Information System (LOCIS) is now available over the Internet. The telnet address is: locis.loc.gov 140.147.254.3 LOCIS accepts both telnet 3270 and line mode. LOCIS includes over 15 million catalog records and over 10 million records for other types of information: federal legislation, copyright registrations, Braille and audio, organizations, and selected foreign legal materials. Searching hours are (all times USA eastern; closed national holidays): Monday - Friday: 6:30am - 9:30pm Saturday: 8:00am - 5:00pm Sunday: 1:00pm - 5:00pm Printed manuals will be available for sale later this summer and very soon via FTP (ftp seq1.loc.gov /pub/LC.Online). There will be a LOCIS Quick Search Guide and a LOCIS Reference Manual. LC Online Internet: lconline@seq1.loc.gov Library of Congress Stan Horwitz Internet: STAN@VM.TEMPLE.EDU Bitnet: STAN@TEMPLEVM Temple University's Sr. Mainframe Consultant; Manager of the Help-Net and Suggest lists; Listserv Postmaster (Standard disclaimers apply) ----------------------------------------------------------------------------- Gleason Sackman, Coordinator BBS: sackman@sendit.nodak.edu SENDIT - NoDak's K-12 Telcom Network Internet: sackman@plains.nodak.edu 226 IACC, North Dakota State University Bitnet: sackman@plains.bitnet Fargo, ND 58105 Voice: (701)237-8109 Fax: (701)237-8541   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28375; 5 May 93 16:37 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa28369; 5 May 93 16:37 EDT Received: from mocha.bunyip.com by CNRI.Reston.VA.US id aa25716; 5 May 93 16:37 EDT Received: by mocha.bunyip.com (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA03223 on Wed, 5 May 93 15:04:36 -0400 Received: from fernwood.mpk.ca.us by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA03219 (mail destined for /usr/lib/sendmail -odq -oi -furi-request uri-out) on Wed, 5 May 93 15:04:29 -0400 Received: by fernwood.mpk.ca.us; id AA12250; Wed, 5 May 93 12:08:09 -0700 Newsgroups: list.ietf.uri Path: mitra Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Mitra Subject: Wrappers for URLs Organization: Pandora Systems Date: Wed, 5 May 1993 18:46:23 GMT Message-Id: X-Newsreader: TIN [version 1.1 PL9] Apparently-To: uri@bunyip.com A couple of people have brought up the problem of parsing URL's especially if they contain spaces, and the possible need for wrappers. I think (and am prepared to be shot down in flames :-) that this is not a problem. One goal of URL's is to have them work across multiple environments, and I assert that the wrapper is a function of where the URL is recorded, for example in Mime it might be URL: ftp://ftp.path.net/pub/patches/fred.patch whereas in Gopher it wuld be returned as a selector 1Patch to Fredftp://ftp.path.net/pub/patchesashpool.micro.umn.edu70 in email it would probably be given a line on it's own, or put in quotes, with a human doing the cut and paste, or put in quotes. - Mitra   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29036; 5 May 93 17:10 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa29030; 5 May 93 17:10 EDT Received: from mocha.bunyip.com by CNRI.Reston.VA.US id aa27188; 5 May 93 17:09 EDT Received: by mocha.bunyip.com (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA03098 on Wed, 5 May 93 14:35:04 -0400 Received: from [192.197.208.2] by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA03094 (mail destined for /usr/lib/sendmail -odq -oi -furi-request uri-out) on Wed, 5 May 93 14:34:50 -0400 Received: by expresso.bunyip.com (NX5.67c/NeXT-1.0) id AA01948; Wed, 5 May 93 14:33:25 -0400 Message-Id: <9305051833.AA01948@expresso.bunyip.com> Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Peter Deutsch Date: Wed, 5 May 1993 14:33:23 -0400 In-Reply-To: Marc Andreessen's message as of May 5, 1:25 X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Marc Andreessen Subject: Re: Spaces or %20 in URLs Cc: "John A. Kunze" , uri@bunyip.com [ Marc wrote: ] > Peter Deutsch writes: > > As I said at far too great a length in my previous post, > > I'd like us to give serious consideration to a real quoting > > mechanism, canning the current hex encoding mechanism > > since it seems many people are going to a way to do this > > right. I think the current mechanism is a real bag on the > > side and I think we should fix it before this goes out > > into the world. > > Isn't it a bit late for that? First, let me clarify that one of the points of my post was to flag what I thought was a fuzziness in our design criteria which was leading us into possibly questionable decisions. Before we make decisions on such questions as how to do white space in URLs (embedded or surrounding components of them), or how to do quoting in general, I'd like to see an agreed upon list of characteristics that our URLs should have. I feel this should help us decide such questions more easily (and from a quick scan of the mail this morning, getting such a list together may be easier than I thought). If at that point we decide to make _no_ changes to the current doc I'd be happy to live with it, since at least I could feel that the community made an informed decision. I was just worried by what I was seeing in the white space debate and wanted to bring the issue up before things became carved in stone. Now, if it is not a design criterion that a URL specifier be as close as possible to a specification in the parent access method, then so be it. Then it's acceptable to require that Gopher filenames, or WHOIS specs, or whatever, frequently be re-encoded. I don't really mind, but I thought that readibility was important (and hex encoding seems to work against readability). I also thought that there was an implied understanding that any particular access method's URL encoding would be as close as possible to its representation in its home environment (which would also seem to rule against encoding, except in exceptional cases). I may have misread that one, but given that the trend seems to be towards the fairly ubiquitous use of encoding, I thought I'd bring it up. Now, to address your specific question about whether it is too late to change things, the URL paper has only now gone into Internet Draft status. From what I understand of the process, this is exactly the time for the entire community to examine the proposal in detail and catch any mistakes, before the concrete sets and things become difficult or impossible to change. So, as far as I can tell, it is not to late - assuming rough consensus - for the group to decide to change the quoting mechanism, or accept embedded white space, or whatever. I'm actually not particularly committed to us doing this, I'm just calling out some points of order on the process that I thought needed discussion. Look, I don't want to be known as "the trouble-maker who's holding up URLs". I just want to see that we do them right the first time. As me 'ole dad is fond of saying "how come there's never time to do it right, yet always time to do it over?" - peterd -- ------------------------------------------------------------------------------ Peter Deutsch, (514) 875-8611 (phone) Bunyip Information Systems Inc. (514) 875-8134 (fax) "any sufficiently advanced magic is indistinguishable from technology" (- with apologies to Arthur C. Clarke, who almost got it right...) ------------------------------------------------------------------------------   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02871; 7 May 93 9:11 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02865; 7 May 93 9:11 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa08379; 7 May 93 9:11 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa15907; 7 May 93 8:46 EDT Received: from cheviot.ncl.ac.uk by NNSC.NSF.NET id aa15891; 7 May 93 8:44 EDT Received: from eata.ncl.ac.uk by cheviot.ncl.ac.uk id (5.65cVUW/NCL-CMA.1.35 for ) with SMTP; Fri, 7 May 1993 13:43:44 +0100 Date: Fri, 07 May 93 13:43:09 BST Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Jill.Foster@newcastle.ac.uk Subject: IETF Report To: us-wg@nnsc.nsf.net Message-Id: My report on the Internet Engineering Task Force meeting. Most of it concerns WGs in the User Services Area. -- Jill IETF - Columbus: Mar 29-Apr 2, 1993 =================================== Trip Report: Jill Foster - Newcastle University, UK Chairman: RARE Information Services and User Support Working Group Introduction ============ The 26th IETF (Internet Engineering Task Force) Meeting took place in Columbus, Ohio from March 29th - April 2nd. Attendance was up again with over 535 pre-registered and a final total of 644 attendees. My main reasons for attending (thanks to funding from RARE) were to: o represent RARE Information Services and User Support Working Group (which I chair) [RARE is the Association of European Research Networks] o join in the User Services and associated WG sessions. o co-chair a WG session on networked information retrieval tools. o co-chair a WG session on network training materials. The following informal report is in note form and deals mainly with the areas of User Support and Networked Information Retrieval, although reports of some of the plenary sessions are also included. Whilst it is as accurate as I can make it, it is naturally a personal account and may be inaccurate due to lack of background information or misinterpretation of what I heard. Corrections of fact are welcome, but any discussion of items contained here would be best directed to the appropriate mailing lists. Minutes of individual sessions are also available via anonymous ftp from nri.reston.va.us This report will be stored on the UK Mailbase Server. To retrieve a copy, email to Mailbase@mailbase.ac.uk with the following command in the body of the message: send wg-isus ietf.03.93 Alternatively use anonymous ftp to: mailbase.ac.uk file: pub/wg-isus/ietf.03.93 [Also available via gopher] Note: in general I have not expanded acronyms as those readers involved in a particular topic should know them whilst those who aren't familiar with the acronyms should still be able to get a reasonable overview of the topic. All addresses quoted in the report are in internet (rather than UK JANET) order. Each section has a double underlined heading - to enable you to skip sections not of interest. Working Group Chairmen's Workshop ================================= The IETF has grown so large both in terms of number of attendees at the meetings and in terms of the number of Working Groups (WGs) that it is no longer possible to pass on tips to WG Chairmen by word of mouth. An informational RFC on guidelines for WG Chairmen is in preparation. As part of the development of this, Dave Crocker held a workshop for Working Group chairs (starting Monday at 8am!). Dave requested feed back on his talk. The talk concentrated on aspects of project and group management (such as the difficulties of making progress whilst remaining fair in listening to all points of view). It could perhaps have contained more of the nitty gritty of the IETF procedural issues (such as progressing a document via draft RFC to full RFC status and the components of a WG charter etc). Nonetheless, it was a useful session, and the forthcoming RFC will be welcome in providing much needed information in one place. Plenary ======= Phil Gross welcomed attendees to the IETF and spoke about the work of the Nominating Committee. As a result of discussions at previous IETFs about the procedural processes of the IETF and the subsequent work of the POISED WG - about half of the IAB and IESG positions were made available and nominations for these had been sought. The nominations committee had been given the task of producing a short-list of suitable candidates who could commit the level of effort required. The committee had sent a list of nominees to the ISOC Trustees and were expecting a decision during the IETF meeting (see later section on Plenary). Technical Presentation: "Next Generation of IP" ---------------------------------------------- Robert Ullman Problems o Address space o Route scaling o TCP window and sequence space (will wrap in 32s on giga bit link) o Interoperation with version 4 required because by then will see a large investment in commercial IP. New generation protocol will take some time to install and by which time several billion dollars investment in V4, therefore, interoperability vital. IPv7 Addresses - want o Small number of top level administrative domains. o Ability to subnet every network assignment. Admin Domain ------------------|--------------|-------------- | | | | | | | Host | ------------------|--------------|-------------- Network This is equivalent to giving everyone on the planet their own network assignment! o Direct mapping of IPv4 numbers. o NSF Administrative Domain. Data Elements ad hoc Group Meeting ================================== IETF sessions run from 9am (sometimes 8!) until 10pm - with an overspill into bar BOFs ("birds of a feather" informal discussions). Nonetheless a group of people interested in (or at least concerned about) data elements managed to squeeze in several informal meetings to discuss the need for standardised ways of describing networked information resources. This followed on partly from the IETF and CNI meetings in Washington in November and the meetings set up there with the Library of Congress and OCLC and subsequent meetings. The group (included various IETF WG chairs, CNI (Coalition for Networked Information) representatives, CNIDR (Clearing House for Networked Information Discovery and Retrieval) and the Top Node Project. The immediate need was to try to agree on a common naming of data elements in use by the NIR, IAFA and WHOIS++ templates and on the syntax of the values of some of these elements. Pete Percival (Top Node Project) - who had been battling with the problem of describing networked information resources for some time - tried hard to keep us focussed - but the discussions tended to be circular. There was some disagreement on whether or not one "record" should refer to a resource that appeared in multiple formats or was accessible via multiple methods. I thought it should do - looking at it from the point of view of someone completing the record for the resource. (Resource - such as a set of training workshop sheets available in ascii, postscript, rtf - via anonymous ftp, email or gopher and also available on disc or on paper.) Others, involved in writing the tools to handle the records or templates, wanted multiple records - one for each format. As far as the IAFA, NIR, WHOIS++ templates are concerned, it was agreed that we should draw up an "approved" list of fields for each WG to choose from and use as applicable. There would be a core set of common data elements plus some optional elements. An attempt was made to list and agree on those elements and one of the group volunteered to try to pull some of the discussions together. The need for URNs (Uniform Resource Numbers) and, in the first instance, URLs (Uniform Resource Locators) to be included - was acknowledged. Uniform Resource Identifier WG: Peter Deutsch, Alan Emtage ========================================================== URI is now the union of Uniform Resource Location and Uniform Resource Number. The idea is to identify information resources uniquely and to allow the location of these by navigational tools. U = Uniform R = Resource { L,N,I, .... } = { Locator, Number, Identifier, ... } In the interests of making real progress in this area, this group had three separate sessions scheduled during this IETF. URL Session ----------- Tim Berners-Lee's revised document was discussed. The problems of addressing sub-objects in a service independent way and of specifying URLs for filenames containing non Latin characters was raised. It was suggested that the MIME specifications were relevant in this area and should be considered rather than producing a separate different specification. It was agreed that in the interests of making progress and of getting out an RFC that the URL should be kept simple and that the other needs and problems should be pushed to the URN. Fragmentation would also be discussed only at a later stage. The document was to get one more pass on the mailing list before being submitted as an RFC. URLs are transient and this fact might pose a security risk as it may provide a false reference and point people to the wrong document. There might be a need for separate authentication in some cases. URI Session ----------- There is difficulty in assigning an identifier to variant forms of a document some of which are "lossy" translations of the original (for example without format information). We need the flexibility to extract content on a variety of levels. We need "Citation" information. We are beginning to see servers that could say "I have this document and I can convert it to 32 different formats for you". A paper submitted to the mailing list by John Kunze was discussed. The URI is the first thing a user will get back from a search. He will need to be able to make a quick decision on which URI he wants. The URI could give cost/no-cost indication. Information needs to be both human and machine/tool readable. Need a Uniform Resource Citation and a method of updating these. Peter Deutsch talked about URNs (why?, characteristics, etc) and a publishing model. Need URNs for o testing equality of content o tracking and versioning o permanent naming. He maintained that the author should have the authority to determine equality but this should be a transferable right. The URN should be unique and be assigned when the document is "published" via a "publisher". Clifford Lynch pointed out that there was not a clean distinction between content and representation. Different people have different ideas on the equality of two documents. For example an archivist may not agree with a librarian. Different publishing agencies may also have different criteria. Perhaps there will be different name spaces with URNs being unique within a given name space. There was a heated argument as to whether there could be a unique URN for a given resource which contained changing data (for example a weather database, gopher menu item, etc). The URN would point to the "box" whose contents might change. There is a need for extra information about objects. Karen Sollins talked about a bag of "factoids" (attribute: value pairs) associated with the resource. Needed to be able to define a set of attributes (but an open set). Should use RFC822 and MIME extensions for this. Tim Berners-Lee pointed out that the http specification had used the RFC822 specification and added some additional attributes - such as the operations which could be performed on the object. Have URN -> identification of object URC (citation) -> Description URL -> Location and access information Erik Jul (OCLC) recommended caution when discussing the description. He said terms had been formalised in librarianship and information science. Need for a pilot naming service on the net (for URNs). Need Data Element names and a list of values. Need mechanism for handing around non-text attributes (e.g. icons). It was agreed that someone needed to write a paper to define the context of these discussions for those coming in to it (particularly as library people become involved). Alan Emtage and Chris Weider intend to do this. Mailing list: uri@bunyip.com To join, mail to: uri-request@bunyip.com Archive: archives.cc.mcgill.ca Directory: /pub/uri WHOIS and Network Information Look Up Service Working Group: WNILS: ================================================================== Joan Gargano The WHOIS++ project aims to develop a lightweight useful Internet Directory Service using simple technology. The data model is template oriented. Structure of WHOIS++ database (logical) Template type 1 type 2 type N etc --------- ---------- ---------- | 1 | | | | | --------- | ---------- | ---------- | | 2 | | | | | | | | --------- |-- ----------- |-- ----------- |-- | 3 | | | | | | | | | |-- | |- | |- | | | | | | --------- ----------- ----------- people services ...... Summary information from WHOIS++ servers is propagated up the tree to "centroids". Clients can query parent servers to find servers with given keywords. A new document (WHOIS++ Architecture Document) had been posted to the WNILS list on the Thursday before the meeting. A pilot version of the server had been coded in November and they were currently working on extensions for optional extras, such as a multi-lingual facility and security and authentication. Dave Crocker suggested that the MIME Specification should be used as the basis for some work in this area. Other work required: Error messages extending centroids writing templates support for synonyms (meeting voted against work on this) Data Management tools. BUNYIP (Peter Deutsch et al) had a contract to work on a URN->URL server by the end of April. Jim Fullton reported that they have students working on WHOIS++ clients. Mark Prior (Adelaide) is also working on a server. The aim is to get the current document to an internet draft as soon as possible (feed back required) and to have working server code by end April. mailing list: ietf-wnils@ucdavis.edu mail archives: /pub/archive/wnils or gopher: ucdavis.edu port 70 Integration of Internet Information Resources Working Group (IIIR): ================================================================== Chris Weider The purpose of this working group was to start to pull together some of the applications (WAIS, gopher, archie) and to work on interoperability issues, what new tools should do and to discuss gateway protocol design. Chris Weider had written a paper on "Transponders". The idea was that each networked information resource had an extra "active" bit that remembered who knew about it (held references to it). The purpose of the transponder was to let these "users" know when the resource was moved from its current location. This would require URNs and URLs to be in place first. The vision of the group was of an information architecture that allowed for a variety of protocols (gopher, WAIS, WWW ...) and involved a directory service for resolving a URN -> URL(s). The group was chartered to produce a taxonomy of services such as: Resource Discovery (WHOIS++ eventually) Resource Location archie Resource Access gopher, W3, WAIS Resource Management A taxonomy would indicate the holes in the architecture and would help to focus the debate and would help to rationalise how new information retrieval topics are addressed in the IETF. (Need to avoid the current proliferation of WGs.) IIIR: create RFCs for protocols not yet documented (e.g. gopher protocol). User Services Working Group Chair: Joyce Reynolds =========================== US-WG is the umbrella WG for the various user services area WGs. This is the group which spawns new WGs and coordinates the work in this area. Mailing list for this group: us-wg@nnsc.nsf.net To join, mail to: us-wg-request@nnsc.nsf.net Joyce Reynolds reported that the User Glossary, the DISI (Directory Information Services Infrastructure) and the NOC Tools Working Groups had completed their work and closed down. New Working Groups included IDS (Integrated Directory Services) and the Network Training Working Group. The Internet Users' Glossary RFC1392/FYI18 had been completed. RARE ISUS WG Report: Jill Foster -------------------------------- I had previously circulated a report to the us-wg mailing list prior to the IETF. this report is available via anonymous ftp from: mailbase.ac.uk in the file: /pub/wg-isus/isus-026 The report includes the various ISUS subgroups, their progress and mailing lists. Mailing list of ISUS: wg-isus@rare.nl To join, mail to: mailserver@rare.nl the command (in the text of the message): subscribe wg-isus firstname lastname (substituting your own first and last name) INTERNICS --------- Susan Calcari from General Atomics gave a presentation on the Internics. There had been an NSF solicitation for network information services for NSFnet and NREN. Three separate organisations had received contracts to provide services for (respectively): o Registration - Network Solutions Inc (NSI) o Directory and Database Services - AT&T o Information Services - General Atomics/CERFnet [These services went live on April 1st (during the IETF)] Susan Calcari introduced herself as an "Info Scout" and promised to keep in touch with the IETF and us-wg in particular. The Internic Information Services will run the NIC of NICs providing service to mid level and campus NICs. They would be providing access to their information by o telnet, ftp and mail o archie, WAIS, gopher o NIC link (facility to distribute information out to other NICs) They would be keeping a list of information resources and providing discipline specific information packets. They already had information for the following groups: o Biology o Chemistry o Networking o Librarians o K-12 (schools) Info Scout A five year mission to explore new worlds, seek out new tools and resources, to boldly go where no Internant has gone before! Try to keep track and to have someone keep in touch and keep information up to date. InterNIC Mailing List o Intended for end users and NICs o Announcements only o Collaborative project o nis@InterNIC.net to join, mail to: listserv@InterNIC.net text: subscribe nis your name Quality Evaluation o Tracking o Trouble tickets o Reports o Internal quality scores Co-ordination Services o InterNIC Liaison Council o International Co-operation o Representation to the Community Community Outreach to include: IETF, Farnet, CNI, CIX, ISOC, Educom, SIGUCS NIS "Fest" (National meeting for NIC people) NIS minifests (small regional ones) Training o Use the experts o work with the midlevels and campuses o offer established courses at a discount InterNIC Team Co-ordination o unified InterNIC Interface o common trouble ticket system o joint community activities (did Interop together for example) as appropriate. Unified InterNIC Interface o Common telephone identity .800.444.4345 o Common electronic identity info@internic.net Reference Desk will answer this mailbox and phone Individual Contact Information o Information services info@is.internic.net o Directory and Database Services admin@ds.internic.net o Registration Services hostmaster@rs.internic.net Registration Services will run WHOIS and DNS and will have T1 link. There were questions raised re performance of machines chosen for services. NSF and charging Nothing offered on-line will be charged for (at least for two years) Cost recovery on hard copy. Commercial community will be charged at cost plus. Seminars - charged for - cost recovery. Fees collected will be ploughed back into project in first five years - not for profit. Full staff of seven (two currently). Addresses to contact: scout@internic.net - suggestions for information to put up info@internic.net - general queries Calls routed from old NICs: NNSC and Merit (Pat Smith of Merit said: "Goodbye and good luck!") There would be an NIS fest West Coast July (probably) In an early announcement of the Internic it had stated that the Internic might charge non-US users for access to the information. I asked Susan about this as I was concerned about the implications for central Eastern European users and internet users from third world countries (and the UK!). It might also inhibit a free flow of information from Europe to the US if we then found we were paying for information we'd provided! Susan stated that there were NO plans to charge users for information provided on-line. FYI 4 and 7 (FAQ): Gary Malkin ------------------------------ FYI 7 "FYI on Questions and Answers: Answers to Commonly Asked 'Experienced Internet User' Questions", (Also RFC 1207), February 1991. FYI 4 "FYI on Questions and Answers: Answers to Commonly Asked 'New Internet User' Questions", (Also RFC 1325), May 1992. Gary wanted to update the new user and experienced user Frequently Asked Questions (FAQ) RFCs. He suggested "creating" questions for FYI 4. FIY 7 contains actual questions from mailing lists. He had decided that it would be better to use contrived questions and answers for this too. To join the list, mail to: QUAIL-request@XYLOGICS.COM It was suggested that people who had to answer user questions should send in their own "top 5" frequently asked questions to QUAIL@XYLOGICS.COM. World Wide Web BOF Tim Berners Lee ================== The purpose of the BOF was to look at the status of WWW and the possible future directions and to get it started through the IETF review process. The idea of a WWW consortium was raised. There was a need for a single point of presence to go out and push WWW. Need for a place to register WWW servers. WWW - sometimes difficult to install a server. Installation scripts need more work. The vote on whether to start a WWW news group was mentioned. mailing list: www-talk@info.cern.ch to join, mail to: www-talk-request@info.cern.ch NISI - Networked Information Services Infrastructure WG ======================================================= Chair: April Marine This group is concerned with co-ordinating NICs (network information centres) and improving the service they provide. NIC Profile: The group was trying to collect information on the various NICs in the nic-profiles. To place your NIC information: 1. anonymous ftp to merit.edu 2. get /pub/nisi/nic_template 3. edit the template and put in your NIC's information 4. mail the completed template to X500test@merit.edu with 'add' in the subject field if you want more information send to the same address with "help" in subject field NETHELP: The idea was that a new inexperienced user should be able to sit down at a terminal or PC and say "nethelp". This idea has been around for about five years now and the group were facing a decision on whether to drop this idea. Ed Krol had come up with some suggestions on how to implement this. The user's machine should be able to send a packet to the network to find a help file - which would be serviced by the nearest entity - such as the campus router or national provider. The difficulty of course would be the need to update thousands of routers. Some simpler suggestions were made at the meeting, in particular Susan Calcari suggested that the local NIC Services contact could be added to the Templates used for registering Networks - so that a user who did "whois" for his network would be presented with the contact information. Mailing list: nisi@merit.edu To join, mail to: nisi-request@merit.edu Also: Mailing list: nic-forum@merit.edu To join, mail to: nic-forum-request@merit.edu Plenary ======= Erik Huizer: IETF Amsterdam - what to expect. Erik Huizer gave a short entertaining presentation on Amsterdam (complete with 35mm slides) to try to prepare prospective IETF-ers for the first IETF meeting outside of North America (July '93). He appeared in wooden clogs (which he presented to Vint Cerf) and handed out Jeneva and chocolates to various of the IESG and Secretariat. He explained where Holland was "for the benefit of those who had passed through the US educational system" and that people in Europe tended to be more polite to one another. (Hmm!) The conference centre is separate from the hotels (and therefore the registration fee will be slightly higher). He went on to say that there are 1.8 bikes/person in Holland; that you might see more than just coffee on the menu in a coffee shop and that Holland is smaller than Lake Michigan! Networked Information Retrieval WG ================================== Co-chairs: Jill Foster, Jane Smith (for George Brett) Jane Smith (Assistant Director of CNIDR) reported on the Clearing House for Networked Information Discovery and Retrieval. They have a cooperative agreement with NSF from April 1st and will be coordinating with the three INTERNICs. They will be rebundling the latest version of WAIS with various other bits and pieces: FreeWAIS. Close liaison with Brewster Kahle (now of WAIS Inc) will be maintained. Peter Scott's Hytelnet will be supported and distributed via CNIDR for a $20 donation for this shareware. Jill Foster gave a brief report on the RARE Information Services and User Support Working Group and the various sub groups (Multimedia Information Services, UNITE: user network interface to everything, etc). NIR "status report": Since the Washington NIR WG, the information on most of the NIR groups and tools had been updated from the appropriate contacts and had been edited together into an internet draft which had been made available prior to the meeting. Access details: anonymous ftp from mailbase.ac.uk file name: pub/nir/nir.status.report An appendix of "Forthcoming Attractions" had been added as well as the other appendices discussed last time. It was agreed to move NCSA MOSAIC for X into the main body of the report. Various other small changes were suggested. The next stage is "evaluation". There needs to be a check-list of facilities. Various volunteers agreed to work on drawing up the checklist and would then circulate this to the main list for comment. Mailing list: nir@mailbase.ac.uk To join, mail to: mailbase@mailbase.ac.uk The text: subscribe nir Archives in Directory: /pub/nir Gopher BOF ========== The gopher protocol document which had been around for about two years had been submitted as a draft RFC. There was some discussion as to whether or not it covered current agreed practice. There was also some discussion as to whether the IETF or Gopher Con was the appropriate forum for discussing gopher. The Gopher Team would be attending the next IETF (in Amsterdam). It was agreed not to mention "The L-word": A reference to the controversy over the licensing of gopher. Privacy Enhanced Mail ===================== At the start of the plenary Wolfgang.Schneider@gmd.de announced a version of PEM for non-US citizens (to get around the export restrictions on the algorithms). They have a PEM filter which implements RSA Cryptography, X.509 functionality and local security features. Available for Sun OS 4.1.2 (other Unix, MS-DOS and Mac - soon). UCL (UK) version and Inria (France) versions also expected soon. Internet Talk Radio =================== Carl Malamud gave a presentation on the Internet Talk Radio which would be produced by the company he'd set up. The idea was to produce good quality radio programmes for distribution to various ftp sites around the internet. (Around 60 Mbytes/week.) The content would concern the technology, the politics etc. Sun and O'Reilly were acting as sponsors which meant that the programmes could be made freely available. In the future, conferences could be covered - with daily summaries being given. He also suggested that the IETF "TV" (multicasting the IETF) should now move into production mode to free up the researchers (who usually ran the sessions). Other ideas were mailing list summaries and Internet Traffic congestion reports ("we have just had a report of congestion over south-east Australia ..."). The Radio Show would feature "Geek of the Week" - an interview with an Internet "personality", book reviews, etc. Training Materials WG: Ellen Hoffman and Jill Foster ===================================================== This was the first meeting of the Working Group following the initial BOF session in Washington. A reminder that the main objectives are: o to provide a comprehensive package of "mix and match" training materials for the broad academic community. o to provide a catalogue of existing training materials. Ellen Hoffman described some of the Merit NSFnet Training Seminars and Jill Foster gave an update on the UK NISP/ITTI Training Materials Project at Newcastle. This project had pulled together a list of network training materials available - but the project had now moved on to the next phase. The working group agreed that this catalogue of materials would form a useful basis for work in this group and a couple of members volunteered to work further on this. Jill Foster and other members of the group had tried to define a template for collection of information about training materials taking into account the Top Node Data Elements. There remained some outstanding issues to be resolved - and there was a danger in this becoming bogged down in the more general "Data Elements" discussions. It was also noted that the template needed to include a URN (Uniform Resource Number). The "catalogue" would be followed up on the mailing lists having been pushed forward by a small set of volunteers. Michael Mealing from Georgia Tech was asked to talk about MUDs (multi-user dungeons and dragons), MUSHs (multi-user shared halucinations) and MOOs (object oriented MUDs) in the context of training. The idea was that the next generation of network users will be the "NINTENDO" generation and that we should investigate the possibilities offered by learning by "playing" in a directed interesting environment which allowed interaction with other learners. Michael described a MUSH that had been set up for Biologists and allowed one to "walk around" the DNA sequence. He held an informal BOF on MUDs etc. I would like to see gopher or world wide web being used as a training tool using something like the Tour of the Internet as the basis. The new user could browse the information at a variety of levels of depth and could call out and try various services described. Several sites have put up new user sections. It wouldn't take too much to move from "documentation" to "training material". Perhaps some sound and visuals could be added too - such as very very short messages from prominent people on using the network. The discussion then moved on to the training pack. The Newcastle project is producing a mix and match set of training materials - and the working group discussed the possibilities. I'd like to see high quality recordings of sound interviews being made specifically for training purposes and made available on the network. Carl Malamud (Internet Talk Radio) seemed quite receptive to the idea. We just need to come up with some concrete ideas. Some people felt that sound or radio was very limiting in a training situation. However the idea is to produce a mix and match set of materials that trainers can pick from to suit their personal training style and to match the needs of the particular group they were training. Sound mixed with visuals could be quite effective and would help to vary the format of the presentation. Various people volunteered to work on some of the issues raised and to report back to the mailing list. The RARE WG and US WG mailing lists are currently being used for this Training WG. RARE ISUS: wg-isus@rare.nl to join, mail to: mailserver@rare.nl the text: subscribe wg-isus US-WG: us-wg@nnsc.nsf.net to join, mail to: us-wg-request@nnsc.nsf.net Plenary: INTERNIC ================= The three parties running the Internic (Network Solutions Inc. AT&T and General Atomics) held a plenary session on April 1st to outline their plans and to officially launch the InterNIC. Various people from the parties concerned called in over the network to say their piece as part of the launch and to underline the distributed nature of the InterNIC. One of the aims set out in the NIC solicitation was to use the network for collaboration between the various distributed parts of the NIC. (See also the section on us-wg for details on the Internic Information Services.) Scott Williamson (NSI) described the registration services that they would offer and the move to delegated Registries. (RIPE NCC already handles IP address registration for Europe.) Rick Huber (AT&T) talked about the Directory and Database Services. They would be putting together the Directory of Directories. They would have resource description files and would validate them periodically (say every six months). This information would be made available via WAIS, archie, ftp and gopher by July '93. There would be no fees for accessing the information. Information providers could have one page of information on their resource listed for free. There would also be the option of paying for a more extended listing. Plenary: IESG/IAB Nominations ============================= The results of the votes on the vacant IESG/IAB positions were announced at the last evening of the conference. On the whole the results were greeted favourably, although concern was expressed that WG chairmen of the areas concerned had not been consulted over the choice of area director and that a candidate's attendance (or otherwise) at IETFs had not seemed to have been taken into account. IETF/IESG chair: Phil Gross Standards AD: Lyman Chapin Service Applications AD: Dave Crocker Applications AD: Brewster Kahle Internet AD: Steve Knowles Network Management: Marshall Operations: Scott Bradner Transport AD: Alison Mankin Concluding Remarks ================== The Columbus IETF saw the attendance reach a new maximum and saw the fourth multicast audio and video transmission across the network of the plenary sessions and some WG sessions. This time the OARnet team and the IETF Secretariat handled much of the work for IETF Channel 1 and Channel 2. The idea is to move this facility from "research" to "production service". Again a very hectic, intense and productive IETF with overlap of interest (for me) in the mainstream areas I had wanted to attend and no time to attend related areas (Mail and Directories Working Group meetings). The next IETF will be the first outside of North America. It will be interesting to see whether the high attendance can be maintained. Finally, a reminder that these notes are my view of the IETF. They may not be an accurate view, and certainly do not cover the wide range of topics discussed at the workshop. It's also five weeks ago now since the IETF and things have moved on.... Jill Foster (Jill.Foster@newcastle.ac.uk) 06.05.93   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14867; 13 May 93 10:30 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa14861; 13 May 93 10:30 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa14211; 13 May 93 10:30 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa02891; 13 May 93 10:15 EDT Received: from him3.cc.umich.edu by NNSC.NSF.NET id aa02879; 13 May 93 10:14 EDT Date: Thu, 13 May 93 10:14:58 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Susan.R.Harris@um.cc.umich.edu To: us-wg@nnsc.nsf.net Message-ID: <22960523@um.cc.umich.edu> X-MTS-Userid: W080 Subject: Postings from NETTRAIN and the Am. Library Association Message forwarded by NETTRAIN moderator. Address inquiries to original sender: Date: Fri, 7 May 93 15:48:56 +0100 From: Tim Berners-Lee World-Wide Web Software Put Into Public Domain =============================================== A declaration that the basic World-Wide Web software from CERN is in the public domain has been signed by H. Weber, CERN's Director for Administration and W. Hoogland, Director for Computing. The declaration, signed on 30 April 1993, makes it clear that this is not a precedent for CERN software. It states, "CERN's intention is to further compatibility, common practices, and standards in networking and computer supported collaboration." The declaration covers the "libwww" common code library, the line mode browser (www) and the W3 server (httpd). The World-Wide Web (W3) is a global information system with a easy point-and click interface. It provides access to almost all existing Internet-based information as well as a whole new world of data presented to the user as multimedia hypertext. By a sequence of hypertext jumps and text searches, anyone can find his way though the mass of information available all over the world. The High Energy Physics community, of which CERN is a European center, already uses W3 extensively. In all there are more than 70 servers around the world providing data using special W3 protocols, including such diverse areas as hypertext of US law from the Legal Information Institute at Cornell University, to the "Thesaurus Linguarum Hiberniae" collection of medaeval Irish manuscripts from University College, Cork. Software for making servers is part of that put into the public domain by CERN. The other part is the "client" software which allows the reader to move seamlessly through this data and also all the existing data on servers using existing "FTP", "WAIS", "Gopher", and network news protocols. There are more than 14 different client programs for different computing platforms, written by people from institues in many countries. "The existence of a common, public domain kernel of software to handle the protocols will ensure compatibility, and prevent people having to 'reinvent the wheel'", says CERN's Tim Berners-Lee, W3's creator. The W3 project is a success story of international collaboration. The National Center for Supercomputer Applications (NCSA) in Illinois have been a powerful force, producing a popular "Mosaic" client for workstations, and other contributions have come from many other universities throughout the world. In the US, the Web is seen as an answer to the Clinton administration's call for a National Information Infrastructure. It is growing fast. "Traffic we see on our CERN server has more than doubled every four months for the last two years", says Berners-Lee, "and of course there is a new server every few days". "With the Web, we are sharing knowledge," says Berners-Lee, "without discrimination as to who or where in the world you are." The W3 developers look forward to a time when the Internet, and so the Web, will be accessible from homes and high schools anywhere. As well as an opening up of research centers and government, they are looking for a sharing of ideas and educational material for all tastes and ages. Ends. __________________________________________________________________ Tim Berners-Lee timbl@info.cern.ch World Wide Web team leader CERN, CN Division Tel: +41(22)767 3755 1211 Geneva 23, Switzerland Fax: +41(22)767 7155 ________________________________________________________________ ================================================================== Message forwarded by NETTRAIN moderator. Address inquiries to original sender: Date: Sat, 08 May 93 12:06:40 CST From: Joyce Iannuzzi The Internet Companion and Krol's Whole Internet Guide, along with a few other (well-chosen) Internet related books, can be ordered via e-mail (provide a credit card number) from the new InterNIC. I tried this service and it works--GREAT. I seem to have a talent for lending my personal books to persons who promptly disappear from my world so I had a few replacements to order. Gopher to (or telnet to and then select GOPHER) rs.internic.net. select InterNIC Information Services select InterNIC Store select Books select How to Order Books and follow the instructions for completing the order template. I hope I can resist losing my books in the future by pointing others to this service who always lose the notes I write for them to acquire their own copy. I hope I myself do not need to use it again (unless they add new books to the list). rs.internic.net really is very easy to use. Browse around while your are there. I have no reason to push the InterNIC's service other than I find it very easy for beginners to use and like the way InterNIC is starting out (with a Gopher server that also works nicely via telnet for those without a Gopher client). This is also the new WHOIS location. It probably has more to do with where I am and where it is than anything else but, wow, it is fast. InterNIC announcement, etc. has already appeared on NETTRAIN. On Fri, 7 May 1993 16:02:00 CST NETTRAIN said: ..... >OBS/The.Internet.Companion subdirectory at world.std.com -- I think it >is important that nettrainers know that this file is available for personal >electronic use only, not for printing and distributing. Paper copies can >be purchased for $10.95 (and are well worth it, I might add. This and >Krol's Whole Internet Guide are wonderful resource for beginners.) > >Thanks ! Kate Wakefield, User Services Librarian, NEBASE/NE Lib Commission ________________________________________________________________ ------- Forwarded Message Date: Fri, 07 May 93 16:39:59 EDT To: Multiple recipients of list ALA-WO From: ALA Washington Office Subject: ALAWON Vol. 2, No. 17 Sender: "ALA Washington Office Update" X-To: ala-wo@uicvm.uic.edu ******************************************************************* ALAWON ALA Washington Office Newsline An electronic publication of the American Library Association Washington Office Volume 2, Number 17 May 7, 1993 ******************************************************************* LC FILES NOW AVAILABLE VIA INTERNET The following message has been posted to several library lists by Judy L. Stork (lconline@SEQ1.LOC.GOV): ----------------------------------------------------------------- The Library of Congress Information System (LOCIS) is now available over the Internet. The telnet address is: locis.loc.gov 140.147.254.3 LOCIS accepts both telnet 3270 and line mode. LOCIS includes over 15 million catalog records and over 10 million records for other types of information: federal legislation, copyright registrations, Braille and audio, organizations, and selected foreign legal materials. Searching hours are (all times USA eastern; closed national holidays): Monday - Friday: 6:30am - 9:30pm Saturday: 8:00am - 5:00pm Sunday: 1:00pm - 5:00pm Printed manuals will be available for sale later this summer and very soon via FTP (ftp seq1.loc.gov /pub/LC.Online). There will be a LOCIS Quick Search Guide and a LOCIS Reference Manual. LC Online Internet: lconline@seq1.loc.gov Library of Congress ------------------------------------------------------------------ Of particular interest to ALAWON subscribers is the section on Federal Legislation. This section tracks legislation introduced in the U.S. Congress from 1973 to the present. Each Congress has its own file, and it is possible to search all files at once. Information on each bill includes the date it was introduced, a brief description, the committee(s) to which it was referred, the action taken on the bill, and the cosponsors. Although LOCIS supports both tn3270 and line mode, tn3270 will present the information in a slightly more readable fashion. ***************************************************************** NEW ALA WASHINGTON OFFICE INTERNET ADDRESSES The ALA Washington Office now has its own Internet domain name and individual addresses for some staff members. Mail can be sent directly to the following people: Carol Henderson cch@alawash.org Anne Heanue aah@alawash.org Mary Costabile mrc@alawash.org Fred King fdk@alawash.org Mail to Eileen Cooke and all other ALA Washington Office staff members can be sent to: alawash@alawash.org Mail sent to our old addresses, nu_alawash@cua.edu (Internet) and nu_alawash@cua (Bitnet) will be forwarded to alawash@alawash.org for the next few months. The address for subscribing to ALAWON has not changed. ****************************************************************** ***************************************************************** ALAWON is an irregular publication of the American Library Association Washington Office, 110 Maryland Avenue, N.E., Washington, DC 20002-5675. Phone: 202-547-4440; Fax: 202-547-7363; Internet: alawash@alawash.org. Editor and List Owner: Fred King (fdk@alawash.org). All or part of ALAWON may be redistributed, with appropriate credits. ALAWON is available free of charge and is available only in electronic form. To subscribe, send the message "subscribe ala-wo [your name]" to listserv@uicvm (Bitnet) or listserv@uicvm.uic.edu (internet). Back issues of ALAWON are available from the list server. To find out what's available, send the message "send ala-wo filelist" to the listserv. The ALA-WO filelist contains the list of files with the exact filename and filetype. To get a particular file, issue the command "send filename filetype" to the listserv. ==================================================================== Message forwarded by NETTRAIN moderator. Address inquiries to original sender: Date: Tue, 11 May 1993 15:45:29 CDT From: "Craig A. Summerhill" I posted this announcement on the Coalition's CNI-ANNOUNCE forum last week. I thought it might interest readers of the PACS-L forum too. Craig A. Summerhill, Systems Coordinator and Program Officer Coalition for Networked Information 21 Dupont Circle, N.W., Washington, D.C. 20036 Internet: craig@cni.org AT&Tnet (202) 296-5098 ------------------------ top of announcement ---------------------------- The Coalition for Networked Information is pleased to announce the availability of a Coalition Gopher server. Due to popular demand, access to the Coalition's FTP archives, archives of Coalition electronic mail forums, Coalition Task Force and Working Group documentation, Coalition databases, and more is being made available through a Gopher interface. Effective immediately, you can point your favorite Gopher client to: gopher.cni.org 70 Questions, comments and criticisms should be directed to Craig A. Summerhill, Coalition Systems Coorindator, . A couple of notes about the Coalition Gopher server: [1] The Coalition Gopher Server is not currently registered with the University of Minnesota. Therefore, I can not tell you "what series of menus" (i.e. "All Gopher Servers in the World/North America/etc...) to select in order to connect. It doesn't appear in the Minnesota top-level hierarchy at this time. For the time being, you will need to run a client such as "Turbo Gopher" for Mac, "PC Gopher III" for DOS, or the unix "vt100 client" that will allow you to make a root connection to 'gopher.cni.org 70'. If you're not sure how to do this, please consult your local systems support staff. [2] I will be registering the Coalition server in the not too distant future. So, eventually, you will be able to access it through the geographical server of "All Gopher Servers in the World" at Minnesota. [3] None of the Coalition documentation is currently indexed in Veronica. COALITION FOR NETWORKED INFORMATION: The Coalition for Networked Information, a joint project of the Association of Research Libraries, CAUSE, and EDUCOM promotes the creation of and access to information resources in networked environments in order to enrich scholarship and to enhance intellectual productivity. Roughly 180 organizations and institutions are members of the Coalition Task Force. For more information on the Coalition, take a look at our Gopher server. ------------------------ end of announcement ---------------------------- P.S. -- Regarding my last couple of postings about "Gophers, Copyright, the IETF, and the Corporation for National Research Initiatives." Judging from some of the personal mail I have recieved, there seems to be a misunderstanding about the nature of CNRI and CNI. Please note, I work for the Coalition for Networked Information. It is the Corporation for National Research Initiatives that handles orders for IETF Proceedings. We're different organizations. - Craig -   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02463; 24 May 93 17:01 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02455; 24 May 93 17:01 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa17751; 24 May 93 17:01 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa00895; 24 May 93 16:52 EDT Received: from zephyr.isi.edu by NNSC.NSF.NET id aa00891; 24 May 93 16:50 EDT Received: by zephyr.isi.edu (5.65c/5.61+local-10) id ; Mon, 24 May 1993 13:50:29 -0700 Date: Mon, 24 May 1993 13:50:29 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Joyce Reynolds Message-Id: <199305242050.AA15285@zephyr.isi.edu> To: us-wg@nnsc.nsf.net Subject: Amsterdam IETF User Services Area sessions Cc: jkrey@isi.edu Folks, Here is the current draft agenda of the IETF User Services Area sessions that are scheduled for Amsterdam. Joyce ========================================================== MONDAY, 12 July 1993 1330-1530 Afternoon Sessions I USV WHOIS and Network Information Lookup Service WG (wnils) (Joan Gargano/UCDavis) 1600-1800 Afternoon Sessions II USV Uniform Resource Identifiers WG (uri) (Alan Emtage/Bunyip and Jim Fullton/UNC) 1930-2200 Evening Sessions USV Integration of Internet Information Resources WG (iiir) (Chris Weider/Merit) NOTE: Monday evening's sessions may be moved as the IETF Social has been scheduled at that time. TUESDAY, 13 July 1993 0900-1200 Morning Sessions USV User Services WG (uswg) (Joyce K. Reynolds/ISI) 1330-1530 Afternoon Sessions I USV Uniform Resource Identifiers WG (uri) (Alan Emtage/Bunyip and Jim Fullton/UNC) 1600-1800 Afternoon Sessions II USV User Documents WG (userdoc2) (Ellen Hoffman/UMich and Lenore Jackson/NASA) WEDNESDAY, 14 July 1993 0900-1200 Morning Sessions USV Uniform Resource Identifiers WG (uri) (Alan Emtage/Bunyip and Jim Fullton/UNC) 1330-1530 Afternoon Sessions I USV Networked Information Retrieval WG (nir) (Jill Foster/UNewcastle-Upon-Tyne and George Brett/MCNC) 1600-1800 Afternoon Sessions II (Cliff Neuman/ISI) USV Network Information Services Infrastructure WG (nisi) (April Marine/NASA and Pat Smith/Merit) THURSDAY, 15 July 1993 0930-1200 Morning Sessions USV Network Training Materials WG (trainmat) (Ellen Hoffman/Merit and Jill Foster/UNewcastle-Upon-Tyne) 1330-1530 Afternoon Sessions I USV Internet School Networking WG (isn) (John Clement/EDUCOM, Connie Stout/TheNet and Art St. George/UNM)   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06897; 26 May 93 11:06 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06891; 26 May 93 11:06 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa12134; 26 May 93 11:06 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa16633; 26 May 93 11:01 EDT Received: from atlas.xylogics.com by NNSC.NSF.NET id aa16629; 26 May 93 10:59 EDT Received: by atlas.xylogics.com id AA05960 (5.65c/UK-2.1-930202); Wed, 26 May 1993 11:02:01 -0400 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Gary Scott Malkin Date: Wed, 26 May 1993 11:02:01 -0400 Message-Id: <5960.199305261502@atlas.xylogics.com> To: us-wg@nnsc.nsf.net Subject: Intro material needed I've seen a lot of mail recently about how things are WAIS indexed and gopherized and so on. What I don't see is a document which is an introduction to this new generation of information retrieval. If there isn't anything out there which explains, Archie, Gopher, WWW, WAIS, etc., and how they all interact with each other, then maybe the USWG should consider writing something. I know I would find it useful. ---------------------------------------------------------------------- Gary Malkin Remember- take care of your feet, (617) 272-8140 and always have respect for cows.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07268; 26 May 93 11:26 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07262; 26 May 93 11:26 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa12886; 26 May 93 11:26 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa16966; 26 May 93 11:20 EDT Received: from NIC.PREP.NET by NNSC.NSF.NET id aa16961; 26 May 93 11:19 EDT Received: by nic.prep.net (5.57/2.00) id AA03487; Wed, 26 May 93 11:19:16 -0400 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Marsha Perrott Message-Id: <9305261519.AA03487@nic.prep.net> Subject: Re: Intro material needed To: Gary Scott Malkin Date: Wed, 26 May 93 11:19:16 EDT Cc: us-wg@nnsc.nsf.net In-Reply-To: <5960.199305261502@atlas.xylogics.com>; from "Gary Scott Malkin" at May 26, 93 11:02 am > If there isn't anything out there which explains, Archie, Gopher, > WWW, WAIS, etc., and how they all interact with each other, then > maybe the USWG should consider writing something. I know I would > find it useful. I agree! Marsha Perrott PREPnet   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07776; 26 May 93 12:11 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07770; 26 May 93 12:11 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa13998; 26 May 93 12:11 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa17366; 26 May 93 12:03 EDT Received: from ncar.ucar.edu by NNSC.NSF.NET id aa17362; 26 May 93 12:02 EDT Received: from niwot.scd.ucar.edu by ncar.ucar.EDU (5.65/ NCAR Central Post Office 03/11/93) id AA10109; Wed, 26 May 93 10:02:01 MDT Date: Wed, 26 May 93 10:02:00 MDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Don Morris Message-Id: <9305261602.AA17932@niwot.scd.ucar.EDU> Received: by niwot.scd.ucar.EDU (5.65/ NCAR Mail Server 04/10/90) id AA17932; Wed, 26 May 93 10:02:00 MDT To: gmalkin@xylogics.com, us-wg@nnsc.nsf.net Subject: Re: Intro material needed Look at the paper: "A Comparison of Internet Resource Discovery Approaches" Michael F. Schwartz, et. al. Computing Systems (The Journal of the USENIX Association) Volume 5, No. 4, Fall 1992 It is fairly involved, and you probably couldn't turn it over to a K-12er to get a feel for whats going on, but its all in there. --Don--   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09852; 26 May 93 13:32 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa09846; 26 May 93 13:32 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa16410; 26 May 93 13:32 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa17969; 26 May 93 13:24 EDT Received: from atlas.xylogics.com by NNSC.NSF.NET id aa17965; 26 May 93 13:23 EDT Received: by atlas.xylogics.com id AA11811 (5.65c/UK-2.1-930202); Wed, 26 May 1993 13:26:02 -0400 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Gary Scott Malkin Date: Wed, 26 May 1993 13:26:02 -0400 Message-Id: <11811.199305261726@atlas.xylogics.com> To: morris@niwot.scd.ucar.edu Cc: us-wg@nnsc.nsf.net In-Reply-To: Don Morris's message of Wed, 26 May 93 10:02:00 MDT <9305261602.AA17932@niwot.scd.ucar.EDU> Subject: Intro material needed Assuming I can find a copy of that journal :-) ---------------------------------------------------------------------- Gary Malkin Remember- take care of your feet, (617) 272-8140 and always have respect for cows.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10037; 26 May 93 13:36 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10030; 26 May 93 13:36 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa16528; 26 May 93 13:36 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa18020; 26 May 93 13:31 EDT Received: from taunivm.tau.ac.il by NNSC.NSF.NET id aa18016; 26 May 93 13:30 EDT Received: from TAUNIVM.TAU.AC.IL by VM.TAU.AC.IL (IBM VM SMTP V2R1) with BSMTP id 1741; Wed, 26 May 93 20:30:13 IST Received: from TAUNIVM.TAU.AC.IL (NJE origin A79@TAUNIVM) by TAUNIVM.TAU.AC.IL (LMail V1.1d/1.7f) with RFC822 id 1200; Wed, 26 May 1993 20:30:13 +0200 Date: Wed, 26 May 93 20:05:39 IST Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: David Sitman Subject: Re: Intro material needed To: us-wg@nnsc.nsf.net In-Reply-To: Your message of Wed, 26 May 1993 11:02:01 -0400 Message-ID: <9305261336.aa16528@CNRI.Reston.VA.US> On Wed, 26 May 1993 11:02:01 -0400 Gary Malkin said: >I've seen a lot of mail recently about how things are WAIS indexed >and gopherized and so on. What I don't see is a document which is >an introduction to this new generation of information retrieval. > >If there isn't anything out there which explains, Archie, Gopher, >WWW, WAIS, etc., and how they all interact with each other, then >maybe the USWG should consider writing something. I know I would >find it useful. That's exactly what we (EARN) thought a few months ago, so we put together the Guide to Network Resource Tools. Our purpose was to give someone unfamiliar with these tools a basic idea of what each tool is, instructions on how to start using it and pointers to more information. It covers Gopher, WAIS, WWW, Archie, Listserv, Netnews and several other tools (a few of which are rather EARNcentric). The first edition, a rush job, was published, warts and all, in time for a European conference earlier this month. We are committed to producing a much-improved second edition in time for the Network Services Conference in Warsaw in October. We would welcome comments and criticisms from US-WG members. We would also be quite interested in turning it into an FYI, with the help of US-WG. The guide is available via Listserv in plain text and Postscript versions. Send mail to LISTSERV@EARNCC.BITNET with the line: GET NETTOOLS MEMO (plain text version) or GET NETTOOLS PS (Postscript version) The guide should now be available from ripe.net for access via FTP, gopher, WAIS and WWW (at ftp.ripe.net, gopher.ripe.net, wais.ripe.net, etc.) If not, it will be available in the near future. I have noticed that others have made it available via gopher as well, but without coordinating with us, so there is no guarantee of timely updates at those sites. We also printed several thousand copies of the guide as a small booklet which we have distributed to representatives in EARN member countries. I was quite surprised at the very positive response we received: "Finally, something on paper!" David Sitman EARN   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10977; 26 May 93 14:21 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10971; 26 May 93 14:21 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa18489; 26 May 93 14:21 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa18362; 26 May 93 14:15 EDT Received: from mocha.bunyip.com by NNSC.NSF.NET id aa18353; 26 May 93 14:15 EDT Received: from expresso.Bunyip.Com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA10744 (mail destined for us-wg@NNSC.NSF.NET) on Wed, 26 May 93 14:15:12 -0400 Received: by expresso.bunyip.com (NX5.67c/NeXT-1.0) id AA06287; Wed, 26 May 93 14:11:20 -0400 Message-Id: <9305261811.AA06287@expresso.bunyip.com> Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Peter Deutsch Date: Wed, 26 May 1993 14:11:19 -0400 In-Reply-To: Gary Scott Malkin's message as of May 26, 13:26 X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Gary Scott Malkin , morris@niwot.scd.ucar.edu Subject: Re: Intro material needed Cc: us-wg@nnsc.nsf.net [ You wrote: ] > Assuming I can find a copy of that journal :-) Or have a functioning Internet connnection... ;-) Mike Schwartz has a copy of the paper on the machine "ftp.cs.colorado.edu" in the directory "/pub/cs/techreports/schwartz/[ ASCII | PostScript ]" (that means in either the ASCII or PostScript directories). The file is called "RD.Comparison.txt.Z" (at least it is in the ASCII directory, I didn't check in the PostScript directory). I pulled it across to make sure it's the right one, but as it's close to 40k I decided to post the pointer, instead of the whole thing (you're welcome). If anyone can't do an ftp or can't uncompress it I'd be glad to help. - peterd -- ------------------------------------------------------------------------------ Peter Deutsch, (514) 875-8611 (phone) Bunyip Information Systems Inc. (514) 875-8134 (fax) "Charging for information is not a crime, any more than charging for food is a crime. On the other hand, I agree that letting people _starve_ is a crime." ------------------------------------------------------------------------------   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11670; 26 May 93 14:42 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11664; 26 May 93 14:42 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa19248; 26 May 93 14:42 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa18571; 26 May 93 14:32 EDT Received: from zephyr.isi.edu by NNSC.NSF.NET id aa18567; 26 May 93 14:31 EDT Received: by zephyr.isi.edu (5.65c/5.61+local-10) id ; Wed, 26 May 1993 11:31:08 -0700 Date: Wed, 26 May 1993 11:31:08 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Joyce Reynolds Message-Id: <199305261831.AA26273@zephyr.isi.edu> To: A79%TAUNIVM.TAU.AC.IL@taunivm.tau.ac.il Subject: Re: Intro material needed Cc: us-wg@nnsc.nsf.net, gmalkin@xylogics.com David, Thanks for the note! BTW to the US-WG folks, the posting of David's announcement was made to this email list by me on 3 May, if you would like additional information. I have a hardcopy of the guide and have read it. The EARN folks should be congratulated (regardless of "warts and all")!! It is super and vital. Joyce   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08222; 27 May 93 11:20 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08216; 27 May 93 11:20 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa13123; 27 May 93 11:20 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa26378; 27 May 93 11:07 EDT Received: from zephyr.isi.edu by NNSC.NSF.NET id aa26374; 27 May 93 11:05 EDT Received: by zephyr.isi.edu (5.65c/5.61+local-10) id ; Thu, 27 May 1993 08:05:21 -0700 Date: Thu, 27 May 1993 08:05:21 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Joyce Reynolds Message-Id: <199305271505.AA17838@zephyr.isi.edu> To: us-wg@nnsc.nsf.net Subject: FYI19, RFC1463 on FYI--Short Bibliography ----- Begin Included Message ----- From ietf-announce-request@IETF.CNRI.Reston.VA.US Wed May 26 16:38:49 1993 To: IETF-Announce: ; Subject: FYI19, RFC1463 on FYI--Short Bibliography Cc: jkrey@ISI.EDU Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Date: Wed, 26 May 93 15:07:49 PDT Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US From: "Joyce K. Reynolds" Content-Length: 2889 --NextPart A new For Your Information (FYI) Request for Comments is now available in online RFC libraries. FYI 19: RFC 1463: Title: FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings Author: E. Hoffman & L. Jackson Mailbox: ellen@merit.edu, jackson@nsipo.arc.nasa.gov Pages: 4 Characters: 7,116 Updates/Obsoletes: none This bibliography offers a short list of recent information resources that will help the network novice become familiar with the Internet, including its associated networks, resources, protocols, and history. This FYI RFC includes references to free sources of information available on-line as well as traditional publications. A short section at the end includes information for accessing the on-line files. This FYI is intentionally brief so it can be easily used as a handout by user services personnel. This document is based upon the work of the User Documents Working Group in the User Services Area of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to "rfc-info@ISI.EDU" with the message body "help: ways_to_get_rfcs". For example: To: rfc-info@ISI.EDU Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC Authors", for further information. Joyce K. Reynolds USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mail-server@nisc.sri.com" Content-Type: text/plain SEND rfc1463.txt --OtherAccess Content-Type: Message/External-body; name="rfc1463.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain --OtherAccess-- --NextPart-- ----- End Included Message -----   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08234; 27 May 93 11:21 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08228; 27 May 93 11:21 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa13162; 27 May 93 11:21 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa26370; 27 May 93 11:07 EDT Received: from zephyr.isi.edu by NNSC.NSF.NET id aa26366; 27 May 93 11:05 EDT Received: by zephyr.isi.edu (5.65c/5.61+local-10) id ; Thu, 27 May 1993 08:05:00 -0700 Date: Thu, 27 May 1993 08:05:00 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Joyce Reynolds Message-Id: <199305271505.AA17830@zephyr.isi.edu> To: us-wg@nnsc.nsf.net Subject: FYI20, RFC1462 on What is the Internet? ----- Begin Included Message ----- From ietf-announce-request@IETF.CNRI.Reston.VA.US Wed May 26 17:15:36 1993 To: IETF-Announce: ; Subject: FYI20, RFC1462 on What is the Internet? Cc: jkrey@ISI.EDU Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Date: Wed, 26 May 93 15:11:27 PDT Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US From: "Joyce K. Reynolds" Content-Length: 2656 --NextPart A new For Your Information (FYI) Request for Comments is now available in online RFC libraries. FYI 20: RFC 1462: Title: FYI on "What is the Internet?" Author: E. Krol & E. Hoffman Mailbox: e-krol@uiuc.edu, ellen@merit.edu Pages: 11 Characters: 27,811 Updates/Obsoletes: none This FYI RFC answers the question, "What is the Internet?" and is produced by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). Containing a modified chapter from Ed Krol's 1992 book, "The Whole Internet User's Guide and Catalog," the paper covers the Internet's definition, history, administration, protocols, financing, and current issues such as growth, commercialization, and privatization. We would like to thank O'Reilly & Associates for permission to reprint the chapter for use in this FYI RFC. This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to "rfc-info@ISI.EDU" with the message body "help: ways_to_get_rfcs". For example: To: rfc-info@ISI.EDU Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC Authors", for further information. Joyce K. Reynolds USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mail-server@nisc.sri.com" Content-Type: text/plain SEND rfc1462.txt --OtherAccess Content-Type: Message/External-body; name="rfc1462.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain --OtherAccess-- --NextPart-- ----- End Included Message -----   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa25906; 31 May 93 12:34 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa25900; 31 May 93 12:34 EDT Received: from NNSC.NSF.NET by CNRI.Reston.VA.US id aa25042; 31 May 93 12:34 EDT Received: from nnsc.nsf.net by NNSC.NSF.NET id aa25329; 31 May 93 12:32 EDT Received: from merit.edu by NNSC.NSF.NET id aa25325; 31 May 93 12:30 EDT Return-Path: Received: from tyche.merit.edu by merit.edu (5.65/1123-1.0) id AA25667; Mon, 31 May 93 12:30:33 -0400 Received: by tyche.merit.edu (4.1/client-0.9) id AA05405; Mon, 31 May 93 12:30:31 EDT Date: Mon, 31 May 93 12:30:31 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: psmith@merit.edu Message-Id: <9305311630.AA05405@tyche.merit.edu> To: nisi@merit.edu, us-wg@nnsc.nsf.net Subject: accessing nic-profiles through Gopher Cc: psmith@merit.edu Please excuse the duplication of this note. Just wanted to point out that we can access nic-profiles through Gopher. Go to the main gopher/phone books/x.500 gateway/nic-profiles In the not-to-distant (she says, optimistically) future, some mods will be made to customize the searching ability for the profiles. As always, questions/comments to psmith@merit.edu. --------Pat Smith Merit Network, Inc. Ann Arbor, MI 48109-2016 313-936-3000-------------