2.2 Protocol Summary

The following table provides a comprehensive list of the member protocols for Content Caching and Retrieval.

Protocol name

Description

Short name

Peer Content Caching and Retrieval: Content Identification

Specifies a binary data structure that is used in the Content Caching and Retrieval. The primary role in Content Caching and Retrieval is content identification.

[MS-PCCRC]

Peer Content Caching and Retrieval Discovery Protocol

Specifies a multicast to discover and locate services that are based on the Web Services Dynamic Discovery (WS-Discovery) protocol [WS-Discovery]. There are two modes of operations in WS-Discovery: client-initiated probes and service-initiated announcements; both are sent through IP multicast to a predefined group. The primary role in Content Caching and Retrieval is content discovery.

[MS-PCCRD]

Peer Content Caching and Retrieval: Retrieval Protocol

Specifies the messages that are required to query peer-role servers or a hosted cache server for the availability of certain content and to retrieve the content. The primary role in Content Caching and Retrieval is content retrieval.

[MS-PCCRR]

Peer Content Caching and Retrieval: Hosted Cache Protocol

Specifies an HTTP/HTTPS-based mechanism for clients to notify a hosted cache server about the availability of content and for a hosted cache server to indicate interest in the content.<5> The primary role in Content Caching and Retrieval is content notification.

[MS-PCHC]

Peer Content Caching and Retrieval: HTTP Extensions

Specifies a content encoding known as PeerDist that is used by an HTTP/1.1 client and an HTTP/1.1 server to communicate content to each other. The primary role in Content Caching and Retrieval is metadata (hash) retrieval.

[MS-PCCRTP]

Server Message Block (SMB) Version 2.1 Protocol

Specifies a metadata retrieval mechanism. Version 2.1 of this protocol has enhancements to detect content caching-enabled shares and retrieval of metadata that is related to content caching. The primary role in Content Caching and Retrieval is metadata (hash) retrieval.

[MS-SMB2]

The following table provides a comprehensive list of the member protocols of Content Caching and Retrieval. The member protocols are grouped according to their primary purpose.

Protocol name

Group description

Short name

Metadata (Hash) Retrieval

Server Message Block (SMB) Version 2.1 Protocol

SMB 2.1 and HTTP are the current protocols that are enabled for metadata retrieval.

[MS-SMB2]

Peer Content Caching and Retrieval: HTTP Extensions

Specifies a content encoding known as PeerDist that is used by an HTTP/1.1 client and an HTTP/1.1 server to communicate content to each other. The primary role in Content Caching and Retrieval is metadata (hash) retrieval.

[MS-PCCRTP]

File Retrieval

Server Message Block (SMB) Version 2.1 Protocol

SMB2 version 2.1 and HTTP (as described in [MS-PCCRTP] specifies content encoding over HTTP) are the two protocols used for file retrieval that are content caching aware.

[MS-SMB2]

Peer Content Caching and Retrieval: HTTP Extensions

Specifies a content encoding known as PeerDist that is used by an HTTP/1.1 client and an HTTP/1.1 server to communicate content to each other. The primary role in Content Caching and Retrieval is metadata (hash) retrieval.

[MS-PCCRTP]

 

Content Identification

Peer Content Caching and Retrieval: Content Identification

A binary data structure that is used for content identification.

[MS-PCCRC]

Content Discovery

Peer Content Caching and Retrieval Discovery Protocol

Based on the Web Services Dynamic Discovery (WS-Discovery) protocol [WS-Discovery]. There are two modes of operations in WS-Discovery: client-initiated probes and service-initiated announcements; both are sent through IP multicast to a predefined group.

[MS-PCCRD]

Content Retrieval

Peer Content Caching and Retrieval: Retrieval Protocol

Content in the form of blocks is transferred by using HTTP, with the message format, as described in [MS-PCCRR].

[MS-PCCRR]

Authentication

Transport Layer Security (TLS)

Hosted server authentication uses HTTP/HTTPS for secure transport of hosted content, as described in [MS-PCHC].<6> [MS-TLSP] describes the Windows implementation of TLS.

[MS-TLSP]

RFC 4559

Client authentication, as described in [RFC4559]. When a hosted cache server is used, SPNEGO HTTP client authentication can be enabled. For more information on SPNEGO see [MS-SPNG] and [MS-NEGOEX].

[RFC4559]