SNMP is better for looking at nodes in one's own domain. Pavlin says, yes, we do want to have access to other domains, especially for debugging. This access can be turned off when desired. Maybe these messages should be in a separate draft as a feature to use only during debugging stage. This doesn't complicate AAP because it needs this info anyway.
Third solution is to run at least one diskful MASC node, maybe in a non-router.
There is a problem with this because there could be a conflict between what one learns from AAP and from MASC peers. Those need to be consistent. The info is signed from MASC to AAP, and the same info is returned, so it should not get messed up unless one lies to oneself. Not strongly in favor of one solution or other, but we should figure out one way to do it. Having two different implementations may still work, but there is the possibility of confusion about the architecture.