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

Proposal to Change the Dash ('-') Notation in Reverse DOMAIN Objects
by Denis Walker 18 Apr '11

18 Apr '11

[Apologies for duplicate emails] Dear Colleagues, What follows is a short proposal to change the process of creating and updating reverse DOMAIN objects in the RIPE Database. Because this is a proposed RIPE Database change, please direct any discussion to the RIPE Database Working Group mailing list to keep it focused in one place. Regards, Denis Walker Business Analyst RIPE NCC Database Group Proposal to change the dash ('-') notation in reverse DOMAIN objects Introduction ------------ Reverse delegation DOMAIN objects allow the use of a dash ('-') in the syntax. The current arrangement causes problems with DNSSEC. We propose to drop the current behaviour. We would also introduce a new syntax using the dash notation to avoid the need for manual intervention for classless delegations. Both the current and the new behaviour described in this document only apply to IPv4 delegations. Feature to be deprecated ------------------------ Currently, we allow a dash in the third octet of an IPv4 reverse delegation. So, for the address range 10.2.1.0 - 10.2.100.255, the syntax allows a reverse delegation DOMAIN object to be submitted as 1-100.2.10.in-addra.arpa. The RIPE Database update software will expand this into 100 separate objects in the database with prefixes from 1.2.10.in-addra.arpa to 100.2.10.in-addra.arpa. Apart from the prefix, all the other data in the submitted object will be duplicated in all 100 objects. To modify or delete this set of objects, the user has to process all 100 objects individually. No bulk operations are possible after the original object has been expanded in the database. This feature is not compatible with using DNSSEC. The value of the "ds-rdata:" attribute is a hash that includes the delegation. By definition, this must be different for each DOMAIN object. These different hash values for multiple objects cannot be entered by submitting a single object with the dash notation. This issue was raised by members of the DNS community, and the RIPE NCC now proposes to deprecate this update feature. Feature to be added ------------------- Classless delegations, according to RFC2317 (http://www.ietf.org/rfc/rfc2317.txt), are currently handled manually by the DNS Department at the RIPE NCC. Although the objects can be created in the RIPE Database, they will not be propagated to the zone files. The RIPE NCC proposes to allow a dash in the fourth octet of an IPv4 reverse delegation. So, for the address range 10.2.1.6 - 10.2.1.25, the syntax would allow a reverse delegation DOMAIN object to be submitted as 6-25.1.2.10.in-addra.arpa. This object would not be expanded by the RIPE Database update software into 20 separate objects, as it is with the feature described above. It would be created in the database as a single object, including the dash in the range. New DNS provisioning software would handle the new dash notation and propagate this delegation to the zone file. However, the range 0-255 is a special case and would not be allowed in the fourth octet. Modification and deletion can be performed on the single object in the database. Any change would be propagated into the zone file by the new delegation software.

6 10

APNIC Announces its IPv4 Address Pool Reaches Final /8
by Axel Pawlik 15 Apr '11

15 Apr '11

[Apologies for duplicate emails] Dear Colleagues, Today, Friday 15 April 2011, APNIC, the Regional Internet Registry (RIR) for the Asia Pacific region, announced that it has distributed the final IPv4 address space from its reserves of IPv4. This means that APNIC is now supplying IPv4 address space to its members from the last /8 it holds according to the guidelines in section 9.10 in "Policies for IPv4 address space management in the Asia Pacific region": http://www.apnic.net/policy/add-manage-policy This event does not affect the RIPE NCC's reserves of IPv4 address space and we will continue to distribute these resources to our members on the basis of need until we reach the last /8. According to RIPE Document ripe-509, section 5.6, once the RIPE NCC reaches the last /8 of IPv4 address space, each Local Internet Registry (LIR) can receive one /22 (1024 IPv4 addresses) upon application for IPv4 resources. In order to obtain this /22 allocation, the LIR must already have an IPv6 allocation and have a demonstrated need for address space. IPv6 - Act Now --------------- The RIPE NCC cannot predict how long its own supply of IPv4 address space will last and has worked for several years to inform all stakeholders of the urgent need to deploy IPv6. It is now imperative that all stakeholders deploy IPv6 on their networks to ensure the continuity of their online operations and the long-term growth of the Internet. For more information on IPv6 and its deployment, advice from experts and where to get training, please see: www.ipv6actnow.org Further Information -------------------- For more information on IPv4 exhaustion, please see: http://www.ripe.net/internet-coordination/ipv4-exhaustion For more information on how the RIPE NCC's last /8 will be distributed, please see: http://www.ripe.net/ripe/docs/ripe-509 For information about the amount of IPv4 address space left in the RIPE NCC's available pool of IPv4, please see the graph online at: http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-po… Regards, Axel Pawlik Managing Director RIPE NCC

1 0

Next RIPEstat live demo on 19 April 2011
by Mirjam Kuehne 14 Apr '11

14 Apr '11

[apologies for duplicates] Dear colleagues, The next RIPEstat Live Demo is scheduled for Tuesday, 19 April 2011 at 11:30 - 12:00 Amsterdam time (9:30 - 10:00 UTC). Please observe the change to summer time. I hope you will join us. Details on how to join the demo session can be found on RIPE Labs: http://labs.ripe.net/Members/markd/ripestat-live-demo-4 The minutes of the last sessions and some more information about RIPEstat can be found on RIPE Labs: http://labs.ripe.net/ripestat Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Resource Certification Web Validator Released
by Mirjam Kuehne 13 Apr '11

13 Apr '11

Dear colleagues, The RIPE NCC released a Resource Certification Web Validator. Read more on RIPE Labs: http://labs.ripe.net/Members/AlexBand/resource-certification-web-validator-… Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Call For Agenda Items RIPE 62
by Bijal Sanghani 12 Apr '11

12 Apr '11

Dear NCC-Services WG, RIPE 62 in Amsterdam is approaching fast and we are looking at putting the agenda together for the NCC Services WG. This is your opportunity to let the RIPE NCC know what you want from them, if you would like to suggest a presentation or raise a topic for discussion please let me know. Kind regards, Bijal Sanghani RIPE NCC Services WG Co-Chair The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

Resource Certification Statistics
by Mirjam Kuehne 12 Apr '11

12 Apr '11

Dear colleagues, We published some statistics on RIPE Labs that show the number of certificates generated since we launched the service in January 2011: http://labs.ripe.net/Members/AlexBand/resource-certification-statistics Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Deletion of Forward DOMAIN object data from the RIPE Database
by Denis Walker 07 Apr '11

07 Apr '11

[Apologies for duplicate emails] Dear Colleagues, The RIPE NCC announced to the mailing lists on 29 March that Forward DOMAIN object data will be deleted this week: http://www.ripe.net/ripe/maillists/archives/db-wg/2011/msg00074.html All Forward DOMAIN object data has now been deleted from the RIPE Database, except for the four top-level domain (TLD) operators who are still actively using the RIPE Database. It is not possible for any user to re-create a top-level Forward DOMAIN object in the RIPE Database. Without the TLD object, no second-level DOMAIN object creations can be authorised. When the last four TLD operators have moved their data to their own systems, we will modify the update software so it will not recognise any Forward DOMAIN objects. Regards, Denis Walker RIPE NCC Database Group

3 4

Registration Services Procedure - Now Online
by Alex le Heux 31 Mar '11

31 Mar '11

Dear colleagues, The RIPE NCC has published a Registration Services Procedure to help guide our members through the process of submitting an IPv4 address space request. The document can be found at: http://www.ripe.net/lir-services/resource-management/contact/registration-p… The aim is to inform LIRs about what is expected from them during an evaluation and what kind of information the IP Resource Analyst (IPRA) is looking for. This document covers the most common types of requests that reflect the business models and technology deployments in the RIPE NCC service region. If the document is considered useful by the RIPE NCC membership, the RIPE NCC will produce the same documentation for IPv6 and aut-num requests. Best regards, Alex Le Heux RIPE NCC

1 0

Now Online - Registration Services Procedures
by Alex Le Heux 31 Mar '11

31 Mar '11

Dear colleagues, The RIPE NCC has published a Registration Services Procedure to help guide our members through the process of submitting an IPv4 address space request. The document can be found at: https://www.ripe.net/lir-services/resource-management/contact/registration-… The aim is to inform LIRs about what is expected from them during an evaluation and what kind of information the IP Resource Analyst (IPRA) is looking for. This document covers the most common types of requests that reflect the business models and technology deployments in the RIPE NCC service region. If this document is considered to be useful by the RIPE NCC membership, the RIPE NCC will produce the same documentation for IPv6 and AS Number requests. Best regards, Alex Le Heux Policy Implementation Co-ordinator RIPE NCC

1 0

Deletion of Forward DOMAIN data from the RIPE Database
by Denis Walker 29 Mar '11

29 Mar '11

[Apologies for duplicate emails] Dear colleagues, The RIPE NCC is ready for the next stage of this clean-up process, as discussed at the last few RIPE Meetings. The RIPE Database still contains many forward DOMAIN objects, listed below. Only four TLD Registries are still actively using the RIPE Database for their whole provisioning or for a second-level dataset, .SM, .MC, .NO, .IL. These four Registries are working on alternative solutions and their data will remain in the RIPE Database until their arrangements are complete. Looking at the update logs for the last year, there has been very little activity on all the other DOMAIN data (summarised below). The occasional updates are End Users who maintain their own DOMAIN objects. Even though the activity logs show that these Registries were not actively using the RIPE Database, we still contacted them for confirmation. In some cases, we received no response. The RIPE NCC will delete all the forward DOMAIN data (except for the four active users) in the week beginning Monday, 4 April 2011. Regards, Denis Walker Business Analyst RIPE NCC Database Group List of registries with forward DOMAIN data in the RIPE Database 2 al 12 at 2 az 9 ba 2 by 2 cm 24 com 1 cx 1 dz 8 ee 2 es 56 fi 2 ga 668 gm 26 hu 8 ie 176 il 2 ir 1 jj 3 jo 1 ke 1 kg 1 kr 4 kz 1 lb 1 lc 1 lv 1 ly 1 ma 702 mc 1 mt 55 net 82 no 9 org 1 pk 99 pl 20 pt 4 ru 6 sa 2210 sm 33 tr 1 va Activity over last year 2010 1 Create Modify delete fo 34 29 12 il 0 2 0 sm 27 12 15 2010 2 Create Modify delete fo 26 21 41 md 0 2 0 pl 0 1 0 sm 18 44 12 2010 3 Create Modify delete TLD si 0 0 1 es 0 0 1 fo 34 48 24 ly 0 0 3 sm 24 23 15 2010 4 Create Modify delete fo 38 34 13 net 0 0 1 si 0 0 1 sm 26 9 13 2010 5 Create Modify delete TLD de 0 1 0 fo 32 27 13 gr 0 1 0 il 0 2 0 mc 0 1 0 org 0 1 0 sm 37 10 10 2010 6 Create Modify delete TLD dk 0 1 0 fo 3 10 2 mc 2 8 0 sm 9 5 12 2010 7 Create Modify delete TLD fo 0 1 0 fo 0 0 1 gr 0 2 0 mc 2 2 0 sm 18 8 16 2010 8 Create Modify delete TLD fo 0 3 0 fo 0 0 3109 sm 16 14 10 2010 9 Create Modify delete mc 2 0 0 sm 20 20 9 2010 10 Create Modify delete be 0 0 1 gr 0 1 0 mc 1 0 0 sm 25 16 119 2010 11 Create Modify delete be 0 0 30 bg 0 0 5 cz 0 0 3 de 0 0 1 fi 0 1 0 gl 0 0 22 gr 0 0 75 it 0 0 2 lv 0 0 62 md 0 0 15 ro 0 0 1 se 0 0 6 sm 29 15 11 tn 0 0 2 ug 0 0 1 uk 0 0 4 2010 12 Create Modify delete sm 11 272 7 2011 1 Create Modify delete mc 2 0 0 sm 22 9 23 2011 2 Create Modify delete TLD is 0 1 0 fi 0 2 0 sm 13 3 66

1 0