Version upgrade etc. use cases

["Hallam-Baker, Phillip" <pbaker@verisign.com>]

I think these questions are linked because if we have done the job right in
1.0 there will be no SAML 1.0 schema, only extension schemas that build on
the 1.0 schema.


Versioning

Version 1.0 client attempts to access version 1.0 service
	Desired behavior - it works

Version 1.0 client attempts to access version 1.x service
	Desired behavior - service downgrades to 1.0

Version 1.x client attempts to access version 1.0 service
	Desired behavior - client accepts 1.0 response

Version 2.x client attempts to access version 1.y service
	Desired behavior MAY be referal to 2.0 service, 
		MAY be advice to downgrade request, 
		MAY be 1.y response [Group MUST choose NOW]

Version 1.y client attempts to access version 2.x service
	Desired behavior MAY be referal to 2.0 service, 
		MAY be advice to downgrade request, 
		MAY be 1.y response [2.x group SHOULD choose IN FUTURE]


Client capability negotiation

Client requests attributes from service
	Client supports attribute schemas P,Q,R
	Server supports attribute schemas Q,R,S

	Desired behavior 
		Server responds with schema Q or R.

Client makes request for assertion defined in extended schema X
	Service supports schema X
	Desired behavior - it works

Client makes request for assertion defined in extended schema X
	Service does not support schema X
	Desired behavior - error response


		Phill

Phillip Hallam-Baker FBCS C.Eng.
Principal Scientist
VeriSign Inc.
pbaker@verisign.com
781 245 6996 x227

Phillip Hallam-Baker (E-mail).vcf