rfc2739.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 900 行 · 第 1/2 页


RFC 2739                Locating a Calendar User            January 2000


   Type examples:

      CALURI;PREF:http://cal.host1.com/calA
      CALURI:ftp://ftp.host1.com/calA.ics

2.4 Directory Lookup Using The LDAP v3 Protocol

   Another way to obtain these URIs is to look them up in a directory
   using the LDAP protocol [1].

   If a user's URIs can be found using directory lookup (i.e., searching
   for one of the LDAP schema extensions defined below), they should, in
   general, be considered "more up-to-date" than URIs in any vCards that
   are stored locally.

2.4.1 LDAP Schema Extensions

   In order to encode the calendaring URIs in the directory, the
   following are defined:

   - One object class:

      - calEntry

   - Eight attributes:

      - calCalURI

      - calFBURL

      - calCAPURI

      - calCalAdrURI

      - calOtherCalURIs

      - calOtherFBURLs

      - calOtherCAPURIs

      - calOtherCalAdrURIs

   The calCalURI contains the URI to a snapshot of the user's entire
   default calendar. The calFBURL contains the URI to the user's default
   busy time data. The calCAPURI represents contains a URI that can be
   used to communicate with the user's calendar. The calCalAdrURI
   contains a URI that points to the location to which event requests
   should be sent for that user.



Small, et al.               Standards Track                     [Page 9]

RFC 2739                Locating a Calendar User            January 2000


   The calOtherCalURIs is a multi-valued property containing URIs to
   snapshots of other calendars that the user may have. The
   calOtherFBURLs is a multi-valued property containing URIs to other
   free/busy data that the user may have. The calOtherCAPURIs attribute
   is a multi-valued property containing URIs to other calendars that
   the user may have. The calOtherCalAdrURIs attribute is a multi-valued
   property containing URIs to other locations that a user may want
   event requests sent to.

   There is no predetermined order to the values in either multi-valued
   property.

2.4.2  Notation

   The notation used in this memo is the same as that used in [2].

2.4.3  Object Definitions

2.4.3.1  calEntry

   The Calendar Entry is a class derived from "TOP" [2], which contains
   the four calendaring attributes.

      (1.2.840.113556.1.5.87
        NAME 'calEntry'
        TOP
        AUXILIARY
        MAY (calCalURI calFBURL calOtherCalURIs calOtherFBURLs calCAPURI
        calOtherCAPURLs)
      )

2.4.4  Attribute Definitions

2.4.4.1 calCalURI

      (1.2.840.113556.1.4.478
        NAME 'calCalURI'
        EQUALITY caseIgnoreMatch
        SUBSTRING caseIgnoreMatch
        SYNTAX 'IA5String'
        USAGE userApplications
      )

2.4.4.2  calFBURL

      (1.2.840.113556.1.4.479
        NAME 'calFBURL'
        EQUALITY caseIgnoreMatch



Small, et al.               Standards Track                    [Page 10]

RFC 2739                Locating a Calendar User            January 2000


        SUBSTRING caseIgnoreMatch
        SYNTAX 'IA5String'
        USAGE userApplications
      )

2.4.4.3  calCAPURI

      (1.2.840.113556.1.4.480
        NAME 'calCAPURI'
        EQUALITY caseIgnoreMatch
        SUBSTRING caseIgnoreMatch
        SYNTAX 'IA5String'
        USAGE userApplications
      )

2.4.4.4  calCalAdrURI

      (1.2.840.113556.1.4.481
        NAME 'calCalAdrURI'
        EQUALITY caseIgnoreMatch
        SUBSTRING caseIgnoreMatch
        SYNTAX 'IA5String'
        USAGE userApplications
      )

2.4.4.5  calOtherCalURIs

        (1.2.840.113556.1.4.482
        NAME 'calOtherCalURIs'
        EQUALITY caseIgnoreMatch
        SUBSTRING caseIgnoreMatch
        SYNTAX 'IA5String'
        MULTI-VALUE
        USAGE userApplications
      )

2.4.4.6  calOtherFBURLs

      (1.2.840.113556.1.4.483
        NAME 'calOtherFBURLs'
        EQUALITY caseIgnoreMatch
        SUBSTRING caseIgnoreMatch
        SYNTAX 'IA5String'
        MULTI-VALUE
        USAGE userApplications
      )





Small, et al.               Standards Track                    [Page 11]

RFC 2739                Locating a Calendar User            January 2000


2.4.4.7  calOtherCAPURIs

      (1.2.840.113556.1.4.484
        NAME 'calOtherCAPURIs'
        EQUALITY caseIgnoreMatch
        SUBSTRING caseIgnoreMatch
        SYNTAX 'IA5String'
        MULTI-VALUE
        USAGE userApplications
      )

2.4.4.8  calOtherCalAdrURIs

      (1.2.840.113556.1.4.485
        NAME 'calOtherCalAdrURIs'
        EQUALITY caseIgnoreMatch
        SUBSTRING caseIgnoreMatch
        SYNTAX 'IA5String'
        MULTI-VALUE
        USAGE userApplications
      )

3  IANA Considerations

   This memo defines IANA registered extensions to the attributes
   defined by LDAP [1] and vCard [3].

   IANA registration proposals for vCard are to be emailed to the
   registration agent for the "text/directory" MIME content-type,
   <MAILTO:  [e-mail]> using the format defined in
   [3].

4  Security Considerations

   Standard vCard and LDAP security rules and support apply for the
   extensions described in this document, and there are no special
   security issues for these extensions.

   Please note, though, that LDAP servers may permit anonymous clients
   to refresh entries which they did not create. Servers are also
   permitted to control a refresh access to an entry by requiring
   clients to bind before issuing a RefreshRequest. This will have
   implications on the server performance and scalability.

   Please also note, though, that vCard objects may have been created by
   an entity other than that represented by the vCard. Recipients should
   be certain of the source that generated the vCard.




Small, et al.               Standards Track                    [Page 12]

RFC 2739                Locating a Calendar User            January 2000


   Also, care should be taken in making use of information obtained from
   directory servers that has been supplied by client, as it may now be
   out of date. In many networks, for example, IP addresses are
   automatically assigned when a host connects to the network, and may
   be reassigned if that host later disconnects. An IP address obtained
   from the directory may no longer be assigned to the host that placed
   the address in the directory. This issue is not specific to LDAP or
   dynamic directories.

5  Acknowledgments

   The authors wish to acknowledge the work of Alec Dun, who acted as an
   author for the early drafts of this memo. In addition, this document
   received input from the various participants in the IETF CALSCH
   Working Group discussions.

6  Authors' Addresses

   The following address information is provided in a vCard v3.0 [3],
   Electronic Business Card, format.

   BEGIN:VCARD
   VERSION:3.0
   N:Small;Tony
   FN:Tony Small
   ORG:XpertSite.Com
   ADR;TYPE=WORK,POSTAL,PARCEL:;;4700 42nd Ave. SW, Suite 440;
    Seattle;WA;98116;USA
   TEL;TYPE=WORK,MSG:[phone]
   TEL;TYPE=WORK,FAX:[phone]
   EMAIL;TYPE=INTERNET:[e-mail]
   CALADRURI:MAILTO:[e-mail]
   END:VCARD

   BEGIN:VCARD
   VERSION:3.0
   N:Hennessy;Denis
   FN:Denis Hennessy
   ORG:ISOCOR
   ADR;TYPE=WORK,POSTAL,PARCEL:;;42-47 Lower Mount St;
    Dublin 2;Ireland
   TEL;TYPE=WORK,MSG:[phone]
   TEL;TYPE=WORK,FAX:[phone]
   EMAIL;TYPE=INTERNET:[e-mail]
   CALADRURI:MAILTO:[e-mail]
   END:VCARD





Small, et al.               Standards Track                    [Page 13]

RFC 2739                Locating a Calendar User            January 2000


   BEGIN:VCARD
   VERSION:3.0
   N:Dawson;Frank
   FN:Frank Dawson
   ORG:Lotus Development Corporation
   ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive;
    Raleigh;NC;27613-3502;USA
   TEL;TYPE=WORK,PREF:[phone]
   TEL;TYPE=WORK,MSG:[phone]
   TEL;TYPE=FAX:[phone]
   EMAIL;TYPE=INTERNET,PREF:[e-mail]
   EMAIL;TYPE=INTERNET:[e-mail]
   CALADRURI;TYPE=PREF:MAILTO:[e-mail]
   CALADRURI:MAILTO:[e-mail]
   URL:http://home.earthlink.net/~fdawson
   END:VCARD

   This memo is a result of the work of the Internet Engineering Task
   Force Calendaring and scheduling Working Group. The chairman of that
   working group is:

   BEGIN:VCARD
   VERSION:3.0
   N:Egen;Pat
   FN:Pat Egen
   ORG:Engan Consulting
   ADR;TYPE=WORK:;;803 Creek Overlook;Chattanooga;TN;37415;USA
   TEL;TYPE=WORK,VOICE:423.875.2652
   TEL;TYPE=WORK,FAX:[phone]
   EMAIL:[e-mail]
   URL:http://www.egenconsulting.com
   CALADRURI:MAILTO:[e-mail]
   END:VCARD


















Small, et al.               Standards Track                    [Page 14]

RFC 2739                Locating a Calendar User            January 2000


7  Bibliography

   [1] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory Access
       Protocol (v3)", RFC 2251, December 1997.

   [2] Wahl, M., Coulbeck, A., Howes, T. and  S. Kille, "Lightweight
       Directory Access Protocol (v3): Attribute Syntax Definitions",
       RFC 2252, December 1997.

   [3] Dawson, F. and  T. Howes, "vCard MIME Directory Profile", RFC
       2426, September 1998.

   [4] Dawson, F. and D. Stenerson, "Internet Calendaring and Scheduling
       Core Object Specification (iCalendar)", RFC 2445, November 1997.

   [5] Dawson, F. and S. Mansour, "iCalendar Message-Based
       Interopability Protocal (iMIP)", RFC 2447, November 1997.


































Small, et al.               Standards Track                    [Page 15]

RFC 2739                Locating a Calendar User            January 2000


8  Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Small, et al.               Standards Track                    [Page 16]