- lir-wg - mailman.ripe.net

Mntners with only MAIL-FROM auth
by Andrei Robachevsky 25 Jul '02

25 Jul '02

Attention owners of mntner objects using _only_ MAIL-FROM authentication method. Dear Colleagues, We recently sent out a message to all contacts for maintainers that still used MAIL-FROM as the ONLY means of authentication. This method is no longer valid and no updates can be authorised if any of the maintainers checked are in this situation. The message pointed to the proposed procedure on how to fix such situation (http://www.ripe.net/db/mailfrom.html) The RIPE-DBM support team has been overwhelmed with fax requests to update these maintainers. At the moment we are not able to respond to these requests as quickly as we would like to do. We have found it necessary to give a higher priority to other support requests. Therefore the response time for updates to maintainer authentication may be 5 to 10 working days. Please do not send repeat faxes unless we ask for them and do not send e-mails asking for a status update on the changes. This only slows the whole process down. We will reply to each request as soon as we make the change or find that we need additional information. This message will also be sent to all contacts for maintainers that still use MAIL-FROM as the ONLY means of authentication. Please bear with us on this and we apologise for the delay. Regards, Andrei Robachevsky DB Group Manager RIPE NCC

1 0

Question to a multihomed PA-space connection
by "Thoß, Janko" 25 Jul '02

25 Jul '02

Hello, I have "little" question (but notice that I'm not a guru in BGP-routing and RIPE-problems). We want to connect a customer which don't want to register as a new AS. But he wants a connect to 2 provivers (different AS's). We have tried to get PI-space from RIPE but the automaticly response told us the following: -------- Quote -------- 1. Why is PI space required rather than PA space? - If PI is requested for multi-homing please explain why the second provider cannot route PA space as a more specific route(with the PA block holder adding a more specific route too). - The same policies apply to PI space as PA. Administrative ease and/or routing are not reasons for PI. Please read the information about PA/PI from the RIPE Document, IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region, Sections 5.1.5 and 5.1.6: -------- Unquote -------- Can anyone tell me what is to do for that the second provider is able to announce the /24-PA from the first provider (to emulate a multihomed connection) or is it only possible to use the second provider for backup with the same space? wait hopefully for tips or hints regards, Janko Thoß -- envia.tel GmbH Projektmanager Leipziger Str. 116 b 04425 Taucha Tel.: +49 (0) 341 / 120 7069 Fax: +49 (0) 341 / 120 7052 Mobil: +49 (0) 173 / 379 0048 eMail: janko.thoss(a)envia-tel.de Web: http://www.envia-tel.de

2 1

join two objects
by Mohamed Ibrahem 24 Jul '02

24 Jul '02

Dear all I have some objects for the same customer and I want to merge them in one object. Please advise THANX Mohamed Ibrahim Ali Data Communication ENG

1 0

RE: Help Again Please !
by Razavi (Support) 23 Jul '02

23 Jul '02

I know about this site and i have some documents, but the problem is they dont help and dont give enough information, even i have training course booklet but its not clear ! Regards, --Cathy Razavi. -----Original Message----- From: Stephane Bortzmeyer [mailto:bortzmeyer@gitoyen.net] Sent: Thursday, July 18, 2002 5:00 PM To: Razavi (Support) Cc: bortzmeyer(a)gitoyen.net Subject: Re: Help Again Please ! On Mon, Jul 15, 2002 at 03:20:50PM +0430, Razavi (Support) <krazavi(a)dpimail.net> wrote a message of 9 lines which said: > How can i change our Database or how can i have access to our DB ? i want > to change the information about technical person and get a new Nichhandle ! Read RIPE's documentation. www.ripe.net, it is well organized.

2 1

Re: NCC#2002069654 HMQUESTION
by Knowtion Hostmaster Role Account 23 Jul '02

23 Jul '02

> You are correct to say that you can not remove a maintainer from a <aut-num> > object without adding a new one. > > The attribute <mnt-by> in the <aut-num> object is mandatory, the AS number > AS9179 is part of the <as-block> from the RIPE NCC, and if correct the > maintainer <AS9179-MNT> is being maintained by yourselves. How can I phrase this better ? AS9179-MNT (me / my company) is the current but out-of-date maintainer on an object. Without deleting the object (as it is not relly mine) how can I cease being associated with it ? I (AS9179-MNT) no longer am the maintainer of various objects that really belong to the company X in the UK. My company has not been associated with them or provided services to them for sometime. Is it good and recommended practice therefore for me to just delete the objects - this may affect someones service ? cc'ed to lir-wg in case anyone has a better idea... Petr

5 5

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