2.3.3 System Influences
The Content Caching and Retrieval protocols can be influenced by the external systems and components that are shown in the following table.
|
External entity |
Content Caching and Retrieval protocols depend on an external entity for |
Consequences if absent |
|---|---|---|
|
Authentication Services system |
Authenticating client and server principals. |
Centralized identity management does not work if the Domain Interaction System is not available. |
|
Group Policy system |
Configuration of individual capabilities within the Content Caching and Retrieval protocols. |
Cannot centrally configure some functionality of the system. |
|
Domain interaction system |
Content Caching and Retrieval to operate either in a domain or in a workgroup. Domain services are required for hosted cache client authentication. |
Hosted cache client authentication cannot function. |
|
File Access system |
File Access Services to which Content Caching and Retrieval is an adjunct. |
No file access and therefore no Content Caching and Retrieval. |
|
Web server |
HTTP Content Caching that depends on the availability of content that is delivered via HTTP. |
No HTTP content caching can be performed. |
|
Certification Authority system |
Hosted cache mode requires an X.509 certificate to authenticate. Either security protocol Secure Sockets Layer (SSL) or Transport Layer Security (TLS) may be used. TLS supersedes SSL and should be used in new development with a X509v3 certificate. See the following specifications [RFC2818], [RFC5246], [RFC5280]. |
Hosted cache communication will fail. |
Specific-system influences are as follows:
Group Policy enables a client to interact with the Content Cache Service, which is turned off by default. This enables a computer to act as both a client-role peer and client-role server, thereby publishing and retrieving content and metadata that are obtained from a content server.
The Background Intelligent Transfer Service (BITS) Upload Protocol, as described in [MC-BUP], specifies an HTTP 1.1-based upload protocol. This protocol is used to transfer large payloads from a client to a server or a server to a client over networks with frequent disconnections and to send notifications about the availability of uploaded payloads. This protocol is a client of the Content Caching and Retrieval protocols.