Change Tracking This section identifies changes that were made to this document since the last release. Changes are classified as Major, Minor, or None. The revision class means that the technical content in the document was significantly revised. Major Major changes affect protocol interoperability or implementation. Examples of major changes are: A document revision that incorporates changes to interoperability requirements. A document revision that captures changes to protocol functionality. The revision class means that the meaning of the technical content was clarified. Minor changes Minor 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 None means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the relevant technical content is identical to the last released version. The changes made to this document are listed in the following table. For more information, please contact . Revision Section Description class 6842 : Example 3: Updated Initial Update diagram and Synchronization step 1 to Minor to Update indicate that Client this step is optional. 6842 : Added a product 3.3 Example 3: behavior Initial Update note to Synchronization indicate Minor to Update product Client appicability for functionality. 6842 : Example 4: Updated Differential diagram and Update step 1 to Minor Synchronization indicate that to Update this step is Client optional. 6842 : Added a 3.4 Example 4: product Differential behavior Update Minor note to Synchronization indicate to Update product Client appicability for
Change Tracking This section identifies changes that were made to this document since the last release. Changes are classified as Major, Minor, or None. 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. A document revision that captures changes to protocol functionality. 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 None means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the relevant technical content is identical to the last released version. The changes made to this document are listed in the following table. For more information, please contact . Section Description Revision class Example 3: Initial Update Synchronization to Update Client 6842 : Updated diagram and step 1 to indicate that this step is optional. Minor 3.3 Example 3: Initial Update Synchronization to Update Client 6842 : Added a product behavior note to indicate product appicability for functionality. Minor Example 4: Differential Update Synchronization to Update Client 6842 : Updated diagram and step 1 to indicate that this step is optional. Minor 3.4 Example 4: Differential Update Synchronization to Update Client 6842 : Added a product behavior note to indicate product appicability for Minor