1 / 8

DataGrid WP 6/CA CA Acceptance/Feature Matrices

DataGrid WP 6/CA CA Acceptance/Feature Matrices. Trinity College Dublin (TCD) Brian Coghlan. P aris MAR -2002. Proposed Syntax Changes. For Web Server & LDAP Server cert & CRL : publication_frequency  publication_frequency [days] publication_latency [days]

siran
Download Presentation

DataGrid WP 6/CA CA Acceptance/Feature Matrices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DataGrid WP6/CACA Acceptance/Feature Matrices Trinity College Dublin (TCD) Brian Coghlan ParisMAR-2002

  2. Proposed Syntax Changes • For Web Server & LDAP Server cert & CRL : • publication_frequency •  publication_frequency [days] • publication_latency [days] • publication_validity [days]

  3. Proposed Syntax Changes • For cert_issuance : • identity_check = personal_contact | email | phone •  <expression> • where : operators = AND, OR • precedence = (), AND, OR • elements = personal_contact | email | phone • | contact_with_superior • | public_directory_check

  4. Scaling • Let us consider: • Scaling of Acceptance/Feature Matrix functionality • Let us NOT consider: • Scaling of whole grid authentication scheme

  5. Functionality • The Acceptance Matrix will scale if : • inspection is done by machines not people • e.g. by evaluating CA feature matrix according to rule set • not done yet • scope is deliberately limited, e.g. to VOs • not done yet • The presentation software will scale if : • it can be run from memory • not done yet, but is designed as just one source file • it automatically adapts to addition/removal of CAs • already done

  6. Functionality • The matrix admin will scale if : • each CA manages their own matrix info on site, • with remote access by the software • not done yet • maybe should not be until methodology stabilizes • a CA automatically gets out of the blacklist when • they fix the problem • as soon as next remote access to their matrix info • not done yet

  7. Future Functionality • Utilization by programs might be accommodated by : • use of RGMA/MDS/LDAP, both for remote matrix info • access and for presenting matrix results • Exceptional incidents might be accommodated by : • continuing to support the current manual inspection, • both for CAs and for VOs • Fault-tolerance might be accommodated by: • using RGMA/MDS/LDAP replication [when available] • Notification of changes to a CA might be accommodated by: • email [initially] • notification by information system [when available]

  8. Acceptance/Feature Matrices THE END

More Related