<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing with OASIS Tables v3.0 20080202//EN" "journalpub-oasis3.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:oasis="http://docs.oasis-open.org/ns/oasis-exchange/table" dtd-version="3.0">
  <front>
    <journal-meta>
<journal-id journal-id-type="publisher">ARS</journal-id>
<journal-title-group>
<journal-title>Advances in Radio Science</journal-title>
<abbrev-journal-title abbrev-type="publisher">ARS</abbrev-journal-title>
<abbrev-journal-title abbrev-type="nlm-ta">Adv. Radio Sci.</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">1684-9973</issn>
<publisher><publisher-name>Copernicus GmbH</publisher-name>
<publisher-loc>Göttingen, Germany</publisher-loc>
</publisher>
</journal-meta>

    <article-meta>
      <article-id pub-id-type="doi">10.5194/ars-13-149-2015</article-id><title-group><article-title>A test method for analysing disturbed ethernet data streams</article-title>
      </title-group><?xmltex \runningtitle{A test method for analysing disturbed ethernet data streams}?><?xmltex \runningauthor{M.~Kreitlow et al.}?>
      <contrib-group>
        <contrib contrib-type="author" corresp="yes" rid="aff1">
          <name><surname>Kreitlow</surname><given-names>M.</given-names></name>
          <email>matthiaskreitlow@bundeswehr.org</email>
        </contrib>
        <contrib contrib-type="author" corresp="no" rid="aff1">
          <name><surname>Sabath</surname><given-names>F.</given-names></name>
          
        </contrib>
        <contrib contrib-type="author" corresp="no" rid="aff2">
          <name><surname>Garbe</surname><given-names>H.</given-names></name>
          
        <ext-link>https://orcid.org/0000-0003-1601-1321</ext-link></contrib>
        <aff id="aff1"><label>1</label><institution>Bundeswehr Research Institute for Protective
Technologies and NBC Protection, Munster, 29633 Germany</institution>
        </aff>
        <aff id="aff2"><label>2</label><institution>Institute of Electrical Engineering and Measurement Technology, Leibniz University Hannover, Hannover, 30167 Germany</institution>
        </aff>
      </contrib-group>
      <author-notes><corresp id="corr1">M. Kreitlow (matthiaskreitlow@bundeswehr.org)</corresp></author-notes><pub-date><day>3</day><month>November</month><year>2015</year></pub-date>
      
      <volume>13</volume>
      <issue>5</issue>
      <fpage>149</fpage><lpage>153</lpage>
      <history>
        <date date-type="received"><day>13</day><month>January</month><year>2015</year></date>
           <date date-type="rev-recd"><day>12</day><month>May</month><year>2015</year></date>
           <date date-type="accepted"><day>22</day><month>May</month><year>2015</year></date>
      </history>
      <permissions>
<license license-type="open-access">
<license-p>This work is licensed under a Creative Commons Attribution 3.0 Unported License. To view a copy of this license, visit <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/3.0/">http://creativecommons.org/licenses/by/3.0/</ext-link></license-p>
</license>
</permissions><self-uri xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015.html">This article is available from https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015.html</self-uri>
<self-uri xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015.pdf">The full text article is available as a PDF file from https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015.pdf</self-uri>


      <abstract>
    <p>Ethernet connections, which are widely used in many computer networks, can
suffer from electromagnetic interference. Typically, a degradation of the
data transmission rate can be perceived as electromagnetic disturbances lead
to corruption of data frames on the network media. In this paper a
software-based measuring method is presented, which allows a direct
assessment of the effects on the link layer. The results can directly be
linked to the physical interaction without the influence of software related
effects on higher protocol layers. This gives a simple tool for a
quantitative analysis of the disturbance of an Ethernet connection based on
time domain data. An example is shown, how the data can be used for further
investigation of mechanisms and detection of intentional electromagnetic
attacks.</p>
  </abstract>
    </article-meta>
  </front>
<body>
      

<sec id="Ch1.S1" sec-type="intro">
  <title>Introduction</title>
      <p>Ethernet following the IEEE 802.3 standard <xref ref-type="bibr" rid="bib1.bibx4" id="paren.1"/> is a
technique, which is used in many network environments. At least the lowest
level in big network installations is usually realised with CAT5e copper
twisted pair lines for signal transmission. This enables for data
transmission using the variant 1000BASE-T, which is also known as Gigabit
Ethernet. Twisted pair lines of the category CAT5e do not require a metallic
shielding. Therefore, these lines are more susceptible against radiated
electromagnetic interferences. Especially intentional interferences have been
subject of many investigations over the past years
<xref ref-type="bibr" rid="bib1.bibx8 bib1.bibx6 bib1.bibx9 bib1.bibx3" id="paren.2"/>. Amongst others, it
was shown that interference from high-power electromagnetics (HPEM) can have
a dramatic impact on data transmissions over Ethernet networks.</p>
      <p>Typically the effects can be perceived on the application layer with regard
to their criticality, e.g. when the data transmission rate of a file transfer
drops significantly or an interactive network application like voice-over-IP
shows big lags <xref ref-type="bibr" rid="bib1.bibx13" id="paren.3"/>. In practise, it is very hard to find out
what exactly is causing such a behaviour as the effects on application layer
are normally not directly linked to the physical interaction. Figure <xref ref-type="fig" rid="Ch1.F1"/>
illustrates the process of logical communication within
modern IP networks and physical interaction on the basis of the TCP/IP
reference model <xref ref-type="bibr" rid="bib1.bibx11" id="paren.4"/>. This model can be considered as simpolified
breakdown of the more general OSI layer model <xref ref-type="bibr" rid="bib1.bibx5" id="paren.5"/>.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F1"><caption><p>Communication with the TCP/IP reference model.</p></caption>
        <?xmltex \igopts{width=213.395669pt}?><graphic xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015-f01.pdf"/>

      </fig>

      <p>Errors within the communication can be caused by a hardware problem, a
bottle-neck in the network infrastructure due to high utilization or even by
a intentional electromagnetic interference (IEMI). Observing and detecting
the last-mentioned is a real challenge. Reliable detection with field
monitors is still subject of ongoing research and in big network
infrastructures an effective field monitoring will probably be a high cost
factor <xref ref-type="bibr" rid="bib1.bibx2" id="paren.6"/>.</p>
      <p>Therefore a new approach shall be discussed which allows for observation of
disturbed data transmissions over an Ethernet network. Software-related
effects on higher protocol layers, like control algorithms reacting to data
errors, have to bypassed. It will be shown that a practical software
implementation of a new test method gives a finely granulated time resolution
of Ethernet frames and disturbances on the physical layer. This data can be
used for further analysis to detect IEMI. Additionally this new method allows
for testing network equipment with comparable results independently from user
applications and specific software environments.</p>
</sec>
<sec id="Ch1.S2">
  <title>Error mechanisms in classical TCP based communication</title>
      <p>Many network applications, such as file transfers, require a reliable data
transmission. Altering or loss of data is unacceptable. Therefore typical
techniques, like the file transfer protocol (FTP), utilize the transmission
control protocol (TCP) on the transport layer, as this protocol offers
integrated security measures. TCP operates on top of the IP protocol
<xref ref-type="bibr" rid="bib1.bibx12" id="paren.7"/>. Whereas IP is only responsible for the logical routing of
data packets from one destination to another through the network topology,
TCP opens the communication endpoint for an application.</p>
      <p>When testing a network for effects due to EMI, traffic has to be generated.
This is often done by simply copying a file from one computer to another
while the interference is present <xref ref-type="bibr" rid="bib1.bibx1" id="paren.8"/>. This approach presents a
problem, as the TCP protocol's integrated security mechanisms will react to
occurring packet losses and delays. Therefore, the perceived effects are not
linked to the physical processes on the network cables or within the
computers. In <xref ref-type="bibr" rid="bib1.bibx14" id="text.9"/> and <xref ref-type="bibr" rid="bib1.bibx7" id="text.10"/> it was shown that an observed
drop of the transmission speed can be a result of the control algorithms,
although the physical degradation of the network is not very strong.</p>
      <p>To conclude this, it can be said that investigating an IT network under the
influence of EMI with TCP based applications will only give information on
this specific network application in a specific network environment. This
data is hardly comparable, as the TCP implementation will act as a “black
box”. To overcome these issues s new method shall be implemented.</p>
</sec>
<sec id="Ch1.S3">
  <title>Design of a new test method</title>
      <p>The basic idea for a new measuring method is not to use a “black box”
software like a FTP server/client to generate load on the network, which can
be observed using network sniffing tools like Wireshark. Rather the data
stream itself shall be generated in a well defined way without the influence
of software based control algorithms. To achieve this, the user datagram
protocol (UDP) will be used. UDP is also a part of the network stack of every
modern operating system and operates on top of IP like TCP does
<xref ref-type="bibr" rid="bib1.bibx10" id="paren.11"/>.<?xmltex \hack{\newpage}?></p>
      <p>Compared to this, UDP is a stateless protocol that provides no security and
integrity checks on the transport layer. If a data packet gets lost or the
data gets corrupted within an UDP connection, there will be no way to detect
and handle this on protocol level as opposed to TCP. This makes UDP a very
simple protocol with less overhead, but for this reason the application
itself has to handle segmenting, flow-control and especially loss or
corruption of data. Exactly this behaviour of UDP will be used to detect
interferences without having influences of unknown control algorithms.</p>
<sec id="Ch1.S3.SS1">
  <title>Testing procedure</title>
      <p>As stated before the new method is based on UDP. It consists of a client,
which requests a data stream from the server addressed by its IP address. The
request itself is sent as an UDP datagram and defines all necessary testing
parameters. In particular these are the test duration in seconds and the
payload, which is the same for each packet to be sent. The payload size also
defines the actual size of the packet. Additionally, there is a possibility
to define delay-times for throttling the data transmission by inserting a
delay after each UDP datagram. This is usually set to zero to achieve the
maximum speed.</p>
      <p>After sending the request to the server, the client immediately starts
listening for incoming UDP datagrams originating from the servers IP address.
The server will process the request and start sending UDP datagrams back to
the clients IP address. The first four bytes of each datagram represent an
32-bit integer number, which acts as a sequence number. For each packet this
number is increased consecutively, then the packet is filled up with the
given payload up to the defined size. This process is running in a loop, that
stops, when the server has been sending data for the specified duration.</p>
      <p>On the other side of the connection the client will wait for incoming data.
If a UDP datagram from the sever arrives, the client will check first check
whether the payload specified in the request has been altered. This can be
handled as a corruption. In practical tests this will actually never happen
as data corruption due to bit flips will cause the frame check sequence of
this Ethernet frame to fail. If this happens, the whole frame will be
discarded. If an UDP datagram with the correct payload arrives, the sequence
number will be read from the first 4 bytes of the datagram. This sequence
number in combination with a time stamp is consecutively logged to a file.
The client will stop its receiving and logging process, when it receives no
datagrams for a specified time. After each test run, the logged data can be
analysed off-line. This file will have the following format, where the first
column is the time stamp in microseconds and the second column is the
sequence number: <italic>[time stamp];[SEQ#];</italic>.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F2" specific-use="star"><caption><p>Flowchart for the test procedure.</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015-f02.pdf"/>

        </fig>

      <?xmltex \floatpos{t}?><fig id="Ch1.F3" specific-use="star"><caption><p>Frame structure.</p></caption>
          <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015-f03.pdf"/>

        </fig>

      <p>The whole process is shown in Fig. <xref ref-type="fig" rid="Ch1.F2"/> as a flow chart. The
structure of each resulting Ethernet frame is illustrated in in Fig. <xref ref-type="fig" rid="Ch1.F3"/>.
It is obvious that each Ethernet frame corresponds to exactly
one UDP datagram and therefore to one unique sequence number. If an Ethernet
frame is discarded or lost, this can be directly seen in the log file as the
sequence number in the corresponding UDP datagram will not occur, because UDP
uses no techniques like retransmission or error correcting for securing the
data transmission. Also all following Ethernet frames will not be affected by
a single event due to the absence of flow control algorithms. By using this
behaviour of UDP and the implementation above it is possible to detect
interferences with the data transmission with a resolution down to single
Ethernet frames.</p>
</sec>
<sec id="Ch1.S3.SS2">
  <title>Implementation</title>
      <p>For a of concept the method was implemented in C as a Win32 application. The
software has a user interface as shown in Fig. <xref ref-type="fig" rid="Ch1.F4"/>. An off-line
analysis of the log file was done in MATLAB. However, there are some
limitations in this implementation. As every UDP datagram is unique and must
be generated in real-time, the maximum transmission speed is currently
limited to 7.5 Mbyte s<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula> at the moment. This is equivalent to approximately
5000 full-sized Ethernet frames (1538 bytes frame<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula>) per second. Using
high-resolution timers from Microsoft Windows, the time resolution is
basically in the range of microseconds. Actually the absolute precision of
this timers differs up to 10 % from the exact time in this testing set-up.
This is a consequence from the fact, that a high resolution and a good
absolute accuracy with negligible drift, while summing up each small time
step, is not possible at the same time using the software defined clock of an
operating system.<?xmltex \hack{\newpage}?></p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F4"><caption><p>User interface of the test software.</p></caption>
          <?xmltex \igopts{width=241.848425pt}?><graphic xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015-f04.png"/>

        </fig>

      <?xmltex \floatpos{t}?><fig id="Ch1.F5" specific-use="star"><caption><p>Topology of the test network.</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015-f05.pdf"/>

        </fig>

</sec>
</sec>
<sec id="Ch1.S4">
  <title>Test results</title>
      <p>The new method was used to perform some test of a IT network under the
influence of IEMI. A simple topology as shown in Fig. <xref ref-type="fig" rid="Ch1.F5"/> was set
up. Two computers PC1 and PC2 are connected over a line of switches SW1 to
SW4. The computers are connected to the switches using CAT5e twisted pair
cables. The switches SW2 and SW3 are also connected by twisted pair cables.
SW1 and SW2 as well as SW3 and SW4 are linked with an optical fibre. Using an
optical connection between these switches ensures that electromagnetic
disturbances can not spread out over the whole network when only one
component is exposed to interferences.</p>
<sec id="Ch1.S4.SS1">
  <title>Measuring data transmission rate</title>
      <p>Each line in the log file represents one UDP packet and therefore one
Ethernet frame. The size of the frame is defined within in the test software.
This information can be used to calculate the current data transmission rate
<inline-formula><mml:math display="inline"><mml:mi>R</mml:mi></mml:math></inline-formula> on the lowest layer as
            <disp-formula id="Ch1.E1" content-type="numbered"><mml:math display="block"><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mi>S</mml:mi><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo>-</mml:mo><mml:msub><mml:mi>t</mml:mi><mml:mrow><mml:mi>n</mml:mi><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mstyle><mml:mo>,</mml:mo></mml:mrow></mml:math></disp-formula>
          where <inline-formula><mml:math display="inline"><mml:mi>S</mml:mi></mml:math></inline-formula> is the size of the complete Ethernet frame, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mi>n</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> is the time
when the actual frame arrived and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mrow><mml:mi>n</mml:mi><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> is the time when the previous
frame arrived.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F6"><caption><p>Data transmission rate over time.</p></caption>
          <?xmltex \igopts{width=241.848425pt}?><graphic xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015-f06.pdf"/>

        </fig>

      <p>Figure <xref ref-type="fig" rid="Ch1.F6"/> shows the result for an experiment where PC2 was exposed
to ultra wide band (UWB) pulses with a a field-strength of 7.5 kV m<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula> and a
pulse repetition frequency of 100 Hz, while PC2 was sending data to PC1. The
data shows that the data transmission rate drops with every UWB pulse, but
almost no data gets corrupted. In this detailed view only at 11.065 s, where
the data rate drops to zero, a packet loss actually happens. From this data
it can be deduced, that the data transmission itself is not directly affected
most of the time, but the PC delays sending new data for a short time, when
it is affected by an UWB pulse.</p>
      <p>This time domain data can be used to detect intentional attacks on computers
as the pulse repetition frequency is reflected in the data transmission rate
measured with the new method. Otherwise it would be hard to detect due to the
absence of exorbitant packet loss, although the transmission speed within
applications will slow down.</p>
</sec>
<sec id="Ch1.S4.SS2">
  <title>Measuring of packet losses</title>
      <p>Corrupted Ethernet frames can be detected by enumerating the sequence numbers
in the log file. Without disturbances they should increase by one with each
line. If the difference between two sequence numbers of two subsequent lines
in the log file is higher than one, this indicates the number of missing
Ethernet frames. The time stamps give the time window for the data
corruption.</p>
      <p>Another experiment was done, where an error current was directly coupled into
the twisted pair cable between SW2 and SW3. The current also had the shape of
an UWB pulse and the pulse repetition frequency was set to 20 kHz. Figure <xref ref-type="fig" rid="Ch1.F7"/>
shows at which time Ethernet frames get corrupted due to the
interference. Each line in the diagram represents a corrupted frame. Although
the disturbance source was permanently activated, the errors occur in bursts.
The reason for this is a beat effect between the the packet rate
(<inline-formula><mml:math display="inline"><mml:mo>∼</mml:mo></mml:math></inline-formula> 5000 Hz) and the repetition
frequency of the source.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F7"><caption><p>Corrupted Ehernet frames over time.</p></caption>
          <?xmltex \igopts{width=241.848425pt}?><graphic xlink:href="https://ars.copernicus.org/articles/13/149/2015/ars-13-149-2015-f07.pdf"/>

        </fig>

      <p>The data show that it is possible to catch single disturbance for a data
stream with a high resolution in time. However due to the limited packet rate
not every single event on the link layer can be caught as the software is not
able to utilize the network line by 100 %. But if an effect occurs while the
test software occupies the network line, it will be detected by this method.
This makes the approach behind this method suitable especially for detecting
repetitive interferences.</p>
</sec>
</sec>
<sec id="Ch1.S5" sec-type="conclusions">
  <title>Conclusions</title>
      <p>In this paper the challenges, when assessing the disturbance in a real world
Ethernet set-ups, have been discussed. It has to be distinguished between the
hardware effects and software-related effects to get comparable results. To
overcome this issue, a new test method was developed and implemented as a
simple user application using the stateless user datagram protocol. In
contrast to observing normal data transfers from e.g. FTP servers/clients,
the effects on application layer perceived with this new method are directly
linked to the disturbances on the physical layer. The results of the method
are presented as time-domain data within a resolution in the range of
approximately a few hundred microseconds. This data can be used for further
investigations using known techniques of signal analysis to detect
intentional interferences.</p>
      <p>The implementation of the test-software is a proof of concept and still under
development status. The source code can be requested from the corresponding
author.<?xmltex \hack{\newline}?><?xmltex \hack{\newline}?><?xmltex \hack{\noindent}?><?xmltex \bgroup\small?>Edited by: F. Gronwald<?xmltex \hack{\newline}?> Reviewed by: S. Dickmann and one anonymous referee<?xmltex \egroup?></p>
</sec>

      
      </body>
    <back><ref-list>
    <title>References</title>

      <ref id="bib1.bibx1"><label>Adami et al.(2012)</label><mixed-citation>
Adami, C., Braun, C., Clemens, P., Jöster, M., Suhrke, M., and Taenzer, H.-J.:
High Power Microwave Tests of Media Converters, International
Symposium on Electromagnetic Compatibility 2012 (EMC Europe), Rome,
Italy, 17–21 September, 2012.</mixed-citation></ref>
      <ref id="bib1.bibx2"><label>Adami et al.(2014)</label><mixed-citation>
Adami, C., Braun, C., Clemens, P., Jöster, M., Suhrke, M., Schmidt, H.-U.,
and Tänzer, H.-J.: HPM-Detektionssystem mit Frequenzbestimmung, EMV Konferenz
2014, Düsseldorf, Germany, 11–13 March, 2014.</mixed-citation></ref>
      <ref id="bib1.bibx3"><label>Brauer(2010)</label><mixed-citation>
Brauer, F., ter Haseborg, J. L., Potthast, S.: Protection Circuits for IT
Equipment under HPEM Conditions, AMEREM 2010, Ottawa, Canada, 2010.</mixed-citation></ref>
      <ref id="bib1.bibx4"><label>IEEE Standard Association(2012)</label><mixed-citation>
IEEE Standard Association: IEEE 802.3-2012 – IEEE Standard for Ethernet,
Section 3, 2012.</mixed-citation></ref>
      <ref id="bib1.bibx5"><label>ITU(1994)</label><mixed-citation>
International Telecommunication Union (ITU): Telecommunication
Standardization Section Sector of ITU (ITU-T), Information technology –
Open Systems Interconnection – Basic Reference Model: The basic model,
Recommendation X.200, 1994.</mixed-citation></ref>
      <ref id="bib1.bibx6"><label>Jeffrey et al.(2004)</label><mixed-citation>Jeffrey, I., Gilmore, C., Siemens, G., and LoVetri, J.: Hardware invariant
protocol disruptive interference for 100BaseTX Ethernet communications, IEEE
Transactions on Electromagnetic Compatibility, 46, 412–422, 2004.
 </mixed-citation></ref><?xmltex \hack{\newpage}?>
      <ref id="bib1.bibx7"><label>Kreitlow et al.(2014)</label><mixed-citation>
Kreitlow, M., Garbe, H., and Sabath, F.: Influence of Software Effects on the
Susceptibility of Ethernet Connections, IEEE International Symposium on
Electromagnetic Compatibility EMC, Raleigh, NC, USA, 3–8 August, 2014.</mixed-citation></ref>
      <ref id="bib1.bibx8"><label>Mojert et al.(2001)</label><mixed-citation>
Mojert, C., Nitsch, D., Friedhoff, H., Maack, J., Sabath, F., Camp, M.,
and Garbe, H.: UWB and EMP Susceptibility of Microprocessors and Networks, 14th
International Zürich Symposium &amp; Technical Exhibition on Electromagnetic
Compatibility, Zurich, Switzerland, 20–22 Februar, 2001.</mixed-citation></ref>
      <ref id="bib1.bibx9"><label>Parfenov et al.(2008)</label><mixed-citation>
Parfenov, Y. V., Kohlberg, I., Radasky, W. A., Titov, B. A., and Zdoukhov, L. N.:
The Probabilistic Analysis of Immunity of a Data Transmission Channel
to the Influence of Periodically Repeating Voltage Pulses, Asia-Pacific
Symposium on Electromagnetic Compatibility &amp; 19th International Zurich
Symposium on Electromagnetic Compatibility, Singapore, 283–286,
2008.</mixed-citation></ref>
      <ref id="bib1.bibx10"><label>Postel(1980)</label><mixed-citation>Postel, J.: User Datagram Protocol, RFC 768, USC/Information Sciences
Institute, available at: <uri>http://tools.ietf.org/rfc/rfc768.txt</uri>, 1980.</mixed-citation></ref>
      <ref id="bib1.bibx11"><label>Postel(1981a)</label><mixed-citation>Postel, J. (Ed.): Internet Protocol, DARPA Internet Program – Protocol
Specification, RFC: 791, Defense Advanced Research Projects Agency (DARPA), Arlington,
Virginia, USA, available at: <uri>http://tools.ietf.org/rfc/rfc791.txt</uri>,
1981a.</mixed-citation></ref>
      <ref id="bib1.bibx12"><label>Postel(1981b)</label><mixed-citation>Postel, J. (Ed.): Transmission Control Protocol, DARPA Internet Program – Protocol
Specification, RFC: 793, Defense Advanced Research Projects Agency (DARPA), Arlington,
Virginia, USA, available at: <uri>http://tools.ietf.org/rfc/rfc793.txt</uri>,
1981b.</mixed-citation></ref>
      <ref id="bib1.bibx13"><label>Sabath(2008)</label><mixed-citation>
Sabath, F.: Classification of electromagnetic effects at system level,
Proceedings of the 2008 International Symposium on Electromagnetic
Compatibility (EMC Europe), Wroclaw, Poland, 18–22 August 2008, 1–5, 2008.</mixed-citation></ref>
      <ref id="bib1.bibx14"><label>van Leersum(2013)</label><mixed-citation>
van Leersum, B. J. A. M., Buesink, F. J. K., Bergsma, J. G., and
Leferink, F. B. J.: Ethernet susceptibility to electric fast transients, Proceedings of
the 2013 International Symposium on Electromagnetic Compatibility (EMC
Europe), Brugge, Belgium, 2–6 September 2013, 29–33, 2013.</mixed-citation></ref>

  </ref-list><app-group content-type="float"><app><title/>

    </app></app-group></back>
    </article>
