From shane at ripe.net Mon Mar 1 06:07:40 2004 From: shane at ripe.net (Shane Kerr) Date: Mon, 01 Mar 2004 14:07:40 +0900 Subject: [ncc-services-wg] Improved Secure Communication for Registration Services (RS) Mailboxes In-Reply-To: <20040225225255.B80A24EF06@postman.ripe.net> References: <20040225.164548.103094935.he@uninett.no> <00a901c3fbb7$8fadb9e0$0100a8c0@doom> <20040225225255.B80A24EF06@postman.ripe.net> Message-ID: <4042C51C.2050305@ripe.net> Randy Bush wrote: >>No but it highlights one of the reasons why X.509 might be the >>better choice. >> >> > >to repeat myself, why is there a choice at all? why one xor the >other, as opposed to one or the other? > > Based on the general discussion here, the RIPE NCC will undertake to implement support for PGP and S/MIME in Hostmaster to LIR e-mail communications. Thank you all for the feedback! -- Shane From randy at psg.com Mon Mar 1 06:10:26 2004 From: randy at psg.com (Randy Bush) Date: Sun, 29 Feb 2004 21:10:26 -0800 Subject: [ncc-services-wg] Improved Secure Communication for Registration Services (RS) Mailboxes References: <20040225.164548.103094935.he@uninett.no> <00a901c3fbb7$8fadb9e0$0100a8c0@doom> <20040225225255.B80A24EF06@postman.ripe.net> <4042C51C.2050305@ripe.net> Message-ID: <20040301051028.A9BFF51DD2@postman.ripe.net> > Based on the general discussion here, the RIPE NCC will undertake to > implement support for PGP and S/MIME in Hostmaster to LIR e-mail > communications. thank you, sir randy From marck at rinet.ru Mon Mar 1 11:13:00 2004 From: marck at rinet.ru (Dmitry Morozovsky) Date: Mon, 1 Mar 2004 13:13:00 +0300 (MSK) Subject: [ncc-services-wg] Improved Secure Communication for Registration Services (RS) Mailboxes In-Reply-To: <4042C51C.2050305@ripe.net> References: <20040225.164548.103094935.he@uninett.no> <00a901c3fbb7$8fadb9e0$0100a8c0@doom> <20040225225255.B80A24EF06@postman.ripe.net> <4042C51C.2050305@ripe.net> Message-ID: <20040301131245.I25559@woozle.rinet.ru> On Mon, 1 Mar 2004, Shane Kerr wrote: SK> Based on the general discussion here, the RIPE NCC will undertake to SK> implement support for PGP and S/MIME in Hostmaster to LIR e-mail SK> communications. Thanks a lot! Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru *** ------------------------------------------------------------------------ From leo at ripe.net Mon Mar 1 12:22:57 2004 From: leo at ripe.net (leo vegoda) Date: Mon, 1 Mar 2004 12:22:57 +0100 Subject: [ncc-services-wg] struct. differences in PI vs. PA request forms & use of role: In-Reply-To: <00A2E104.068DF296.19@cc.univie.ac.at> References: <00A2E104.068DF296.19@cc.univie.ac.at> Message-ID: Hi Wilfried, Thanks for your comments. We include details on how role objects can be used and why they might be used in the course. We don't specifically ask people not to use role objects for "admin-c:" as we cannot know the internal structure of the organisation running a network. On the whole we try to let people know their options, so that they can make the decision that is appropriate to their circumstances when they register their objects in the database. On Feb 27, 2004, at 9:49 pm, Wilfried Woeber, UniVie/ACOnet wrote: [...] > A) why is there a difference between PI and PA forms regarding DB > information? The PA request form no longer includes a complete inetnum template. This is because the Hostmasters do not need to see the whole inetnum object to approve the assignment. Including the inetnum template in PA request form caused more problems than it solved. The RIPE NCC registers the inetnum object in the database when PI assignments are made. For that reason we need to see the whole inetnum object. The supporting notes for the request form state: "The "admin-c:" attribute contains the nic-hdl for the administrative contact person. This person should be administratively responsible for the network. A role object nic-hdl can also be used in this attribute." Contacts from different LIRs need different levels of support in requesting address space and registering assignments. That's why the new PA Request Wizard on the LIR Portal helps the requester put the inetnum object together. When the assignment is approved by the Hostmasters the inetnum is automatically inserted into the database. > B) is there still a recommendation or requirement to use a "real" > person: as the reference for an admin-c:? I suspect that this needs to be decided by database users rather than the RIPE NCC. Times change and recommendations might need to change, too. Regards, -- leo vegoda Registration Services Manager RIPE NCC From woeber at cc.univie.ac.at Mon Mar 1 14:05:18 2004 From: woeber at cc.univie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Mon, 01 Mar 2004 14:05:18 +0100 Subject: [ncc-services-wg] struct. differences in PI vs. PA request forms & use of role: Message-ID: <00A2E31E.B141AA86.13@cc.univie.ac.at> >Hi Wilfried, > >Thanks for your comments. Thanks for the comments and explanation! Wilfried. From olaf at ripe.net Thu Mar 4 17:33:01 2004 From: olaf at ripe.net (Olaf M. Kolkman) Date: Thu, 4 Mar 2004 17:33:01 +0100 Subject: [ncc-services-wg] FYI: Cleanup of domain objects. Message-ID: <20040304173301.101da1de.olaf@ripe.net> Dear Colleagues, Excuxes for the duplicate messages. During the third week of March we will perform the cleanup as described in section B of the "Domain Cleanup Proposal"[1]. Users affected by this cleanup were contacted during the first week of January 2004[2]. Once the domain object cleanup has been finished, the RIPE NCC provisioning system will be migrated to generate reverse zones from the whois database. We will proceed with that around the last week of March 2004. This change should be transparent. A small notification will be sent to the dns-wg mailing list. The next step of the RDNS project [3] will be the introduction of the "mnt-domain:" attribute. More information about this introduction will be sent to the ncc-services-wg and dns-wg mailing lists by the end of March 2004. Please reply to me in private or to the mailing list if you have any questions or comments. --Olaf Kolkman New Projects RIPE NCC [1] http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00738.html [2] The set of people contacted was larger than the set of people actually affected by the cleanup see http://www.ripe.net/ripe/mail-archives/db-wg/2004/msg00086.html for details. [3] http://www.ripe.net/reverse/rdns-project/ From ncc at ripe.net Tue Mar 9 11:35:49 2004 From: ncc at ripe.net (Axel Pawlik) Date: Tue, 09 Mar 2004 11:35:49 +0100 Subject: [ncc-services-wg] Membership Growth Survey 2004 - Please Participate Message-ID: <5.2.1.1.2.20040309112717.00aa9ed0@mailhost.ripe.net> Dear Colleagues, The RIPE NCC's survey regarding membership estimates-by-country is underway on the LIR Portal. We ask for your participation, as your input will influence how the RIPE NCC plans membership fees and activities for the coming year. The survey consists of three short questions and will only take a couple of minutes of your time. It will be available until Friday 26 March. When you log in to the LIR Portal, you will be able to see yearly membership totals in your country for the past five years. Everyone who completes the survey will receive a complimentary gift from the RIPE NCC after the survey closes. The LIR Portal can be accessed at: https://lirportal.ripe.net/lirportal/index.html Regards Axel Pawlik Managing Director RIPE NCC From matthew at ripe.net Tue Mar 9 20:07:08 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 9 Mar 2004 20:07:08 +0100 Subject: [ncc-services-wg] ANNOUNCEMENT: The RIS Project's Second Remote Route Collector in North America Deployed at the NYIIX (RRC11) Message-ID: <004b01c40609$b8058ba0$300200c1@rockstar> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate mails] Dear All, The RIPE NCC is pleased to announce that the RIS Project's second Remote Route Collector in North America, RRC11, is now ready to peer with members at the New York International Internet Exchange (NYIIX). The collector is our first outside of the RIPE region to accept IPv6 peering sessions. RRC11, operational since February 2004, is located at TELEHOUSE's NYIIX 25 Broadway facility and is the twelfth collector to be deployed by the RIS. The RRC has an interface on the shared NYIIX fabric, running both IPv4 and IPv6, and collects routing information from all exchange members willing to peer with us. Our details: - ------------ - - Peering addresses: 198.32.160.99 (IPv4); 2001:504:1:0:0:A501:2654:1 (IPv6) - - Autonomous system: 12654 - - Policy: http://www.ripe.net/ris/rrc11.html - - Peering requests: * Email: rispeering at ripe.net * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi The RIS is also present at MAE-West in San Jose and we are currently looking for more peers there. - - Peering information: http://www.ripe.net/ris/rrc08.html The Routing Information Service (RIS), which started as a modest RIPE NCC project in 1999, has gradually grown to over 300 IPv4 and IPv6 peers at now twelve data collection points in Europe, Japan and North America. Our mission is to collect BGP routing information over a function of time and make it available to the Internet community. In essence, this means devising tools that can help ISPs debug problems over time without being limited to a BGP view, and providing RIS raw data regarding the Internet's historical development. RIS Info: http://www.ripe.net/ris/ RIS Tools: http://www.ripe.net/ris/query.html Please send your comments to ris at ripe.net. Best regards, The RIS Team --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQE4V2MHkFbJe+GdoEQLqHgCffLkOzfP2ByetMOm7r5xpYv+5nSMAoJnW auozPP858ptih7iA0E8Bn4ex =ThXI -----END PGP SIGNATURE----- From webmaster at ripe.net Fri Mar 12 12:08:20 2004 From: webmaster at ripe.net (RIPE NCC WebMaster) Date: Fri, 12 Mar 2004 12:08:20 +0100 Subject: [ncc-services-wg] RIPE NCC Power Interruption Message-ID: <200403121108.i2CB8Kht012167@birch.ripe.net> Dear Colleages, The RIPE NCC experienced an unexpected power outage from 02:00 GMT until 04:00 GMT, at one of our premises. The power outage caused an interruption to some of the RIPE NCC services: - Updates to the RIPE Whois Database were delayed - www.ripe.net - ftp.ripe.net - www.aso.icann.org - www.nro.org - AS112.ripe.net We apologise for any interruption or delay in services. Should you have any questions or concerns regarding this issue please contact . Regards, RIPE NCC Operations From BSanghani at flagtelecom.com Tue Mar 16 18:23:02 2004 From: BSanghani at flagtelecom.com (Sanghani, Bijal) Date: Tue, 16 Mar 2004 17:23:02 -0000 Subject: [ncc-services-wg] Minutes from RIPE NCC Services WG - RIPE 47 Message-ID: <147955311569D511AD0D00508B667530010E8BB0@lon-emailcl.flagtelecom.com> Dear Colleagues, About a month ago we published the draft minutes for the RIPE NCC Services WG sessions at RIPE 47. We also asked for input into the agenda for the WG session(s) at RIPE 48, in May. I'd like to remind you that the theme for RIPE 48 is the RIPE NCC Activity Plan. If anyone would like to make a presentation or raise a topic for discussion please let Kurtis and me know and we'll arrange a spot on the agenda. Thanks, Bijal -----Original Message----- From: Sanghani, Bijal [mailto:BSanghani at flagtelecom.com] Sent: Wednesday, February 11, 2004 12:17 PM To: 'ncc-services-wg at ripe.net' Subject: [ncc-services-wg] Minutes from RIPE NCC Services WG - RIPE 47 Hi All, Attached are the draft minutes for the RIPE NCC Services WG session for RIPE 47 last month, please send details of any errors, corrections or clarifications to Kurtis, myself or to this list. The theme for our session at RIPE 48 will be the RIPE NCC Activity Plan, Axel Pawlik has agreed to give us an update on the progress made on the 2004 plan and input into the 2005 Activity Plan is also welcome. If anyone would like to make a presentation or raise a topic for discussion please let Kurtis and myself know and we'll arrange a spot in the agenda. Best regards, Bijal Sanghani FLAG Telecom <> ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. If you have received this message in error, please notify us by email to postmaster at flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com From ncc at ripe.net Thu Mar 25 10:41:38 2004 From: ncc at ripe.net (Axel Pawlik) Date: Thu, 25 Mar 2004 10:41:38 +0100 Subject: [ncc-services-wg] Membership Growth Survey 2004 - Please Participate Message-ID: <5.2.1.1.2.20040325100706.00b05b78@mailhost.ripe.net> Dear Colleagues, The RIPE NCC's Membership Growth Survey 2004 continues on the LIR Portal. We urge you to participate as your input will influence how the RIPE NCC plans membership fees and activities for the coming year. The survey consists of just three short questions and will only take a couple of minutes of your time. When you start the survey, you will be able to see yearly membership totals in your country from the past five years. Everyone who completes the survey will receive a complimentary gift from the RIPE NCC after the survey closes in April. The LIR Portal can be accessed at https://lirportal.ripe.net/lirportal/index.html Regards Axel Pawlik Managing Director RIPE NCC From peter.galbavy at knowtion.net Thu Mar 25 12:11:02 2004 From: peter.galbavy at knowtion.net (Peter Galbavy) Date: Thu, 25 Mar 2004 11:11:02 -0000 Subject: [ncc-services-wg] LIR closure ? Message-ID: <00bb01c41259$dd850c50$5ce0a8c0@petersdesktopho> I have quite vocal, as many will recall, about the (IMNSHO) excessive costs of small LIRs, especially those like myself that have "legacy" networks to deal with. I have now read ripe-304 about closures and realised what no one has bothered to hint to me previously; I could close the LIR and let the end-user assignments stand and not have to pay the N thousand euros a year for, basically, nothing. As I do not intend to make further assignments from by allocations - if I did, then the company would have business and so would be able to afford to be an LIR - so is this the best thing to do ? Given, due to a combination of cash flow and the refusal until very recently of the NCC to activate my portal access and so deprive me of services I should be paying for, I am about 2 quarters behind on bills, should I also ask the NCC to consider crediting those bills and closing the registry retrospectively ? Is this a "fair" thing to do ? Or am I a scum-bag and its "all my fault" for not reading all these documents in the time I haven't got to be an LIR ? What do I / my customers lose by closing the LIR assuming no assignments are likely to ever be required ? -- Peter Galbavy Knowtion Ltd. From denis at ripe.net Thu Mar 25 16:39:42 2004 From: denis at ripe.net (Denis Walker) Date: Thu, 25 Mar 2004 16:39:42 +0100 Subject: [ncc-services-wg] New database Features Message-ID: <4062FD3E.6010908@ripe.net> Dear Colleagues, [Apologies for duplicate mails] We have recently installed an updated version of the Whois software and Database update software. As well as some bug fixes there are three new features in the Database software. X.509 ----- This is now fully implemented. You are able to create the new X.509 KEY-CERT objects and reference these in the "auth:" lines of a maintainer. You can now use X.509 authentication with all our update methods: mail, syncupdates and webupdates. There is a link to the X.509 enabled webupdates script from the RIPE Whois Database page of the RIPE NCC web site: http://www.ripe.net/db/index.html The direct link is: https://www.ripe.net/perl/webupdates-x509.pl For documentation please refer to: http://www.ripe.net/db/x509.html You may also wish to check some other updated documents on security of objects: http://www.ripe.net/db/security.html http://www.ripe.net/db/Maintainer_Creation_Procedure.html http://www.ripe.net/db/pgp.html CIDR notation for inetnum creation. ---------------------------------- We now allow the use of CIDR notation when creating INETNUM objects. The CIDR string is replaced by the expanded range notation before the object is processed. This feature is ONLY permitted when creating an object. For example if the following object is submitted to the RIPE Database: inetnum: 1.2.0.0/16 before any further processing is done it will be converted to: inetnum: 1.2.0.0 - 1.2.255.255 A warning message will be added to the acknowledgement reply. It is now standard policy to add a warning if any changes are made to the submitted data. Prefix range lists for "mnt-routes:" ---------------------------------- The "mnt-routes:" attribute's syntax has been extended to allow prefix range lists. This will enable people to specify which maintainer has to authorise the creation of the specific routes. As an example: mnt-routes: MY-MNT { 20.34.0.0/1617-18, 20.34.0.0/16^- } mnt-routes: NOT-MY-MNT { ANY } Support for the previous syntax is unchanged. The extended syntax complies with RFC2725 which can be found at: ftp://ftp.ripe.net/rfc/rfc2725.txt For questions and comments please contact . Best regards, -- Denis Walker RIPE NCC Software Engineering Department From matthew at ripe.net Fri Mar 26 14:15:57 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 26 Mar 2004 14:15:57 +0100 Subject: [ncc-services-wg] LAST REMINDER: Two More Days Until the Deadline for Inter-Domain Routing Workshop (IDRWS) Contributions Message-ID: <003701c41334$79da8e10$300200c1@rockstar> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate mails] Dear All, The Inter-Domain Routing Workshop will take place at the RIPE NCC in Amsterdam during the weekend before RIPE 48 (May 1-2, 2004). This RIPE meeting will also be held in Amsterdam. The goal of the workshop is to bring together a focused group of operators, vendors, and researchers to discuss important mid- and long-term operational problems, as well as new academic ideas, in an OPEN forum. The wide scope for topics was intended on our part. Please remember to submit the abstract of your contribution for the workshop by March 28, 2004. See URL for more information: http://www.tm.uka.de/idrws/ Please feel free to drop us a line at idrws at ripe.net. Kind regards, Matthew Williams --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQGQtCcHkFbJe+GdoEQIrmgCfbqka6sFozswIISSklDoh4RFqZvMAoJ8Z Yc/ECI+aav7m1rxW3DdliYyc =lfTS -----END PGP SIGNATURE-----