Ipv6 help

JORDI PALET MARTINEZ jordi.palet at consulintel.es
Sun Aug 30 07:19:28 UTC 2020


In many situations it will make sense to keep the CPE provided by the ISP in a configuration equivalent to a "bridge" (I know is not a bridge, I'm trying to use a single word to describe it), so it runs things like the NAT for IPv4 and the CLAT for IPv6, even DHCP, or RA, etc. It all depends on what you have behind. Many customers will just have one or two routers acting just as APs in a single bridged domain, others may have different subnets, etc.

This keeps the customer happy if they need to have a better WiFi, or whatever.

If you have just a dozen of deployments per month, I think the choice to buy a good Chinese hardware that already comes with OpenWRT, or your preferred retail CPE that allows to be reflashed with OpenWRT, is handy. That system will work for most of the customers, and if some customer want a "bigger" system, just provide the low cost CPE as a "bridge" to its real network.
 
 

El 30/8/20 3:05, "NANOG en nombre de Brandon Martin" <nanog-bounces+jordi.palet=consulintel.es at nanog.org en nombre de lists.nanog at monmotha.net> escribió:

    On 8/26/20 12:48 PM, JORDI PALET MARTINEZ via NANOG wrote:
    > I work and I'm in touch with many CPE vendors since long time ago ... many are on the way (I can remember about 12 on top of my head right now, but because contracts, can't name them). It takes time. However, in many cases, they just do for specific customers or specific models. I know other people that contacted the same vendors and they told them "we could do it for the model you use as well". In some cases, they require a minimum volume per year (less than what you could expect. I've seen cases that start with just 500 units per month).
    > 
    > But this only works if you contact them. The CPE vendors business model seems to be very "ISP" direct. I think the retail marked models, unfortunately, will take a bit more time.
    > 
    > A hint about some vendors: You may take a look at the co-authors in the RFC.

    The whole point here is not that some vendors can support these features 
    in a semi-custom firmware image that's specific to a particular ISP 
    deployment - I know that's a possibility and have vendors willing to 
    work with me on a much smaller volume than even what you've indicated - 
    but rather what about customers who want to "upgrade" their router or, 
    for whatever reason (and there are some very valid ones) want to provide 
    their own.

    Right now, it's essentially impossible for them to walk into a local 
    retailer and walk out with a model that they know for sure will work 
    with my network if I'm requiring e.g. 464XLAT for basic functionality. 
    Even if they buy online and dive fairly deep into model documentation, 
    it is still hard to come up with a model that they know will work, and 
    the lack of documentation will limit their choice of models 
    unnecessarily (i.e. there are probably some options that support the 
    necessary functionality but don't advertise it in the slightest).

    If someone wants me to provide them with a router, then of course I'll 
    hand them one that I know works on my network.  That's easy since I have 
    control over the selection of it (and have presumably done some testing) 
    even if I don't have my own provider-customized firmware.

    I'll point out that 500 new services (taking a new router) per month is 
    not a particularly small provider.  It's not large, no, but it's also a 
    lot bigger than many deployments are at least when they're new, and 
    these are questions you have to essentially answer "up front" in many cases.
    -- 
    Brandon Martin



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.






More information about the NANOG mailing list