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-ipxcp-04.txt
< prev
next >
Wrap
Text File
|
1993-12-14
|
2KB
|
63 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1552:
Title: The PPP Internetworking Packet Exchange Control
Protocol (IPXCP)
Author: W. Simpson
Mailbox: Bill.Simpson@um.cc.umich.edu
Pages: 14
Characters: 29,173
Updates/Obsoletes: none
The Point-to-Point Protocol (PPP) provides a method for transmitting
multi-protocol datagrams over point-to-point links. PPP defines an
extensible Link Control Protocol, and proposes a family of Network
Control Protocols for establishing and configuring different
network-layer protocols. The IPX protocol was originally used in
Novell's NetWare products, and is now supported by numerous other
vendors. This document defines the Network Control Protocol for
establishing and configuring the IPX protocol over PPP. This memo is
the product of the Point-to-Point Protocol 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@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.
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