2009-07 New Policy Proposal (Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries)
PDP Number: 2009-07 Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries Dear Colleagues A new RIPE Policy Proposal has been made and is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2009-07.html We encourage you to review this proposal and send your comments to <address-policy-wg@ripe.net> before 24 June 2009. Regards Filiz Yilmaz Policy Development Manager RIPE NCC
On Wed, May 27, 2009 at 04:48:13PM +0200, Filiz Yilmaz wrote:
PDP Number: 2009-07 Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries
Dear Colleagues
A new RIPE Policy Proposal has been made and is now available for discussion.
You can find the full proposal at:
http://www.ripe.net/ripe/policies/proposals/2009-07.html
We encourage you to review this proposal and send your comments to <address-policy-wg@ripe.net> before 24 June 2009.
I fully support this proposal. Piotr Strzyżewski -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
On 27/05/2009 15:48, Filiz Yilmaz wrote:
Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries
No objection to this proposal. Nick -- Network Ability Ltd. | Head of Operations | Tel: +353 1 6169698 3 Westland Square | INEX - Internet Neutral | Fax: +353 1 6041981 Dublin 2, Ireland | Exchange Association | Email: nick@inex.ie
Before this gets lost in the loud and off-topic discussion about 2009-06: I fully support this proposal in the sense that it improves on the current situation - I'm afraid however that we'll be looking at a new proposal somewhere next year extending the date even further out. We could lose a lot of time discussing this date (or any other arbitrary deadline other than actually running out) but I'd rather see this proposal accepted as-is ASAP. Best, Remco
-----Original Message----- From: address-policy-wg-admin@ripe.net [mailto:address-policy-wg-admin@ripe.net] On Behalf Of Filiz Yilmaz Sent: woensdag 27 mei 2009 16:48 To: policy-announce@ripe.net Cc: address-policy-wg@ripe.net Subject: [address-policy-wg] 2009-07 New Policy Proposal (Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries)
PDP Number: 2009-07 Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries
Dear Colleagues
A new RIPE Policy Proposal has been made and is now available for discussion.
You can find the full proposal at:
http://www.ripe.net/ripe/policies/proposals/2009-07.html
We encourage you to review this proposal and send your comments to <address-policy-wg@ripe.net> before 24 June 2009.
Regards
Filiz Yilmaz Policy Development Manager RIPE NCC
This email is from Equinix Europe Limited or one of its associated/subsidiary companies. This email, and any files transmitted with it, contains information which is confidential, may be legally privileged and is solely for the use of the intended recipient. If you have received this email in error, please notify the sender and delete this email immediately. Equinix Europe Limited. Registered Office: Quadrant House, Floor 6, 17 Thomas More Street, Thomas More Square, London E1W 1YW. Registered in England and Wales No. 6293383.
On 27 May 2009, at 15:48, Filiz Yilmaz wrote:
Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries [...] http://www.ripe.net/ripe/policies/proposals/2009-07.html
Hi, Filiz, everyone -- I support this proposal. As somebody involved with spreading information about the operational problems that were discovered with several asn32 implementations, please could I make a few comments : - The time-extension should be to help mitigate effects of the first generation asn32 bgp code, not buy a solution to inertia. ASN32 is now broadly safe to plan and implement, so understand the issues that were uncovered last year and then please do roll out a safe implementation on your networks ! - Do we need an additional RIPE policy alongside this advisory, extending the asn16 space in the ripe region by some months or a year ? Kind regards, Andy Davidson
participants (5)
-
Andy Davidson
-
Filiz Yilmaz
-
Nick Hilliard
-
Piotr Strzyzewski
-
Remco van Mook