Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Frame Relay
open-in-new
<h2 id="technical-description">Technical description</h2> <p>The designers of Frame Relay aimed to provide a telecommunication service for cost-efficient data transmission for intermittent traffic between <a href="/facts/Local_area_network/edUDxJ6J">local area networks</a> (LANs) and between end-points in a wide area network (WAN). Frame Relay puts data in variable-size units called "frames" and leaves any necessary <a href="/facts/Error_correction/o2rH8e3n">error-correction</a> (such as retransmission of data) up to the end-points. This speeds up overall data transmission. For most services, the network provides a <a href="/facts/Permanent_virtual_circuit/8HqpnTxl">permanent virtual circuit</a> (PVC), which means that the customer sees a continuous, dedicated connection without having to pay for a full-time <a href="/facts/Leased_line/JzGppCIP">leased line</a>, while the <a href="/facts/Service_provider/m4lLh5u7">service-provider</a> figures out the route each frame travels to its destination and can charge based on usage. </p><p>An enterprise can select a <a href="/facts/Quality_of_service/joz9VkUm">level of service quality</a>, prioritizing some frames and making others less important. Frame Relay can run on fractional <a href="/facts/Digital_Signal_1/cghJPRpQ">T-1</a> or <a href="/facts/E-carrier/h0MXcgXN">E1</a>, or full <a href="/facts/T-carrier/tCsEdK72">T-carrier</a> or <a href="/facts/E-carrier/h0MXcgXN">E-carrier</a> system carriers. Frame Relay complements and provides a mid-range service between basic rate <a href="/facts/ISDN/zcV99rUb">ISDN</a>, which offers bandwidth at 128 kbit/s, and <a href="/facts/Asynchronous_Transfer_Mode/SzA8ewFL">Asynchronous Transfer Mode</a> (ATM), which operates in somewhat similar fashion to Frame Relay but at speeds from 155.520 Mbit/s to 622.080 Mbit/s.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> </p><p>Frame Relay has its technical base in the older <a href="/facts/X.25/yaGPqw2Y">X.25</a> <a href="/facts/Packet-switching/olDlDP1R">packet-switching</a> technology, designed for transmitting data on analog voice lines. Unlike X.25, whose designers expected <a href="/facts/Analog_signal/xDbb4uB5">analog signals</a> with a relatively high chance of transmission errors, Frame Relay is a <a href="/facts/Fast_packet_switching/V2TE4RgU">fast packet switching</a> technology operating over links with a low chance of transmission errors (usually practically lossless like <a href="/facts/Plesiochronous_Digital_Hierarchy/oTrEENKx">PDH</a>), which means that the protocol does not attempt to correct errors. When a Frame Relay network detects an error in a frame, it simply drops that frame. The end points have the responsibility for detecting and retransmitting dropped frames. (However, <a href="/facts/Digital_network/3w5RM99p">digital networks</a> offer an incidence of error extraordinarily small relative to that of analog networks.) </p><p>Frame Relay often serves to connect <a href="/facts/Local_area_network/edUDxJ6J">local area networks</a> (LANs) with major <a href="/facts/Backbone_network/EondGP5q">backbones</a>, as well as on public wide-area networks (WANs) and also in private network environments with leased lines over T-1 lines. It requires a dedicated connection during the transmission period. Frame Relay does not provide an ideal path for voice or video transmission, both of which require a steady flow of transmissions. However, under certain circumstances, voice and video transmission do use Frame Relay. </p><p>Frame Relay originated as an extension of integrated services digital network (ISDN). Its designers aimed to enable a <a href="/facts/Packet-switched_network/olDlDP1R">packet-switched network</a> to transport over circuit-switched technology. The technology has become a stand-alone and cost-effective means of creating a WAN. </p><p>Frame Relay switches create virtual circuits to connect remote LANs to a WAN. The Frame Relay network exists between a LAN border device, usually a router, and the carrier switch. The technology used by the carrier to transport data between the switches is variable and may differ among carriers (i.e., to function, a practical Frame Relay implementation need not rely solely on its own transportation mechanism). </p><p>The sophistication of the technology requires a thorough understanding of the terms used to describe how Frame Relay works. Without a firm understanding of Frame Relay, it is difficult to troubleshoot its performance. </p><p>Frame-relay frame structure essentially mirrors almost exactly that defined for LAP-D. Traffic analysis can distinguish Frame Relay format from LAP-D by its lack of a control field.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p> <h3>Protocol data unit</h3> <p>Each Frame Relay <a href="/facts/Protocol_data_unit/UJMVQEt9">protocol data unit</a> (PDU) consists of the following fields: </p> <ol><li>Flag Field. The flag is used to perform high-level data link synchronization which indicates the beginning and end of the frame with the unique pattern 01111110. To ensure that the 01111110 pattern does not appear somewhere inside the frame, <a href="/facts/Bit_stuffing/y8UX3vI7">bit stuffing and destuffing</a> procedures are used.</li> <li>Address Field. Each address field may occupy either octet 2 to 3, octet 2 to 4, or octet 2 to 5, depending on the range of the address in use. A two-octet address field comprises the EA=ADDRESS FIELD EXTENSION BITS and the C/R=COMMAND/RESPONSE BIT. <ol><li>DLCI-Data Link Connection Identifier Bits. The <a href="/facts/DLCI/mWXLMWPk">DLCI</a> serves to identify the virtual connection so that the receiving end knows which information connection a frame belongs to. Note that this DLCI has only local significance. A single physical channel can <a href="/facts/Multiplexing/YE7hK8cw">multiplex</a> several different virtual connections.</li> <li>FECN, BECN, DE bits. These bits report congestion: <ul><li>FECN=Forward Explicit Congestion Notification bit</li> <li><a href="/facts/BECN/9ohkRMso">BECN</a>=Backward Explicit Congestion Notification bit</li> <li>DE=Discard Eligibility bit</li></ul></li></ol></li> <li>Information Field. A system parameter defines the maximum number of data bytes that a host can pack into a frame. Hosts may negotiate the actual maximum frame length at call set-up time. The standard specifies the maximum information field size (supportable by any network) as at least 262 octets. Since end-to-end protocols typically operate on the basis of larger information units, Frame Relay recommends that the network support the maximum value of at least 1600 octets in order to avoid the need for segmentation and reassembling by end-users.</li> <li>Frame Check Sequence (FCS) Field. Since one cannot completely ignore the bit error-rate of the medium, each switching node needs to implement error detection to avoid wasting bandwidth due to the transmission of <i>err</i>ed frames. The error detection mechanism used in Frame Relay uses the <a href="/facts/Cyclic_redundancy_check/u2exo4sv">cyclic redundancy check</a> (CRC) as its basis.</li></ol> <h3>Congestion control</h3> <p class="note">"FECN" redirects here. For the compound, see <a href="/facts/FeCN/6I3JQQDR">FeCN</a>.</p> <p>The Frame Relay network uses a simplified protocol at each switching node. It achieves simplicity by omitting link-by-link flow-control. As a result, the offered load has largely determined the performance of Frame Relay networks. When offered load is high, due to the bursts in some services, temporary overload at some Frame Relay nodes causes a collapse in network throughput. Therefore, Frame Relay networks require some effective mechanisms to control the congestion. </p><p><a href="/facts/Congestion_control/9ohkRMso">Congestion control</a> in Frame Relay networks includes the following elements: </p> <ol><li>Admission Control. This provides the principal mechanism used in Frame Relay to ensure the guarantee of resource requirement once accepted. It also serves generally to achieve high network performance. The network decides whether to accept a new connection request, based on the relation of the requested traffic descriptor and the network's residual capacity. The traffic descriptor consists of a set of parameters communicated to the switching nodes at call set-up time or at service-subscription time, and which characterizes the connection's statistical properties. The traffic descriptor consists of three elements:</li> <li><a href="/facts/Committed_information_rate/KMfADsgD">Committed information rate</a> (CIR). The average rate (in bit/s) at which the network guarantees to transfer information units over a measurement interval T. This T interval is defined as: T = Bc/CIR.</li> <li><a href="/facts/Committed_burst_size/zNrtT9KP">Committed burst size</a> (BC). The maximum number of information units transmittable during the interval T.</li> <li>Excess burst size (BE). The maximum number of uncommitted information units (in bits) that the network will attempt to carry during the interval.</li></ol> <p>Once the network has established a connection, the edge node of the Frame Relay network must monitor the connection's traffic flow to ensure that the actual usage of network resources does not exceed this specification. Frame Relay defines some restrictions on the user's information rate. It allows the network to enforce the end user's information rate and discard information when the subscribed access rate is exceeded. </p><p>Explicit congestion notification is proposed as the congestion avoidance policy. It tries to keep the network operating at its desired equilibrium point so that a certain <a href="/facts/Quality_of_service/joz9VkUm">quality of service</a> (QoS) for the network can be met. To do so, special congestion control bits have been incorporated into the address field of the Frame Relay: FECN and BECN. The basic idea is to avoid data accumulation inside the network. </p><p>FECN means forward explicit congestion notification. The FECN bit can be set to 1 to indicate that congestion was experienced in the direction of the frame transmission, so it informs the destination that congestion has occurred. BECN means backwards explicit congestion notification. The BECN bit can be set to 1 to indicate that congestion was experienced in the network in the direction opposite of the frame transmission, so it informs the <i>sender</i> that congestion has occurred. </p> <h2 id="origin">Origin</h2> <p>Frame Relay began as a stripped-down version of the X.25 protocol, releasing itself from the error-correcting burden most commonly associated with X.25. When Frame Relay detects an error, it simply drops the offending packet. Frame Relay uses the concept of shared access and relies on a technique referred to as "best-effort", whereby error-correction practically does not exist and practically no guarantee of reliable data delivery occurs. Frame Relay provides an industry-standard encapsulation, utilizing the strengths of high-speed, packet-switched technology able to service multiple virtual circuits and protocols between connected devices, such as two routers. Although Frame Relay became very popular in North America, it was never very popular in Europe. X.25 remained the primary standard until the wide availability of IP made packet switching almost obsolete. It was used sometimes as backbone for other services, such as X.25 or IP traffic. Where Frame Relay was used in the USA also as carrier for TCP/IP traffic, in Europe backbones for IP networks often used ATM or <a href="/facts/Packet_over_SONET%2fSDH/V7RSvI5c">PoS</a>, later replaced by <a href="/facts/Carrier_Ethernet/d6pkk6Ha">Carrier Ethernet</a><a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> </p> <h3>Relationship to X.25</h3> <p><a href="/facts/X.25/yaGPqw2Y">X.25</a> was an important early WAN protocol, and is often considered to be the grandfather of Frame Relay as many of the underlying protocols and functions of X.25 are still in use today (with upgrades) by Frame Relay.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> </p><p><a href="/facts/X.25/yaGPqw2Y">X.25</a> provides quality of service and error-free delivery, whereas Frame Relay was designed to relay data as quickly as possible over low error networks. Frame Relay eliminates a number of the higher-level procedures and fields used in X.25. Frame Relay was designed for use on links with error-rates far lower than available when X.25 was designed. </p><p>X.25 prepares and sends packets, while Frame Relay prepares and sends frames. X.25 packets contain several fields used for error checking and <a href="/facts/Flow_control_(data)/qcdKcLon">flow control</a>, most of which are not used by Frame Relay. The frames in Frame Relay contain an expanded <a href="/facts/Link_layer/pHRpQ3k7">link layer</a> address field that enables Frame Relay nodes to direct frames to their destinations with minimal processing. The elimination of functions and fields over X.25 allows Frame Relay to move data more quickly, but leaves more room for errors and larger delays should data need to be retransmitted. </p><p>X.25 packet switched networks typically allocated a fixed bandwidth through the network for each X.25 access, regardless of the current load. This resource allocation approach, while apt for applications that require guaranteed quality of service, is inefficient for applications that are highly dynamic in their load characteristics or which would benefit from a more dynamic resource allocation. Frame Relay networks can dynamically allocate bandwidth at both the physical and logical channel level. </p> <h2 id="virtual-circuits">Virtual circuits</h2> <p>As a WAN protocol, Frame Relay is most commonly implemented at Layer 2 (<a href="/facts/Data_link_layer/K9yPufbt">data link layer</a>) of the Open Systems Interconnection <a href="/facts/OSI_model/oxN9Xhjz">(OSI) seven layer model</a>. Two types of circuits exist: <a href="/facts/Permanent_virtual_circuit/8HqpnTxl">permanent virtual circuits</a> (PVCs) which are used to form logical end-to-end links mapped over a physical network, and <a href="/facts/Switched_virtual_circuit/8HqpnTxl">switched virtual circuits</a> (SVCs). The latter are analogous to the circuit-switching concepts of the <a href="/facts/Public_switched_telephone_network/eVrCTDU7">public switched telephone network</a> (PSTN), the global phone network. </p> <h2 id="local-management-interface">Local management interface</h2> <p class="note">Main article: <a href="/facts/Local_Management_Interface/NCgBEt3g">Local Management Interface</a></p> <p>Initial proposals for Frame Relay were presented to the Consultative Committee on International Telephone and Telegraph (<a href="/facts/ITU-T/9nJwkPYx">CCITT</a>) in 1984. Lack of interoperability and standardization prevented any significant Frame Relay deployment until 1990, when <a href="/facts/Cisco_Systems/ocDgQt6T">Cisco</a>, <a href="/facts/Digital_Equipment_Corporation/ztxs6keA">Digital Equipment Corporation</a> (DEC), <a href="/facts/Northern_Telecom/VYJnskS6">Northern Telecom</a>, and <a href="/facts/StrataCom/keJTNPbU">StrataCom</a> formed a consortium to focus on its development. They produced a protocol that provided additional capabilities for complex inter-networking environments. These Frame Relay extensions are referred to as the <a href="/facts/Local_Management_Interface/NCgBEt3g">local management interface</a> (LMI). </p><p>Datalink connection identifiers (<a href="/facts/DLCI/mWXLMWPk">DLCIs</a>) are numbers that refer to paths through the Frame Relay network. They are only locally significant, which means that when device-A sends data to device-B it will most likely use a different DLCI than device-B would use to reply. Multiple virtual circuits can be active on the same physical end-points (performed by using <a href="/facts/Subinterface/zdfp8unT">subinterfaces</a>). </p><p>The LMI global addressing extension gives Frame Relay data-link connection identifier (DLCI) values global rather than local significance. DLCI values become DTE addresses that are unique in the Frame Relay WAN. The global addressing extension adds functionality and manageability to Frame Relay internetworks. Individual network interfaces and the end nodes attached to them, for example, can be identified by using standard address-resolution and discovery techniques. In addition, the entire Frame Relay network appears to be a typical LAN to routers on its periphery. </p><p>LMI virtual circuit status messages provide communication and synchronization between Frame Relay <a href="/facts/Data_terminal_equipment/o7qvJVQq">DTE</a> and <a href="/facts/Data_circuit-terminating_equipment/asE4FHvh">DCE</a> devices. These messages are used to periodically report on the status of PVCs, which prevents data from being sent into black holes (that is, over PVCs that no longer exist). </p><p>The LMI multicasting extension allows multicast groups to be assigned. Multicasting saves bandwidth by allowing routing updates and address-resolution messages to be sent only to specific groups of routers. The extension also transmits reports on the status of multicast groups in update messages. </p> <h2 id="committed-information-rate">Committed information rate</h2> <p>Frame Relay connections are often given a <a href="/facts/Committed_information_rate/KMfADsgD">committed information rate (CIR)</a> and an allowance of <a href="/facts/Burstable/N7vVdYYQ">burstable</a> bandwidth known as the extended information rate (EIR). The provider guarantees that the connection will always support the C rate, and sometimes the PRa rate should there be adequate bandwidth. Frames that are sent in excess of the CIR are marked as <i>discard eligible</i> (DE) which means they can be dropped should congestion occur within the Frame Relay network. Frames sent in excess of the EIR are dropped immediately. </p> <h2 id="market-reputation">Market reputation</h2> <p>Frame Relay aimed to make more efficient use of existing physical resources, permitting the over-provisioning of data services by telecommunications companies to their customers, as clients were unlikely to be using a data service 45 percent of the time. In more recent years, Frame Relay has acquired a bad reputation in some markets because of excessive bandwidth <a href="/facts/Overbooking/KzpS9Xks">overbooking</a>. </p><p>Telecommunications companies often sell Frame Relay to businesses looking for a cheaper alternative to <a href="/facts/Dedicated_line/EUcgDjdM">dedicated lines</a>; its use in different geographic areas depended greatly on governmental and telecommunication companies' policies. Some of the early companies to make Frame Relay products included <a href="/facts/StrataCom/keJTNPbU">StrataCom</a> (later acquired by <a href="/facts/Cisco_Systems/ocDgQt6T">Cisco Systems</a>) and <a href="/facts/Cascade_Communications/6uTaKLr2">Cascade Communications</a> (later acquired by <a href="/facts/Ascend_Communications/ANNFyaPk">Ascend Communications</a> and then by <a href="/facts/Lucent_Technologies/uzgpVmLa">Lucent Technologies</a>). </p><p>As of June 2007, <a href="/facts/AT%2526T/y3Lo9uhk">AT&T</a> was the largest Frame Relay service provider in the US, with local networks in 22 states, plus national and international networks. </p> <h2 id="frf12">FRF.12</h2> <p>When multiplexing packet data from different virtual circuits or flows, <a href="/facts/Quality_of_service/joz9VkUm">quality of service</a> concerns often arise. This is because a frame from one virtual circuit may occupy the line for a long enough period of time to disrupt a service guarantee given to another virtual circuit. <a href="/facts/IP_fragmentation/efmuF7f2">IP fragmentation</a> is a method for addressing this. An incoming long packet is broken up into a sequence of shorter packets and enough information is added to reassemble that long frame at the far end. FRF.12 is a specification from the <a href="/facts/Frame_Relay_Forum/cxY92Q0T">Frame Relay Forum</a> which specifies how to perform fragmentation on frame relay traffic primarily for voice traffic. The FRF.12 specification describes the method of fragmenting Frame Relay frames into smaller frames.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a><a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a><a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a><a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a><a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Multiprotocol_Label_Switching/k7cx1PWw">Multiprotocol Label Switching</a></li> <li><a href="/facts/List_of_interface_bit_rates/RJzvfP0g">List of interface bit rates</a></li></ul> <h2 id="external-links">External links</h2> <ul><li>RFC <a href="https://www.rfc-editor.org/rfc/rfc1490">1490</a> – Multiprotocol Interconnect over Frame Relay</li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc1973">1973</a> – PPP in Frame Relay</li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc2427">2427</a> – Multiprotocol Interconnect over Frame Relay</li> <li><a href="https://www.broadband-forum.org/technical/ipmplstechspec.php">Broadband Forum - IP/MPLS Forum, MPLS Forum, ATM, and Frame Relay Forum Specifications</a> <a href="https://web.archive.org/web/20160803184823/https://www.broadband-forum.org/technical/ipmplstechspec.php">Archived</a> 2016-08-03 at the <a href="/facts/Wayback_Machine/nmQ3a6JC">Wayback Machine</a></li> <li><a href="http://docwiki.cisco.com/wiki/Frame_Relay">Cisco Frame Relay Tutorial</a> <a href="https://web.archive.org/web/20121106101953/http://docwiki.cisco.com/wiki/Frame_Relay">Archived</a> 2012-11-06 at the <a href="/facts/Wayback_Machine/nmQ3a6JC">Wayback Machine</a></li> <li><a href="https://web.archive.org/web/20120316134019/http://www.visualland.net/view.php?cid=1336&protocol=Frame%20Relay&title=1.%20Frame%20Relay%20Basics&ctype=2">Frame Relay animation</a>[<i>usurped</i>]</li> <li><a href="http://www.itu.int/rec/T-REC-I.233">CCITT I.233 ISDN Frame Mode Bearer Services</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"Definition of "Frame Relay" on SearchEnterpriseWAN". Archived from the original on 9 April 2012. Retrieved 9 April 2012. <a href="https://web.archive.org/web/20120409171824/http://searchenterprisewan.techtarget.com/definition/frame-relay" target="_blank">https://web.archive.org/web/20120409171824/http://searchenterprisewan.techtarget.com/definition/frame-relay</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>US 7333508, Rabie, Sameh; Magd, Osama Aboul & Abdullah, Bashar et al., "Method and system for Ethernet and frame relay network interworking", published 2008-02-19, issued 2004-12-09, assigned to Nortel Networks Ltd. <a href="https://worldwide.espacenet.com/textdoc?DB=EPODOC&IDX=US7333508" target="_blank">https://worldwide.espacenet.com/textdoc?DB=EPODOC&IDX=US7333508</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>The Network Encyclopedia about Frame Relay, visited 14 July 2012 <a href="http://www.thenetworkencyclopedia.com/d2.asp?ref=798" target="_blank">http://www.thenetworkencyclopedia.com/d2.asp?ref=798</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"Frame relay". techtarget.com. <a href="https://searchenterprisewan.techtarget.com/definition/frame-relay" target="_blank">https://searchenterprisewan.techtarget.com/definition/frame-relay</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"Frame Relay Fragmentation for Voice". Cisco. Retrieved 17 June 2016. <a href="http://www.cisco.com/c/en/us/support/docs/voice/voice-over-frame-relay-vofr/9232-fr-frag.html" target="_blank">http://www.cisco.com/c/en/us/support/docs/voice/voice-over-frame-relay-vofr/9232-fr-frag.html</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"How to use FRF.12 to improve voice quality on Frame Relay networks | Other Collaboration, Voice, and Video Subjects | Cisco Support Community | 5791 | 11956". supportforums.cisco.com. 18 June 2009. <a href="https://supportforums.cisco.com/document/11956/how-use-frf12-improve-voice-quality-frame-relay-networks" target="_blank">https://supportforums.cisco.com/document/11956/how-use-frf12-improve-voice-quality-frame-relay-networks</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"VoIP over Frame Relay with Quality of Service (Fragmentation, Traffic Shaping, LLQ / IP RTP Priority)". Cisco. Retrieved 17 June 2016. <a href="http://www.cisco.com/c/en/us/support/docs/voice/voice-quality/12156-voip-ov-fr-qos.html" target="_blank">http://www.cisco.com/c/en/us/support/docs/voice/voice-quality/12156-voip-ov-fr-qos.html</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>Malis, Andrew G. "Frame Relay Fragmentation Implementation Agreement FRF.12" (PDF). www.broadband-forum.org. Archived (PDF) from the original on 2022-10-09. Retrieved 17 June 2016. <a href="https://www.broadband-forum.org/technical/download/FRF.12/frf12.pdf" target="_blank">https://www.broadband-forum.org/technical/download/FRF.12/frf12.pdf</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>"FRF.12 Frame Relay Fragmentation section in Frame Relay". www.rhyshaden.com. Retrieved 17 June 2016. <a href="http://www.rhyshaden.com/frame.htm" target="_blank">http://www.rhyshaden.com/frame.htm</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> </ol>