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/[email protected]/
[address-policy-wg] 2014-12 Last Call for Comments (Allow IPv6 Transfers)
- Previous message (by thread): [address-policy-wg] 2014-12 Last Call for Comments (Allow IPv6 Transfers)
- Next message (by thread): [address-policy-wg] 2014-12 Last Call for Comments (Allow IPv6 Transfers)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erik Bais
ebais at a2b-internet.com
Thu Feb 12 21:38:17 CET 2015
Hi Gert, I missed that one as well, so I'll take a partial (bl/sh)ame on this ... > Questions / Discussion items: > Nick Hilliard, request to clarify the wording on the minimum block > size requirements for IPv6 PI at that time, and a question about > the 24-month cooling period On the minimum block size requirement for IPv6 PI ... Nick is stating that with the current wording the intent is ambiguous. The specific line is : >Provider Independent (PI) address space may only be re-assigned in accordance with the RIPE Document, “Contractual Requirements for Provider Independent Resource Holders in the > RIPE NCC Service Region”. The block that is to be re-assigned must not be smaller than the minimum assignment block size at the time of re-assignment. It is clear that we are talking about IPv6 PI space here.. that the contract needs to be in place, that we talk about a re-assignment (read - PI space assignment..) and that the minimum assignment size needs to be matched. It is clear that it is not about an allocation (IPv6 PA space) or do I miss something here which is a detail that a native speaker would see and I'm missing .. ?? If we look at the practical side here ... We are talking about PI IPv6 .. where most of those assignments will be a /48 ... Those assignments can't be split up into smaller prefixes ... There are roughly 60 IPv6 PI assignments that I could find which are not a /48 ... And because those need to submit lots of documentation to have received that prefix. I think it is unlikely that they will split their precious.. If a company (End-User) has an IPv6 PI assignment, having third parties (as you may have with PA IPv6) using it, is against the use-case for IPv6 PI space... And as it is still possible to get IPv6 PI space (unlike with IPv4 PI space), there is no requirement to split a PI IPv6 prefix, unless you are breaking up a company / infrastructure. It is my expectation that the majority of the v6 PI transfers will be on complete prefix transfers and not partials or splits... Specifically companies merging together, reorganizing. Having said that .. that also explains the not having the 24 month 'hoarding' cool down period... There is little to hoard ... I don't see a commercial market .. as any LIR will get a larger prefix than anyone would get via a IPv6 PI transfer ... without documentation ... And anyone can request a /48 PI IPv6 if they like, without documentation ... And every PI assignment will cost you a yearly maintenance fee as a sponsoring LIR of at least 50 euro ... I hope that I've addressed the points ( a bit late I admit..) but addressed Nick his points anyway. Regards, Erik Bais
- Previous message (by thread): [address-policy-wg] 2014-12 Last Call for Comments (Allow IPv6 Transfers)
- Next message (by thread): [address-policy-wg] 2014-12 Last Call for Comments (Allow IPv6 Transfers)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]