December 2008 - address-policy-wg

IPv6 assignment for the RIPE meeting network
by Andrei Robachevsky 06 Dec '08

06 Dec '08

Dear Colleagues, This is an informal submission of the proposal that was presented at RIPE 57 in Dubai (http://www.ripe.net/ripe/meetings/ripe-57/presentations/Robachevsky-IPv6_as…), as was suggested by the community. Your feedback is appreciated as well as your opinion whether a formal submission should follow. Regards, Andrei Robachevsky RIPE NCC IPv6 address space assignment for RIPE Meetings --------------------------------------- A dedicated IPv6 prefix is assigned to the organisation that organises the RIPE Meetings. The size of this prefix is a /48 and the assignment will be valid as long as the organisation is responsible for organising the RIPE Meetings and the usage of the prefix is limited to RIPE Meeting networks. The status of this assignment will be 'ASSIGNED MEETING’ in the RIPE Database and must be returned to the RIPE NCC if not in use for RIPE Meeting networks. Rationale: -------- a. Arguments supporting the proposal RIPE NCC has been organising RIPE Meetings for over a decade now and it is still responsible for the setup of the meeting network. As IPv6 deployment has became more of a necessity, the RIPE NCC has been providing IPv6 network during RIPE Meetings too. Although first couple of setups were more at an experimental level, currently we offer this as a production-grade service to the attendees. The IPv6 space for these networks so far has been provided by some other organisations and so the assignments were in temporary nature. We appreciate the support these organisations have provided so far. Today a permanent IPv6 prefix is a necessity to be able to provide a stable and high quality service during RIPE Meetings. Having such a permanent and dedicated prefix, the RIPE Meeting Team of the RIPE NCC will be able to design and test the RIPE meeting network beforehand, which will ensure stable operation of the IPv6 network during the RIPE Meetings. This will also allow the team to have complete control over the network to effectively address issues related to security, redundancy and setting efficient routing policies with third parties. The proposal is worded in a way that the IPv6 prefix will be provided to the RIPE Meeting organiser. This is to ensure that the prefix will stay with the meeting organiser for the sole usage in RIPE meetings. This means if the RIPE NCC ceases being the RIPE Meeting organiser in the future, the prefix will be returned to the free pool. The reason for the size being set to a /48 is about routing reasons. Because this is the minimum excepted routable assignment size that is common among all regions, we think a prefix in this size will guarantee connectivity during RIPE Meetings. b. Arguments opposing the proposal Some may argue that this will cause waste of address space because the prefix will be only in use effectively during RIPE meeting

12 14

Re: [address-policy-wg] Revisiting RIPE Policy Proposal 2007-01
by Sander Steffann 05 Dec '08

05 Dec '08

Hello Clive, >> Note that I'm not a lawyer - but as far as I understand, this is how the >> articles of the NCC are set up. The majority of the LIRs (+proxy votes) >> that attend the AGM vote for the board members and decide on the charging >> scheme (and possible changes to the articles). > > But what is the quorum for the meeting? Is it really as small as under 1%? > If the meeting isn't quorate, its decisions are invalid. If you want to discuss RIPE NCC member related issues, I think you should start a discussion on members-discuss(a)ripe.net. Discussing the RIPE NCC AGM on this list is not really appropriate. We should focus on address policy development here. I understand that this touches both RIPE policy and RIPE NCC membership/fee issues. Let's discuss each issue on the appropriate list. Thanks, Sander Steffann APWG co-chair

1 0

Clarification on End User Assignments Identity Verification
by Flor Paredes 04 Dec '08

04 Dec '08

Dear Colleagues, We wish to clarify the RIPE NCC Registration Services Department procedures with regards to direct End User assignments and the requirement for company registration documents. The RIPE NCC requires some form of registration documents to be submitted with all direct End User assignments, such as ASN, PI, Anycast and IXP assignments. The rationale behind this is to ensure that the End User's proper name is registered in the RIPE Database and in our internal records. Due to the wide variety of entities requiring resources in the RIPE NCC service region, we accept a variety of documents, as long as those documents correctly verify the name of the End User. In a situation where a direct assignment is requested for an organisation that is also an LIR, we waive this requirement because a signed contract and registration documents are already on file. Occasionally, an IPRA may still ask for registration documents during the evaluation of such requests because it may not be immediately obvious from the request form that the assignment is intended for the LIR itself. Once it becomes clear that the assignment is for the LIR itself, we no longer require these documents to be submitted. Best regards, Flor de Maria Paredes Mattos Registration Services Manager RIPE NCC

1 0

RE: [address-policy-wg] Revisiting RIPE Policy Proposal 2007-01
by poty＠iiat.ru 04 Dec '08

04 Dec '08

-----Original Message----- From: address-policy-wg-admin(a)ripe.net [mailto:address-policy-wg-admin@ripe.net] On Behalf Of Garry Glendown Sent: Thursday, December 04, 2008 1:59 PM To: address-policy-wg(a)ripe.net Subject: Re: [address-policy-wg] Revisiting RIPE Policy Proposal 2007-01 ... Speaking of customers - what about customers who aren't an LIR's customers anymore? Can those PI assignments be "redirected" towards either RIPE or the new provider? Or the Enduser himself? Might be hard to come up out of the blue and send a bill over x€ in such a case ... -garry -------------------------- That is the point! There is no way of controlling PIs which have been already issued. Some of them are already routed through other companies and have no relation to the issuer LIR. And there is no mechanism of "returning" these PI assignments and avoid the unfair burdens. Vladislav Potapov Ru.iiat

1 0

Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
by Ana Matic 03 Dec '08

03 Dec '08

PDP Number: 2006-01 Provider Independent (PI) IPv6 Assignments for End User Organisations Dear Colleagues, The text of the policy proposal 2006-01 has been revised based on the community feedback received on the mailing list and during RIPE 56 and 57. We have published the new version (version 4) today. As a result a new Discussion Phase is set for the proposal. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2006-01.html We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net> before 23 December 2008. Regards, Ana Matic RIPE NCC Policy Development Officer

18 20