December 2009 - ncc-services-wg

New RIPE NCC Procedural Document Available
by Andrea Cima 28 Feb '11

28 Feb '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate emails] Dear Colleagues, The RIPE NCC has published a new RIPE NCC procedural document: ripe-475, "Independent Internet Number Resources – Contractual Relationship Changes between sponsoring LIR and End User" This document describes the steps to be taken when there are changes in the contractual relationship between the End User of independent Internet number resources and the sponsoring Local Internet Registry (LIR). It also describes the scenarios in which the RIPE NCC may de-register independent Internet number resources and what happens to those resources once they are de-registered. The new document is available at: http://www.ripe.net/ripe/docs/ripe-475.html Kind regards, Andrea Cima RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpfPukACgkQXOgsmPkFrjNlEwCcDtE364DhQCU0USBoK3kJhord yBgAoMbRsLFCStkXfvEaV6Mtm5b2sfxW =fKC3 -----END PGP SIGNATURE-----

8 11

Independent Resource procedure and implementation
by Daniel Suchy 28 Oct '10

28 Oct '10

Hello, I would like to open discussion related to "Action Required: Contractual Relationship for Independent Resource Assignments" emails, that almost all LIRs received from RIPE NCC in the past. I have some notes from perspective of small LIR (or from perspective of person helping running multiple small LIRs). My first note points to system in general. Although RIPE NCC has many required informations in own existing databases already, it requires additional action from LIR in general. Typical small LIR has one or more PA allocations and exactly _one_ autonomous system registered. In RIPE database, there are records matching allocated PA prefix and ASN (route objects with proper origin AS and related inetnum objects, many ASNs has paired LIRs org: in aut-num object). In addition, RIS service (with history!) can be used for verification of these informations obtained automatically from database. For incomprehensible reason, RIPE NCC doesn't use these informations at all and instead of this abuses ALL LIRs with submiting simple form with exactly one record within it. I thing RIPE RCC has enough resources (financial and human) to do that automatically. My second note points to implementation of this new tool. I discovered, that I'm not able to "new" tool used for confirmation. I'm using PKI login feature and I have one identity paired with more LIRs. Although I'm able login to the LIR portal and modify everything I need with my certificate, I'm _NOT_ able to update informations on "Independent Resources" page. The main reason is, that RIPE NCC created new and separated (!) tool instead of simple integration of new feature/functionality to existing LIR portal. So, instead of reusing existing code used for LIR portal authentication, new outside code was developed for this new tool. And this new code doesn't implement all authentication features from LIR portal. In my point of view, this is quite unprofessional approach of modern application development. Aplications should be multi-layer, allowing easy new feature implementation. I reported this issue to RIPE NCC on friday last week, but first "answer" I received yesterday from RIPE NCC was initiation of audit in one LIR. Just fortuitous event? I don't believe. I have no problems with audit itself, I have all records, but this takes some additional time (and of course, money). Just because I claimed some problems to RIPE NCC staff due to problematic internal _implementation_ of new policy. Ok, I would like to open public discussions about this problem. There are some questions to answer and discuss: * why RIPE NCC just doesn't use informations from RIPE database in case of their availability and verifiability, why abuses small LIRs instead * why aren't RIS data used for automatic obtaining of requested informations, where this can be applicable * why RIPE NCC didn't integrate "confirmation" tool to existing LIR portal and why new outside application with _limited_ functionality was developed instead of reusing of existing code and functionality * what architecture is used for LIR portal in general, can be there easily implemented new features Of course, I understand, that there are large LIRs and some historic mess, where this action may be required due to lack of records in existing databases. But, I think this is NOT a case of LIRs started in past couple of years, where all required data should be available. With regards, Daniel

13 28

2007-01 Policy Implementation - Phase Two Deadline Extended
by Arne Kiessling 30 Dec '09

30 Dec '09

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 two months. LIRs now have until 1 March, 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 <enduser-contract(a)ripe.net>. Kind regards, Arne Kiessling IP Resource Analyst RIPE NCC

1 0

RE: [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key
by Thor Kottelin 18 Dec '09

18 Dec '09

> From: "Cosku Yilmaz" <cosku(a)cccmos.com> > To: <ncc-services-wg(a)ripe.net>, > <ncc-announce(a)ripe.net> > Date: Fri, 18 Dec 2009 12:39:15 +0300 > Would you please explain what is need to be done and what the steps > are. Do you use, or intend to start using, PGP? If not, you do not need to do anything. If you do use PGP, the steps are basically: download the key, check its authenticity, sign it using your copy of PGP and add it to a key ring. Then use the new key (instead of the previous one) to verify the email messages you receive from the RIPE NCC. -- Thor Kottelin http://www.anta.net/

2 3

FW: [ncc-announce] New RIPE NCC PGP Key
by Cosku Yilmaz 18 Dec '09

18 Dec '09

To whom it may concern; I received your e-mail below. Unfortunately it is not clear what I am supposed to do? Would you please explain what is need to be done and what the steps are. Best Regards, ___________________________________ Cosku Yilmaz Managing Director CCCMOS Group Microsoft Gold Certified Partner Tel/ Fax : + 7 (495) 727 41 77 (pbx) E-Mail : cosku.yilmaz(a)cccmos.com URL : http://www.cccmos.com -----Original Message----- From: ncc-announce-admin(a)ripe.net [mailto:ncc-announce-admin@ripe.net] On Behalf Of Laura Cobley Sent: Thursday, December 17, 2009 7:29 PM To: ncc-services-wg(a)ripe.net; ncc-announce(a)ripe.net Subject: [ncc-announce] New RIPE NCC PGP Key [Apologies for duplicate e-mails] Dear Colleagues, On Wednesday, 6 January 2010 we will start using our 2010 key to sign e-mail from our ticketing system. The new key has been signed by the old key as described in the key-management policy on our web site: https://www.ripe.net/rs/pgp/index.html The old key remains valid until Wednesday, 10 February 2010. If you have any questions about this, please contact <ncc(a)ripe.net>. Kind Regards, Laura Cobley RIPE NCC

2 1

New RIPE NCC PGP Key
by Laura Cobley 17 Dec '09

17 Dec '09

[Apologies for duplicate e-mails] Dear Colleagues, On Wednesday, 6 January 2010 we will start using our 2010 key to sign e-mail from our ticketing system. The new key has been signed by the old key as described in the key-management policy on our web site: https://www.ripe.net/rs/pgp/index.html The old key remains valid until Wednesday, 10 February 2010. If you have any questions about this, please contact <ncc(a)ripe.net>. Kind Regards, Laura Cobley RIPE NCC

1 0

DOMAIN object proposals
by Denis Walker 14 Dec '09

14 Dec '09

Dear Colleagues, The RIPE NCC made two proposals recently concerning DOMAIN objects: 22 October New rules for reverse domain object creation in the RIPE Database http://www.ripe.net/ripe/maillists/archives/dns-wg/2009/msg00104.html 23 November Removal of Forward DOMAIN data from the RIPE Database http://www.ripe.net/ripe/maillists/archives/dns-wg/2009/msg00119.html There have been no comments for or against either of these proposals on the mailing lists. They were both discussed at RIPE Meetings, without any negative comments. We would like to ask for any final comments by this Friday, 4 December 2009, so the working group chairs can then draw a consensus. Regards, Denis Walker Business Analyst, Database Group RIPE NCC

3 2

2009-08 Implementation: IPv6 PI Assignments for LIRs
by Nathalie Trenaman 10 Dec '09

10 Dec '09

[Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that RIPE Policy Proposal 2009-08,"IPv6 Provider Independent (PI) Assignments for LIRs", has been implemented. The RIPE NCC is now ready to accept requests for IPv6 address space under the new policy. This proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2009-08.html The updated "IPv6 Address Allocation and Assignment Policy" document is available at: http://www.ripe.net/ripe/docs/ipv6-policies.html The following document has also been updated to reflect this policy implementation: http://ripe.net/ripe/docs/ipv6-pi-support.html Regards, Nathalie Trenaman Registration Services RIPE NCC

1 0