- techsec-wg - mailman.ripe.net

ANNOUNCEMENT: RIPE NCC DNSSEC Course, introduction to the concept and current state
by Henk Uijterwaal (RIPE-NCC) 27 Jun '02

27 Jun '02

* * * Announcement * * * DNSSEC, introduction to the concept and current state Date: Saturday 14 September 2002 Time: 0900 - 1700 Location: Rhodos, Greece AND Date: Tuesday 22 October 2002 Time: 0900 - 1700 Location: Sarajevo, Bosnia AND Date: Thursday 28 November 2002 Time: 0900 - 1700 Location: Paris, France AND Date: Thursday 12 December 2002 Time: 0900 - 1700 Location: Amsterdam, The Netherlands The Domain Name System (DNS) is one of the main parts of the Internet Infrastructure. DNS is trusted by the end-users to is trusted by many end-users to give correct results. At the moment, however, DNS lacks a mechanism to establish the authenticity and integrity of the data it provides. DNSSEC is a set of extensions to provide end-to-end authenticity and integrity. This introduction will cover. - DNS security threads; - DNSSEC security mechanisms; + DNSSEC server protection; + DNSSEC data protection; - Delegation issues; - Key management issues; - Current developments; The DNSSEC introduction is intended for those who are familiar with common DNS terminology and are interested in learning about the concepts and mechanisms that DNSSEC offers. Our goal is to provide participants with sufficient background to be able to deploy DNSSEC in their own organization. Examples are based on the BIND name server. More information about the details of the DNSSEC Introduction can be found at: http://www.ripe.net/disi/ Kind regards, Sandra Gijzen RIPE NCC Training Co-Ordinator REGISTRATION ============ To register for these Courses, please complete the registration form below and reply to <training(a)ripe.net>. Please send only the registration form in your reply and edit out all other text. Add a value in the `box' area marked between the square brackets (i.e. "[" and "]" ). Alternatively, you can use the Training Course Request Form at: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions about the DNSSEC Introduction, your registration form or the web page, please contact us at <training(a)ripe.net>. --------------------------- %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The Course you plan to attend (date and location) # COURSE [ ] %END

1 0

Agenda, TechSec at RIPE42
by ted＠tednet.nl 16 Apr '02

16 Apr '02

Agenda for TechSec at RIPE 42 1st slot: 0. Administrativia 1. Minutes of previous meeting (Rene Wilhelm <wilhelm(a)ripe.net>) 2. DISI status update (20-30 minutes, Olaf(a)ripe.net) 3. NLnet Labs reports on securing .nl (20-30 minutes, miekg(a)nlnetlabs.nl) 4. TF-CSIRT update, news about IODEF development, EU projects and Training for the new CSIRTs. (15-20 minutes, Yuri Demchenko <demch(a)terena.nl>) 5. IRT object in the RIPE Database: current status (10-15 minutes, Andrei Robachevsky <andrei(a)ripe.net>) 2nd slot 6. Hugh Daniel reports on FreeS/WAN and issues around authentication/privacy and user perceptions. (10 min. introduction, then open discussion) 7. A.O.B. See you at RIPE42, -- ted

1 0

Proposed agenda, TechSec at RIPE42
by ted＠tednet.nl 11 Apr '02

11 Apr '02

Proposed agenda for TechSec at RIPE 42 1st slot: 0. Administrativia 1. Minutes of previous meeting (Rene Wilhelm <wilhelm(a)ripe.net>) 2. DISI status update (20-30 minutes, by Olaf(a)ripe.net) 3. NLnet Labs reports on securing .nl (20-30 minutes, by miekg(a)nlnetlabs.nl) 2nd slot 4. Hugh Daniel reports on FreeS/WAN and issues around authentication/privacy and user perceptions. (10 min. introduction, then open discussion) 5. A.O.B. Please note that in both the first and second slot we have some time left for additional reports and other talks, but if you want it in the official (printed) agenda, now is the time to come forward. Regards, -- ted

2 1

Request for agenda items for TechSec WG at RIPE42
by ted＠tednet.nl 04 Apr '02

04 Apr '02

Sofar I have 2 items besides the usual administrativa, minutes, and AOB: - DISI status update (Olaf Kolkman/RIPE NCC) - DNSSEC at .nl testbed (Miek Gieben, NLnet Labs) More items are very welcome, regards, -- ted

1 0

Draft minutes of RIPE41 techsec-wg
by Rene Wilhelm 31 Jan '02

31 Jan '02

Dear all, Here are the minutes of the TechSec WG session at RIPE41. If you have any comments/corrections send them to me, I'll add them to the document. Kind regards, -- Rene Minutes of Techsec-WG meeting at RIPE41 (version 0.2) ======================================================= Chair: Ted Lindgreen Scribe: Rene Wilhelm Date: 16-Jan-2002, 14:00 Agenda ------ A. Administrativia B. Minutes of previous meeting C. DISI status update (Olaf Kolkman/RIPE NCC). D. CSIRT update (Yuri Demschenko/Terena). E. IRT object (Andrei Robachevsky/RIPE NCC) F. AOB ---------------------------------- A. Administrativia Rene Wilhelm volunteered as scribe B. Minutes of previous meeting Minutes of techsec-wg meeting at RIPE40 were approved C. DISI Status update (Olaf Kolkman/RIPE NCC) [slides at http://www.ripe.net/ripe/meetings/archive/ripe-41/presentations/disi-progre… ] Olaf starts with explaining what the DISI (Deployment of Internet Security Infrastructures) project is all about. Though the first activity focusses on DNSSSEC, the project is broader and expected to take on other activities as needed. DNSSEC status: o Deployment problems, Delegation of authority and Signing of large zones o IETF solutions: DS (delegation signer) Resource Record and OPT-IN DS records are published and signed by the parent and will reduce the number of key exchange interactions. OPT-IN optionally excludes parts of the zone from signing; will reduce the final size of the zone, which is important for deployement in e.g. .com zone. Price paid is a loss of authenticated denial in parts of the zone on which opt-in is deployed. DS and OPT-IN documents will go to last call in Februari 2002. There is broad consensus about DS, the document will likely be advanced. There is no consensus yet about OPT-IN, but there is a compromise (from Olaf Kolkman), with which consensus may be reached. Updated version of RFC2535 document will go to last call in March. Deployement of DNSSEC on reverse tree is expected in last quarter of 2002 DNSSEC courses and tutorials: o Full day course material finalizing The two workshops held in 2001 provided useful feedback o 4 day DNS/DNSSEC course at APRICOT planned half-a-day DNSSEC tutorial at APNIC meeting and SANE o Waiting for protocol developments before organising more courses o Budget for +/- 10 courses, schedule expected in March 2002 Other DISI work: o Host lab/workshop on DNS secure dynamic update and DCHP roaming (next week) o Name Server Daemon Problem with authoritative servers realized: lack of code diversity! (vast majority of servers run BIND) Study in collaboration with NLnet Labs led to Name Server Daemon; robust, high performing, open source software targeted at authoritative servers. Details and annoucement in tomorrow's DNS-WG session. QUESTIONS? None. D. TF-CSIRT update (Yuri Demchenko, Terena) [ slides at http://www.ripe.net/ripe/meetings/archive/ripe-41/presentations/techsec-tf-… ] Yuri presented an update of Terena's activity of CSIRT coordination for Europe No TF-CSIRT meetings were held after previous presentation in RIPE40 (next one scheduled for Jan24-25 in Stockholm), but some new developments are reported: TF-CSIRT and relations with European Commission: Lobbying CSIRT interests is seen as an important function of TF-CSIRT. New initiative supported by EC: EWIS - Early Warning and Information System was discussed and criticized at last TF-CSIRT meeting Trusted Introducer: purpose: build a web of trust for the CSIRT community via two intermediate steps ('known team' and 'candidate team') a new team can be introduced to the Level2 of maintainable trust. procedure is working, currently 19 teams at level2, 1 at level1. contract with TERENA has been renewed for one more year; better PR/promotion needed Training new CSIRT staff members: First CSIRT training course to be held immediately before the next TF-CSIRT meeting. Covers legal, organisational, technical, market and operational issues. Incident Object Description and Exchange Format WG: Webpage and charter http://www.terena.nl/task-forces/tf-csirt/iodef/ mail archive http://hypermail.terena.nl/iodef-list/mail-archive/ o Requirements document published as RFC 3067 - http://www.ietf.org/rfc/rfc3067.txt o Held INCident Handling (INCH) BOF session at IETF52 draft minutes at http://www.terena.nl/tech/inch/inch-bof-ietf52-minutes-draft.txt proposed charter http://www.terena.nl/tech/inch/inch-wg-charter-draft.html o Creation of INCH WG was agreed with IETF Security Area. Scope: - Define data formats for communication between CSIRT and parties involved in an incident investigation - Information model needed to support the typical, operational workflow of the incident handling processes Clearinghouse of Incident Handling Tools (CHIHT): Goals: o Creating repository of popular tools used by CSIRTs to collect incident data/evidence; investigate and track incidents o Ease setting up work procedure for new CSIRT teams Further work will be conducted by CHIHT WG Kick-off meeting at next TF-CSIRT meeting on January 24, 2002 in Stockholm QUESTIONS Q. trusted introducer, how does it work in practice for a new team to join? A. This is described on the website [ http://www.ti.terena.nl/howto.html and http://www.ti.terena.nl/process.html ] New team first needs to be recognized as a known (level0) team by filling in a form, specifying contact details and such. Once added to the list, can apply for level2. When application is approved, automatically upgraded to level1. Next, during a two month period, team will be checked, monitored and might be visited; if fine, added to the trust level2. Note: commercial ISPs will have to pay a fee. E. IRT object (Andrei Robachevsky/RIPE NCC) [ slides at http://www.ripe.net/ripe/meetings/archive/ripe-41/presentations/database-ir… ] Andrei presented an update on the status of IRT objects in the RIPE database. The idea is to provide an easy way to find contact information of a CSIRT and a means of linking it to registered IP address space (inetnum objects). Object definition is finished. support for new '-c' query has been added to the database code. Currently available for public review (beta test) at test-whois.ripe.net, updates to test-dbm(a)ripe.net. Open issues (for production db): o IRT objects will be inserted manually by RIPE NCC database operator, need an authentication procedure o Adding a reference from a inetnum object is secure, removing a reference is different o Need a RIPE document with detailed description, best current practice and procedures QUESTIONS Q. Do you have any idea how authentication would be done? can it work with the trusted introducer? A. Andrei: we haven't disucssed this yet. Yuri: it is a topic for next week's meeting F. AOB No other business, meeting closed at 15:00 =============================================================================

1 0

IETF52 INCH BoF: minutes, mailing list and Draft INCH WG Charter
by Yuri Demchenko 22 Jan '02

22 Jan '02

Dear TECHSEC WG members, This is to inform you about the successful INCH BoF at IETF52 and invite you to the inch mailing list: Post: inch(a)nic.surfnet.nl Archive: http://listserv.surfnet.nl/archives/inch.html How to join the list: http://listserv.surfnet.nl/scripts/wa.exe?SUBED1=inch&A=1 INCH BOF information page http://www.terena.nl/tech/inch/ Direct pointers to Draft minutes and Draft INCH WG Charter http://listserv.surfnet.nl/scripts/wa.exe?A2=ind01&L=inch&F=&S=&P=142 http://listserv.surfnet.nl/scripts/wa.exe?A2=ind02&L=inch&F=&S=&P=44 Please send your comments and suggestions how to shape the future INCH WG activity to the inch mailing list. Please note that the last call for the Charter discussion has been set up January 23, 2001. Regards, Yuri -- ----------------------------------------------------------------------- Yuri Demchenko, TERENA, Singel 468D, 1017 AW Amsterdam, The Netherlands Tel: +31 20 530 4488 Fax: +31 20 530 4499 E-mail: demchenko(a)terena.nl -----------------------------------------------------------------------

1 0

techsec @ripe40 minutes (fwd)
by Henk Uijterwaal (RIPE-NCC) 12 Jan '02

12 Jan '02

Dear all, This somehow slipped through the cracks, sorry about that. Henk Minutes of the TechSec working group meeting at RIPE40 ====================================================== Chair: Henk Uijterwaal Scribe: Rene Wilhelm Agenda 1. Administrativia 2. Discussion of charter for the group 3. DISI project, status and plans 4. TF-CSIRT update 5. Discussion of workplan for the group 5. AOB -------------- 1. Administrativia Minutes of the BoF session at Bologna RIPE meeting are approved. 2. Discussion of Charter and workplan for the group, Henk Uijterwaal Henk presented the results of the discussion that took place on the mailing list. As there are no further coments, the charter is accepted and will be posted on the web. slides: http://www.ripe.net/ripencc/pub-services/np/DISI/Talks/0110_techsec/index.h… 3. DISI project status and plans, Olaf Kolkman. Olaf gave an update of the status and plans of the DISI project. slides: http://www.ripe.net/ripe/meetings/archive/ripe-40/presentations/RIPE40-disi… Discussion: Q. Organizing a DNSSEC workshop in conjunction with the RIPE meeting was discussed in Bologna and is a good idea, but having the workshop the monday after the meeting poses difficulties: would mean longer time away from the office, thus cannot attend. Strongly suggest to next time organize the workshop during the RIPE meeting week. A. We will consider it, was not possible this time due to room availability. Q. How much lead time do you need to organize a workshop? A. Since the material is there, about two days plus the time it takes to arrange a plane ticket and a place to stay. However, for the workshop to be successfull will have to prepare and plan for attending, thus realistic lead time is about four weeks. Q. Will there be a workshop at the january 2002 RIPE meeting in Amsterdam? A. That depends on what happens with DNSSEC in the IETF, if there's enough interest we can do this. 3. TF-CSIRT Update, Yuri Demchenko Yuri presented an overview of Terena's TF-CSIRT activities on coordinating CSIRT activity in Europe. slides: http://www.ripe.net/ripencc/pub-services/np/DISI/Talks/0110_yuri/index.html 4. Discussion on workplan for the group What are appropriate topics for the techsec working group to discuss? Henk identified as regular items update reports from the RIPE NCC's DISI project and Terena's TF_CSIRT working group. Other items? Yuri: TF-CSIRT chair and TechSec chair should get together to discuss areas of common intereset and activity; more coordination. 5. External Chair Since RIPE NCC will be regularly reporting DISI progress to the techsec working group, Henk feels it is not appropriate for him to chair the group. He therefore asks for an external person to take over. Ted Lindgreen volunteers and is accepted as new chair. 6. A.O.B. no other business, the meeting is closed. ======================================================

1 0

Non-member submission from [Andrei Robachevsky <andrei@ripe.net>]
by Henk Uijterwaal (RIPE-NCC) 12 Jan '02

12 Jan '02

---------- Forwarded message ---------- Date: 11 Jan 2002 17:54:41 -0000 From: owner-techsec-wg(a)ripe.net To: techsec-wg-approval(a)ripe.net Subject: BOUNCE techsec-wg(a)ripe.net: Non-member submission from [Andrei Robachevsky <andrei(a)ripe.net>] Received: (qmail 24565 invoked by uid 0); 11 Jan 2002 17:54:40 -0000 Received: from birch.ripe.net (193.0.1.96) by postman.ripe.net with SMTP; 11 Jan 2002 17:54:40 -0000 Received: from ripe.net (x43.ripe.net [193.0.1.43]) by birch.ripe.net (8.11.6/8.11.6) with ESMTP id g0BHsei28208; Fri, 11 Jan 2002 18:54:40 +0100 Message-ID: <3C3F26E0.4050204(a)ripe.net> Date: Fri, 11 Jan 2002 18:54:40 +0100 From: Andrei Robachevsky <andrei(a)ripe.net> Organization: RIPE NCC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: db-wg(a)ripe.net, techsec-wg(a)ripe.net Subject: IRT object Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dear Colleagues, The irt object has been implemented and we put the new software on our test whois server (please see http://www.ripe.net/ripencc/pub-services/db/testdb.html) We also took liberty to make some modifications to the original proposal (http://www.ripe.net/ripe/mail-archives/db-wg/20010701-20020101/msg00036.html) Namely: - an "irt-nfy:" attribute is now optional/multiple/inevrse key in the irt object. It specifies an e-mail address used to send notifications whenever a reference to the object is added or removed. We thought it would be very useful from security prospective. - a name of an irt object should start with "IRT-" prefix reserved for this type of object. This will eliminate possible confusion, such as mixing up with mntner. We have created some object to play with: irt: IRT-TEST inetnum: 172.18.0.0 - 172.25.255.255 So you may try: $ whois -h test-whois IRT-TEST $ whois -h test-whois -i mnt-irt IRT-TEST $ whois -h test-whois -i irt-nfy bitbucket(a)ripe.net $ whois -h test-whois 172.18.10.1 $ whois -h test-whois -c 172.18.10.1 The irt objects are not created automatically, but are forwarded to RIPE Database Administration (ripe-dbm(a)ripe.net) But this restriction does not apply to the TEST database, so you may try to create one yourself. Have a nice weekend, Regards, Andrei Robachevsky DB Group Manager RIPE NCC

1 0

Non-member submission from [Philippe Bourcier <philippe@cyberabuse.org>] (fwd)
by Henk Uijterwaal (RIPE-NCC) 08 Jan '02

08 Jan '02

------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(a)ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk Singel 258 Phone: +31.20.5354414 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ That problem that we weren't having yesterday, is it better? (Big ISP NOC) ---------- Forwarded message ---------- Date: 7 Jan 2002 22:02:47 -0000 From: owner-techsec-wg(a)ripe.net To: techsec-wg-approval(a)ripe.net Subject: BOUNCE techsec-wg(a)ripe.net: Non-member submission from [Philippe Bourcier <philippe(a)cyberabuse.org>] Received: (qmail 22109 invoked by uid 0); 7 Jan 2002 22:02:47 -0000 Received: from birch.ripe.net (193.0.1.96) by postman.ripe.net with SMTP; 7 Jan 2002 22:02:47 -0000 Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g07M2kl12212 for <techsec-wg(a)ripe.net>; Mon, 7 Jan 2002 23:02:46 +0100 Received: (qmail 22098 invoked by uid 0); 7 Jan 2002 22:02:46 -0000 Received: from lafontaine.noos.net (HELO smtp.noos.fr) (212.198.2.72) by postman.ripe.net with SMTP; 7 Jan 2002 22:02:46 -0000 Received: (qmail 138538585 invoked by uid 0); 7 Jan 2002 22:02:45 -0000 Received: from unknown (HELO psy.cyberabuse.org) ([195.132.136.27]) (envelope-sender <philippe(a)cyberabuse.org>) by 212.198.2.72 (qmail-ldap-1.03) with SMTP for <gabriella.paolini(a)garr.it>; 7 Jan 2002 22:02:45 -0000 Message-Id: <5.1.0.14.2.20020107222534.027724c8(a)ns0.ovh.net> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 07 Jan 2002 23:04:07 +0100 To: gabriella.paolini(a)garr.it From: Philippe Bourcier <philippe(a)cyberabuse.org> Subject: Re: Status of IRT object Cc: techsec-wg(a)ripe.net, db-wg(a)ripe.net, lir-wg(a)ripe.net, enzo.valente(a)garr.it In-Reply-To: <3C3A0794.7F8F97F6(a)surfnet.nl> References: <Pine.OSF.4.40.0201071757070.8825-100000(a)dxgarr.dir.garr.it> <p05100305b85f8b712c40(a)[193.0.1.185]> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Re, > > if nothing unexpected happens, you will be able to look at irt > > objects in the RIPE DB this week. > >As a member of another CERT team, I'd like to say I am very pleased with >this :). As the coder of the CyberAbuse whois and a heavy user of all the whois db's I'm happy to hear things finally goes in the right direction. Note that the CyberAbuse whois does check remarks/descr/trouble fields for emails starting with abuse@/csirt@/security@. I had removed cert@ since it seemed not to be used. Though, since the CyberAbuse whois abuse contacts are in most cases netadmin's emails (coordinators/admin-c) I provide a way for admins to modify the Abuse contact field. If you go to http://www.cyberabuse.org/whois/?page=change, then you can have enzo.valente(a)infn.it become cert(a)garr.it. Though this won't be needed since I re-added cert@ in the list of mails to catch. Note that there is a web version of the CyberAbuse whois at http://www.cyberabuse.org/whois/?page=whois , it's a bit more powerfull (reverse AS checking and host lookup). There is also a "light" version at whois.light.cyberabuse.org, for the anti-spam community which runs batch against it to contact administrators of open relays. Sincerely, Philippe Bourcier

1 0

BOUNCE techsec-wg@ripe.net: Non-member submission from [Joao Luis Silva Damas <joao@ripe.net>] (fwd)
by Henk Uijterwaal (RIPE-NCC) 07 Jan '02

07 Jan '02

---------- Forwarded message ---------- Date: 7 Jan 2002 17:30:13 -0000 From: owner-techsec-wg(a)ripe.net To: techsec-wg-approval(a)ripe.net Subject: BOUNCE techsec-wg(a)ripe.net: Non-member submission from [Joao Luis Silva Damas <joao(a)ripe.net>] Received: (qmail 31029 invoked by uid 0); 7 Jan 2002 17:30:12 -0000 Received: from birch.ripe.net (193.0.1.96) by postman.ripe.net with SMTP; 7 Jan 2002 17:30:12 -0000 Received: from [193.0.1.185] (dhcp185.ripe.net [193.0.1.185]) by birch.ripe.net (8.11.6/8.11.6) with ESMTP id g07HU3l01871; Mon, 7 Jan 2002 18:30:03 +0100 Mime-Version: 1.0 X-Sender: joao(a)birch.ripe.net Message-Id: <p05100305b85f8b712c40(a)[193.0.1.185]> In-Reply-To: <Pine.OSF.4.40.0201071757070.8825-100000(a)dxgarr.dir.garr.it> References: <Pine.OSF.4.40.0201071757070.8825-100000(a)dxgarr.dir.garr.it> Date: Mon, 7 Jan 2002 18:30:01 +0100 To: Gabriella Paolini <gabriella.paolini(a)garr.it>, techsec-wg(a)ripe.net, <db-wg(a)ripe.net>, <lir-wg(a)ripe.net> From: Joao Luis Silva Damas <joao(a)ripe.net> Subject: Re: Status of IRT object Cc: info(a)cyberabuse.org, <philippe(a)cyberabuse.org>, <enzo.valente(a)garr.it> Content-Type: text/plain; charset="us-ascii" ; format="flowed" Dear gabriella, if nothing unexpected happens, you will be able to look at irt objects in the RIPE DB this week. Joao At 18:26 +0100 7/1/02, Gabriella Paolini wrote: >Dear all, >which is the status of IRT object? >Is the trial implementation available? >This example shows again the need for a specific object. >If someone uses whois information from cyberabuse.org, as many times >people does, that information is wrong, because ciberabuse guys used >Admin-c email without considering all other informations in inetnum >object and in role object. > >Thanks and regards, >Gabriella Paolini >INFN-GARR > >[ Informations about 193.204.17.211 ] > >IP range : 193.204.16.0 - 193.204.23.255 >Network name : UNIBAS-NET >AS number : AS137 >Infos : Universita' Degli Studi Di Basilicata >Infos : Centro Interfacolta' Servizi Informatici E Telematici - Cisit >Phone number : +39 06 49914352 >Country : IT >Abuse contact : enzo.valente(a)infn.it >Source : RIPE > >right information are > >inetnum: 193.204.16.0 - 193.204.23.255 >netname: UNIBAS-NET >descr: Universita' degli Studi di Basilicata >descr: Centro Interfacolta' Servizi Informatici e Telematici - >CISIT >country: IT >admin-c: EV182-RIPE >tech-c: GL965-RIPE >tech-c: GM976-RIPE >... >remarks: To notify abuse mailto: cert(a)garr.it >remarks: Multiple lan of university departments >remarks: GARR - Italian academic and research network >mnt-by: GARR-LIR >... > >role: GARR LIR >... >trouble: To notify abuse mailto: cert(a)garr.it >trouble: Information at http://www.lir.garr.it/ >... > >person: Enzo Valente >address: INFN - Dipartimento di Fisica >address: Universita' La Sapienza >address: Piazzale Aldo Moro,2 >address: I-00185 Roma >address: Italy >phone: +39 06 49914352 >fax-no: +39 06 4957697 >e-mail: Enzo.Valente(a)infn.it >... --

1 0