1 / 5

Concluding LDUP

Concluding LDUP. State of Various Deliverables. Architectural Model needs some alignment with other documents Information Model major rewrite needed we have volunteers URP fairly solid there were a couple of open issues pending resolution of other WG topics LCUP

sherry
Download Presentation

Concluding LDUP

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. Concluding LDUP

  2. State of Various Deliverables • Architectural Model • needs some alignment with other documents • Information Model • major rewrite needed • we have volunteers • URP • fairly solid • there were a couple of open issues pending resolution of other WG topics • LCUP • substantive issues uncovered during WG Last Call • editors are working on a revision • proposal from Kurt Z. on resolving the eventual convergence issue • Mandatory Replica Management • one remaining section to be completed • General Usage Profile • needs to be revised pending other document revisions • we have volunteers • its important, but its not Rocket Science • there’s no reason this document’s state should hold us back • Replication Protocol Specification • needs to be revised in parallel with changes to other documents • may be the most significant roadblock to concluding with a meaningful set of products • need to confirm if existing authors are willing to continue or if we need volunteers to take over

  3. Co-Chairs’ Proposal • Recommend LCUP as Standards Track to IESG after a WG Last Call that we exit with only minor issues • Pursue publication of all remaining documents as follows: • Informational: • Architectural Model • Experimental: • URP • Replication Protocol Specification • Information Model • Mandatory Replica Management • General Usage Profile

  4. Co-Chairs’ Proposal (cont.) • Include documentation of and a reference to using X.500 BAC within the context of LDAPv3 Replication in the following documents: • General Usage Profile • Architectural Model • Request that the Directory Directorate review the recent X.500-related I-Ds written by Kurt Z/Steven L • If those documents aren’t moved forward to become RFCs, we can still reference X.500 BAC in the X.500 Recommendations

  5. Co-Chairs’ Proposal (cont.) • We’ll discuss this proposal on the mailing list and let consensus decide if a charter revision is appropriate • If so, we should aim for completing all documents on or before June 2003 • “Completing” them means that they are ready to enter WG Last Call by that date

More Related