- ncc-services-wg - mailman.ripe.net

RE: RIPE 48 NCC-Services WG Agenda
by Sanghani, Bijal 23 Apr '04

23 Apr '04

Dear All, With the addition of the NRO update, I've updated the proposed agenda - (Tuesday) A. Administrative Matters -(5 mins) - Welcome - Select a scribe - Distribute participants list - Finalise agenda - Approve minutes from RIPE 47: http://www.ripe.net/ripe/wg/ncc-services/r47-minutes.html> B. Axel - RIPE NCC Update (10-15 mins)/2004 Activity Plan (10-15 mins) C. Number Resource Organization (NRO) Update (10-15 mins) D. RIPE NCC - LIR Portal Update and Members Feedback (10-15 mins) (Thursday) - Distribute participants list E. Axel - 2005 Activity Plan (10-15 mins) F. Kurtis - WG input for the 2005 Activity Plan (10-15 mins) G. Filiz Yilmaz - Authentication for Hostmaster Robot (10-15 mins) H. Daniel Karrenberg - De-Bogonising New Address Blocks (10-15 mins) Y. Open Microphone Z. AOB regards, Bijal -----Original Message----- From: Sanghani, Bijal [mailto:BSanghani@flagtelecom.com] Sent: Thursday, April 15, 2004 4:23 PM To: 'ncc-services-wg(a)ripe.net' Cc: 'webmaster(a)ripe.net'; 'meeting(a)ripe.net'; 'wg-chairs(a)ripe.net' Subject: RIPE48 NCC-Services WG Agenda Dear Colleagues, Below is the Proposed RIPE NCC Services WG Agenda - (Tuesday) A. Administrative Matters -(5 mins) - Welcome - Select a scribe - Distribute participants list - Finalise agenda - Approve minutes from RIPE 47: http://www.ripe.net/ripe/wg/ncc-services/r47-minutes.html> B. Axel - RIPE NCC Update (10-15 mins) C. Axel - 2004 Activity Plan (10-15 mins) D. RIPE NCC - LIR Portal Update and Members Feedback (10-15 mins) E. Filiz Yilmaz - Authentication for Hostmaster Robot (10-15 mins) (Thursday) - Distribute participants list F. Axel - 2005 Activity Plan (10-15 mins) G. Kurtis - WG input for the 2005 Activity Plan (10-15 mins) H. Daniel Karrenberg - De-Bogonising New Address Blocks (10-15 mins) Y. Open Microphone Z. AOB 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. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)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

1 0

ORGANISATION objects in the RIPE Whois Database
by DB-News 19 Apr '04

19 Apr '04

Dear Colleagues, (apologies for duplicate messages) The RIPE NCC is pleased to announce that as of 17, April 2004, a new type of object, the ORGANISATION object, is available in the RIPE Whois Database. You can find more information about the ORGANISATION object at: http://www.ripe.net/db/organisation.html As part of the transition process, the RIPE NCC has: - created ORGANISATION objects for LIRs (around 4000 ORGANISATION objects) - updated LIR allocation objects to include "org:" attributes pointing to these new ORGANISATION objects (around 6500 INETNUM/INET6NUM objects) LIRs can update parts of their ORGANISATION objects through the ORGANISATION Object Editor available through the LIR Portal: https://lirportal.ripe.net/lirportal/index.html Please contact <ripe-dbm(a)ripe.net> for any questions. Best Regards, -- Engin Gunduz RIPE NCC Software Engineering Department

1 0

RIPE NCC Regional Meeting, Moscow, 16-18 June 2004
by Membership Liaison Officer 19 Apr '04

19 Apr '04

[Apologies for duplicate emails] Dear Colleagues, The RIPE NCC is pleased to announce the RIPE NCC Regional Meeting, Moscow, to be held 16 - 18 June 2004 at the Hotel Metropol, Moscow, Russia. Registration for the Regional Meeting opens 19 April 2004. Attendance to the RIPE NCC Regional Meeting is open and free of charge. However, attendees are responsible to cover their own travel and accommodation costs. To register, please see: http://www.ripe.net/cgi-bin/moscow-reg The RIPE NCC Regional Meeting will focus on Internet resource allocation and Internet management issues including: - How to participate in and influence IP address management policy-making; - The industry self-regulatory open structures and processes used by the RIPE NCC and the global Internet community; - Are we running out of IPv4 address space?; - An update on IPv6; - Local, Regional and Global Internet Working and Routing; - Domain Name management on the Internet; - Root Server Operations The Regional Meeting draft agenda can be found at: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/agenda.html RIPE and the RIPE NCC will explain their roles in the administration of the Internet infrastructure as well as specific aspects in managing and operating the Internet infrastructure. The discussions will be directly related to the particular needs and concerns surrounding these issues in the region. The current draft meeting agenda reflects our intentions. However, it requires active participation from the local community to discuss specific issues of the region. The RIPE NCC has reserved several presentation opportunities for those with local knowledge of Internet management and operational issues affecting the region. If your organisation wishes to provide a presentation or suggest a relevant topic, please send your proposal by e-mail to: <contact(a)ripe.net> The RIPE NCC is one of four Regional Internet Registries (RIRs) that provide Internet resource allocation, registration services and co-ordination activities that support the operation of the Internet globally. The RIPE NCC is an independent, not-for-profit membership organisation that provides services to members in its service region currently covering Europe, the Middle East, Central Asia and African countries located north of the equator. Further information about the RIPE NCC and RIPE can be found at: http://www.ripe.net More information about the RIPE NCC Regional Meeting, Moscow is available from: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/ Any further questions can be sent directly to: <contact(a)ripe.net>. Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC

1 0

RIPE48 NCC-Services WG Agenda
by Sanghani, Bijal 15 Apr '04

15 Apr '04

Dear Colleagues, Below is the Proposed RIPE NCC Services WG Agenda - (Tuesday) A. Administrative Matters -(5 mins) - Welcome - Select a scribe - Distribute participants list - Finalise agenda - Approve minutes from RIPE 47: http://www.ripe.net/ripe/wg/ncc-services/r47-minutes.html> B. Axel - RIPE NCC Update (10-15 mins) C. Axel - 2004 Activity Plan (10-15 mins) D. RIPE NCC - LIR Portal Update and Members Feedback (10-15 mins) E. Filiz Yilmaz - Authentication for Hostmaster Robot (10-15 mins) (Thursday) - Distribute participants list F. Axel - 2005 Activity Plan (10-15 mins) G. Kurtis - WG input for the 2005 Activity Plan (10-15 mins) H. Daniel Karrenberg - De-Bogonising New Address Blocks (10-15 mins) Y. Open Microphone Z. AOB 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. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)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

1 0

ANNOUNCEMENT Maintenance on Whois Server Regarding ORGANISATION Object
by DB-News 15 Apr '04

15 Apr '04

Dear Colleagues, [apologies for duplicate messages] On Saturday April 17, 2004, the RIPE NCC will perform maintenance work on the whois server. The aim of the maintenance is to upgrade the whois server to add support for a new object type, the organisation object. The maintenance is scheduled to start at 8:00 UTC (10:00 Amsterdam time) and expected to last around 10 hours. During the maintenance: - e-mail updates to <auto-dbm(a)ripe.net> will be queued to be processed after the maintenance - webupdates and syncupdates interfaces will NOT be available - whois query service will NOT be interrupted The maintenance work will consist of: - upgrading the whois software - creating ORGANISATION objects for LIRs - updating LIRs' allocation objects to have "org:" attributes pointing to these new ORGANISATION objects. We are sorry for any inconvenience this may cause. Please contact <ripe-dbm(a)ripe.net> for any questions. Best regards, -- Engin Gunduz RIPE NCC Software Engineering Department

1 0

Change in Reverse Zone File Generation
by Olaf M. Kolkman 06 Apr '04

06 Apr '04

Dear Colleagues, Apologies for any duplicate messages. This message about our zone file generation process is for your information, there is no action required on your part. We have completed the cleanup of a number of DOMAIN objects in the Whois Database and NS Resource Records in the DNS files [1, 2 and 3]. We have verified that data within zone files generated from the Whois Database matches the data currently in our zone files. We will start generating our zone files from the Whois Database on Tuesday 13 April 2004. >From a DNS point of view this change will be transparent. DNS delegations will not change and there will be no interruptions in DNS service. The change in the method of zone generation allows us to migrate to a new interface for submission of reverse delegation requests. We plan to have the new interface available by the end of April, an announcement to the <dns-wg(a)ripe.net> and <ncc-services-wg(a)ripe.net> mailing lists will be sent. We hope we have informed you sufficiently, do not hesitate to contact us if you have further questions. --Olaf Kolkman New Projects, RIPE NCC References: [1] Original RDNS Project Proposal http://www.ripe.net/reverse/proposal.html [2] Cleanup Proposal http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00738.html [3] RDNS Project Page: http://www.ripe.net/reverse/rdns-project/

1 0

Beta release of Whois S/W with organisation object
by Engin Gunduz 06 Apr '04

06 Apr '04

Dear Colleagues, [Apologies for duplicate mails] We have made available the beta version of RIPE Whois Software that supports the organisation object. You can find it at ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.2.0-org-obj-beta.tar.gz Plese note that the software has been tested only on Solaris 8 environment. Please contact me at <engin(a)ripe.net> for any questions/comments. Best regards, -- Engin Gunduz RIPE NCC Software Engineering Department

1 0

LAST REMINDER: Two More Days Until the Deadline for Inter-Domain Routing Workshop (IDRWS) Contributions
by Matthew Williams 26 Mar '04

26 Mar '04

-----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(a)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-----

1 0

New database Features
by Denis Walker 25 Mar '04

25 Mar '04

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 <ripe-dbm(a)ripe.net>. Best regards, -- Denis Walker RIPE NCC Software Engineering Department

1 0

LIR closure ?
by Peter Galbavy 25 Mar '04

25 Mar '04

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.

1 0