BS ISO/IEC 16512-2:2016
$215.11
Information technology. Relayed multicast protocol: Specification for simplex group applications
Published By | Publication Date | Number of Pages |
BSI | 2016 | 132 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | Blank Page |
7 | CONTENTS |
9 | Introduction |
11 | 1 Scope 2 References 2.1 Identical Recommendations | International Standards 2.2 Additional references |
12 | 3 Definitions 3.1 Terms defined elsewhere 3.2 Terms defined in this Recommendation |
13 | 4 Abbreviations and acronyms |
14 | 5 Conventions |
15 | 6 Overview 6.1 Overview of basic RMCP-2 6.1.1 RMCP-2 service |
16 | 6.1.2 RMCP-2 entities 6.1.3 Protocol modules of RMCP-2 |
18 | 6.1.4 RMCP-2 control model 6.1.5 Simplex delivery model of RMCP-2 |
19 | 6.2 Overview of secure RMCP-2 6.2.1 Secure RMCP-2 entities |
20 | 6.2.2 Session manager 6.2.3 Dedicated multicast agents Key/message security management module Group/member security management module |
21 | 6.2.4 Sender and receiver multicast agents 6.2.5 Protocol modules of secure RMCP-2 |
22 | 6.2.6 Structure of regional security management 6.3 Types of RMCP-2 messages |
23 | 7 Protocol operation for basic RMCP-2 7.1 Session manager’s operation 7.1.1 Session initiation 7.1.1.1 Normal procedure |
24 | 7.1.1.2 Handling SID duplication 7.1.2 Membership control 7.1.2.1 Membership subscription 7.1.2.1.1 MAID allocation 7.1.2.1.2 Handling extended information |
25 | 7.1.2.2 Member expulsion 7.1.3 Heartbeat 7.1.4 Session monitoring |
26 | 7.1.5 Session termination 7.2 Multicast agent’s operation 7.2.1 Session subscription 7.2.1.1 Subscription of an SMA |
27 | 7.2.1.2 Subscription of an MA 7.2.2 Neighbour discovery 7.2.2.1 Neighbour discovery in a multicast network 7.2.2.1.1 Role of an HMA |
28 | 7.2.2.1.2 HMA discovery 7.2.2.1.3 New HMA election |
29 | 7.2.2.1.4 Handling HANNOUNCE message contention 7.2.2.1.5 HMA continuity |
30 | 7.2.2.2 Neighbour discovery in the unicast network 7.2.2.2.1 Neighbour discovery |
31 | 7.2.2.2.2 Exploring more 7.2.2.2.3 Selecting a PMA candidate using system information 7.2.2.2.4 Selecting a PMA candidate through distance measurement 7.2.3 Session join |
32 | 7.2.4 Leave 7.2.4.1 Leave at own will 7.2.4.1.1 MA leave in a unicast network |
33 | 7.2.4.1.2 MA leave in a multicast network |
34 | 7.2.4.2 Parent switching |
35 | 7.2.4.3 MA expulsion 7.2.4.3.1 Expulsion by PMA 7.2.4.3.2 Expulsion by SM |
36 | 7.2.4.4 SMA leave 7.2.5 Maintenance 7.2.5.1 Heartbeat 7.2.5.2 Monitoring |
37 | 7.2.5.3 Fault detection and recovery |
38 | 7.2.5.3.1 Loop detection and prevention 7.2.5.3.2 Network partition detection and recovery |
40 | 7.2.5.4 Tree reconstruction |
41 | 7.2.6 Termination 8 Protocol operation for secure RMCP-2 8.1 Session manager’s operation 8.1.1 Admission control 8.1.1.1 TLS authentication 8.1.1.2 Admission of the SMA |
42 | 8.1.1.3 Admission of DMAs 8.1.1.4 Admission of RMAs to open groups 8.1.1.5 Admission of RMAs to closed groups 8.1.2 Key management for which the SM is responsible 8.1.2.1 Session key |
43 | 8.1.2.2 TLS key 8.1.3 Establishment of security policy 8.1.4 Agreement of security mechanisms 8.1.4.1 Agreement between SMA and DMAs |
44 | 8.1.4.2 Agreement between RMAs 8.1.5 Access control for RMAs |
45 | 8.2 Multicast agent’s operation 8.2.1 Key management for which the SMA and DMAs are responsible 8.2.1.1 Group key management 8.2.1.2 Content encryption key management 8.2.1.3 Membership authentication key 8.2.2 Secure session subscription |
46 | 8.2.3 Membership authentication for joining the RMCP tree 8.2.4 Secure tree join |
47 | 8.2.5 Secure tree leave 8.2.5.1 Leave of RMA from a multicast network and unicast network 8.2.5.2 Leave of HMA from a multicast network |
48 | 8.2.5.3 Leave of DMA from a unicast network |
49 | 8.2.6 Message encryption/decryption |
50 | 8.2.7 Encryption/decryption and delivery of content data 9 RMCP-2 message format |
51 | 9.1 Common format of RMCP-2 message 9.2 Control data format 9.2.1 Common control format 9.2.2 Common sub-control format |
52 | 9.2.3 Formatting multiple controls 9.3 RMCP-2 messages 9.3.1 SUBSREQ message |
53 | 9.3.2 SUBSANS message |
54 | 9.3.3 PPROBREQ message |
55 | 9.3.4 PPROBANS message 9.3.5 HSOLICIT message |
56 | 9.3.6 HANNOUNCE message |
57 | 9.3.7 HLEAVE message |
58 | 9.3.8 RELREQ message |
59 | 9.3.9 RELANS message |
60 | 9.3.10 STREQ message |
61 | 9.3.11 STANS message |
62 | 9.3.12 STCOLREQ message |
63 | 9.3.13 STCOLANS message |
64 | 9.3.14 LEAVREQ message |
65 | 9.3.15 LEAVANS message 9.3.16 HB message |
66 | 9.3.17 FAILCHECK message |
67 | 9.3.18 TERMREQ message |
68 | 9.3.19 TERMANS message 9.3.20 SECAGREQ message |
69 | 9.3.21 SECLIST message |
70 | 9.3.22 SECALGREQ message |
71 | 9.3.23 SECAGANS message |
72 | 9.3.24 KEYDELIVER message 9.3.25 HRSREQ message |
73 | 9.3.26 HRSANS message |
74 | 9.4 RMCP-2 controls 9.4.1 RP_COMMAND control 9.4.2 SI_COMMAND control 9.4.3 DATAPROFILE control |
75 | 9.4.4 NEIGHBORLIST control 9.4.5 REASON control |
76 | 9.4.6 RESULT control 9.4.7 ROOTPATH control |
77 | 9.4.7.1 RP_XXX sub-control |
78 | 9.4.8 SYSINFO control 9.4.8.1 SI_UPTIME sub-control 9.4.8.2 SI_DELAY sub-control |
79 | 9.4.8.3 SI_ROOM_CMA sub-control 9.4.8.4 SI_PROV_BW sub-control 9.4.8.5 SI_POSS_BW sub-control |
80 | 9.4.8.6 SI_SND_BW sub-control 9.4.8.7 SI_SND_PACKET sub-control 9.4.8.8 SI_SND_BYTES sub-control |
81 | 9.4.8.9 SI_RCV_BW sub-control 9.4.8.10 SI_RCV_PACKET sub-control 9.4.8.11 SI_RCV_BYTES sub-control |
82 | 9.4.8.12 SI_TREE_CONN sub-control 9.4.8.13 SI_TREE_MEM sub-control |
83 | 9.4.9 TIMESTAMP control 9.4.10 CANDIDATEHMA control |
84 | 9.4.11 TREEEXPLOR control 9.4.12 COLLECT control 9.4.13 PSEUDO_HB control |
85 | 9.4.14 PARAMETER control |
86 | 9.4.15 SERV_USER_IDENT control 9.4.16 AUTH control 9.4.17 AUTH_ANS control |
87 | 9.4.17.1 KEY_MATERIAL sub-control 9.4.18 SMA_PROPOSE control |
88 | 9.4.19 GK_MECH_CAPAB control 9.4.20 EN_DEC_CAPAB control 9.4.21 AUTH_ALG_CAPAB control |
89 | 9.4.22 GK_MECH control 9.4.23 AUTH_MECH control |
90 | 9.4.24 CON_EN_DEC_ALG control 9.4.25 GK_EN_DEC_ALG control 9.4.26 AUTH_ALG control |
91 | 9.4.27 GK_MECH_DELIVER control 9.4.28 AUTH_MECH_DELIVER control |
92 | 9.4.29 CON_EN_DEC_DELIVER control 9.4.30 GK_EN_DEC_DELIVER control 9.4.31 AUTH_ALG_DELIVER control |
93 | 9.4.32 SEC_RETURN control 9.4.33 KEY_INFO control |
94 | 9.4.33.1 KEY_MATERIAL sub-control 9.4.34 ACL_LIST control 9.4.34.1 ACL_DATA sub-control 10 Parameters |
95 | 10.1 Identifications used in RMCP-2 10.1.1 Session ID 10.1.2 Multicast agent ID (MAID) 10.2 Code values used in RMCP-2 10.2.1 Codes values for basic RMCP-2 node types |
96 | 10.2.2 Code values for RMCP-2 message types 10.2.3 Code values for RMCP-2 control types |
97 | 10.3 Code values for sub-control types 10.3.1 Sub-control types for the ROOTPATH control |
98 | 10.3.2 Sub-control types for the SYSINFO control |
99 | 10.3.3 Sub-control types for a secure RMCP-2 10.4 Code values used in control 10.4.1 Reason code 10.4.2 Result code |
100 | 10.4.3 Return code 10.4.4 Key type code 10.5 Code values related to the security policy for a secure RMCP-2 |
101 | 10.6 Timer related parameters 10.6.1 Parameters for neighbour discovery |
102 | 10.6.2 Parameters for heartbeat 10.6.3 Parameters for report and monitoring 10.6.4 Parameters for HMA-related operation |
103 | 10.6.5 Parameters for maintenance of the tree 10.6.6 Parameters for session leave 10.7 Data profile used in RMCP-2 |
105 | A.1 Overview A.2 Authentication procedure |
107 | B.1 Overview B.2 Session information sharing between SMs |
108 | B.3 Supporting session subscription in RMCP-2 between multiple SMs |
109 | B.4 Supporting a session leave in RMCP-2 between multiple SMs |
110 | B.5 Other operations of the RMA in RMCP-2 between multiple SMs B.6 RMCP-2 messages for sharing session information between SMs B.6.1 SINFO |
111 | B.6.2 SMNOTI |
112 | C.1 Bootstrapping rule C.2 HMA selection rule |
113 | C.3 CMA acceptance rule C.4 Parent decision rule |
114 | C.5 Tree improvement rule C.6 PMA’s expulsion rule |
115 | D.1 Overview D.2 Data delivery scheme using IP-IP tunnel mechanism |
116 | D.3 Data delivery scheme using a non-encapsulation scheme |
118 | E.1 Overview E.2 Issues for a reliable data delivery scheme E.2.1 Data buffering E.2.2 Data sequence numbering |
119 | E.2.3 Retransmission request E.3 Operation E.3.1 Session join |
120 | E.3.2 Parent switching |
121 | E.4 Service data unit (SDU) format E.5 Data profile |
123 | F.1 Overview F.1.1 APIs F.1.2 Use of RMCP-2 API |
124 | F.2 RMCP-2 API functions F.2.1 Functions related to the MA control int rmcp2_socket (void) int rmcp2_bind(int sd, session_profile *profile, int profile_len) |
125 | int rmcp2_connect(int sd, struct sockaddr *sm_addr, int addrlen) int rmcp2_close(int sd) int rmcp2_setsockopt(int sd, int opt_type, char *opt, int optlen) int rmcp2_getsockopt(int sd, int opt_type, char *opt, int *optlen) F.2.2 Functions related to an MA’s data delivery int rmcp2_recv(int sd, char *buf, int len, int flags) int rmcp2_send(int sd, char *buf, int len, int flags) F.2.3 Functions related to session management SID rmcp2_session_open(session_profile *session_profile) int rmcp2_session_close(SID session_id) |
126 | int rmcp2_member_out(SID session_id, MAID maid) int rmcp2_status_report(SID session_id, int command, char *result, int *result_len) int rmcp2_char_change(SID session_id, int command, char *opt, int optlen) |