1 / 7

Position of SDLS protocol functions in TM SDLP internal stack

Space Data Link Security Protocol Position of SDLS protocol functions in Space Data Link Protocols stack. Position of SDLS protocol functions in TM SDLP internal stack. Position of SDLS protocol functions in TM SDLP internal stack. Encryption/decryption :

gabby
Télécharger la présentation

Position of SDLS protocol functions in TM SDLP internal stack

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Space Data Link Security ProtocolPosition of SDLS protocol functions in Space Data Link Protocols stack

  2. Position of SDLS protocol functions in TM SDLP internal stack

  3. Position of SDLS protocol functions in TM SDLP internal stack • Encryption/decryption : • applicable to frame data field only, either from the packet service or from a private source (VCA service) • FSH and OCF left in the clear • Authentication / validation : • idea is to protect the full frame apart from the frame ECF (which should not be used if authentication is used on the given VC) • therefore should protect FSH and OCF whether they are inserted at VC level or MC level. • Nevertheless, MC_FSH and MC_OCF are not linked to VCs contrary to Security Associations • option : move authentication after virtual channel generation and do not authenticate fields which are not VC specific to be in line with Security Association concept

  4. Position of SDLS protocol functions in AOS SDLP internal stack

  5. Position of SDLS protocol functions in AOS SDLP internal stack • Encryption/decryption : • applicable to frame data field only, either from the packet service or bitstream service or from a private source (VCA service) • OCF left in the clear • Authentication / validation : • idea is to protect the full frame apart from the frame ECF (which should not be used if authentication is used on the given VC) • nevertheless, cannot protect the insert zone which is inserted synchronously when the transfer frame is sent to transmitter. Besides insert service is linked to a space link and not to a VC (or a MC) • no real need for insert authentication since inserts are real-time TDM data or audio/video relatively robust to spoofing

  6. Position of SDLS protocol functions in TC SDLP internal stack

  7. Position of SDLS protocol functions in TC SDLP internal stack • Encryption/decryption : • applicable to frame data field only, either from the MAP service, packet service or from a private source (VCA service), or from COP management service (2 types of commands : unlock, set V(r)) • ciphering COP control commands is debatable since those commands do not carry any user sensitive information • Authentication / validation : • idea is to protect the full frame apart from the frame ECF (which should not be used if authentication is used on the given VC) • all fields of TC transfer frame are VC specific and are generated by VC generation function. Therefore, authentication function should be placed after this function in the stack.

More Related