Section 6.6 "Mutually-Authenticated TLS with Server Certificate Provided" and 6.4 "Server-Authenticated TLS with Server 
Certificate Provided" propose policies that allow for verification of the server through a certificate included in the 
policy. To document recognises the potential problems with this if the policy is acquired through unsecured means, but 
still allows them. I think that  the possibility of compromise seriously weakens these policies. I wonder if a chain of 
trust will be maintained with proper diligence by the creators of the consuming software? I can see that it is 
convenient and, when properly implemented, will be very useful, to transfer server certificates - but it does have the 
potential of causing security problems in poor implementations.