[
https://issues.apache.org/jira/browse/DIRSERVER-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-125:
----------------------------------------
Fix Version/s: 2.5.0
postponed
> Refactor apachedns.schema
> -------------------------
>
> Key: DIRSERVER-125
> URL: https://issues.apache.org/jira/browse/DIRSERVER-125
> Project: Directory ApacheDS
> Issue Type: New Feature
> Components: dns
> Reporter: Enrique Rodriguez
> Assignee: Enrique Rodriguez
> Fix For: 2.5.0
>
>
> Based on new understanding of RFC's 1034 and 1035 we can refactor the apache
> DNS schema to eliminate a number of unnecessary attributes and make zone
> configuration more intuitive:
> o remove name. name is implicit in the relative DN (RFC 2247).
> o remove type. type is implicit in the objectClass.
> o move class from MUST on abstract record type to MAY on SOA. class will be
> determined from the SOA or default to IN (RFC 1035 5.2).
> o change TTL to MAY. TTL will default to SOA MINIMUM.
> o add MAY 'description'.
> o separate OC's for apacheDnsReferralNameServer and
> apacheDnsNameServerRecord. The meaning of these name servers is
> fundamentally different.
> o separate OC's for apacheDnsReferralAddress and apacheDnsAddressRecord.
> The meaning of these address records is fundamentally different.
> o use domainComponents, CS.UCL.AC.UK maps to DC=CS,DC=UCL,DC=AC,DC=UK,
> according to RFC 2247.
> o Note: ldap-common NamespaceTools.inferLdapName( example.com ) will return
> a DN for a zone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
