home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_j_p
/
draft-ietf-pppext-multilink-12.txt
< prev
next >
Wrap
Text File
|
1996-08-16
|
3KB
|
70 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1990:
Title: The PPP Multilink Protocol (MP)
Author: K. Sklower, B. Lloyd, G. McGregor, D. Carr
& T. Coradetti
Date: August 1996
Mailbox: sklower@CS.Berkeley.EDU, brian@lloyd.com,
glenn@lloyd.com, dcarr@Newbridge.COM,
70761.1664@compuserve.com
Pages: 24
Characters: 53,271
Obsoletes: 1717
URL: ftp://ds.internic.net/rfc/rfc1990.txt
This document proposes a method for splitting, recombining and
sequencing datagrams across multiple logical data links. This work
was originally motivated by the desire to exploit multiple bearer
channels in ISDN, but is equally applicable to any situation in which
multiple PPP links connect two systems, including async links. This
is accomplished by means of new PPP options and protocols. The
differences between the current PPP Multilink specification (RFC 1717)
and this memo are explained in Section 11. Any system implementing
the additional restrictions required by this memo will be backwards
compatible with conforming RFC 1717 implementations. This RFC is the
product of the Point-to-Point Protocol Extensions Working Group of the
IETF.
This is now a Draft 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@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
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 admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute