I'm sponsoring this fast-track for Milan Jurik. The requested release binding is patch/micro.
The timer is set for 10/01/2008. Note: the whole interface is Committed, n?e Evolving. Nico On Wed, Sep 24, 2008 at 02:33:59PM -0700, Nicolas Williams wrote: > > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > libldap:ber_printf() 'O' in format string > 1.2. Name of Document Author/Supplier: > Author: Milan Jurik > 1.3 Date of This Document: > 24 September, 2008 > 4. Technical Description > 1. Introduction > 1.1. Project/Component Working Name: > Support of 'O' in format string of libldap5:ber_printf() > > 1.2. Name of Document Author/Supplier: > Milan Jurik > 1.3. Date of This Document: > 09/18/08 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > Solaris PAC > 1.4.2. The ARC(s) you expect to review your project: > PSARC > 1.4.3. The Director/VP who is "Sponsoring" this project: > Chris.Armes at Sun.COM > 1.4.4. The name of your business unit: > Software > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: Joe.G at Sun.COM > 1.5.2. Responsible Engineer: Milan.Jurik at Sun.COM > > 2. Project Summary > 2.1. Project Description: > This project wants to add 'O' between characters for encoding BER > element octet string, to improve compatibility with OpenLDAP. > 2.2. Risks and Assumptions: > We assume no 3rd part software depending on not supported 'O' in > format string for ber_printf() > > 3. Business Summary > 3.1. Problem Area: > Samba is accessing the Active Directory using the LDAP page mode. > Handling the cookie between the subsequent queries > ber_scanf()/ber_prinf() calls are used to save/restore the cookie > payload in "ber element" and 'O' is needed for this. > We already support 'O' in ber_scanf() today. > > 3.4. Competitive Analysis: > OpenLDAP and libldap6 support this format > > 3.6. How will you know when you are done?: > Samba bundled with Solaris will support more than 1000 users > > 4. Technical Description: > 4.1. Details: > The fix is trivial and it's based on few lines of additional case in > switch for ber_printf(), where it will reuse libldap internal > function, > which is used for similar encodings already. The fix is in sync with > upstream. > > 4.2. Bug/RFE Number(s): > CR 6745345 > > 4.3. In Scope: > Modification of libldap ber_printf() > 4.4. Out of Scope: > Upgrade of libldap to the latest release because there are API changes > between > Solaris bundled libldap and upstream. > Changing Samba LDAP backend because OpenLDAP isn't integrated in > Solaris 10. > > 4.6. Doc Impact: > Manual page for ber_encode(3LDAP) will document new string format > character. > > 5. Reference Documents: > CR 6745345 - ber_printf() malforming the octet string refusing the "O" > format option > CR 6634710 - winbind fetches only first 1000 Active Directory users > PSARC/2000/362 - libldap > RFC 2696 - LDAP Control Extension for Simple Paged Results Manipulation > > 6. Resources and Schedule: > 6.1. Projected Availability: > November 2008 > > 6.2. Cost of Effort: > 2 weeks > > 6.4. Product Approval Committee requested information: > 6.4.1. Consolidation or Component Name: > ON > 6.4.3. Type of CPT Review and Approval expected: > BugFix > 6.4.7. Target RTI Date/Release: > November 2008 > > 6.5. ARC review type: > FastTrack > 6.6. ARC Exposure: > open > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > PSARC > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open >