Differences between revisions 3 and 4
Revision 3 as of 2008-10-22 11:30:07
Size: 2150
Comment:
Revision 4 as of 2008-10-22 11:36:10
Size: 2423
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
The standardised SCS (Simulcrypt Synchroniser) to ECMG (Entitlement Control Message Generator) interface is used to allow multiple key management systems to operate in parallel, each generating its own (typically proprietary) ECMs (Entitlement Control Messages).
Line 12: Line 13:
 * [[TCP]]: For the SCS (Simulcrypt Synchroniser) to ECMG (Entitlement Control Message Generator), SIMULCRYPT uses [[TCP]] as its transport protocol. There is no well known TCP port for SIMULCRYPT traffic as multiple TCP connections are possible (typically each TCP connection is associated to a given key management system for a particular TV channel).  * [[TCP]]: For the SCS to ECMG, SIMULCRYPT uses [[TCP]] as its transport protocol. There is no well known TCP port for SIMULCRYPT traffic as multiple TCP connections are possible (typically each TCP connection is associated to a given key management system for a particular TV channel).
Line 48: Line 49:
 * [[http://www.ietf.org/rfc/rfc123.txt|RFC 123]] ''The RFC title'' - explanation of the RFC content.  * [[http://pda.etsi.org/pda/queryform.asp]] '' ETSI TS 103 197 V1.5.1 (2008-10)'' - Digital Video Broadcasting (DVB);Head-end implementation of DVB SimulCrypt, latest version.

Simulcrypt (Simulcrypt)

A DVB protocol published by ETSI used in IPTV / broadcast TV head-ends to enable use of multiple key management systems. The standardised SCS (Simulcrypt Synchroniser) to ECMG (Entitlement Control Message Generator) interface is used to allow multiple key management systems to operate in parallel, each generating its own (typically proprietary) ECMs (Entitlement Control Messages).

History

XXX - add a brief description of PROTO history

Protocol dependencies

  • TCP: For the SCS to ECMG, SIMULCRYPT uses TCP as its transport protocol. There is no well known TCP port for SIMULCRYPT traffic as multiple TCP connections are possible (typically each TCP connection is associated to a given key management system for a particular TV channel).

Example traffic

XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot).

Wireshark

The PROTO dissector is (fully functional, partially functional, not existing, ... whatever the current state is). Also add info of additional Wireshark features where appropriate, like special statistics of this protocol.

Preference Settings

(XXX add links to preference settings affecting how PROTO is dissected).

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.

Display Filter

A complete list of PROTO display filter fields can be found in the display filter reference

  • Show only the PROTO based traffic:

     proto 

Capture Filter

You cannot directly filter PROTO protocols while capturing. However, if you know the TCP port used (see above), you can filter on that one.

  • Capture only the PROTO traffic over the default port (80):

     tcp port 80 

  • add link to PROTO specification and where to find additional info on the web about it, e.g.:
  • http://pda.etsi.org/pda/queryform.asp ETSI TS 103 197 V1.5.1 (2008-10) - Digital Video Broadcasting (DVB);Head-end implementation of DVB SimulCrypt, latest version.

Discussion

SIMULCRYPT (last edited 2010-10-05 19:07:27 by GuyHarris)