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

Erroneous Domain Cleanup Messages
by Olaf Kolkman 13 Jan '04

13 Jan '04

Dear Colleagues, Apologies for duplicate mails. == Introduction We recently informed the Working Groups about the start of a cleanup of inconsistencies between data in our reverse DNS and data in the Whois Database [1]. Since Wednesday 7 January, 2004 we have been sending out warning messages. Unfortunately a number of messages were sent out in error. == The Problem Due to a bug in the script, messages have been sent to contacts for /24 DOMAIN objects that have a more specific /16 object, stating that there are no matching NS RRs in the zone files and that the DOMAIN object will be deleted. This has been done in error and these DOMAIN objects will remain unaltered. The contacts for these /24 DOMAIN objects will be sent a message shortly confirming that their objects will remain unaltered and that no further action is required on their part. == Background The Whois Database holds informational data for domains in the reverse tree. The database holds information about reverse domains corresponding to /8, /16 and /24 address space. The '/8 domain' zone files at the RIPE NCC only contain NS RRs for the delegation corresponding to the most less specific address block. If there is a /16 DOMAIN object and a number of more specific /24 DOMAIN objects in the database only a delegation will be created corresponding to the /16 DOMAIN object. In other words, if the /16 domain has been delegated one cannot delegate its children any longer. Therefore, the absence of the NS resource records corresponding to the "nserver:" attributes in the /24 DOMAIN objects is not an error. Note: for End Users it is not obvious if an NS RR is in the zone files of the RIPE NCC since ns.ripe.net is a secondary DNS server for the /16 zones. Our apologies for any confusion and extra work this may have caused. For further clarification please do not hesitate to contact <ripe-dbm(a)ripe.net>. --Olaf Kolkman New Projects RIPE NCC [1]: http://www.ripe.net/ripe/mail-archives/dns-wg/2004/msg00000.html Further information about the cleanup project can be found at: http://www.ripe.net/reverse/rdns-project/cleanup.html

1 0

Agenda items....
by Kurt Erik Lindqvist 13 Jan '04

13 Jan '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A small reminder of the agenda for the upcoming RIPE47. So, if you have something you would like to present or discuss.... - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQAOTpaarNKXTPFCVEQKJbQCghHY/8dElwAPC/vNHwuHIDvzJowsAoIi+ Bkvd8wPqlJsuU+Y87SSNGsCn =an2y -----END PGP SIGNATURE-----

1 0

E-mail Client Testing for S/MIME Compliance
by Denis Walker 09 Jan '04

09 Jan '04

[apologies for duplicate messages] Dear Colleagues, At the RIPE 45 Meeting a proposal was presented to implement an additional form of strong authentication for protecting objects in the RIPE Database and to allow for secure communication by e-mail with the RIPE NCC. This implementation uses the X.509 certificates. A question was raised by some members about how widespread is the compliance of S/MIME within mail clients. The RIPE NCC Software Engineering Department has undertaken a study to evaluate the use of S/MIME by mail clients. The results of this study can be found on our web site at: http://www.ripe.net/ripencc/pub-services/db/mail_client_tests.html Regards, -- Denis Walker Software Engineering Department RIPE NCC

4 5

Domail Clean-up
by RIPE Database Manager 06 Jan '04

06 Jan '04

Dear Colleagues, As of 6 January, 2004, messages concerning inconsistencies between "nserver:" attributes in DOMAIN objects and delegation NS RRs in our zone files will be sent out. The messages will be mailed to various contact addresses for the relevant DOMAIN objects. In addition to the description of the inconsistencies, an indication of the 'default actions' will also be provided. We kindly request data be updated so that the inconsistencies are corrected before 1 March, 2004. About two weeks before 1 March, 2004 we will send a second set of warnings for the remaining inconsistencies. By 1 March, 2004 all remaining inconsistencies will be cleaned by the RIPE NCC, using the 'default actions'. If you receive a warning about inconsistencies we recommend that you fix the data yourself. It may be that you receive multiple mails for multiple domains with multiple inconsistencies. If you want to configure a dedicated mail filter the messages will contain the subject header "Subject: Reverse DNS inconsistencies in the RIPE Database" and originate "From: <ripe-dbm(a)ripe.net>". If you have further questions please contact <ripe-dbm(a)ripe.net>. Background The cleanup is part of the effort to streamline reverse DNS operations [1] and make it easier for network range users to manipulate related DOMAIN objects. The goal of the cleanup [2] is to streamline the contents of DOMAIN objects and zone configuration files so that we can create zone files from the Whois Database. An explanation of the various possible inconsistencies can be found at: http://www.ripe.net/reverse/rdns-project/Cleanup.html. ----- [1]: Original proposal http://www.ripe.net/reverse/proposal.html. Discussion on this proposal has taken place on the RIPE NCC Services WG mailing list and was summarized in: http://www.ripe.net/ripe/mail-archives/ncc-services-wg/2003/msg00361.html [2]: Original cleanup proposal http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00738.html. ----- Can Bican Software Engineering Department Olaf Kolkman New Projects Group RIPE NCC

1 0

Call for agenda items
by Kurt Erik Lindqvist 02 Jan '04

02 Jan '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Again, if people have something they would like to bring up at the next NCC WG meeting, please send me an email. Best regards, - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBP/WyYaarNKXTPFCVEQIeYQCg5nDrjSUTu/KhOgh+DHzljqbwbrcAn2sR dMArqQhdu93Dv4DFOaFJTqmt =OpOv -----END PGP SIGNATURE-----

1 0

Change of Minumum IPv4 Allocation Size
by Filiz Yilmaz 23 Dec '03

23 Dec '03

Dear Colleagues, The final date for comments on the "Last Call" on the proposal to change the minimum IPv4 allocation size to /21 ended on 22 December 2003. There were no comments made therefore we will implement this policy change on 1 January 2004. Please note that there will be two changes. Firstly, the minimum IPv4 allocation size is /21. Secondly, it is no longer required to demonstrate efficient utilisation of a /22. Our supporting documentation and software will be updated as soon as possible. Please note that /21 allocations will only come from the 83.0.0.0/8 and 84.0.0.0/8 blocks. A full listing of the "Smallest RIPE NCC Allocation / Assignment Sizes" can be found at: http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html Kind regards, Filiz Yilmaz Snr. Hostmaster RIPE NCC

1 0

LIR Portal maintenance
by Shane Kerr 16 Dec '03

16 Dec '03

Dear Colleagues, On Wednesday, 17th December, between 10:00 and 11:00 CET, there will be a temporary power outage affecting the RIPE NCC LIR Portal. Expected downtime is 15 minutes. During this period the LIR Portal will be unavailable. We apologise for any inconvenience that this downtime may cause to your operations. Regards, -- Shane Kerr RIPE NCC

1 0

Version 2.0 of the LIR Portal to be released on 15 December 2003
by Paul Rendek 15 Dec '03

15 Dec '03

[Apologies for duplicate mails.] Dear Colleagues, We are pleased to announce the release of version 2.0 of the RIPE NCC LIR Portal, the web interface that provides LIRs with simplified access to RIPE NCC services. Version 2.0 of the LIR Portal will be released on Monday, 15 December 2003. Following input received from the RIPE NCC membership, new functionality in version 2.0 of the LIR Portal includes: - Provider Aggregatable (PA) Assignment Request Wizard The wizard is designed for users that are new to the PA request form. It guides the user through the fields, automatically completes certain fields and ensures that the user supplies all the necessary information for RIPE NCC Hostmasters to evaluate the request. This wizard is offered in addition to the existing CGI PA Request Form, which is still available. - Access to multiple LIR Portal accounts LIR Portal users who are contacts for more than one LIR can now be easily added to other LIR Portal accounts and can move between accounts without having to log out and log back in again. - Training Notifications A notification message regarding upcoming training courses in a user's country will be visible on the front page of the LIR Portal as soon as the user logs in. With the release of version 2.0, users will also notice that the navigation menu has been expanded to make navigating the LIR Portal easier. Since the LIR Portal was released in January 2003, new features have been introduced including PKI functionality, the Allocation Editor, CGI request forms and access to member tools and utilities. Bug fixes and regular updates have also been made. We welcome your feedback. Comments on features of the LIR Portal should be sent to <lirportal-feedback(a)ripe.net>. Kind regards, Paul Rendek Head of Member Services & Communications RIPE NCC

1 0

New Statistics Format Released
by Shane Kerr 08 Dec '03

08 Dec '03

Dear Colleagues, The RIPE NCC has been working with the other Regional Internet Registries (RIRs) - APNIC, ARIN, and LACNIC - to provide Internet number resource statistics in a common format and location. The RIR Statistic files summarise the current state of Internet number resources, and are intended to provide a snapshot of their status without transactional or historical details. The following changes will be made to the existing statistics files: - Addition of IPv6 allocations - Addition of Early Registry Transfer (ERX) IPv4 networks - Addition of Provider Independent (PI) assignments - MD5 checksum provided for verification - New directory - Minor changes in format The statistics in the new format are available at: ftp://ftp.ripe.net/pub/stats/ripencc/new/ And the statistics in the current format are available at: ftp://ftp.ripe.net/pub/stats/ripencc/ The RIPE NCC will continue to produce the statistics in the current and new format until 5 January 2004. On this date, the statistics will be in the new format at: ftp://ftp.ripe.net/pub/stats/ripencc/ Statistics previously generated will be available at: ftp://ftp.ripe.net/pub/stats/ripencc/old/ Documentation of the format of these files may be found at: ftp://ftp.ripe.net/pub/stats/ripencc/new/RIR-Statistics-Exchange-Format.txt -- Shane Kerr Software Engineering Department Manager RIPE NCC

1 0

Deprecation of "cross-nfy:" and "cross-mnt:" attributes in the RIPE Whois Database
by Katie Petrusha 05 Dec '03

05 Dec '03

[ Apologies for duplicate messages ] Dear colleagues, "cross-nfy:" and "cross-mnt:" attributes will be deprecated in the RIPE Whois Database by 1 February 2004. The RIPE Whois Database previously had a cross notification mechanism. This mechanism used "cross-nfy:" and "cross-mnt:" attributes of route and aut-num objects to notify particular maintainers and contacts when an overlapping route object had been added or removed. In May 2003, this mechanism was deprecated, as it is already covered by Routing Policy System Security functionality. In March 2003, the proposal was circulated to deprecate "cross-nfy:" and "cross-mnt:" attributes in the RIPE Whois Database as they are no longer needed: http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00035.html Approximately 180 aut-num and 620 route objects will be affected by this change. These objects should be modified before 1 February 2003 and the "cross-nfy:" and/or "cross-mnt:" attributes should be removed from them. As soon as these attributes have been deprecated, they will not be accepted in the RIPE Whois Database. Therefore, we encourage everyone to make the necessary modifications in advance. The RIPE Database Administration will update the objects still requiring modifications to change deprecated attributes into "remarks:" attributes. No individual notifications will be sent. Relevant maintainers will be notified via the usual RIPE Whois Database notification mechanism. This information can be found at: http://www.ripe.net/db/cross_nfy_mnt_deprecation.html -- Katie Petrusha Software Engineering Department RIPE NCC

1 0