However im not sure regarding the encapsulation and VLAN ID get set?

Sure, because for DHCP, there is no way to actually use any username/password. The question is what they mean by the "automated network authentication", whether that's just a marketing BS or there is some real meaning in it. Can't you test at a friend's before signing the contract?

The TalkTalk help pages do not appear to have caught up with their available broadband products, having only recently started selling FTTP services via Openreach connections - PTM encoding and VLAN 101 are only applicable to FTTC / VDSL2 connections.

Whilst PPPoE is often used to provide the customer WAN connection Openreach do permit both PPPoE and IPoE, the ISP can use either or both as they desire. As TalkTalk use IPoE for their Openreach FTTC / VDSL2 services it is likely they do the same for their FTTP connections, so you should just need to use DHCP.

As to the "automated network authentication" the Openreach information notes state "Where PPPoE is detected from the client router additional tags will be inserted into the upstream flow by the Intermediate Agent (IA) in the OLT, the IA tags will be removed by the OLT in the downstream direction." Also "Where DHCPv4 is detected, the OLT will insert an option 82 agent information field into the upstream flow (DHCP Discover), the option 82 field will be removed by the OLT in the downstream response (DHCP Offer)." Similarly "Where DHCPv6 is detected, the OLT will insert options 17, 18 and 37 into the upstream flow (DHCP Solicit), the option fields will be removed by the OLT in the downstream response (DHCP Offer)."

An ISP can request a specific agent ID to be inserted when they order a circuit for a customer and use this to identify the customer from the DHCP request or PPPoE discovery, rather than from a router MAC address or PPPoE credentials. This is not mandatory, for example Sky use IPoE but require the client router to include a specific DHCP option 61 (a.k.a. "MER") for authentication.

That does seem to make sense with TalkTalk documentation not being up to date as I did find a forum post on the talk talk community that says you dont need to do the VLAN tagging any more for FTTP. The official TalkTalk documentation for using your own router doesnt specify if those settings are for FTTP or FTTC but as you rightly say, based on that forum post I found it looks like its for FTTC. Their official documentation only states "Fibre" and doesnt specify what type of fibre.

https://community.talktalk.co.uk/t5/Gen ... -p/1502255

Sounds like I just need to remove the PPPoE interface from my Ether1 interface on the Mikrotik when I switch over and just setup DHCP client on the Ether1 interface then and I should be golden!?

Finally someone who knows what talk talk is :)

Just one more remark from my side, I don't know what speeds (bandwidth) you'll get from talk talk, but the 2011 may become a bottleneck as its CPU is quite weak. So offloading the VLAN tagging/untagging task to the switch chip may relieve it a bit. If everything works well the way I've suggested and you'll notice the router's CPU to struggle, come back for more information on how to set up such an offload.

The TalkTalk help pages do not appear to have caught up with their available broadband products, having only recently started selling FTTP services via Openreach connections - PTM encoding and VLAN 101 are only applicable to FTTC / VDSL2 connections.

Whilst PPPoE is often used to provide the customer WAN connection Openreach do permit both PPPoE and IPoE, the ISP can use either or both as they desire. As TalkTalk use IPoE for their Openreach FTTC / VDSL2 services it is likely they do the same for their FTTP connections, so you should just need to use DHCP.

As to the "automated network authentication" the Openreach information notes state "Where PPPoE is detected from the client router additional tags will be inserted into the upstream flow by the Intermediate Agent (IA) in the OLT, the IA tags will be removed by the OLT in the downstream direction." Also "Where DHCPv4 is detected, the OLT will insert an option 82 agent information field into the upstream flow (DHCP Discover), the option 82 field will be removed by the OLT in the downstream response (DHCP Offer)." Similarly "Where DHCPv6 is detected, the OLT will insert options 17, 18 and 37 into the upstream flow (DHCP Solicit), the option fields will be removed by the OLT in the downstream response (DHCP Offer)."

An ISP can request a specific agent ID to be inserted when they order a circuit for a customer and use this to identify the customer from the DHCP request or PPPoE discovery, rather than from a router MAC address or PPPoE credentials. This is not mandatory, for example Sky use IPoE but require the client router to include a specific DHCP option 61 (a.k.a. "MER") for authentication.

Thank you :)

That does seem to make sense with TalkTalk documentation not being up to date as I did find a forum post on the talk talk community that says you dont need to do the VLAN tagging any more for FTTP. The official TalkTalk documentation for using your own router doesnt specify if those settings are for FTTP or FTTC but as you rightly say, based on that forum post I found it looks like its for FTTC. Their official documentation only states "Fibre" and doesnt specify what type of fibre.

https://community.talktalk.co.uk/t5/Gen ... -p/1502255

Sounds like I just need to remove the PPPoE interface from my Ether1 interface on the Mikrotik when I switch over and just setup DHCP client on the Ether1 interface then and I should be golden!?