![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF.
Title : PPP over AAL5
Author(s) : M. Kaycee, A. Malis, A. Lin, J. Stephens, G. Gross
Filename : draft-ietf-pppext-aal5-06.txt
Pages : 11
Date : 06-May-98
The Point-to-Point Protocol (PPP) [1] provides a standard method
for transporting multi-protocol datagrams over point-to-point
links.
This document describes the use of ATM Adaptation Layer 5 (AAL5)
for framing PPP encapsulated packets.
Internet-Drafts are available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-ietf-pppext-aal5-06.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-pppext-aal5-06.txt
Internet-Drafts directories are located at:
Africa: ftp.is.co.za
Europe: ftp.nordu.net
ftp.nis.garr.it
Pacific Rim: munnari.oz.au
US East Coast: ftp.ietf.org
US West Coast: ftp.isi.edu
Internet-Drafts are also available by mail.
Send a message to: mailserv at ietf.org. In the body type:
"FILE /internet-drafts/draft-ietf-pppext-aal5-06.txt".
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.