<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2798 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2798.xml">
<!ENTITY RFC4510 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4510.xml">
<!ENTITY RFC4524 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4524.xml">
<!ENTITY RFC6530 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6530.xml">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- used by XSLT processors -->
<!-- OPTIONS, known as processing instructions (PIs) go here. -->
<!-- For a complete list and description of PIs,
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable PIs that most I-Ds might want to use. -->
<?rfc strict="yes" ?> <!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC): -->
<?rfc toc="yes"?> <!-- generate a ToC -->
<?rfc tocdepth="2"?> <!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references: -->
<?rfc symrefs="yes"?> <!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?> <!-- sort the reference entries alphabetically -->
<!-- control vertical white space:
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?> <!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?> <!-- keep one blank line between list items -->
<!-- end of popular PIs -->

<rfc  category="info" docName="draft-stroeder-mailboxrelatedobject-02" ipr="trust200902">

  <front>

    <title abbrev="LDAP Mailbox Related Objects">
      Lightweight&#160;Directory&#160;Access&#160;Protocol&#160;(LDAP):
      Auxiliary&#160;Object&#160;Class&#160;'mailboxRelatedObject'
    </title>

    <author fullname="Michael Stroeder" initials="M" surname="Stroeder">
      <organization>Independent consultant</organization>
      <address>
        <postal>
          <street>Klauprechtstr. 11</street>
          <city>Karlsruhe</city>
          <code>76137</code>
          <country>DE</country>
        </postal>
<!-- <phone/> -->
        <email>michael@stroeder.com</email>
        <uri>http://www.stroeder.com</uri>
      </address>
    </author>

    <date year="2013" />
<!-- <area/> -->
    <workgroup>Network Working Group</workgroup>
    <keyword>ldap</keyword>
    <keyword>mailboxRelatedObject</keyword>

    <abstract>
      <t>
        This document defines the auxiliary object class 
        'mailboxRelatedObject' that can be used to associate an 
        arbitrary object with a RFC 2822 mail address.
        Furthermore a attribute 'intlMailAdr' is defined for
        internationalized email addresses.
      </t>
    </abstract>

  </front>

  <middle>

    <section title="Introduction">
      <t>
        Often there is a need to add attribute 'mail' defined in
        <xref target="RFC4524"/> to directory entries to associate a, most 
        times non-personal, RFC 2822 mail address with an arbitrary 
        object.
      </t>
      <t>
        This document defines the auxiliary object class 'mailboxRelatedObject'
        for that purpose so abusing person object classes
        like 'inetOrgPerson' defined in <xref target="RFC2798"/> for
        non-personal mail addresses is not needed.
      </t>
      <t>
        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
        this document are to be interpreted as described in
        <xref target="RFC2119"/>.
      </t>
      <t>
        This document is being discussed on the ldapext@ietf.org mailing list.
      </t>
    </section>

    <section anchor="at_def" title="Attribute Type Definition">

      <t>
        The attribute type 'intlMailAdr' is defined for storing 
        internationalized email addressess like used in <xref target=
        "RFC6530"/> and <xref target="RFC6530"/>.
      </t>
      <figure><artwork><![CDATA[
    ( 1.3.6.1.4.1.5427.1.389.4.18
      NAME 'intlMailAdr'
      DESC 'Internationalized Email Address'
      EQUALITY caseIgnoreMatch
      SUBSTR caseIgnoreSubstringsMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
      ]]></artwork></figure>

    </section>

    <section anchor="oc_def" title="Object Class Definition">

      <t>
        Entries of auxiliary object class 'mailboxRelatedObject' MAY 
        contain the following optional attributes:
        'mail' <xref target="RFC4524"/> 
        'displayName' <xref target="RFC2798"/>
        'intlMailAdr'
      </t>
      <figure><artwork><![CDATA[
    ( 1.3.6.1.4.1.5427.1.389.6.9
      NAME 'mailboxRelatedObject'
      DESC 'Associated RFC 2822 mailbox for any entry'
      AUXILIARY
      MAY ( displayName $ mail $ intlMailAdr ) )
      ]]></artwork></figure>

    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>
        The OID arc used for the object class defintion is:
        <vspace blankLines="0" />
        iso(1) org(3) dod(6) internet(1) private(4) enter-prise(1) stroeder.com(5427) public(1) ldap(389) objectClasses(6)
      </t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>
        The introduction of these object classes does not impact the
        security of the Internet or a particular LDAP directory service.
      </t>
      <t>
        Security considerations for LDAP in general are discussed in documents
        comprising the technical specification <xref target="RFC4510"/>.
      </t>
    </section>

  </middle>

  <back>

    <references title="Normative References">
      &RFC2119;
      &RFC2798;
      &RFC4510;
      &RFC4524;
    </references>

    <references title="Informative References">
      &RFC6530;
   </references>


  </back>

</rfc>
