This may not be necessary for v1.02. See related issue.

Use Mantis issue to validate that all profile /conformance units have correct verbage wih regard to related mantis issue

All items reviewed - the following issue need discussion:

If a Nano embedded profile is to support username/passoword - currently it will require that a certificate is provided (user name password is part of Core facet). If this is not possible them maybe the solution is to remove username/password from core - instead add it to Micro embedded which would cause this profile to require a certificate.(not a cyrto-library since only need to decode password - no other functionality is needed).

Transports - all indicate support for either ws secure conversation or UA secure converastion - not sure how testing the transport can be accomplished if only none included since then no security is provided - Maybe alternate transport needs to be defined - with no security or as a minimum additional text needs to be added to these release profiles indicating that they must be coupled with a security policy to actually define the security provided by the transport.

Reviewed all ConformanceUnits and found no required changes

Agreed in UA F2F.

Agreed in UA F2F.

Agreed in UA F2F.