Google translated that for me. “I have no idea what you are trying to say.”
Read this: From Bridging and Switching Case Studies → Bridge VLAN Table → Background which is a glossary of terminology. Then look at Trunk/Access port setup (note this is really worth a read if you want to understand the vlan-filtering bridge. I think it is reasonably easy to follow as long as you understand how vlans work. It has some examples with a router as a separate entity and also an example where the bridge PVID is set 30 and ether3 given untagged access. The base bridge interface uses untagged on the “internal trunk” between the CPU and the Switch for the vlan that the bridge has its PVID set to. For example, in the following snippet untagged traffic from the bridge interface will be mapped to vlan 30 in the switch ASIC. From the switch ASIC, packets for vlan 30 could leave other bridge ports either untagged or tagged. In this example ether3 is an access port for vlan 30, and it will be “connected” to the base bridge1 interface (which has pvid 30) and is using untagged traffic between the switch ASIC and the CPU.
/interface bridge set [find name=bridge1] pvid=30
/interface bridge vlan set [find vlan-ids=30] untagged=bridge1,ether3
Just before the Diagram with bold title “Without Ingress Filtering” you will find the following:
I agree in this case it is probably being paranoid, and it is a belt and suspenders solution, since the bridge has no ip address on it anyway.
A downside of this is that it makes it easier to lock yourself out when switching to vlan-filtering.