my ballot for GROUPS 6, 7, 8, 9

["Mishra, Prateek" <pmishra@netegrity.com>]

BALLOT
----------------------------------------------------------------------

All issue resolutions are mutually exclusive, so please choose one
option for each issue.

[UC-6-01:XMLProtocol] 

1. Change requirement for binding to SOAP to binding to XML Protocol.
(X) 2. Leave current binding to SOAP.
3. Remove mention of binding to either of these protocols.

[UC-7-01:Enveloping]

   1. Add proposed requirement [CR-7-01:Enveloping].
 (X)2. Do not add this proposed requirement.

Some care is needed on this issue. Are we proposing to build a general
packaging
infra-structure so SAML can "enclose" arbitrary XML payloads?? To me that
seems to
be far beyond the scope (and resources) of this group.

[UC-7-02:Enveloped]

   (X)1. Add proposed requirement [CR-7-02:Enveloped].
   2. Do not add this proposed requirement.

[UC-8-01:Intermediaries]

   (X)1. Add proposed requirement [CR-8-01:Intermediaries].
   2. Do not add this requirement to the document.

[UC-8-02:IntermediaryAdd]

   (X)1. Add the given use-case scenario to the document.
   2. Don't add this use-case scenario.

We need to keep any "addition" real simple; assertions should
be atomic but an intermediary can certainly add some new assertions.
These new assertions may "depend upon" existing assertions.

[UC-8-03:IntermediaryDelete]

   1. Add the given use-case scenario to the document.
   (X)2. Don't add this use-case scenario.

[UC-8-04:IntermediaryEdit]

   1. Add this use-case scenario to the document.
   (X)2. Don't add this use-case scenario.

[UC-8-05:AtomicAssertion]

   (X)1. Add the non-goal [CR-8-05:AtomicAssertion] to the document, and
      change use case scenarios to specify that intermediaries must
      treat assertions as atomic.
   2. Don't add this non-goal.

[UC-9-01:RuntimePrivacy]

   (X)1. Add the proposed non-goal [CR-9-01:RuntimePrivacy].
   2. Do not add this proposed non-goal.

[UC-9-02:PrivacyStatement]

   1. Add [CR-9-02-3-DisclosureMorgan] as a requirement.
   2. Add [CR-9-02-2-DisclosureBlakley] as a requirement.
   (X)3. Add [CR-9-02-4-DisclosureMishra] as a requirement.
   4. Add none of these as requirements.





------
Attachments are virus free!

This message has been scanned for viruses at the originating end by
Nemx Anti-Virus for MS Exchange Server/IMC
	http://www.nemx.com/products/antivirus

  

BALLOT
----------------------------------------------------------------------

All issue resolutions are mutually exclusive, so please choose one
option for each issue.

[UC-6-01:XMLProtocol] 

1. Change requirement for binding to SOAP to binding to XML Protocol.
(X) 2. Leave current binding to SOAP.
3. Remove mention of binding to either of these protocols.

[UC-7-01:Enveloping]

   1. Add proposed requirement [CR-7-01:Enveloping].
 (X)2. Do not add this proposed requirement.

Some care is needed on this issue. Are we proposing to build a general packaging
infra-structure so SAML can "enclose" arbitrary XML payloads?? To me that seems to
be far beyond the scope (and resources) of this group.

[UC-7-02:Enveloped]

   (X)1. Add proposed requirement [CR-7-02:Enveloped].
   2. Do not add this proposed requirement.

[UC-8-01:Intermediaries]

   (X)1. Add proposed requirement [CR-8-01:Intermediaries].
   2. Do not add this requirement to the document.

[UC-8-02:IntermediaryAdd]

   (X)1. Add the given use-case scenario to the document.
   2. Don't add this use-case scenario.

We need to keep any "addition" real simple; assertions should
be atomice but an intermediary can certainly add some new assertions.
These new assertions may "depend upon" existing assertions.

[UC-8-03:IntermediaryDelete]

   1. Add the given use-case scenario to the document.
   (X)2. Don't add this use-case scenario.

[UC-8-04:IntermediaryEdit]

   1. Add this use-case scenario to the document.
   (X)2. Don't add this use-case scenario.

[UC-8-05:AtomicAssertion]

   (X)1. Add the non-goal [CR-8-05:AtomicAssertion] to the document, and
      change use case scenarios to specify that intermediaries must
      treat assertions as atomic.
   2. Don't add this non-goal.

[UC-9-01:RuntimePrivacy]

   (X)1. Add the proposed non-goal [CR-9-01:RuntimePrivacy].
   2. Do not add this proposed non-goal.

[UC-9-02:PrivacyStatement]

   1. Add [CR-9-02-3-DisclosureMorgan] as a requirement.
   2. Add [CR-9-02-2-DisclosureBlakley] as a requirement.
   (X)3. Add [CR-9-02-4-DisclosureMishra] as a requirement.
   4. Add none of these as requirements.