• Hide

      See description

      Show
      See description
    • Hide

      1. Specification does not provide a means for exchanging supported claim type encoding, occurs out of band
      2. Conforming parties are either IPs or RPs, any assertions they produce must conform to these specifications. We do not believe there is a need for a third conformance target.
      3. The TC believes the specification is consistent as written and no change is necessary.

      Show
      1. Specification does not provide a means for exchanging supported claim type encoding, occurs out of band 2. Conforming parties are either IPs or RPs, any assertions they produce must conform to these specifications. We do not believe there is a need for a third conformance target. 3. The TC believes the specification is consistent as written and no change is necessary.

      http://lists.oasis-open.org/archives/imi-comment/201006/msg00000.html

      1- Is there any way to notify the behavior of Relying Party w/r to what is accepted / not accepted, e.g.
      "Implementations MAY accept claim types encoded using the convention where..."
      How is the implementation supposed to communicate that it does not accept these (any error or warning to be generated?)

      2- Reading the conformance clause, it sounds like there are 3 conformance targets, not just 2:
      (a) Identity Provider implementation
      (b) Relying Party implementation
      (c) assertions
      Since the concept of consistent (or conforming) assertion is so important to
      "implementations" (a and b) as these are actually evaluated on their ability to handle such assertions
      shouldn't the conf clause also define what a conforming assertion is and more explicitly refer
      to the related normative text (which I feel are not just restricted to section 2.3.3. ?)

      3- Conformance Clause editorial:

      • " A Relying Party implementation conforms to this profile if it can accept assertions consistent with the
        normative text of Section 2.4. "
        Not only I believe: because the assertions it is supposed to accept are also to be consistent with 2.3.3.
        Might be resolved by addressing comment #2.
      • Given the very concise wording of the conformance clause, it might be helpful to
        clarify that being "consistent with the normative text" actually means that the implementation
        only needs to behave consistently with normative statements using MUST / MUST NOT
        (as readers might wonder what does it mean to be consistent with a SHOULD statement...).

            Assignee:
            Michael Jones (Inactive)
            Reporter:
            Marc Goodner (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: