D. Grossmann and J. Heinanen. Multiprotocol Encapsulation over ATM Adaptation Layer 5. Proposed Standard RFC 2684, September 1999. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
New Transport Services for Next-Generation SONET/SDH Systems - Cavendish, al. (2002) (Correct)
....cell delineation. However, as opposed to ATM, GFP allows variable length payloads, which enhances the effective bandwidth for packet transport. For example, in current Ethernet over ATM over SONET SDH framing, 1500 bytes of Ethernet frame is first encapsulated with ATM adaptation layer 5 (AAL5) [6], resulting in 1536 bytes with appropriate padding and CPCS PDU trailer. These bytes are then divided into 32 pieces of 48 bytes each. Finally, a 5 byte header is added to each 48 bytes of data, resulting in a total of 1696 bytes for 1500 bytes of Ethernet data. Overall, as much as 13 percent cell ....
J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5," IETF RFC 1483, July 1993.
Design of a Medical-Video-on-Demand System over ATM-Networks - Wolf (1997) (Correct)
....current Windows 95 driver for the Efficient Networks ATM card supports Multiprotocol Encapsulation, Classical IP over ATM or LAN Emulation. The protocol that was found easiest to simulate in the server software is Multiprotocol Encapsulation or Bridged Ethernet according to RFC 1483 section 4. 2 [8]. This protocol is used to forward Ethernet packets over an ATM network. The structure of an AAL5 frame for Bridged Ethernet is shown in Figure 5. FIGURE 5. Data encapsulation for Bridged Ethernet The data is prepended with a User Datagram Protocol (UDP) header. It contains the port number used ....
....6.1 ATM under Microsoft Windows The Efficient Network ATM adapter can be set to operate in one of three different modes under Windows 95 Windows NT: Multiprotocol Encapsulation, Classical IP over ATM or LAN Emulation. For this project Multiprotocol Encapsulation (according to RFC 1483 [8]) was chosen because it requires few changes in the server software and is easy to use under Windows. network playback workstation playback format translator software playback user interface user TCPconnection UDPconnection (ATM) 6.1.1 Installation To install the network adapter open the ....
Heinanen, Juha: "Multiprotocol Encapsulation over ATM Adaptation Layer 5", Request for Comments: 1483, July 1993.
On the Impact of Long-Range-Dependent Traffic in Dimensioning.. - Lin, Suda (1998) (Correct)
....connectionless services using AAL5 protocol. In IP over ATM, for example, AAL5 provides the equivalent of data link layer services to support IP. As IP packets enter the ATM network, they are encapsulated into AAL5 frames for transmission according to the IETF stan dard as shown in Figure 2 [11, 12]; and AAL5 frames are segmented into cells for transmission. Within the ATM network, cells from various connections are reassembled into AAL5 frames at an IP router before they are forwarded to the IP router of the next logical IP subnet (see Figure 3) The buffer space required for the above ....
J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5," RFC 1683, July 1993.
Design and Implementation of a Full Bandwidth ATM.. - Paul, Laurent.. (2001) (Correct)
....limited to the analysis of the first ATM cell of AAL5 frames. Since AAL5 frames generally include a whole IP packet, the firstATM cell usually includes the IP and transport headers. Figure 4 describes the fields that can usually be found within the firstATM cell when Classical IP over ATM [17] is used (CLIP1 provides the content of the cell for SNAP LLC encapsulation, whereas CLIP2 provides the content of the cell when NULL encapsulation is used) FIGURE 4. FIRST ATM CELL ANALYSIS. As described in Figure 4, most of the information generally used by traditional packet filters can be ....
D. Grossman, J. Heinanen, RFC 2694, Multiprotocol Encapsulation over ATM Adaptation Layer 5, September 1999.
The BETEUS (Broadband Exchange for Trans-European USage).. - Walter, Brunner, al. (Correct)
....the underlying communication infrastructure. Although all BETEUS user sites now run FORE ATM switches [5] this was not obvious when the design of the communication platform was started. But, at that time, it was apparent that IP connectivity was available for all partners either directly over ATM [6] [7] or SMDS (Switched Multimegabit Data Service) Secondly, the communication platform can be extended so that IP multicast facilities [8] can be used for point to multipoint communication as is requested by tele teaching applications. Thirdly, sockets are flexible in the sense that a different ....
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
The Internetworking of Connectionless Data Networks.. - Hong, Vickers, Suda.. (1994) (1 citation) (Correct)
....do now. The IETF has taken a slightly different approach from the ATM Forum, opting instead to support connectionless service through the network layer rather than through the MAC sublayer. The IETF solution consists of encapsulating IP frames with IEEE 802.2 LLC and IEEE 802.1a SNAP headers [2]. The encapsulated IP frames are then stored in the payload of an AAL 5 PDU for subsequent segmentation and transmission via the ATM network. Address resolution in the IETF model of connectionless service is achieved through the use of ARP servers located in each IP subnet [3] Interconnection of ....
J. Heinanen, "Multiprotocol encapsulation over ATM Adaptation Layer 5," NIC Request for Comments 1483, July 1993. 14
Impact of Network Performance Parameters on the End-to-End.. - Yamamoto, Beerends (Correct)
....PCR can be directly derived from the maximum datagram size M (since the rate R=r is chosen in function of M) by taking into account the additional protocol overhead and then converting the result from bytes per second to cells per second. Following the encapsulation schemes defined in RFC1483 [10] (VC multiplexing or LLC encapsulation for IP over AAL5) up to 8 extra bytes of header overhead have to be taken in to account, in addition to the 8 bytes of the AAL5 trailer. PCR can be then calculated as follows: PCR M drate M hsize 16 48 . where drate is the codec data rate equal ....
....and thus improved with respect to the pure IP solution. The worst case would be when all the IP elements are connected via disjoint ATM networks (no shortcuts possible) In this case little benefit can be taken from IP over ATM compared to pure IP or ATM. 3.3. 2 Data loss According to RFC1483 [10] an IP packet must be discarded in case of AAL5 CRC mismatch, which occurs due to lost ATM cells, or cells containing errors. Considering this, a worst case approximation on the IP packet loss ratio (IP plr) as a function of ATM CLR (Cell Loss Ratio) and CER (Cell Error Ratio) given the maximum ....
J. Heinanen, Multiprotocol Encapsulation over ATM Adaptation Layer 5, RFC 1483, July 1993.
Reconfigurable Router Modules Using Network Protocol Wrappers - Braun, Lockwood, Waldvogel (2001) (3 citations) (Correct)
....are sent as multiple cells. Several adaption layers have been specified, which differ in the property of being connection oriented or connectionless, in the ability to multiplex several protocols over one virtual channel and to reorder cells during transmission. In the ATM Adaption Layer 5 (AAL5) [7, 8] datagrams or frames of arbitrary length are put into protocol data units (PDU) A PDU s length is always a multiple of 48 octets, because a PDU is sent as a multiple of ATM cells. One bit in the ATM header, the user bit of the PTI field, is used to indicate whether a cell is the last one of a ....
Juha Heinanen. Multiprotocol encapsulation over ATM adaptation layer 5. Internet RFC 1483, July 1993.
Firewalls for ATM Networks - Ellermann, Benecke (1998) (1 citation) (Correct)
....extract the information required for filtering from cells, thus avoiding reassembly. To understand how this could be implemented, a short description of the transmission mechanisms for IP datagrams over ATM networks is required. The CLIP protocol stack is shown in figure 1. First, a SNAP header [Heinanen 93] is prepended to an IP datagram. The SNAP header identifies the transmitted payload as IP. SNAP header (8 bytes) and IP datagram are then encapsulated in an AAL 5 frame (see [Peterson et al. 96] The AAL 5 frame has a trailer of 8 bytes. It also contains a variable number of padding bytes to ....
Juha Heinanen. "Multiprotocol Encapsulation over ATM Adaptation Layer 5". RFC 1483, July 1993. (ftp://ds.internic.net/rfc/rfc1483.txt)
The Internetworking of Connectionless Data Networks.. - Hong, Vickers.. (1994) (1 citation) (Correct)
....do now. The IETF has taken a slightly different approach from the ATM Forum, opting instead to support connectionless service through the network layer rather than through the MAC sublayer. The IETF solution consists of encapsulating IP frames with IEEE 802.2 LLC and IEEE 802.1a SNAP headers [5]. The encapsulated IP frames are then stored in the payload of an AAL 5 PDU for subsequent segmentation and transmission via the ATM network. Address resolution in the IETF model of connectionless service is achieved through the use of ARP servers located in each IP subnet [6] Interconnection of ....
J. Heinanen, "Multiprotocol encapsulation over ATM Adaptation Layer 5," IETF Network Working Group RFC 1483, July, 1993.
KANGA: A framework for building application specific communication .. - Babai (Correct)
....inherit from both the user developed NFS service class and the MemMap class to provide memory mapped access to both local and remote files through the same FILE class interface. The current hierarchy could also be made wider and deeper to provide an interface to other protocols, such as ATM AAL5[Hei93, Int93a] This might involve a RAW SAP abstract class deriving from IPC SAP. Then ATM and Ethernet classes could be derived from RAW SAP. Having more direct access to the network, but still following the ACE design goal of type safe and simple interfaces, may provide better performance for the ....
J. Heinanen. Multiprotocol encapsulation over ATM adaptation layer 5. Request for Comments (Experimental) RFC 1483, Internet Engineering Task Force, July 1993. BIBLIOGRAPHY 184
Experiences with TCP/IP over an ATM OC12 WAN - Nitzan, Tierney (1999) (1 citation) (Correct)
....Mbps) 622.08 Mbps 23.04 Mbps = 599.04 Mbps 4 The ATM overhead is 5 bytes per 53 byte cell, or 9.43 : 599.04 Mbps (9. 43 of 599.04 Mbps) 599.04 Mbps 56.49 Mbps = 542.55 Mbps The ATM Adaptation Layer 5 (AAL5) SubNetwork Attachment Point (SNAP) in this case, is 16 bytes per PDU [JH93]. Given that the MTU was near 9180 bytes, the AAL5 SNAP is less than .09 overhead leaving the IP layer approximately 542.06 Mbps. Figure 4. This shows the theoretical bandwidth available after protocol overhead. 2.0.1 HP Analyzer Throughput Testing The rates achieved with these ATM level tests ....
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", July 1993. RFC 1483.
Robust IP Backbone Network Utilizing WDM Optical Paths - Watanabe, Okamoto, Sato (1999) (Correct)
....will be decreased. The IP packets are accommodated in the optical path payload via layer 2 frames (e.g. point to point protocol 1116 IEICE TRANS. COMMUN. VOL. E82 B, NO. 8 AUGUST 1999 (PPP) 3] high level data link control (HDLC) 4] classical IP over ATM [5] multiprotocol overATM (MPOA) [6], frame relay (FR) 7] or simplified data link (SDL) 8] The detailed optical signal format and layer structure are described in Sects. 2.3 and 3.1, respectively. The layer 2 frame plays a key role in forming stream type data from the burst IP packet data. 2.2 Tera Bit Class PTS PTS ....
J.Heinanen, "Multiprotocol encapsulation overATM adaptation layer 5," IETF RFC 1483, July 1993.
The Impact of the Internet on Telecommunication.. - Hubaux, Gbaguidi.. (1998) (6 citations) (Correct)
....such as the Gigabit Ethernet [62] and Terabit Switches Routers [63] can deliver satisfying QoS at a lower cost than ATM. Certainly, ATM still has a future as a backbone technology, or in combined scenarios with other protocols, such as IP over ATM [64] multiprotocol encapsulation over ATM [65], and AREQUIPA [66] However, local area networks will continue to be primarily frame rather than cell based; hence, the end systems will continue to have to cope with this technology. It becomes more and more likely that the B ISDN will in fact be based on the Internet Intranet technologies, ....
J. Heinanen, Multiprotocol Encapsulation over ATM Adaptation Layer 5, IETF RFC 1483, July 1993.
IP Integrated Services with RSVP over ATM - Berson, Berger (1996) (12 citations) (Correct)
....encapsulation for both RSVP packets and associated IP data packets must be defined. There are currently two encapsulation options for running IP over ATM, RFC 1483 and LANE. There is also the possibility of future encapsulation options, such as MPOA[3] The first option is described in RFC 1483[9] and is currently used for Classical IP over ATM and NHRP. Berson, Berger Expires May 26, 1997 [Page 22] Internet Draft Integrated Services with RSVP over ATM November 1996 The second option is LAN Emulation, as described in [2] LANE encapsulation does not currently include a QoS signalling ....
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5," RFC 1483.
Connectionless Service for Public ATM Networks - Vickers, Suda (1994) (7 citations) (Correct)
....approach from the ATM Forum, choosing instead to support connectionless service for ATM end systems through existing connectionless network layers (i.e. IP) rather than through the MAC sublayer. The IETF solution consists of encapsulating IP frames with IEEE 802.2 LLC and IEEE 802.1a SNAP headers [2]. The encapsulated IP frames are then stored in the payload of an ATM Adaptation Layer 5 (AAL 5) convergence sublayer PDU for subsequent segmentation and transmission via the ATM network. Address resolution in the IETF model of connectionless service is achieved through the use of ARP servers ....
J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5," Request for Comments 1483, July 1993.
RSVP over ATM Implementation Requirements - Berger (1997) (5 citations) (Correct)
....per [11] Berger Expires January 11, 1998 [Page 6] Internet Draft RSVP over ATM Requirements July 1997 2.5 Encapsulation There are multiple encapsulation options for data sent over RSVP triggered QoS VCs. All RSVP over ATM implementations MUST be able to support LLC encapsulation per RFC 1483[12] on such QoS VCs. Implementations MAY negotiate alternative encapsulations using the B LLI negotiation procedures defined in ATM Signalling, see [14] for details. When a QoS VC is only being used to carry IP packets, implementations SHOULD negotiate VC based multiplexing to avoid incurring the ....
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5," RFC 1483.
Advice for Internet Subnetwork Designers - (ed.), Bormann, Fairhurst.. (2004) (5 citations) Self-citation (Grossman) (Correct)
No context found.
Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684, September 1999.
A Framework for IP Based Virtual Private Networks - Gleeson, Lin, Heinanen.. (2000) (46 citations) Self-citation (Heinanen) (Correct)
No context found.
Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684, September 1999.
A Framework for IP Based Virtual Private Networks - Gleeson, Lin, Heinaren.. (2000) (46 citations) Self-citation (Heinanen) (Correct)
No context found.
Heinanen, J. - "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC1483.
A Framework for IP Based Virtual Private Networks - Gleeson, Lin, Heinaren.. (2000) (46 citations) Self-citation (Heinanen) (Correct)
....and origin and target VPN , that are used by the underlying protocol mechanisms for disambiguation and scoping, and these are also used by the BGP policy mechanism in the construction of VPNs, but there is nothing corresponding with the VPN ID as used in the other documents. Note also that [Grossman] defines a multiprotocol encapsulation for use over ATM AAL5 that uses the standard VPN ID format. 5.2.2 VPN Membership Information Configuration and Dissemination In order to establish a VPRN, or to insert new customer sites into an established VPRN, an ISP edge router must determine which stub ....
Grossman, D. and Heinanen, J. - "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684.
Translation of Specification Units between IP and ATM Quality of.. - Schmitt (Correct)
No context found.
D. Grossmann and J. Heinanen. Multiprotocol Encapsulation over ATM Adaptation Layer 5. Proposed Standard RFC 2684, September 1999.
Radon Spectroscopy of Packet Delay - Broido, King, Nemeth, claffy (2003) (Correct)
No context found.
J.Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5, RFC1483," 1993.
Unknown - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group B. Fox Request for Comments: 2685.. - Status Of This (Correct)
No context found.
Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684, September 1999.
RSVP over ATM Implementation Requirements - Berger (1998) (5 citations) (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group R. Cole Request for Comments: 1932 D.. - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, Telecom Finland, July 1993.
Interoperation of Controlled-Load Service and Guaranteed.. - Garrett, Borden (1998) (18 citations) (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group S. Jackowski Request for Comments: 1946 .. - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group E. Crawley, Editor Request for.. - Baker Cisco Systems (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group M. Suzuki Request for Comments.. - Protocol Specification .. (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
A Pseudonymous Communications Infrastructure For The Internet - Goldberg (2000) (11 citations) (Correct)
No context found.
Juha Heinanen. Multiprotocol Encapsulation over ATM Adaptation Layer 5, July 1993. RFC 1483.
Unknown - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993. Ethernet is a registered trademark of Xerox Corp. All other product names mentioned herein may be trademarks of their respective
Unknown - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group Y. Katsube Request for Comments: 2098.. - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group M. Laubach Request for Comments: 2225.. - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group M. Laubach Request for Comments.. - Recommendations For The (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, Telecom Finland, July 1993.
MEHARI: An IP/ATM Traffic Analysis Platform based.. - Alvarez-Campana.. (1999) (Correct)
No context found.
J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, IETF, July 1993.
Unknown - (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Unknown - (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Unknown - (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Unknown - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Network Working Group A. Singh Request for Comments: 3355.. - Over Atm Adaptation (Correct)
No context found.
Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684, September 1999.
Experimental and Simulation Performance Results of TCP/IP over .. - Atm Over Acts (1998) (Correct)
No context found.
Juha Heinanen. Multiprotocol Encapsulation over ATM Adaptation Layer 5, July 1993. RFC 1483.
Network Working Group B. Fox Request for Comments: 2735.. - Status Of This (Correct)
No context found.
Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684, September 1999.
Network Working Group M. Laubach Request for Comments: 1577.. - Status Of This (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, Telecom Finland, July 1993.
Unknown - Status Of This (Correct)
No context found.
Grossman, D., Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684, September 1999.
LDP Specification - Andersson, Doolan, Feldman.. (2001) (42 citations) (Correct)
No context found.
Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 1483, July 1993.
Buffer Size (Bytes) - Mbyte Mbytes Mbytes (Correct)
No context found.
Heinanen, J., Multiprotocol Encapsulation over ATM Adaptation Layer 5, RFC1483, July 1993.
N³: A Native NBMA Networking stack - Georgopoulos, Zahariadis.. (1998) (Correct)
No context found.
J.Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5," RFC 1483, July 1993.
First 50 documents Next 50
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC