Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[802.3_ISAAC] Questions on Conrad presentation

Hi Conrad,

Just to recap the questions on your presentation.
  1. Pages 3-6 discuss ASA ML own ASEP, PTB, ASAsec
    I wanted to clarify if ASEP, PTB and ASAsec are proposed to be used with 802.3dm.
    Following the question from Mr. Zimmerman, my understanding is NO.
    This is OK for me. Just wanted to point out ASEP etc. cannot be re-used 1:1 as there will be MIPI CCPAL/A, IEEE1722 ACF GISF, PTP etc which are different than ASEP/PTB.

  2. Page 11 you mentionned only 5% overhead is considered
    When going over ethernet, CSI-2 (as well as I2C) will have additional protocol overhead for MIPI CCPAL/A, 1722 ACF GISF, ACF I2C (or GBB), MAC framing etc.
    Is 5% realistic here?
    Encapsulating CSI-2 raw data in Ethernet Frames requires:
    1. Network header: 18B (DA (6) + SA (6) + TPID (2) + TCI (2) + EtherType (2) = 18)
    2. AVTP header (1722): min is with NTSCF V0 = 12B; max is with TSCF V1 = 40B;
    3. GISF header: 20B
    4. SEP Header: min is 8B (more if CSE FuSa and/or Security is used)
    5. FCS: 4B
  3. To that Packet over head need to be added: Preamble (7) + SFD (1) + IPG (12) = 20B
    Taking only the minimum size for each layer overhead it adds 82 Bytes. With a regular 1500B payload it is already > 5%.

    Additional at minimum per each video frame (lowest overhead):
    • FuSa elements such as Message/Frame Counter and CRC-64
      Security elements such as MACsec header and ICV (or SEP's Message Authentication Code) will add to each video frame.

  4. The 8MP imager in the provided example may have to use 10G MAC rate mainly depending on the frame rate. This is more dominant than the protocol overhead. Why is the example stopping at 45fps?
Kind Regards
Ariel

To unsubscribe from the STDS-802-3-ISAAC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-ISAAC&A=1