Export (0) Print
Expand All

8 Change Tracking

This section identifies changes that were made to the [MS-OXNSPI] protocol document between the July 2014 and October 2014 releases. Changes are classified as New, Major, Minor, Editorial, or No change.

The revision class New means that a new document is being released.

The revision class Major means that the technical content in the document was significantly revised. Major changes affect protocol interoperability or implementation. Examples of major changes are:

  • A document revision that incorporates changes to interoperability requirements or functionality.

  • The removal of a document from the documentation set.

The revision class Minor means that the meaning of the technical content was clarified. Minor changes do not affect protocol interoperability or implementation. Examples of minor changes are updates to clarify ambiguity at the sentence, paragraph, or table level.

The revision class Editorial means that the formatting in the technical content was changed. Editorial changes apply to grammatical, formatting, and style issues.

The revision class No change means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the technical content of the document is identical to the last released version.

Major and minor changes can be described further using the following change types:

  • New content added.

  • Content updated.

  • Content removed.

  • New product behavior note added.

  • Product behavior note updated.

  • Product behavior note removed.

  • New protocol syntax added.

  • Protocol syntax updated.

  • Protocol syntax removed.

  • New content added due to protocol revision.

  • Content updated due to protocol revision.

  • Content removed due to protocol revision.

  • New protocol syntax added due to protocol revision.

  • Protocol syntax updated due to protocol revision.

  • Protocol syntax removed due to protocol revision.

  • Obsolete document removed.

Editorial changes are always classified with the change type Editorially updated.

Some important terms used in the change type descriptions are defined as follows:

  • Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces.

  • Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire.

The changes made to this document are listed in the following table. For more information, please contact dochelp@microsoft.com.

Section

Tracking number (if applicable)
and description

Major
change
(Y or N)

Change type

2.1
Transport

Added details describing which RPC protocol sequence will use the well-known endpoint, and which use RPC dynamic endpoints.

N

Content updated.

2.1
Transport

Specified that the protocol uses RPC over HTTPS.

Y

Content updated.

2.2.1.6
Unicode Comparison Flags

Updated section number.

N

Content updated.

2.2.1.10
Table Sort Orders

Specified that Exchange 2010 SP3 and Exchange 2013 do not support the SortTypePhoneticDisplayName sort order.

Y

New product behavior note added.

2.2.1.13
NspiQueryColumns Flag

Updated the description of the NspiUnicodeProptypes flag to clarify that the PtypString8 type is returned if the flag is not set.

N

Content updated.

2.2.1.15
NspiModLinkAtt Flags

Updated the description of the fDelete flag to clarify that the server adds values when modifying if the flag is not set.

N

Content updated.

2.2.8
STAT

Updated the descriptions for the NumPos and TotalRecs fields to indicate the behavior if absolute positioning is used.

N

Content updated.

2.2.9.3
PermanentEntryID

Added a product behavior note for the Distinguished Name field.

N

New product behavior note added.

3.1.4.1.1
NspiBind (Opnum 0)

Changed constraint 4 to reference constraint 3.

N

Content updated.

3.1.4.1.1
NspiBind (Opnum 0)

Specified that the fAnonymousLogin’s bit flag in dwFlags is 0x20.

Y

Content updated.

3.1.4.1.4
NspiUpdateStat (Opnum 2)

Revised the first statement under the fifth constraint of the server processing rules to indicate that absolute positioning is used, and added associated reference link.

N

Content updated.

3.1.4.1.7
NspiGetProps (Opnum 9)

Added a product behavior note for the fourth constraint under server processing rules.

N

New product behavior note added.

3.1.4.1.8
NspiQueryRows (Opnum 3)

Updated constraint 16 to reference NspiUpdateStat method instead of NspiGetProps method and updated constraints 14 and 16 to reference constraint 6 instead of constraint 5.

N

Content updated.

3.1.4.1.8
NspiQueryRows (Opnum 3)

Changed NspiQueryRows output parameter pStat to NspiQueryRows input parameter pStat in constraint 14.

N

Content updated.

3.1.4.1.12
NspiCompareMIds (Opnum 10)

Revised the description of the plResult field for clarity.

N

Content updated.

3.1.4.1.14
NspiModProps (Opnum 11)

Updated the fourth constraint under Server Processing Rules to indicate that if the value of "Reserved" contains any value besides 0, it is ignored by the server.

N

Content updated.

3.1.4.1.14
NspiModProps (Opnum 11)

Revised the fourth constraint under Server Processing Rules: Changed "...the server returns the value "InvalidParameter" to "...the server MUST ignore the value".

N

Content updated.

3.1.4.1.14
NspiModProps (Opnum 11)

Specified that Exchange 2010 SP3 and Exchange 2013 do not add values for the PidTagUserX509Certificate and PidTagAddressBookX509Certificate properties.

Y

New product behavior note added.

3.1.4.1.15
NspiModLinkAtt (Opnum 14)

Revised the fifth constraint under Server Processing Rules: Changed the value returned by the server from "Success" to "AccessDenied".

N

Content updated.

3.1.4.1.15
NspiModLinkAtt (Opnum 14)

Added product behavior note describing behavior of Exchange 2013 when modification of either the PidTagAddressBookMember property or the PidTagAddressBookPublicDelegates property is attempted.

Y

New product behavior note added.

3.1.4.1.16
NspiResolveNames (Opnum 19)

Removed the constraint in the server processing rules that described the server response when the NspiQueryRows method returns "Success" or "ErrorsReturned".

N

Content removed.

3.1.4.1.16
NspiResolveNames (Opnum 19)

Revised the description on the seventh constraint under server processing rules to eliminate details about specific parameters that are returned to the client.

N

Content updated.

3.1.4.1.17
NspiResolveNamesW (Opnum 20)

Revised the description on the seventh constraint under server processing rules to eliminate details about specific parameters that are returned to the client.

N

Content updated.

3.1.4.1.17
NspiResolveNamesW (Opnum 20)

Removed the constraint in the server processing rules that described the server response when the NspiQueryRows method returns "Success" or "ErrorsReturned".

N

Content updated.

Show:
© 2014 Microsoft