Re: [v6ops] LISP support for draft-ietf-v6ops-rfc7084-bis-00

[Philip Homburg <[e-mail]>]

>Because this customer behavior is so unlikely, it's irrelevant whether or not 
>a retail router supports 6rd. 
>In fact, any transition technology that does not ship enabled, simultaneous wi
>th dual stack, is irrelevant in retail devices.

I have a strong preference for dual stack, so in that sense I don't
particularly care about transtition mechanisms, but that said...

Since for ever, I have been able to buy retail routers that support an insane
number of ways to configure ADSL or VDSL. For ADSL you need at least
VPI and VCI, and encapsulation mode. For VDSL you often need to configure
the VLAN number and whether to use PPPoE or not. In addition you may have
to configure user name and password for PPP variations.

Surprisingly, despite the fact that consumers are utterly incapable of 
configuring those parameters, these routers can be easily bought retail.

Some vendors are cheating though. Some of them spell out the parameters for
different ISPs in the manual. Others go even further and have a configuration
wizzard where you just select your ISP.

Note that in some cases, the ISP supplied device doesn't do what you want.
Then it is good if there are retail devices that support your ISP's choice 
of protocols. So for me it is weird to say that just because all relevant
ISPs provide a 6rd capable router, there is no need for that protocol in a
retail device. Retail devices should support protocols popular in the
region where the device is sold. 

Here, one ISP refuses to provide bridge mode in the cable modem when IPv6
is enabled because not all (or too few) retail routers support the
transitioning technology they are using.