[MS-GRVPROT]:
Groove Protocols Overview
This document provides an overview of the protocols in the Microsoft Groove and Microsoft SharePoint Workspace system. It is intended for use in conjunction with Microsoft protocol technical specifications, publicly available standard specifications, network programming art, and Microsoft Windows distributed systems concepts. It assumes that the reader is either familiar with the aforementioned material or has immediate access to it.
This system does not require use of Microsoft programming tools or programming environments to implement the protocols within it. Implementers who have access to Microsoft programming tools and environments are free to take advantage of them.
Intellectual Property Rights Notice for Open Specifications Documentation
Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions.
Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation.
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting .
Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit
Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it.
Abstract
This document describes the intended functionality of the Microsoft Groove and Microsoft SharePoint Workspace system and how the protocols within this system interact. It also provides examples of some common user scenarios. It does not restate the processing rules and other details that are specific to each protocol. Those details are described in the protocol specifications for each of the protocols and data structures that make up this system.
The Groove and SharePoint Workspace system is designed for Internet-based collaboration. The system consists of protocol clients that communicate with each other and with supporting protocol servers. The system protocols, as described in [MS-GRVRDB], [MS-GRVDYNM], [MS-GRVWDPP], [MS-GRVSSTPS], [MS-GRVSSTP], [MS-GRVHENC], [MS-GRVSPCM], and [MS-GRVSPMR], are designed to facilitate and help secure communications, data synchronization, and supporting services and management.
Revision Summary
Date / Revision History / Revision Class / Comments4/4/2008 / 0.01 / Major / Initial Availability
6/27/2008 / 1.0 / Minor / Revised and edited technical content
12/12/2008 / 1.01 / Editorial / Revised and edited technical content
7/13/2009 / 1.02 / Major / Revised and edited the technical content
8/28/2009 / 1.03 / Editorial / Revised and edited the technical content
11/6/2009 / 1.04 / Editorial / Revised and edited the technical content
2/19/2010 / 2.0 / Minor / Updated the technical content
3/31/2010 / 2.01 / Editorial / Revised and edited the technical content
4/30/2010 / 2.02 / Editorial / Revised and edited the technical content
6/7/2010 / 2.03 / Editorial / Revised and edited the technical content
6/29/2010 / 2.04 / Editorial / Changed language and formatting in the technical content.
7/23/2010 / 2.04 / None / No changes to the meaning, language, or formatting of the technical content.
9/27/2010 / 2.05 / Minor / Clarified the meaning of the technical content.
11/15/2010 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
12/17/2010 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
3/18/2011 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
6/10/2011 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
1/20/2012 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
4/11/2012 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
7/16/2012 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
10/8/2012 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
2/11/2013 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
7/30/2013 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
11/18/2013 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
2/10/2014 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
4/30/2014 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
7/31/2014 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
10/30/2014 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
6/23/2016 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
9/14/2016 / 2.05 / None / No changes to the meaning, language, or formatting of the technical content.
Table of Contents
1Introduction
1.1Glossary
1.2References
2Functional Architecture
2.1Overview
2.1.1Protocol Client
2.1.2Management Server
2.1.3Relay Server
2.1.4Data Bridge Server
2.2Protocol Summary
2.3Environment
2.3.1Dependencies on This System
2.3.2Dependencies on Other Systems/Components
2.4Assumptions and Preconditions
2.5Use Cases
2.5.1Create an Account
2.5.2Publish Presence Status
2.5.3Create a Shared Space
2.5.4Display Presence Information
2.5.5Search for Users
2.5.6Add Contacts
2.5.7Invite Users to Join a Shared Space
2.5.8Update a Shared Space
2.5.9Create a Domain
2.5.10Add Users to a Domain
2.5.11Add a Policy to a Domain
2.5.12Delete Policies from a Domain
2.5.13Add a Relay Server
2.5.14Add Users to a Relay Server
2.6Versioning, Capability Negotiation, and Extensibility
2.7Error Handling
2.8Coherency Requirements
2.9Security
2.9.1Protocol Security
2.9.1.1Groove Dynamics Protocol
2.9.1.2SSTP Security Protocol
2.9.1.3Groove SOAP Security
2.9.2Application Security
2.9.2.1Protocol Clients
2.9.2.2Protocol Servers
2.9.2.3Server Administration Applications
2.10Additional Considerations
3Examples
3.1Example 1: Create an Account
3.2Example 2: Add Contacts
3.3Example 3: Update a Shared Space
3.4Example 4: Add a Policy to a Domain
3.5Example 5: Add Users to a Relay Server
4Microsoft Implementations
4.1Product Behavior
5Change Tracking
6Index
1Introduction
The Microsoft Groove and Microsoft SharePoint Workspace system is designed to facilitate Internet-based collaboration. The system consists of protocol clients and supporting management, relay, and data bridge servers. The following diagram provides a high-level overview of the system.
Figure 1: Overview of the Groove and SharePoint Workspace system
Protocol clients within the system can connect to each other through local area networks (LANs) or the Internet. The management server provides services for managing users of the system. The relay server provides services for protocol clients when direct peer-to-peer communications are not possible. The data bridge server enables integration with external applications.
Users of the system can create shared spaces and share those spaces with other users. A shared space can contain documents and tools, such as calendar, discussion, and meeting tools, and it is synchronized automatically between protocol clients. Members of a collaboration team can be part of the same organization or multiple, independent organizations. In addition, users can work either online or offline.
1.1Glossary
This document uses the following terms:
account configuration code: A unique code that is generated by a management server. It is used to bind an identity to a member of a management server.
data bridge server: A server application that facilitates data integration between protocol clients and external databases or other applications.
Domain Name System (DNS): A hierarchical, distributed database that contains mappings of domain names (1) to various types of data, such as IP addresses. DNS enables the location of computers and services by user-friendly names, and it also enables the discovery of other information stored in the database.
fanout: The process of transmitting a message from a client device to a relay server for replication and distribution to multiple recipients.
Hypertext Transfer Protocol (HTTP): An application-level protocol for distributed, collaborative, hypermedia information systems (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.
identity: A digital persona that is associated with two key pairs, one for encrypting data and another for signing data.
management server: A server application that is used to manage SharePoint Workspace and Groove identities and services.
peer: An additional endpoint (5) that is associated with an endpoint in a session. An example of a peer is the callee endpoint for a caller endpoint.
presence: A status indicator on a client device that is transmitted by using the Wide Area Network Device Presence Protocol (WAN DPP).
relay server: A server application that provides message transmission services for Simple Symmetric Transport Protocol (SSTP) messages.
Secure Sockets Layer (SSL): A security protocol that supports confidentiality and integrity of messages in client and server applications that communicate over open networks. SSL uses two keys to encrypt data-a public key known to everyone and a private or secret key known only to the recipient of the message. SSL supports server and, optionally, client authentication (2) using X.509 certificates (2). For more information, see [X509]. The SSL protocol is precursor to Transport Layer Security (TLS). The TLS version 1.0 specification is based on SSL version 3.0 [SSL3].
shared space: A set of tools that is synchronized between different endpoints (3), as described in [MS-GRVDYNM].
Simple Symmetric Transport Protocol (SSTP): A protocol that enables two applications to engage in bi-directional, asynchronous communication. SSTP supports multiple application endpoints (5) over a single network connection between client nodes.
SOAP: A lightweight protocol for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework, which provides a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics. SOAP 1.2 supersedes SOAP 1.1. See [SOAP1.2-1/2003].
TCP/IP: A set of networking protocols that is widely used on the Internet and provides communications across interconnected networks of computers with diverse hardware architectures and various operating systems. It includes standards for how computers communicate and conventions for connecting networks and routing traffic.
Web Services Description Language (WSDL): An XML format for describing network services as a set of endpoints that operate on messages that contain either document-oriented or procedure-oriented information. The operations and messages are described abstractly and are bound to a concrete network protocol and message format in order to define an endpoint. Related concrete endpoints are combined into abstract endpoints, which describe a network service. WSDL is extensible, which allows the description of endpoints and their messages regardless of the message formats or network protocols that are used.
1.2References
Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata.
[MS-GRVDYNM] Microsoft Corporation, "Groove Dynamics Protocol".
[MS-GRVHENC] Microsoft Corporation, "HTTP Encapsulation of Simple Symmetric Transport Protocol (SSTP)".
[MS-GRVRDB] Microsoft Corporation, "Groove RDB Commands Protocol".
[MS-GRVSPCM] Microsoft Corporation, "Client to Management Server Groove SOAP Protocol".
[MS-GRVSPMR] Microsoft Corporation, "Management Server to Relay Server Groove SOAP Protocol".
[MS-GRVSSTPS] Microsoft Corporation, "Simple Symmetric Transport Protocol (SSTP) Security Protocol".
[MS-GRVSSTP] Microsoft Corporation, "Simple Symmetric Transport Protocol (SSTP)".
[MS-GRVWDPP] Microsoft Corporation, "Wide Area Network Device Presence Protocol (WAN DPP)".
[MS-OCPROTO] Microsoft Corporation, "Office Client Protocols Overview".
[MSDN-GWSDF] Microsoft Corporation, "Microsoft Office Groove 2007 Web Services Developer Reference",
2Functional Architecture
The following sections describe the functional architecture of the Microsoft Groove and Microsoft SharePoint Workspace system.
2.1Overview
The Microsoft Groove and Microsoft SharePoint Workspace system is designed to facilitate collaboration over the Internet, primarily through the use of shared spaces.
The protocols within the system are designed to facilitate and help secure communications between protocol clients and protocol servers, which includes data bridge servers, management servers, and relay servers. A data bridge server is a peer to protocol clients and it enables integration between external applications and the system. Such integration is possible through the use of Groove Web Services, which are described in [MSDN-GWSDF] and are based on the Web Services Description Language (WSDL).
The following diagram provides a high-level overview of communications between protocol clients and protocol servers that are part of the system.
Figure 2: Overview of system communications
As shown in the preceding diagram, protocol clients and a data bridge server are peers that can communicate with each other. They act as clients of a management server and a relay server, and they use request/response-based communications to interact with those servers. In addition, a management server is a client of a relay server and it can be used to manage a relay server. External applications use the Groove Web Services protocol, as described in [MSDN-GWSDF], and a data bridge server to communicate with the system.
The protocols within the system are Internet-based and they use standard Internet protocols for transport. The following figure illustrates the relationship between the system and standard Internet protocols.
Figure 3: Relationship between the system and standard Internet protocols
System protocols consist of:
Client to Management Server Groove SOAP Protocol, as described in [MS-GRVSPCM]
Groove Dynamics Protocol, as described in [MS-GRVDYNM]
Groove RDB Commands Protocol, as described in [MS-GRVRDB]
HTTP Encapsulation of SSTP, as described in [MS-GRVHENC]
Management Server to Relay Server Groove SOAP Protocol, as described in [MS-GRVSPMR]
Simple Symmetric Transport Protocol (SSTP), as described in [MS-GRVSSTP]
SSTP Security Protocol, as described in [MS-GRVSSTPS]
Wide Area Network Device Presence Protocol (WAN DPP), as described in [MS-GRVWDPP]
The following figure illustrates the relationships between system protocols and standard Internet protocols.
Figure 4: Relationships between system protocols and standard Internet protocols
The Groove RDB Commands Protocol uses the Groove Dynamics Protocol as its transport. The Groove Dynamics Protocol and the Wide Area Network Device Presence Protocol (WAN DPP) use the Simple Symmetric Transport Protocol (SSTP) as their transport. The SSTP Security Protocol is a subset of SSTP. SSTP can use either TCP or HTTP Encapsulation of SSTP as its transport. The HTTP Encapsulation of SSTP, the Client to Management Server Groove SOAP Protocol, and the Management Server to Relay Server Groove SOAP Protocol use HTTP as their transport.
The Groove RDB Commands and the Groove Dynamics protocols are designed to synchronize shared spaces. The WAN DPP is designed to enable protocol clients to discover the presence of other protocol clients. The SSTP is designed as a data transport protocol. If direct SSTP connections are not possible because of firewalls and proxy servers, the HTTP Encapsulation of SSTP can be used to pass through those firewalls and proxy servers. The Client to Management Server Groove SOAP Protocol is designed for user management. The Management Server to Relay Server Groove SOAP Protocol is designed for relay service management.
2.1.1Protocol Client
A protocol client provides a more secure environment for users to share data and work with team members by connecting through local area networks (LANs) or over the Internet. Users can create shared spaces and invite other users to participate in those shared spaces. Members of a shared space can then create or edit documents that are part of that shared space and add new tools to the shared space as necessary. Members of a shared space can also have different roles, such as manager or participant, within that shared space. Shared spaces are synchronized automatically for all members.
Each user is associated with a user account and has an identity that is associated with that user account. An identity is a digital persona for the user. It contains the user’s contact information, such as name, e-mail address, phone number, and organization name. A user’s name, as it appears in shared spaces and contact lists, is based on the user’s identity.