Académique Documents
Professionnel Documents
Culture Documents
Singh
Request for Comments: 3355 Motorola
Category: Standards Track R. Turner
Paradyne
R. Tio
S. Nanji
Redback Networks
August 2002
Copyright Notice
Abstract
Applicability
1. Introduction
2. Conventions
4. Multi-Protocol Encapsulation
An L2TP implementation:
When LLC encapsulation is used, the payload field of the AAL5 CPCS
PDU SHALL be encoded as shown in Figure 1. The pertinent fields in
that diagram are:
+-------------------------+ --------
| Destination SAP (0xAA) | ^
+-------------------------+ |
| Source SAP (0xAA) | LLC header
+-------------------------+ |
| Frame Type = UI (0x03) | V
+-------------------------+ --------
| OUI (0x00-00-5E)| |
+-+-+-+-+-+-+-+-+-+-+-+-+-| SNAP Header
| PID (0x00-07) | |
+-------------------------+ --------
| | |
| | L2TP PDU
| | |
+-------------------------+ --------
Note: The format of the overall AAL5 CPCS PDU is shown in the next
section.
+-------------------------------+ -------
| . | ^
| . | |
| CPCS-PDU payload | L2TP PDU
| up to 2^16 - 1 octets) | |
| . | V
+-------------------------------+ -------
| PAD ( 0 - 47 octets) |
+-------------------------------+ -------
| CPCS-UU (1 octet ) | ^
+-------------------------------+ |
| CPI (1 octet ) | |
+-------------------------------+CPCS-PDU Trailer
| Length (2 octets) | |
+-------------------------------| |
| CRC (4 octets) | V
+-------------------------------+ -------
The PAD field pads the CPCS-PDU to fit exactly into the ATM cells
such that the last 48 octet cell payload created by the SAR sublayer
will have the CPCS-PDU Trailer right justified in the cell.
The CPI (Common Part Indicator) field aligns the CPCS-PDU trailer to
64 bits. Possible additional functions are for further study in
ITU-T. When only the 64 bit alignment function is used, this field
SHALL be coded as 0x00.
The CRC field is computed over the entire CPCS-PDU except the CRC
field itself.
payload field will always contain an L2TP PDU. The SNAP IPI is
employed only to use the IANA L2TP protocol value to specify the VC-
multiplexed PDU.
If the caller offers both encapsulation methods and the called peer
accepts the call, the called peer SHALL specify the encapsulation
method by including exactly one B-LLI IE in the Connect message.
When a connection setup fails, the L2TP entity that attempted the
connection setup MAY consider the called entity unreachable until
notified that the unreachable entity is available. The conditions
under which an entity determines that another is unreachable and how
it determines that the other is available again are implementation
decisions.
When there are no active sessions on an SVC tunnel, either end MAY
optionally clear the connection.
8. Connection Failure
9. Security Considerations
10. Acknowledgments
This document draws heavily on material from: "PPP Over AAL5" (RFC
2364) by George Gross, Manu Kaycee, Arthur Lin, Andrew Malis, and
John Stephens and an earlier document of L2TP over AAL5 by Nagraj
Arunkumar, Manu Kaycee, Tim Kwok, and Arthur Lin.
Special thanks to Mike Davison, Arthur Lin, John Stevens for making
significant contributions to the initial version of this document.
The security section of this document is based upon RFC 3337, "Class
Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2
(AAL2)", by Bruce Thompson, Bruce Buffam and Thima Koren.
11. References
[RFC2661] Townsley, W., Valencia, A., Rubens, A., Singh Pall, G.,
Zorn, G. and B. Palter, "Layer Two Tunneling Protocol
(L2TP)", RFC 2661, August 1999.
[RFC2331] Maher, M., "ATM Signaling Support for IP over ATM - UNI
Signaling 4.0 Update", RFC 2331, April 1998.
[AFSEC1] The ATM Forum, "ATM Security Framework Version 1.0", af-
sec-0096.000, February 1998
Appendix A. Acronyms
IE Information Element
VC Virtual Circuit
Authors' Addresses
Rollins Turner
Paradyne Corporation
8545 126th Avenue North
Largo, FL 33773
EMail: rturner@eng.paradyne.com
Rene Tio
Redback Networks, Inc.
300 Holger Way
San Jose, CA 95134
EMail: tor@redback.com
Ajoy Singh
Motorola
1421 West Shure Dr,
Arlington Heights, IL 60004
EMail: asingh1@motorola.com
Suhail Nanji
Redback Networks, Inc.
300 Holger Way
Sunnyvale, CA 95134
EMail: suhail@redback.com
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
Acknowledgement