This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
- Previous message (by thread): [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
- Next message (by thread): [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rueegg, Daniel
drueegg at emea.att.com
Tue Apr 14 17:22:36 CEST 2009
Hi Remco, I'm not sure where you see that a second AS would allow a LIR to get a second /32. I'm happy to reword the Policy Text but I think it already specifies the rule: "...separate AS number and a unique routing policy..." The unique routing policy implies that the two AS will have different peering relations so are operated as two different networks. I'm happy to add a sentence about peering too it that makes it clear. I agree to the comment Marco wrote. It would make sense to specify a time-line by when a low used /32 has to be returned after AS have merged together. Dani -----Original Message----- From: address-policy-wg-admin at ripe.net [mailto:address-policy-wg-admin at ripe.net] On Behalf Of Remco van Mook Sent: Tuesday, April 14, 2009 5:01 PM To: address-policy-wg at ripe.net Subject: RE: [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs) Dear all, While I sympathise with the idea, I don't support the proposal as-is today. As I read it, it allows a LIR to avoid any requirements for fillrates of address space as long as they've got an extra AS, essentially making the number of ASes a metric for the amount of address space one can get without questions. This puts a lot of extra weight on the decision of assigning an extra AS to a LIR and that should be a fully separate discussion. If we can somehow fix this unintended interdependency I'll gladly review my opinion. Kind regards, Remco van Mook -----Original Message----- From: address-policy-wg-admin at ripe.net [mailto:address-policy-wg-admin at ripe.net] On Behalf Of Ingrid Wijte Sent: dinsdag 14 april 2009 14:58 To: policy-announce at ripe.net Cc: address-policy-wg at ripe.net Subject: [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs) PDP Number: 2009-05 Multiple IPv6 /32 Allocations for LIRs 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-05.html We encourage you to review this proposal and send your comments to <address-policy-wg at ripe.net> before 12 May 2009. Regards Ingrid Wijte Assistant Policy Development Officer 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.
- Previous message (by thread): [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
- Next message (by thread): [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]