RFC1551 on IPXWAN

"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 09 December 1993 21:42 UTC

Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12093; 9 Dec 93 16:42 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa22266; 9 Dec 93 16:42 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12080; 9 Dec 93 16:42 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12010; 9 Dec 93 16:40 EST
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa22176; 9 Dec 93 16:40 EST
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-16) id <AA05466>; Thu, 9 Dec 1993 13:40:56 -0800
Message-Id: <199312092140.AA05466@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1551 on IPXWAN
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 09 Dec 1993 13:40:53 -0800
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 1551:

        Title:      Novell IPX Over Various WAN Media (IPXWAN)
        Author:     M. Allen
        Mailbox:    mallen@novell.com
        Pages:      22
        Characters: 54,210
        Obsoletes:  1362


This document describes how Novell IPX operates over various WAN
media.  Specifically, it describes the common "IPX WAN" protocol
Novell uses to exchange necessary router to router information prior
to exchanging standard IPX routing information and traffic over WAN
datalinks.  This document supercedes RFC 1362 and adds capability for
Unnumbered RIP links, On-demand statically routed links and client to
router connectivity.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ds.internic.net/rfc/rfc1551.txt"><ftp://ds.internic.net/rfc/rfc1551.txt>