RFC 3337 on Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)
rfc-editor@rfc-editor.org Sat, 14 December 2002 01:58 UTC
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13071; Fri, 13 Dec 2002 20:58:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18N1gC-00033G-00 for ietf-announce-list@ran.ietf.org; Fri, 13 Dec 2002 21:05:24 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18N13B-0001qi-00 for all-ietf@ran.ietf.org; Fri, 13 Dec 2002 20:25:05 -0500
Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12126 for <all-ietf@ietf.org>; Fri, 13 Dec 2002 20:14:15 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id gBE1HBD28857; Fri, 13 Dec 2002 17:17:11 -0800 (PST)
Message-Id: <200212140117.gBE1HBD28857@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3337 on Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 13 Dec 2002 17:17:11 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3337 Title: Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2 Author(s): B. Thompson, T. Koren, B. Buffam Status: Standards Track Date: December 2002 Mailbox: brucet@cisco.com, tmima@cisco.com, bruce@seawaynetworks.com Pages: 7 Characters: 14911 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pppext-ppp-over-aal2-class-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3337.txt The Point-to-Point Protocol (PPP) over Asynchronous Transfer Mode (ATM) Adaptation Layer 2 defines the encapsulation that allows a PPP session to be transported over an ATM virtual circuit using the ATM Adaptation Layer 2 (AAL2) adaptation layer. This document defines a set of class extensions to PPP over AAL2 that implement equivalent functionality to Multi Class Multi Link PPP over a single ATM virtual circuit. Instead of using Multi Link PPP as the basis for fragmentation functionality, this document uses the functionality of the Segmentation and Reassembly Service Specific Convergence Sublayer that is already required as the basic encapsulation format of PPP over AAL2. This document is a product of the Point-to-Point Protocol Extensions Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.