- ipv6-wg - mailman.ripe.net

Fwd: [routing-wg] IPv6 Routing Recommendations.
by Rob Evans 24 Feb '11

24 Feb '11

Good people of the IPv6 Working Group, It was suggested to me that for some strange reason you may also be interested in this document and discussion... Best regards, Rob -------- Original Message -------- Subject: [routing-wg] IPv6 Routing Recommendations. Date: Wed, 23 Feb 2011 14:39:18 +0800 From: Rob Evans <rhe(a)nosc.ja.net> To: routing-wg(a)ripe.net All, You may remember that back in the mists of time (about a year ago) we had a document that updated RIPE-399 with some IPv6 routing recommendations. After the meeting last May, the authors were to go away and take out mention of any specific suggestions on filtering (e.g. /36). Over the past 12 months, Philip and I have been hard at work constantly refining this document to reflect the changing nature of the IPv6 routing table. Well, kind-of. Anyway, my laziness aside, appended is the document as it stands at the moment. Comments and discussion please! Rob RIPE Routing Working Group Recommendations on IPv6 Route Aggregation ==================================================================== Rob Evans Philip Smith Introduction ============ Recent discussion has shown there is a limited requirement to be able to advertise more specific prefixes from an IPv6 Provider Aggregatable (PA) allocation where a Local Internet Registry (LIR) contains several networks which are not interconnected, or for traffic engineering purposes. This document recommends such advertisements are limited in both length and scope. It is intended to supplement the working group's Recommendations on Route Aggregation [RIPE-399]. Background ========== The IPv6 address allocation and assignment policy for the RIPE region [V6-ALLOC] only allows LIRs to obtain more than the minimum PA allocation if they can demonstrate address utilisation that requires it. This fits with the address space management principle of conservation. However, as understood in the RIPE Routing Working Group's Recommendations on Route Aggregation [RIPE-399], there are occasionally requirements for the advertisement of more specific routes from within an allocation. With a few ISPs currently filtering at the minimum PA allocation (/32) within the relevant address ranges, this can cause significant difficulties for some networks wishing to deploy IPv6. Some reasons for wanting to advertise multiple prefixes from a PA allocation could be: - The LIR has several networks that are not interconnected. - Traffic engineering: A single prefix that covers an LIR's entire customer base may attract too much traffic over a single peering link This document is only concerned with IPv6 Provider Aggregatable (PA) allocations, and does not discuss Provider Independent (PI) prefixes. Recommendation ============== It is suggested that prefix filters allow for prudent subdivision of an IPv6 allocation. The operator community will ultimately decide what degree of subdivision is supportable, but the majority of ISPs accept prefixes up to a length of /48 within PA space. Advertisement of more specific prefixes should not be used unless absolutely necessary and, where sensible, a covering aggregate should also be advertised. Further, LIRs should use BGP methods such as NO_EXPORT [RFC-1997], [AS-PATHLIMIT], or provider-specific communities, as described in [RIPE-399] to limit the propagation of more specific prefixes in the routing table. Discussion ========== There is a valid need for some LIRs to advertise more than one IPv6 PA prefix. As either obtaining more address space and advertising more /32 prefixes, or advertising more specific prefixes within an already allocated /32 have the same impact on the routing table, it is suggested that the latter approach is taken to prevent address space wastage. It is understood that this may not cover all possibilities. There may be circumstances where sites will have to consider the suitability of Provider Independent addresses, or LIRs may have to consider mechanisms of obtaining more than a /32 of Provider Aggregatable space. References ========== [V6-ALLOC] http://www.ripe.net/ripe/docs/ipv6policy.html [RIPE-399] http://www.ripe.net/ripe/docs/ripe-399 [RFC-1997] http://www.rfc-editor.org/rfc/rfc1997.txt [AS-PATHLIMIT] http://tools.ietf.org/html/draft-ietf-idr-as-pathlimit-03 Work in Progress.

1 0

Announcement: RIPE NCC Training Courses
by Training Mailbox 22 Feb '11

22 Feb '11

[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/lir-services/training/courses/lir/outline/ - 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/lir-services/training/courses/rr/ - 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 <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

RIPE 62 working group session
by Marco Hogewoning 22 Feb '11

22 Feb '11

Dear Colleagues, Registration for the RIPE 62 meeting, which takes place from 2 till 6 May in Amsterdam (NL). As you may have noticed the IPv6 working group is missing from the meeting plan. This is not an error, but an intentional change to the agenda. After some discussion with the working group chairs collective and other stakeholders, we concluded that the IPv4 run out and the associated need to deploy IPv6 will most likely be a very hot topic on this upcoming meeting. It has therefor been decided that the time originally allocated for our working group would be added to the plenary program. Any interesting IPv6 topics, and I'm sure there are many, will be placed in the plenary schedule. At the same time, the closing plenary on Friday morning will host a "IPv6 roundup". In this session we will discuss the outcome of the meeting, based on input received from the working groups and presentations or comments during the plenary sessions. In other words, no need to panic. The IPv6 working group will be present, although not in a formal setting this time. If you have any interesting information on IPv6 deployment, interactions between IPv4 and IPv6 and deployment of transitioning techniques. Please consider presenting about it on this meeting and send a short description of what you like to present together with your contact details to ipv6-wg-chairs at ripe dot net. See you in Amsterdam, The IPv6 working group chairs, Marco, Shane and David.

1 0

Registering IPv6 Assignments in the RIPE Database
by Denis Walker 15 Feb '11

15 Feb '11

[Apologies for duplicate emails] Dear Colleagues The RIPE community recently approved RIPE Policy Proposal 2010-06, "Registration Requirements for IPv6 End User Assignments". The proposal is available at: [http://www.ripe.net/ripe/policies/proposals/2010-06] This has now been implemented in the RIPE Database and other RIPE NCC processes, where necessary. Details of how to use the new aggregation feature of the RIPE Database can be found at: http://www.ripe.net/data-tools/support/documentation/documenting-ipv6-assig… For those who have already made some IPv6 assignments, you will need to document them in the RIPE Database according to the policy if you have not already done so. All new IPv6 assignments must be registered in the RIPE Database in accordance with this policy. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

2010-06 Proposal Accepted (Registration Requirements for IPv6 End User Assignments)
by emadaio＠ripe.net 10 Feb '11

10 Feb '11

Dear Colleagues, Consensus has been reached, and the proposal described in 2010-06 has been accepted by the RIPE community. The updated policy "IPv6 Address Allocation and Assignment Policy" is available at: http://www.ripe.net/ripe/docs/ripe-512 The new policy "Value of the "status:" and "assignment-size:" attributes in inet6num objects for sub-assigned PA space" is available at: http://www.ripe.net/ripe/docs/ripe-513 You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2010-06 Thank you for your input. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

FWD: IANA Allocates Two /8s of IPv4 Space to APNIC
by David Kessens 02 Feb '11

02 Feb '11

----- Forwarded message from Axel Pawlik <no-reply(a)ripe.net> ----- Date: Tue, 01 Feb 2011 05:27:16 +0100 From: Axel Pawlik <no-reply(a)ripe.net> To: ripe-list(a)ripe.net, ncc-announce(a)ripe.net, ncc-services-wg(a)ripe.net Subject: IANA Allocates Two /8s of IPv4 Space to APNIC Reply-To: no-reply(a)ripe.net [Apologies for duplicate emails] Dear colleagues, On 1 February 2011, the IANA allocated two /8s of IPv4 address space to APNIC, the Regional Internet Registry (RIR) for the Asia Pacific region. This means that only five /8s of IPv4 address space are left in the IANA free pool and the "Global Policy for the Allocation of the Remaining IPv4 Address Space" will be triggered. This policy can be found online at: http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm When this policy comes into effect, the five RIRs will each receive one of the five remaining /8s and the global IPv4 pool will be exhausted. We expect IANA to allocate these final /8s within the next few days. For further information please see: http://www.ripe.net/v4exhaustion/ Regards, Axel Pawlik Managing Director RIPE NCC ----- End forwarded message -----

1 0

[sunny@apnic.net: [apops] Two /8s allocated to APNIC from IANA (39/8 and 106/8)]
by David Kessens 01 Feb '11

01 Feb '11

----- Forwarded message from Srinivas Chendi <sunny(a)apnic.net> ----- Date: Tue, 01 Feb 2011 09:20:41 +1000 From: Srinivas Chendi <sunny(a)apnic.net> To: apops(a)apops.net Subject: [apops] Two /8s allocated to APNIC from IANA (39/8 and 106/8) _______________________________________________________________________ Two /8s allocated to APNIC from IANA (39/8 and 106/8) _______________________________________________________________________ Dear Colleagues The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following IPv4 address blocks from IANA in February 2011 and will be making allocations from these ranges in the near future: 39/8 106/8 Reachability and routability testing of the new prefixes will commence soon. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon Please be aware, this will be the final allocation made by IANA under the current framework and will trigger the final distribution of five /8 blocks, one to each RIR under the agreed "Global policy for the allocation of the remaining IPv4 address space". http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm After these final allocations, each RIR will continue to make allocations according to their own established policies. APNIC expects normal allocations to continue for a further three to six months. After this time, APNIC will continue to make small allocations from the last /8 block, guided by section 9.10 in "Policies for IPv4 address space management in the Asia Pacific region". This policy ensures that IPv4 address space is available for IPv6 transition. http://www.apnic.net/policy/add-manage-policy It is expected that these allocations will continue for at least another five years. APNIC reiterates that IPv6 is the only means available for the sustained ongoing growth of the Internet, and urges all members of the Internet industry to move quickly towards its deployment. Kind regards, _______________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 3646 South Brisbane, QLD 4101 Australia Fax: +61 7 3858 3199 6 Cordelia Street, South Brisbane, QLD http://www.apnic.net _______________________________________________________________________ * Sent by email to save paper. Print only if necessary. _______________________________________________ apops mailing list apops(a)apops.net http://mailman.apnic.net/mailman/listinfo/apops Website: www.apops.net ----- End forwarded message -----

1 0

Re: [ipv6-wg] 2010-06 is going to Last Call
by David Kessens 28 Jan '11

28 Jan '11

[ Courtesy copy sent to address policy and database working groups. Please follow up on the ipv6-wg list. ] All, We have not received any input so far whether you support draft policy 2010-06. While silence will in general be interpreted as consensus, we prefer to have a good number of statements of support as that will make it unequivocally clear that consensus was indeed reached. The last call period will end 2010-02-03 (Thursday, 3 February 2011). Please e-mail any final comments to ipv6-wg(a)ripe.net before then. Thanks, David & Shane --- On Thu, Jan 06, 2011 at 02:20:25PM +0100, Shane Kerr wrote: > Hello, > > [ Courtesy copy sent to address policy and database working groups. Please > follow up on the ipv6-wg list. ] > > The Review Phase for the RIPE policy proposal 2010-06 ended on > 2010-12-27 (Monday, 27 December 2010). > > You can see the policy proposal here: > > http://ripe.net/ripe/policies/proposals/2010-06.html > > There were some clarifications during the Review Phase, but nothing > indicating changes needed. > > David and I have decided that the proposal is ready for a Last Call. (As > co-author of the proposal, Marco has recused himself from any consensus > judgments.) > > The last call period is four weeks, so will end 2010-02-03 (Thursday, 3 > February 2011). Please e-mail any final comments to ipv6-wg(a)ripe.net > before then. > > Thanks, > > -- > Shane

26 35

Proposed Implementation Plan for Policy Proposal 2010-06 in the RIPE Database
by Denis Walker 26 Jan '11

26 Jan '11

[Apologies for duplicate emails] Dear Colleagues, To prepare for the possible acceptance of RIPE Policy Proposal 2010-06, "Registration Requirements for IPv6 End User Assignments", the Database Group at the RIPE NCC proposes the following implementation plan. We will implement a new attribute ("assignment-size:") in INET6NUM objects, add some business logic for its use and add a new value (AGGREGATED-BY-LIR) for the "status:" attribute of an INET6NUM object. Schema and syntax changes in INET6NUM objects: - New attribute "assignment-size:" - Syntax is numeric value > 0 - INET6NUM object will include "assignment-size:" as an optional, single attribute - "assignment-size:" will not be an inverse searchable attribute - New value for the "status:" attribute of an INET6NUM object will be AGGREGATED-BY-LIR Business rules: - "assignment-size:" is optional in INET6NUM objects but required if "status:" is AGGREGATED-BY-LIR - The value of "assignment-size:" must be greater than the prefix size of the INET6NUM object containing the attribute - Parent status of INET6NUM object with status AGGREGATED-BY-LIR can be: ALLOCATED-BY-RIR ALLOCATED-BY-LIR AGGREGATED-BY-LIR - If parent status is AGGREGATED-BY-LIR, grandparent status cannot be AGGREGATED-BY-LIR - If an object has the status AGGREGATED-BY-LIR, a more specific object can only have the status AGGREGATED-BY-LIR (subject to the aforementioned constraints) We will prepare implementation of this plan during the week commencing 31 January 2011. It will be deployed during the week commencing 7 February 2011 should RIPE Policy Proposal 2010-06 be formally approved. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

Future of the IPv6 CPE survey - Your Input Needed
by Mirjam Kuehne 24 Jan '11

24 Jan '11

[apologies for duplicates] Dear colleagues, Based on new information we received since the last publication, we updated the IPv6 CPE matrix: http://labs.ripe.net/Members/mirjam/ipv6-cpe-survey-updated-january-2011 In order to make this information more useful for a large user base, we are preparing a detailed survey to gather more structural feedback about the range of equipment that is currently in use. Not only would we like you to participate in this survey, but we also ask you for help in identifying the right survey questions. Please find a call for input on RIPE Labs: http://labs.ripe.net/Members/marco/future-of-the-ipv6-cpe-survey-more-input… Kind Regards, Mirjam Kuehne & Marco Hogewoning RIPE NCC

1 0