Revision Summary Date Revision History Revision Class Comments 12/5/2008 0.1 Major Initial Availability 1/16/2009 0.2 Minor Clarified the meaning of the technical content. 2/27/2009 0.2.1 Editorial Changed language and formatting in the technical content. 4/10/2009 1.0 Updated and revised the technical content. 5/22/2009 1.1 Minor Clarified the meaning of the technical content. 7/2/2009 1.1.1 Editorial Changed language and formatting in the technical content. 8/14/2009 1.2 Minor Clarified the meaning of the technical content. 9/25/2009 1.3 Minor Clarified the meaning of the technical content. 11/6/2009 1.4 Minor Clarified the meaning of the technical content. 12/18/2009 1.5 Minor Clarified the meaning of the
technical content. 1/29/2010 1.6 Minor Clarified the meaning of the technical content. 3/12/2010 1.6.1 Editorial Changed language and formatting in the technical content. 4/23/2010 1.6.2 Editorial Changed language and formatting in the technical content. 6/4/2010 1.6.3 Editorial Changed language and formatting in the technical content. 7/16/2010 1.6.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 1.6.3 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 1.6.4 Editorial Changed language and formatting in the technical content.
11/19/2010 1.6.4 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 1.6.4 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 1.6.4 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 1.6.4 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 1.6.4 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 1.7 Minor Clarified the meaning of the technical content. 9/23/2011 1.7 None No changes to the meaning, language, or formatting
Security Security Considerations for Implementers Peer Content Caching and Retrieval: Hosted Cache Protocol messages are secured using HTTPS. An HTTPS connection is established by the client with the hosted cache, where the hosted cache can choose to authenticate clients and a higher layer or administrator action can configure it to stop authenticating clients. HTTP authentication is the mechanism used to complete these actions as specified in . Index of Security Parameters Security Parameter Section HTTPS
Index A Abstract data 20 18 9 B 14 C Cache - hosted 24 23 25 23 24 10 29 Client 20 21 21 22 message processing 21 21 22 21 22 20 sequencing rules 21 21 22 21 22 20 12 D Data model - abstract 20 18 E Examples 24 23 25 23 24 F 10 G 6 H Higher-layer triggered events 21 18 Hosted cache 24 23 25 23 24 21 I 26 26 8 13 Initialization 21 18 6 L Local events 22 20 M Message processing client 21 21 22 21 server 19 18 19 19 12 Messages 11 16 11 11 N 8 O local events
22 20 8 P 26 26 9 9 27 Protocol Details 18 R 8 8 8 9 11 11 16 16 16 S Security 26 26 13 Sequencing rules client 21 21 22 21 server 19 18 19 19 Server 18 18 18 20 message processing 19 18 19 19 20 18 sequencing rules 19 18 19 19 20 18 10 11 T events 22 20 Timers 20 18 29 11 16 Triggered events - higher-layer 21 18 V 10 10