From filiz at ripe.net Mon Feb 1 13:41:29 2010 From: filiz at ripe.net (Filiz Yilmaz) Date: Mon, 1 Feb 2010 13:41:29 +0100 Subject: [ncc-services-wg] Re: [routing-wg]Re: [address-policy-wg] 32-bit AS Number status? In-Reply-To: References: <4B61C989.8010604@time-travellers.org> <0E878365-0E54-4F6B-9038-14ABDDC25EEC@ripe.net> Message-ID: <990D1D6D-509E-463A-9FCB-E6BA251CA20A@ripe.net> Hello, The presentation I have mentioned in my previous mail did not discuss a proposed change in the RIPE ASN policy. In fact, there has been no revisions on the policy document since then and it is still as follows: ---- .. # From 1 January 2009 the RIPE NCC will process applications that specifically request 16-bit AS Numbers and assign such AS Numbers as requested by the applicant. In the absence of any specific request for a 16-bit AS Number, the RIPE NCC will assign a 32-bit only AS Number. # From 1 January 2010 the RIPE NCC will cease to make any distinction between 16-bit AS Numbers and 32-bit only AS Numbers, and will operate AS Number assignments from an undifferentiated 32-bit AS Number allocation pool. ---- The question that the presentation asked was on how exactly the RIPE Community thought the RIPE NCC should be assigning ASN numbers in 2010, following the two pieces of text above and whether they saw a need to change this text. The answer was to continue the way it was done during 2009, seeing no need for a change in the policy text or in the current procedure of the RIPE NCC. The minutes of this discussion was posted to the AP WG mailing list on 13 Aug 2009. Having said that, you can still make a policy proposal if you think that the policy text and so the RIPE NCC procedure must be changed. As a side note, during this presentation, one other issue about 32 bit AS Numbers, relating to the Global ASN policy, was also discussed. This resulted in a formal global proposal and it was discussed in all regions because it required a change in the global policy. You can see the details of this proposal at http://www.ripe.net/ripe/policies/proposals/2009-07.html . RIPE Community reached consensus on this proposal back in September 2009. Kind regards, Filiz Yilmaz Policy Development Manager RIPE NCC On 30 Jan 2010, at 21:21, Hank Nussbacher wrote: > On Fri, 29 Jan 2010, Filiz Yilmaz wrote: > >> Dear Shane, >> >> During RIPE 58, Daniel Karrenberg has made a presentation, titled >> "32-bit ASN Take-Up Report, Policy Adjustments Needed?". >> You can find the presentation at the archives at http://www.ripe.net/ripe/meetings/ripe-58/content/presentations/asn32-take-up-report.pdf >> >> Slide 5 of the presentation relates to your question. The RIPE NCC >> proposed that the method of assigning ASNs that was employed in >> 2009 should continue after 1 January 2010. This means that all >> assignments will be for 32-bit only ASNs by default, unless a 16- >> bit ASN is specifically requested. The AP WG agreed with this >> proposal. > > Does the RIPE NCC consider a slide in a presentation as proper > documentation for revised ASN assignment procedures? > > -Hank > >> >> You can find the records of this at: >> >> http://www.ripe.net/ripe/meetings/ripe-58/meeting-report.php >> and >> http://www.ripe.net/ripe/wg/address-policy/r58-minutes.html >> >> I hope this helps. >> >> Kind regards, >> >> Filiz Yilmaz >> Policy Development Manager >> RIPE NCC >> >> >> On 28 Jan 2010, at 18:29, Shane Kerr wrote: >> >>> All, >>> I noticed that the proposed updated AS Number policy was sent to the >>> address-policy-wg recently. >>> There is a timeline for 32-bit AS Number in both the old and new >>> versions, which says: >>> "From 1 January 2010 the RIPE NCC will cease to make any distinction >>> between 16-bit AS Numbers and 32-bit only AS Numbers, and will >>> operate >>> AS Number assignments from an undifferentiated 32-bit AS Number >>> allocation pool." >>> I'm not sure exactly what this means, but I think it is supposed >>> to mean >>> that people get 32-bit AS Numbers now. Did this happen? >>> If it didn't, why not? Do we need to change "2010" to "2011"? Is >>> it ever >>> going to happen? >>> If it did, was there any effect? I mean both from humans (angry >>> LIRs, >>> peasants marching on the castle with torches, riots in the >>> streets), or >>> on the Intertubes (ugly routing artifacts, mass reboots of boxes >>> with >>> old firmware, monitoring systems gone wild)? >>> Just wondering. :) >>> -- >>> Shane >> From mir at ripe.net Wed Feb 10 14:51:31 2010 From: mir at ripe.net (Mirjam Kuehne) Date: Wed, 10 Feb 2010 14:51:31 +0100 Subject: [ncc-services-wg] RIPE NCC Membership Statistics published on RIPE Labs Message-ID: <4B72B9E3.70602@ripe.net> [apologies for duplicates] Dear colleagues, With the year 2009 behind us, we looked at RIPE NCC membership growth and demographics over time. You can find some interesting statistics on RIPE Labs: http://labs.ripe.net/content/ripe-ncc-membership-growth Next we will look at the distribution of number resources among the membership. Stay tuned! Kind Regards, Mirjam Kuehne From denis at ripe.net Tue Feb 16 13:02:50 2010 From: denis at ripe.net (Denis Walker) Date: Tue, 16 Feb 2010 13:02:50 +0100 Subject: [ncc-services-wg] Unreferenced personal data cleanup process Message-ID: <4B7A896A.1040808@ripe.net> [Apologies for duplicates] Dear Colleagues The RIPE NCC was asked at RIPE 59 to explain in more detail the workings of the new clean-up process for unreferenced personal data. This expanded explanation is now available, with examples, at: http://www.ripe.net/db/support/unreferenced-personal-data-clean-up.html Regards Denis Walker Business Analyst RIPE NCC Database Group From olivia at ripe.net Tue Feb 16 13:31:59 2010 From: olivia at ripe.net (Olivia Mijnals-Ruimwijk) Date: Tue, 16 Feb 2010 13:31:59 +0100 Subject: [ncc-services-wg] Announcement: RIPE NCC Training Courses Message-ID: <4B7A903F.8030600@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/training/lir/outline.html - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/training/rr/outline.html - The IPv6 Training Course This course teaches LIRs about the need for IPv6 and includes basic information on how to plan your deployment. A course outline is available at: http://www.ripe.net/training/ipv6/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: RIPE NCC Upcoming Courses List & Registration https://lirportal.ripe.net/lirportal/training/course-list.html If you have any questions, please do not hesitate to contact us at . Kind regards, Rumy Kanis Training Services Manager RIPE NCC From mir at ripe.net Wed Feb 17 14:59:50 2010 From: mir at ripe.net (Mirjam Kuehne) Date: Wed, 17 Feb 2010 14:59:50 +0100 Subject: [ncc-services-wg] RIPE NCC Membership Growth Statistics (Part 2) on RIPE Labs Message-ID: <4B7BF656.2020508@ripe.net> [apologies for duplicates] Dear colleagues, As announced in an earlier mail, we looked at the distribution of Internet number resources among the RIPE NCC membership. You can find the details on RIPE Labs: http://labs.ripe.net/content/members-and-their-number-resources Kind Regards, Mirjam K?hne From denis at ripe.net Thu Feb 18 18:20:00 2010 From: denis at ripe.net (Denis Walker) Date: Thu, 18 Feb 2010 18:20:00 +0100 Subject: [ncc-services-wg] New Update Reference Manual Message-ID: <4B7D76C0.7050304@ripe.net> Dear Colleagues, [Apologies for duplicates] An updated version of the RIPE Database Update Reference Manual has just been published. This reflects a number of changes made over the last year. It is available in both PDF and HTML formats at: http://www.ripe.net/db/docs.html Regards, Denis Walker Business Analyst RIPE NCC Database Group From denis at ripe.net Thu Feb 18 18:25:46 2010 From: denis at ripe.net (Denis Walker) Date: Thu, 18 Feb 2010 18:25:46 +0100 Subject: [ncc-services-wg] Mandatory maintainer on PERSON and ROLE objects Message-ID: <4B7D781A.2070809@ripe.net> [Apologies for duplicate emails] Dear Colleagues, The Data Protection Task Force asked the RIPE NCC to enforce maintaining all data in the RIPE Database. Currently, the "mnt-by:" attribute is optional in PERSON and ROLE objects. The RIPE NCC has now made this attribute mandatory in both these object types in a test environment. We recommend that anyone who uses automated scripts to generate or modify these objects should test their procedures and scripts against the test facilities. The test server has a recent copy of the RIPE Database data. One significant effect of this change is the circular dependency between PERSON and MNTNER objects. For a new user with no data in the RIPE Database, these two objects must be created together. This cannot be done by the normal update methods. There is a new user start-up interface that creates this pair of objects: https://www.db.ripe.net/cgi-bin/new-user-startup.pl This start-up process is described in the new RIPE Database Update Reference Manual: http://www.ripe.net/db/docs.html The test service is available on a test server at the following URL: whois-mandatory-mntby.db.ripe.net Queries to this database instance can be directed to: whois-mandatory-mntby.db.ripe.net:43 Email updates can be sent to. Synchronous updates are available at: https://syncupdates-mandatory-mntby.db.ripe.net/ Near Real-Time Mirror (NRTM) access is available at: whois-mandatory-mntby.db.ripe.net:4444 Regards Denis Walker Business Analyst RIPE NCC Database Group From denis at ripe.net Tue Feb 23 17:22:02 2010 From: denis at ripe.net (Denis Walker) Date: Tue, 23 Feb 2010 17:22:02 +0100 Subject: [ncc-services-wg] Clean-up of unreferenced personal data in RIPE Database Message-ID: <4B8400AA.2040803@ripe.net> [Apologies for duplicate emails] Dear Colleagues, The RIPE NCC Database Group has restarted the clean-up of unreferenced personal data. This follows the process outlined in the document recently published at: http://www.ripe.net/db/support/unreferenced-personal-data-clean-up.html Regards Denis Walker Business Analyst RIPE NCC Database Group From noreply at ripe.net Thu Feb 25 10:43:30 2010 From: noreply at ripe.net (Arne Kiessling) Date: Thu, 25 Feb 2010 10:43:30 +0100 Subject: [ncc-services-wg] 2007-01 Policy Implementation - Phase Two Deadline - Final Extension Message-ID: <4B864642.30502@ripe.net> Dear Colleagues, We would like to inform you that the RIPE NCC has extended the deadline for phase two of the 2007-01 policy implementation ("Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region") by 2.5 months. LIRs now have until 17 May, 2010 to provide the required documentation for the independent resources that they have marked as "My End User". For further information on the documentation required please see: http://ripe.net/rs/pi-existing-assignments.html If you have any comments or questions, please contact . Kind regards, Arne Kiessling IP Resource Analyst RIPE NCC