(Ebooks PDF) Download Recent Advances in Computational Optimization: Results of The Workshop On "Computational Optimization" and "Numerical Search and Optimization" 2018 Stefka Fidanova Full Chapters
(Ebooks PDF) Download Recent Advances in Computational Optimization: Results of The Workshop On "Computational Optimization" and "Numerical Search and Optimization" 2018 Stefka Fidanova Full Chapters
com
https://textbookfull.com/product/the-shorttube-80-telescope-a-user-s-
guide-neil-t-english/
textbookfull.com
https://textbookfull.com/product/essentials-of-hypertension-
the-120-80-paradigm-1st-edition-flavio-danni-fuchs-auth/
textbookfull.com
https://textbookfull.com/product/sew-your-own-wardrobe-more-
than-80-techniques-1st-edition-alison-smith/
textbookfull.com
https://textbookfull.com/product/public-debt-dynamics-of-europe-and-
the-us-1st-edition-dimitris-n-chorafas-auth/
textbookfull.com
https://textbookfull.com/product/the-hundred-year-walk-an-armenian-
odyssey-first-edition-mackeen/
textbookfull.com
https://textbookfull.com/product/effective-project-management-
traditional-agile-extreme-wysocki/
textbookfull.com
https://textbookfull.com/product/gardens-illustrated-pot-of-
style-40-beautiful-planting-ideas-for-containers-gardens-illustrated/
textbookfull.com
https://textbookfull.com/product/public-budgeting-reform-in-china-
theory-and-practice-1st-edition-xiaonan-liu-eds/
textbookfull.com
Empirical Research in Statistics Education 1st Edition
Andreas Eichler
https://textbookfull.com/product/empirical-research-in-statistics-
education-1st-edition-andreas-eichler/
textbookfull.com
Studies in Computational Intelligence 838
Recent Advances
in Computational
Optimization
Results of the Workshop on
“Computational Optimization” and
“Numerical Search and Optimization”
2018
Studies in Computational Intelligence
Volume 838
Series Editor
Janusz Kacprzyk, Polish Academy of Sciences, Warsaw, Poland
The series “Studies in Computational Intelligence” (SCI) publishes new develop-
ments and advances in the various areas of computational intelligence—quickly and
with a high quality. The intent is to cover the theory, applications, and design
methods of computational intelligence, as embedded in the fields of engineering,
computer science, physics and life sciences, as well as the methodologies behind
them. The series contains monographs, lecture notes and edited volumes in
computational intelligence spanning the areas of neural networks, connectionist
systems, genetic algorithms, evolutionary computation, artificial intelligence,
cellular automata, self-organizing systems, soft computing, fuzzy systems, and
hybrid intelligent systems. Of particular value to both the contributors and the
readership are the short publication timeframe and the world-wide distribution,
which enable both wide and rapid dissemination of research output.
The books of this series are submitted to indexing to Web of Science,
EI-Compendex, DBLP, SCOPUS, Google Scholar and Springerlink.
Recent Advances
in Computational
Optimization
Results of the Workshop on “Computational
Optimization” and “Numerical Search
and Optimization” 2018
123
Editor
Stefka Fidanova
Parallel Algorithms
Institute of Information and Communication
Technologies, Bulgarian Academy
of Sciences
Sofia, Bulgaria
This Springer imprint is published by the registered company Springer Nature Switzerland AG
The registered company address is: Gewerbestrasse 11, 6330 Cham, Switzerland
Organization
Conference Co-chairs
For WCO
Stefka Fidanova, IICT-BAS (Bulgaria)
Antonio Mucherino, IRISA (Rennes, France)
Daniela Zaharie, West University of Timisoara (Romania)
For NSO
Stefka Fidanova, IICT-BAS (Bulgaria)
Gabriel Luque, University of Malaga (Spain)
Kalin Penev, Southampton Solent University (UK)
Program Committee
v
vi Organization
vii
Contents
ix
x Contents
Abstract IP protocols have been used to distribute compressed media over private
and public networks for a number of years. Recently the broadcast sector has started
to adopt IP technologies to transport real time media within and between their facil-
ities during production. However, the high bitrate of uncompressed media and its
sensitivity to latency and timing variations requires careful design of the network in
order to maintain quality of service. Connectionless protocols are commonly used,
which means that packet loss is of particular concern and redundant paths must be
provisioned with mechanisms to switch between them. This project develops and
critically analyses a method for measuring the effectiveness of first hop redundancy
protocols for broadcast video production networks. The aim extends previous work
[1] to recommend particular configurations to optimise networks and to provide a
method that broadcast engineers can use to verify performance. Cisco’s HSRP is
recommended with static routes configured for redundant paths. It is recommended
that the network is tested using a synthetic RTP stream with a low complexity packet
sniffer and NICs with hardware timestamps. Further work is identified including
ways to improve the accuracy of the results and to consider the impact of more
complex networks.
1 Introduction
2 Background
IP networks are becoming increasing important throughout the broadcast video work-
flow from production through to distribution. Value can be added to the signal chain
via the flexibility of dynamically routed signals and format agnostic transport proto-
cols. There has been significant uptake of services distributed using IP technologies
such as Over the Top (OTT) and Internet Protocol Television (IPTV) [13, 14]. OTT
services such as Netflix and BBC iPlayer are delivered over the public Internet with-
out the need for proprietary devices whereas IPTV services such as Virgin Media
use managed networks. Due to the nature of the networks OTT is usually deliv-
ered using Hyper Text Transport Protocol (HTTP) using the connection-orientated
Transmission Control Protocol (TCP). With the use of a buffer, this provides bene-
fits such as retransmission but at the expense of latency. IPTV or real-time signals
within a production environment are more likely to use Realtime Transport Protocol
(RTP) over the connectionless User Datagram Protocol (UDP). RTP is used by many
media-centric protocols as a transport mechanism to provide sequence numbers and
timestamps with minimal overhead. The information provided within the headers
may be used by high level applications to improve QoS and further feedback is usu-
ally exchanged between participants using the RTP Control Protocol (RTCP) [15].
The small receive buffer and lack of a retransmission mechanism means that RTP
is vulnerable to packet-loss and necessitates a rapid failover mechanism to maintain
resilience using a secondary path.
First Hop Redundancy Protocols (FHRP) provide an essential tool for increas-
ing availability in critical switched IP networks. They provide a mechanism for fast
failover to the next hop from a primary path to a secondary path within a group of
backup routers. The process is faster than waiting for spanning tree or dynamic rout-
ing protocols to converge on a new path due to the limited scope and pre-configuration
of the FHRP. Essentially two or more routers are able to share the default gateway
at OSI layer 3, which provides an alternative route or may even be used for rudi-
mentary load balancing. This does necessitate the use of multilayer switches but can
be implemented at the Access Layer or Distribution Layer [16, 17]. YanHua and
WeiZhe [18] have shown that such protocols are suitable for use within cable tele-
vision IP networks when combined with device redundancy, although they caution
against diminishing returns as the network complexity increases.
Cisco has developed two major proprietary protocols Hot Standby Routing Proto-
col (HSRP) and Gateway Load Balancing Protocol (GLBP). Another common proto-
col is the Virtual Router Redundancy Protocol (VRRP), which is available as an open
IEFT standard RFC5798. It is similar to HSRP in operation but not compatible [19,
20]. Other equipment vendors also have proprietary protocols; Juniper Networks
has NetScreen Redundancy Protocol (NSRP), Avaya has Routed Split Multi-link
Trunking (R-SMLT) and Extreme Networks has Extreme Standby Routing Protocol
(ESRP) [21–24]. Broadcast installations usually combine best-of-breed equipment
and are generally multivendor environments built on open standards. However Cisco
have a dominant position in the switching and routing market with over 50% of the
4 P. Bourne et al.
worldwide market share in 2016 [25]. As such this investigation will focus on HSRP,
GLBP and VRRP. Common Address Redundancy Protocol (CARP) was considered
but relies on the Berkeley Software Distribution so is not practical on many platforms
[26].
HSRP is configured for an interface using the standby command and allows the
user to configure a virtual gateway for the connected hosts to use. Priorities are
specified such that an active router is allocated with one or more standby routers
sharing the virtual address with the active router as shown by Fig. 1. Packets are
forwarded based on an IP/MAC address pair and standby routers monitor the status
of the active router to promote a backup router in the case of a link failure on the active
path. Tracking objects can be used to monitor interfaces or Service Level Agreement
(SLA) tracking can monitor connectivity beyond the first hop. Either method can
update the router priorities to determine the active path. Different priorities can also
be assigned to different Virtual Local Area Networks (VLAN) to implement basic
load balancing, although this may become unwieldy on large networks [17, 27].
GLBP uses multiple gateways simultaneously, which enables more effective load
balancing and therefore uses all the bandwidth within the topology. Routers within a
GLBP group may be the Active Virtual Gateway (AVG), an Active Virtual Forwarder
(AVF) or the Standby Virtual Gateway (SVG). The AVG assigns virtual MAC address
to the other group members. Up to four AVFs, including the AVG, are able to forward
packets and the SVG is ready to take over from the AVG based on a similar priority
system to HSRP with decrements based on tracking objects. GLBP is implemented
on an interface using the glbp command and load balancing can be achieved within
the group by assigning packets to the MAC addresses of the AVFs via an equal
round-robin, by weighting certain paths or based on the host [17, 28].
Fig. 1 A typical HSRP configuration with the host using a common virtual gateway IP address
Developing a Method for Measuring the Failover Times … 5
VRRP is very similar to HSRP in that is uses a single virtual gateway that is shared
between a master and one or more backup router. It is implemented on the interface
using the vrrp command and supports object tracking to determine failures. Fewer
IP addresses may be used by VRRP than HSRP as the physical IP address for the
master router may also be used as the virtual IP address [29].
Several articles have been published that outline the configuration options for
HSRP, GLBP and VRRP [20, 30–32]. These discuss how the options affect the
underlying algorithm but there appears to be little guidance on how to optimise the
parameters or how the common protocols compare under similar conditions. Ibrahimi
et al. [32] and Rahman et al. [33] demonstrate a basic method, using continuous
Internet Control Message Protocol (ICMP) echo requests to show the duration of a
link failure. Pavlik et al. [17] show a more accurate method to determine the interval
between missing and restored replies using timestamps from a packet sniffer. None of
the studies investigate the time taken to restore a link after the primary link recovers.
QoS describes the technical performance of a network, which can usually be
objectively quantified and measured at specific points within the network topology.
Common parameters include latency, jitter and packet loss but bandwidth and packet
reordering are also important within video networks due to the temporal sensitivity
and inter-packet dependencies of media flows [34, 35]. Latency is the time it takes
for packets to reach their destination whereas jitter is the variance in the inter-packet
latency. Latency is often acceptable when there is minimal jitter or packet loss,
although it can be a problematic in live broadcasting when disparate sources are
combined such as when conducting interviews. Packet loss tends to be caused by
excessive latency or jitter that causes buffers to underflow and tends to result in
audio or video frames freezing or degrading. Receive buffers can reduce jitter and
therefore packet loss but at the expense of latency [36]. Bandwidth is of concern
within production facilities due to the high data rates of video at 2.97 Gbps for a
single uncompressed High Definition (HD) stream. Gharai, Perkins and Lehman [37]
have noted that in video networks, packet reordering should be treated on an equal
footing with packet loss and the European Broadcast Union (EBU) recommends that a
receiver should not have to accommodate packets out of order by more than 10 places.
Packet reordering is often caused during redundancy switches. Cisco recommends
that for video networks latency should be less than 300 ms, jitter less than 50 ms and
packet loss of less than 0.5% [38] although production environments may have to
work to stricter limits for control and monitoring with latency as low as 10 ms and
virtually no packet loss [39, 40].
3 Test Method
How to measure the effectiveness of FHRPs is one of the major objectives of the
research and a clear and accessible method should be one of the outputs. Previous
studies of the quality of video over IP have made a distinction between the QoS
provision from the network and the QoS provision from the media application [36,
6 P. Bourne et al.
41]. Studies at the application layer have tended to focus on comparing image qual-
ity by detecting artefacts such as blocking and blurring or calculating Peak Signal
to Noise Ratio (PSNR) using bespoke measurement applications. These are very
dependent on the configuration of the codec and often require reliable side-channels
to make mathematical comparisons with a reference stream. This study will instead
focus on the QoS of the network, which Tao, Apostolopoulos and Guerin [41] state
is largely driven by packet loss, delay and jitter. This may be achieved by generating
and injecting a stream of timestamped packets into a test network to be captured and
analysed at a receiver. Previous studies into FHRPs demonstrate a method to test
availability using a continuous stream of Internet Control Message Protocol (ICMP)
echo requests to determine the duration of a link failure [32, 33]. Alternatively a
packet sniffer can be used to observe the interval between missing echo relies as
demonstrated by Pavlik et al. [17]. Essentially packet drop and the unavailability
interval provide the same information as the packet drop is a function of the interval
and bitrate.
There are several network simulation packages that may be used to rapidly anal-
yse the behaviour of different configurations. Common simulators include Cisco’s
Packet Tracer, open source application GNS3 and Riverbed Modeler. For these to
produce accurate results, they require detailed implementations of the software and
protocols running on the network devices as well as accurate models of the hardware
performance. The level of difficulty required to accurately reproduce the test envi-
ronment is not necessary where real equipment is available to provide accurate real
time results.
A testbed was created to emulate a typical spine-and-leaf network architecture as
recommended for high available networks. The topology is shown by Fig. 2.
The source had an edge ‘customer’ router, which connected to their Local Area
Net-work (LAN). This had redundant links to an external network via primary and
secondary routers, which were connected to the ‘main’ router at the destination on a
WAN. The switch simplified the configuration of the customer router by removing
the need for two interfaces on the same subnet. The primary link utilised a Gigabit
Ethernet connection whereas the secondary was only Fast Ethernet. Secondary links
are often metered in practice so load balancing was not implemented. To simulate a
link failure, the interface G0/0 was shut down on the primary router with a tracking
object to promote the secondary link based on the line-protocol state. The FHRPs
were configured to decrement the priority of the primary router below that of the
secondary router if the line protocol went down; this causes the secondary router to
pre-empt the primary router and traffic would be rerouted. An alternative method
would be to check the reachability of the loopback interface on the destination net-
work using ICMP requests to decrement the priority upon failure. This would be a
more meaningful detection method within a real network but the non-deterministic
nature of packet generation and propagation may distort the results, which should be
focused on the responsiveness of the redundancy protocol itself.
All routes were statically defined within the routers to prevent the dynamic rout-
ing protocols from interfering with the results. The FHRPs were configured on the
primary and secondary routers with a default static route on the customer router
Developing a Method for Measuring the Failover Times … 7
pointing to the virtual IP address. A default and more rapid configuration was tested
for each FHRP using the parameters shown by Table 1. By default HSRP sets the
time between hello messages to 3 s and the hold time to be 10 s. The hold time is the
interval after which the active router is declared to be down once hello messages are
not acknowledged. The hold timer must be greater than the hello timer—usually at
least three—to avoid the active router being declared down between hello messages
[42, 43]. GLBP uses the same system of hello and hold timers with identical default
and minimum values [44]. HSRP and GLBP timers can be set with millisecond gran-
ularity but a shorter timer increases the amount of overhead traffic and can cause the
system to behave erratically as it becomes too sensitive [34]. For the rapid test the
hello timer will be set to 1 s and the hold timer to 3 s; this will allow the effect
of smaller timers to be observed without creating instability. VRRP advertisements
are sent every second by default with a failover delay calculated by three times the
advertisement interval plus the router’s skew time. The skew time is based on the
8 P. Bourne et al.
inverse of the priority. The standard doesn’t include shorter advertisement intervals
but Cisco has implemented this in their IOS down to 20 ms [30, 45]. The priorities
were configured as high as possible for the rapid test to reduce the skew time. It
should be noted that pre-emption delay should normally be configured to allow for
the boot time of the equipment [34]. Each configuration was tested ten times.
Two methods were employed for measuring the interval between the interface
changing state and the FHRP responding. A third method that would track missing
ICMP echo replies was considered and trialed during earlier studies [1]; the results
from this would be more comparable to existing studies but the flow was found to
be too simplistic and imprecise to represent media streams.
Method 1: The packet loss was measured using a test stream and packet sniffer.
This relies on the accuracy of the packet generator as well as the timestamps within
the captured stream. VLC Media Player was used to generate a stream of colour bars
and tone from an MP4 file. netsniff-ng was used to capture traffic for analysis using
Wireshark’s RTP dissector. The interval between missing sequence numbers could
be used to determine the packet loss during failover or restoration. The jitter on the
captured packets was also measured to determine the inter-packet arrival variance
and therefore the precision to which the time interval could be reliably calculated.
Method 2: Timestamped debug messages on the routers were used to report the
interface failure and pre-emption of a new router. NTP was used to synchronise
the internal clocks so that the timestamps from different devices could be compared.
The accuracy of the log timestamps was investigated by sending 1000 PING requests
from the source PC to the primary router with 100 ms interval. The SPAN feature on
the primary router was used to copy packets from the G0/1 interface to a netsniff-ng
packet capture on the SPAN PC. Logging was configured on the primary router to
millisecond accuracy using an Access Control List (ACL) to also log the arrival of
the ICMP echo requests. The timestamps on the packet capture were compared to
the logging timestamps to indicate any discrepancy with the logging process. The
jitter inherent on the network was also measured using the Iperf utility.
Developing a Method for Measuring the Failover Times … 9
4 Results
Of the 1000 PING requests sent, the maximum deviation from the intended 100 ms
interval was ± 4 ms within the raw Cisco timestamps. The PING utility and source
interface will introduce jitter so the figures were adjusted based on the inter-packet
arrival intervals from the SPAN capture. This reduced the error slightly to +4 ms
and −3 ms. In total 31 packets were logged as having a different arrival time to the
SPAN data with an average absolute deviation of 2 ms. The round trip time reported
by the PING utility ranged from 1 to 2 ms with an average of 1.88 ms.
After running 10 cycles of the jitter measurements, the maximum jitter reported
was 570 µs, the minimum 26 µs and the mean average result was 82 µs with a
standard deviation of just 0.1.
The results from the experiment suggest that Cisco’s logging timestamps have
the potential to be accurate to within +4/−3 ms. The jitter added from the test
equipment was much lower than this, which suggests that the figures are reliable. This
is enough precision to compare FHRP but Accedian [46] suggest that inaccuracies in
timestamps approaching even a tenth of a millisecond are unsuitable for measuring
high performance SLA metrics. One concern is that the load on the router was
extremely low during this experiment as there was no significant traffic being routed
or other events for the router to log. As such this indicates the best accuracy of the
logging timestamp.
The minimum, maximum and mean average time have been presented for the
default and rapid configurations of each redundancy protocol. The failover times
are summarised in Table 2 and the restoration times in Table 3. The average jitter
calculated from the stream captures is included to provide an indication of the system
stability—jitter data has not been presented for the rapid configuration of VRRP as
it was consistently reported to be zero. The mean absolute differences between the
results from the two methods are shown as absolute value and percentages.
The mean failover and restoration delays as well as the mean number of packets
dropped are shown as radar plots for the default and rapid configuration in Fig. 3 and
Fig. 4 respectively. The metrics have been scaled to produce a plot whereby the outer
edge indicates the worst performance and the center indicates ideal performance.
It can be seen from Tables 2 and 3 that the two test methods produce similar results
for VRRP and GLBP but there is significant disparity for HSRP—the captures suggest
that the protocol is 83–88% faster than the logs report. Inspection of the packet
captures verifies that this figure is correct and suggests that the logging process
introduces a delay with this protocol. The results correlate well with the studies
completed by Pavlik et al. [17] although it is interesting to note that all of the protocols
were faster than in their study. This is likely to be due to the different topologies used
and will be particularly affected by the use of static routes in this study. Previous
studies have not analysed the restoration delays, which were also found to be fastest
with HSRP closely followed by VRRP.
The packet loss showed some particularly interesting results. The rapid failover
of HSRP led to the fewest losses whilst GLBP resulted in the most. Surprisingly
10 P. Bourne et al.
GLBP resulted in slightly more loss with its rapid configuration even though the link
initially came back up more quickly. VRRP consistently dropped a significant number
of packets during restoration when configured with the default parameters—no other
configuration exhibited this behaviour including the rapid configuration of VRRP.
This is highly undesirable as it will result in an additional video glitch in the event
of a failover.
5 Conclusions
The initial tests logging ICMP echo requests suggested that timestamps could be
accurate to within ± 4 ms and that the jitter from low-level packet generation tools
would have minimal influence on the results. However, the disparity between the logs
and packet captures show that the timestamps from logs cannot be relied upon for
more complex protocols—this could be due to the interface between the protocol and
the logging procedure or due to the priority that is assigned to logging the protocol. It
is recommended that it is more accurate to capture an RTP stream to test the failover
delay.
Originally packEth was going to be used to generate an RTP stream. The thread-
ing used to generate the traffic is reported to be stable to microsecond resolution
[47] and Srivastava et al. [48, 49] found the tool to be more suitable than alter-
natives for testing high capacity links. However this tool doesn’t produce RTCP
messages, which caused the routers to drop the RTP stream. Instead VLC Media
Player was used, which had to encode real video frames rather than generating a
synthetic stream. The captures showed a throughput of approximately 20–30 pack-
ets per second, which didn’t give much resolution and the delta between consecutive
packets varied from approximately 0.04 to 250 ms, which is quite bursty. The resolu-
tion could be improved by increasing the data-rate at the source but the burstiness is
likely to be harder to solve. The jitter in the network was fairly consistent throughout
the experiment at around 70 ms. A video network would be expected to have jitter
below 30 ms to maintain QoS [50]. The high figure is likely to be due to using a
software application to generate the RTP stream. The worst case jitter originating
from the source and capture NICs themselves was measured to be just 0.57 ms. A
tool is needed to synthetically generate RTP streams with RTCP messaging so that
a high throughput can be generated with low jitter. This could be an extension to
packEth or a separate utility.
The results themselves suggest that HSRP is the most effective protocol and that
the rapid configuration improves its performance. This protocol is Cisco proprietary
so VRRP would have to be used within a multivendor environment with the config-
uration customised to avoid the packet loss observed using the default parameters.
This work could be extended by reducing the configured timers further to find the
limits of the protocol. As broadcasters are likely to use larger systems with best of
breed equipment, the effects of multiple standby devices and mixed-vendor equip-
ment should also be investigated.
Developing a Method for Measuring the Failover Times … 13
References
1. Bourne, P., et al.: Quantifying the effectiveness of first-hop redundancy protocols in IP networks.
In: Numerical Methods and Applications, NMA 2018. Lecture Notes in Computer Science,
vol 11189. Springer, Cham (2019)
2. Ramsey, C.: 2018 Mediatech Outlook. Newbay, s.l. (2018)
3. IP in 2018—A Growth in Market Confidence. https://www.tvtechnology.com/news/ip-in-2018-
a-growth-in-market-confidence. Accessed 27 Jan 2019
4. Timeline Television to Showcase 4 K-HDR IP OB Truck on SAM’s IBC 2017 Booth. https://
www.thebroadcastbridge.com/content/entry/9387/timeline-television-to-showcase-its-ip-4k-
hdr-ob-truck-on-sams-ibc-2017-boo. Accessed 21 Jan 2019
5. About—The Broadcast Bridge. https://www.thebroadcastbridge.com/about. Accessed 21 Jan
2019
6. Overview—AIMS Alliance. https://www.aimsalliance.org/overview/. Accessed 21 Jan 2019
7. Man, H., Li, Y.: Multi-stream video transport over MPLS networks. In: IEEE Workshop on
Multimedia Signal Processing, pp. 384–387 (2002)
8. Aria Networks Shows Off Self-Healing Video Distribution Using SDN + AI Combo.
http://www.aria-networks.com/news/aria-networks-self-healing-video-distribution-sdn-ai/.
Accessed 21 Jan 2019
9. Demystifying SDN: It’s an integral part of next-gen IP video transport. https://www.
tvtechnology.com/expertise/demystifying-sdn. Accessed 21 Jan 2019
10. TV, Vendors Struggle To Keep Up With Tech. https://tvnewscheck.com/article/114036/tv-
vendors-struggle-to-keep-up-with-tech/. Accessed 21 Jan 2019
11. What Broadcasters Can Learn From Telcos About IP. https://www.tvtechnology.com/
broadcast-engineering/what-broadcasters-can-learn-from-telcos-about-ip. Accessed 21 Jan
2019
12. Whether It’s Called IP or IT, Media Networks Are Different. https://www.thebroadcastbridge.
com/content/entry/7062/whether-its-called-ip-or-it-media-networks-are-different. Accessed
21 Jan 2019
13. Quarter of European OTT platforms target cross-border audiences. https://www.
broadbandtvnews.com/2017/11/15/quarter-of-european-ott-platforms-target-cross-border-
audiences/. Accessed 21 Jan 2019
14. The revolutionary transition to an all-IP video production workflow. https://www.ibc.
org/production/revolutionary-transition-to-all-ip-video-production-workflow/925.article.
Accessed 21 Jan 2019
15. Cheng, Y., et al.: From QoS to QoE: a tutorial on video quality assessment. IEEE Commun.
Surv. Tutor 17(20), 1126–1165 (2015)
16. CCNA Routing and Switching Practice and Study Guide: LAN Redundancy. http://www.
ciscopress.com/articles/article.asp?p=2204384&seqNum=4. Accessed 21 Jan 2019
17. Pavlik, J., et al.: Gateway redundancy protocols. In: 15th IEEE International Symposium on
Computational Intelligence and Informatics, pp. 459–464. IEEE, Budapest (2014)
18. YanHua, Z., WeiZhe, M.: The design of cable television IP access network based on hot standby
router protocol. In: International Conference on Image Analysis and Signal Processing, pp. 1–4.
IASP, Hangzhou (2012)
19. Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6. https://tools.ietf.
org/html/rfc5798. Accessed 21 Jan 2019
20. Oppenheimer, P.: Top-Down Network Design, 3rd edn. Cisco Press, Indianapolis (2011)
21. OpenBSD PF—Firewall Redundancy (CARP and pfsync). https://www.openbsd.org/faq/pf/
carp.html. Accessed 21 Jan 2019
22. NSRP overview. https://kb.juniper.net/InfoCenter/index?page=content&id=KB4263&cat=
HA_REDUNDANCY&actp=LIST. Accessed 21 Jan 2019
23. Routed split multilink trunking. https://worldwide.espacenet.com/publicationDetails/biblio?
FT=D&date=20050113&DB=&locale=en_EP&CC=US&NR=2005007951A1&KC=A1&
ND=1. Accessed 21 Jan 2019
14 P. Bourne et al.
24. ExtremeWare XOS Concepts Guide Software Version 11.3, p. 445. https://www.manualslib.
com/manual/511330/Extreme-Networks-Extremeware-Xos-Guide.html?page=1#manual.
Accessed 4 July 2018
25. Switching market stays steady as Cisco’s domination continues. https://www.cbronline.
com/data-centre/switching-market-stays-steady-as-ciscos-domination-continues-4993282/.
Accessed 21 Jan 2019
26. Chapter 28. Introduction to the Common Address Redundancy Protocol (CARP). https://www.
netbsd.org/docs/guide/en/chap-carp.html. Accessed 21 Jan 2019
27. Hot Standby Router Protocol Features and Functionality. https://www.cisco.com/c/en/us/
support/docs/ip/hot-standby-router-protocol-hsrp/9281-3.html. Accessed 21 Jan 2019
28. Cisco: First Hop Redundancy Protocols Configuration Guide. Cisco IOS Release 12.2SX.
Cisco, San Jose (2011)
29. VRRP Overview. https://www.juniper.net/documentation/en_US/junose15.1/topics/concept/
vrrp-overview.html. Accessed 21 Jan 2019
30. First Hop Redundancy Protocols Configuration Guide, Cisco IOS Release 15SY. https://www.
cisco.com/c/en/us/td/docs/ios-xml/ios/ipapp_fhrp/configuration/15-sy/fhp-15-sy-book/fhp-
vrrp.html. Accessed 21 Jan 2019
31. Configuring VRRP. https://www.juniper.net/documentation/en_US/junos/topics/example/
vrrp-configuring-example.html. Accessed 21 Jan 2019
32. Ibrahimi, M., et al.: Deploy redundancy of Internet using first Hop redundancy protocol and
monitoring it using IP service level agreements. Int. J. Eng. Sci. Comput. 7(10), 15320–15322.
Pearl Media Publications, Bangalore (2017)
33. Rahman, Z., et al.: Performance evaluation of first HOP redundancy protocols (HSRP, VRRP
& GLBP). J. Appl. Environ. Biol. Sci. 7(3), 268–278. Textroad, Egypt (2017)
34. Froom, R., Sivasubramanian, B., Frahim, E.: Implementing Cisco Switched Networks. Cisco,
Indianapolis (2010)
35. Arthur, C., et al.: The effects of packet reordering in a wireless multimedia environment. In:
1st International Symposium on Wireless Communication Systems, pp. 453–457 (2004)
36. Cheng, Y., Wu, K., Zhang, Q.: From QoS to QoE: a tutorial on video quality assessment. IEEE
Commun. Surv. Tutor. 17(20), 1126–1165 (2015)
37. Gharai, L., Perkins, C., Lehman, T.: Packet reordering, high speed networks and transport
protocol performance. In: 13th International Conference on Computer Communications and
Networks, 1401591, pp. 73–78 (2004)
38. Video Quality of Service (QOS) Tutorial. https://www.cisco.com/c/en/us/support/docs/quality-
of-service-qos/qos-video/212134-Video-Quality-of-Service-QOS-Tutorial.html. Accessed 21
Jan 2019
39. Understanding—and Reducing—Latency in Video Compression Systems. http://www.
cast-inc.com/blog/white-paper-understanding-and-reducing-latency-in-video-compression-
systems. Accessed 21 Jan 2019
40. IP Networks for Broadcaster Applications. https://www.researchgate.net/publication/
308764506_IP_Networks_for_Broadcaster_Applications. Accessed 21 Jan 2019
41. Tao, S., Apostolopoulos, J., Guerin, R.: Real-time monitoring of video quality in IP networks.
IEEE/ACM Trans. Netw. 16(5), 1052–1065 (2008)
42. Hot Standby Router Protocol (HSRP): Frequently Asked Questions. https://www.cisco.com/c/
en/us/support/docs/ip/hot-standby-router-protocol-hsrp/9281-3.html. Accessed 21 Jan 2019
43. Standby-hold-timer. https://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com.
ibm.dp.doc/standby-hold-timer_interface.html. Accessed 21 Jan 2019
44. Timers (GLBP). https://www.cisco.com/c/m/en_us/techdoc/dc/reference/cli/n5k/commands/
timers-glbp.html. Accessed 21 Jan 2019
45. VRRP failover-delay Overview. https://www.juniper.net/documentation/en_US/junos/topics/
concept/vrrp-failover-delay-overview.html. Accessed 21 Jan 2019
46. White Paper—One-Way Delay Measurement Techniques. https://www.accedian.com/wp-
content/uploads/2015/05/One-WayDelayMeasurementTechniques-AccedianWhitePaper.pdf.
Accessed 21 Jan 2019
Developing a Method for Measuring the Failover Times … 15
‘Suspirat ab imis
Pectoribus, lacrimaeque genis labuntur obortae.’
1467 f. Pont. i. 2. 29 f.
1469. Cp. Metam. xiii. 539.
1473. Ovid, Metam. viii. 469.
1475. Metam. iv. 135, borrowed without much regard to the
context.
1485. From Ovid, Her. xiv. 37, where however we have ‘calor,’
not ‘color,’ a material difference.
1496. Her. v. 46.
1497. The expression ‘verbis solabar amicis’ is from Ovid (Fasti,
v. 237), but here ‘solabar’ seems to be made passive in sense.
1501 f. i.e. ‘cessat amor eius qui prius,’ &c., with a rather harsh
ellipse of the antecedent. The couplet is a parody of Ovid, Pont. iv. 6.
23 f.,
LIB. II.
With the general drift of what follows cp. Conf. Amantis, Prol. 529
ff.
1. Incausti specie, cp. Conf. Amantis, viii. 2212.
18. nos: meaning the people of England, as compared with those
of other countries.
31 f. Cp. Ovid, Tristia, v. 8. 19 f.
33. Tristia, v. 5. 47.
41. Job v. 6, ‘Nihil in terra sine causa fit’: cp. Mirour de l’Omme,
26857.
59. This is the usual opposition of rose and nettle, based perhaps
originally on Ovid, Rem. Amoris, 46: cp. Conf. Amantis, ii. 401 ff.
67 f. Cp. Boethius, Consol. Phil. 2 Pr. 4, ‘in omni adversitate
fortunae infelicissimum genus est infortunii fuisse felicem.’ So Dante,
Inf. v. 121 ff.,
117 ff. Cp. Ovid, Her. v. 109 ff. In l. 117 ‘siccis’ is substituted, not
very happily, for ‘suci.’
138. Cp. Conf. Amantis, Latin Verses after ii. 1878,
LIB. III.
1-28. The form of these lines which stood originally in S is given
by the Trinity College, Dublin, and the Hatfield MSS. The passage
has been rewritten over erasure in CHG, and it must be left doubtful
what text they had originally. From the fact that the erasure in G
begins with the second line, it may seem more probable that the
original text of this manuscript agreed with that which we have now
in S, rather than with TH₂: for in the latter case there would have
been no need to begin the erasure before l. 4. In CH the whole
passage has been recopied (the same hand appearing here in the
two MSS.) so that we can draw no conclusion about the point where
divergence actually began. EDL have the same text by first hand. It
will be noted that the lines as given by TH₂ make no mention of the
schism of the Papacy.
11 ff. With this we may compare Mirour de l’Omme, 18769 ff.
22. nisi, for ‘nil nisi’: cp. l. 32.
41. Cp. Ovid, Amores, iii. 8. 55.
63. Fasti, i. 225.
65 f. Cp. Fasti, i. 249 f.
85-90. Chiefly from the Aurora of Petrus (de) Riga, (MS. Bodley
822) f. 71,
Gower is right in reading ‘serit,’ which is given in MS. Univ. Coll. 143,
f. 13.
1206. Cp. l. 1376.
1213. Cp. Ovid, Ars Amat. iii. 655.
1215 f. Cp. Ars Amat. iii. 653 f.
1233. Cp. Ars Amat. ii. 279.
1247 ff. Cp. Mirour, 18793 ff.
1267. Vox populi, &c.: cp. Speculum Stultorum, p. 100, l. 4, and
see also the note on iii. Prol. 11.
1271. Cp. Conf. Amantis, Prol. 304 ff. and Mirour, 18805.
1313. With the remainder of this Book, treating of the secular
clergy, we may compare Mirour de l’Omme, 20209-20832.
1341. Cp. Mirour, 18889 ff.
1342. participaret, ‘he ought to share’: see note on l. 676.
1359 f. Cp. Conf. Amantis, i. 1258 ff.
1375 ff. Cp. Mirour, 20287 ff.
1376. The reading ‘vngat vt’ is given by the Digby MS. and
seems almost necessary: cp. l. 1206.
1405. prece ruffi ... et albi, ‘by reason of the petition of the red
and the white,’ that is, presumably, by the influence of gold and
silver, ‘dominis’ in the next line being in a loose kind of apposition to
a dative case suggested by ‘Annuit.’
1407. S has here in the margin, in a rather later hand, ‘contra
rectores Oxon.’
1417. Eccles. iv. 10, ‘Vae soli, quia cum ceciderit, non habet
sublevantem se.’
1432. The margin of S has here, in the same hand as at 1407,
‘Nota rectores et studentes Oxon.’
1443. formalis, that is, ‘eminent,’ from ‘forma’ meaning ‘rank’ or
‘dignity,’ but here also opposed to ‘materialis.’
1454. Originally the line was ‘Dum legit, inde magis fit sibi sensus
hebes,’ but this was altered to ‘plus sibi sensus hebes est,’ with the
idea apparently of taking ‘magis’ with ‘legit.’ This involves an
awkward metrical licence, ‘hebes est’ equivalent to ‘hebest,’ and the
original text stands in CEH as well as in TH₂. The expedient of the
Roxburghe editor is quite inexcusable.
1493 ff. Cp. Mirour, 20314. The sporting parson was quite a
recognized figure in the fourteenth century. Readers of Froissart will
remember how when the capture of Terry in Albigeois was effected
by stratagem, the blowing of the horn to summon the company in
ambush was attributed by those at the gate to a priest going out into
the fields, ‘Ah that is true, it was sir Francis our priest; gladly he
goeth a mornings to seek for an hare.’
1498. fugat: used apparently as subjunctive also in l. 2078, but it
is possible that ‘Nec fugat’ may be the true reading here.
1509 ff. Cp. Mirour de l’Omme, 20313 ff.
1527. Est sibi missa, ‘his mass is over.’
1546. Apparently a proverbial expression used of wasting
valuable things.
1549. If benefices went from father to son, little or nothing would
be gained by those who go to Rome to seek preferment, for an heir
would seldom fail.
1555 ff. Cp. Mirour de l’Omme, 20497 ff. The priests here spoken
of are the ‘annuelers,’ who get their living by singing masses for the
dead, the ‘Annua seruicia’ spoken of below:
1807 f.
‘Aurum ueste gerit presul, cum splendet in illo
Pre cunctis rutilans clara sophia patris.’
Aurora, f. 45.
1809 ff.
1885 ff. Our author still borrows from the same source, though
from a different part of it. We find these lines nearly in the same form
in the Aurora, f. 103,
1891 f.
The meaning is that the bad priests cry ‘Cras,’ like crows, and
encourage men to put off repentance, while the others sing ‘Hodie,’
like doves, the words ‘cras’ and ‘hodie’ being imitations of the notes
of the two birds. The expression ‘Cras primam cantant,’ in l. 2039, is
not intelligible, and probably Gower missed the full sense of the
passage.
2045. ‘sit’ has been altered in S from ‘fit.’
2049 ff. Cp. Mirour de l’Omme, 20785 ff.
2071. Cp. Mirour, 20798.
2078. fugat: cp. l. 1498.
2097 f. Cp. iv. 959 and note.
LIB. IV.
The matter of this book corresponds to that of the Mirour de
l’Omme, ll. 20833-21780.
19 f. Cp. Lib. iii. Prol. 11.
34. ‘dompnus’ or ‘domnus’ was the form of ‘dominus’ which was
properly applied as a title to ecclesiastical dignitaries, and it seems
to have been especially used in monasteries. Ducange quotes John
of Genoa as follows: ‘Domnus et Domna per syncopen proprie
convenit claustralibus; sed Dominus, Domina mundanis.’ Cp. l. 323
of this book and also 327 ff.
57. humeris qui ferre solebat, ‘who used to bear burdens,’ as a
labourer.
87. Cp. Godfrey of Viterbo, Pantheon, p. 74 (ed. 1584).
91. Pantheon, p. 74.
109 f. Cp. Ovid, Fasti, i. 205 f.
111. Ars Amat. ii. 475, but Ovid has ‘cubilia.’
112. Cp. Fasti, iv. 396, ‘Quas tellus nullo sollicitante dabat.’
Gower has not improved the line by his changes.
114. Fasti, iv. 400.
115. Metam. i. 104, but Ovid has of course ‘fraga.’