- address-policy-wg - mailman.ripe.net

RE: [address-policy-wg] PI for Not-DNS Anycast.
by Greg L. 13 Aug '07

13 Aug '07

I think that the PI /24 block should be assigned only to UDP related services as RFC suggests, however, I have yet to see the successful implementation of TCP data, state... replication in case one router withdraws BGP announcement of the /24 prefix. IPv4 anycast is a perfect way to distribute load and hopefully with lowest latency (not always true) for the following UDP related services: -syslog -dns -ddos mitigation The PI /24 anycast block should be assigned only when the applicant can demonstrate: at least 5 physically disperse locations (verification done by traceroute and checking the hop before the last hop in the traceroute). Traceroute's can be performed from open traceroute gateways (over the web etc - there are hundreds) or public ISP BGP route servers. to manage the server you will need a non anycast address(es), however, customers may keep this info secret if they do not want it to be public.... all anycast nodes must speak BGP to the upstream and in case the server goes down, the BGP router withdraws the BGP anycast /24 route Ps. If Ripe will allow anycast /24 PI allocation for syslog and ddos, and other UDP based services, then expect all free /24 blocks taken in a year or less for sure ;) My $0.02 cents... Greg http://www.LinuxAdmin.org

12 22

PI for Not-DNS Anycast.
by Andy Davidson 11 Aug '07

11 Aug '07

Hi, Can I get the community's thoughts on this, please .. I think we have a well defined policy on what to do when someone needs some PI in order to run an Anycasted DNS service. We set out a family of requirements based on geographic diversity, for instance, that clearly states what should be in place when a request for PI for DNS use is made. What if a company wants to try to deploy an anycasted production service for something which is not DNS ? It could be a proprietary protocol, or something standard like http. Is the community view that they should just deaggregate some of their PA - which I don't like the sound of - or apply for PI in the normal way, and pretend anycast isn't necessarily involved ? Many thanks Andy

13 25

2007-06: New Policy Proposal (Global Policy for the Allocationof the Remaining IPv4 Address Space)
by Alex Le Heux 03 Aug '07

03 Aug '07

PDP Number: 2007-06 Global Policy for the Allocation of the Remaining IPv4 Address Space Dear Colleagues, A new RIPE Policy has been proposed and is now available for discussion. This policy describes the process for the allocation of the remaining IPv4 space from IANA to the RIRs. When a minimum amount of available space is reached, an identical number of IPv4 allocation units (/8s) will be allocated from IANA to each RIR, replacing the current IPv4 allocation policy. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2007-06.html We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 27 August 2007. Best regards, Alex Le Heux RIPE NCC Policy Implementation Co-ordinator

8 11

New IPv4 blocks allocated to RIPE NCC
by Alex Le Heux 31 Jul '07

31 Jul '07

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv4 address ranges 94/8 and 95/8 from the IANA in July 2007. We will begin allocating from these ranges in the near future. The minimum allocation size from these two /8s has been set at /21. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Please also note that two "pilot" prefixes are being announced from each /8. These prefixes are: 95.192.0.0/16 95.255.248.0/21 They all originate in AS12654. The following pingable addresses are available in these blocks: 95.192.0.1 95.255.248.1 More information on this "pilot" activity is available in the document "De-Bogonising New Address Blocks", which can be found at: http://www.ripe.net/ripe/docs/ripe-351.html Best regards, Alex Le Heux RIPE NCC Policy Implementation Co-ordinator

1 0

LLUIS PONT GASAU/CAIXA01 es troba fora de l'oficina.
by lpont＠lacaixa.es 30 Jul '07

30 Jul '07

Estaré ausente de la oficina desde el 30/07/2007 y no volveré hasta el 15/08/2007. Estaré fora de l'oficina des del 30/07/2007 fins el 15/08/2007. Per temes urgents, contacteu si us plau amb l'Elisabet Moliner (934047037). Gràcies.

1 0

2006-02 Implementation: IPv6 Address Allocation and Assignment Policy
by Alex Le Heux 30 Jul '07

30 Jul '07

[Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that the policy proposed in 2006-02 "IPv6 Address Allocation and Assignment Policy" has been implemented. The RIPE NCC is now ready to accept requests for IPv6 address space under the new policy. The archived proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2006-02.html The updated "IPv6 Address Allocation and Assignment Policy" is available at: http://www.ripe.net/ripe/docs/ripe-412.html The following RIPE documents have also been updated to reflect this policy implementation: Supporting Notes for the IPv6 First Allocation Request Form http://ripe.net/ripe/docs/ripe-413.html IPv6 First Allocation Request Form http://ripe.net/ripe/docs/ripe-414.html Best regards, Alex Le Heux RIPE NCC Policy Implementation Co-ordinator

1 0

IPv6 PI policy implemented
by Ernest Byaruhanga (AfriNIC) 19 Jul '07

19 Jul '07

Dear Colleagues, Please note that AfriNC has implemented the following policy: "IPv6 Provider Independent (PI) Assignment for End-Sites" http://www.afrinic.net/docs/policies/afpol-v6200701.htm We have consequently as of today started making /48 PI assignments from the following block: 2001:43f8::/29 You may need to adjust any filters in place accordingly. For more information, please see: http://www.afrinic.net/Registration/afsup-ipv6pi-assignments.htm Regards, Ernest AfriNIC

6 10

2007-04 Last Call for Comments (IANA Policy for Allocation of ASN Blocks to RIRs)
by Filiz Yilmaz 17 Jul '07

17 Jul '07

PDP Number: 2007-04 IANA Policy for Allocation of ASN Blocks to RIRs Dear Colleagues The proposal described in 2007-04 is now at its Concluding Phase. This proposal is to have a global policy for the Regional Internet Registries (RIRs) to receive blocks of Autonomous System Numbers (ASNs) from the Internet Assigned Numbers Authority (IANA). You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2007-04.html Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 14 August 2007. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

2 1

2007-05 Discussion Period extended until 13 August 2007 (IPv6 ULA-Central)
by Filiz Yilmaz 16 Jul '07

16 Jul '07

PDP Number: 2007-05 IPv6 ULA-Central Dear Colleagues The Discussion Period for the proposal described in 2007-05 has been extended until 13 August 2007. This policy is intended to allow the assignment of IPv6 blocks within the so-called 'Centrally Assigned Unique Local IPv6 Unicast Addresses' to organisations or individuals requiring it. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2007-05.html We encourage you to review this policy proposal and send your comments to <address-policy(a)ripe.net>. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

6 6

2006-02 Proposal Accepted (IPv6 Address Allocation and Assignment Policy)
by Filiz Yilmaz 12 Jul '07

12 Jul '07

PDP Number: 2006-02 IPv6 Address Allocation and Assignment Policy Dear Colleagues, Consensus has been reached on the proposal described in 2006-02 and it is accepted by the RIPE community. This proposal is to change the IPv6 Initial Allocation criteria and the End Site definition in the "IPv6 Address Allocation and Assignment Policy". You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2006-02.html We will implement this new policy in approximately three weeks and notify you when it becomes effective. Thank you for your input. Regards, Filiz Yilmaz RIPE NCC Policy Development Officer

1 0