Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07169; 1 May 95 14:38 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07165; 1 May 95 14:38 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa12711; 1 May 95 14:38 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Mon, 1 May 1995 18:42:01 +0100 Received: from gatepas.gc.ca by bells.cs.ucl.ac.uk with Internet SMTP id ; Mon, 1 May 1995 18:41:40 +0100 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: /DD.NTADDR=NJM03-SEG-DATA0#l#a#r#HWC/S=NJM03-SEG-DATA0/@lotus.hc-sc.x400.gc.ca Reply-To: /DD.NTADDR=NJM03-SEG-DATA0#l#a#r#HWC/S=NJM03-SEG-DATA0/@lotus.hc-sc.x400.gc.ca Errors-To: /DD.NTADDR=NJM03-SEG-DATA0#l#a#r#HWC/S=NJM03-SEG-DATA0/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@x400.gc.ca Date: Mon, 01 May 1995 13:41:36 -0400 Priority: normal Content-Identifier: Re: I-D ACTION:d X400-Content-Type: P2-1984 X400-MTS-Identifier: [/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/;XGW-950501134136-0400-04975] To: /DD.NTADDR=anne_philpott#l#a#r#hwc/G=anne/S=philpott/@lotus.hc-sc.x400.gc.ca, gatepas.gc.ca@gatepas Cc: osi-ds@cs.ucl.ac.uk Subject: Re: I-D ACTION:draft-ietf-osids-cldap-02.txt Message-Id: <"0501174136-Re: I-D ACTION:draft-ietf-osids-cldap-02.txt"*/DD.NTADDR=NJM03-SEG-DATA0#l#a#r#HWC/S=NJM03-SEG-DATA0/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@MHS> Importance: normal Hhhhmmmm..... On Apr 24, 5:17, /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpo wrote: > Subject: I-D ACTION:draft-ietf-osids-cldap-02.txt > -> --MIMEboundary950424081838.4734 -> Content-type: application/Bilaterally Defined -> Content-transfer-encoding: base64 -> Content-Description: body2 -> -> Q29udGVudC1UeXBlOiB0ZXh0L3BsYWluCkNvbnRlbnQtSUQ6IDwxOTk1MDQyMDE2MDUyMy5J -> LURAQ05SSS5SZXN0b24uVkEuVVM+CgpFTkNPRElORyBtaW1lCkZJTEUgL2ludGVybmV0LWRy -> YWZ0cy9kcmFmdC1pZXRmLW9zaWRzLWNsZGFwLTAyLnR4dAo= The above base64 decodes to...: -> Content-Type: text/plain -> Content-ID: <19950420160523.I-D@CNRI.Reston.VA.US> -> -> ENCODING mime -> FILE /internet-drafts/draft-ietf-osids-cldap-02.tx I've been unable to find any reference to Content-Type: application/Bilaterally Defined. I'm using...: URL:ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application as a reference to the known MIME types. Is there somewhere else I should be looking? -- Cheers! [ psr ]   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07195; 1 May 95 14:39 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07191; 1 May 95 14:39 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa12729; 1 May 95 14:39 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Mon, 1 May 1995 18:18:03 +0100 Received: from gatepas.gc.ca by bells.cs.ucl.ac.uk with Internet SMTP id ; Mon, 1 May 1995 18:17:36 +0100 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca Reply-To: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca Errors-To: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@x400.gc.ca Date: Mon, 01 May 1995 13:17:23 -0400 Priority: normal Content-Identifier: Re: I-D ACTION:d X400-Content-Type: P2-1984 X400-MTS-Identifier: [/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/;XGW-950501131723-0400-01017] To: /DD.NTADDR=anne_philpott#l#a#r#hwc/G=anne/S=philpott/@lotus.hc-sc.x400.gc.ca, gatepas.gc.ca@gatepas Cc: osi-ds@cs.ucl.ac.uk Subject: Re: I-D ACTION:draft-ietf-osids-cldap-02.txt Message-Id: <"0501171723-Re: I-D ACTION:draft-ietf-osids-cldap-02.txt"*/DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@MHS> Importance: normal Hhhhmmmm..... On Apr 24, 5:17, /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpo wrote: > Subject: I-D ACTION:draft-ietf-osids-cldap-02.txt > -> --MIMEboundary950424081838.4734 -> Content-type: application/Bilaterally Defined -> Content-transfer-encoding: base64 -> Content-Description: body2 -> -> Q29udGVudC1UeXBlOiB0ZXh0L3BsYWluCkNvbnRlbnQtSUQ6IDwxOTk1MDQyMDE2MDUyMy5J -> LURAQ05SSS5SZXN0b24uVkEuVVM+CgpFTkNPRElORyBtaW1lCkZJTEUgL2ludGVybmV0LWRy -> YWZ0cy9kcmFmdC1pZXRmLW9zaWRzLWNsZGFwLTAyLnR4dAo= The above base64 decodes to...: -> Content-Type: text/plain -> Content-ID: <19950420160523.I-D@CNRI.Reston.VA.US> -> -> ENCODING mime -> FILE /internet-drafts/draft-ietf-osids-cldap-02.tx I've been unable to find any reference to Content-Type: application/Bilaterally Defined. I'm using...: URL:ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application as a reference to the known MIME types. Is there somewhere else I should be looking? -- Cheers! [ psr ]   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13326; 1 May 95 19:07 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13322; 1 May 95 19:07 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa18843; 1 May 95 19:07 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Mon, 1 May 1995 21:22:54 +0100 Received: from x400gate.bnr.ca by bells.cs.ucl.ac.uk with Internet SMTP id ; Mon, 1 May 1995 21:22:18 +0100 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Mon, 1 May 1995 16:20:29 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Mon, 1 May 1995 16:20:20 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Mon, 1 May 1995 16:20:00 -0400 Date: Mon, 1 May 1995 16:20:00 -0400 X400-Originator: /dd.id=1660747/g=peter/i=pw/s=whittaker/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars520.b.274:01.04.95.20.20.20] X400-Content-Type: P2-1984 (2) Content-Identifier: Bug in QUIPU'... Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "peter (p.w.) whittaker" X-Orig-Sender: "peter (p.w.) whittaker" Message-ID: <"9277 Mon May 1 16:20:22 1995"@bnr.ca> To: osi-ds@cs.ucl.ac.uk, quipu@cs.ucl.ac.uk, bug-quipu@isode.com Subject: Bug in QUIPU's handling of searches at different levels of tree? I have noticed some bizarre behavior in how QUIPU (IC 1.1v3) handles searches at different levels of the DIT. Nutshell summary: Searches for sn=allen, sn="*allen*", cn="*allen" all succeed if searching at or below second level of the DIT (@c=US@o=test1). Searches for sn="*allen*", cn="*allen" succeed when searching at first level of the DIT (c=US). As you would expect. Searches for sn=allen at the first level of the tree (c=US) fail! Why? Why should a wildcard search (sn="*allen*") succeed at the first level of the tree and a very specific search (sn=allen) fail? Slightly less terse summary: DSA configuration: DSA configured to allow searches at level 0 (root) or 1 (country) (tests below performed against both cases). DIT structure: one country (c=US), two organizations (o=test1 and o=test2) directly below c=US, people and OUs below test[12]. No list ACLs or search ACLs in place. Actual ACLs allow global reading and returning of all data, used primarily to control write/modify access. Several entries with sn=allen or cn="*allen*" exist. Tree @c=US index for surname and commonName. Non-optimized searches OK. Now the bizarre behaovior: search command (from dish or from an LDAP client): base c=US@test1 filter sn="*allen*" scope subtree result: success AS YOU'D EXPECT search command (from dish or from an LDAP client): base c=US@test1 filter cn="*allen*" scope subtree result: success AS YOU'D EXPECT search command (from dish or from an LDAP client): base c=US@o=test1 filter sn=allen scope subtree result: success AS YOU'D EXPECT search command (from dish or from an LDAP client): base c=US filter sn="*allen*" scope subtree result: success AS YOU'D EXPECT search command (from dish or from an LDAP client): base c=US filter cn="*allen*" scope subtree result: success AS YOU'D EXPECT search command (from dish or from an LDAP client): base c=US filter sn=allen scope subtree result: failure THAT'S BIZARRE. WHY? pww Peter Whittaker [~~~~~~~~~~~~~~~~~~~~~~~~~~] X.500 DS Specialist pww@entrust.com [ ] NORTEL Secure Networks Ph: +1 613 765 2064 [ ] P.O. Box 3511, Station C FAX:+1 613 765 3520 [__________________________] Ottawa, Canada, K1Y 4H7   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04479; 3 May 95 12:19 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04472; 3 May 95 12:19 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa10188; 3 May 95 12:19 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Wed, 3 May 1995 16:40:12 +0100 Received: from bastion.sware.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 3 May 1995 16:39:40 +0100 Received: from shlep.sware.com (shlep.sware.com [139.131.1.14]) by bastion.sware.com (8.6.5/8.6.5) with SMTP id LAA02604; Wed, 3 May 1995 11:28:51 -0401 Received: by shlep.sware.com (5.65/2.0) from alehouse.sware.com id AA12346; Wed, 3 May 95 11:34:12 -0400 Received: by alehouse.sware.com (5.65/2.1) from localhost id AA01924; Wed, 3 May 95 11:34:02 -0400 X-Orig-Sender: "Luis P. Caamano" Message-Id: <9505031534.AA01924@alehouse.sware.com> Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Luis P. Caamano" X-Mailer: InterMail [2.0 alpha3] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: quipu , OSI-DS , ldap@umich.edu Subject: LDAP on DSA instead of separate process. Date: Wed, 03 May 95 11:34:02 EDT Sorry for the crossposting, but the subject seems appropriate for all three lists. We have a situation where we need to write several utility programs that query an X.500 directory. We would like to use the LDAP client library for this in order to use plain sockets and minimize the overhead. The problem is that we would like not to need the ldapd daemon. We want to have only two processes talking: the client program and the DSA. The first thought is to add LDAP support to the DSA. That is, make the DSA listen on port 389 also, merge in LDAP support and eliminate the ldapd. Now the question, has this been done? Is this crazy or does it make sense? thanks ---------------------------------------------------------------- Luis P. Caamano (LC2385) | lpc@sware.com SecureWare, Inc. Atlanta, GA, USA | (404) 315-6296   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04518; 3 May 95 12:21 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04514; 3 May 95 12:21 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa10251; 3 May 95 12:21 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Wed, 3 May 1995 14:56:15 +0100 Received: from thoth.mch.sni.de by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 3 May 1995 14:56:05 +0100 Received: from macbeth.mch.sni.de by thoth.mch.sni.de with SMTP id AA15530 (5.67a/IDA-1.5 for ); Wed, 3 May 1995 15:55:55 +0200 Received: (from kapur@localhost) by macbeth.mch.sni.de (8.6.9/8.6.9) id PAA22866 for osi-ds@cs.ucl.ac.uk; Wed, 3 May 1995 15:55:53 +0200 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Kapur Sandeep Message-Id: <199505031355.PAA22866@macbeth.mch.sni.de> Subject: HELP To: osi-ds@cs.ucl.ac.uk Date: Wed, 3 May 1995 15:55:53 +0200 (DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 10 subscribe   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08751; 3 May 95 16:37 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08747; 3 May 95 16:37 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa15676; 3 May 95 16:36 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Wed, 3 May 1995 17:21:48 +0100 Received: from x400gate.bnr.ca by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 3 May 1995 17:21:08 +0100 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 3 May 1995 12:18:58 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 3 May 1995 12:18:48 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 3 May 1995 12:17:00 -0400 Date: Wed, 3 May 1995 12:17:00 -0400 X400-Originator: /dd.id=1616671/g=sharon/i=sm/s=boeyen/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.153:03.04.95.16.18.48] X400-Content-Type: P2-1984 (2) Content-Identifier: 1993 X.500 Pu... Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "sharon (s.m.) boeyen" X-Orig-Sender: "sharon (s.m.) boeyen" Message-ID: <"19155 Wed May 3 12:18:50 1995"@bnr.ca> To: nadf-l@ema.org, OSIdirectory@az.05.bull.com, OSI-ds@cs.ucl.ac.uk, dssig@nist.gov Subject: 1993 X.500 Published FYI, While in Geneva last week I purchased a print copy of the 1993 X.500 Recommendations. I understand that these either are or will be made available (for purchase) on the ITU TIES system as well. Publication had just occurred and the publications desk wasn't yet set up for the orders, but they are now. I don't know how long before these will be available through the other channels (e.g. UN Bookstore in New York), but thought I'd pass along the word that formal publication has FINALLY happened. Sharon Boeyen   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14460; 8 May 95 22:25 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14452; 8 May 95 22:25 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa21029; 8 May 95 22:25 EDT X400-Received: by mta haig.cs.ucl.ac.uk in /PRMD=uk.ac/ADMD=gold 400/C=gb/; Relayed; Fri, 5 May 1995 08:22:17 +0100 Date: Fri, 5 May 1995 08:22:17 +0100 X400-Originator: osi-ds-request@cs.ucl.ac.uk X400-Recipients: non-disclosure:; X400-MTS-Identifier: [/PRMD=uk.ac/ADMD=gold 400/C=gb/;haig.cs.uc.032:05.04.95.07.22.17] Priority: Non-Urgent DL-Expansion-History: osi-ds@cs.ucl.ac.uk ; Fri, 5 May 1995 08:22:17 +0100; Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Alan Shepherd Message-ID: <17103.799658492@nexor.co.uk> To: panamas@paradise.ulcc.ac.uk, osi-ds@cs.ucl.ac.uk Subject: Root level prodir combined results Reply-To: prodir-support@nexor.co.uk *** N.B. The probing results below are influenced by network failures *** *See also: the WWW entry, "http://web.nexor.co.uk/users/quipu/x500/graphroot.gif" Probing from SWITCH@Zurich, SURFnet@Delft, NEXOR, ULCC, Cambridge Computer Lab, Community: internet ========== ======== No DSAs had 100.00% availability. Other DSAs: ----- ----- %Avail Organisation,DSA Attempts Average Time ------ ---------------- -------- ------------ 99.21 SURFnet, Hornero 632 0.81 4 Timed out after 60 seconds 99.05 Inmarsat, Hedgehog 632 2.20 4 Timed out after 60 seconds 98.89 ARNES, Proteus 633 1.35 5 Timed out after 60 seconds 1 Connection refused 98.76 Unknown Organisation, opaxdsa, CNRS, FR 161 1.66 2 Timed out after 60 seconds 98.73 DFN, Margay 632 3.86 7 Timed out after 60 seconds 98.58 SWITCH, Condor 632 1.47 7 Timed out after 60 seconds 98.26 UNINETT, Electric Eel 632 1.75 6 Timed out after 60 seconds 98.10 ULCC, Giant Tortoise 632 1.95 8 Timed out after 60 seconds 1 Connection refused 97.94 SWITCH, Chinchilla 632 1.30 7 Timed out after 60 seconds 2 Connection refused 1 Unavailable 97.94 North Atlantic Treaty Or..., Violaceous Trogon 632 1.65 11 Timed out after 60 seconds 1 Host is unreachable 97.78 Restena, Guppy 632 5.13 14 Timed out after 60 seconds 97.63 SUNET, Andean Cat 632 1.42 11 Timed out after 60 seconds 1 Connection refused 97.63 DKUUG, Axolotl 632 7.50 11 Timed out after 60 seconds 97.47 UMK, Ocelot 632 8.41 10 Timed out after 60 seconds 1 Unavailable 4 Host is unreachable 97.31 Victoria University of W..., Kakapo 632 3.80 15 Timed out after 60 seconds 1 Connection refused 1 Unavailable 96.99 Universidad Politecnica ..., Cayman 632 2.80 8 Timed out after 60 seconds 5 Host is unreachable 1 Connection refused 96.84 ULCC, Ocellated Turkey 632 1.33 6 Connection refused 10 Timed out after 60 seconds 96.68 UNINETT, Boa Constrictor 633 2.58 8 Connection refused 7 Timed out after 60 seconds 96.68 Unknown Organisation, Dorcan Gazelle 632 7.86 15 Timed out after 60 seconds 96.52 RedIRIS, iguana 632 2.04 8 Timed out after 60 seconds 6 Connection refused 3 Host is unreachable 95.89 ULCC, Inca Dove 632 1.16 20 Timed out after 60 seconds 3 Connection refused 95.73 RCCN Portugal, Zebu 632 7.73 3 Connection refused 11 Timed out after 60 seconds 1 Unavailable 6 Host is unreachable 95.41 National Computer Board ..., Lion 632 8.81 2 Connection refused 14 Timed out after 60 seconds 1 Host is unreachable 95.41 Technische Universitaet ..., Puma 632 2.88 1 Unavailable 20 Timed out after 60 seconds 1 Connection refused 95.26 Matej Bel University, UA..., Tarpon 633 6.52 14 Timed out after 60 seconds 1 Unavailable 1 Host is unreachable 94.15 Prague University of Eco..., woolly opossum 632 5.51 22 Timed out after 60 seconds 1 Unavailable 3 Connection refused 1 Host is unreachable 93.99 Unknown Organisation, opaxdsa, CNRS, FR 632 3.35 27 Timed out after 60 seconds 2 Unavailable 3 Connection refused 93.51 WIDE project, Sloth 632 4.95 21 Timed out after 60 seconds 92.72 GARR-NIS, Black Widow 632 3.12 32 Timed out after 60 seconds 1 Connection refused 91.47 SURIS, Elephant Seal 633 4.41 13 Timed out after 60 seconds 9 Connection refused 1 Unavailable 4 Host is unreachable 19 Invalid credentials 91.46 GARR-NIS, Black Widow 632 4.22 39 Timed out after 60 seconds 1 Connection refused 90.98 Unknown Organisation, Corncrake 632 3.29 10 Timed out after 60 seconds 34 Connection refused 90.36 Vrije Universiteit Brussel, Woolly Spider... 467 7.01 5 Connection refused 37 Timed out after 60 seconds 90.03 Foundation Of Research a..., Caretta Caretta 632 8.76 43 Timed out after 60 seconds 2 Connection refused 1 Unavailable 90.03 FUNET, Jaguar 632 1.70 41 Connection refused 9 Timed out after 60 seconds 89.40 U.S. DMD, Fruit Bat 632 4.78 27 Timed out after 60 seconds 17 Connection refused 1 Unavailable 88.92 U.S. DMD, alpaca 632 4.05 30 Timed out after 60 seconds 21 Connection refused 1 Host is unreachable 88.61 Universitaet Wien, Rockhopper Pe... 632 5.02 37 Timed out after 60 seconds 17 Host is unreachable 88.13 Australian Academic and ..., Anaconda 632 7.33 48 Timed out after 60 seconds 6 Unavailable 1 Host is unreachable 1 Connection refused 87.97 SUNET, Hummingbird 632 1.37 53 Connection refused 5 Timed out after 60 seconds 87.50 UNI-C, Armadillo 632 1.46 16 Timed out after 60 seconds 45 Connection refused 86.73 Australian Academic and ..., Bush Dog 633 7.08 2 Unavailable 43 Timed out after 60 seconds 7 Connection refused 1 Host is unreachable 84.81 Moscow State University, Bear 632 4.21 67 Timed out after 60 seconds 1 Connection refused 6 Host is unreachable 82.97 Brussels University, Red Titi Monkey 634 27.06 49 Timed out after 60 seconds 3 Unavailable 2 Connection refused 78.80 NSTN Inc, beluga whale 632 5.65 56 Timed out after 60 seconds 37 Connection refused 2 Unavailable 76.30 U.S. DMD, Pied Tamarin 633 7.84 29 Timed out after 60 seconds 67 Connection refused 1 Unavailable 70.73 Swiss Telecom PTT, TellXdir 632 0.91 16 Timed out after 60 seconds 1 Connection refused 67.09 Unknown Organisation, Long Moustach... 632 9.11 84 Timed out after 60 seconds 69 Connection refused 45.09 Trinity College Dublin, Irish Elk 632 4.85 252 Connection refused 8 Timed out after 60 seconds 41.17 Universidade Federal do ..., paca 634 11.33 46 Timed out after 60 seconds 200 Connection refused 2 Unavailable 1 Host is unreachable 40.88 IIT Delhi, IN, Pelican 636 19.56 30 Timed out after 60 seconds 65 Host is unreachable 4 Connection refused 1 Unavailable 24.65 FUNET, Northern Pudu 637 2.28 349 Connection refused 5 Timed out after 60 seconds 19.69 Tallinn Technical University, saki 635 2.63 340 Connection refused 7 Timed out after 60 seconds 0.00 Master DSA of KOREA, Darter 632 0.00 467 Timed out after 60 seconds 0.00 Computer and Automation ..., Guinea Pig 632 0.00 462 Connection refused 5 Timed out after 60 seconds 0.00 University of Zagreb - F..., Roufous Motmot 632 0.00 356 Connection refused 92 Timed out after 60 seconds 1 Host is unreachable   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08574; 18 May 95 13:48 EDT Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa08570; 18 May 95 13:48 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa12807; 18 May 95 13:47 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Thu, 18 May 1995 18:06:12 +0100 Received: from terminator.rs.itd.umich.edu by bells.cs.ucl.ac.uk with Internet SMTP id ; Thu, 18 May 1995 18:06:02 +0100 Received: from terminator.rs.itd.umich.edu by terminator.rs.itd.umich.edu (8.6.12/2.3) with SMTP id LAA14412; Thu, 18 May 1995 11:23:05 -0400 Message-Id: <199505181523.LAA14412@terminator.rs.itd.umich.edu> Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tim Howes To: P.Deveze@frec.bull.fr cc: osi-ds@cs.ucl.ac.uk Subject: Re: Looking for an LDAP client In-reply-to: Your message of "Wed, 17 May 1995 16:27:17 BST." <9505171427.AA10314@yoko.frec.bull.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 18 May 1995 11:23:05 -0400 X-Orig-Sender: tim@terminator.rs.itd.umich.edu > From: P.Deveze@frec.bull.fr (pascal Deveze) > To: osi-ds@cs.ucl.ac.uk > We have one running version of an LDAP server on a machine that runs an X500 > product. We are now looking for an LDAP client (shareware release) on PC/Windo > and/or on X/MOTIF to complete our configuration and to propose a nice user > interface. > > Maybe some of you have judicious advice on that subject. I'll be very happy to > get information directly from experts. You might check out this web page: http://www.umich.edu/~rsug/ldap/ It contains a list of clients, among other things. We're still building the list, but it's got some stuff now. -- Tim   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08593; 18 May 95 13:49 EDT Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa08588; 18 May 95 13:48 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa12832; 18 May 95 13:48 EDT Received: from cs.ucl.ac.uk by haig.cs.ucl.ac.uk via Local Delivery channel id ; Thu, 18 May 1995 13:17:53 +0100 Old-Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Wed, 17 May 1995 15:17:56 +0100 Old-Received: from ecbull.frec.bull.fr by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 17 May 1995 15:17:40 +0100 Old-Received: from yoko.frec.bull.fr by ecbull.frec.bull.fr; Wed, 17 May 1995 16:14:56 +0200 (MET) Old-Received: by yoko.frec.bull.fr; Wed, 17 May 95 16:27:19 +0200 (MET) Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: pascal Deveze Message-Id: <9505171427.AA10314@yoko.frec.bull.fr> Subject: Looking for an LDAP client To: osi-ds@cs.ucl.ac.uk Date: Wed, 17 May 1995 16:27:17 +0100 (EET) Reply-To: P.Deveze@frec.bull.fr Return-Path: Organization: Bull S.A. (Echirolles) X-Mailer: ELM [version 2.4 PL2] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Length: 995 Resent-Date: Thu, 18 May 1995 13:17:53 +0100 Resent-From: Postmaster@cs.ucl.ac.uk Resent-To: osi-ds@cs.ucl.ac.uk We have one running version of an LDAP server on a machine that runs an X500 product. We are now looking for an LDAP client (shareware release) on PC/Windows and/or on X/MOTIF to complete our configuration and to propose a nice user interface. Maybe some of you have judicious advice on that subject. I'll be very happy to get information directly from experts. Thank you for your possible answer, Pascal +----------------------------------------------------------------------+ Pascal Deveze Org. : OSS/OSB/XCOM/A&S Bull S.A. E.Mail : P.Deveze@frec.bull.fr 1, Rue de Provence Phone : + (33) 76 29 78 68 B.P. 208 Fax : + (33) 76 29 77 70 38432 ECHIROLLES CEDEX Bullcom : (229) 78 68 FRANCE P.C. : FREC B1-319 +----------------------------------------------------------------------+ "Save trees and forests, use electronic Mail ...."   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14679; 18 May 95 18:33 EDT Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa14675; 18 May 95 18:33 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa18449; 18 May 95 18:33 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Thu, 18 May 1995 19:22:03 +0100 Received: from ceres.fokus.gmd.de by bells.cs.ucl.ac.uk with Internet SMTP id ; Thu, 18 May 1995 19:21:50 +0100 Received: from fokus.gmd.de by ceres.fokus.gmd.de id <10320-0@ceres.fokus.gmd.de>; Thu, 18 May 1995 20:18:43 +0200 To: panamas@paradise.ulcc.ac.uk, osi-ds@cs.ucl.ac.uk, rosenqui@esltd.com Subject: XDS based experience....... Date: Thu, 18 May 1995 20:18:43 +0200 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "P.G. Tsigaridas" X-Orig-Sender: tsigaridas@fokus.gmd.de Message-ID: <9505181833.aa18449@CNRI.Reston.VA.US> Hi, i am currently working in a project, which objectives are: a) case studies describing a DUA or DUA API written on top of XDS being ported amongst several XDS implementations (currently ISODE & HP Open View). b) developing a portable DUA or DUA API (using the XDS ISODE plattform), that can then been ported in a another plattform (e.g HP Open View), just by compiling the own code and the ASN.1 definitios in the new plattform. We are looking for the best way to develop something like this above, without loosing the flexibility, which is provided, for example, currently by "libdsap.a" and "libdish.a" in the ISODE plattform. Is there people having experience with APIs written on the top of XDS ?. I'd be interested in any experiences poeple had. Thanks in advance Panos Tsigaidas.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16035; 18 May 95 21:03 EDT Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa16031; 18 May 95 21:03 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa20630; 18 May 95 21:03 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Fri, 19 May 1995 01:06:40 +0100 Received: from shark.mel.dit.CSIRO.AU by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 19 May 1995 01:04:58 +0100 Received: from conger.mel.dit.CSIRO.AU by shark.mel.dit.csiro.au with SMTP id AA01161 (5.65c/IDA-1.4.4/DIT-1.3 for osi-ds@cs.ucl.ac.uk); Fri, 19 May 1995 10:03:13 +1000 Message-Id: <199505190003.AA01161@shark.mel.dit.csiro.au> To: "P.G. Tsigaridas" Cc: panamas@paradise.ulcc.ac.uk, osi-ds@cs.ucl.ac.uk, rosenqui@esltd.com, ajw@mel.dit.csiro.au Subject: Re: XDS based experience....... In-Reply-To: Your message of "Thu, 18 May 1995 20:18:43 +0200." <"brolga.cc.uq:293250:950518215239"@cc.uq.oz.au> Date: Fri, 19 May 1995 10:03:12 +1000 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Andrew Waugh Panos, > i am currently working in a project, which objectives are: > > a) case studies describing a DUA or DUA API written on top > of XDS being ported amongst several XDS implementations > (currently ISODE & HP Open View). I've not seen any work which tested the actual portability of XDS applications. (Or, for that matter, the portability of applications which used the related X.400 and X.700 APIs.) If anyone is aware of any I'd like to know. In practice, I'd expect some problems. First, because there hasn't been any portability testing. The XDS/XOM standards are complicated enough that individual implementors can make subtly different interpretations of the text and hence produce implementations that are not portable. The solution to this is a 'portability bakeoff' where various vendors implementations are tested. A consensus of correct behaviour will quickly develop. The 'test' applications then form valuable resource for testing correct behaviour. This approach has worked well for the Internet, but I haven't heard of it being adopted with XDS. Second, because XDS is not a complete interface to X.500. In particular, it doesn't provide access to the authentication features when binding, nor has it been extended (as far as I know) to support the 1993 standard. Various implementations will have extended XDS in a variety of ad hoc ways to support these aspects. I will have practical experience of porting an XDS application within a couple of months! > b) developing a portable DUA or DUA API (using the XDS ISODE > plattform), that can then been ported in a another > plattform (e.g HP Open View), just by compiling the own > code and the ASN.1 definitios in the new plattform. > > We are looking for the best way to develop something like this > above, without loosing the flexibility, which is provided, for example, > currently by "libdsap.a" and "libdish.a" in the ISODE plattform. > Is there people having experience with APIs written on the top of > XDS ?. > I'd be interested in any experiences poeple had. I am not sure exactly what you want to do. XDS is designed to be portable amongst many different systems and has been widely adopted by vendors. If your goal is portability, you are unlikely to be able to design an API which is more portable than XDS - simply because you would have to convince the vendors to drop XDS and support your API. So your goal cannot be (or shouldn't be) portability. Is your goal to support the Quipu API on top of XDS? That would be a useful goal. The major problems you will have (speaking from experience, see below) is that it is very unlikely that the structure of the XDS operation requests/results will map exactly into the Quipu equivalents. They will *almost* directly map, but the exceptions will drive you insane! (And mean a large number of exceptions to be handled in code.) My experience comes from working on a short project to provide a text based interface to XDS. This constructs an XDS operation request from a textual description of an X.500 operation. It also does the converse for an X.500 result or error, allows the user to extract components of the result by name, and supports cutting and pasting X.500 components. The goal is to make it easier to use X.500, and to allow more readable (and hence maintainable) application code. The method is to produce a toolkit which hides the details of using XDS (for example, memory allocation, the structures used and how they are linked together, and what the structure fields are for and how they are set). andrew waugh   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09514; 19 May 95 14:10 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09510; 19 May 95 14:10 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa12304; 19 May 95 14:10 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Fri, 19 May 1995 15:29:08 +0100 Received: from URSA-MAJOR.SPDCC.COM by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 19 May 1995 15:28:49 +0100 Received: by ursa-major.spdcc.com with sendmail-5.65/4.7 id ; Fri, 19 May 95 10:28:24 -0400 Received: from park-st.bsw.com by redsox.bsw.com (4.1/SMI-4.1) id AA20828; Fri, 19 May 95 09:00:48 EDT Received: from haymarket.bsw.com by park-st.bsw.com (5.65/1.35) id AA01571; Fri, 19 May 95 10:00:27 -0400 X-Sender: campbell@park-st.bsw.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 19 May 1995 10:02:23 -0400 To: Andrew Waugh , "P.G. Tsigaridas" Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Larry Campbell Subject: Re: XDS based experience....... Cc: panamas@paradise.ulcc.ac.uk, osi-ds@cs.ucl.ac.uk, rosenqui@esltd.com, ajw@mel.dit.csiro.au At 10:03 AM 5/19/95, Andrew Waugh Panos, > >> i am currently working in a project, which objectives are: >> >> a) case studies describing a DUA or DUA API written on top >> of XDS being ported amongst several XDS implementations >> (currently ISODE & HP Open View). > >I've not seen any work which tested the actual portability of XDS >applications. (Or, for that matter, the portability of applications >which used the related X.400 and X.700 APIs.) If anyone is aware of >any I'd like to know. We have written an access unit that interfaces to many different X.400 MTAs using the X/Open MT interface. The access unit is used to connect to our InterOFFICE product, which is basically a message bus into which access units for several different email systems may be plugged, to build a large number of different gateways. The X.400 MTAs we have successfully interfaced with using the X/Open API include ISOPRO from ISOCOR, Messenger 400 from Infonet Software Solutions (formerly Osiware), OSI/6000 from IBM, SunLink X.400 from Sun, and OSI/MHS from Tandem (the only non-UNIX one, and also not really X/Open but "X/Open-like"). We're also in the process now of integrating with the ISODE implementation and with HP's X.400 product. Although each vendor's implementation had its own peculiarities (bugs), we have actually been fairly pleasantly surprised at how little conditional code we've had to write and at how smoothly the ports have gone after the initial implementation was debugged. (Well, maybe it's easy to pleasantly surprise a cynic.) Yes, we've had to work around some bugs, but ultimately we've gotten all of these interfaces to work pretty well.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09589; 19 May 95 14:14 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09585; 19 May 95 14:13 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa12387; 19 May 95 14:13 EDT X400-Received: by mta haig.cs.ucl.ac.uk in /PRMD=uk.ac/ADMD=gold 400/C=gb/; Relayed; Fri, 19 May 1995 08:23:12 +0100 Date: Fri, 19 May 1995 08:23:12 +0100 X400-Originator: osi-ds-request@cs.ucl.ac.uk X400-Recipients: non-disclosure:; X400-MTS-Identifier: [/PRMD=uk.ac/ADMD=gold 400/C=gb/;haig.cs.uc.067:19.04.95.07.23.12] Priority: Non-Urgent DL-Expansion-History: osi-ds@cs.ucl.ac.uk ; Fri, 19 May 1995 08:23:12 +0100; Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Alan Shepherd Message-ID: <28448.800868132@nexor.co.uk> To: panamas@paradise.ulcc.ac.uk, osi-ds@cs.ucl.ac.uk Subject: Root level prodir combined results Reply-To: prodir-support@nexor.co.uk *** N.B. The probing results below are influenced by network failures *** *See also: the WWW entry, "http://web.nexor.co.uk/users/quipu/x500/graphroot.gif" Probing from SURFnet@Delft, SWITCH@Zurich, NEXOR, ULCC, Cambridge Computer Lab, Community: internet ========== ======== The following DSAs were available 100% of the time: c=FR@o=CNRS@cn=opaxdsa Other DSAs: ----- ----- %Avail Organisation,DSA Attempts Average Time ------ ---------------- -------- ------------ 99.83 SURFnet, Hornero 596 0.92 1 Unavailable 99.66 Unknown Organisation, opaxdsa, CNRS, FR 596 2.74 1 Timed out after 60 seconds 1 Unavailable 99.66 North Atlantic Treaty Or..., Violaceous Trogon 596 1.85 2 Timed out after 60 seconds 98.99 SWITCH, Condor 596 1.33 5 Timed out after 60 seconds 1 Connection refused 98.66 FUNET, Northern Pudu 596 2.69 7 Timed out after 60 seconds 1 Invalid credentials 98.66 Universitaet Wien, Rockhopper Pe... 596 3.15 4 Connection refused 3 Timed out after 60 seconds 1 Host is unreachable 98.49 Victoria University of W..., Kakapo 596 4.65 9 Timed out after 60 seconds 98.32 ARNES, Proteus 597 1.31 8 Invalid credentials 1 Connection refused 1 Unavailable 97.90 Vrije Universiteit Brussel, Woolly Spider... 429 5.38 8 Connection refused 1 Timed out after 60 seconds 97.82 Inmarsat, Hedgehog 596 3.17 12 Timed out after 60 seconds 1 Invalid credentials 97.48 Moscow State University, Bear 596 4.59 13 Timed out after 60 seconds 1 Host is unreachable 1 Unavailable 97.32 ULCC, Inca Dove 596 1.58 12 Timed out after 60 seconds 4 Connection refused 97.32 Technische Universitaet ..., Puma 596 4.04 3 Connection refused 11 Timed out after 60 seconds 2 Invalid credentials 96.98 UNINETT, Boa Constrictor 596 2.45 12 Connection refused 1 Unavailable 5 Timed out after 60 seconds 96.98 ULCC, Giant Tortoise 596 1.93 17 Timed out after 60 seconds 1 Connection refused 95.81 SUNET, Hummingbird 596 1.39 8 Connection refused 11 Timed out after 60 seconds 6 Invalid credentials 95.13 RCCN Portugal, Zebu 596 9.18 18 Connection refused 11 Timed out after 60 seconds 94.30 Prague University of Eco..., woolly opossum 596 4.74 13 Host is unreachable 19 Timed out after 60 seconds 1 Unavailable 94.13 WIDE project, Sloth 596 5.91 3 Host is unreachable 29 Timed out after 60 seconds 1 Invalid credentials 2 Unavailable 92.95 DFN, Margay 596 4.73 16 Connection refused 15 Timed out after 60 seconds 11 Invalid credentials 92.79 Matej Bel University, UA..., Tarpon 596 5.34 1 Host is unreachable 13 Timed out after 60 seconds 29 Invalid credentials 92.68 ULCC, Ocellated Turkey 601 1.06 42 Timed out after 60 seconds 2 Connection refused 92.11 DKUUG, Axolotl 596 10.45 40 Timed out after 60 seconds 2 Connection refused 3 Unavailable 2 Host is unreachable 91.95 UNINETT, Electric Eel 596 1.86 48 Timed out after 60 seconds 91.61 National Computer Board ..., Lion 596 9.40 39 Timed out after 60 seconds 11 Invalid credentials 90.52 University of Zagreb - F..., Roufous Motmot 601 22.47 50 Timed out after 60 seconds 89.93 SURIS, Elephant Seal 596 4.82 10 Connection refused 2 Host is unreachable 42 Invalid credentials 6 Timed out after 60 seconds 88.76 Restena, Guppy 596 3.93 15 Timed out after 60 seconds 2 Host is unreachable 44 Connection refused 5 Invalid credentials 1 Unavailable 87.75 Unknown Organisation, Dorcan Gazelle 596 5.66 66 Timed out after 60 seconds 6 Invalid credentials 1 Connection refused 86.69 SUNET, Andean Cat 601 2.28 47 Connection refused 29 Timed out after 60 seconds 1 Invalid credentials 86.41 Australian Academic and ..., Anaconda 596 8.41 41 Timed out after 60 seconds 6 Unavailable 33 Invalid credentials 1 Host is unreachable 85.40 Australian Academic and ..., Bush Dog 596 8.23 65 Timed out after 60 seconds 19 Connection refused 1 Host is unreachable 2 Unavailable 84.56 NSTN Inc, beluga whale 596 8.99 59 Timed out after 60 seconds 1 Host is unreachable 32 Invalid credentials 84.23 UMK, Ocelot 596 13.09 22 Host is unreachable 71 Timed out after 60 seconds 1 Connection refused 84.23 U.S. DMD, Pied Tamarin 596 8.04 77 Timed out after 60 seconds 6 Connection refused 10 Invalid credentials 1 Unavailable 83.81 Brussels University, Red Titi Monkey 599 27.40 10 Connection refused 77 Timed out after 60 seconds 1 Unavailable *** (sent srcref of 0x11bb, got 0x0 (Mismatched references at transport) 8 Unavailable 1 Unavailable *** (sent srcref of 0x2a3b, got 0x0 (Mismatched references at transport) 83.22 Universidad Politecnica ..., Cayman 596 3.21 26 Timed out after 60 seconds 74 Connection refused 79.03 Foundation Of Research a..., Caretta Caretta 596 13.50 66 Timed out after 60 seconds 1 Host is unreachable 45 Connection refused 11 Invalid credentials 2 Unavailable 77.52 UNI-C, Armadillo 596 1.72 133 Timed out after 60 seconds 1 Unavailable 77.18 RedIRIS, iguana 596 2.61 59 Timed out after 60 seconds 77 Connection refused 67.00 Universidade Federal do ..., paca 597 11.44 76 Timed out after 60 seconds 36 Host is unreachable 81 Connection refused 3 Unavailable 66.00 U.S. DMD, alpaca 600 4.91 106 Connection refused 16 Timed out after 60 seconds 1 Unavailable 65.33 Unknown Organisation, Corncrake 597 3.79 148 Connection refused 30 Timed out after 60 seconds 4 Host is unreachable 25 Invalid credentials 63.99 U.S. DMD, Fruit Bat 597 6.48 197 Timed out after 60 seconds 2 Host is unreachable 16 Connection refused 59.90 Trinity College Dublin, Irish Elk 596 6.27 197 Connection refused 38 Timed out after 60 seconds 4 Unavailable 56.71 SWITCH, Chinchilla 596 1.18 88 Timed out after 60 seconds 170 Invalid credentials 50.42 GARR-NIS, Black Widow 601 2.79 34 Connection refused 253 Timed out after 60 seconds 7 Invalid credentials 1 Host is unreachable 50.08 GARR-NIS, Black Widow 601 5.82 35 Connection refused 258 Timed out after 60 seconds 6 Invalid credentials 42.28 Swiss Telecom PTT, TellXdir 596 0.86 244 Timed out after 60 seconds 2 Connection refused 97 Invalid credentials 29.95 IIT Delhi, IN, Pelican 601 19.79 218 Host is unreachable 13 Connection refused 177 Timed out after 60 seconds 3 Unavailable 1 Invalid credentials 17.95 FUNET, Jaguar 596 3.20 16 Timed out after 60 seconds 472 Connection refused 1 Unavailable 0.00 Master DSA of KOREA, Darter 596 0.00 594 Timed out after 60 seconds 2 Host is unreachable 0.00 Computer and Automation ..., Guinea Pig 596 0.00 587 Connection refused 5 Host is unreachable 4 Timed out after 60 seconds 0.00 Unknown Organisation, Long Moustach... 596 0.00 569 Connection refused 26 Timed out after 60 seconds 1 Host is unreachable 0.00 Tallinn Technical University, saki 596 0.00 573 Connection refused 2 Host is unreachable 10 Timed out after 60 seconds   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07530; 22 May 95 12:30 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09401; 22 May 95 12:30 EDT Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07501; 22 May 95 12:30 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07383; 22 May 95 12:26 EDT Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09331; 22 May 95 12:26 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa07378; 22 May 95 12:26 EDT To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ietf-osi-ds@cs.ucl.ac.uk Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: IESG Secretary Subject: Protocol Action: Connection-less Lightweight Directory Access Protocol to Proposed Standard Date: Mon, 22 May 95 12:26:49 -0400 X-Orig-Sender: scoya@CNRI.Reston.VA.US Message-ID: <9505221226.aa07378@IETF.CNRI.Reston.VA.US> The IESG has approved the Internet-Draft "Connection-less Lightweight Directory Access Protocol" as a Proposed Standard. This work was initiated in the [now defunct] OSI Directory Services Working Group and completed by the Access and Synchronization of the Internet Directories Working Group. The IESG contact person is Harald Tveit Alvestrand. Technical Summary The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP) as specified in X.500. In particular, it is aimed at avoiding the elapsed time that is associated with connection-oriented communication and it facilitates use of the Directory in a manner analagous to the DNS. It is specifically targeted at simple lookup applications that require to read a small number of attribute values from a single entry. It is intended to be a complement to DAP and LDAP (RFC 1487). The protocol specification draws heavily on that of LDAP (RFC 1487) that has proven to be the most widely used and implemented access protocol for X.500 to date. Advice on how to implement a retransmission strategy was added after the previous IESG review. Working Group Summary Most of the debate on CLDAP focused on improvements to LDAP. There was a clear concensus on the connectionless approach. Protocol Quality The specification has been reviewed by a member of the Applications Area Directorate and by one of the Area Directors.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09834; 22 May 95 14:08 EDT Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa09830; 22 May 95 14:08 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa11250; 22 May 95 14:08 EDT Received: from bastion.sware.com by haig.cs.ucl.ac.uk with Internet SMTP id ; Mon, 22 May 1995 15:38:02 +0100 Received: from shlep.sware.com (shlep.sware.com [139.131.1.14]) by bastion.sware.com (8.6.12/8.6.5) with SMTP id KAA01975; Mon, 22 May 1995 10:28:43 -0401 Received: by shlep.sware.com (5.65/2.0) from alehouse.sware.com id AA07230; Mon, 22 May 95 10:28:57 -0400 Received: by alehouse.sware.com (5.65/2.1) from localhost id AA25319; Mon, 22 May 95 10:25:37 -0400 X-Orig-Sender: "Luis P. Caamano" Message-Id: <9505221425.AA25319@alehouse.sware.com> Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Luis P. Caamano" X-Mailer: SecureMail [2.0 alpha4] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: quipu , OSI-DS , ldap@umich.edu Subject: Quipu's treeStructure attribute in oidtables Date: Mon, 22 May 95 10:25:37 EDT -----BEGIN PRIVACY-ENHANCED MESSAGE----- Proc-Type: 4,MIC-CLEAR Content-Domain: RFC822 Originator-Certificate: MIIBxDCCAW4CFQD+3dh80bkgena8z1dku13NAAAAADANBgkqhkiG9w0BAQIFADBZ MQswCQYDVQQGEwJVUzEYMBYGA1UEChMPU2VjdXJlV2FyZSBJbmMuMRcwFQYDVQQL Ew5TZWN1cmVXYXJlIFBDQTEXMBUGA1UECxMORW5naW5lZXJpbmcgQ0EwHhcNOTUw NTEwMTI1NTEwWhcNOTgwNTA5MTI1NTEwWjBwMQswCQYDVQQGEwJVUzEYMBYGA1UE ChMPU2VjdXJlV2FyZSBJbmMuMRcwFQYDVQQLEw5TZWN1cmVXYXJlIFBDQTEXMBUG A1UECxMORW5naW5lZXJpbmcgQ0ExFTATBgNVBAMTDEx1aXMgQ2FhbWFubzBZMAoG BFUIAQECAgIAA0sAMEgCQQDeftoWgYd1YSQVvsw426ceoEu5mnkSIlxu8ON8YTH3 0d+zi86sXhVwrTt2XvUqBWDTc8O3JwizaLdcSdKmqUGjAgMBAAEwDQYJKoZIhvcN AQECBQADQQA2GPvwoPpzt1dg0M+OKbYsHj7k+whCtIsZ6P71CrL0oe44c+Ees7iG /LpyQDwvnRlAyeoMO46JZ1MCnW4F1Ivj Issuer-Certificate: MIIBkzCCAT0CFEbO5h6/SKxULWrq4aExKoYAAAAAMA0GCSqGSIb3DQEBAgUAMEAx CzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9TZWN1cmVXYXJlIEluYy4xFzAVBgNVBAsT DlNlY3VyZVdhcmUgUENBMB4XDTk1MDUwODIwMjAxNloXDTk3MDUwNzIwMjAxNlow WTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1NlY3VyZVdhcmUgSW5jLjEXMBUGA1UE CxMOU2VjdXJlV2FyZSBQQ0ExFzAVBgNVBAsTDkVuZ2luZWVyaW5nIENBMFkwCgYE VQgBAQICAgADSwAwSAJBAL4Od/KxhOB6HyUbBJC2X6Ic2P0XEcGnddzJ1QEHjSFy x5qzn098ScMWDEJSiwrsVmQFbNvN01hkke7ZE21aG5sCAwEAATANBgkqhkiG9w0B AQIFAANBALtOOv3SWxy+/VEvvY6j06wUNQRhqbtX5g8HgOwPgvoqcrRl939lcOcx X7q8YB5bVVTow4PsFfnorV5gsOBwnf4= MIC-Info: RSA-MD5,RSA, h56nvkEFDtshcdYsjigVBoUSym9orbhCcrbTn0zvkkTZ6ejXqPudk7jGA9GwdgO3 Rb6DYPeFf7HgENYg9Em2bQ== Since the value of the treeStructure attribute is very static, wouldn't it be nice if we had it in the oidtable.oc? That way, we define it once and not every time one creates a entry of an object class that needs a treeStructure attribute. I've been thinking about modifying quipu to handle this as an exercise, but would like some opinions before I go ahead. Does anybody have any info regarding this? thanks - ---------------------------------------------------------------- Luis P. Caamano (LC2385) | lpc@sware.com SecureWare, Inc. Atlanta, GA, USA | (404) 315-6296 -----END PRIVACY-ENHANCED MESSAGE-----   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09861; 22 May 95 14:10 EDT Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa09857; 22 May 95 14:10 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa11323; 22 May 95 14:10 EDT X400-Received: by mta haig.cs.ucl.ac.uk in /PRMD=uk.ac/ADMD=gold 400/C=gb/; Relayed; Mon, 22 May 1995 16:33:18 +0100 Date: Mon, 22 May 1995 16:33:18 +0100 X400-Originator: osi-ds-request@cs.ucl.ac.uk X400-Recipients: non-disclosure:; X400-MTS-Identifier: [/PRMD=uk.ac/ADMD=gold 400/C=gb/;haig.cs.uc.646:22.04.95.15.33.18] Priority: Non-Urgent DL-Expansion-History: osi-ds@cs.ucl.ac.uk ; Mon, 22 May 1995 16:33:17 +0100; Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Colin Robbins Message-ID: <"12875 Mon May 22 16:32:48 1995"@nexor.co.uk> To: "Luis P. Caamano" Cc: quipu , OSI-DS , ldap@umich.edu In-Reply-To: <9505221425.AA25319@alehouse.sware.com> Subject: Re: Quipu's treeStructure attribute in oidtables >Since the value of the treeStructure attribute is very static, wouldn't >it be nice if we had it in the oidtable.oc? That way, we define it >once and not every time one creates a entry of an object class that >needs a treeStructure attribute. I've been thinking about modifying >quipu to handle this as an exercise, but would like some opinions >before I go ahead. > >Does anybody have any info regarding this? TreeStructure is an out of date component of QUIPU. If you do any modifications at all you should consider implementing the structure rules as offered by X.500(93). These are stored "out of the way" in sub entries of the DIT, but have the advantage of being available to DUAs over DAP if they need to be accessed for some reason. Colin   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07242; 23 May 95 14:22 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07236; 23 May 95 14:22 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa11799; 23 May 95 14:22 EDT Received: from gatepas.gc.ca by haig.cs.ucl.ac.uk with Internet SMTP id ; Tue, 23 May 1995 15:45:40 +0100 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca Reply-To: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca Errors-To: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@x400.gc.ca Date: Tue, 23 May 1995 10:40:45 -0400 Priority: normal Content-Identifier: Looking for an L X400-Content-Type: P2-1984 X400-MTS-Identifier: [/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/;XGW-950523104045-0400-05075] To: osi-ds@cs.ucl.ac.uk Subject: Looking for an LDAP client Message-Id: <"0523144045-Looking for an LDAP client"*/DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@MHS> Importance: normal We have one running version of an LDAP server on a machine that runs an product. We are now looking for an LDAP client (shareware release) on PC/Windows and/or on X/MOTIF to complete our configuration and to propose a nice user interface. Maybe some of you have judicious advice on that subject. I'll be very happy to get information directly from experts. Thank you for your possible answer, Pascal +----------------------------------------------------------------------+ Pascal Deveze Org. : OSS/OSB/XCOM/A&S Bull S.A. E.Mail : P.Deveze@frec.bull.fr 1, Rue de Provence Phone : + (33) 76 29 78 68 B.P. 208 Fax : + (33) 76 29 77 70 38432 ECHIROLLES CEDEX Bullcom : (229) 78 68 FRANCE P.C. : FREC B1-319 +----------------------------------------------------------------------+ "Save trees and forests, use electronic Mail ...."   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07457; 23 May 95 14:28 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07451; 23 May 95 14:28 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa11868; 23 May 95 14:26 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Tue, 23 May 1995 17:57:13 +0100 Received: from lupine.nsi.nasa.gov by bells.cs.ucl.ac.uk with Internet SMTP id ; Tue, 23 May 1995 17:55:51 +0100 Received: (from mnewell@localhost) by lupine.nsi.nasa.gov (8.6.12/8.6.12) id MAA26964; Tue, 23 May 1995 12:53:45 -0400 Date: Tue, 23 May 1995 12:53:44 -0400 (EDT) Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Michael C. Newell" To: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca cc: osi-ds@cs.ucl.ac.uk Subject: Re: Looking for an LDAP client In-Reply-To: <"0523144045-Looking for an LDAP client"*/DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@MHS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII NASA used to have one available on "naic.nasa.gov" called "wdua". I wrote one a LONG time ago called "piXie", but wdua has since replaced it. Mike On Tue, 23 May 1995 /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca wrote: > Date: Tue, 23 May 1995 10:40:45 -0400 > From: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca > To: osi-ds@cs.ucl.ac.uk > Subject: Looking for an LDAP client > > We have one running version of an LDAP server on a machine that runs an > product. We are now looking for an LDAP client (shareware release) on > PC/Windows > and/or on X/MOTIF to complete our configuration and to propose a nice > user > interface. > > Maybe some of you have judicious advice on that subject. I'll be very > happy to > get information directly from experts. > > > Thank you for your possible answer, > > Pascal > > > > +----------------------------------------------------------------------+ > Pascal Deveze Org. : OSS/OSB/XCOM/A&S > Bull S.A. E.Mail : P.Deveze@frec.bull.fr > 1, Rue de Provence Phone : + (33) 76 29 78 68 > B.P. 208 Fax : + (33) 76 29 77 70 > 38432 ECHIROLLES CEDEX Bullcom : (229) 78 68 > FRANCE P.C. : FREC B1-319 > +----------------------------------------------------------------------+ > > "Save trees and forests, use electronic Mail ...." > Thanks, Mike +--------------------------------------+------------------------------------+ |Mike Newell | The opinions expressed herein are | |NASA Science Internet Network Systems | my own, and do not necessarily | |Sterling Software, Inc. | reflect those of the NSI program, | |MNewell@nsipo.nasa.gov | Sterling Software, NASA, or anyone | |+1-202-434-8954 | else. | +--------------------------------------+------------------------------------+   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07513; 23 May 95 14:30 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07509; 23 May 95 14:30 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa11957; 23 May 95 14:30 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Tue, 23 May 1995 14:40:26 +0100 Received: from gatepas.gc.ca by bells.cs.ucl.ac.uk with Internet SMTP id ; Tue, 23 May 1995 14:40:13 +0100 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca Reply-To: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/@lotus.hc-sc.x400.gc.ca Errors-To: /DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@x400.gc.ca Date: Tue, 23 May 1995 09:40:31 -0400 Priority: normal Content-Identifier: Protocol Action: X400-Content-Type: P2-1984 X400-MTS-Identifier: [/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/;XGW-950523094031-0400-06038] To: gatepas.gc.ca@gatepas PP-Warning: Parse error in original version of preceding line Original-To: ;IETF-Announce:;@gatepas.gc.ca@gatepas Cc: rfc-editor@isi.edu, iab@isi.edu, osi-ds@cs.ucl.ac.uk Subject: Protocol Action: Connection-less Lightweight Directory Access Protocol to Proposed Standard Message-Id: <"0523134031-Protocol Action: Connection-less Lightweight Director"*/DD.NTADDR=Anne_Philpott#l#a#r#HWC/G=Anne/S=Philpott/O=lotus/PRMD=gc+hc.sc/ADMD=govmt.canada/C=ca/@MHS> Importance: normal The IESG has approved the Internet-Draft "Connection-less Lightweight Directory Access Protocol" as a Proposed Standard. This work was initiated in the [now defunct] OSI Directory Services Working Group and completed by the Access and Synchronization of the Internet Directories Working Group. The IESG contact person is Harald Tveit Alvestrand. Technical Summary The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP) as specified in X.500. In particular, it is aimed at avoiding the elapsed time that is associated with connection-oriented communication and it facilitates use of the Directory in a manner analagous to the DNS. It is specifically targeted at simple lookup applications that require to read a small number of attribute values from a single entry. It is intended to be a complement to DAP and LDAP (RFC 1487). The protocol specification draws heavily on that of LDAP (RFC 1487) that has proven to be the most widely used and implemented access protocol for X.500 to date. Advice on how to implement a retransmission strategy was added after the previous IESG review. Working Group Summary Most of the debate on CLDAP focused on improvements to LDAP. There was a clear concensus on the connectionless approach. Protocol Quality The specification has been reviewed by a member of the Applications Area Directorate and by one of the Area Directors.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00729; 26 May 95 5:05 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00725; 26 May 95 5:05 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa01687; 26 May 95 5:00 EDT X400-Received: by mta haig.cs.ucl.ac.uk in /PRMD=uk.ac/ADMD=gold 400/C=gb/; Relayed; Fri, 26 May 1995 08:22:51 +0100 Date: Fri, 26 May 1995 08:22:51 +0100 X400-Originator: osi-ds-request@cs.ucl.ac.uk X400-Recipients: non-disclosure:; X400-MTS-Identifier: [/PRMD=uk.ac/ADMD=gold 400/C=gb/;haig.cs.uc.977:26.04.95.07.22.51] Priority: Non-Urgent DL-Expansion-History: osi-ds@cs.ucl.ac.uk ; Fri, 26 May 1995 08:22:51 +0100; Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Alan Shepherd Message-ID: <24203.801472930@nexor.co.uk> To: panamas@paradise.ulcc.ac.uk, osi-ds@cs.ucl.ac.uk Subject: Root level prodir combined results Reply-To: prodir-support@nexor.co.uk *** N.B. The probing results below are influenced by network failures *** *See also: the WWW entry, "http://web.nexor.co.uk/users/quipu/x500/graphroot.gif" Probing from SURFnet@Delft, SWITCH@Zurich, NEXOR, ULCC, Cambridge Computer Lab, Community: internet ========== ======== The following DSAs were available 100% of the time: cn=Proteus Other DSAs: ----- ----- %Avail Organisation,DSA Attempts Average Time ------ ---------------- -------- ------------ 99.37 ULCC, Giant Tortoise 635 1.60 3 Timed out after 60 seconds 1 Connection refused 99.37 SURFnet, Hornero 635 0.72 2 Timed out after 60 seconds 1 Unavailable 1 Connection refused 99.36 Vrije Universiteit Brussel, Woolly Spider... 467 4.90 1 Connection refused 1 Timed out after 60 seconds 99.06 SWITCH, Condor 635 1.06 6 Timed out after 60 seconds 98.90 UNINETT, Electric Eel 635 2.03 1 Host is unreachable 4 Timed out after 60 seconds 1 Connection refused 1 Unavailable 98.76 Unknown Organisation, opaxdsa, CNRS, FR 161 1.23 2 Timed out after 60 seconds 98.74 Inmarsat, Hedgehog 635 4.38 7 Timed out after 60 seconds 1 Invalid credentials 98.43 UNINETT, Boa Constrictor 635 2.46 8 Connection refused 2 Timed out after 60 seconds 98.11 Universitaet Wien, Rockhopper Pe... 635 3.58 4 Timed out after 60 seconds 7 Invalid credentials 1 Connection refused 98.11 Matej Bel University, UA..., Tarpon 635 5.40 1 Unavailable 10 Timed out after 60 seconds 1 Host is unreachable 97.80 Unknown Organisation, opaxdsa, CNRS, FR 635 2.47 2 Connection refused 10 Timed out after 60 seconds 1 Host is unreachable 1 Unavailable 97.80 North Atlantic Treaty Or..., Violaceous Trogon 635 1.88 13 Timed out after 60 seconds 1 Invalid credentials 97.64 Technische Universitaet ..., Puma 635 1.57 11 Connection refused 4 Timed out after 60 seconds 97.32 UNI-C, Armadillo 635 2.01 8 Host is unreachable 9 Timed out after 60 seconds 97.17 ULCC, Ocellated Turkey 635 0.89 8 Connection refused 10 Timed out after 60 seconds 96.85 Universidad Politecnica ..., Cayman 635 2.62 4 Host is unreachable 12 Timed out after 60 seconds 2 Invalid credentials 1 Connection refused 1 Unavailable 96.85 ULCC, Inca Dove 635 0.96 4 Connection refused 16 Timed out after 60 seconds 96.70 Prague University of Eco..., woolly opossum 636 4.34 16 Timed out after 60 seconds 4 Host is unreachable 95.91 RCCN Portugal, Zebu 635 10.73 1 Connection refused 23 Timed out after 60 seconds 95.59 DFN, Margay 635 3.96 3 Timed out after 60 seconds 1 Connection refused 24 Invalid credentials 95.28 SUNET, Andean Cat 635 1.48 2 Connection refused 7 Timed out after 60 seconds 21 Invalid credentials 95.28 SUNET, Hummingbird 635 1.07 1 Timed out after 60 seconds 27 Invalid credentials 2 Connection refused 95.28 WIDE project, Sloth 635 5.66 26 Timed out after 60 seconds 2 Unavailable 92.76 Victoria University of W..., Kakapo 635 4.12 17 Host is unreachable 3 Connection refused 18 Timed out after 60 seconds 7 Invalid credentials 1 Unavailable 92.45 UMK, Ocelot 636 12.28 41 Timed out after 60 seconds 5 Host is unreachable 1 Connection refused 92.28 Restena, Guppy 635 6.20 15 Timed out after 60 seconds 33 Invalid credentials 1 Host is unreachable 92.13 GARR-NIS, Black Widow 635 3.40 39 Timed out after 60 seconds 9 Connection refused 2 Invalid credentials 91.97 Unknown Organisation, Corncrake 635 3.17 27 Timed out after 60 seconds 2 Unavailable 22 Invalid credentials 91.02 DKUUG, Axolotl 635 8.19 30 Timed out after 60 seconds 9 Connection refused 5 Unavailable 13 Invalid credentials 90.87 U.S. DMD, Fruit Bat 635 4.56 43 Timed out after 60 seconds 14 Connection refused 1 Host is unreachable 88.35 U.S. DMD, Pied Tamarin 635 6.46 50 Timed out after 60 seconds 21 Invalid credentials 2 Connection refused 1 Unavailable 87.72 GARR-NIS, Black Widow 635 4.94 67 Timed out after 60 seconds 9 Connection refused 2 Invalid credentials 86.25 FUNET, Jaguar 640 1.54 79 Connection refused 7 Timed out after 60 seconds 1 Host is unreachable 85.98 Australian Academic and ..., Bush Dog 635 8.37 71 Timed out after 60 seconds 7 Unavailable 1 Host is unreachable 10 Connection refused 85.98 National Computer Board ..., Lion 635 9.79 82 Timed out after 60 seconds 4 Host is unreachable 3 Connection refused 83.78 SURIS, Elephant Seal 635 4.82 22 Invalid credentials 64 Connection refused 5 Host is unreachable 12 Timed out after 60 seconds 83.23 Brussels University, Red Titi Monkey 638 26.55 89 Timed out after 60 seconds 8 Connection refused 1 Unavailable *** (sent srcref of 0x228, got 0x0 (Mismatched references at transport) 6 Unavailable 80.91 U.S. DMD, alpaca 639 4.06 89 Connection refused 17 Timed out after 60 seconds 80.50 Australian Academic and ..., Anaconda 636 7.61 43 Timed out after 60 seconds 1 Host is unreachable 2 Unavailable 72 Invalid credentials 3 Connection refused 80.03 NSTN Inc, beluga whale 636 8.95 85 Timed out after 60 seconds 20 Connection refused 16 Host is unreachable 1 Unavailable 75.75 FUNET, Northern Pudu 635 2.54 30 Timed out after 60 seconds 123 Connection refused 1 Invalid credentials 73.54 Swiss Telecom PTT, TellXdir 635 0.87 168 Invalid credentials 66.77 RedIRIS, iguana 635 2.60 197 Connection refused 11 Timed out after 60 seconds 3 Host is unreachable 66.25 Foundation Of Research a..., Caretta Caretta 637 9.04 17 Timed out after 60 seconds 183 Connection refused 11 Invalid credentials 1 Unavailable 1 Host is unreachable 61.89 Unknown Organisation, Dorcan Gazelle 635 9.76 222 Timed out after 60 seconds 13 Host is unreachable 5 Unavailable 2 Connection refused 47.40 SWITCH, Chinchilla 635 0.57 8 Connection refused 325 Invalid credentials 1 Timed out after 60 seconds 45.78 Trinity College Dublin, Irish Elk 640 6.86 340 Connection refused 1 Unavailable 1 Invalid credentials 5 Timed out after 60 seconds 20.31 IIT Delhi, IN, Pelican 640 22.45 187 Host is unreachable 108 Timed out after 60 seconds 4 Connection refused 1 Unavailable 8.19 University of Zagreb - F..., Roufous Motmot 635 27.25 525 Connection refused 55 Timed out after 60 seconds 2 Host is unreachable 1 Unavailable 7.87 Moscow State University, Bear 635 3.92 249 Timed out after 60 seconds 336 Connection refused 0.00 Master DSA of KOREA, Darter 635 0.00 630 Timed out after 60 seconds 5 Host is unreachable 0.00 Computer and Automation ..., Guinea Pig 635 0.00 632 Connection refused 3 Timed out after 60 seconds 0.00 Unknown Organisation, Long Moustach... 635 0.00 21 Timed out after 60 seconds 613 Connection refused 1 Host is unreachable 0.00 Universidade Federal do ..., paca 635 0.00 602 Connection refused 31 Timed out after 60 seconds 2 Host is unreachable 0.00 Tallinn Technical University, saki 635 0.00 470 Connection refused 140 Timed out after 60 seconds   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03657; 28 May 95 18:43 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03653; 28 May 95 18:43 EDT Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa11334; 28 May 95 18:43 EDT Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id ; Sun, 28 May 1995 22:57:04 +0100 Received: from cdsmail.cdc.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Sun, 28 May 1995 22:56:51 +0100 Received: from slipcgj.arh.cdc.com by cdsmail.cdc.com; Sun, 28 May 95 16:56:38 -0500 Date: Sun, 28 May 95 21:56:29 0400 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Gordon Jenkins X-Mailer: Mozilla 1.1b3 (Macintosh; I; 68K) MIME-Version: 1.0 To: osi-ds@cs.ucl.ac.uk Subject: subscribe X-URL: http://web.nexor.co.uk/users/quipu/x500/x500.html Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=iso-8859-1 Message-Id: <2fc8f197575b002@cdsmail.cdc.com> subscribe