directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSERVER-125) Refactor apachedns.schema
Date Tue, 07 Feb 2006 05:24:57 GMT
     [ http://issues.apache.org/jira/browse/DIRSERVER-125?page=all ]

Alex Karasulu updated DIRSERVER-125:
------------------------------------

    Component: dns

> Refactor apachedns.schema
> -------------------------
>
>          Key: DIRSERVER-125
>          URL: http://issues.apache.org/jira/browse/DIRSERVER-125
>      Project: ApacheDS
>         Type: New Feature
>   Components: dns
>     Reporter: Enrique Rodriguez
>     Assignee: Enrique Rodriguez

>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message