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-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Previous message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Next message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Baeza (Red y Sistemas TVT)
d.baeza at tvt-datos.es
Mon Oct 13 10:02:21 CEST 2014
Hi all! El 11/10/2014 16:56, Jan Ingvoldstad escribió: > On Sat, Oct 11, 2014 at 10:45 AM, Roger Jørgensen <rogerj at gmail.com > On Fri, Oct 10, 2014 at 9:57 PM, Erik Bais <ebais at a2b-internet.com > > Hi Gert, > > > > Any windows dressing in the policy should be avoided .. If people want to implement v6, they will .. If people need to request v6 in order to obtain v6, they will.. But it doesn't mean they will deploy ... > > > > Based on that, I would say, strike the v6 requirement in order to request the last v4 /22 .. > > Added to that, having people that deployed v6 based on PI having to turn in their space as it doesn't fit the requirement feels like a slap in the face and a waste of effort ... I would vote to have that fixed ... > > agree, let's just drop the v6 and give out the last /22 to those > that want it. > > > I could probably write a couple of thousands of words about this, but > I'll be brief: > > Yes, please let's just drop the v6 requirement. I totally disagree. In other hand, I'll make harder the v6 requeriment to get the /22. How? Making the policy not only "to have" the v6 alloc, I'll require also having it with route6 and published in BGP. RIPEstat is a good tool to check if the v6 is publicly visible. Cheers, -- Daniel Baeza
- Previous message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Next message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]