Nish:
@MikeHales or @morat or someone else, can anyone please validate if I can use my current firewall and just do the vlan tagging on it and not use the HG659? I know its somewhat been eluded that the vlan tarecgging will happen but I need to validate this before I make the jump to it.
Swapping out the HG659 isn't a supported configuration, but we're (opps, did I just out myself) not doing anything to actively police or require its presence.
So providing you're up to configuring .1q on your router's upstream interface, and getting it to DHCP its WAN-facing IP address, we'll neither know nor care if you swap out the HG659 (but if you screw up and break your connection, our response is likely to be 'plug in the router we gave you, k?').
The only caveat would be that it's entirely possible that products will be rolled out to the network that assume the presence of the HG659 (one of the major design drivers in the current rollout has been reducing the differences between the HFC and UFB networks from a platforms and processes point of view, so we can offer a more uniform product suite (as well as reduce the information load on our front line staff) so I wouldn't be surprised to see us making the most of that (note: I'm not a products guy, so I'm just specularing there)). If that were the case, you obviously wouldn't be able to make use of said products without the expected RGW on your connection.