Summarize using RFC1918

Hi all

A couple of months ago I was tasked with migrating our 3 US offices + DC from an existing l2vpn (full mesh with our UK DCs + EU sites) to an isolated l3vpn with a new provider, we will be peering with managed CPEs using EIGRP. The new WAN environment will include the US sites + the UK DCs, with the UK acting as a transit between the US and the rest of our environment. The UK site is our HQ.

All of our sites will be advertising /16 summary routes 10.x and the US DC will advertise a default route for the US sites + a couple of /24 DMZ subnets 192.168.x.

This project is taking a long time to get going due to things outside of my control so i have had a long time to ponder over my design and now having doubts! My plan was to summarize RFC1918 on the UK interfaces towards the new l3vpn. This means the routing tables in the US sites should only have:

3 x RFC1918 routes, 3 x /16 from the other US offices, 2 x /24 DMZ subnet from US DC, Any number of public static routes advertised from elsewhere and 1 x default route from the US DC.

I labbed this up in GNS3 and it seems to be sound but i still feel like i may be missing something. Can't seem to find any route summarization examples using RFC 1918 but my only other option is to just allow all global sunbets to be advertised and summarize what i can.

Any one done something similar?