1 / 5

LDUP Architecture Draft: Key Updates on Naming Context and Replication Management

The latest LDUP architecture draft addresses key issues from the previous meeting, focusing on terminology changes and administrative alignment. Notably, "Naming Context" has been replaced with "Replication Context," emphasizing its association with replication administration without spanning Directory Service Agents (DSAs). The draft explores three models for policy enforcement across administrative areas, ensuring that all applicable policy information is available on servers hosting replicas. This development aims to improve clarity and functionality within LDUP's replication processes.

tory
Télécharger la présentation

LDUP Architecture Draft: Key Updates on Naming Context and Replication Management

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. LDUP Architecture Draft - Status

  2. General • Issues from last meeting have been addressed • Replication area versus other administrative areas such as ACL • Terminology problem w.r.t Naming Context • Submission of draft to LDUP hadn’t gone through • Ready for last call

  3. Terminology - Naming Context • What was referred to as “Naming Context” has been replaced with “Replication Context” • represents the area associated with replication administration • does not span DSAs • a directory area can only be in one “Replication Context” • Other choice was “Replication Area” • “Naming Context” definition referenced back to X.500

  4. Replication versus Other Administrative Domains • Problem: Administrative areas of other services might not be congruent with that of replication • E-g: A prescriptive ACL policy could span into a subordinate replication context • Requirement: For policies to be faithfully enforced by a server all “applicable” policy information must be “made available” within the server hosting a replica.

  5. Replication versus Other Administrative Domains • Resolution: Architecture draft identifies three potential models for accomplishing this: • The administration model for specific services (such as access controls) define mechanisms for representing and transmitting policy information (as if part of root of all associated “Replication Context”) • Directory administrators establish one or more explicit agreements to cover all applicable entries • A Replication Agreement implicitly includes all ancestral administrative entries (all sub-entries whose scope is inherited) • LDUP protocol could choose this mechanism if implementation assessed to be relatively less complex.

More Related