6 Appendix A: Product Behavior
The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.
Windows NT operating system
Windows 2000 operating system
Windows XP operating system
Windows Server 2003 operating system
Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.
The TAPI ILS variant of the LDAP protocol supported by the ILS server is available only on particular versions of Windows:
ILS is supported only on Windows 2000 Server operating system. On Windows Server 2003, dynamic object features were added to Active Directory to support TAPI clients on Windows XP.
TAPI 3.0, which is included in Windows 2000, requires a Windows 2000 ILS server or Site Server 3.0.
TAPI 3.1, which is included in Windows XP, can communicate with a Windows 2000 ILS server or a Windows Server 2003 application partition.
<2> Section 1.4: In the absence of an ILS server, TAPI clients can interact directly with Windows Server 2003 using standard LDAP V3 protocol to manipulate objects that are instances of the classes msTAPI-rtPerson and msTAPI-rtConference.
<3> Section 2.2.2: The TAPI client uses the value "ms-netmeeting".
<4> Section 2.2.2: By default, TAPI clients populate this attribute with a value of "0"; they do not use the value.
<5> Section 2.2.2: Microsoft NetMeeting Clients populate this attribute with the status of being in a call.
<6> Section 2.2.2: By default, TAPI clients populate this attribute with a value of "1"; they do not use the value.
<7> Section 2.2.2: By default, TAPI clients populate this attribute with a value of "1"; they do not use the value.
<8> Section 2.2.2: By default, TAPI clients populate this attribute with the value of "4"; they do not use the value.
<9> Section 2.2.2: This attribute is present for NetMeeting compatibility.
<10> Section 2.2.2: This attribute is required by the schema, although it is only used for NetMeeting 2.0 compatibility. Originally, the attribute was used by NetMeeting 2.0 as a filter when searching a directory for a user. It is not required for interoperability with NetMeeting 3.0 or later.
<11> Section 2.2.3: It is no longer used and is retained to be compatible with Site Server 3.0. NetMeeting clients populate this attribute with "-" (a dash).
By default, TAPI clients populate this attribute with "US" (United States); they do not use the value.
<12> Section 2.2.3: NetMeeting clients populate this attribute with the email address that the user supplied during setup or later. TAPI clients populate this attribute with the common (display) name of the user.
<13> Section 2.2.3: NetMeeting clients populate this attribute with the name that the user supplied during setup or later.
By default, TAPI clients populate this attribute with "Generated by TAPI3"; they do not use the value.
<14> Section 2.2.3: By default, TAPI clients populate this attribute with a value of "0"; they do not use the value.
<15> Section 2.2.3: By default, TAPI clients populate this attribute with a value of "1"; they do not use the value.
<16> Section 2.2.3: By default, TAPI clients populate this attribute with a value of "1"; they do not use the value.
<17> Section 2.2.3: By default, TAPI clients populate this attribute with the value of "4"; they do not use the value.
<18> Section 2.2.3: NetMeeting populates this attribute with the value "1503" (Data port) and "1720" (Audio/Video port).
<19> Section 2.2.3: NetMeeting clients populate this attribute with the email address that the user supplied during setup or later.
<20> Section 2.2.3: NetMeeting clients populate this attribute with the operation commands in ModifyRequest. By default, TAPI clients populate this attribute with "0" (ADD); they do not use the value.
<21> Section 2.2.3: NetMeeting clients populate this attribute with the name that the user supplied during setup or later.
TAPI clients populate this attribute with a single white space "" (no surname); they do not use the value.
<22> Section 2.2.3: NetMeeting clients populate this attribute with a string form of a DWORD, which is based on a semi-unique ID obtained from a clock tick. It is used to identify a user in the case of NetMeeting problems and a reconnect with the server is required.
By default, TAPI clients populate this attribute with "1508109"; they do not use the value.
<23> Section 2.3: The following tables list the NetMeeting and Dialer attributes, and indicate whether the attribute is used or not. Use of the attribute by NetMeeting or Dialer does not imply visible behavior on the wire.
rtApplicationUser – The User of an Application
|
Attribute |
Used by NetMeeting |
Used by Dialer |
|---|---|---|
|
applicationID |
Yes |
Yes |
|
appName |
Yes |
Yes |
|
Application Name |
Yes |
No |
|
groupObject |
No |
No |
|
guid |
Yes |
Yes |
|
ILSA26214430 |
Yes |
Yes |
|
ILSA26279966 |
Yes |
No |
|
ILSA32833566 |
Yes |
Yes |
|
ILSA32964638 |
Yes |
Yes |
|
ILSA39321630 |
Yes |
Yes |
|
mimeType |
Yes |
Yes |
|
objectClass |
Yes |
Yes |
|
port |
Yes |
Yes |
|
protocolGUID |
Yes |
No |
|
protocolID |
Yes |
Yes |
|
protocolMimeType |
Yes |
Yes |
|
sFlags |
Yes |
No |
|
userObject |
Yes |
Yes |
rtPerson – An Online Person
|
Attribute |
Used by NetMeeting |
Used by Dialer |
|---|---|---|
|
c |
Yes |
Yes |
|
cn |
Yes |
Yes |
|
comment |
Yes |
Yes |
|
givenName |
Yes |
Yes |
|
guid |
Yes |
Yes |
|
ILSA26214430 |
Yes |
Yes |
|
ILSA26279966 |
Yes |
No |
|
ILSA32833566 |
Yes |
Yes |
|
ILSA32964638 |
Yes |
Yes |
|
ILSA39321630 |
Yes |
Yes |
|
ipAddress |
Yes |
Yes |
|
location |
Yes |
Yes |
|
mimeType |
Yes |
Yes |
|
o |
Yes |
Yes |
|
port |
Yes |
Yes |
|
protocolMimeType |
Yes |
Yes |
|
rfc822mailbox |
Yes |
Yes |
|
sFlags |
Yes |
Yes |
|
smodop |
Yes |
Yes |
|
surName |
Yes |
Yes |
|
securityToken |
Yes |
Yes |
rtConference – An Online Conference
|
Attribute |
Used by NetMeeting |
Used by Dialer |
|---|---|---|
|
advertisingScope |
No |
No |
|
announcementScope |
No |
No |
|
applicationID |
No |
No |
|
Attendees |
No |
No |
|
attendeesCount |
No |
No |
|
confAddr |
No |
No |
|
conferenceBlob |
No |
Yes |
|
contactInformation |
No |
No |
|
generalDescription |
No |
No |
|
isEncrypted |
No |
No |
|
maxAttendeesCount |
No |
No |
|
Originator |
No |
No |
|
protocolID |
No |
Yes |
|
rating |
No |
No |
|
startTime |
No |
No |
|
stopTime |
No |
No |
|
subType |
No |
No |
|
url |
No |
No |
|
uid |
No |
Yes |
<24> Section 2.3.4: The unique GUID used is 6D12FC99-B836-11D0-9601-00C04FC30E1A3.
<25> Section 2.3.5: The unique GUID used is ed1af3b3-bcfa-11d0-853a-00a0c90c93e1.
<26> Section 3.5.3: NetMeeting 3.01 only performs a simple bind using LDAP v2 and therefore never performs an authenticated bind.
<27> Section 3.5.4: The TAPI Client Phone Dialer 1.00 included with Windows 2000 Server and Windows 2000Workstation performs authentication using Sicily Authentication. Only Active Directory security principles can authenticate in this manner.
<28> Section 3.5.11: NetMeeting 3.01 specifies "base" scope in search requests, when an LDAP server would normally use "sub".
<29> Section 3.6: An ILS Server will remove objects from the database when the entryTTL attribute reaches zero. This removal might not be immediate and will depend on various indeterminate factors such as processor speed, processor load, and available memory.
<30> Section 4.1.1: NetMeeting clients work in this manner.
<31> Section 4.2.1: NetMeeting clients work in this manner.
<32> Section 4.11.1: NetMeeting 3.01 specifies "base" scope in search requests, when an LDAP server would normally use "sub".