Asynchronous Transfer Mode (ATM) as a new important networking technology \t\t\t\t\t offers many benefits (higher capacity, bandwidth, scalability etc.). Given the \t\t\t\t\t vast installed base of Local Area Networks (LAN), the success of ATM lies largely \t\t\t\t\t in its ability to allow interoperability between LAN technologies and ATM. LANE \t\t\t\t\t is a standard developed by the ATM Forum, that allows legacy networks, legacy \t\t\t\t\t protocols and applications to operate unchanged over ATM. This paper shortly \t\t\t\t\t describes LANE basic principle and functions.<\/p>\n
The main function of the LANE protocols is to emulate a LAN on the top of the ATM network. Specifically, mechanisms have been defined for emulating of either an IEEE 802.3 Ethernet or an 802.5 Token Ring. LANE protocol does not define mechanism for emulation of FDDI networks. LANE protocol defines a service interface for higher layers (network layer)protocols. The packets of these networks protocols are sent across the ATM network to be encapsulated in the appropriate LAN MAC packet format. The LANE protocols make an ATM network look and behave to network protocols like an Ethernet or token ring LAN, but operating at higher speed than a real network. The LANE services present the same interface of existing MAC protocols to network layer drivers, hence no changes are required in those drivers. In this way the IP protocol (and others) that is running previously on Ethernet and Token Ring, requires no modifications to operate over the ATM network. This helps to accelerate deployment of the ATM.<\/p>\n
<\/p>\n
The basic function of the LANE protocol is to map MAC addresses into \t\t\t\t\t ATM addresses. The goal of LANE is to perform such address mappings so that \t\t\t\t\t LANE end systems on LANs can connect to other end systems in LANs, as well as \t\t\t\t\t to ATM-attached servers, routers, and switches.<\/p>\n
<\/p>\n
The LANE protocol defines operation of a single Emulated LAN (ELAN) only. There are two types of Emulated LAN: Ethernet\/IEEE 802.3 or IEEE 802.5 (Token Ring). Each Emulated LAN is composed of a set of LAN Emulation Clients (LECs) and a single LAN Emulation Service (LE Service). This LE Service consists of one or more LE Configuration Servers (LECS), one or more LE Servers (LES), and one or more Broadcast and Multicast Servers (BUS) [LANE2]. Multiple ELANs may coexist simultaneously in a single ATM network. However, each of the ELANs is logically independent from the others and for communication between them, some type of interconnection device (router, bridge) is required.<\/p>\n
<\/p>\n
<\/p>\n
LAN Emulation Client (LEC):<\/b><\/p>\n
The LEC is the entity of an end system that \t\t\t\t\t performs data forwarding and address resolution, and other control functions \t\t\t\t\t for a single end system within a single ELAN. Each of the LECs has a unique \t\t\t\t\t ATM address, and is associated with one or more MAC addresses, which are reachable \t\t\t\t\t through this ATM address.<\/p>\n
<\/p>\n
<\/p>\n
LAN Emulation Server (LES):<\/b><\/p>\n
The LES implement control co-ordination function for the Emulated LAN. The LES provides facility for registering and \t\t\t\t\t resolving of unicast and multicast MAC addresses and\/or to route descriptors \t\t\t\t\t to ATM addresses.<\/p>\n
<\/p>\n
<\/p>\n
Broadcast and Unknown Server (BUS):<\/b><\/p>\n
The Broadcast and Unknown Servers handle \t\t\t\t\t data sent by clients to the broadcast MAC address, multicast data and initial \t\t\t\t\t unicast data which are sent by a LEC before the data direct connection is built \t\t\t\t\t between two LECs.<\/p>\n
<\/p>\n
<\/p>\n
LAN Emulation Configuration Server (LECS):<\/b><\/p>\n
The LECS is an entity that assign individual \t\t\t\t\t LANE clients to particular ELANs by giving them the appropriate LES ATM address, \t\t\t\t\t that corresponds to the ELAN. <\/p>\n
The LANE entities communicate with each other \t\t\t\t\t using series of ATM connections. LECs maintain separate connections for data \t\t\t\t\t transmission and for control traffic. LANE v2 ads support for LLC-multiplexed \t\t\t\t\t Virtual Circuit Connections (VCCs).<\/p>\n
The control connections are:<\/i><\/b> \t\t\t\t\t
\n1. Configurations Direct VCC:<\/i><\/p>\n
a bi-directional VCC set up by the LEC (or \t\t\t\t\t other entity) is used to obtain configuration information from a LECS.<\/p>\n
2.Control Direct VCC:<\/i><\/p>\n
a bi-directional, point-to-point VCC, set up by the \t\t\t\t\t LEC to the LES for sending control traffic.<\/p>\n
\n3. Control Distribute VCC:<\/i><\/p>\n
unidirectional point-to-multipoint VCC that may be \t\t\t\t\t optionally established by the LES to distribute control traffic to the LEC.<\/p>\n
The data connections are:<\/i><\/b> \t\t\t\t\t
\n1. Data-Direct VCC:<\/i><\/p>\n
a bi-directional point-to-point VCC, which is set up \t\t\t\t\t between LECs.<\/p>\n
\n2.Multicast Send VCCs:<\/i><\/p>\n
A LEC sets up one or more bi-directional point-to-point \t\t\t\t\t VCCs to the BUS, they are used for all unknown, broadcast and multicast data.<\/p>\n
\n3. Multicast Forward VCCs: <\/i><\/p>\n
unidirectional point-to-point VCCs, which the BUS may \t\t\t\t\t additionally set up to the LECs. <\/p>\n
<\/p>\n
The LANE system and components operation \t\t\t\t\t may be described through the following stages:<\/p>\n
<\/p>\n
Upon initialization (such power up) a LEC \t\t\t\t\t has to contacts the LECS. The mechanisms used to find a LECS are the following: \t\t\t\t\t 1) to configure the ATM address of the LECS into the LEC. 2) to get it through \t\t\t\t\t Interim Local Management Protocol (ILMI). 3) to use well-known address [LANE2] \t\t\t\t\t to open a configuration VCC. After finding the location of the LECS, the LEC \t\t\t\t\t will establish the Configuration Direct VCC to the LECS. Through configuration \t\t\t\t\t protocols it informs the LECS about its ATM addresses, type of the LAN, name \t\t\t\t\t of the ELAN and the maximum frame size. The LECS provides to the LEC the information \t\t\t\t\t that is required for connection into its target ELAN. This includes the ATM \t\t\t\t\t address of the LES, the type of ELAN, the maximum frame size and the ELAN name.<\/p>\n
<\/p>\n
After the LEC obtains the LES ATM \t\t\t\t\t address, it sets up the control direct VCC to the LES. The LEC registers its \t\t\t\t\t ATM address, the MAC address, the type of LAN, the maximum data frame size, \t\t\t\t\t the ELAN name and whether it works as proxy. The LES sets up the control distribute \t\t\t\t\t VCC back to the LEC and assigns its own a unique LEC ID (LE Client identifier) \t\t\t\t\t to the LECS, the ELAN name, the maximum frame data size, and the LAN type. After \t\t\t\t\t this join phase LEC may attempt to register any number unicast and multicast \t\t\t\t\t MAC addresses (if the LEC is a proxy) for which it is responsible.<\/p>\n
Address resolution is a procedure by the \t\t\t\t\t means of which the LEC associates LAN MAC destination address with the particular \t\t\t\t\t ATM address of another LEC or BUS. For this purpose (already established) Control \t\t\t\t\t Direct VCC and Control Distribute VCC between the LEC and the LES are used. \t\t\t\t\t If the LEC needs to know the ATM address of the destinations, the LEC formulates \t\t\t\t\t LE_ARP request (LAN Emulation Address Resolution Protocol) and sends it to the \t\t\t\t\t LES. If the LES recognises this, it reply to the relevant LEC. If the LES does \t\t\t\t\t not know mapping, the LE_ARP is distributed to all LECs by the means the Control \t\t\t\t\t Distribute VCC.<\/p>\n
<\/p>\n
The LES might not know mapping – it is because \t\t\t\t\t of the address of a node is behind the LEC, that is a type of a bridge – in \t\t\t\t\t a side of a network, which the bridge connect to the ATM network. The LEC may \t\t\t\t\t not have registered all these addresses, for which it works as proxy. The LECs \t\t\t\t\t working as proxy nodes have been registered to the LES in joining phase as a \t\t\t\t\t proxy, hence redirection LE_ARP requests have to sent only these LECs.<\/p>\n
<\/p>\n
When the LES obtains from the LEC \t\t\t\t\t this ATM address, which is proxying for that MAC address, the LES will forward \t\t\t\t\t the response to the requesting LEC, or optionally to all LECs, that can learn \t\t\t\t\t and cache the particular address mapping.<\/p>\n
The LE_ARP mechanism explained above \t\t\t\t\t is used by the LEC to determine the ATM address of the BUS. It does it by sending \t\t\t\t\t a LE_ARP request for the « all ones » MAC broadcast address to the \t\t\t\t\t LES, which respond with the BUS’s ATM address. The LEC then sets up the Multicast \t\t\t\t\t Send VCC to the BUS and the BUS set up back to the LEC the Multicast Forward \t\t\t\t\t VCC.<\/p>\n
The LEC may receive either network layer \t\t\t\t\t packets to transmit from a higher layer protocol (in the case of NIC), or it \t\t\t\t\t receives a MAC packet to forward across a LAN port (in the case a LAN switch). \t\t\t\t\t In the first case, the LEC search in its internal cache table (if any exist) \t\t\t\t\t for MAC address to ATM address mapping, that it learns through a LE_ARP.<\/p>\n
<\/p>\n
In the case, when the LEC has no ATM address \t\t\t\t\t of a destination, it formulates a LE_ARP request and sends it to the LES. Waiting \t\t\t\t\t for a response, the LEC forwards also the frame to the BUS that will forward \t\t\t\t\t the frame to at least all proxy clients. This must be done, because in an Emulated \t\t\t\t\t LAN the case can arise, when the LEC does not know where the MAC address is \t\t\t\t\t located (when the destinations of frame are reached through a passive device). \t\t\t\t\t Similarly, as in a case of a learning bridge, a LEC will learn the location \t\t\t\t\t of the device if and only if it responds to the flooded frame. Additionally, \t\t\t\t\t resolving a LE_ARP or establishing a Data Direct VCC may take some time and \t\t\t\t\t many network protocols are intolerant of either loss (if the LEC choose to discard \t\t\t\t\t the frame while waiting to the LE_ARP response), or latency (if the frame is \t\t\t\t\t buffered).<\/p>\n
<\/p>\n
If the LEC already knows the ATM address \t\t\t\t\t (an LE_ARP respond is received), the LEC then sets up a Data Direct VCC to the \t\t\t\t\t destination node. Before it, the LEC must use the LANE<\/p>\n
Flush procedure<\/i><\/p>\n
to ensure that all frame previously sent to the BUS were delivered to the destination \t\t\t\t\t prior to using of the data direct VCC. For this purpose, a control cell is sent \t\t\t\t\t down the first transmission path, following the past packet. The Flush procedure \t\t\t\t\t allows the sender to avoid the possibility delivering frames out of order that \t\t\t\t\t can cause multiple paths. Since Token Ring and Ethernet LANs do not permit delivery \t\t\t\t\t of frames out of order, applications designed to run over LANs do not always \t\t\t\t\t have robust mechanisms for dealing with out of order frames.<\/p>\n
<\/p>\n
The BUS is also used for broadcast and multicast \t\t\t\t\t frames, which are forwarding to all LECs. It can cause that the source LEC may \t\t\t\t\t receive a copy of its own frame. Since some protocols cannot tolerate it, the \t\t\t\t\t LANE packets use a prefix with the LEC ID. The LECs then filter this field for \t\t\t\t\t all frames received from the BUS to ensure that it never receives its own frames. <\/p>\n
<\/p>\n
A LEC locally caches any address mappings \t\t\t\t\t that it learns through the LE_ARP. When the LEC receives packets and has mappings \t\t\t\t\t for a particular MAC address, it uses them rather then sending of another LE_ARP. \t\t\t\t\t Such entries will be cleared aged out over configurable time period.<\/p>\n
LANE is a possible way how to run existing network applications across the ATM network, and how \t\t\t\t\t to interconnect the installed base of the Ethernet and Token Ring LANs with \t\t\t\t\t the ATM network. But it has also some disadvantage, such as preventing of the \t\t\t\t\t user from taking advantage of some of ATM’s feature (for example limited ability \t\t\t\t\t to specify Quality of Service). LANE is the first step in transition of networks \t\t\t\t\t to ATM connectivity.<\/p>\n
[LANE] The ATM Forum – "LAN Emulation \t\t\t\t\t Over ATM Specification – Version 1", ATM Forum Specification, January 1995<\/p>\n
[LANE2] The ATM Forum -"LAN Emulation Over \t\t\t\t\t ATM Version 2 – LUNI Specification", ATM Forum Specification, July 1997<\/p>\n
C.Rigault, \t\t\t\t\t P.Martins, T.Ková\u010diková: Signaling Requirements and Network Information Models \t\t\t\t\t for Multimedia Session and Call Control”, ICT’98 – International Conference \t\t\t\t\t on Telecommunications, Porto Carras, Greece, 22.-25.June 1997<\/p>\n
T. Ková\u010diková \t\t\t\t\t – COST257: “Impacts of New Services on the Architecture and \t\t\t\t\t Performance of Broadband Services”, ro\u010dná hodnotiaca správa medzinárodného projektu \t\t\t\t\t za rok 1997, \u017dilina 9.1.1997<\/p>\n
Summary<\/span><\/b><\/p>\n LANE je jednou z mo\u017eností ako zabezpe\u010di\u0165 beh sie\u0165ových aplikácii nad ATM \t\t\t\t\t sie\u0165ou a ako prepoji\u0165 u\u017e inštalované LAN siete typu Ethernet a Token Ring so \t\t\t\t\t sie\u0165ou ATM. Ale takisto toto riešenie má ur\u010dité nevýhody, ktoré bránia u\u017eívate\u013eovy \t\t\t\t\t vyu\u017ei\u0165 niektoré z vlastnosti ATM (napríklad LANE poskytuje u\u017eívate\u013eovy \t\t\t\t\t limitované mo\u017enosti špecifikova\u0165 QoS). LANE je prvý krok pri prechode sietí \t\t\t\t\t smerom k ATM konektivite.<\/span><\/i><\/p>\n LANE ist eine aus den M<\/span><\/i>öglichkeiten, \t\t\t\t\t wie kann man der Betrieb den Netzaplikationen über ATM Netz zu sichern und wie \t\t\t\t\t kann man schon instalierte LAN Netze von den Typen Ethernet und Token Ring zu \t\t\t\t\t verbinden. Diese Lösung hat bestimmte Urteile, die dem Benutzer nicht ermöglicht \t\t\t\t\t einige von den ATM Eingenschaften zu benutzen (Zum Beispiel LANE bietet dem \t\t\t\t\t Benutzer die limitierenden Möglichkeiten für die QoS Spezifikation. LANE ist \t\t\t\t\t der erste Schritt bei dem Übergang der Netze in der Richtung zur ATM Konektivität.<\/span><\/i><\/p>","protected":false},"excerpt":{"rendered":"LAN Emulation over ATM (LANE)<\/h2>\n
1.0 Introduction<\/h4>","protected":false},"author":8,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[629],"tags":[],"class_list":["post-98","post","type-post","status-publish","format-standard","hentry","category-atm-interworking-lane-en"],"taxonomy_info":{"category":[{"value":629,"label":"LANE"}]},"featured_image_src_large":false,"author_info":{"display_name":"Peter Seemann","author_link":"https:\/\/nil.uniza.sk\/en\/author\/peter-seemann\/"},"comment_info":6,"category_info":[{"term_id":629,"name":"LANE","slug":"atm-interworking-lane-en","term_group":0,"term_taxonomy_id":627,"taxonomy":"category","description":"","parent":625,"count":1,"filter":"raw","cat_ID":629,"category_count":1,"category_description":"","cat_name":"LANE","category_nicename":"atm-interworking-lane-en","category_parent":625}],"tag_info":false,"_links":{"self":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts\/98","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/comments?post=98"}],"version-history":[{"count":0,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts\/98\/revisions"}],"wp:attachment":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/media?parent=98"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/categories?post=98"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/tags?post=98"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}