IEF-RA 1.0 FTF Avatar
  1. OMG Issue

IEFRA_ — Amend IEFRA-24 Proposal

  • Key: IEFRA_-149
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Michael Abramson)
  • Summary:

    Suggest different wording (affected text shown under the numbered list):
    1- remove "to" between "metadata" and "authorizes".
    2 - add a period after the closing parenthesis just before "This Reference Arch..."
    3 - "updated to reflect change" should be "updated to reflect changes"
    4 - "are representatives of the interactions between IEF components" should be "representative of interactions between IEF components"
    5 - "adjudication" should be "adjudications".
    "...metadata to authorizes receipt or release, or filtering specific non-complient elements) This Reference Architecture will be updated to reflect change imposed by the individual component specifications for the PEP, PDP, PAP, and PPS. The Sequence Diagrams in this Annex are representatives of the interactions between IEF components, and do not represent all possible interactions or adjudication of user security policy..."

  • Reported: IEF-RA 1.0b1 — Wed, 6 Mar 2019 02:39 GMT
  • Disposition: Deferred — IEF-RA 1.0
  • Disposition Summary:

    Correction for IEFRA-149

    Suggest different wording (affected text shown under the numbered list):
    1- remove "to" between "metadata" and "authorizes".
    2 - add a period after the closing parenthesis just before "This Reference Arch..."
    3 - "updated to reflect change" should be "updated to reflect changes"
    4 - "are representatives of the interactions between IEF components" should be "representative of interactions between IEF components"
    5 - "adjudication" should be "adjudications".
    "...metadata to authorizes receipt or release, or filtering specific non-complient elements) This Reference Architecture will be updated to reflect change imposed by the individual component specifications for the PEP, PDP, PAP, and PPS. The Sequence Diagrams in this Annex are representatives of the interactions between IEF components, and do not represent all possible interactions or adjudication of user security policy..."

  • Updated: Tue, 8 Oct 2019 17:56 GMT