edugain policy comments

[Andreas Åkre Solberg <andreas.solberg AT uninett.no>]

* Dispute if one SP would like to be published to edugain through more than 
one federation... How is this sorted out? Example: Dreamspark, Elsevier.
* What about ProtectNetwork IdP. Allowed or not in eduGAIN?
* XML Extension to data protection profile: what about using entityattributes 
instead of a new namespace?
* Document mentions SAML 2.0 as if it was the only protocol supported, but I 
cannot find anywhere that SAML 2.0 is actually the required as a protocol, as 
a contrast to in example SAML 1.1, OpenID or InfoCard.
* Document mentions Identity Providers and Service Providers, and add 
requirements to these roles, but it does not mention other roles; such as 
attribute authority. 
* The document include alot of fancy experimental metadata extensions that 
AFAIK nobody has started using in their own federation (yet). Warning: this 
will delay things... [MDattribs] and [IdPDiscovery]

Kind regards,
Andreas

Attachment: smime.p7s
Description: S/MIME cryptographic signature