1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T X.609.1 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2016) SERIES X: DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY OSI networking and system aspects Networking Managed P2P communications: Peer activity manag
2、ement protocol (PAMP) Recommendation ITU-T X.609.1 ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY PUBLIC DATA NETWORKS Services and facilities X.1X.19 Interfaces X.20X.49 Transmission, signalling and switching X.50X.89 Network aspects X.90X.149 Maintenance X.15
3、0X.179 Administrative arrangements X.180X.199 OPEN SYSTEMS INTERCONNECTION Model and notation X.200X.209 Service definitions X.210X.219 Connection-mode protocol specifications X.220X.229 Connectionless-mode protocol specifications X.230X.239 PICS proformas X.240X.259 Protocol Identification X.260X.2
4、69 Security Protocols X.270X.279 Layer Managed Objects X.280X.289 Conformance testing X.290X.299 INTERWORKING BETWEEN NETWORKS General X.300X.349 Satellite data transmission systems X.350X.369 IP-based networks X.370X.379 MESSAGE HANDLING SYSTEMS X.400X.499 DIRECTORY X.500X.599 OSI NETWORKING AND SY
5、STEM ASPECTS Networking X.600X.629 Efficiency X.630X.639 Quality of service X.640X.649 Naming, Addressing and Registration X.650X.679 Abstract Syntax Notation One (ASN.1) X.680X.699 OSI MANAGEMENT Systems management framework and architecture X.700X.709 Management communication service and protocol
6、X.710X.719 Structure of management information X.720X.729 Management functions and ODMA functions X.730X.799 SECURITY X.800X.849 OSI APPLICATIONS Commitment, concurrency and recovery X.850X.859 Transaction processing X.860X.879 Remote operations X.880X.889 Generic applications of ASN.1 X.890X.899 OP
7、EN DISTRIBUTED PROCESSING X.900X.999 INFORMATION AND NETWORK SECURITY X.1000X.1099 SECURE APPLICATIONS AND SERVICES X.1100X.1199 CYBERSPACE SECURITY X.1200X.1299 SECURE APPLICATIONS AND SERVICES X.1300X.1399 CYBERSECURITY INFORMATION EXCHANGE X.1500X.1599 CLOUD COMPUTING SECURITY X.1600X.1699 For fu
8、rther details, please refer to the list of ITU-T Recommendations. Rec. ITU-T X.609.1 (06/2016) i Recommendation ITU-T X.609.1 Managed P2P communications: Peer activity management protocol (PAMP) Summary Recommendation ITU-T X.609.1 specifies a peer activity management protocol (PAMP) that runs on tw
9、o interfaces: 1) an interface between a peer activity management server (PAMS) and a peer; 2) an interface between a PAMS and an overlay management server (OMS). A PAMP is used to deliver peer activity status information with the goal of optimization of the overlay network. Peer activity status info
10、rmation includes both static and dynamic status information. Recommendation ITU-T X.609.1 provides the requirements, protocol operations, and message formats used in each operation for a PAMP. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T X.609.1 2016-06-13 11 11.1002/1000
11、/12886 Keywords Managed P2P, PAMP, PAMS, peer activity management. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T X.609.1 (0
12、6/2016) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible
13、for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T st
14、udy groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basi
15、s with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory
16、provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use
17、 of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no p
18、osition concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protec
19、ted by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2016 All rights reserved. No part of
20、 this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T X.609.1 (06/2016) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations a
21、nd acronyms 2 5 Conventions 3 6 Overview . 3 7 Requirements of a PAMP . 5 7.1 General requirements 5 7.2 Protocol requirements . 6 7.2.1 Operations . 6 8 Protocol operation . 8 8.1 Basic operations 8 8.2 Extended operations . 10 9 Messages . 18 9.1 Resource element type 18 9.2 Message format 23 Bibl
22、iography. 33 Rec. ITU-T X.609.1 (06/2016) 1 Recommendation ITU-T X.609.1 Managed P2P communications: Peer activity management protocol (PAMP) 1 Scope This Recommendation specifies a peer activity management protocol (PAMP). The purpose of a PAMP is to collect and exchange peer activity status inform
23、ation. A PAMP is used among a peer activity management server (PAMS), an overlay management server (OMS), and the peer, which are involved in managed peer-to-peer (P2P) communications. The scope of this Recommendation covers: the requirements of a PAMP based on ITU-T X.609; the protocol operation of
24、 a PAMP; the messages and parameters used by a PAMP. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recomm
25、endations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly
26、published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T X.609 Recommendation ITU-T X.609 (2015), Managed peer-to-peer (P2P) communications: Functional architecture. IETF RFC 7231 IETF RFC 7231 (2014), Hypert
27、ext Transfer Protocol (HTTP/1.1), Semantics and Content. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 fragment ITU-T X.609: A piece of the shared content. 3.1.2 functional entity b-ITU-T Y.2012: An entity that comprises an indivisibl
28、e set of specific functions. Functional entities are logical concepts, while groupings of functional entities are used to describe practical, physical implementations. 3.1.3 managed peer-to-peer b-ISO/IEC TR 20002: P2P with manageability features to manage the P2P-based service and P2P network by th
29、e P2P participants such as P2P service provider, ISP, and peer. 3.1.4 overlay network b-ITU-T X.1162: An overlay network is a virtual network that runs on top of another network. Like any other network, the overlay network comprises a set of nodes and links between them. Because the links are logica
30、l ones, they may correspond to many physical links of the underlying network. 3.1.5 peer b-ITU-T X.1161: Communication node on P2P network that functions simultaneously as both “client“ and “server“ to the other nodes on the network. 2 Rec. ITU-T X.609.1 (06/2016) 3.1.6 peer-to-peer (P2P) b-ITU-T Y.
31、2206: A system is considered to be P2P if the nodes of the system share their resources in order to provide the service the system supports. The nodes in the system both provide services to other nodes and request services from other nodes. 3.1.7 peer status information ITU-T X.609: Both dynamic and
32、 static status information of a peer. The dynamic status information describes the activity of peer in the participating overlay network. The static status information describes a peers activity configuration. 3.1.8 reference point b-ITU-T Y.2012: A conceptual point at the conjunction of two non-ove
33、rlapping functional entities that can be used to identify the type of information passing between these functional entities. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 JavaScript object notation (JSON): A lightweight, text-based, language-independ
34、ent data interchange format. NOTE Definition based on that given in b-IETF RFC 7159. 3.2.2 leech; leecher: A peer possessing none or some of fragments composing the content shared among peers participating in the same overlay network. A leech can upload its fragments to other peers and it can also d
35、ownload fragments from other peers. 3.2.3 seed; seeder: A peer possessing all fragments composing the content shared among peers participating in the same overlay network. A seed can upload fragments to other peers, but it does not download any fragment. 3.2.4 uniform resource identifier (URI): A si
36、mple and extensible means for identifying a resource. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CS Cache Server DHT Distributed Hash Table FE Functional Entity FQDN Fully Qualified Domain Name HTTP Hypertext Transfer Protocol ID Identifier IXS In
37、dex Server JSON JavaScript Object Notation MP2P Managed Peer-to-Peer N/A Not Applicable OIM Overlay Information Management OMS Overlay Management Server ONIM Overlay Network Information Management PAIM Peer Activity Information Management PAM Peer Activity Management Rec. ITU-T X.609.1 (06/2016) 3 P
38、AMP Peer Activity Management Protocol PAMS Peer Activity Management Server P2P Peer-to-Peer PIA Peer Information Analysis PLM Peer List Management PLO Peer List Optimization PPIM Peer Profile Information Management PPM Peer Profile Management REST Representational State Transfer RS Relay Server RSM
39、Resource Status Management TLS Transport Layer Security UMS User Management Server UNIS Underlying Network Information Server VoIP Voice over Internet Protocol 5 Conventions In this Recommendation: The keywords “is required to“ indicate a requirement which must be strictly followed and from which no
40、 deviation is permitted, if conformance to this Recommendation is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. The keywords “can optionally“ indicate an o
41、ptional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendors implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may op
42、tionally provide the feature and still claim conformance with the specification. 6 Overview Peer-to-peer (P2P) networking is a decentralized communication, where the participants, called peers, can directly communicate with each other. P2P networking enables one peers resources to be shared with oth
43、er peers in the same P2P network. The P2P network is self-organized, composed of peers capable of adapting to the dynamics of a peer without central coordination. P2P networking has been used in various applications, such as file distribution, VoIP and multimedia streaming. However, P2P networking i
44、ncurs problems such as load concentration on a specific peer and free-riding. Managed peer-to-peer (MP2P) aims to provide manageability features to the P2P network in order to solve or alleviate concerns about P2P networking. Peers organizing a P2P network are equally privileged, but may not have th
45、e same amount of resources. In other words, a peer with more resources can contribute more than peers with fewer resources. Peers may want to retrieve data from peers with abundant resources. However, this can impose a burden on the specific peer that results in an inefficient P2P network. Thus the
46、amount of burden imposed on each peer needs to be considered when setting up an efficient P2P network. To 4 Rec. ITU-T X.609.1 (06/2016) achieve this, ITU-T X.609 has defined an entity, called a peer activity management server (PAMS). A PAMS collects peer activity status information from peers. Peer
47、 activity status information is based on an abstract view of peer activity in the overlay network. These views provide status information about the overlay network for an overlay management server (OMS) to effectively utilize them. A peer can also utilize this information to select the appropriate p
48、eers for retrieving data. Figure 1 shows reference points among entities for MP2P communications. This Recommendation describes a peer activity management protocol (PAMP) and its related interfaces, denoted as R1 and R2 in Figure 1. Figure 1 Framework and interface of an MP2P ITU-T X.609 A PAMS coll
49、ects and analyses the status information received from peers. The PAMS can provide analysis results to an OMS to be utilized to set up an overlay network. Figure 2 shows functional entities (FEs) and their interactions to support PAMP operations. A PAMS has the following FEs involved in the PAMP: a peer activity information management (PAIM) FE manages peer dynamic activity information; a peer profile information management (PPIM) FE manages peer static information; a peer informati
