Re: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?

[Alexandre Petrescu <[e-mail]>]

'IPv4aaS' in the subject line and 'IPv6-only' in the original vendor's 
question... hmmm... please clarify what is meant?

These two things are very different.

If the vendor wants to do something about providing only IPv6 to 
in-residence network is a different intention than wanting to do 
something about providing IPv4 as a service on that IPv6.

Le 24/11/2021 à 03:25, Lorenzo Colitti a écrit :
> Hi all,
> 
> Is there any data on what IPv4aaS transition mechanisms are deployed by 
> ISPs today? I was approached by a router vendor asking me "how they 
> should provide IPv6-only"

One of the feedback should be to advise the ISP to run a DHCPv6-PD 
server in the CPE.

My ISP CPE still does IPv6 static routes in the CPE towards the 
in-residence subnets, which is difficult to type each time.

Alex


  and I was looking for data on which mechanisms
> are most common.
> 
> Official IETF guidance in RFC 8585 and 8026 is "do all of them and let 
> ISPs decide, have a nice day", but that's not very helpful to a 
> development team with finite engineering resources and low margins. In 
> particular, it's not helpful to vendors of routers that are updatable 
> and that can thus credibly claim that they can deliver other mechanisms 
> via software update. Those vendors could reasonably argue that it's 
> better for everyone if they launch the most common mechanism(s) first, 
> and then deliver the others in software updates.
> 
> It seems like reasonable implementation guidance would be to request 
> OPTION_S46_PRIORITY and parse it, but only initially implement one or 
> two of the mechanisms and leave the others for a future release. If a 
> router did this, what mechanisms should it implement first? MAP-E?
> 
> Cheers,
> Lorenzo
> 
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops
>