A Multinational Enterprise and Its Extranet198 Red Hat Directory Server Deployment Guide • May 2005• Many of the data elements need to accommodate data values of severaldifferent languages and charactersets.The deployment team also determines the following about the data design of theextranet:• Suppliers will need to log in to example.com’s directory to manage theircontracts with example.com. Suppliers will depend upon data elements usedfor authentication, such as name and user password.• example.com’s partners will use the directory as a way to look up the emailaddresses and phone number of people in the partner network.Schema Designexample.com builds upon its original schema design by adding schema elementsto support the extranet. example.com adds two new objects, theexampleSupplier object class and the examplePartner object class.The exampleSupplier object class allows one attribute, the exampleSupplierIDattribute. This attribute contains the unique ID assigned by example.comInternational to each auto parts supplier with which it works.The examplePartner object class allows one attribute, the examplePartnerIDattribute. This attribute contains the unique ID assigned by example.comInternational to each trade partner.For information about customizing the default directory schema, refer to“Customizing the Schema,” on page 50.Directory Tree Designexample.com creates a directory tree as follows:• The directory tree is rooted in the suffix dc=com. Under this suffix,example.com creates two branches. One branch, dc=exampleCorp,dc=com,contains data internal to example.com International. The other branch,dc=exampleNet,dc=com, contains data for the extranet.• The directory tree for the intranet (under dc=exampleCorp,dc=com) has threemain branches, each corresponding to one of the regions where example.comhas offices. These branches are identified using the l(locality) attribute.
