2. /32 vs. /48 V6 prefix - routability aspect

From a routing table perspective there is no difference if the prefix is longer or shorter.

Well, for those so keen on preserving the last bit of memory, a _shorter_ prefix would actually be more efficient ;-)

When asking around which prefix length would have a good chance to ensure the goal of not beeing filtered I have felt consensus that a /32 has by far the best chances. However I'm considering if it wouldn't be best to declare a /32 microallocation block from which RIPE will assign /48 blocks.

Other than the goal of conservation (which we have beaten to death already) what is the benefit of doing that? Administrative ease to collate them from the database? I would be be more worried abut the potential of taking the whole block down in one big sweep by misconfiguration and/or leaking announcements. But maybe this isn't an issue in the world of anycast for "critical" DNS services. Otoh, for those who don't like the concept, it would make it easier to cut off connectivty to those segments by entering just 1 filter... Wilfried.