[vc_empty_space][vc_empty_space]
Key management analysis of secure real time protocol version 2
Seftyanto D.a, Kurniawan Y.a
a School of Electrical and Informatics, Institut Teknologi Bandung, Bandung, Indonesia
[vc_row][vc_column][vc_row_inner][vc_column_inner][vc_separator css=”.vc_custom_1624529070653{padding-top: 30px !important;padding-bottom: 30px !important;}”][/vc_column_inner][/vc_row_inner][vc_row_inner layout=”boxed”][vc_column_inner width=”3/4″ css=”.vc_custom_1624695412187{border-right-width: 1px !important;border-right-color: #dddddd !important;border-right-style: solid !important;border-radius: 1px !important;}”][vc_empty_space][megatron_heading title=”Abstract” size=”size-sm” text_align=”text-left”][vc_column_text]© 2017 IEEE.Secure Real Time (SRT) is a protocol for ensuring confidentiality, integrity, authenticity, non-repudiation and resists of replay attacks for end-to-end messaging, specifically over instant messaging (chatting) networks. The SRT uses many cryptography keys with different algorithms and crypto period, but in the first version has not been managed to keep the key protected during its lifecycle. In this paper, we describe the results of key management of SRT protocol by considering the system requirements, recommendations and opinions of key management observers. In addition to identifying the keys involved, we determine the key management policy. In addition to identifying the SRT stage in each key management life cycle phase, we add stages that are not yet present in SRT. Accordingly, the contribution of this paper is to provide the key management analysis results of the previous SRT protocol, which is to produce the protocol design of SRT version 2 and its key management policy.[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Author keywords” size=”size-sm” text_align=”text-left”][vc_column_text]chatting,Instant messaging,Key management,Non repudiation,Protocol design,Real time protocols,Replay attack,System requirements[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Indexed keywords” size=”size-sm” text_align=”text-left”][vc_column_text]chatting,key management,protocol cryptography[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Funding details” size=”size-sm” text_align=”text-left”][vc_column_text][/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”DOI” size=”size-sm” text_align=”text-left”][vc_column_text]https://doi.org/10.1109/ICITSI.2017.8267955[/vc_column_text][/vc_column_inner][vc_column_inner width=”1/4″][vc_column_text]Widget Plumx[/vc_column_text][/vc_column_inner][/vc_row_inner][/vc_column][/vc_row][vc_row][vc_column][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][/vc_column][/vc_row]