...
- AL3_ID_VRC#030 Record Retention concern posted by Mark Coderre
- (Richard) agree with Mark's suggestion; note that we are talking about records of the verification and revocation process
- (Myisha) the proposed language may not be specific enough for auditors? (Richard) yes; (Myisha) does this drop us out of alignment with the FICAM requirements? (Richard) no, because if they are going for FICAM compliance, they are invoking those obligations on their own; (Scott) if they claims they are making satisfy the jurisdictional requirements of their area, this works;
- (Myisha) blanket Kantara approval without looking at a profile is possibly problematic; (Richard) if we go down that path, we'll have to be explicit for every possible legal requirement; maybe we shoudl require if they are claiming any additional considerations or requirements, they have to include this in their public statements; (Joni) it is already public, for when we make an approval, we make explict what additional documents or criteria were applied; why would this just not go in the additional FICAM criteria by Kantara to make sure this is applied?
- (Colin) this should go in an updated requirements document, since this came in after the 45-day review period; (Richard) do we have to park any further changes in any part of this revision or are we empowered/willing to accept injection of further changes at this late stage in to present updates; (Joni) should the group decide to create a set of changes after comment period, they do not have to go back for another full review by membership, if there are IP considerations however introduced by the changes, that is where we should be cautious; (Myisha) given the relationship between the ARB and the IAWG, we can expect more regular comments outside of the official Comment Period and it is good to separate out the 45-day comments and the ARB comments for now, but we need to consider how we're going to handle this going forward when it may be a significant change via the ARB; (Richard) reasonable to defer formal proposition of this change though since we've discussed it this much we should finish the text; consensus was to defer incorporation of this comment until the next iteration of the document set as it was injected in to the process after the 45 day review period
- What is the method to track the outside issues coming in for comments beyond formal Disposition of Comments? HF to start tracking, will require an index to track the version of the doc that is being
- (Myisha) likes the language that Mark included, that this would be added to additional criteria document and doc would be changed to Profile and Additional Criteria doc; Richard suggests adding "or by any form of other binding agreement or obligation"
- Kantara IAF-1400 Service Assessment Criteria (Kantara IAF-1400 SAC v2-1)
- Kantara IAF-1300 Assurance Assessment Scheme (Kantara IAF-1300 AAS v2-1)
- Kantara IAF-1800 Rules for Assurance Assessments (Kantara IAF-1800 RAA v0-1)
- Kantara IAF-1100 Glossary (Kantara IAF-1100-Glossary v2.1
...