July 2002 - lir-wg - mailman.ripe.net

Draft document "New Values of the 'status:' attribute for inet6num Objects" is available
by Andrei Robachevsky 23 Jul '02

23 Jul '02

Dear Colleagues, [apologies for duplicate messages] The draft document "New Values of the 'status:' attribute for inet6num Objects" is available on the RIPE NCC website at: http://www.ripe.net/ripencc/draft-documents/ This document describes the new values of the "status:" attribute for inet6num objects and their impact on database operation. The deadline for comments and suggestions is Wednesday, 24th July. After incorporating any suggested changes to the document the final document will be published as a RIPE Document. On Thursday, 25th July, subject to any additional comments, the described Database functionality will be put in to practice. Please send your comments and suggestions to <lir-wg(a)ripe.net>. Regards, Andrei Robachevsky RIPE NCC

2 2

New address announcement
by RIPE NCC Staff 19 Jul '02

19 Jul '02

Dear Colleagues, The RIPE NCC has a new postal address. The new address is: RIPE NCC P.O. Box 10096 1001 EB AMSTERDAM THE NETHERLANDS The new address should be used for all postal contacts. Please update your records to reflect this change. Kind Regards, The RIPE NCC

1 0

Re: [lir-wg] rfc-ignorant.org
by Wilfried Woeber, UniVie/ACOnet 19 Jul '02

19 Jul '02

>Oh, yes, I have no illusions about whether this will actually be a >universal solution to any problem other than as a means to get the >rfc-ignorant.org folks off our collective backs. People unwilling to >provide a usable e-mail address will just fill in a non-usable >(/dev/null'ed?) e-mail address. It's not going to get anybody anywhere, unless we go to the extreme of a 3-way verification as a precondition to holdership of resources registered in the DB, and a recurring verification procedure. If you force a "usable address" you might as well end up with an anon mailer at yahoo, hotmail, gmx,... And if you block those, then nobody prevents me from simply picking an address which is contained in a different, randomly chosen, object. Pretty cheap DoS mechanism, in the end ;-) And last but not least, with the procedures in place for many (most?) ISPs these days, and the channnel-hopping behaviour of users/sites in the domain name space, there is no basis any longer for consistency *and actually getting a human being look at the message*. If rfc-ignorant.org folks don't understand that, then we should suggest a default entry being put in by the DB software (how about postmaster(a)rfc-ignorant.org ?). A maybe more heplful question would be: what do they want to achieve, and is there reasonable merit in those goals to have the community find a sound mechanism for implementation? Wilfried.

1 0

New Document available: RIPE-254
by RIPE NCC Document Announcement Service 19 Jul '02

19 Jul '02

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. "IRT Object in the RIPE Database" (ripe-254) Short content description ------------------------- This document describes the irt object and related functionality in the RIPE Database. The irt object is used to provide information about a Computer Security Incident Response Team (CSIRT). This document also describes the creation procedure for the irt object. Accessing the RIPE document store --------------------------------- The document is on-line at the following URL: http://www.ripe.net/ripe/docs/irt-object.html The RIPE document store is available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-254.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-254.txt plain text version Kind Regards, RIPE NCC Document Announcement Service

1 0

RE: [lir-wg] rfc-ignorant.org
by Pieterjan d'Hertog 18 Jul '02

18 Jul '02

What about RFC954 dating from 1985... <snip> WHO SHOULD BE IN THE DATABASE DCA requests that each individual with a directory on an ARPANET or MILNET host, who is capable of passing traffic across the DoD Internet, be registered in the NIC WHOIS Database. MILNET TAC users must be registered in the database. To register, send via electronic mail to REGISTRAR(a)SRI-NIC.ARPA your full name, middle initial, U.S. mailing address (including mail stop and full explanation of abbreviations and acronyms), ZIP code, telephone (including Autovon and FTS, if available), and one network mailbox. Contact the DDN Network Information Center, REGISTRAR(a)SRI-NIC.ARPA or (800) 235-3155, for assistance with registration. </snip> Shouldn't it be made obsolete ?

4 4

RE: [lir-wg] rfc-ignorant.org
by Wilfried Woeber, UniVie/ACOnet 18 Jul '02

18 Jul '02

> The IP address block 194.78.245.172/30 has a WHOIS contact, > RD3539-RIPE, which lacks an email address. > wripe -t person % This is the RIPE Whois server. % The objects are in RPSL format. % Please visit http://www.ripe.net/rpsl for more information. person: [mandatory] [single] [lookup key] [ ... ] e-mail: [optional] [multiple] [lookup key] [ ... ] ^^^^^^^^ And if we would make it required (I would not object, btw!) - how about registering the.pope(a)holy.see.vt ;-) When and how would we check the usefulness of the eMail entry? And how to deal with race conditions for new sites/networks? Puzzled. Wilfried.

2 1

Re: [lir-wg] rfc-ignorant.org
by Mally Mclane 18 Jul '02

18 Jul '02

On Thu, 18 Jul 2002, D'HERTOG Pieterjan wrote: > Did someone else receive such emails from rfc-ignorant.org? : You may find apnic's APOPs list and the rfc-ignorant discussion list helpful for background: http://www.apnic.net/mailing-lists/apops/archive/2001/10/msg00008.html http://lists.megacity.org/pipermail/rfci-discuss/2001-October/000054.html Do feel free to make your opinion about them and the service they offer. We personally haven't been contacted by them (afaik), but we often get others threatening to submit us to them. Cheers, Mally

1 0

RE: [lir-wg] AS Number Policy
by Wilfried Woeber, UniVie/ACOnet 18 Jul '02

18 Jul '02

>> But, to come back to another comment: we're discussing details of >> routing configuration (because that's "easy"?) but I haven't seen any >> comment yet on my question on price/effort vs. (expected) result ratio >> (maybe because it's a bit more difficult? ;-). > >I am not sure this has anything to do with routing configuration vs >pricing. I agree. >It has to do with application of AS-numbers and who are entiled to >get/have one. > >- kurtis - My point is that any attempt to actively reclaim AS#s is going to *cost money*, both on the NCC's end as well as on the community's end. And as many(?) of the ASs which we are presumably talking about have been distributed _before_ the RIRs have been established, there is probably no (longer) a direct AS#/LIR/RIR (i.e. funding) relationship. And even if, we are talking about *our* (the LIRs') money! That's the reason why I'd like to find out about the expected cost, and even more about any educated guess relating to the number of ASs that can likely be reclaimed. And what a difference that number would make in the context of avoiding the introduction of AS#s with more than 16 bits. I hope I was able this time to get my point across ? Wilfried.

8 9

rfc-ignorant.org
by D'HERTOG Pieterjan 18 Jul '02

18 Jul '02

Did someone else receive such emails from rfc-ignorant.org? : > -----Original Message----- > From: > bounce-ripe+194.78.245.172_ripe_skynet.be(a)beatrice.rutgers.edu > > [mailto:bounce-ripe+194.78.245.172_ripe_skynet.be@beatrice.rut > gers.edu] On Behalf Of > reply-ripe+194.78.245.172_ripe_skynet.be(a)beatrice.rutgers.edu > Sent: donderdag 18 juli 2002 0:18 > To: submit-ipwhois(a)rfc-ignorant.org > Cc: ripe(a)skynet.be; noc(a)skynet.be > Subject: 194.78.245.172/30 > > > > The IP address block 194.78.245.172/30 has a WHOIS contact, > RD3539-RIPE, which lacks an email address. This CIDR block is > therefore subject to listing on the blacklist > ipwhois.rfc-ignorant.org (see http://www.rfc-ignorant.org). > This email is CCd to the following locatable responsible parties: > ripe(a)skynet.be > noc(a)skynet.be > See below for the WHOIS data. > > -Allen > > inetnum: 194.78.245.172 - 194.78.245.175 > netname: SKY-1869366 > descr: Friends Of The Earth > country: BE > admin-c: RD3539-RIPE > tech-c: SN2068-RIPE > rev-srv: ns1.skynet.be > rev-srv: ns2.skynet.be > rev-srv: ns3.skynet.be > rev-srv: ns4.skynet.be > status: ASSIGNED PA > mnt-by: SKYNETBE-MNT > changed: ripe(a)skynet.be 20010806 > source: RIPE > > role: Skynet NOC administrators > address: Belgacom Skynet SA/NV > address: rue colonel Bourg 124 > address: B-1140 Brussels > address: Belgium > phone: +3227061311 > fax-no: +3227269311 > email: ripe(a)skynet.be > admin-c: JFS1-RIPE > tech-c: PDH16-RIPE > nic-hdl: SN2068-RIPE > remarks: ------------------------------------------ > remarks: Abuse notifications to: abuse(a)skynet.be > remarks: Network problems to: noc(a)skynet.be > remarks: Peering requests to: peering(a)skynet.be > remarks: ------------------------------------------ > notify: noc(a)skynet.be > mnt-by: SKYNETBE-MNT > changed: ripe(a)skynet.be 20010907 > source: RIPE > > person: Roger Doiron > address: Friends Of The Earth > address: Rue Blanche 29 > address: 1060 Bruxelles > phone: +32 25420180 > nic-hdl: RD3539-RIPE > remarks: SKYNET-SKYNET-1602730 > notify: noc(a)skynet.be > mnt-by: SKYNETBE-MNT > changed: Ripe(a)skynet.be 20010802 > source: RIPE > > > -- > Allen Smith http://cesario.rutgers.edu/easmith/ > September 11, 2001 A Day That Shall Live In Infamy II > "They that can give up essential liberty to obtain a little > temporary safety deserve neither liberty nor safety." - > Benjamin Franklin > --- Pieterjan d'Hertog, Senior Network Engineer Belgacom Skynet NV/SA, 2 Rue Carli, B-1140 Brussels Phone +3227061311 Fax +3227061150 http://www.skynet.be PGP fingerprint: D9AB CD6A 2A78 73CC 68BF 0AFA 8FB3 5821 E4BB 9D2E

1 0

Anna Skyllberg/Tele2 is out of the office.
by anna.skyllberg＠tele2.se 17 Jul '02

17 Jul '02

I will be out of the office starting 2002-06-21 and will not return until 2002-08-12. I will respond to your message when I return.

1 0