Announcements

• Microsoft Office MSDN Release Notes - January 2009

  Chris MullaneyMSFTWednesday, February 04, 2009 9:01 PM
  This release includes document changes made since the previous release. A major change for this release is the addition of a new protocol document for Office 2007, [MS-OFBA]: Office Forms Based Authentication Protocol Specification. This release also contains a new Standard document, [MS-CUSTOMUI]: Custom UI XML Markup.
  
  Issues specific to the January release include:
  
  

  1. Revisions to the Product Behavior section of all Office File Format documents have been updated to remove the specific Service Pack indicators. All documents will apply to all releases of the applicable product version.
  2. A correction was made to the version history table and version number of MS-UCDX.

  The following known issues exist in the January Release:

  1. Underscore characters are not always visible in code in the PDF files depending on the magnification selected by the user. Those characters are present in printed versions.
  2. Information in a table row may split across two pages.
  3. Table borders are not always visible depending upon the magnification selected by the user. Borders are present in printed versions of the PDF.
  4. Cross-protocol links are only functional when the PDF files for the protocols are in the same folder.

  Note: Links in the PDFs don’t resolve in Adobe Reader 9 because Adobe has changed the default setting for view mode in Adobe Reader 9. To access links, perform the following procedure:
  
  1. In Adobe Reader 9, go to the Edit menu and click Preferences.
  2. In the Categories list, click Documents.
  3. Under PDF/A View Mode, change the selection from Only for PDF/A documents to Never, and click OK.
  
  Additional details on changing the setting can be located via the Adobe help site: http://help.adobe.com/en_US/Acrobat/9.0/Standard/WS3E0E8467-B787-4020-A1D3-6BC762A42DF2.w.html

• Description of the Communicator 2007 R2 hotfix rollup package: April 2009

  Chris MullaneyMSFTFriday, April 10, 2009 7:54 PM

  To support the Communicator 2007 R2 hotfix rollup package: April 2009, several modifications have been made in the protocols that enable communication between Microsoft Office Communicator and Office Communications Server.

   

  For information about the service release, see knowledgebase article #967673: Description of the Communicator 2007 R2 hotfix rollup package: April 2009.

   

  Protocol Documents

  The following Microsoft Office Protocols have been updated.

  1       [MS-SIPREGE]: Session Initiation Protocol (SIP) Registration Extensions

  MS-SIPREGE has been updated to include a new provisionGroup element to support the disabling of file transfer functionality.

  Page 24: Data Model for userSetting provisionGroup

  2007 R2

  This is the March 13, 2009 protocol content.

   

  provisionGroup (name='userSetting')

       |

       |-- ucUserLocationProfile

   

  ucUserLocationProfile: Supplies the location profile for voice call features. This is used by the extensions specified in [MS-SIPRE].

   

   

  2007 R2 Hotfix: April 2009

  The disableFileTransfer element has been added.

   

  provisionGroup (name='userSetting')

       |

       |-- ucUserLocationProfile

       |-- disableFileTransfer

   

  ucUserLocationProfile: Supplies the location profile for voice call features. This is used by the extensions specified in [MS-SIPRE].

   

  disableFileTransfer:Supplies whether file transfer is to be disabled or not. The value MUST be true or false.

   

   

  2       [MS-PRES]: Presence Protocol Specification

   

  Page 70: userProperties

   

  2007 R2

  This is the March 13, 2009 protocol content.

   

  telephonyMode: The value of this element controls the audio/video features on the client. It MUST have one of the following tokens: "None", "Uc", "Rcc", or "Dual".

   

  2007 R2 Hotfix: April 2009

  The list of tokens allowable for telephonyMode has been expanded to include "NoAudioVideo"

   

  telephonyMode: The value of this element controls the audio/video features on the client. It MUST have one of the following tokens: "None", "Uc", "Rcc", "Dual" or "NoAudioVideo".

   

   

  3      [MS-CONMGMT]: Connection Management Protocol Specification

  Page 14: Timers

   

  2007 R2

  This is the March 13, 2009 protocol content.

   

  The server MUST maintain an expiry timer.

   

  The server SHOULD define a timeout value for keeping the connection alive. A timeout of 300 seconds is recommended. If the server accepts the keep-alive request, the timer MUST be set to the timeout value plus a grace period of at least a SIP transaction (transaction) timeout (Timer B or Timer F from [RFC3261], 32 seconds by default), and the server MUST send the response with an Ms-Keep-Alive header field that contains the timeout value in ms-keep-alive-timeout. The expiry timer MUST be reset to the timeout value whenever any traffic is received on the connection. Clients MUST maintain a refresh timer. When the client retrieves the timeout value from the ms-keep-alive-timeout parameter in the Ms-Keep-Alive header field, it MUST set the refresh timer with the timeout value. The server expiry timer is reset to the expiry timer value if the client sends any data on the connection.

   

  Clients MUST maintain a refresh timer.

   

  When the client retrieves the timeout value from the ms-keep-alive-timeout parameter in the Ms-Keep-Alive header field, it MUST set the refresh timer with the timeout value. The server expiry timer is reset to the expiry timer value if the client sends any data on the connection

   

  2007 R2 Hotfix: April 2009

  The expiry timer behavior has changed. Note the italicized text.

   

  The server MUST maintain an expiry timer.

  The server SHOULD define a timeout value for keeping the connection alive. A timeout of 300 seconds is recommended. If the server accepts the keep-alive request, the timer MUST be set to the timeout value plus a  grace period of at least a SIP transaction (transaction) timeout (Timer B or Timer F from [RFC3261], 32 seconds by default), and the server MUST send the response with an Ms-Keep-Alive header field that contains the timeout value in ms-keep-alive-timeout. The expiry timer MUST be reset to the timeout value whenever any traffic is received on the connection.

  Clients MUST maintain a refresh timer.

  When the client retrieves the timeout value from the ms-keep-alive-timeout parameter in the Ms-Keep-Alive header field, it SHOULD set the refresh timer to 2/3 of the timeout value. The server expiry timer is reset to the expiry timer value if the client sends any data on the connection.